Jul 07 20:44:01-538745 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 20:44:01-589854 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 20:44:01-600478 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 20:44:01-602537 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-614940 util-8620 DEBUG Config section `core'
Jul 07 20:44:01-619665 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-623884 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-625700 util-8620 DEBUG Config value BINARY="gnunet-service-core"
Jul 07 20:44:01-626172 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-626423 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-626680 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-core.sock"
Jul 07 20:44:01-626930 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-627185 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-628715 util-8620 DEBUG Config value USE_EPHEMERAL_KEYS="YES"
Jul 07 20:44:01-629984 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-632612 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 20:44:01-632987 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 20:44:01-633467 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 20:44:01-633876 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-634197 util-8620 DEBUG Config section `namestore'
Jul 07 20:44:01-634414 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-635291 util-8620 DEBUG Config value USER_SERVICE="YES"
Jul 07 20:44:01-635563 util-8620 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-namestore.sock"
Jul 07 20:44:01-635820 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-636068 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-636335 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-636586 util-8620 DEBUG Config value BINARY="gnunet-service-namestore"
Jul 07 20:44:01-636836 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-637086 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-637376 util-8620 DEBUG Config value DATABASE="sqlite"
Jul 07 20:44:01-637639 util-8620 DEBUG Config section `namestore-sqlite'
Jul 07 20:44:01-637853 util-8620 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/namestore/sqlite.db"
Jul 07 20:44:01-638135 util-8620 DEBUG Config section `namestore-postgres'
Jul 07 20:44:01-638350 util-8620 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 20:44:01-638615 util-8620 DEBUG Config value TEMPORARY_TABLE="NO"
Jul 07 20:44:01-638874 util-8620 DEBUG Config section `uri'
Jul 07 20:44:01-639082 util-8620 DEBUG Config value gns="gnunet-namestore"
Jul 07 20:44:01-639349 util-8620 DEBUG Config section `fcfsd'
Jul 07 20:44:01-639581 util-8620 DEBUG Config value BINARY="gnunet-namestore-fcfsd"
Jul 07 20:44:01-639833 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-640192 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-fcfsd.sock"
Jul 07 20:44:01-640483 util-8620 DEBUG Config value HTTPPORT="18080"
Jul 07 20:44:01-640891 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-641112 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 20:44:01-641353 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 20:44:01-641623 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 20:44:01-641807 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-642014 util-8620 DEBUG Config section `vpn'
Jul 07 20:44:01-642220 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-642483 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-642743 util-8620 DEBUG Config value BINARY="gnunet-service-vpn"
Jul 07 20:44:01-642986 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-643229 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-643482 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-vpn.sock"
Jul 07 20:44:01-643740 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-643987 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-644246 util-8620 DEBUG Config value IPV6ADDR="1234::1"
Jul 07 20:44:01-644489 util-8620 DEBUG Config value IPV6PREFIX="32"
Jul 07 20:44:01-644735 util-8620 DEBUG Config value IPV4ADDR="10.11.10.1"
Jul 07 20:44:01-644983 util-8620 DEBUG Config value IPV4MASK="255.255.0.0"
Jul 07 20:44:01-645273 util-8620 DEBUG Config value VIRTDNS="10.11.10.2"
Jul 07 20:44:01-645523 util-8620 DEBUG Config value VIRTDNS6="1234::17"
Jul 07 20:44:01-645772 util-8620 DEBUG Config value IFNAME="vpn-gnunet"
Jul 07 20:44:01-646002 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-646212 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 20:44:01-646409 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 20:44:01-646695 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 20:44:01-646879 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-647096 util-8620 DEBUG Config section `arm'
Jul 07 20:44:01-647317 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-647571 util-8620 DEBUG Config value BINARY="gnunet-service-arm"
Jul 07 20:44:01-647812 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-648065 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-648328 util-8620 DEBUG Config value DEFAULTSERVICES="topology hostlist dht nse cadet fs revocation"
Jul 07 20:44:01-648603 util-8620 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-arm.sock"
Jul 07 20:44:01-648852 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-649097 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-650473 util-8620 DEBUG Config value GLOBAL_PREFIX=""
Jul 07 20:44:01-651229 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-651449 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 20:44:01-651646 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 20:44:01-651912 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 20:44:01-652096 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-652302 util-8620 DEBUG Config section `set'
Jul 07 20:44:01-652511 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-652778 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-653029 util-8620 DEBUG Config value BINARY="gnunet-service-set"
Jul 07 20:44:01-653311 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-653555 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-653809 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-set.sock"
Jul 07 20:44:01-654056 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-654301 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-654519 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-654730 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 20:44:01-654927 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 20:44:01-655193 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 20:44:01-655377 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-655584 util-8620 DEBUG Config section `cadet'
Jul 07 20:44:01-655792 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-656074 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-656334 util-8620 DEBUG Config value BINARY="gnunet-service-cadet"
Jul 07 20:44:01-656579 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-656822 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-657077 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock"
Jul 07 20:44:01-657350 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-657597 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-657850 util-8620 DEBUG Config value REFRESH_CONNECTION_TIME="5 min"
Jul 07 20:44:01-658098 util-8620 DEBUG Config value ID_ANNOUNCE_TIME="1 h"
Jul 07 20:44:01-658345 util-8620 DEBUG Config value CONNECT_TIMEOUT="30 s"
Jul 07 20:44:01-658641 util-8620 DEBUG Config value DEFAULT_TTL="64"
Jul 07 20:44:01-658899 util-8620 DEBUG Config value DHT_REPLICATION_LEVEL="3"
Jul 07 20:44:01-659150 util-8620 DEBUG Config value MAX_TUNNELS="1000"
Jul 07 20:44:01-659400 util-8620 DEBUG Config value MAX_CONNECTIONS="1000"
Jul 07 20:44:01-659655 util-8620 DEBUG Config value MAX_MSGS_QUEUE="10000"
Jul 07 20:44:01-659908 util-8620 DEBUG Config value MAX_PEERS="1000"
Jul 07 20:44:01-660163 util-8620 DEBUG Config value REKEY_PERIOD="12 h"
Jul 07 20:44:01-660384 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-660596 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 20:44:01-660793 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 20:44:01-661063 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 20:44:01-661286 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-661502 util-8620 DEBUG Config section `peerinfo'
Jul 07 20:44:01-661712 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-661982 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-662227 util-8620 DEBUG Config value BINARY="gnunet-service-peerinfo"
Jul 07 20:44:01-662473 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-662718 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-662976 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock"
Jul 07 20:44:01-663228 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-663476 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-663862 util-8620 DEBUG Config value HOSTS="$GNUNET_DATA_HOME/peerinfo/hosts/"
Jul 07 20:44:01-664162 util-8620 DEBUG Config value NO_IO="NO"
Jul 07 20:44:01-664437 util-8620 DEBUG Config value USE_INCLUDED_HELLOS="YES"
Jul 07 20:44:01-664696 util-8620 DEBUG Config section `uri'
Jul 07 20:44:01-664904 util-8620 DEBUG Config value hello="gnunet-peerinfo"
Jul 07 20:44:01-665153 util-8620 DEBUG Config value friend-hello="gnunet-peerinfo"
Jul 07 20:44:01-665398 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-665611 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 20:44:01-665807 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 20:44:01-666103 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 20:44:01-666287 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-666495 util-8620 DEBUG Config section `transport'
Jul 07 20:44:01-666702 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-666974 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-667221 util-8620 DEBUG Config value BINARY="gnunet-service-transport"
Jul 07 20:44:01-667491 util-8620 DEBUG Config value NEIGHBOUR_LIMIT="50"
Jul 07 20:44:01-667737 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-667995 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-668245 util-8620 DEBUG Config value PLUGINS="tcp udp"
Jul 07 20:44:01-668499 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock"
Jul 07 20:44:01-668763 util-8620 DEBUG Config value BLACKLIST_FILE="$GNUNET_CONFIG_HOME/transport/blacklist"
Jul 07 20:44:01-669033 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-669324 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-669858 util-8620 DEBUG Config section `transport-unix'
Jul 07 20:44:01-670079 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-transport-plugin-unix.sock"
Jul 07 20:44:01-670355 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-670615 util-8620 DEBUG Config section `transport-tcp'
Jul 07 20:44:01-670842 util-8620 DEBUG Config value PORT="2086"
Jul 07 20:44:01-671116 util-8620 DEBUG Config value ADVERTISED_PORT="2086"
Jul 07 20:44:01-671365 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-671639 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-671905 util-8620 DEBUG Config value TIMEOUT="5 s"
Jul 07 20:44:01-672221 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-673388 util-8620 DEBUG Config section `transport-udp'
Jul 07 20:44:01-673624 util-8620 DEBUG Config value PORT="2086"
Jul 07 20:44:01-673909 util-8620 DEBUG Config value BROADCAST="YES"
Jul 07 20:44:01-674157 util-8620 DEBUG Config value BROADCAST_RECEIVE="YES"
Jul 07 20:44:01-674414 util-8620 DEBUG Config value BROADCAST_INTERVAL="30 s"
Jul 07 20:44:01-674670 util-8620 DEBUG Config value MAX_BPS="1000000"
Jul 07 20:44:01-674920 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-675194 util-8620 DEBUG Config section `transport-http_client'
Jul 07 20:44:01-675406 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-675700 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-676189 util-8620 DEBUG Config section `transport-http_server'
Jul 07 20:44:01-676416 util-8620 DEBUG Config value PORT="1080"
Jul 07 20:44:01-676719 util-8620 DEBUG Config value ADVERTISED_PORT="1080"
Jul 07 20:44:01-676971 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-677273 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-677545 util-8620 DEBUG Config section `transport-https_client'
Jul 07 20:44:01-677756 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-678073 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-678581 util-8620 DEBUG Config section `transport-https_server'
Jul 07 20:44:01-678905 util-8620 DEBUG Config value PORT="4433"
Jul 07 20:44:01-679241 util-8620 DEBUG Config value ADVERTISED_PORT="4433"
Jul 07 20:44:01-679498 util-8620 DEBUG Config value CRYPTO_INIT="NORMAL"
Jul 07 20:44:01-679756 util-8620 DEBUG Config value KEY_FILE="$GNUNET_DATA_HOME/transport/https.key"
Jul 07 20:44:01-680023 util-8620 DEBUG Config value CERT_FILE="$GNUNET_DATA_HOME/transport/https.cert"
Jul 07 20:44:01-680283 util-8620 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 20:44:01-680540 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-680809 util-8620 DEBUG Config section `transport-wlan'
Jul 07 20:44:01-681035 util-8620 DEBUG Config value INTERFACE="mon0"
Jul 07 20:44:01-681397 util-8620 DEBUG Config value TESTMODE="0"
Jul 07 20:44:01-681655 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-681918 util-8620 DEBUG Config section `transport-bluetooth'
Jul 07 20:44:01-682145 util-8620 DEBUG Config value INTERFACE="hci0"
Jul 07 20:44:01-682489 util-8620 DEBUG Config value TESTMODE="0"
Jul 07 20:44:01-682740 util-8620 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 20:44:01-682964 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-683181 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 20:44:01-683378 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 20:44:01-683666 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 20:44:01-683850 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-684077 util-8620 DEBUG Config section `ats'
Jul 07 20:44:01-684286 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-684570 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-684811 util-8620 DEBUG Config value BINARY="gnunet-service-ats"
Jul 07 20:44:01-685052 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-685335 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-685590 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-ats.sock"
Jul 07 20:44:01-685838 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-686101 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-686379 util-8620 DEBUG Config value MODE="PROPORTIONAL"
Jul 07 20:44:01-686652 util-8620 DEBUG Config value UNSPECIFIED_QUOTA_IN="64 KiB"
Jul 07 20:44:01-686904 util-8620 DEBUG Config value UNSPECIFIED_QUOTA_OUT="64 KiB"
Jul 07 20:44:01-687175 util-8620 DEBUG Config value LOOPBACK_QUOTA_IN="unlimited"
Jul 07 20:44:01-687425 util-8620 DEBUG Config value LOOPBACK_QUOTA_OUT="unlimited"
Jul 07 20:44:01-687694 util-8620 DEBUG Config value LAN_QUOTA_IN="unlimited"
Jul 07 20:44:01-687943 util-8620 DEBUG Config value LAN_QUOTA_OUT="unlimited"
Jul 07 20:44:01-688209 util-8620 DEBUG Config value WAN_QUOTA_IN="64 KiB"
Jul 07 20:44:01-688468 util-8620 DEBUG Config value WAN_QUOTA_OUT="64 KiB"
Jul 07 20:44:01-688734 util-8620 DEBUG Config value WLAN_QUOTA_IN="1 MiB"
Jul 07 20:44:01-688986 util-8620 DEBUG Config value WLAN_QUOTA_OUT="1 MiB"
Jul 07 20:44:01-689284 util-8620 DEBUG Config value BLUETOOTH_QUOTA_IN="128 KiB"
Jul 07 20:44:01-689543 util-8620 DEBUG Config value BLUETOOTH_QUOTA_OUT="128 KiB"
Jul 07 20:44:01-689898 util-8620 DEBUG Config value PROP_PROPORTIONALITY_FACTOR="2.00"
Jul 07 20:44:01-690192 util-8620 DEBUG Config value PROP_STABILITY_FACTOR="1.25"
Jul 07 20:44:01-690589 util-8620 DEBUG Config value MLP_MAX_MIP_GAP="0.025"
Jul 07 20:44:01-690863 util-8620 DEBUG Config value MLP_MAX_LP_MIP_GAP="0.025"
Jul 07 20:44:01-691385 util-8620 DEBUG Config value MLP_DUMP_PROBLEM_ON_FAIL="YES"
Jul 07 20:44:01-691663 util-8620 DEBUG Config value MLP_DUMP_SOLUTION_ON_FAIL="YES"
Jul 07 20:44:01-692010 util-8620 DEBUG Config value RIL_STEP_TIME_MIN="500 ms"
Jul 07 20:44:01-692281 util-8620 DEBUG Config value RIL_STEP_TIME_MAX="1000 ms"
Jul 07 20:44:01-692572 util-8620 DEBUG Config value RIL_ALGORITHM="Q-LEARNING"
Jul 07 20:44:01-692834 util-8620 DEBUG Config value RIL_DISCOUNT_BETA="0.7"
Jul 07 20:44:01-693098 util-8620 DEBUG Config value RIL_GRADIENT_STEP_SIZE="0.3"
Jul 07 20:44:01-693405 util-8620 DEBUG Config value RIL_TRACE_DECAY="0.2"
Jul 07 20:44:01-693673 util-8620 DEBUG Config value RIL_EXPLORE_RATIO="0.1"
Jul 07 20:44:01-693944 util-8620 DEBUG Config value RIL_GLOBAL_REWARD_SHARE="1"
Jul 07 20:44:01-694187 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-694403 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 20:44:01-694599 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 20:44:01-694919 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 20:44:01-695104 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-695311 util-8620 DEBUG Config section `exit'
Jul 07 20:44:01-695520 util-8620 DEBUG Config value BINARY="gnunet-daemon-exit"
Jul 07 20:44:01-695839 util-8620 DEBUG Config value IPV6ADDR="2001:DB8::1"
Jul 07 20:44:01-696136 util-8620 DEBUG Config value IPV6PREFIX="64"
Jul 07 20:44:01-696459 util-8620 DEBUG Config value IPV4ADDR="169.254.86.1"
Jul 07 20:44:01-696735 util-8620 DEBUG Config value IPV4MASK="255.255.255.0"
Jul 07 20:44:01-697032 util-8620 DEBUG Config value EXIT_RANGE_IPV4_POLICY="0.0.0.0/0:!25;"
Jul 07 20:44:01-697351 util-8620 DEBUG Config value EXIT_RANGE_IPV6_POLICY="::/0:!25;"
Jul 07 20:44:01-697702 util-8620 DEBUG Config value TUN_IFNAME="exit-gnunet"
Jul 07 20:44:01-698084 util-8620 DEBUG Config value EXIT_IFNAME="eth0"
Jul 07 20:44:01-698372 util-8620 DEBUG Config value EXIT_IPV4="NO"
Jul 07 20:44:01-698666 util-8620 DEBUG Config value EXIT_IPV6="NO"
Jul 07 20:44:01-699054 util-8620 DEBUG Config value EXIT_DNS="NO"
Jul 07 20:44:01-699341 util-8620 DEBUG Config value DNS_RESOLVER="8.8.8.8"
Jul 07 20:44:01-699620 util-8620 DEBUG Config value ENABLE_IPV4="YES"
Jul 07 20:44:01-699900 util-8620 DEBUG Config value ENABLE_IPV6="YES"
Jul 07 20:44:01-700205 util-8620 DEBUG Config value MAX_CONNECTIONS="256"
Jul 07 20:44:01-700426 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-700644 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 20:44:01-700841 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 20:44:01-701145 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 20:44:01-701388 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-701597 util-8620 DEBUG Config section `testbed'
Jul 07 20:44:01-701808 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-702104 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-702348 util-8620 DEBUG Config value BINARY="gnunet-service-testbed"
Jul 07 20:44:01-702620 util-8620 DEBUG Config value OPERATION_TIMEOUT="30 s"
Jul 07 20:44:01-703023 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-703281 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-703549 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-testbed.sock"
Jul 07 20:44:01-703801 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-704049 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-704366 util-8620 DEBUG Config value MAX_PARALLEL_OPERATIONS="1000"
Jul 07 20:44:01-704620 util-8620 DEBUG Config value MAX_PARALLEL_TOPOLOGY_CONFIG_OPERATIONS="1"
Jul 07 20:44:01-704969 util-8620 DEBUG Config value OVERLAY_TOPOLOGY="NONE"
Jul 07 20:44:01-705560 util-8620 DEBUG Config value MAX_PARALLEL_SERVICE_CONNECTIONS="256"
Jul 07 20:44:01-705868 util-8620 DEBUG Config value CACHE_SIZE="30"
Jul 07 20:44:01-706161 util-8620 DEBUG Config value MAX_OPEN_FDS="512"
Jul 07 20:44:01-706472 util-8620 DEBUG Config value SETUP_TIMEOUT="5 m"
Jul 07 20:44:01-706993 util-8620 DEBUG Config value SHARED_SERVICES=""
Jul 07 20:44:01-707267 util-8620 DEBUG Config section `testbed-logger'
Jul 07 20:44:01-707476 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-707778 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-708028 util-8620 DEBUG Config value BINARY="gnunet-service-testbed-logger"
Jul 07 20:44:01-708297 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-gnunet-testbed-logger.sock"
Jul 07 20:44:01-708552 util-8620 DEBUG Config value DIR="/tmp"
Jul 07 20:44:01-708799 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-709051 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-709368 util-8620 DEBUG Config section `testbed-barrier'
Jul 07 20:44:01-709579 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-709886 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-710144 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-testbed-barrier.sock"
Jul 07 20:44:01-710400 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-710651 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-710972 util-8620 DEBUG Config section `testbed-underlay'
Jul 07 20:44:01-711182 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-711487 util-8620 DEBUG Config value BINARY="gnunet-daemon-testbed-underlay"
Jul 07 20:44:01-711799 util-8620 DEBUG Config section `latency-logger'
Jul 07 20:44:01-712008 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-712290 util-8620 DEBUG Config value BINARY="gnunet-daemon-latency-logger"
Jul 07 20:44:01-712544 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-712767 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 20:44:01-712981 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 20:44:01-713285 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 20:44:01-713473 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-713681 util-8620 DEBUG Config section `revocation'
Jul 07 20:44:01-713888 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-714199 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-714448 util-8620 DEBUG Config value BINARY="gnunet-service-revocation"
Jul 07 20:44:01-714696 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-714986 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-715247 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-revocation.unix"
Jul 07 20:44:01-715502 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-715751 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-716076 util-8620 DEBUG Config value WORKBITS="25"
Jul 07 20:44:01-716339 util-8620 DEBUG Config value DATABASE="$GNUNET_DATA_HOME/revocation.dat"
Jul 07 20:44:01-716562 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-716774 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 20:44:01-716971 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 20:44:01-717273 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 20:44:01-717459 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-717667 util-8620 DEBUG Config section `topology'
Jul 07 20:44:01-717875 util-8620 DEBUG Config value MINIMUM-FRIENDS="0"
Jul 07 20:44:01-718168 util-8620 DEBUG Config value FRIENDS-ONLY="NO"
Jul 07 20:44:01-718413 util-8620 DEBUG Config value TARGET-CONNECTION-COUNT="16"
Jul 07 20:44:01-718665 util-8620 DEBUG Config value FRIENDS="$GNUNET_CONFIG_HOME/topology/friends.txt"
Jul 07 20:44:01-718918 util-8620 DEBUG Config value BINARY="gnunet-daemon-topology"
Jul 07 20:44:01-719144 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-719353 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 20:44:01-719549 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 20:44:01-719826 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 20:44:01-720010 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-720215 util-8620 DEBUG Config section `fs'
Jul 07 20:44:01-720423 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-720709 util-8620 DEBUG Config value INDEXDB="$GNUNET_DATA_HOME/fs/idxinfo.lst"
Jul 07 20:44:01-720974 util-8620 DEBUG Config value RESPECT="$GNUNET_DATA_HOME/fs/credit/"
Jul 07 20:44:01-721244 util-8620 DEBUG Config value STATE_DIR="$GNUNET_DATA_HOME/fs/persistence/"
Jul 07 20:44:01-721495 util-8620 DEBUG Config value UPDATE_DIR="$GNUNET_DATA_HOME/fs/updates/"
Jul 07 20:44:01-721756 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-722000 util-8620 DEBUG Config value BINARY="gnunet-service-fs"
Jul 07 20:44:01-722244 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-722488 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-722762 util-8620 DEBUG Config value DELAY="YES"
Jul 07 20:44:01-723034 util-8620 DEBUG Config value CONTENT_CACHING="YES"
Jul 07 20:44:01-723342 util-8620 DEBUG Config value CONTENT_PUSHING="YES"
Jul 07 20:44:01-723609 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-fs.sock"
Jul 07 20:44:01-723907 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-724186 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-724486 util-8620 DEBUG Config value MAX_PENDING_REQUESTS="65536"
Jul 07 20:44:01-724782 util-8620 DEBUG Config value DATASTORE_QUEUE_SIZE="1024"
Jul 07 20:44:01-725099 util-8620 DEBUG Config value MIN_MIGRATION_DELAY="100 ms"
Jul 07 20:44:01-725434 util-8620 DEBUG Config value EXPECTED_NEIGHBOUR_COUNT="128"
Jul 07 20:44:01-725734 util-8620 DEBUG Config value DISABLE_ANON_TRANSFER="NO"
Jul 07 20:44:01-726102 util-8620 DEBUG Config value MAX_CADET_CLIENTS="128"
Jul 07 20:44:01-726379 util-8620 DEBUG Config section `gnunet-auto-share'
Jul 07 20:44:01-726589 util-8620 DEBUG Config value BINARY="gnunet-auto-share"
Jul 07 20:44:01-726924 util-8620 DEBUG Config value OPTIONS="$GNUNET_DATA_HOME/fs/share/"
Jul 07 20:44:01-727194 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-727413 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 20:44:01-727613 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 20:44:01-727878 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 20:44:01-728062 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-728271 util-8620 DEBUG Config section `datacache-postgres'
Jul 07 20:44:01-728485 util-8620 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 20:44:01-728744 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-728954 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 20:44:01-729151 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 20:44:01-729444 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 20:44:01-729628 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-729834 util-8620 DEBUG Config section `identity'
Jul 07 20:44:01-730042 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-730328 util-8620 DEBUG Config value USER_SERVICE="YES"
Jul 07 20:44:01-730584 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-730839 util-8620 DEBUG Config value BINARY="gnunet-service-identity"
Jul 07 20:44:01-731086 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-731332 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-731591 util-8620 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-identity.unix"
Jul 07 20:44:01-731847 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-732095 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-732380 util-8620 DEBUG Config value EGODIR="$GNUNET_DATA_HOME/identity/egos/"
Jul 07 20:44:01-732672 util-8620 DEBUG Config value SUBSYSTEM_CFG="$GNUNET_CONFIG_HOME/identity/subsystem_defaults.conf"
Jul 07 20:44:01-732899 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-733612 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 20:44:01-733826 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 20:44:01-734099 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 20:44:01-734283 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-734490 util-8620 DEBUG Config section `dht'
Jul 07 20:44:01-734697 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-735000 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-735241 util-8620 DEBUG Config value BINARY="gnunet-service-dht"
Jul 07 20:44:01-735481 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-735723 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-735967 util-8620 DEBUG Config value BUCKET_SIZE="4"
Jul 07 20:44:01-736216 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock"
Jul 07 20:44:01-736488 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-736734 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-737133 util-8620 DEBUG Config value CACHE_RESULTS="YES"
Jul 07 20:44:01-737436 util-8620 DEBUG Config value DISABLE_TRY_CONNECT="NO"
Jul 07 20:44:01-737702 util-8620 DEBUG Config section `dhtcache'
Jul 07 20:44:01-737910 util-8620 DEBUG Config value DATABASE="heap"
Jul 07 20:44:01-738216 util-8620 DEBUG Config value QUOTA="50 MB"
Jul 07 20:44:01-738501 util-8620 DEBUG Config value DISABLE_BF_RC="NO"
Jul 07 20:44:01-738716 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-738929 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 20:44:01-739127 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 20:44:01-739394 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 20:44:01-739577 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-739784 util-8620 DEBUG Config section `TESTING'
Jul 07 20:44:01-740020 util-8620 DEBUG Config value CONNECT_TIMEOUT="30 s"
Jul 07 20:44:01-740347 util-8620 DEBUG Config value CONNECT_ATTEMPTS="3"
Jul 07 20:44:01-740612 util-8620 DEBUG Config value MAX_OUTSTANDING_CONNECTIONS="50"
Jul 07 20:44:01-740934 util-8620 DEBUG Config value DELETE_FILES="YES"
Jul 07 20:44:01-741159 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-741408 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 20:44:01-741613 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 20:44:01-741880 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 20:44:01-742065 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-742270 util-8620 DEBUG Config section `pt'
Jul 07 20:44:01-742478 util-8620 DEBUG Config value BINARY="gnunet-daemon-pt"
Jul 07 20:44:01-742799 util-8620 DEBUG Config value TUNNEL_IPV4="NO"
Jul 07 20:44:01-743065 util-8620 DEBUG Config value TUNNEL_IPV6="NO"
Jul 07 20:44:01-743333 util-8620 DEBUG Config value TUNNEL_DNS="NO"
Jul 07 20:44:01-743558 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-743769 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 20:44:01-743965 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 20:44:01-744232 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 20:44:01-744416 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-744632 util-8620 DEBUG Config section `template'
Jul 07 20:44:01-744840 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-745148 util-8620 DEBUG Config value PORT="9999"
Jul 07 20:44:01-745414 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-745661 util-8620 DEBUG Config value BINARY="gnunet-service-template"
Jul 07 20:44:01-745908 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-746154 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-746412 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-template.sock"
Jul 07 20:44:01-746664 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-746912 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-747268 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-747481 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 20:44:01-747677 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 20:44:01-747956 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 20:44:01-748140 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-748347 util-8620 DEBUG Config section `PATHS'
Jul 07 20:44:01-748722 util-8620 DEBUG Config value GNUNET_HOME="${GNUNET_TEST_HOME:-${HOME:-${USERPROFILE}}}"
Jul 07 20:44:01-749123 util-8620 DEBUG Config value GNUNET_DATA_HOME="${XDG_DATA_HOME:-$GNUNET_HOME/.local/share}/gnunet/"
Jul 07 20:44:01-749453 util-8620 DEBUG Config value GNUNET_CONFIG_HOME="${XDG_CONFIG_HOME:-$GNUNET_HOME/.config}/gnunet/"
Jul 07 20:44:01-749747 util-8620 DEBUG Config value GNUNET_CACHE_HOME="${XDG_CACHE_HOME:-$GNUNET_HOME/.cache}/gnunet/"
Jul 07 20:44:01-750195 util-8620 DEBUG Config value GNUNET_RUNTIME_DIR="${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/"
Jul 07 20:44:01-750501 util-8620 DEBUG Config value GNUNET_USER_RUNTIME_DIR="${TMPDIR:-${TMP:-/tmp}}/gnunet-${USERHOME:-${USER:-user}}-runtime/"
Jul 07 20:44:01-750925 util-8620 DEBUG Config section `PEER'
Jul 07 20:44:01-751138 util-8620 DEBUG Config value PRIVATE_KEY="$GNUNET_DATA_HOME/private_key.ecc"
Jul 07 20:44:01-751463 util-8620 DEBUG Config section `TESTING'
Jul 07 20:44:01-751676 util-8620 DEBUG Config value SPEEDUP_INTERVAL="0 ms"
Jul 07 20:44:01-751927 util-8620 DEBUG Config value SPEEDUP_DELTA="0 ms"
Jul 07 20:44:01-752265 util-8620 DEBUG Config value USE_ABSTRACT_SOCKETS="NO"
Jul 07 20:44:01-752490 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-752705 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 20:44:01-752901 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 20:44:01-753174 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 20:44:01-753384 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-753591 util-8620 DEBUG Config section `nat'
Jul 07 20:44:01-753813 util-8620 DEBUG Config value BEHIND_NAT="NO"
Jul 07 20:44:01-754148 util-8620 DEBUG Config value PUNCHED_NAT="NO"
Jul 07 20:44:01-754413 util-8620 DEBUG Config value ENABLE_UPNP="NO"
Jul 07 20:44:01-754683 util-8620 DEBUG Config value USE_LOCALADDR="YES"
Jul 07 20:44:01-754952 util-8620 DEBUG Config value USE_HOSTNAME="NO"
Jul 07 20:44:01-755322 util-8620 DEBUG Config value ENABLE_ICMP_CLIENT="NO"
Jul 07 20:44:01-755568 util-8620 DEBUG Config value ENABLE_ICMP_SERVER="NO"
Jul 07 20:44:01-755930 util-8620 DEBUG Config value DISABLEV6="NO"
Jul 07 20:44:01-756205 util-8620 DEBUG Config value RETURN_LOCAL_ADDRESSES="NO"
Jul 07 20:44:01-756495 util-8620 DEBUG Config value HOSTNAME_DNS_FREQUENCY="20 min"
Jul 07 20:44:01-756799 util-8620 DEBUG Config value IFC_SCAN_FREQUENCY="15 min"
Jul 07 20:44:01-757090 util-8620 DEBUG Config value DYNDNS_FREQUENCY="7 min"
Jul 07 20:44:01-757389 util-8620 DEBUG Config section `gnunet-nat-server'
Jul 07 20:44:01-757611 util-8620 DEBUG Config value HOSTNAME="gnunet.org"
Jul 07 20:44:01-757915 util-8620 DEBUG Config value PORT="5724"
Jul 07 20:44:01-758153 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-758368 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 20:44:01-758565 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 20:44:01-758836 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 20:44:01-759020 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-759227 util-8620 DEBUG Config section `hostlist'
Jul 07 20:44:01-759437 util-8620 DEBUG Config value BINARY="gnunet-daemon-hostlist"
Jul 07 20:44:01-759764 util-8620 DEBUG Config value HTTPPORT="8080"
Jul 07 20:44:01-760110 util-8620 DEBUG Config value HOSTLISTFILE="$GNUNET_CONFIG_HOME/hostlist/learned.txt"
Jul 07 20:44:01-760458 util-8620 DEBUG Config value OPTIONS="-b"
Jul 07 20:44:01-760732 util-8620 DEBUG Config value SERVERS="http://v10.gnunet.org/hostlist"
Jul 07 20:44:01-761251 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-761467 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 20:44:01-761666 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 20:44:01-761930 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 20:44:01-762114 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-762320 util-8620 DEBUG Config section `regex'
Jul 07 20:44:01-762527 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-762859 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-regex.sock"
Jul 07 20:44:01-763106 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-763363 util-8620 DEBUG Config value BINARY="gnunet-service-regex"
Jul 07 20:44:01-763609 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-763854 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-764070 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-764280 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 20:44:01-764475 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 20:44:01-764753 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 20:44:01-764981 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-765187 util-8620 DEBUG Config section `dns'
Jul 07 20:44:01-765434 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-765737 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-765979 util-8620 DEBUG Config value BINARY="gnunet-service-dns"
Jul 07 20:44:01-766227 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-dns.sock"
Jul 07 20:44:01-766537 util-8620 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 20:44:01-766781 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-767115 util-8620 DEBUG Config value IFNAME="gnunet-dns"
Jul 07 20:44:01-767418 util-8620 DEBUG Config value IPV6ADDR="2001:DB8::1"
Jul 07 20:44:01-767663 util-8620 DEBUG Config value IPV6PREFIX="126"
Jul 07 20:44:01-767935 util-8620 DEBUG Config value IPV4ADDR="169.254.1.1"
Jul 07 20:44:01-768184 util-8620 DEBUG Config value IPV4MASK="255.255.0.0"
Jul 07 20:44:01-768523 util-8620 DEBUG Config value DNS_EXIT="8.8.8.8"
Jul 07 20:44:01-768750 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-768964 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 20:44:01-769160 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 20:44:01-769464 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 20:44:01-769648 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-769853 util-8620 DEBUG Config section `gns'
Jul 07 20:44:01-770060 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-770366 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-770606 util-8620 DEBUG Config value BINARY="gnunet-service-gns"
Jul 07 20:44:01-770858 util-8620 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-gns.sock"
Jul 07 20:44:01-771118 util-8620 DEBUG Config value USER_SERVICE="YES"
Jul 07 20:44:01-771402 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-771688 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-771971 util-8620 DEBUG Config value MAX_PARALLEL_BACKGROUND_QUERIES="1000"
Jul 07 20:44:01-772248 util-8620 DEBUG Config value ZONE_PUBLISH_TIME_WINDOW="4 h"
Jul 07 20:44:01-772570 util-8620 DEBUG Config section `gns-proxy'
Jul 07 20:44:01-772779 util-8620 DEBUG Config value BINARY="gnunet-gns-proxy"
Jul 07 20:44:01-773091 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-773372 util-8620 DEBUG Config value USER_SERVICE="YES"
Jul 07 20:44:01-773651 util-8620 DEBUG Config value PROXY_CACERT="$GNUNET_DATA_HOME/gns/gns_ca_cert.pem"
Jul 07 20:44:01-773919 util-8620 DEBUG Config value PROXY_UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-gns-proxy.sock"
Jul 07 20:44:01-774195 util-8620 DEBUG Config section `dns2gns'
Jul 07 20:44:01-774403 util-8620 DEBUG Config value BINARY="gnunet-dns2gns"
Jul 07 20:44:01-774714 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-774955 util-8620 DEBUG Config value USER_SERVICE="YES"
Jul 07 20:44:01-775226 util-8620 DEBUG Config value OPTIONS="-d 8.8.8.8"
Jul 07 20:44:01-775440 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-775653 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 20:44:01-775861 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 20:44:01-776145 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 20:44:01-776328 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-776535 util-8620 DEBUG Config section `namecache'
Jul 07 20:44:01-776742 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-777068 util-8620 DEBUG Config value USER_SERVICE="NO"
Jul 07 20:44:01-777346 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-namecache.sock"
Jul 07 20:44:01-777597 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-777843 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-778109 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-778357 util-8620 DEBUG Config value BINARY="gnunet-service-namecache"
Jul 07 20:44:01-778606 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-778854 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-779105 util-8620 DEBUG Config value DATABASE="sqlite"
Jul 07 20:44:01-779372 util-8620 DEBUG Config section `namecache-sqlite'
Jul 07 20:44:01-779585 util-8620 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/namecache/sqlite.db"
Jul 07 20:44:01-779927 util-8620 DEBUG Config section `namecache-postgres'
Jul 07 20:44:01-780140 util-8620 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 20:44:01-780478 util-8620 DEBUG Config value TEMPORARY_TABLE="NO"
Jul 07 20:44:01-780729 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-780941 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 20:44:01-781140 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 20:44:01-781448 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 20:44:01-781633 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-781843 util-8620 DEBUG Config section `statistics'
Jul 07 20:44:01-782051 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-782378 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-782634 util-8620 DEBUG Config value BINARY="gnunet-service-statistics"
Jul 07 20:44:01-782883 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-783129 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-783387 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock"
Jul 07 20:44:01-783641 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-783890 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-784146 util-8620 DEBUG Config value DATABASE="$GNUNET_DATA_HOME/statistics.dat"
Jul 07 20:44:01-784501 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-784712 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 20:44:01-784908 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 20:44:01-785213 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 20:44:01-785400 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-785606 util-8620 DEBUG Config section `nse'
Jul 07 20:44:01-785813 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-786145 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-786385 util-8620 DEBUG Config value BINARY="gnunet-service-nse"
Jul 07 20:44:01-786626 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-786867 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-787128 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-nse.unix"
Jul 07 20:44:01-787375 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-787618 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-787870 util-8620 DEBUG Config value PROOFFILE="$GNUNET_DATA_HOME/nse/proof.dat"
Jul 07 20:44:01-788182 util-8620 DEBUG Config value HISTOGRAM_DIR="$GNUNET_CACHE_HOME/nse/histogram"
Jul 07 20:44:01-788558 util-8620 DEBUG Config value WORKDELAY="5 ms"
Jul 07 20:44:01-788909 util-8620 DEBUG Config value INTERVAL="1 h"
Jul 07 20:44:01-789284 util-8620 DEBUG Config value WORKBITS="22"
Jul 07 20:44:01-789515 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-789730 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 20:44:01-789926 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 20:44:01-790194 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 20:44:01-790377 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-790584 util-8620 DEBUG Config section `resolver'
Jul 07 20:44:01-790792 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-791124 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-791369 util-8620 DEBUG Config value BINARY="gnunet-service-resolver"
Jul 07 20:44:01-791615 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-791872 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-792131 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-resolver.sock"
Jul 07 20:44:01-792382 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-792630 util-8620 DEBUG Config value UNIX_MATCH_GID="NO"
Jul 07 20:44:01-792985 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-793223 util-8620 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 20:44:01-793423 util-8620 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 20:44:01-793691 util-8620 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 20:44:01-793875 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-794083 util-8620 DEBUG Config section `datastore'
Jul 07 20:44:01-794302 util-8620 DEBUG Config value AUTOSTART="YES"
Jul 07 20:44:01-794642 util-8620 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-datastore.sock"
Jul 07 20:44:01-794893 util-8620 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 20:44:01-795138 util-8620 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 20:44:01-795403 util-8620 DEBUG Config value HOSTNAME="localhost"
Jul 07 20:44:01-795651 util-8620 DEBUG Config value BINARY="gnunet-service-datastore"
Jul 07 20:44:01-795901 util-8620 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 20:44:01-796148 util-8620 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 20:44:01-796398 util-8620 DEBUG Config value QUOTA="5 GB"
Jul 07 20:44:01-796652 util-8620 DEBUG Config value BLOOMFILTER="$GNUNET_DATA_HOME/datastore/bloomfilter"
Jul 07 20:44:01-796916 util-8620 DEBUG Config value DATABASE="sqlite"
Jul 07 20:44:01-797215 util-8620 DEBUG Config section `datastore-sqlite'
Jul 07 20:44:01-797447 util-8620 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/datastore/sqlite.db"
Jul 07 20:44:01-797793 util-8620 DEBUG Config section `datastore-postgres'
Jul 07 20:44:01-798006 util-8620 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 20:44:01-798359 util-8620 DEBUG Config section `datastore-mysql'
Jul 07 20:44:01-798568 util-8620 DEBUG Config value DATABASE="gnunet"
Jul 07 20:44:01-798912 util-8620 DEBUG Config value CONFIG="~/.my.cnf"
Jul 07 20:44:01-799234 util-8620 DEBUG Config section `datastore-heap'
Jul 07 20:44:01-799443 util-8620 DEBUG Config value HASHMAPSIZE="1024"
Jul 07 20:44:01-799774 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-802789 util-8620 DEBUG Asked to parse config file `/home/gnunet/.config/gnunet.conf'
Jul 07 20:44:01-802996 util-8620 DEBUG Config file name expanded to `/home/gnunet/.config/gnunet.conf'
Jul 07 20:44:01-803266 util-8620 DEBUG Deserializing contents of file `/home/gnunet/.config/gnunet.conf'
Jul 07 20:44:01-803451 util-8620 DEBUG Deserializing config file
Jul 07 20:44:01-803661 util-8620 DEBUG Config section `arm'
Jul 07 20:44:01-803899 util-8620 DEBUG Config value DEFAULTSERVICES="topology hostlist dht nse fs revocation"
Jul 07 20:44:01-804210 util-8620 DEBUG Config section `transport'
Jul 07 20:44:01-804431 util-8620 DEBUG Config value PLUGINS="tcp udp http_server http_client https_server https_client"
Jul 07 20:44:01-804777 util-8620 DEBUG Config section `cadet'
Jul 07 20:44:01-804986 util-8620 DEBUG Config value PREFIX="valgrind"
Jul 07 20:44:01-805344 util-8620 DEBUG Config value OPTIONS="-L DEBUG -l /home/gnunet/cadet.log"
Jul 07 20:44:01-805668 util-8620 DEBUG Config value AUTOSTART="NO"
Jul 07 20:44:01-805967 util-8620 DEBUG Config section `nat'
Jul 07 20:44:01-806176 util-8620 DEBUG Config value DISABLEV6="YES"
Jul 07 20:44:01-806438 util-8620 DEBUG Config section `hostlist'
Jul 07 20:44:01-806663 util-8620 DEBUG Config value HTTPPORT="8080"
Jul 07 20:44:01-807048 util-8620 DEBUG Config value OPTIONS="-p"
Jul 07 20:44:01-807295 util-8620 DEBUG Config value SERVERS=""
Jul 07 20:44:01-807510 util-8620 DEBUG Finished deserializing config
Jul 07 20:44:01-830018 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `cadet'
Jul 07 20:44:01-831856 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `cadet'
Jul 07 20:44:01-834109 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock', $-expanding
Jul 07 20:44:01-839535 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock
Jul 07 20:44:01-842346 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-cadet.sock' with default (null)
Jul 07 20:44:01-843068 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:01-843843 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:01-845986 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:01-846182 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:01-847649 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:01-849297 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:01-849826 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:01-850028 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:01-850213 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:01-850554 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:01-850874 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:01-851055 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:01-852129 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:01-854846 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:01-861300 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:01-861862 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:01-862177 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:01-865641 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:01-867008 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock'
Jul 07 20:44:01-868179 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock', *nix-expanding
Jul 07 20:44:01-869789 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock'
Jul 07 20:44:01-880875 util-8620 DEBUG Asked to retrieve string `ACCEPT_FROM' in section `cadet'
Jul 07 20:44:01-893207 util-8620 DEBUG Asked to retrieve string `ACCEPT_FROM6' in section `cadet'
Jul 07 20:44:01-904882 util-8620 DEBUG Asked to retrieve filename `USERNAME' in section `cadet'
Jul 07 20:44:01-905094 util-8620 DEBUG Asked to retrieve string `USERNAME' in section `cadet'
Jul 07 20:44:01-906309 util-8620 DEBUG Failed to retrieve filename
Jul 07 20:44:01-907865 util-8620 DEBUG Service `cadet' runs with configuration from `/home/gnunet/.config/gnunet.conf'
Jul 07 20:44:01-920170 util-scheduler-8620 DEBUG Registering signal handlers
Jul 07 20:44:01-939103 util-scheduler-8620 DEBUG Adding continuation task: 1 / 0xbed57a60
Jul 07 20:44:01-947319 util-scheduler-8620 DEBUG Adding task: 2 / (nil)
Jul 07 20:44:01-961861 util-scheduler-8620 DEBUG Checking readiness of task: 2 / (nil)
Jul 07 20:44:01-965927 util-scheduler-8620 DEBUG Running task: 2 / (nil)
Jul 07 20:44:01-967769 util-8620 DEBUG Not installing a handler because $GNUNET_OS_CONTROL_PIPE is empty
Jul 07 20:44:01-977010 util-scheduler-8620 DEBUG Running task: 1 / 0xbed57a60
Jul 07 20:44:01-992946 util-8620 DEBUG Speed up disabled
Jul 07 20:44:01-996015 util-8620 DEBUG Asked to retrieve string `HOSTNAME' in section `resolver'
Jul 07 20:44:02-015789 util-scheduler-8620 DEBUG Adding task: 3 / 0x45515e0
Jul 07 20:44:02-025407 util-scheduler-8620 DEBUG Adding task: 4 / 0xbed57a60
Jul 07 20:44:02-033290 util-8620 INFO Service `cadet' runs at /tmp/gnunet-system-runtime//gnunet-service-cadet.sock
Jul 07 20:44:02-036085 cadet-8620 DEBUG starting to run
Jul 07 20:44:02-040788 util-scheduler-8620 DEBUG Adding task: 5 / (nil)
Jul 07 20:44:02-041787 cadet-8620 INFO reading key
Jul 07 20:44:02-042759 util-8620 DEBUG Asked to retrieve filename `PRIVATE_KEY' in section `PEER'
Jul 07 20:44:02-042961 util-8620 DEBUG Asked to retrieve string `PRIVATE_KEY' in section `PEER'
Jul 07 20:44:02-043388 util-8620 DEBUG Retrieved filename `$GNUNET_DATA_HOME/private_key.ecc', $-expanding
Jul 07 20:44:02-043604 util-8620 DEBUG Asked to $-expand $GNUNET_DATA_HOME/private_key.ecc
Jul 07 20:44:02-043801 util-8620 DEBUG Split into `GNUNET_DATA_HOME' and `private_key.ecc' with default (null)
Jul 07 20:44:02-043993 util-8620 DEBUG Asked to retrieve string `GNUNET_DATA_HOME' in section `PATHS'
Jul 07 20:44:02-044243 util-8620 DEBUG Asked to $-expand ${XDG_DATA_HOME:-$GNUNET_HOME/.local/share}/gnunet/
Jul 07 20:44:02-044454 util-8620 DEBUG Split into `XDG_DATA_HOME' and `/gnunet/' with default $GNUNET_HOME/.local/share
Jul 07 20:44:02-044640 util-8620 DEBUG Asked to retrieve string `XDG_DATA_HOME' in section `PATHS'
Jul 07 20:44:02-044846 util-8620 DEBUG Filename for `XDG_DATA_HOME' is not in PATHS config section
Jul 07 20:44:02-045030 util-8620 DEBUG `XDG_DATA_HOME' is not an environment variable
Jul 07 20:44:02-045232 util-8620 DEBUG Asked to $-expand $GNUNET_HOME/.local/share
Jul 07 20:44:02-045415 util-8620 DEBUG Split into `GNUNET_HOME' and `.local/share' with default (null)
Jul 07 20:44:02-045599 util-8620 DEBUG Asked to retrieve string `GNUNET_HOME' in section `PATHS'
Jul 07 20:44:02-045850 util-8620 DEBUG Asked to $-expand ${GNUNET_TEST_HOME:-${HOME:-${USERPROFILE}}}
Jul 07 20:44:02-046051 util-8620 DEBUG Split into `GNUNET_TEST_HOME' and `' with default ${HOME:-${USERPROFILE}}
Jul 07 20:44:02-046238 util-8620 DEBUG Asked to retrieve string `GNUNET_TEST_HOME' in section `PATHS'
Jul 07 20:44:02-046458 util-8620 DEBUG Filename for `GNUNET_TEST_HOME' is not in PATHS config section
Jul 07 20:44:02-046649 util-8620 DEBUG `GNUNET_TEST_HOME' is not an environment variable
Jul 07 20:44:02-046827 util-8620 DEBUG Asked to $-expand ${HOME:-${USERPROFILE}}
Jul 07 20:44:02-047020 util-8620 DEBUG Split into `HOME' and `' with default ${USERPROFILE}
Jul 07 20:44:02-047203 util-8620 DEBUG Asked to retrieve string `HOME' in section `PATHS'
Jul 07 20:44:02-047405 util-8620 DEBUG Filename for `HOME' is not in PATHS config section
Jul 07 20:44:02-047848 util-8620 DEBUG Prefix is `/home/gnunet'
Jul 07 20:44:02-048069 util-8620 DEBUG Expanded to `/home/gnunet'
Jul 07 20:44:02-048259 util-8620 DEBUG Prefix is `/home/gnunet'
Jul 07 20:44:02-048467 util-8620 DEBUG Expanded to `/home/gnunet'
Jul 07 20:44:02-048663 util-8620 DEBUG Prefix is `/home/gnunet'
Jul 07 20:44:02-048873 util-8620 DEBUG Expanded to `/home/gnunet/.local/share'
Jul 07 20:44:02-049063 util-8620 DEBUG Prefix is `/home/gnunet/.local/share'
Jul 07 20:44:02-049285 util-8620 DEBUG Expanded to `/home/gnunet/.local/share/gnunet/'
Jul 07 20:44:02-049480 util-8620 DEBUG Prefix is `/home/gnunet/.local/share/gnunet/'
Jul 07 20:44:02-049689 util-8620 DEBUG Expanded to `/home/gnunet/.local/share/gnunet//private_key.ecc'
Jul 07 20:44:02-050082 util-8620 DEBUG Expanded to filename `/home/gnunet/.local/share/gnunet//private_key.ecc', *nix-expanding
Jul 07 20:44:02-050496 util-8620 DEBUG Filename result is `/home/gnunet/.local/share/gnunet//private_key.ecc'
Jul 07 20:44:02-914845 cadet-8620 INFO STARTING SERVICE (CADET) for peer [GN10]
Jul 07 20:44:02-916232 cadet-loc-8620 DEBUG init
Jul 07 20:44:02-919325 util-scheduler-8620 DEBUG Canceling task: 3 / 0x45515e0
Jul 07 20:44:02-922510 cadet-hll-8620 DEBUG init
Jul 07 20:44:02-924698 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-924921 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-925228 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 20:44:02-925434 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 20:44:02-925631 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 20:44:02-925821 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-926127 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-926343 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-926529 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-926736 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-926924 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-927102 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-927297 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-927478 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-927680 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-927858 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-928030 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-928330 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-928525 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-928736 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-928922 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-929122 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-929360 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-929572 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-929790 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 20:44:02-930005 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-931863 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-932077 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-932335 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 20:44:02-932533 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 20:44:02-932725 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 20:44:02-932914 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-933148 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-933372 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-933557 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-933766 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-933947 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-934121 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-934311 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-934492 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-934726 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-934907 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-935082 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-935257 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-935446 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-935649 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-935843 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-936049 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-936245 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-936452 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-936661 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 20:44:02-936869 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-944832 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' succeeded! (0x465d478)
Jul 07 20:44:02-946694 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'!
Jul 07 20:44:02-949636 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-949839 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-950110 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 20:44:02-950310 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 20:44:02-950504 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 20:44:02-950696 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-950932 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-951133 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-951317 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-951522 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-951704 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-951880 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-952070 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-952252 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-952455 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-952634 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-952808 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-952981 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-953169 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-953394 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-953580 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-953777 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-953974 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-954191 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-954410 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 20:44:02-954622 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-954868 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-955053 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 20:44:02-955303 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 20:44:02-955498 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 20:44:02-955716 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 20:44:02-955906 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-956139 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-956338 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-956523 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-956725 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-956904 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-957079 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-957292 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-957476 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-957679 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-957857 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-958030 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-958200 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-958382 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-958578 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-958762 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-958959 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-959154 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-959362 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-959576 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 20:44:02-959787 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 20:44:02-960397 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' succeeded! (0x465ee60)
Jul 07 20:44:02-960719 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'!
Jul 07 20:44:02-967224 util-8620 DEBUG Scheduling transmission (0x465ee60).
Jul 07 20:44:02-970559 util-scheduler-8620 DEBUG Adding task: 6 / 0x465ee60
Jul 07 20:44:02-972935 cadet-con-8620 DEBUG init
Jul 07 20:44:02-980576 cadet-p2p-8620 DEBUG init
Jul 07 20:44:02-986206 core-api-8620 DEBUG Connecting to CORE service
Jul 07 20:44:02-987646 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `core'
Jul 07 20:44:02-987848 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `core'
Jul 07 20:44:02-988134 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-core.sock', $-expanding
Jul 07 20:44:02-988333 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-core.sock
Jul 07 20:44:02-988526 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-core.sock' with default (null)
Jul 07 20:44:02-988713 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-988946 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-989148 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-989354 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-989557 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-989738 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-989910 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-990099 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-990279 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-990480 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-990658 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-990830 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-991027 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-991224 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-991431 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-991614 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-991814 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-992011 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-992218 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 20:44:02-992422 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-core.sock', *nix-expanding
Jul 07 20:44:02-992630 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 20:44:02-992876 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `core'
Jul 07 20:44:02-993057 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `core'
Jul 07 20:44:02-993325 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-core.sock', $-expanding
Jul 07 20:44:02-993517 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-core.sock
Jul 07 20:44:02-993717 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-core.sock' with default (null)
Jul 07 20:44:02-993903 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:02-994134 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:02-994330 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:02-994513 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:02-994713 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:02-994890 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:02-995061 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:02-995247 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:02-995427 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:02-995628 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:02-995806 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:02-995978 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:02-996146 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:02-996327 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-996519 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:02-996704 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:02-996900 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-997095 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:02-997323 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 20:44:02-997530 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-core.sock', *nix-expanding
Jul 07 20:44:02-997734 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 20:44:02-998198 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' succeeded! (0x46620a0)
Jul 07 20:44:02-998396 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-core.sock'!
Jul 07 20:44:03-000420 core-api-8620 INFO (Re)connecting to CORE service, monitoring messages of type 0
Jul 07 20:44:03-004445 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:03-004793 util-scheduler-8620 DEBUG Adding task: 7 / 0x46620a0
Jul 07 20:44:03-010171 transport-api-8620 DEBUG Connecting to transport service.
Jul 07 20:44:03-010833 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `transport'
Jul 07 20:44:03-011028 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `transport'
Jul 07 20:44:03-011324 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock', $-expanding
Jul 07 20:44:03-011525 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-transport.sock
Jul 07 20:44:03-011744 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-transport.sock' with default (null)
Jul 07 20:44:03-011938 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:03-012172 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:03-012376 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:03-012560 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:03-012765 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:03-012946 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:03-013122 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:03-013344 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:03-013527 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:03-013731 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:03-013911 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:03-014085 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:03-014256 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:03-014442 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-014649 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:03-014833 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-015032 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-015229 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-015438 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 20:44:03-015655 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-transport.sock', *nix-expanding
Jul 07 20:44:03-015866 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 20:44:03-016143 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `transport'
Jul 07 20:44:03-016327 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `transport'
Jul 07 20:44:03-016601 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock', $-expanding
Jul 07 20:44:03-016859 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-transport.sock
Jul 07 20:44:03-017054 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-transport.sock' with default (null)
Jul 07 20:44:03-017276 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:03-017513 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:03-017714 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:03-017901 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:03-018106 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:03-018300 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:03-018477 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:03-018667 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:03-018854 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:03-019065 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:03-019251 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:03-019429 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:03-019600 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:03-019785 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-019984 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:03-020170 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-020373 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-020575 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-020790 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 20:44:03-021041 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-transport.sock', *nix-expanding
Jul 07 20:44:03-021284 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 20:44:03-021684 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' succeeded! (0x4663d68)
Jul 07 20:44:03-021896 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'!
Jul 07 20:44:03-024962 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:44:03-029711 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:03-030918 util-scheduler-8620 DEBUG Adding task: 8 / 0x46624e8
Jul 07 20:44:03-033015 cadet-dht-8620 DEBUG init
Jul 07 20:44:03-040941 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `dht'
Jul 07 20:44:03-041212 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `dht'
Jul 07 20:44:03-041466 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock', $-expanding
Jul 07 20:44:03-041667 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-dht.sock
Jul 07 20:44:03-041863 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-dht.sock' with default (null)
Jul 07 20:44:03-042053 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:03-042288 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:03-042492 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:03-042677 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:03-042881 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:03-043063 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:03-043239 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:03-043429 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:03-043611 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:03-043815 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:03-043996 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:03-044170 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:03-044342 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:03-044529 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-044734 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:03-044918 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-045118 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-045336 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-045545 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 20:44:03-045751 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-dht.sock', *nix-expanding
Jul 07 20:44:03-045970 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 20:44:03-046198 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `dht'
Jul 07 20:44:03-046391 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `dht'
Jul 07 20:44:03-046623 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock', $-expanding
Jul 07 20:44:03-046817 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-dht.sock
Jul 07 20:44:03-047006 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-dht.sock' with default (null)
Jul 07 20:44:03-047194 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:03-047426 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:03-047624 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:03-047808 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:03-048035 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:03-048216 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:03-048391 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:03-048580 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:03-048762 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:03-048965 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:03-049145 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:03-049339 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:03-049510 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:03-049693 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-049887 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:03-050070 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:03-050268 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-050466 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:03-050676 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 20:44:03-050884 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-dht.sock', *nix-expanding
Jul 07 20:44:03-051092 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 20:44:03-051524 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' succeeded! (0x4665be0)
Jul 07 20:44:03-051722 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'!
Jul 07 20:44:03-053776 util-scheduler-8620 DEBUG Adding task: 9 / (nil)
Jul 07 20:44:03-055358 cadet-tun-8620 DEBUG init
Jul 07 20:44:03-057427 util-scheduler-8620 DEBUG Adding task: 10 / (nil)
Jul 07 20:44:03-058773 cadet-8620 DEBUG Cadet service running
Jul 07 20:44:03-064865 util-scheduler-8620 DEBUG Checking readiness of task: 7 / 0x46620a0
Jul 07 20:44:03-066489 util-scheduler-8620 DEBUG Checking readiness of task: 6 / 0x465ee60
Jul 07 20:44:03-067468 util-scheduler-8620 DEBUG Running task: 6 / 0x465ee60
Jul 07 20:44:03-068873 util-8620 DEBUG transmit_ready running (0x465ee60).
Jul 07 20:44:03-072434 util-8620 DEBUG process_notify is running
Jul 07 20:44:03-074784 util-8620 DEBUG client_notify is running
Jul 07 20:44:03-078931 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:03-082334 util-scheduler-8620 DEBUG Adding task: 11 / 0x465ee60
Jul 07 20:44:03-085343 util-8620 DEBUG Transmitting message of type 334 and size 8 to peerinfo service.
Jul 07 20:44:03-089457 util-8620 DEBUG Connection transmitted 8/8 bytes to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)
Jul 07 20:44:03-090215 util-scheduler-8620 DEBUG Running task: 7 / 0x46620a0
Jul 07 20:44:03-090585 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:03-090883 util-8620 DEBUG process_notify is running
Jul 07 20:44:03-091227 util-8620 DEBUG client_notify is running
Jul 07 20:44:03-093401 core-api-8620 DEBUG Transmitting control message with 24 bytes of type 64 to core.
Jul 07 20:44:03-096135 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:03-096425 util-scheduler-8620 DEBUG Adding task: 12 / 0x46620a0
Jul 07 20:44:03-098442 core-api-8620 DEBUG Core connection down, not processing queue
Jul 07 20:44:03-099219 util-8620 DEBUG Transmitting message of type 64 and size 24 to core service.
Jul 07 20:44:03-102090 util-8620 DEBUG Connection transmitted 24/24 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:03-102412 util-scheduler-8620 DEBUG Running task: 10 / (nil)
Jul 07 20:44:05-189660 util-scheduler-8620 DEBUG Adding task: 13 / (nil)
Jul 07 20:44:05-190294 util-scheduler-8620 DEBUG Running task: 9 / (nil)
Jul 07 20:44:05-191469 cadet-dht-8620 DEBUG Announce ID
Jul 07 20:44:05-192473 cadet-hll-8620 DEBUG  mine is (nil)
Jul 07 20:44:05-193314 util-scheduler-8620 DEBUG Adding task: 14 / (nil)
Jul 07 20:44:05-194281 cadet-dht-8620 DEBUG   no hello, waiting!
Jul 07 20:44:05-194701 util-scheduler-8620 DEBUG Running task: 8 / 0x46624e8
Jul 07 20:44:05-197082 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:44:05-198218 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:44:05-198443 util-scheduler-8620 DEBUG Adding task: 15 / 0x4663d68
Jul 07 20:44:05-199892 util-scheduler-8620 DEBUG Checking readiness of task: 15 / 0x4663d68
Jul 07 20:44:05-200118 util-scheduler-8620 DEBUG Checking readiness of task: 12 / 0x46620a0
Jul 07 20:44:05-200701 util-scheduler-8620 DEBUG Checking readiness of task: 11 / 0x465ee60
Jul 07 20:44:05-201319 util-scheduler-8620 DEBUG Running task: 11 / 0x465ee60
Jul 07 20:44:05-205925 util-8620 DEBUG receive_ready read 2506/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:44:05-209967 util-scheduler-8620 DEBUG Adding task: 16 / 0x465f008
Jul 07 20:44:05-210862 util-scheduler-8620 DEBUG Running task: 12 / 0x46620a0
Jul 07 20:44:05-211406 util-8620 DEBUG receive_ready read 240/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:05-211659 util-scheduler-8620 DEBUG Adding task: 17 / 0x4662248
Jul 07 20:44:05-211876 util-scheduler-8620 DEBUG Running task: 15 / 0x4663d68
Jul 07 20:44:05-212067 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:44:05-212265 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-212447 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-215562 transport-api-8620 DEBUG Transmitting `START' request.
Jul 07 20:44:05-217721 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-217953 util-scheduler-8620 DEBUG Adding task: 18 / 0x4663d68
Jul 07 20:44:05-219405 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:44:05-222315 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:44:05-222788 util-8620 DEBUG Transmitting message of type 360 and size 40 to transport service.
Jul 07 20:44:05-223209 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:44:05-223477 util-scheduler-8620 DEBUG Checking readiness of task: 18 / 0x4663d68
Jul 07 20:44:05-223674 util-scheduler-8620 DEBUG Running task: 18 / 0x4663d68
Jul 07 20:44:05-224082 util-8620 DEBUG receive_ready read 758/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:44:05-224349 util-scheduler-8620 DEBUG Adding task: 19 / 0x4663f10
Jul 07 20:44:05-224566 util-scheduler-8620 DEBUG Running task: 17 / 0x4662248
Jul 07 20:44:05-226675 util-8620 DEBUG Received message of type 65 and size 40 from core service.
Jul 07 20:44:05-232684 core-api-8620 DEBUG Processing message of type 65 and size 40 from core service
Jul 07 20:44:05-234802 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-237127 core-api-8620 DEBUG Connected to core service of peer `GN10'.
Jul 07 20:44:05-238491 cadet-p2p-8620 DEBUG Core init
Jul 07 20:44:05-244805 util-scheduler-8620 DEBUG Adding task: 20 / 0x45515e0
Jul 07 20:44:05-253309 cadet-p2p-8620 INFO CONNECTED GN10 (self)
Jul 07 20:44:05-258045 cadet-p2p-8620 DEBUG adding path [1] to peer GN10
Jul 07 20:44:05-259465 cadet-p2p-8620 DEBUG  final length: 1
Jul 07 20:44:05-261646 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-263186 util-scheduler-8620 DEBUG Adding task: 21 / 0x4662248
Jul 07 20:44:05-263884 util-scheduler-8620 DEBUG Checking readiness of task: 20 / 0x45515e0
Jul 07 20:44:05-264093 util-scheduler-8620 DEBUG Running task: 20 / 0x45515e0
Jul 07 20:44:05-268723 util-8620 DEBUG Accepting connection on `/tmp/gnunet-sydyÕ¾€@
©ßôH'
Jul 07 20:44:05-276363 util-8620 INFO Accepting connection from `<unbound UNIX client>': 0x4d5c418
Jul 07 20:44:05-277870 util-8620 DEBUG Server accepted incoming connection.
Jul 07 20:44:05-282567 cadet-loc-8620 DEBUG client connected: 0x4d5c578
Jul 07 20:44:05-285318 util-scheduler-8620 DEBUG Adding task: 22 / 0x4d5c418
Jul 07 20:44:05-286811 util-scheduler-8620 DEBUG Adding task: 23 / 0x45515e0
Jul 07 20:44:05-287274 util-scheduler-8620 DEBUG Running task: 21 / 0x4662248
Jul 07 20:44:05-287638 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:44:05-288018 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:44:05-289534 core-api-8620 DEBUG Received notification about connection from `KNAS'.
Jul 07 20:44:05-293086 cadet-p2p-8620 INFO CONNECTED GN10 <= KNAS
Jul 07 20:44:05-302189 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `statistics'
Jul 07 20:44:05-302406 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `statistics'
Jul 07 20:44:05-302646 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock', $-expanding
Jul 07 20:44:05-302849 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock
Jul 07 20:44:05-303053 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-statistics.sock' with default (null)
Jul 07 20:44:05-303242 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:05-303484 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:05-303699 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:05-303899 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:05-304114 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:05-304306 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:05-304489 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:05-304693 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:05-304882 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:05-305093 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:05-305308 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:05-305489 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:05-305665 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:05-305858 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:05-306073 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:05-306264 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:05-306467 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:05-306670 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:05-306883 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 20:44:05-307096 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock', *nix-expanding
Jul 07 20:44:05-307329 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 20:44:05-307547 util-8620 DEBUG Asked to retrieve filename `UNIXPATH' in section `statistics'
Jul 07 20:44:05-307731 util-8620 DEBUG Asked to retrieve string `UNIXPATH' in section `statistics'
Jul 07 20:44:05-307950 util-8620 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock', $-expanding
Jul 07 20:44:05-308148 util-8620 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock
Jul 07 20:44:05-308338 util-8620 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-statistics.sock' with default (null)
Jul 07 20:44:05-308524 util-8620 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 20:44:05-308769 util-8620 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 20:44:05-308967 util-8620 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 20:44:05-309149 util-8620 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 20:44:05-309377 util-8620 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 20:44:05-309556 util-8620 DEBUG `TMPDIR' is not an environment variable
Jul 07 20:44:05-309729 util-8620 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 20:44:05-309919 util-8620 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 20:44:05-310129 util-8620 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 20:44:05-310332 util-8620 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 20:44:05-310509 util-8620 DEBUG `TMP' is not an environment variable
Jul 07 20:44:05-310682 util-8620 DEBUG Asked to $-expand /tmp
Jul 07 20:44:05-310851 util-8620 DEBUG Doesn't start with $ - not expanding
Jul 07 20:44:05-311042 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:05-311236 util-8620 DEBUG Expanded to `/tmp'
Jul 07 20:44:05-311418 util-8620 DEBUG Prefix is `/tmp'
Jul 07 20:44:05-311612 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 20:44:05-311805 util-8620 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 20:44:05-312013 util-8620 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 20:44:05-312220 util-8620 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock', *nix-expanding
Jul 07 20:44:05-312429 util-8620 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 20:44:05-312864 util-8620 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' succeeded! (0x4d5e5d8)
Jul 07 20:44:05-313064 util-8620 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'!
Jul 07 20:44:05-316401 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-316631 util-scheduler-8620 DEBUG Adding task: 24 / 0x4d5e5d8
Jul 07 20:44:05-317582 cadet-p2p-8620 DEBUG adding path [2] to peer KNAS
Jul 07 20:44:05-318484 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-318756 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-319172 util-scheduler-8620 DEBUG Adding task: 25 / 0x4662248
Jul 07 20:44:05-319551 util-scheduler-8620 DEBUG Checking readiness of task: 24 / 0x4d5e5d8
Jul 07 20:44:05-319756 util-scheduler-8620 DEBUG Checking readiness of task: 23 / 0x45515e0
Jul 07 20:44:05-319950 util-scheduler-8620 DEBUG Checking readiness of task: 22 / 0x4d5c418
Jul 07 20:44:05-320145 util-scheduler-8620 DEBUG Running task: 23 / 0x45515e0
Jul 07 20:44:05-320540 util-8620 DEBUG Accepting connection on `/tmp/gnunet-sy320145'
Jul 07 20:44:05-320932 util-8620 INFO Accepting connection from `<unbound UNIX client>': 0x4d5ee10
Jul 07 20:44:05-321326 util-8620 DEBUG Server accepted incoming connection.
Jul 07 20:44:05-322094 cadet-loc-8620 DEBUG client connected: 0x4d5ef70
Jul 07 20:44:05-322545 util-scheduler-8620 DEBUG Adding task: 26 / 0x4d5ee10
Jul 07 20:44:05-322763 util-scheduler-8620 DEBUG Adding task: 27 / 0x45515e0
Jul 07 20:44:05-322981 util-scheduler-8620 DEBUG Running task: 22 / 0x4d5c418
Jul 07 20:44:05-323390 util-8620 DEBUG receive_ready read 152/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:44:05-327584 util-8620 DEBUG Server receives 152 bytes from `<unbound UNIX client>'.
Jul 07 20:44:05-330347 util-8620 DEBUG Server-mst receives 152 bytes with 0 bytes already in private buffer
Jul 07 20:44:05-331796 util-8620 DEBUG Server-mst has 152 bytes left in inbound buffer
Jul 07 20:44:05-334145 util-8620 DEBUG Tokenizer gives server message of type 272 from client
Jul 07 20:44:05-336340 util-8620 DEBUG Server schedules transmission of 8-byte message of type 272 to client.
Jul 07 20:44:05-338718 util-scheduler-8620 DEBUG Adding task: 28 / 0x4d5c578
Jul 07 20:44:05-340255 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-341224 cadet-loc-8620 DEBUG new client connected 0x4d5c578
Jul 07 20:44:05-343332 cadet-loc-8620 DEBUG   client id 0
Jul 07 20:44:05-344298 cadet-loc-8620 DEBUG   client has 1 ports
Jul 07 20:44:05-345871 cadet-loc-8620 DEBUG     port: 19
Jul 07 20:44:05-354906 util-scheduler-8620 DEBUG Canceling task: 28 / 0x4d5c578
Jul 07 20:44:05-356185 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-357378 cadet-loc-8620 DEBUG new client processed
Jul 07 20:44:05-359183 util-8620 DEBUG Server-mst has 144 bytes left in inbound buffer
Jul 07 20:44:05-361577 util-8620 DEBUG Server-mst leaves 144 bytes in private buffer
Jul 07 20:44:05-363638 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:44:05-364438 util-8620 DEBUG Server-mst receives 0 bytes with 144 bytes already in private buffer
Jul 07 20:44:05-366444 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:44:05-366820 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:44:05-367057 util-scheduler-8620 DEBUG Adding task: 29 / 0x4d5c578
Jul 07 20:44:05-368124 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-369048 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:44:05-370276 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:05-372057 cadet-chn-8620 DEBUG   towards P00P:19
Jul 07 20:44:05-377237 cadet-p2p-8620 DEBUG peer_connect towards P00P
Jul 07 20:44:05-379809 cadet-p2p-8620 DEBUG   Starting DHT GET for peer P00P
Jul 07 20:44:05-381230 cadet-dht-8620 DEBUG   Starting DHT GET for peer P00P
Jul 07 20:44:05-386572 dht-api-8620 DEBUG Sending query for P00PHXNA to DHT 0x46642c0
Jul 07 20:44:05-395829 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:44:05-396108 util-scheduler-8620 DEBUG Adding task: 30 / 0x4665be0
Jul 07 20:44:05-399652 cadet-tun-8620 DEBUG Tunnel P00P cstate CADET_TUNNEL_NEW => CADET_TUNNEL_SEARCHING
Jul 07 20:44:05-407677 cadet-tun-8620 DEBUG Adding channel 0x4d60800 to tunnel 0x4d60080
Jul 07 20:44:05-409093 cadet-tun-8620 DEBUG  adding 0x4d609e0 to (nil)
Jul 07 20:44:05-414730 cadet-chn-8620 DEBUG CREATED CHANNEL P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:44:05-419938 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:44:05-423611 cadet-tun-8620 DEBUG GMT Send on Tunnel P00P
Jul 07 20:44:05-425474 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:44:05-426953 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-428084 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-429228 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-430377 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-431366 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-432859 cadet-tun-8620 DEBUG TTT  - P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:44:05-433941 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-435070 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-437313 cadet-tun-8620 DEBUG queue data on Tunnel P00P
Jul 07 20:44:05-437887 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:44:05-438228 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-438571 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-438911 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-440371 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-441245 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-441628 cadet-tun-8620 DEBUG TTT  - P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:44:05-441957 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-442282 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-445457 util-scheduler-8620 DEBUG Canceling task: 29 / 0x4d5c578
Jul 07 20:44:05-445775 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-446671 util-8620 DEBUG Server-mst leaves 96 bytes in private buffer
Jul 07 20:44:05-447559 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:44:05-447787 util-8620 DEBUG Server-mst receives 0 bytes with 96 bytes already in private buffer
Jul 07 20:44:05-447988 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:44:05-448187 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:44:05-448427 util-scheduler-8620 DEBUG Adding task: 31 / 0x4d5c578
Jul 07 20:44:05-448805 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-449141 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:44:05-449510 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:05-449940 cadet-chn-8620 DEBUG   towards KNAS:19
Jul 07 20:44:05-450836 cadet-p2p-8620 DEBUG peer_connect towards KNAS
Jul 07 20:44:05-451780 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:44:05-457744 cadet-p2p-8620 DEBUG   path to use:  GN10 KNAS
Jul 07 20:44:05-468526 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:05-470765 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:05-473874 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:05-475296 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:05-476942 cadet-con-8620 DEBUG register neighbors for connection HS92G30M (->KNAS)
Jul 07 20:44:05-478100 cadet-8620 DEBUG PATH:
Jul 07 20:44:05-479469 cadet-8620 DEBUG   GN10
Jul 07 20:44:05-479925 cadet-8620 DEBUG   KNAS
Jul 07 20:44:05-480930 cadet-8620 DEBUG END
Jul 07 20:44:05-482242 cadet-con-8620 DEBUG own pos 0
Jul 07 20:44:05-483500 cadet-con-8620 DEBUG putting connection HS92G30M (->KNAS) to next peer 0x4d5cb40
Jul 07 20:44:05-484701 cadet-con-8620 DEBUG next peer 0x4d5cb40 KNAS
Jul 07 20:44:05-486043 cadet-con-8620 DEBUG putting connection HS92G30M (->KNAS) to prev peer 0x4d5be88
Jul 07 20:44:05-487234 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:44:05-489509 cadet-p2p-8620 DEBUG adding connection HS92G30M (->KNAS)
Jul 07 20:44:05-490668 cadet-p2p-8620 DEBUG to peer KNAS
Jul 07 20:44:05-492316 cadet-p2p-8620 DEBUG peer KNAS ok, has 0 connections.
Jul 07 20:44:05-493847 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:44:05-494787 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-495687 cadet-p2p-8620 DEBUG adding connection HS92G30M (->KNAS)
Jul 07 20:44:05-497717 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:44:05-498083 cadet-p2p-8620 DEBUG peer GN10 ok, has 0 connections.
Jul 07 20:44:05-498428 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:44:05-498768 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-500999 cadet-tun-8620 DEBUG add connection HS92G30M (->KNAS)
Jul 07 20:44:05-502499 cadet-tun-8620 DEBUG  to tunnel KNAS
Jul 07 20:44:05-504084 util-scheduler-8620 DEBUG Adding task: 32 / 0x4d61838
Jul 07 20:44:05-506691 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection HS92G30M (->KNAS)  (100 bytes)
Jul 07 20:44:05-507736 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0 (create)
Jul 07 20:44:05-508415 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:05-508781 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:05-512293 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:44:05-513538 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:05-515319 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:05-516547 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:05-518013 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:05-520886 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 100 bytes
Jul 07 20:44:05-524571 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:44:05-527180 util-scheduler-8620 DEBUG Adding task: 33 / 0x4d5c9e8
Jul 07 20:44:05-528371 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:05-530393 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:05-531429 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:05-532481 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:05-534688 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on HS92G30M (->KNAS)
Jul 07 20:44:05-536092 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:05-537071 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:05-538402 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:05-539928 cadet-tun-8620 DEBUG Tunnel KNAS cstate CADET_TUNNEL_NEW => CADET_TUNNEL_WAITING
Jul 07 20:44:05-541865 cadet-con-8620 DEBUG Connection HS92G30M (->KNAS) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:44:05-544113 cadet-tun-8620 DEBUG Adding channel 0x4d638d8 to tunnel 0x4d61838
Jul 07 20:44:05-544495 cadet-tun-8620 DEBUG  adding 0x4d639c8 to (nil)
Jul 07 20:44:05-544887 cadet-chn-8620 DEBUG CREATED CHANNEL KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:05-545334 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:05-545720 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:05-545929 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:05-546118 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-546302 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-546481 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-546657 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-546827 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-547042 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:05-547215 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-550498 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [1] buf: 11/11 (qn 0/0)
Jul 07 20:44:05-550928 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-551288 cadet-tun-8620 DEBUG queue data on Tunnel KNAS
Jul 07 20:44:05-551495 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:05-551677 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-551860 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-552038 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-552213 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-552381 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-552596 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:05-552768 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-553151 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [1] buf: 11/11 (qn 0/0)
Jul 07 20:44:05-553362 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-553869 util-scheduler-8620 DEBUG Canceling task: 31 / 0x4d5c578
Jul 07 20:44:05-554071 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-554258 util-8620 DEBUG Server-mst leaves 48 bytes in private buffer
Jul 07 20:44:05-554434 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:44:05-554617 util-8620 DEBUG Server-mst receives 0 bytes with 48 bytes already in private buffer
Jul 07 20:44:05-554804 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:44:05-554991 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:44:05-555208 util-scheduler-8620 DEBUG Adding task: 34 / 0x4d5c578
Jul 07 20:44:05-555386 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-555554 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:44:05-555726 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:05-555928 cadet-chn-8620 DEBUG   towards V8XX:19
Jul 07 20:44:05-556188 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:44:05-556492 cadet-p2p-8620 DEBUG   Starting DHT GET for peer V8XX
Jul 07 20:44:05-556855 cadet-dht-8620 DEBUG   Starting DHT GET for peer V8XX
Jul 07 20:44:05-557312 dht-api-8620 DEBUG Sending query for V8XXK9GA to DHT 0x46642c0
Jul 07 20:44:05-557950 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_NEW => CADET_TUNNEL_SEARCHING
Jul 07 20:44:05-558198 cadet-tun-8620 DEBUG Adding channel 0x4d650a8 to tunnel 0x4d64a70
Jul 07 20:44:05-558397 cadet-tun-8620 DEBUG  adding 0x4d65198 to (nil)
Jul 07 20:44:05-558639 cadet-chn-8620 DEBUG CREATED CHANNEL V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:44:05-558902 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:44:05-559119 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:44:05-559318 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:44:05-559499 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-559681 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-559859 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-560057 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-560226 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-560439 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:44:05-560611 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-560777 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-560974 cadet-tun-8620 DEBUG queue data on Tunnel V8XX
Jul 07 20:44:05-561173 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:44:05-561377 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:44:05-561559 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:44:05-561736 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:05-561911 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:05-562078 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:05-562289 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:44:05-562460 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:05-562628 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:05-562833 util-scheduler-8620 DEBUG Canceling task: 34 / 0x4d5c578
Jul 07 20:44:05-563026 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-563471 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:44:05-565432 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:44:05-566080 util-scheduler-8620 DEBUG Adding task: 35 / 0x4d5c418
Jul 07 20:44:05-567353 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:44:05-568436 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-568748 util-scheduler-8620 DEBUG Checking readiness of task: 30 / 0x4665be0
Jul 07 20:44:05-569228 util-scheduler-8620 DEBUG Checking readiness of task: 27 / 0x45515e0
Jul 07 20:44:05-569431 util-scheduler-8620 DEBUG Checking readiness of task: 26 / 0x4d5ee10
Jul 07 20:44:05-569631 util-scheduler-8620 DEBUG Running task: 27 / 0x45515e0
Jul 07 20:44:05-569871 util-8620 DEBUG Accepting connection on `/tmp/gnunet-sy569631'
Jul 07 20:44:05-570175 util-8620 INFO Accepting connection from `<unbound UNIX client>': 0x4d66008
Jul 07 20:44:05-570367 util-8620 DEBUG Server accepted incoming connection.
Jul 07 20:44:05-570580 cadet-loc-8620 DEBUG client connected: 0x4d66168
Jul 07 20:44:05-570806 util-scheduler-8620 DEBUG Adding task: 36 / 0x4d66008
Jul 07 20:44:05-571021 util-scheduler-8620 DEBUG Adding task: 37 / 0x45515e0
Jul 07 20:44:05-571225 util-scheduler-8620 DEBUG Running task: 26 / 0x4d5ee10
Jul 07 20:44:05-571619 util-8620 DEBUG receive_ready read 8/65535 bytes from `<unbound UNIX client>' (0x4d5ee10)!
Jul 07 20:44:05-571954 util-8620 DEBUG Server receives 8 bytes from `<unbound UNIX client>'.
Jul 07 20:44:05-572152 util-8620 DEBUG Server-mst receives 8 bytes with 0 bytes already in private buffer
Jul 07 20:44:05-572341 util-8620 DEBUG Server-mst has 8 bytes left in inbound buffer
Jul 07 20:44:05-572529 util-8620 DEBUG Tokenizer gives server message of type 272 from client
Jul 07 20:44:05-572716 util-8620 DEBUG Server schedules transmission of 8-byte message of type 272 to client.
Jul 07 20:44:05-572934 util-scheduler-8620 DEBUG Adding task: 38 / 0x4d5ef70
Jul 07 20:44:05-573297 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-573627 cadet-loc-8620 DEBUG new client connected 0x4d5ef70
Jul 07 20:44:05-573904 cadet-loc-8620 DEBUG   client id 1
Jul 07 20:44:05-574171 cadet-loc-8620 DEBUG   client has 1 ports
Jul 07 20:44:05-574514 cadet-loc-8620 DEBUG     port: 3
Jul 07 20:44:05-575475 util-scheduler-8620 DEBUG Canceling task: 38 / 0x4d5ef70
Jul 07 20:44:05-575675 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-575941 cadet-loc-8620 DEBUG new client processed
Jul 07 20:44:05-576252 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:44:05-576568 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:44:05-576799 util-scheduler-8620 DEBUG Adding task: 39 / 0x4d5ee10
Jul 07 20:44:05-577165 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:44:05-577462 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-577658 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-577849 util-scheduler-8620 DEBUG Checking readiness of task: 36 / 0x4d66008
Jul 07 20:44:05-578040 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-578233 util-scheduler-8620 DEBUG Running task: 36 / 0x4d66008
Jul 07 20:44:05-578614 util-8620 DEBUG receive_ready read 4/65535 bytes from `<unbound UNIX client>' (0x4d66008)!
Jul 07 20:44:05-578816 util-8620 DEBUG Server receives 4 bytes from `<unbound UNIX client>'.
Jul 07 20:44:05-579003 util-8620 DEBUG Server-mst receives 4 bytes with 0 bytes already in private buffer
Jul 07 20:44:05-579187 util-8620 DEBUG Server-mst has 4 bytes left in inbound buffer
Jul 07 20:44:05-579367 util-8620 DEBUG Tokenizer gives server message of type 272 from client
Jul 07 20:44:05-579563 util-8620 DEBUG Server schedules transmission of 4-byte message of type 272 to client.
Jul 07 20:44:05-579772 util-scheduler-8620 DEBUG Adding task: 40 / 0x4d66168
Jul 07 20:44:05-579947 cadet-loc-8620 DEBUG 
Jul 07 20:44:05-580117 cadet-loc-8620 DEBUG new client connected 0x4d66168
Jul 07 20:44:05-580293 cadet-loc-8620 DEBUG   client id 2
Jul 07 20:44:05-580464 cadet-loc-8620 DEBUG   client has 0 ports
Jul 07 20:44:05-580687 util-scheduler-8620 DEBUG Canceling task: 40 / 0x4d66168
Jul 07 20:44:05-580876 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:05-581048 cadet-loc-8620 DEBUG new client processed
Jul 07 20:44:05-581240 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:44:05-581442 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:44:05-581639 util-scheduler-8620 DEBUG Adding task: 41 / 0x4d66008
Jul 07 20:44:05-581837 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:44:05-582056 util-scheduler-8620 DEBUG Running task: 30 / 0x4665be0
Jul 07 20:44:05-582242 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:44:05-582436 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-582613 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-584962 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:44:05-585232 util-scheduler-8620 DEBUG Adding task: 42 / 0x4665be0
Jul 07 20:44:05-587363 dht-api-8620 DEBUG Forwarded request of 88 bytes to DHT service
Jul 07 20:44:05-588575 dht-api-8620 DEBUG Starting to process replies from DHT
Jul 07 20:44:05-589493 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-589716 util-scheduler-8620 DEBUG Adding task: 43 / 0x4665be0
Jul 07 20:44:05-590155 util-8620 DEBUG Transmitting message of type 143 and size 88 to dht service.
Jul 07 20:44:05-591232 util-8620 DEBUG Connection transmitted 88/88 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:44:05-592645 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4665be0).
Jul 07 20:44:05-593358 util-scheduler-8620 DEBUG Running task: 33 / 0x4d5c9e8
Jul 07 20:44:05-595319 util-scheduler-8620 DEBUG Adding task: 44 / 0x4d5c9e8
Jul 07 20:44:05-599119 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:05-599667 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:05-599889 util-scheduler-8620 DEBUG Adding task: 45 / 0x46620a0
Jul 07 20:44:05-600101 util-scheduler-8620 DEBUG Running task: 32 / 0x4d61838
Jul 07 20:44:05-601884 util-scheduler-8620 DEBUG Running task: 24 / 0x4d5e5d8
Jul 07 20:44:05-602092 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-602286 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-602458 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-609080 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-609358 util-scheduler-8620 DEBUG Adding task: 46 / 0x4d5e5d8
Jul 07 20:44:05-609785 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:44:05-610112 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-610479 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:05-610684 util-scheduler-8620 DEBUG Running task: 25 / 0x4662248
Jul 07 20:44:05-610877 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:44:05-611079 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:44:05-611399 core-api-8620 DEBUG Received notification about connection from `P00P'.
Jul 07 20:44:05-611826 cadet-p2p-8620 INFO CONNECTED GN10 <= P00P
Jul 07 20:44:05-612108 cadet-p2p-8620 DEBUG adding path [2] to peer P00P
Jul 07 20:44:05-612290 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-612464 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-613625 cadet-p2p-8620 DEBUG peer_connect towards P00P
Jul 07 20:44:05-613965 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:44:05-614442 cadet-p2p-8620 DEBUG   path to use:  GN10 P00P
Jul 07 20:44:05-614896 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:05-615112 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:05-615522 cadet-con-8620 DEBUG  get prev hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:05-615898 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:05-616325 cadet-con-8620 DEBUG register neighbors for connection KT5Q8VM8 (->P00P)
Jul 07 20:44:05-616661 cadet-8620 DEBUG PATH:
Jul 07 20:44:05-616866 cadet-8620 DEBUG   GN10
Jul 07 20:44:05-617053 cadet-8620 DEBUG   P00P
Jul 07 20:44:05-617400 cadet-8620 DEBUG END
Jul 07 20:44:05-617747 cadet-con-8620 DEBUG own pos 0
Jul 07 20:44:05-618149 cadet-con-8620 DEBUG putting connection KT5Q8VM8 (->P00P) to next peer 0x4d5ff80
Jul 07 20:44:05-618528 cadet-con-8620 DEBUG next peer 0x4d5ff80 P00P
Jul 07 20:44:05-618932 cadet-con-8620 DEBUG putting connection KT5Q8VM8 (->P00P) to prev peer 0x4d5be88
Jul 07 20:44:05-619315 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:44:05-619562 cadet-p2p-8620 DEBUG adding connection KT5Q8VM8 (->P00P)
Jul 07 20:44:05-619786 cadet-p2p-8620 DEBUG to peer P00P
Jul 07 20:44:05-619998 cadet-p2p-8620 DEBUG peer P00P ok, has 0 connections.
Jul 07 20:44:05-620197 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:44:05-620376 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-620606 cadet-p2p-8620 DEBUG adding connection KT5Q8VM8 (->P00P)
Jul 07 20:44:05-620809 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:44:05-621015 cadet-p2p-8620 DEBUG peer GN10 ok, has 1 connections.
Jul 07 20:44:05-621235 cadet-p2p-8620 DEBUG  now has 2 connections.
Jul 07 20:44:05-621412 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-621825 cadet-tun-8620 DEBUG add connection KT5Q8VM8 (->P00P)
Jul 07 20:44:05-622190 cadet-tun-8620 DEBUG  to tunnel P00P
Jul 07 20:44:05-622425 util-scheduler-8620 DEBUG Adding task: 47 / 0x4d60080
Jul 07 20:44:05-622851 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:05-623198 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:05-623441 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:05-623653 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:05-624115 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:05-624488 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:05-624877 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:05-625241 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:05-625579 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:05-625898 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:05-626299 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:05-626555 util-scheduler-8620 DEBUG Adding task: 48 / 0x4d683b0
Jul 07 20:44:05-626840 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:05-627207 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:05-627544 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:05-627881 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:05-628282 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:05-628621 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:05-628955 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:05-629336 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:05-629558 cadet-tun-8620 DEBUG Tunnel P00P cstate CADET_TUNNEL_SEARCHING => CADET_TUNNEL_WAITING
Jul 07 20:44:05-629956 cadet-con-8620 DEBUG Connection KT5Q8VM8 (->P00P) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:44:05-630375 util-scheduler-8620 DEBUG Adding task: 49 / 0x4662248
Jul 07 20:44:05-630585 util-scheduler-8620 DEBUG Running task: 19 / 0x4663f10
Jul 07 20:44:05-630781 util-8620 DEBUG Received message of type 17 and size 538 from transport service.
Jul 07 20:44:05-633104 util-scheduler-8620 DEBUG Adding task: 50 / 0x4663f10
Jul 07 20:44:05-636260 transport-api-8620 DEBUG Receiving (my own) `HELLO' message, I am `GN10'.
Jul 07 20:44:05-637746 util-scheduler-8620 DEBUG Running task: 16 / 0x465f008
Jul 07 20:44:05-637962 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:44:05-641765 nse-api-8620 DEBUG Received information about peer `4AE6' from peerinfo database
Jul 07 20:44:05-654406 cadet-hll-8620 DEBUG  hello for 4AE6 (64 bytes), expires on Mon Jul 07 22:33:30 2014
Jul 07 20:44:05-656301 cadet-p2p-8620 DEBUG set hello for 4AE6
Jul 07 20:44:05-658007 cadet-p2p-8620 DEBUG  new (64 bytes)
Jul 07 20:44:05-659652 util-scheduler-8620 DEBUG Adding task: 51 / 0x465f008
Jul 07 20:44:05-659990 util-scheduler-8620 DEBUG Checking readiness of task: 46 / 0x4d5e5d8
Jul 07 20:44:05-660202 util-scheduler-8620 DEBUG Checking readiness of task: 45 / 0x46620a0
Jul 07 20:44:05-660399 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-660596 util-scheduler-8620 DEBUG Checking readiness of task: 42 / 0x4665be0
Jul 07 20:44:05-660791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-660982 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-661173 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-661399 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-661598 util-scheduler-8620 DEBUG Running task: 42 / 0x4665be0
Jul 07 20:44:05-661788 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:44:05-662103 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-662287 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-662935 dht-api-8620 DEBUG Forwarded request of 88 bytes to DHT service
Jul 07 20:44:05-663360 util-8620 DEBUG Transmitting message of type 143 and size 88 to dht service.
Jul 07 20:44:05-664554 util-8620 DEBUG Connection transmitted 88/88 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:44:05-664789 util-scheduler-8620 DEBUG Running task: 45 / 0x46620a0
Jul 07 20:44:05-665030 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:05-665376 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-665650 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-666499 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:05-667158 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-667360 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:05-667651 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:05-667866 util-scheduler-8620 DEBUG Running task: 46 / 0x4d5e5d8
Jul 07 20:44:05-668050 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-668263 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-668433 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-668701 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-668918 util-scheduler-8620 DEBUG Adding task: 52 / 0x4d5e5d8
Jul 07 20:44:05-669119 util-8620 DEBUG Transmitting message of type 168 and size 32 to statistics service.
Jul 07 20:44:05-669434 util-8620 DEBUG Connection transmitted 32/32 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-669632 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:05-669830 util-scheduler-8620 DEBUG Running task: 51 / 0x465f008
Jul 07 20:44:05-670020 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:44:05-670373 nse-api-8620 DEBUG Received information about peer `D3TJ' from peerinfo database
Jul 07 20:44:05-670810 cadet-hll-8620 DEBUG  hello for D3TJ (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:44:05-671213 cadet-p2p-8620 DEBUG set hello for D3TJ
Jul 07 20:44:05-671481 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:44:05-671718 util-scheduler-8620 DEBUG Adding task: 53 / 0x465f008
Jul 07 20:44:05-671918 util-scheduler-8620 DEBUG Running task: 50 / 0x4663f10
Jul 07 20:44:05-672109 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:44:05-672326 util-scheduler-8620 DEBUG Adding task: 54 / 0x4663f10
Jul 07 20:44:05-673933 transport-api-8620 DEBUG Receiving `CONNECT' message for `KNAS'.
Jul 07 20:44:05-675691 transport-api-8620 DEBUG Creating entry for neighbour `KNAS'.
Jul 07 20:44:05-678404 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:44:05-682056 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 initialized with 1024 Bps and max carry 5
Jul 07 20:44:05-687124 util-scheduler-8620 DEBUG Adding task: 55 / 0x4d6c380
Jul 07 20:44:05-689635 transport-api-8620 DEBUG Receiving `CONNECT' message for `KNAS' with quota 23365
Jul 07 20:44:05-691697 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 bandwidth changed to 23365 Bps
Jul 07 20:44:05-698835 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 updated, have 1024 Bps, last update was 11 ms ago
Jul 07 20:44:05-701039 util-scheduler-8620 DEBUG Canceling task: 55 / 0x4d6c380
Jul 07 20:44:05-701590 util-scheduler-8620 DEBUG Adding task: 56 / 0x4d6c380
Jul 07 20:44:05-701927 util-scheduler-8620 DEBUG Running task: 49 / 0x4662248
Jul 07 20:44:05-702127 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:44:05-702332 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:44:05-702555 core-api-8620 DEBUG Received notification about connection from `STRN'.
Jul 07 20:44:05-702838 cadet-p2p-8620 INFO CONNECTED GN10 <= STRN
Jul 07 20:44:05-703087 cadet-p2p-8620 DEBUG adding path [2] to peer STRN
Jul 07 20:44:05-703266 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-703440 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-703654 util-scheduler-8620 DEBUG Adding task: 57 / 0x4662248
Jul 07 20:44:05-703855 util-scheduler-8620 DEBUG Running task: 48 / 0x4d683b0
Jul 07 20:44:05-704075 util-scheduler-8620 DEBUG Adding task: 58 / 0x4d683b0
Jul 07 20:44:05-704431 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:05-704642 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:05-704851 util-scheduler-8620 DEBUG Adding task: 59 / 0x46620a0
Jul 07 20:44:05-705052 util-scheduler-8620 DEBUG Running task: 47 / 0x4d60080
Jul 07 20:44:05-705470 util-scheduler-8620 DEBUG Checking readiness of task: 59 / 0x46620a0
Jul 07 20:44:05-705672 util-scheduler-8620 DEBUG Checking readiness of task: 52 / 0x4d5e5d8
Jul 07 20:44:05-705868 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-706061 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-706252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-706475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-706669 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-706865 util-scheduler-8620 DEBUG Running task: 52 / 0x4d5e5d8
Jul 07 20:44:05-707053 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-707246 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-707420 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-707669 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-707878 util-scheduler-8620 DEBUG Adding task: 60 / 0x4d5e5d8
Jul 07 20:44:05-708082 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:44:05-708390 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-708591 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:05-708789 util-scheduler-8620 DEBUG Running task: 59 / 0x46620a0
Jul 07 20:44:05-708972 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:05-709148 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-709340 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-709518 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:05-709714 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-709903 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:05-710186 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:05-710394 util-scheduler-8620 DEBUG Running task: 57 / 0x4662248
Jul 07 20:44:05-710583 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:44:05-710779 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:44:05-710992 core-api-8620 DEBUG Received notification about connection from `TZQE'.
Jul 07 20:44:05-711265 cadet-p2p-8620 INFO CONNECTED GN10 <= TZQE
Jul 07 20:44:05-711538 cadet-p2p-8620 DEBUG adding path [2] to peer TZQE
Jul 07 20:44:05-711717 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-711889 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-712101 util-scheduler-8620 DEBUG Adding task: 61 / 0x4662248
Jul 07 20:44:05-712297 util-scheduler-8620 DEBUG Running task: 54 / 0x4663f10
Jul 07 20:44:05-712486 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:44:05-712710 util-scheduler-8620 DEBUG Adding task: 62 / 0x4663f10
Jul 07 20:44:05-713048 transport-api-8620 DEBUG Receiving `CONNECT' message for `P00P'.
Jul 07 20:44:05-713437 transport-api-8620 DEBUG Creating entry for neighbour `P00P'.
Jul 07 20:44:05-713800 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:44:05-714162 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 initialized with 1024 Bps and max carry 5
Jul 07 20:44:05-714392 util-scheduler-8620 DEBUG Adding task: 63 / 0x4d6e518
Jul 07 20:44:05-714719 transport-api-8620 DEBUG Receiving `CONNECT' message for `P00P' with quota 16559
Jul 07 20:44:05-715077 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 bandwidth changed to 16559 Bps
Jul 07 20:44:05-716100 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 updated, have 1024 Bps, last update was 1277 µs ago
Jul 07 20:44:05-716318 util-scheduler-8620 DEBUG Canceling task: 63 / 0x4d6e518
Jul 07 20:44:05-716533 util-scheduler-8620 DEBUG Adding task: 64 / 0x4d6e518
Jul 07 20:44:05-716730 util-scheduler-8620 DEBUG Running task: 53 / 0x465f008
Jul 07 20:44:05-716920 util-8620 DEBUG Received message of type 332 and size 420 from peerinfo service.
Jul 07 20:44:05-717156 nse-api-8620 DEBUG Received information about peer `DSTJ' from peerinfo database
Jul 07 20:44:05-718132 cadet-hll-8620 DEBUG  hello for DSTJ (380 bytes), expires on end of time
Jul 07 20:44:05-719411 cadet-p2p-8620 DEBUG set hello for DSTJ
Jul 07 20:44:05-719603 cadet-p2p-8620 DEBUG  new (380 bytes)
Jul 07 20:44:05-719949 util-scheduler-8620 DEBUG Adding task: 65 / 0x465f008
Jul 07 20:44:05-720207 util-scheduler-8620 DEBUG Checking readiness of task: 60 / 0x4d5e5d8
Jul 07 20:44:05-720401 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-720591 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-720780 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-720969 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-721169 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-721384 util-scheduler-8620 DEBUG Running task: 60 / 0x4d5e5d8
Jul 07 20:44:05-721568 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-721745 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-721929 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-722165 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-722374 util-scheduler-8620 DEBUG Adding task: 66 / 0x4d5e5d8
Jul 07 20:44:05-722578 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:44:05-722868 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-723066 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:05-723262 util-scheduler-8620 DEBUG Running task: 65 / 0x465f008
Jul 07 20:44:05-723452 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:44:05-723679 nse-api-8620 DEBUG Received information about peer `KNAS' from peerinfo database
Jul 07 20:44:05-724110 cadet-hll-8620 DEBUG  hello for KNAS (64 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-724331 cadet-p2p-8620 DEBUG set hello for KNAS
Jul 07 20:44:05-724506 cadet-p2p-8620 DEBUG  new (64 bytes)
Jul 07 20:44:05-724714 util-scheduler-8620 DEBUG Adding task: 67 / 0x465f008
Jul 07 20:44:05-724911 util-scheduler-8620 DEBUG Running task: 62 / 0x4663f10
Jul 07 20:44:05-725100 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:44:05-725336 util-scheduler-8620 DEBUG Adding task: 68 / 0x4663f10
Jul 07 20:44:05-725547 transport-api-8620 DEBUG Receiving `CONNECT' message for `STRN'.
Jul 07 20:44:05-725754 transport-api-8620 DEBUG Creating entry for neighbour `STRN'.
Jul 07 20:44:05-725943 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:44:05-726133 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 initialized with 1024 Bps and max carry 5
Jul 07 20:44:05-726352 util-scheduler-8620 DEBUG Adding task: 69 / 0x4d6fa48
Jul 07 20:44:05-726572 transport-api-8620 DEBUG Receiving `CONNECT' message for `STRN' with quota 14866
Jul 07 20:44:05-726759 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 14866 Bps
Jul 07 20:44:05-726995 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 1024 Bps, last update was 819 µs ago
Jul 07 20:44:05-727203 util-scheduler-8620 DEBUG Canceling task: 69 / 0x4d6fa48
Jul 07 20:44:05-727412 util-scheduler-8620 DEBUG Adding task: 70 / 0x4d6fa48
Jul 07 20:44:05-727607 util-scheduler-8620 DEBUG Running task: 61 / 0x4662248
Jul 07 20:44:05-727794 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:44:05-728093 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:44:05-728308 core-api-8620 DEBUG Received notification about connection from `V8XX'.
Jul 07 20:44:05-728630 cadet-p2p-8620 INFO CONNECTED GN10 <= V8XX
Jul 07 20:44:05-728886 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:05-729065 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-729257 cadet-p2p-8620 DEBUG   added last
Jul 07 20:44:05-729470 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:44:05-729645 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:44:05-729944 cadet-p2p-8620 DEBUG   path to use:  GN10 V8XX
Jul 07 20:44:05-730369 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:05-730596 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:05-730836 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:05-731047 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:05-731287 cadet-con-8620 DEBUG register neighbors for connection CMHCKRVP (->V8XX)
Jul 07 20:44:05-731456 cadet-8620 DEBUG PATH:
Jul 07 20:44:05-731646 cadet-8620 DEBUG   GN10
Jul 07 20:44:05-731831 cadet-8620 DEBUG   V8XX
Jul 07 20:44:05-731988 cadet-8620 DEBUG END
Jul 07 20:44:05-732248 cadet-con-8620 DEBUG own pos 0
Jul 07 20:44:05-732480 cadet-con-8620 DEBUG putting connection CMHCKRVP (->V8XX) to next peer 0x4d64970
Jul 07 20:44:05-732692 cadet-con-8620 DEBUG next peer 0x4d64970 V8XX
Jul 07 20:44:05-732932 cadet-con-8620 DEBUG putting connection CMHCKRVP (->V8XX) to prev peer 0x4d5be88
Jul 07 20:44:05-733139 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:44:05-733389 cadet-p2p-8620 DEBUG adding connection CMHCKRVP (->V8XX)
Jul 07 20:44:05-733586 cadet-p2p-8620 DEBUG to peer V8XX
Jul 07 20:44:05-733785 cadet-p2p-8620 DEBUG peer V8XX ok, has 0 connections.
Jul 07 20:44:05-733974 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:44:05-734147 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-734365 cadet-p2p-8620 DEBUG adding connection CMHCKRVP (->V8XX)
Jul 07 20:44:05-734560 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:44:05-734757 cadet-p2p-8620 DEBUG peer GN10 ok, has 2 connections.
Jul 07 20:44:05-734942 cadet-p2p-8620 DEBUG  now has 3 connections.
Jul 07 20:44:05-735112 cadet-p2p-8620 DEBUG result 1
Jul 07 20:44:05-735333 cadet-tun-8620 DEBUG add connection CMHCKRVP (->V8XX)
Jul 07 20:44:05-735532 cadet-tun-8620 DEBUG  to tunnel V8XX
Jul 07 20:44:05-735747 util-scheduler-8620 DEBUG Adding task: 71 / 0x4d64a70
Jul 07 20:44:05-736002 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection CMHCKRVP (->V8XX)  (100 bytes)
Jul 07 20:44:05-736190 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0 (create)
Jul 07 20:44:05-736418 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:05-736624 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:05-736918 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:44:05-737116 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:05-737359 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:05-737542 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:05-737717 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:05-737923 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:44:05-738139 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:44:05-738351 util-scheduler-8620 DEBUG Adding task: 72 / 0x4d6ff98
Jul 07 20:44:05-738529 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:05-738742 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:05-738916 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:05-739091 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:05-739329 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:05-739511 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:05-739687 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:05-739885 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:05-740094 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_SEARCHING => CADET_TUNNEL_WAITING
Jul 07 20:44:05-740333 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:44:05-740521 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-740733 util-scheduler-8620 DEBUG Adding task: 73 / 0x46620a0
Jul 07 20:44:05-740993 util-scheduler-8620 DEBUG Checking readiness of task: 73 / 0x46620a0
Jul 07 20:44:05-741186 util-scheduler-8620 DEBUG Checking readiness of task: 66 / 0x4d5e5d8
Jul 07 20:44:05-741397 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-741586 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-741798 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-741988 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-742176 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-742368 util-scheduler-8620 DEBUG Running task: 66 / 0x4d5e5d8
Jul 07 20:44:05-742555 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-742735 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-742908 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-743154 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:05-743364 util-scheduler-8620 DEBUG Adding task: 74 / 0x4d5e5d8
Jul 07 20:44:05-743567 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:44:05-743879 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-744083 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:05-744283 util-scheduler-8620 DEBUG Running task: 72 / 0x4d6ff98
Jul 07 20:44:05-744495 util-scheduler-8620 DEBUG Adding task: 75 / 0x4d6ff98
Jul 07 20:44:05-744718 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:05-745047 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:05-745274 util-scheduler-8620 DEBUG Adding task: 76 / 0x46620a0
Jul 07 20:44:05-745475 util-scheduler-8620 DEBUG Running task: 71 / 0x4d64a70
Jul 07 20:44:05-745673 util-scheduler-8620 DEBUG Running task: 68 / 0x4663f10
Jul 07 20:44:05-745864 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:44:05-746090 util-scheduler-8620 DEBUG Adding task: 77 / 0x4663f10
Jul 07 20:44:05-746302 transport-api-8620 DEBUG Receiving `CONNECT' message for `TZQE'.
Jul 07 20:44:05-746510 transport-api-8620 DEBUG Creating entry for neighbour `TZQE'.
Jul 07 20:44:05-746713 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:44:05-746904 util-bandwidth-8620 DEBUG Tracker 0x4d73060 initialized with 1024 Bps and max carry 5
Jul 07 20:44:05-747127 util-scheduler-8620 DEBUG Adding task: 78 / 0x4d73060
Jul 07 20:44:05-747350 transport-api-8620 DEBUG Receiving `CONNECT' message for `TZQE' with quota 13651
Jul 07 20:44:05-747539 util-bandwidth-8620 DEBUG Tracker 0x4d73060 bandwidth changed to 13651 Bps
Jul 07 20:44:05-747771 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 1024 Bps, last update was 829 µs ago
Jul 07 20:44:05-747980 util-scheduler-8620 DEBUG Canceling task: 78 / 0x4d73060
Jul 07 20:44:05-748190 util-scheduler-8620 DEBUG Adding task: 79 / 0x4d73060
Jul 07 20:44:05-748385 util-scheduler-8620 DEBUG Running task: 67 / 0x465f008
Jul 07 20:44:05-748574 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:44:05-748799 nse-api-8620 DEBUG Received information about peer `P00P' from peerinfo database
Jul 07 20:44:05-749076 cadet-hll-8620 DEBUG  hello for P00P (64 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-749312 cadet-p2p-8620 DEBUG set hello for P00P
Jul 07 20:44:05-749487 cadet-p2p-8620 DEBUG  new (64 bytes)
Jul 07 20:44:05-749697 util-scheduler-8620 DEBUG Adding task: 80 / 0x465f008
Jul 07 20:44:05-749944 util-scheduler-8620 DEBUG Checking readiness of task: 76 / 0x46620a0
Jul 07 20:44:05-750136 util-scheduler-8620 DEBUG Checking readiness of task: 74 / 0x4d5e5d8
Jul 07 20:44:05-750325 util-scheduler-8620 DEBUG Checking readiness of task: 73 / 0x46620a0
Jul 07 20:44:05-750514 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-750702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-750890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-751078 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-751266 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-751475 util-scheduler-8620 DEBUG Running task: 74 / 0x4d5e5d8
Jul 07 20:44:05-751659 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:05-751835 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-752005 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-752359 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:44:05-752660 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:05-752872 util-scheduler-8620 DEBUG Running task: 76 / 0x46620a0
Jul 07 20:44:05-753056 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:05-753250 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-753420 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-753597 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:05-753791 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-753981 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:05-754281 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:05-754488 util-scheduler-8620 DEBUG Running task: 80 / 0x465f008
Jul 07 20:44:05-754679 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:44:05-754913 nse-api-8620 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 20:44:05-755177 cadet-hll-8620 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-755404 cadet-p2p-8620 DEBUG set hello for STRN
Jul 07 20:44:05-755919 cadet-p2p-8620 DEBUG  new (90 bytes)
Jul 07 20:44:05-756134 util-scheduler-8620 DEBUG Adding task: 81 / 0x465f008
Jul 07 20:44:05-756331 util-scheduler-8620 DEBUG Running task: 77 / 0x4663f10
Jul 07 20:44:05-756521 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:44:05-756712 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-756924 util-scheduler-8620 DEBUG Adding task: 82 / 0x4663d68
Jul 07 20:44:05-757145 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX'.
Jul 07 20:44:05-757381 transport-api-8620 DEBUG Creating entry for neighbour `V8XX'.
Jul 07 20:44:05-757575 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:44:05-757772 util-bandwidth-8620 DEBUG Tracker 0x4d744e8 initialized with 1024 Bps and max carry 5
Jul 07 20:44:05-758000 util-scheduler-8620 DEBUG Adding task: 83 / 0x4d744e8
Jul 07 20:44:05-758227 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX' with quota 9326
Jul 07 20:44:05-758505 util-bandwidth-8620 DEBUG Tracker 0x4d744e8 bandwidth changed to 9326 Bps
Jul 07 20:44:05-758738 util-bandwidth-8620 DEBUG Tracker 0x4d744e8 updated, have 1024 Bps, last update was 931 µs ago
Jul 07 20:44:05-758948 util-scheduler-8620 DEBUG Canceling task: 83 / 0x4d744e8
Jul 07 20:44:05-759159 util-scheduler-8620 DEBUG Adding task: 84 / 0x4d744e8
Jul 07 20:44:05-759405 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-759597 util-scheduler-8620 DEBUG Checking readiness of task: 73 / 0x46620a0
Jul 07 20:44:05-759787 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-759976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-760164 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-760352 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-760540 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-760730 util-scheduler-8620 DEBUG Running task: 73 / 0x46620a0
Jul 07 20:44:05-761139 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:05-761683 util-scheduler-8620 DEBUG Adding task: 85 / 0x4662248
Jul 07 20:44:05-761898 util-scheduler-8620 DEBUG Running task: 81 / 0x465f008
Jul 07 20:44:05-762111 util-8620 DEBUG Received message of type 332 and size 578 from peerinfo service.
Jul 07 20:44:05-762355 nse-api-8620 DEBUG Received information about peer `GN10' from peerinfo database
Jul 07 20:44:05-762643 cadet-hll-8620 DEBUG  hello for GN10 (538 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-762862 cadet-p2p-8620 DEBUG set hello for GN10
Jul 07 20:44:05-763035 cadet-p2p-8620 DEBUG  new (538 bytes)
Jul 07 20:44:05-765432 cadet-hll-8620 DEBUG  updated mine to 0x4d74eb0
Jul 07 20:44:05-765649 util-scheduler-8620 DEBUG Adding task: 86 / 0x465f008
Jul 07 20:44:05-765890 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-766082 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-766271 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-766459 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-766648 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-766836 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-767025 util-scheduler-8620 DEBUG Running task: 86 / 0x465f008
Jul 07 20:44:05-767214 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:44:05-767436 nse-api-8620 DEBUG Received information about peer `QCZ4' from peerinfo database
Jul 07 20:44:05-767697 cadet-hll-8620 DEBUG  hello for QCZ4 (64 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-767937 cadet-p2p-8620 DEBUG set hello for QCZ4
Jul 07 20:44:05-768110 cadet-p2p-8620 DEBUG  new (64 bytes)
Jul 07 20:44:05-768328 util-scheduler-8620 DEBUG Adding task: 87 / 0x465f008
Jul 07 20:44:05-768523 util-scheduler-8620 DEBUG Running task: 85 / 0x4662248
Jul 07 20:44:05-768711 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:05-768903 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:05-770729 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:05-772353 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:05-772580 util-scheduler-8620 DEBUG Adding task: 88 / 0x46620a0
Jul 07 20:44:05-772964 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-773175 util-scheduler-8620 DEBUG Adding task: 89 / 0x46620a0
Jul 07 20:44:05-773447 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-773641 util-scheduler-8620 DEBUG Checking readiness of task: 88 / 0x46620a0
Jul 07 20:44:05-773832 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-774021 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-774210 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-774399 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-774588 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-774777 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-774968 util-scheduler-8620 DEBUG Running task: 88 / 0x46620a0
Jul 07 20:44:05-775154 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:05-775343 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-775515 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-776983 util-scheduler-8620 DEBUG Canceling task: 75 / 0x4d6ff98
Jul 07 20:44:05-778402 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:44:05-781446 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 100)
Jul 07 20:44:05-783118 cadet-p2p-8620 DEBUG Checking 0x4d71d90 towards CMHCKRVP (->V8XX)
Jul 07 20:44:05-785740 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:05-786833 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:05-787960 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:05-789634 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:05-793591 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:05-797852 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:44:05-802245 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:05-808397 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:05-811351 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:05-813306 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:05-816958 util-scheduler-8620 DEBUG Adding task: 90 / 0x4d707d0
Jul 07 20:44:05-821037 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:44:05-822434 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:05-824720 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:05-825278 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:05-825463 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:05-825643 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:05-825935 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:05-827433 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:44:05-828605 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:05-829785 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-830213 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:05-831578 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:05-831810 util-scheduler-8620 DEBUG Running task: 87 / 0x465f008
Jul 07 20:44:05-832009 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:44:05-832258 nse-api-8620 DEBUG Received information about peer `TZQE' from peerinfo database
Jul 07 20:44:05-832641 cadet-hll-8620 DEBUG  hello for TZQE (90 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-832872 cadet-p2p-8620 DEBUG set hello for TZQE
Jul 07 20:44:05-833057 cadet-p2p-8620 DEBUG  new (90 bytes)
Jul 07 20:44:05-833325 util-scheduler-8620 DEBUG Adding task: 91 / 0x465f008
Jul 07 20:44:05-833604 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-833808 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-834004 util-scheduler-8620 DEBUG Checking readiness of task: 43 / 0x4665be0
Jul 07 20:44:05-834202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-834397 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-834593 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-834787 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-835011 util-scheduler-8620 DEBUG Running task: 43 / 0x4665be0
Jul 07 20:44:05-835446 util-8620 DEBUG receive_ready read 346/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:44:05-835725 util-scheduler-8620 DEBUG Adding task: 92 / 0x4665d88
Jul 07 20:44:05-835945 util-scheduler-8620 DEBUG Running task: 91 / 0x465f008
Jul 07 20:44:05-836144 util-8620 DEBUG Received message of type 332 and size 422 from peerinfo service.
Jul 07 20:44:05-836388 nse-api-8620 DEBUG Received information about peer `V8XX' from peerinfo database
Jul 07 20:44:05-836649 cadet-hll-8620 DEBUG  hello for V8XX (382 bytes), expires on end of time
Jul 07 20:44:05-836876 cadet-p2p-8620 DEBUG set hello for V8XX
Jul 07 20:44:05-837059 cadet-p2p-8620 DEBUG  new (382 bytes)
Jul 07 20:44:05-837320 util-scheduler-8620 DEBUG Adding task: 93 / 0x465f008
Jul 07 20:44:05-837584 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-837782 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-837978 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-838172 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-838366 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-838587 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-838779 util-scheduler-8620 DEBUG Running task: 93 / 0x465f008
Jul 07 20:44:05-838971 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:44:05-839365 nse-api-8620 DEBUG Received information about peer `WAKN' from peerinfo database
Jul 07 20:44:05-839649 cadet-hll-8620 DEBUG  hello for WAKN (90 bytes), expires on Tue Jul 08 08:43:56 2014
Jul 07 20:44:05-839902 cadet-p2p-8620 DEBUG set hello for WAKN
Jul 07 20:44:05-840077 cadet-p2p-8620 DEBUG  new (90 bytes)
Jul 07 20:44:05-840294 util-scheduler-8620 DEBUG Adding task: 94 / 0x465f008
Jul 07 20:44:05-840492 util-scheduler-8620 DEBUG Running task: 92 / 0x4665d88
Jul 07 20:44:05-840681 util-8620 DEBUG Received message of type 145 and size 346 from dht service.
Jul 07 20:44:05-841871 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-842100 util-scheduler-8620 DEBUG Adding task: 95 / 0x4665be0
Jul 07 20:44:05-843930 dht-api-8620 DEBUG Received reply for `P00PHXNA' from DHT service 0x46642c0
Jul 07 20:44:05-848482 dht-api-8620 DEBUG Giving 90 byte reply for P00PHXNA to application
Jul 07 20:44:05-854539 cadet-dht-8620 DEBUG    GET has 1 hops.
Jul 07 20:44:05-856293 cadet-dht-8620 DEBUG    Adding from GET: STRN.
Jul 07 20:44:05-857974 cadet-dht-8620 DEBUG    PUT has 4 hops.
Jul 07 20:44:05-859705 cadet-dht-8620 DEBUG    Adding from PUT: TZQE.
Jul 07 20:44:05-860741 cadet-dht-8620 DEBUG    Adding from PUT: KNAS.
Jul 07 20:44:05-864321 cadet-dht-8620 DEBUG    Adding from PUT: GN10.
Jul 07 20:44:05-864618 cadet-dht-8620 DEBUG    Adding from PUT: P00P.
Jul 07 20:44:05-865897 cadet-dht-8620 DEBUG    (first of GET: STRN)
Jul 07 20:44:05-867129 cadet-dht-8620 DEBUG    (first of PUT: P00P)
Jul 07 20:44:05-868102 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:44:05-869670 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:44:05-870163 cadet-dht-8620 DEBUG        3: P00P
Jul 07 20:44:05-871624 cadet-dht-8620 INFO Got path from DHT:  GN10 P00P
Jul 07 20:44:05-873433 cadet-dht-8620 DEBUG Got HELLO for P00P
Jul 07 20:44:05-877321 cadet-p2p-8620 DEBUG adding path [2] to peer P00P
Jul 07 20:44:05-877509 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:05-879928 cadet-p2p-8620 DEBUG set hello for P00P
Jul 07 20:44:05-894738 cadet-p2p-8620 DEBUG  merge into 0x4d793a8 (90 bytes)
Jul 07 20:44:05-899485 transport-api-8620 DEBUG Offering `HELLO' message of `P00P' to transport for validation.
Jul 07 20:44:05-900729 transport-api-8620 DEBUG Control transmit of 90 bytes requested
Jul 07 20:44:05-901125 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:05-901369 util-scheduler-8620 DEBUG Adding task: 96 / 0x46624e8
Jul 07 20:44:05-903602 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-903805 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-904001 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-904191 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-904380 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-904569 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-904758 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-904950 util-scheduler-8620 DEBUG Running task: 96 / 0x46624e8
Jul 07 20:44:05-905260 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:44:05-905467 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:44:05-905680 util-scheduler-8620 DEBUG Adding task: 97 / 0x4663d68
Jul 07 20:44:05-905882 util-scheduler-8620 DEBUG Running task: 94 / 0x465f008
Jul 07 20:44:05-906080 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:44:05-906322 nse-api-8620 DEBUG Received information about peer `Z1SP' from peerinfo database
Jul 07 20:44:05-906597 cadet-hll-8620 DEBUG  hello for Z1SP (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:44:05-906880 cadet-p2p-8620 DEBUG set hello for Z1SP
Jul 07 20:44:05-907060 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:44:05-907289 util-scheduler-8620 DEBUG Adding task: 98 / 0x465f008
Jul 07 20:44:05-907541 util-scheduler-8620 DEBUG Checking readiness of task: 97 / 0x4663d68
Jul 07 20:44:05-907748 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-907938 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-908127 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-908319 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-908507 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-908696 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-908884 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-909075 util-scheduler-8620 DEBUG Running task: 97 / 0x4663d68
Jul 07 20:44:05-909286 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:44:05-909478 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-909650 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-911196 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:44:05-914452 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:44:05-914681 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:05-914882 util-scheduler-8620 DEBUG Adding task: 99 / 0x46624e8
Jul 07 20:44:05-917282 transport-api-8620 DEBUG Added 90 bytes of control message at 0
Jul 07 20:44:05-918298 util-scheduler-8620 DEBUG Canceling task: 99 / 0x46624e8
Jul 07 20:44:05-918698 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:05-918910 util-scheduler-8620 DEBUG Adding task: 100 / 0x46624e8
Jul 07 20:44:05-919267 transport-api-8620 DEBUG Transmitting 90 bytes to transport service
Jul 07 20:44:05-919475 util-8620 DEBUG Transmitting message of type 17 and size 90 to transport service.
Jul 07 20:44:05-919923 util-8620 DEBUG Connection transmitted 90/90 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:44:05-920145 util-scheduler-8620 DEBUG Running task: 98 / 0x465f008
Jul 07 20:44:05-920343 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:44:05-920578 nse-api-8620 DEBUG Received information about peer `FMX4' from peerinfo database
Jul 07 20:44:05-922048 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:44:05-922531 util-scheduler-8620 DEBUG Adding task: 101 / 0x465f008
Jul 07 20:44:05-922799 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-922994 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-923185 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-923375 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-923565 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-923755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-923944 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-924134 util-scheduler-8620 DEBUG Running task: 101 / 0x465f008
Jul 07 20:44:05-924325 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:44:05-924549 nse-api-8620 DEBUG Received information about peer `FMX4' from peerinfo database
Jul 07 20:44:05-924814 cadet-hll-8620 DEBUG  hello for FMX4 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:44:05-925061 cadet-p2p-8620 DEBUG set hello for FMX4
Jul 07 20:44:05-925258 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:44:05-925445 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-925668 util-scheduler-8620 DEBUG Adding task: 102 / 0x465ee60
Jul 07 20:44:05-925867 util-scheduler-8620 DEBUG Running task: 100 / 0x46624e8
Jul 07 20:44:05-926072 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:44:05-926269 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:44:05-926467 util-scheduler-8620 DEBUG Adding task: 103 / 0x4663d68
Jul 07 20:44:05-926708 util-scheduler-8620 DEBUG Checking readiness of task: 103 / 0x4663d68
Jul 07 20:44:05-926900 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:05-927089 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-927279 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-927467 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-927656 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-927844 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-928032 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-928221 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-928411 util-scheduler-8620 DEBUG Running task: 103 / 0x4663d68
Jul 07 20:44:05-928596 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:44:05-928772 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-928943 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-930598 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `P00P'.
Jul 07 20:44:05-933237 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:44:05-933481 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:44:05-933686 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:44:05-934072 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:44:05-940383 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:05-940591 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-940783 util-scheduler-8620 DEBUG Checking readiness of task: 89 / 0x46620a0
Jul 07 20:44:05-940975 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-941164 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-941377 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-941567 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-941756 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-941949 util-scheduler-8620 DEBUG Running task: 89 / 0x46620a0
Jul 07 20:44:05-942355 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:05-942612 util-scheduler-8620 DEBUG Adding task: 104 / 0x4662248
Jul 07 20:44:05-942864 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:05-943055 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-943244 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-943433 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-943622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-943811 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-944000 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-944189 util-scheduler-8620 DEBUG Running task: 104 / 0x4662248
Jul 07 20:44:05-944379 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:05-944576 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:05-944962 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:05-945179 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:05-945411 util-scheduler-8620 DEBUG Adding task: 105 / 0x46620a0
Jul 07 20:44:05-945621 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:05-945827 util-scheduler-8620 DEBUG Adding task: 106 / 0x46620a0
Jul 07 20:44:05-946090 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:05-946284 util-scheduler-8620 DEBUG Checking readiness of task: 105 / 0x46620a0
Jul 07 20:44:05-946482 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:05-946675 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:05-946869 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:05-947059 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:05-947252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:05-947443 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:05-947632 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:05-947827 util-scheduler-8620 DEBUG Running task: 105 / 0x46620a0
Jul 07 20:44:05-948013 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:05-948191 util-8620 DEBUG process_notify is running
Jul 07 20:44:05-948362 util-8620 DEBUG client_notify is running
Jul 07 20:44:05-948550 util-scheduler-8620 DEBUG Canceling task: 58 / 0x4d683b0
Jul 07 20:44:05-948901 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:05-949321 cadet-p2p-8620 DEBUG Queue send towards P00P (max 100)
Jul 07 20:44:05-949720 cadet-p2p-8620 DEBUG Checking 0x4d6a1a8 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:05-950048 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:05-950322 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:05-950585 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:05-950862 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:05-951137 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:05-951499 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:05-951849 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:05-952186 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:05-952532 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:05-952873 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:05-953094 util-scheduler-8620 DEBUG Adding task: 107 / 0x4d68be8
Jul 07 20:44:05-953511 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:44:05-953841 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:05-954118 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:05-954327 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:05-954504 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:05-954679 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:05-954878 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:05-955188 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:05-955477 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:05-955664 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:05-955858 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:05-958493 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:06-193726 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-194109 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-194309 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:06-194502 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-194694 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-194887 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-195079 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-195301 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-195497 util-scheduler-8620 DEBUG Running task: 14 / (nil)
Jul 07 20:44:06-195928 cadet-dht-8620 DEBUG Announce ID
Jul 07 20:44:06-196284 cadet-hll-8620 DEBUG  mine is 0x4d74eb0
Jul 07 20:44:06-198150 cadet-dht-8620 DEBUG Hello 0x4d74eb0 size: 538
Jul 07 20:44:06-201041 util-scheduler-8620 DEBUG Adding task: 108 / 0x4d7d0c8
Jul 07 20:44:06-208660 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:44:06-208936 util-scheduler-8620 DEBUG Adding task: 109 / 0x4665be0
Jul 07 20:44:06-209660 util-scheduler-8620 DEBUG Adding task: 110 / (nil)
Jul 07 20:44:06-210184 util-scheduler-8620 DEBUG Checking readiness of task: 109 / 0x4665be0
Jul 07 20:44:06-210385 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-210578 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-210769 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:06-210959 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-211149 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-211339 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-211528 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-211717 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-211910 util-scheduler-8620 DEBUG Running task: 109 / 0x4665be0
Jul 07 20:44:06-212097 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:44:06-212291 util-8620 DEBUG process_notify is running
Jul 07 20:44:06-212464 util-8620 DEBUG client_notify is running
Jul 07 20:44:06-213708 dht-api-8620 DEBUG Forwarded request of 634 bytes to DHT service
Jul 07 20:44:06-213916 util-8620 DEBUG Transmitting message of type 142 and size 634 to dht service.
Jul 07 20:44:06-215009 util-8620 DEBUG Connection transmitted 634/634 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:44:06-215344 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-215551 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-215753 util-scheduler-8620 DEBUG Checking readiness of task: 95 / 0x4665be0
Jul 07 20:44:06-215953 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-216152 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-216349 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-216546 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-216737 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-220748 util-scheduler-8620 DEBUG Running task: 95 / 0x4665be0
Jul 07 20:44:06-221297 util-8620 DEBUG receive_ready read 16/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:44:06-221575 util-scheduler-8620 DEBUG Adding task: 111 / 0x4665d88
Jul 07 20:44:06-221846 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-222038 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-222228 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-222417 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-222606 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-222798 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-222988 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-223189 util-scheduler-8620 DEBUG Running task: 111 / 0x4665d88
Jul 07 20:44:06-223381 util-8620 DEBUG Received message of type 155 and size 16 from dht service.
Jul 07 20:44:06-223579 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:06-223821 util-scheduler-8620 DEBUG Adding task: 112 / 0x4665be0
Jul 07 20:44:06-225742 util-scheduler-8620 DEBUG Canceling task: 108 / 0x4d7d0c8
Jul 07 20:44:06-817374 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-817763 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-817973 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-818166 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-818357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-818547 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-818737 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-818927 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-819120 util-scheduler-8620 DEBUG Running task: 90 / 0x4d707d0
Jul 07 20:44:06-820922 cadet-con-8620 DEBUG FWD keepalive for CMHCKRVP (->V8XX)
Jul 07 20:44:06-822531 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:06-823248 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection CMHCKRVP (->V8XX)  (100 bytes)
Jul 07 20:44:06-823457 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0 (create)
Jul 07 20:44:06-823693 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:06-823905 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:06-824217 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:44:06-824416 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:06-824643 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:06-824828 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:06-825005 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:06-826040 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:44:06-826277 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:44:06-826510 util-scheduler-8620 DEBUG Adding task: 113 / 0x4d6ff98
Jul 07 20:44:06-826697 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:06-826908 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:06-827087 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:06-827267 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:06-827513 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:06-827711 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:06-827890 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:06-828098 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:06-828938 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-829150 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-829367 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-829558 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-829748 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-829938 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-830130 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-830319 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-830510 util-scheduler-8620 DEBUG Running task: 113 / 0x4d6ff98
Jul 07 20:44:06-830725 util-scheduler-8620 DEBUG Adding task: 114 / 0x4d6ff98
Jul 07 20:44:06-830952 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:06-831156 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:06-831364 util-scheduler-8620 DEBUG Adding task: 115 / 0x46620a0
Jul 07 20:44:06-831605 util-scheduler-8620 DEBUG Checking readiness of task: 115 / 0x46620a0
Jul 07 20:44:06-831798 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-831988 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-832214 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-832404 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-832594 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-832782 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-833612 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-833806 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-833999 util-scheduler-8620 DEBUG Running task: 115 / 0x46620a0
Jul 07 20:44:06-834186 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:06-834366 util-8620 DEBUG process_notify is running
Jul 07 20:44:06-834538 util-8620 DEBUG client_notify is running
Jul 07 20:44:06-834719 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:06-834919 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:06-835110 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:06-835416 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:06-953370 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-953732 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-953928 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-954119 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-954310 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-954500 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-954689 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-954880 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-955072 util-scheduler-8620 DEBUG Running task: 107 / 0x4d68be8
Jul 07 20:44:06-955584 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:44:06-955856 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:06-956111 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:06-956304 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:06-956537 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:06-956747 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:06-957112 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:06-957337 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:06-957564 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:06-957748 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:06-957924 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:06-958131 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:06-958346 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:06-958570 util-scheduler-8620 DEBUG Adding task: 116 / 0x4d683b0
Jul 07 20:44:06-958752 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:06-958963 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:06-959141 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:06-959319 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:06-959561 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:06-959746 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:06-959924 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:06-960128 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:06-960391 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-960586 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-960816 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-961011 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-961228 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-961789 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-961989 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-962254 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-962449 util-scheduler-8620 DEBUG Running task: 116 / 0x4d683b0
Jul 07 20:44:06-962664 util-scheduler-8620 DEBUG Adding task: 117 / 0x4d683b0
Jul 07 20:44:06-962893 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:06-963096 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:06-963303 util-scheduler-8620 DEBUG Adding task: 118 / 0x46620a0
Jul 07 20:44:06-963551 util-scheduler-8620 DEBUG Checking readiness of task: 118 / 0x46620a0
Jul 07 20:44:06-963744 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:06-963933 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:06-964122 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:06-964311 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:06-964500 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:06-964688 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:06-964876 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:06-965064 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:06-965277 util-scheduler-8620 DEBUG Running task: 118 / 0x46620a0
Jul 07 20:44:06-965478 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:06-965997 util-8620 DEBUG process_notify is running
Jul 07 20:44:06-966175 util-8620 DEBUG client_notify is running
Jul 07 20:44:06-966357 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:06-966555 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:06-966747 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:06-967061 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:08-604299 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-604686 util-scheduler-8620 DEBUG Checking readiness of task: 106 / 0x46620a0
Jul 07 20:44:08-604885 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-605078 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-605296 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-605488 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-605679 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-605870 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-606066 util-scheduler-8620 DEBUG Running task: 106 / 0x46620a0
Jul 07 20:44:08-606488 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:08-606746 util-scheduler-8620 DEBUG Adding task: 119 / 0x4662248
Jul 07 20:44:08-607025 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-607217 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-607407 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-607596 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-607786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-607976 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-608197 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-608387 util-scheduler-8620 DEBUG Running task: 119 / 0x4662248
Jul 07 20:44:08-608580 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:08-608779 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:08-609013 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:08-609701 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:08-609920 util-scheduler-8620 DEBUG Adding task: 120 / 0x46620a0
Jul 07 20:44:08-610109 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:08-610318 util-scheduler-8620 DEBUG Adding task: 121 / 0x46620a0
Jul 07 20:44:08-610566 util-scheduler-8620 DEBUG Checking readiness of task: 121 / 0x46620a0
Jul 07 20:44:08-610758 util-scheduler-8620 DEBUG Checking readiness of task: 120 / 0x46620a0
Jul 07 20:44:08-610950 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-611143 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-611333 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-611523 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-611713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-611903 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-612092 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-612284 util-scheduler-8620 DEBUG Running task: 120 / 0x46620a0
Jul 07 20:44:08-612471 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:08-612650 util-8620 DEBUG process_notify is running
Jul 07 20:44:08-612822 util-8620 DEBUG client_notify is running
Jul 07 20:44:08-613010 util-scheduler-8620 DEBUG Canceling task: 44 / 0x4d5c9e8
Jul 07 20:44:08-613259 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:44:08-613482 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 100)
Jul 07 20:44:08-613723 cadet-p2p-8620 DEBUG Checking 0x4d631f0 towards HS92G30M (->KNAS)
Jul 07 20:44:08-614061 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:08-614241 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:08-614412 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:08-614582 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:08-614763 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:08-615030 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:44:08-615224 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:08-615406 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:08-615595 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:08-616114 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:08-616893 util-scheduler-8620 DEBUG Adding task: 122 / 0x4d61c30
Jul 07 20:44:08-617136 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:44:08-617336 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:08-617519 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:08-617720 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:08-617895 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:08-618070 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:08-618270 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:08-618474 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:44:08-618658 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:08-618838 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:08-619030 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:08-620062 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:08-620349 util-scheduler-8620 DEBUG Checking readiness of task: 121 / 0x46620a0
Jul 07 20:44:08-620545 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-620737 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-620928 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-621121 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-621685 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-621878 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-622069 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-622261 util-scheduler-8620 DEBUG Running task: 121 / 0x46620a0
Jul 07 20:44:08-622664 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:08-622895 util-scheduler-8620 DEBUG Adding task: 123 / 0x4662248
Jul 07 20:44:08-623143 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-623335 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-623525 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-623714 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-623917 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-624105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-624294 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-624483 util-scheduler-8620 DEBUG Running task: 123 / 0x4662248
Jul 07 20:44:08-624673 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:08-624867 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:08-625080 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:08-625305 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:08-625508 util-scheduler-8620 DEBUG Adding task: 124 / 0x46620a0
Jul 07 20:44:08-625693 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:08-625902 util-scheduler-8620 DEBUG Adding task: 125 / 0x46620a0
Jul 07 20:44:08-626143 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:08-626333 util-scheduler-8620 DEBUG Checking readiness of task: 124 / 0x46620a0
Jul 07 20:44:08-626524 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:08-626713 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:08-626902 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:08-627092 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:08-627280 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:08-627469 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:08-627658 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:08-627849 util-scheduler-8620 DEBUG Running task: 124 / 0x46620a0
Jul 07 20:44:08-628034 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:08-628209 util-8620 DEBUG process_notify is running
Jul 07 20:44:08-628381 util-8620 DEBUG client_notify is running
Jul 07 20:44:08-628625 util-scheduler-8620 DEBUG Canceling task: 117 / 0x4d683b0
Jul 07 20:44:08-629222 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:08-629441 cadet-p2p-8620 DEBUG Queue send towards P00P (max 100)
Jul 07 20:44:08-629674 cadet-p2p-8620 DEBUG Checking 0x4d802b0 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:08-629906 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:08-630083 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:08-630252 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:08-630421 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:08-630613 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:08-630873 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:08-631068 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:08-631245 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:08-631431 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:08-631611 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:08-632153 util-scheduler-8620 DEBUG Adding task: 126 / 0x4d68be8
Jul 07 20:44:08-632397 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:44:08-632571 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:08-632752 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:08-632954 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:08-633129 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:08-633330 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:08-633532 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:08-633736 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:08-633920 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:08-634099 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:08-634289 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:08-636566 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:09-618041 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:09-618426 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:09-618625 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:09-618824 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:09-619021 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:09-619215 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:09-619412 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:09-619605 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:09-619818 util-scheduler-8620 DEBUG Running task: 122 / 0x4d61c30
Jul 07 20:44:09-620100 cadet-con-8620 DEBUG FWD keepalive for HS92G30M (->KNAS)
Jul 07 20:44:09-620366 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:09-620618 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection HS92G30M (->KNAS)  (100 bytes)
Jul 07 20:44:09-620809 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0 (create)
Jul 07 20:44:09-621041 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:09-621275 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:09-621580 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:44:09-621780 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:09-622006 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:09-622189 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:09-622365 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:09-622572 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 100 bytes
Jul 07 20:44:09-622790 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:44:09-623017 util-scheduler-8620 DEBUG Adding task: 127 / 0x4d5c9e8
Jul 07 20:44:09-623197 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:09-623402 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:09-623577 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:09-623755 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:09-623995 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on HS92G30M (->KNAS)
Jul 07 20:44:09-624178 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:09-624355 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:09-624583 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:09-624843 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:09-625035 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:09-625243 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:09-625434 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:09-625623 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:09-625811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:09-626000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:09-626188 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:09-626377 util-scheduler-8620 DEBUG Running task: 127 / 0x4d5c9e8
Jul 07 20:44:09-626586 util-scheduler-8620 DEBUG Adding task: 128 / 0x4d5c9e8
Jul 07 20:44:09-626808 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:09-627010 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:09-627230 util-scheduler-8620 DEBUG Adding task: 129 / 0x46620a0
Jul 07 20:44:09-627471 util-scheduler-8620 DEBUG Checking readiness of task: 129 / 0x46620a0
Jul 07 20:44:09-627663 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:09-627852 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:09-628041 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:09-628230 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:09-628418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:09-628606 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:09-628794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:09-628982 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:09-629174 util-scheduler-8620 DEBUG Running task: 129 / 0x46620a0
Jul 07 20:44:09-629394 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:09-629573 util-8620 DEBUG process_notify is running
Jul 07 20:44:09-629745 util-8620 DEBUG client_notify is running
Jul 07 20:44:09-629925 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:09-630124 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:09-630314 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:09-630636 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:10-633330 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:10-633701 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-633897 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-634092 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-634282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-634472 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-634661 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-634851 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-635044 util-scheduler-8620 DEBUG Running task: 126 / 0x4d68be8
Jul 07 20:44:10-635313 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:44:10-635491 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:10-635743 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:10-635936 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:10-636172 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:10-636384 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:10-636696 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:10-637010 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:10-637263 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:10-637448 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:10-637624 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:10-637831 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:10-638047 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:10-638274 util-scheduler-8620 DEBUG Adding task: 130 / 0x4d683b0
Jul 07 20:44:10-638453 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:10-638674 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:10-638849 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:10-639024 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:10-639262 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:10-639445 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:10-639619 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:10-639818 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:10-640073 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:10-640264 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-640453 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-640640 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-640829 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-641017 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-641226 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-641416 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-641605 util-scheduler-8620 DEBUG Running task: 130 / 0x4d683b0
Jul 07 20:44:10-641813 util-scheduler-8620 DEBUG Adding task: 131 / 0x4d683b0
Jul 07 20:44:10-642033 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:10-642234 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:10-642440 util-scheduler-8620 DEBUG Adding task: 132 / 0x46620a0
Jul 07 20:44:10-642680 util-scheduler-8620 DEBUG Checking readiness of task: 132 / 0x46620a0
Jul 07 20:44:10-642873 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:10-643062 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-643250 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-643438 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-643626 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-643814 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-644005 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-644193 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-644384 util-scheduler-8620 DEBUG Running task: 132 / 0x46620a0
Jul 07 20:44:10-644567 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:10-644746 util-8620 DEBUG process_notify is running
Jul 07 20:44:10-644916 util-8620 DEBUG client_notify is running
Jul 07 20:44:10-645095 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:10-645310 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:10-645500 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:10-645816 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:10-660114 util-scheduler-8620 DEBUG Checking readiness of task: 125 / 0x46620a0
Jul 07 20:44:10-660341 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-660560 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-660753 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-660944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-661135 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-661348 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-661543 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-661736 util-scheduler-8620 DEBUG Running task: 125 / 0x46620a0
Jul 07 20:44:10-662146 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:10-662385 util-scheduler-8620 DEBUG Adding task: 133 / 0x4662248
Jul 07 20:44:10-662638 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-662828 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-663017 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-663217 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-663406 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-663594 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-663782 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-663971 util-scheduler-8620 DEBUG Running task: 133 / 0x4662248
Jul 07 20:44:10-664161 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:10-664358 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:10-664578 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:10-664776 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:10-664976 util-scheduler-8620 DEBUG Adding task: 134 / 0x46620a0
Jul 07 20:44:10-665161 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:10-665387 util-scheduler-8620 DEBUG Adding task: 135 / 0x46620a0
Jul 07 20:44:10-665626 util-scheduler-8620 DEBUG Checking readiness of task: 135 / 0x46620a0
Jul 07 20:44:10-665816 util-scheduler-8620 DEBUG Checking readiness of task: 134 / 0x46620a0
Jul 07 20:44:10-666007 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-666195 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-666383 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-666571 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-666759 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-666947 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-667135 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-667325 util-scheduler-8620 DEBUG Running task: 134 / 0x46620a0
Jul 07 20:44:10-667522 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:10-667697 util-8620 DEBUG process_notify is running
Jul 07 20:44:10-667867 util-8620 DEBUG client_notify is running
Jul 07 20:44:10-668051 util-scheduler-8620 DEBUG Canceling task: 114 / 0x4d6ff98
Jul 07 20:44:10-668274 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:44:10-668490 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 100)
Jul 07 20:44:10-668722 cadet-p2p-8620 DEBUG Checking 0x4d7eba8 towards CMHCKRVP (->V8XX)
Jul 07 20:44:10-668955 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:10-669131 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:10-669386 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:10-669557 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:10-669737 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:10-669999 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:44:10-670209 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:10-670390 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:10-670577 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:10-670757 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:10-670965 util-scheduler-8620 DEBUG Adding task: 136 / 0x4d707d0
Jul 07 20:44:10-671204 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:44:10-671373 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:10-671556 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:10-671754 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:10-671927 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:10-672099 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:10-672306 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:10-672510 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:44:10-672695 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:10-672873 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:10-673064 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:10-673860 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:10-682407 util-scheduler-8620 DEBUG Checking readiness of task: 135 / 0x46620a0
Jul 07 20:44:10-682666 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-682860 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-683050 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-683240 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-683429 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-683618 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-683807 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-683999 util-scheduler-8620 DEBUG Running task: 135 / 0x46620a0
Jul 07 20:44:10-684408 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:10-684649 util-scheduler-8620 DEBUG Adding task: 137 / 0x4662248
Jul 07 20:44:10-684906 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:10-685098 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:10-685317 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:10-685510 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:10-685706 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:10-685900 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:10-686097 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:10-686291 util-scheduler-8620 DEBUG Running task: 137 / 0x4662248
Jul 07 20:44:10-686569 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:10-686771 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:10-688716 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `KNAS'
Jul 07 20:44:10-693626 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection HS92G30M from KNAS
Jul 07 20:44:10-696987 cadet-con-8620 DEBUG   via peer KNAS
Jul 07 20:44:10-697878 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:10-698097 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:10-699119 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:10-699788 cadet-con-8620 DEBUG Connection HS92G30M (->KNAS) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:44:10-701237 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:10-702410 util-scheduler-8620 DEBUG Adding task: 138 / 0x4d61c30
Jul 07 20:44:10-703421 cadet-p2p-8620 DEBUG adding path [2] to peer KNAS
Jul 07 20:44:10-703624 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:10-704726 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:10-705390 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:10-706006 util-scheduler-8620 DEBUG Adding task: 139 / 0x4d61c30
Jul 07 20:44:10-706254 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:44:10-706804 cadet-con-8620 DEBUG Connection HS92G30M (->KNAS) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:44:10-708688 cadet-con-8620 INFO ===> {           BCK ACK} on connection HS92G30M (->KNAS)
Jul 07 20:44:10-709282 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:10-709499 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:10-710143 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 36)
Jul 07 20:44:10-710347 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:10-710576 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:10-710769 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:10-710946 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:10-712308 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:10-712832 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:10-713015 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:10-713230 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:10-713475 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on HS92G30M (->KNAS)
Jul 07 20:44:10-713659 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:10-713836 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:10-714074 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:10-714254 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:10-714432 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:10-714633 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:10-716212 cadet-tun-8620 DEBUG Tunnel KNAS cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:44:10-717426 cadet-tun-8620 DEBUG   cstate triggered rekey
Jul 07 20:44:10-718969 cadet-tun-8620 INFO Re-key Tunnel KNAS
Jul 07 20:44:10-720533 cadet-tun-8620 INFO   new kx ctx for KNAS
Jul 07 20:44:10-985980 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:44:10-987284 cadet-tun-8620 INFO PE: 00000000
Jul 07 20:44:10-988414 cadet-tun-8620 INFO KM: SY1Y2DBY
Jul 07 20:44:10-989554 cadet-tun-8620 INFO EK: 10W8HCSN
Jul 07 20:44:10-990673 cadet-tun-8620 INFO DK: V6C9J8GN
Jul 07 20:44:10-992274 cadet-tun-8620 INFO ===> EPHM for KNAS
Jul 07 20:44:10-994274 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:10-996470 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:10-998111 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:10-999876 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:11-001335 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:11-006995 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (196 bytes)
Jul 07 20:44:11-009181 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:11-009947 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:11-010166 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:11-010936 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 196)
Jul 07 20:44:11-011145 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:11-011385 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:11-011572 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:11-011755 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:11-012122 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:11-012335 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:11-012516 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:11-012722 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:11-012967 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-013170 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:11-013370 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:11-013610 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-013792 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:11-013967 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:11-014202 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-014395 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:11-014572 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:11-014774 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:11-018751 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:11-019222 util-scheduler-8620 DEBUG Adding task: 140 / 0x4d61838
Jul 07 20:44:11-020857 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:11-021087 util-scheduler-8620 DEBUG Adding task: 141 / 0x46620a0
Jul 07 20:44:11-021401 util-scheduler-8620 DEBUG Checking readiness of task: 141 / 0x46620a0
Jul 07 20:44:11-021602 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-021797 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-021989 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-022180 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-022372 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-022563 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-022753 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-022947 util-scheduler-8620 DEBUG Running task: 79 / 0x4d73060
Jul 07 20:44:11-023836 util-scheduler-8620 DEBUG Running task: 70 / 0x4d6fa48
Jul 07 20:44:11-024042 util-scheduler-8620 DEBUG Running task: 64 / 0x4d6e518
Jul 07 20:44:11-024243 util-scheduler-8620 DEBUG Running task: 56 / 0x4d6c380
Jul 07 20:44:11-330533 util-scheduler-8620 DEBUG Checking readiness of task: 141 / 0x46620a0
Jul 07 20:44:11-330926 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-331122 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-331330 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-331521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-331714 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-331904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-332116 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-332325 util-scheduler-8620 DEBUG Running task: 141 / 0x46620a0
Jul 07 20:44:11-332754 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:11-333024 util-scheduler-8620 DEBUG Adding task: 142 / 0x4662248
Jul 07 20:44:11-333345 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-333543 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-333737 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-333928 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-334122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-334314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-334506 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-334699 util-scheduler-8620 DEBUG Running task: 142 / 0x4662248
Jul 07 20:44:11-334891 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:11-335121 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:11-335355 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:11-335562 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-335770 util-scheduler-8620 DEBUG Adding task: 143 / 0x46620a0
Jul 07 20:44:11-335958 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:11-336163 util-scheduler-8620 DEBUG Adding task: 144 / 0x46620a0
Jul 07 20:44:11-336410 util-scheduler-8620 DEBUG Checking readiness of task: 144 / 0x46620a0
Jul 07 20:44:11-336613 util-scheduler-8620 DEBUG Checking readiness of task: 143 / 0x46620a0
Jul 07 20:44:11-336804 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-336993 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-337180 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-337980 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-338173 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-338363 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-338552 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-338991 util-scheduler-8620 DEBUG Running task: 143 / 0x46620a0
Jul 07 20:44:11-339194 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-339375 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-339549 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-339738 util-scheduler-8620 DEBUG Canceling task: 128 / 0x4d5c9e8
Jul 07 20:44:11-339967 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:44:11-340268 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 100)
Jul 07 20:44:11-340508 cadet-p2p-8620 DEBUG Checking 0x4d84608 towards HS92G30M (->KNAS)
Jul 07 20:44:11-340742 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:11-340919 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:11-341090 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:11-341280 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:11-341461 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:11-341732 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:44:11-342265 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:11-342455 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:11-342646 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:11-342829 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:11-343448 util-scheduler-8620 DEBUG Canceling task: 139 / 0x4d61c30
Jul 07 20:44:11-343896 util-scheduler-8620 DEBUG Adding task: 145 / 0x4d61c30
Jul 07 20:44:11-346341 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:11-346650 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:11-347894 cadet-p2p-8620 DEBUG Checking 0x4d89518 towards HS92G30M (->KNAS)
Jul 07 20:44:11-348170 cadet-p2p-8620 DEBUG Checking 0x4d89518 towards HS92G30M (->KNAS)
Jul 07 20:44:11-349170 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:11-350451 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `KNAS'
Jul 07 20:44:11-350716 util-scheduler-8620 DEBUG Adding task: 146 / 0x4d5c9e8
Jul 07 20:44:11-350910 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:11-351518 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:11-351747 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:11-351929 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:11-352111 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:11-352365 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-352661 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:11-352843 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:11-353081 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-353298 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:11-353503 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:11-353704 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:11-353912 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:44:11-354920 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:11-355144 util-scheduler-8620 DEBUG Adding task: 147 / 0x4d5c9e8
Jul 07 20:44:11-355381 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:11-355585 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-355794 util-scheduler-8620 DEBUG Adding task: 148 / 0x46620a0
Jul 07 20:44:11-355998 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:11-357140 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:11-357370 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:11-357640 util-scheduler-8620 DEBUG Checking readiness of task: 148 / 0x46620a0
Jul 07 20:44:11-357836 util-scheduler-8620 DEBUG Checking readiness of task: 144 / 0x46620a0
Jul 07 20:44:11-358097 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-358288 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-358478 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-358667 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-358866 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-359055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-359244 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-359437 util-scheduler-8620 DEBUG Running task: 148 / 0x46620a0
Jul 07 20:44:11-359624 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-359805 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-360023 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-360204 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:11-360405 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:11-360592 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:11-360891 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:11-361099 util-scheduler-8620 DEBUG Running task: 146 / 0x4d5c9e8
Jul 07 20:44:11-361530 util-scheduler-8620 DEBUG Canceling task: 147 / 0x4d5c9e8
Jul 07 20:44:11-361932 util-scheduler-8620 DEBUG Adding task: 149 / 0x4d5c9e8
Jul 07 20:44:11-362157 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:11-362354 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-362553 util-scheduler-8620 DEBUG Adding task: 150 / 0x46620a0
Jul 07 20:44:11-362834 util-scheduler-8620 DEBUG Checking readiness of task: 150 / 0x46620a0
Jul 07 20:44:11-363025 util-scheduler-8620 DEBUG Checking readiness of task: 144 / 0x46620a0
Jul 07 20:44:11-363216 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-363409 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-363601 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-363791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-363986 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-364183 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-364378 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-364576 util-scheduler-8620 DEBUG Running task: 144 / 0x46620a0
Jul 07 20:44:11-364995 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:11-365294 util-scheduler-8620 DEBUG Adding task: 151 / 0x4662248
Jul 07 20:44:11-365518 util-scheduler-8620 DEBUG Running task: 150 / 0x46620a0
Jul 07 20:44:11-365708 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-365892 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-366064 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-366245 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:11-366445 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:11-367263 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:11-367659 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:11-367939 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-368134 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-368323 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-368512 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-368701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-368889 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-369089 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-369301 util-scheduler-8620 DEBUG Running task: 151 / 0x4662248
Jul 07 20:44:11-369492 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:11-369690 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:11-369916 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:11-370292 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:11-370510 util-scheduler-8620 DEBUG Adding task: 152 / 0x46620a0
Jul 07 20:44:11-370771 util-scheduler-8620 DEBUG Checking readiness of task: 152 / 0x46620a0
Jul 07 20:44:11-370963 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-371152 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-371340 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-371529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-371721 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-371910 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-372098 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-372288 util-scheduler-8620 DEBUG Running task: 152 / 0x46620a0
Jul 07 20:44:11-372690 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:11-372919 util-scheduler-8620 DEBUG Adding task: 153 / 0x4662248
Jul 07 20:44:11-373166 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-373377 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-373567 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-373756 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-373944 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-374133 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-374321 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-374509 util-scheduler-8620 DEBUG Running task: 153 / 0x4662248
Jul 07 20:44:11-374697 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:11-374888 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:11-375097 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:11-375319 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-375518 util-scheduler-8620 DEBUG Adding task: 154 / 0x46620a0
Jul 07 20:44:11-375702 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:11-375898 util-scheduler-8620 DEBUG Adding task: 155 / 0x46620a0
Jul 07 20:44:11-376135 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:11-376325 util-scheduler-8620 DEBUG Checking readiness of task: 154 / 0x46620a0
Jul 07 20:44:11-376515 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-376704 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-376892 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-377080 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-377288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-377476 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-377665 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-377854 util-scheduler-8620 DEBUG Running task: 154 / 0x46620a0
Jul 07 20:44:11-378039 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-378215 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-378386 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-379019 util-scheduler-8620 DEBUG Canceling task: 149 / 0x4d5c9e8
Jul 07 20:44:11-379274 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 36 bytes.
Jul 07 20:44:11-379498 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 100)
Jul 07 20:44:11-379740 cadet-p2p-8620 DEBUG Checking 0x4d89518 towards HS92G30M (->KNAS)
Jul 07 20:44:11-380402 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:11-380586 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:11-381663 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:11-383379 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:11-385022 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:11-385524 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 36)
Jul 07 20:44:11-385725 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:11-385908 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:11-386097 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:11-386278 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:11-386537 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:11-386765 cadet-p2p-8620 DEBUG Checking 0x4e074b8 towards HS92G30M (->KNAS)
Jul 07 20:44:11-387003 cadet-p2p-8620 DEBUG Checking 0x4e074b8 towards HS92G30M (->KNAS)
Jul 07 20:44:11-387274 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:11-387486 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `KNAS'
Jul 07 20:44:11-387711 util-scheduler-8620 DEBUG Adding task: 156 / 0x4d5c9e8
Jul 07 20:44:11-387891 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:11-388068 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:11-388267 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:11-388441 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:11-388615 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:11-388854 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:11-389048 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:11-389258 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:11-389459 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:11-389664 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 36 bytes.
Jul 07 20:44:11-389846 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:11-390050 util-scheduler-8620 DEBUG Adding task: 157 / 0x4d5c9e8
Jul 07 20:44:11-390267 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:11-390465 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-390691 util-scheduler-8620 DEBUG Adding task: 158 / 0x46620a0
Jul 07 20:44:11-390892 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:11-391976 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:11-392179 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:11-392445 util-scheduler-8620 DEBUG Checking readiness of task: 158 / 0x46620a0
Jul 07 20:44:11-392643 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:11-392835 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-393026 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-393241 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-393442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-393635 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-393827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-394018 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-394213 util-scheduler-8620 DEBUG Running task: 158 / 0x46620a0
Jul 07 20:44:11-394410 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-394597 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-394769 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-394947 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:11-395162 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:11-395351 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:11-395585 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:11-395791 util-scheduler-8620 DEBUG Running task: 156 / 0x4d5c9e8
Jul 07 20:44:11-396021 util-scheduler-8620 DEBUG Canceling task: 157 / 0x4d5c9e8
Jul 07 20:44:11-396244 util-scheduler-8620 DEBUG Adding task: 159 / 0x4d5c9e8
Jul 07 20:44:11-396465 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:11-396662 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:11-397103 util-scheduler-8620 DEBUG Adding task: 160 / 0x46620a0
Jul 07 20:44:11-397385 util-scheduler-8620 DEBUG Checking readiness of task: 160 / 0x46620a0
Jul 07 20:44:11-397579 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:11-397768 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:11-397957 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:11-398145 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:11-398333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:11-398521 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:11-398709 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:11-398897 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:11-399087 util-scheduler-8620 DEBUG Running task: 160 / 0x46620a0
Jul 07 20:44:11-399270 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:11-399445 util-8620 DEBUG process_notify is running
Jul 07 20:44:11-399613 util-8620 DEBUG client_notify is running
Jul 07 20:44:11-399789 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:11-399979 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:11-400166 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:11-400448 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:12-672408 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:12-672884 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-673105 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-673357 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-673597 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-673868 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-674116 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-674364 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-674628 util-scheduler-8620 DEBUG Running task: 136 / 0x4d707d0
Jul 07 20:44:12-674903 cadet-con-8620 DEBUG FWD keepalive for CMHCKRVP (->V8XX)
Jul 07 20:44:12-675080 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:12-675362 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection CMHCKRVP (->V8XX)  (100 bytes)
Jul 07 20:44:12-675610 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0 (create)
Jul 07 20:44:12-675912 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:12-676302 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:12-676717 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:44:12-676933 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:12-677159 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:12-677387 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:12-677564 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:12-677774 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:44:12-677989 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:44:12-678215 util-scheduler-8620 DEBUG Adding task: 161 / 0x4d6ff98
Jul 07 20:44:12-678395 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:12-678599 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:12-678774 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:12-678950 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:12-679188 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:12-679370 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:12-679546 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:12-679746 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:12-680006 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:12-680197 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-680386 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-680575 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-680763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-680951 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-681139 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-681430 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-681621 util-scheduler-8620 DEBUG Running task: 161 / 0x4d6ff98
Jul 07 20:44:12-681831 util-scheduler-8620 DEBUG Adding task: 162 / 0x4d6ff98
Jul 07 20:44:12-682057 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:12-682259 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:12-682466 util-scheduler-8620 DEBUG Adding task: 163 / 0x46620a0
Jul 07 20:44:12-682706 util-scheduler-8620 DEBUG Checking readiness of task: 163 / 0x46620a0
Jul 07 20:44:12-682898 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:12-683086 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-683275 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-683465 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-683682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-683875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-684065 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-684267 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-684466 util-scheduler-8620 DEBUG Running task: 163 / 0x46620a0
Jul 07 20:44:12-684658 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:12-684844 util-8620 DEBUG process_notify is running
Jul 07 20:44:12-685023 util-8620 DEBUG client_notify is running
Jul 07 20:44:12-685233 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:12-685446 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:12-685643 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:12-685989 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:12-752026 util-scheduler-8620 DEBUG Checking readiness of task: 155 / 0x46620a0
Jul 07 20:44:12-752403 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-752611 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-752806 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-753026 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-753242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-753435 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-753627 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-753823 util-scheduler-8620 DEBUG Running task: 155 / 0x46620a0
Jul 07 20:44:12-754246 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:12-754507 util-scheduler-8620 DEBUG Adding task: 164 / 0x4662248
Jul 07 20:44:12-754790 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-754983 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-755173 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-755362 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-755551 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-755739 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-755928 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-756117 util-scheduler-8620 DEBUG Running task: 164 / 0x4662248
Jul 07 20:44:12-756321 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:12-756520 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:12-756749 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:12-756955 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:12-757160 util-scheduler-8620 DEBUG Adding task: 165 / 0x46620a0
Jul 07 20:44:12-757523 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:12-757745 util-scheduler-8620 DEBUG Adding task: 166 / 0x46620a0
Jul 07 20:44:12-757989 util-scheduler-8620 DEBUG Checking readiness of task: 166 / 0x46620a0
Jul 07 20:44:12-758179 util-scheduler-8620 DEBUG Checking readiness of task: 165 / 0x46620a0
Jul 07 20:44:12-758370 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-758558 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-758746 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-758934 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-759122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-759357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-759547 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-759737 util-scheduler-8620 DEBUG Running task: 165 / 0x46620a0
Jul 07 20:44:12-759922 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:12-760115 util-8620 DEBUG process_notify is running
Jul 07 20:44:12-760287 util-8620 DEBUG client_notify is running
Jul 07 20:44:12-760474 util-scheduler-8620 DEBUG Canceling task: 159 / 0x4d5c9e8
Jul 07 20:44:12-760699 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 196 bytes.
Jul 07 20:44:12-760918 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:12-761157 cadet-p2p-8620 DEBUG Checking 0x4e074b8 towards HS92G30M (->KNAS)
Jul 07 20:44:12-761448 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:12-761626 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:12-763078 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:12-764590 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 196)
Jul 07 20:44:12-764794 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:12-764979 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:12-765168 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:12-765857 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:12-766430 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:12-766646 util-scheduler-8620 DEBUG Canceling task: 145 / 0x4d61c30
Jul 07 20:44:12-766884 util-scheduler-8620 DEBUG Adding task: 167 / 0x4d61c30
Jul 07 20:44:12-767151 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:12-767429 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:12-767628 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:12-767846 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:12-768028 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:12-768209 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:12-768422 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:12-768635 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 196 bytes.
Jul 07 20:44:12-768823 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:12-769005 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:12-769234 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:12-770594 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:12-786260 util-scheduler-8620 DEBUG Checking readiness of task: 166 / 0x46620a0
Jul 07 20:44:12-786555 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:12-786750 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:12-786942 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:12-787132 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:12-787323 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:12-787513 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:12-787703 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:12-787895 util-scheduler-8620 DEBUG Running task: 84 / 0x4d744e8
Jul 07 20:44:13-761449 util-scheduler-8620 DEBUG Checking readiness of task: 166 / 0x46620a0
Jul 07 20:44:13-761839 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:13-762035 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:13-762228 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:13-762419 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:13-762609 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:13-762799 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:13-763022 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:13-763219 util-scheduler-8620 DEBUG Running task: 166 / 0x46620a0
Jul 07 20:44:13-763642 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:13-763981 util-scheduler-8620 DEBUG Adding task: 168 / 0x4662248
Jul 07 20:44:13-764265 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:13-764457 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:13-764648 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:13-764840 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:13-765030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:13-765244 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:13-765435 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:13-765625 util-scheduler-8620 DEBUG Running task: 168 / 0x4662248
Jul 07 20:44:13-765817 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:13-766015 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:13-766244 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:13-766472 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:13-766681 util-scheduler-8620 DEBUG Adding task: 169 / 0x46620a0
Jul 07 20:44:13-766868 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:13-767074 util-scheduler-8620 DEBUG Adding task: 170 / 0x46620a0
Jul 07 20:44:13-767318 util-scheduler-8620 DEBUG Checking readiness of task: 170 / 0x46620a0
Jul 07 20:44:13-767508 util-scheduler-8620 DEBUG Checking readiness of task: 169 / 0x46620a0
Jul 07 20:44:13-767699 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:13-767888 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:13-768077 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:13-768266 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:13-768454 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:13-768643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:13-768832 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:13-769023 util-scheduler-8620 DEBUG Running task: 169 / 0x46620a0
Jul 07 20:44:13-769232 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:13-769412 util-8620 DEBUG process_notify is running
Jul 07 20:44:13-769585 util-8620 DEBUG client_notify is running
Jul 07 20:44:13-769772 util-scheduler-8620 DEBUG Canceling task: 131 / 0x4d683b0
Jul 07 20:44:13-769995 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:13-770215 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:44:13-770456 cadet-p2p-8620 DEBUG Checking 0x4d85d10 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:13-770690 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:13-770868 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:13-771038 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:13-771258 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:13-771440 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:13-771707 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:13-771901 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:13-772081 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:13-772268 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:13-772449 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:13-772658 util-scheduler-8620 DEBUG Adding task: 171 / 0x4d68be8
Jul 07 20:44:13-772897 cadet-con-8620 DEBUG next keepalive in 4 s
Jul 07 20:44:13-773085 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:13-773305 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:13-773507 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:13-773681 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:13-773856 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:13-774055 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:13-774260 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:13-774443 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:13-774622 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:13-774816 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:13-775609 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:14-675698 util-scheduler-8620 DEBUG Checking readiness of task: 170 / 0x46620a0
Jul 07 20:44:14-676082 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:14-676301 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:14-676493 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:14-676685 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:14-676876 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:14-677067 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:14-677290 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:14-677487 util-scheduler-8620 DEBUG Running task: 170 / 0x46620a0
Jul 07 20:44:14-677919 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:14-678176 util-scheduler-8620 DEBUG Adding task: 172 / 0x4662248
Jul 07 20:44:14-678457 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:14-678651 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:14-678842 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:14-679031 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:14-679220 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:14-679409 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:14-679598 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:14-679789 util-scheduler-8620 DEBUG Running task: 172 / 0x4662248
Jul 07 20:44:14-679980 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:14-680179 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:14-680595 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `KNAS'
Jul 07 20:44:14-681041 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection HS92G30M from KNAS
Jul 07 20:44:14-681452 cadet-con-8620 DEBUG   via peer KNAS
Jul 07 20:44:14-681700 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:14-681911 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:14-682187 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:14-682609 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:14-682972 util-scheduler-8620 DEBUG Canceling task: 138 / 0x4d61c30
Jul 07 20:44:14-683697 util-scheduler-8620 DEBUG Adding task: 173 / 0x4d61c30
Jul 07 20:44:14-683955 cadet-p2p-8620 DEBUG adding path [2] to peer KNAS
Jul 07 20:44:14-684138 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:14-684423 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:14-684953 cadet-con-8620 DEBUG Connection HS92G30M (->KNAS) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:44:14-685378 cadet-con-8620 INFO ===> {           BCK ACK} on connection HS92G30M (->KNAS)
Jul 07 20:44:14-685620 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:14-685857 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:14-686155 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 36)
Jul 07 20:44:14-686353 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:14-686579 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:14-686775 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:14-686951 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:14-687158 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 36 bytes
Jul 07 20:44:14-687374 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `KNAS'
Jul 07 20:44:14-687589 util-scheduler-8620 DEBUG Adding task: 174 / 0x4d5c9e8
Jul 07 20:44:14-687771 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:14-687975 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:14-688150 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:14-688325 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:14-688564 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:14-688747 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:14-688923 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:14-689121 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:14-689548 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:14-689770 util-scheduler-8620 DEBUG Adding task: 175 / 0x46620a0
Jul 07 20:44:14-690020 util-scheduler-8620 DEBUG Checking readiness of task: 175 / 0x46620a0
Jul 07 20:44:14-690214 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:14-690404 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:14-690593 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:14-690782 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:14-690971 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:14-691160 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:14-691348 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:14-691538 util-scheduler-8620 DEBUG Running task: 174 / 0x4d5c9e8
Jul 07 20:44:14-691746 util-scheduler-8620 DEBUG Adding task: 176 / 0x4d5c9e8
Jul 07 20:44:14-691972 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:14-692175 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:14-692378 util-scheduler-8620 DEBUG Adding task: 177 / 0x46620a0
Jul 07 20:44:14-692620 util-scheduler-8620 DEBUG Checking readiness of task: 177 / 0x46620a0
Jul 07 20:44:14-692813 util-scheduler-8620 DEBUG Checking readiness of task: 175 / 0x46620a0
Jul 07 20:44:14-693003 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:14-693216 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:14-693408 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:14-693596 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:14-693785 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:14-693975 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:14-694165 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:14-694356 util-scheduler-8620 DEBUG Running task: 177 / 0x46620a0
Jul 07 20:44:14-694541 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:14-694720 util-8620 DEBUG process_notify is running
Jul 07 20:44:14-694892 util-8620 DEBUG client_notify is running
Jul 07 20:44:14-695075 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:14-695283 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:14-695474 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:14-695838 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:15-579065 util-scheduler-8620 DEBUG Checking readiness of task: 175 / 0x46620a0
Jul 07 20:44:15-579503 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:15-579708 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:15-579907 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:15-580109 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:15-580301 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:15-580492 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:15-580689 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:15-580902 util-scheduler-8620 DEBUG Running task: 175 / 0x46620a0
Jul 07 20:44:15-581367 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:15-581645 util-scheduler-8620 DEBUG Adding task: 178 / 0x4662248
Jul 07 20:44:15-581932 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:15-582127 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:15-582319 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:15-582510 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:15-582700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:15-582891 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:15-583083 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:15-583274 util-scheduler-8620 DEBUG Running task: 178 / 0x4662248
Jul 07 20:44:15-583467 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:15-583671 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:15-583906 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:15-584116 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:15-584324 util-scheduler-8620 DEBUG Adding task: 179 / 0x46620a0
Jul 07 20:44:15-584538 util-scheduler-8620 DEBUG Adding task: 180 / 0x4662248
Jul 07 20:44:15-584780 util-scheduler-8620 DEBUG Checking readiness of task: 179 / 0x46620a0
Jul 07 20:44:15-584974 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:15-585166 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:15-585380 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:15-585569 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:15-585758 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:15-585947 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:15-586135 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:15-586326 util-scheduler-8620 DEBUG Running task: 179 / 0x46620a0
Jul 07 20:44:15-586510 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:15-586688 util-8620 DEBUG process_notify is running
Jul 07 20:44:15-586859 util-8620 DEBUG client_notify is running
Jul 07 20:44:15-587047 util-scheduler-8620 DEBUG Canceling task: 176 / 0x4d5c9e8
Jul 07 20:44:15-587273 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 36 bytes.
Jul 07 20:44:15-587495 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:15-587734 cadet-p2p-8620 DEBUG Checking 0x4e130c0 towards HS92G30M (->KNAS)
Jul 07 20:44:15-587966 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:15-589357 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:15-590130 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:15-590846 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:15-591533 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:15-592215 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 36)
Jul 07 20:44:15-592795 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:15-592982 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:15-593575 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:15-593762 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:15-594320 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:15-594507 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:15-595092 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:15-595647 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:15-595828 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:15-596408 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:15-596618 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 36 bytes.
Jul 07 20:44:15-597181 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:15-597759 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:15-597957 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:15-599731 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:15-600338 util-scheduler-8620 DEBUG Running task: 180 / 0x4662248
Jul 07 20:44:15-600914 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:15-601128 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:15-601790 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:15-602427 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:15-603121 util-scheduler-8620 DEBUG Adding task: 181 / 0x46620a0
Jul 07 20:44:15-603800 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:15-604459 util-scheduler-8620 DEBUG Adding task: 182 / 0x46620a0
Jul 07 20:44:15-605239 util-scheduler-8620 DEBUG Checking readiness of task: 182 / 0x46620a0
Jul 07 20:44:15-605889 util-scheduler-8620 DEBUG Checking readiness of task: 181 / 0x46620a0
Jul 07 20:44:15-606109 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:15-606725 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:15-606927 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:15-607121 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:15-607312 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:15-607503 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:15-607759 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:15-607965 util-scheduler-8620 DEBUG Running task: 181 / 0x46620a0
Jul 07 20:44:15-608155 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:15-608335 util-8620 DEBUG process_notify is running
Jul 07 20:44:15-608509 util-8620 DEBUG client_notify is running
Jul 07 20:44:15-608697 util-scheduler-8620 DEBUG Canceling task: 162 / 0x4d6ff98
Jul 07 20:44:15-608938 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:44:15-609157 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:15-609444 cadet-p2p-8620 DEBUG Checking 0x4e0e0b0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:15-609679 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:15-609856 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:15-610025 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:15-610194 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:15-610374 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:15-610657 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:44:15-610850 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:15-611028 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:15-611241 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:15-611422 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:15-611670 util-scheduler-8620 DEBUG Adding task: 183 / 0x4d707d0
Jul 07 20:44:15-611912 cadet-con-8620 DEBUG next keepalive in 4 s
Jul 07 20:44:15-612082 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:15-612261 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:15-612461 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:15-612635 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:15-612812 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:15-613010 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:15-613234 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:44:15-613418 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:15-613597 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:15-613787 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:15-614514 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:16-019793 util-scheduler-8620 DEBUG Checking readiness of task: 182 / 0x46620a0
Jul 07 20:44:16-020185 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:16-020383 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:16-020577 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:16-020786 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:16-020979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:16-021171 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:16-021393 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:16-021589 util-scheduler-8620 DEBUG Running task: 140 / 0x4d61838
Jul 07 20:44:16-022409 cadet-tun-8620 INFO Re-key Tunnel KNAS
Jul 07 20:44:16-024190 cadet-tun-8620 DEBUG  kx started 5 s ago
Jul 07 20:44:16-025143 cadet-tun-8620 INFO ===> EPHM for KNAS
Jul 07 20:44:16-025533 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:16-025898 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:16-026301 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:16-026642 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:16-027026 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:16-027481 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (196 bytes)
Jul 07 20:44:16-027841 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:16-028093 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:16-028318 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:16-028640 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 196)
Jul 07 20:44:16-028846 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:16-029075 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:16-029351 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:16-029534 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:16-029746 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 196 bytes
Jul 07 20:44:16-029966 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `KNAS'
Jul 07 20:44:16-030196 util-scheduler-8620 DEBUG Adding task: 184 / 0x4d5c9e8
Jul 07 20:44:16-030380 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:16-030588 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:16-030767 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:16-030944 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:16-031186 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:16-031384 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:16-031593 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:16-031796 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:16-032413 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:16-032623 util-scheduler-8620 DEBUG Adding task: 185 / 0x4d61838
Jul 07 20:44:16-032901 util-scheduler-8620 DEBUG Checking readiness of task: 182 / 0x46620a0
Jul 07 20:44:16-033097 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:16-033315 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:16-033507 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:16-033699 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:16-033890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:16-034081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:16-034272 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:16-034465 util-scheduler-8620 DEBUG Running task: 184 / 0x4d5c9e8
Jul 07 20:44:16-034676 util-scheduler-8620 DEBUG Adding task: 186 / 0x4d5c9e8
Jul 07 20:44:16-034901 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:16-035107 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:16-035318 util-scheduler-8620 DEBUG Adding task: 187 / 0x46620a0
Jul 07 20:44:16-035562 util-scheduler-8620 DEBUG Checking readiness of task: 187 / 0x46620a0
Jul 07 20:44:16-035757 util-scheduler-8620 DEBUG Checking readiness of task: 182 / 0x46620a0
Jul 07 20:44:16-035949 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:16-036141 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:16-036341 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:16-036622 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:16-036815 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:16-037008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:16-037222 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:16-037419 util-scheduler-8620 DEBUG Running task: 187 / 0x46620a0
Jul 07 20:44:16-037606 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:16-037787 util-8620 DEBUG process_notify is running
Jul 07 20:44:16-037962 util-8620 DEBUG client_notify is running
Jul 07 20:44:16-038143 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:16-038342 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:16-038535 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:16-038858 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:16-833934 util-scheduler-8620 DEBUG Checking readiness of task: 182 / 0x46620a0
Jul 07 20:44:16-834321 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:16-834518 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:16-834710 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:16-834901 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:16-835092 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:16-835284 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:16-835474 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:16-835672 util-scheduler-8620 DEBUG Running task: 182 / 0x46620a0
Jul 07 20:44:16-836095 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:16-836354 util-scheduler-8620 DEBUG Adding task: 188 / 0x4662248
Jul 07 20:44:16-836632 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:16-836853 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:16-837045 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:16-837263 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:16-837455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:16-837646 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:16-837835 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:16-838024 util-scheduler-8620 DEBUG Running task: 188 / 0x4662248
Jul 07 20:44:16-838216 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:44:16-838416 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:44:16-838648 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `KNAS'
Jul 07 20:44:16-839395 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:16-841840 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:16-842327 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:16-842548 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:16-844436 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:16-844655 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:16-845496 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:16-845703 util-scheduler-8620 DEBUG Canceling task: 173 / 0x4d61c30
Jul 07 20:44:16-845934 util-scheduler-8620 DEBUG Adding task: 189 / 0x4d61c30
Jul 07 20:44:16-846941 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:16-847476 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:16-847700 util-scheduler-8620 DEBUG Adding task: 190 / 0x4d5e5d8
Jul 07 20:44:16-849145 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:16-850655 cadet-tun-8620 INFO <=== EPHM for KNAS
Jul 07 20:44:17-721296 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:44:17-723400 cadet-tun-8620 INFO PE: HV5QVJX5
Jul 07 20:44:17-723879 cadet-tun-8620 INFO KM: SQ65DHN1
Jul 07 20:44:17-724228 cadet-tun-8620 INFO EK: 8G0G7MY3
Jul 07 20:44:17-724586 cadet-tun-8620 INFO DK: 7VEEVN5W
Jul 07 20:44:17-725822 cadet-tun-8620 DEBUG   our key was sent, sending ping
Jul 07 20:44:17-727267 cadet-tun-8620 INFO ===> PING for KNAS
Jul 07 20:44:17-729336 cadet-tun-8620 DEBUG   sending 1463304033
Jul 07 20:44:17-730652 cadet-tun-8620 DEBUG   towards KNAS
Jul 07 20:44:17-731939 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:17-733155 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:17-742519 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:18-166539 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:18-167913 cadet-tun-8620 DEBUG   e sending 913452840
Jul 07 20:44:18-169045 cadet-tun-8620 DEBUG   e towards 3QDV
Jul 07 20:44:18-169875 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:18-170088 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:18-170326 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:18-170509 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:18-170746 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:18-171281 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (80 bytes)
Jul 07 20:44:18-171487 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:18-171729 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:18-171939 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:18-172256 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 80)
Jul 07 20:44:18-172457 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:18-172684 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:18-172868 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:18-173045 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:18-173321 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:18-173527 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:18-173704 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:18-173880 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:18-174129 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-174326 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:18-174509 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:18-174745 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-174939 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:18-175116 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:18-175314 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:18-176113 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:18-176347 util-scheduler-8620 DEBUG Adding task: 191 / 0x46620a0
Jul 07 20:44:18-176639 util-scheduler-8620 DEBUG Checking readiness of task: 191 / 0x46620a0
Jul 07 20:44:18-176839 util-scheduler-8620 DEBUG Checking readiness of task: 190 / 0x4d5e5d8
Jul 07 20:44:18-177032 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-177246 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-177439 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-177629 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-177819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-178008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-178197 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-178393 util-scheduler-8620 DEBUG Running task: 190 / 0x4d5e5d8
Jul 07 20:44:18-178580 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:18-178775 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-178984 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-179261 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:18-179688 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:18-179964 util-scheduler-8620 DEBUG Running task: 191 / 0x46620a0
Jul 07 20:44:18-180376 util-8620 DEBUG receive_ready read 156/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:18-180621 util-scheduler-8620 DEBUG Adding task: 192 / 0x4662248
Jul 07 20:44:18-180832 util-scheduler-8620 DEBUG Running task: 171 / 0x4d68be8
Jul 07 20:44:18-181072 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:44:18-181281 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:18-181525 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:18-181714 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:18-181946 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:18-182153 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:18-182447 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:18-182646 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:18-182869 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:18-183052 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:18-183227 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:18-183433 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:18-183660 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:18-183873 util-scheduler-8620 DEBUG Adding task: 193 / 0x4d683b0
Jul 07 20:44:18-184053 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:18-184257 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:18-184450 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:18-184626 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:18-184864 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:18-185047 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:18-185244 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:18-185445 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:18-185685 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-185880 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-186071 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-186260 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-186449 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-186638 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-186827 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-187015 util-scheduler-8620 DEBUG Running task: 193 / 0x4d683b0
Jul 07 20:44:18-187222 util-scheduler-8620 DEBUG Adding task: 194 / 0x4d683b0
Jul 07 20:44:18-187443 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:18-187647 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-187852 util-scheduler-8620 DEBUG Adding task: 195 / 0x46620a0
Jul 07 20:44:18-188050 util-scheduler-8620 DEBUG Running task: 192 / 0x4662248
Jul 07 20:44:18-188241 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:44:18-188441 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:44:18-188658 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `KNAS'
Jul 07 20:44:18-188909 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:18-189280 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:18-189517 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:18-189727 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:18-189973 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:18-190180 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:18-190367 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:18-190555 util-scheduler-8620 DEBUG Canceling task: 189 / 0x4d61c30
Jul 07 20:44:18-190775 util-scheduler-8620 DEBUG Adding task: 196 / 0x4d61c30
Jul 07 20:44:18-191059 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:18-191315 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:18-191523 util-scheduler-8620 DEBUG Adding task: 197 / 0x4d5e5d8
Jul 07 20:44:18-191867 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:18-193320 cadet-tun-8620 INFO <=== PING for KNAS
Jul 07 20:44:18-194970 cadet-tun-8620 DEBUG   t_decrypt with 7VEEVN5W
Jul 07 20:44:18-196457 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:18-197416 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:18-202703 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:18-214140 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:18-216541 cadet-tun-8620 INFO ===> PONG for KNAS
Jul 07 20:44:18-217976 cadet-tun-8620 DEBUG   sending 2249405204
Jul 07 20:44:18-218746 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:18-219096 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:18-222528 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:18-223335 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:18-224404 cadet-tun-8620 DEBUG   e sending 3056165659
Jul 07 20:44:18-225230 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:18-225443 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:18-225677 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:18-225861 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:18-226083 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:18-226607 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (48 bytes)
Jul 07 20:44:18-226838 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:18-227078 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:18-227316 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:18-227660 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 48)
Jul 07 20:44:18-227860 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:18-228102 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:18-228287 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:18-228463 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:18-228677 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:18-228880 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:18-229056 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:18-229261 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:18-229532 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-229730 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:18-229909 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:18-230145 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-230338 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:18-230514 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:18-230746 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-230938 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:18-231114 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:18-231312 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:18-231771 util-scheduler-8620 DEBUG Adding task: 198 / 0x4662248
Jul 07 20:44:18-232055 util-scheduler-8620 DEBUG Checking readiness of task: 197 / 0x4d5e5d8
Jul 07 20:44:18-232254 util-scheduler-8620 DEBUG Checking readiness of task: 195 / 0x46620a0
Jul 07 20:44:18-232445 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-232636 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-232826 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-233016 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-233225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-233418 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-233607 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-233801 util-scheduler-8620 DEBUG Running task: 195 / 0x46620a0
Jul 07 20:44:18-234472 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-234664 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-234839 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-235019 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:18-235222 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:18-235414 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:18-235733 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-235952 util-scheduler-8620 DEBUG Running task: 197 / 0x4d5e5d8
Jul 07 20:44:18-236137 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:18-236313 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-236483 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-236707 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:18-237084 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:18-237320 util-scheduler-8620 DEBUG Running task: 198 / 0x4662248
Jul 07 20:44:18-237540 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:18-237739 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:18-237962 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:18-238168 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-238376 util-scheduler-8620 DEBUG Adding task: 199 / 0x46620a0
Jul 07 20:44:18-238563 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:18-238778 util-scheduler-8620 DEBUG Adding task: 200 / 0x46620a0
Jul 07 20:44:18-239029 util-scheduler-8620 DEBUG Checking readiness of task: 200 / 0x46620a0
Jul 07 20:44:18-239221 util-scheduler-8620 DEBUG Checking readiness of task: 199 / 0x46620a0
Jul 07 20:44:18-239413 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-239602 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-239791 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-239980 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-240168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-240356 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-240545 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-240735 util-scheduler-8620 DEBUG Running task: 199 / 0x46620a0
Jul 07 20:44:18-240920 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-241094 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-241288 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-241474 util-scheduler-8620 DEBUG Canceling task: 186 / 0x4d5c9e8
Jul 07 20:44:18-241698 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 196 bytes.
Jul 07 20:44:18-241916 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:18-242151 cadet-p2p-8620 DEBUG Checking 0x4e17370 towards HS92G30M (->KNAS)
Jul 07 20:44:18-242384 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:18-242562 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:18-242864 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:18-243157 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 196)
Jul 07 20:44:18-243354 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:18-243548 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:18-243738 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:18-243927 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:18-244106 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:18-244290 util-scheduler-8620 DEBUG Canceling task: 167 / 0x4d61c30
Jul 07 20:44:18-244503 util-scheduler-8620 DEBUG Adding task: 201 / 0x4d61c30
Jul 07 20:44:18-244756 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:18-244927 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:18-245149 cadet-p2p-8620 DEBUG Checking 0x511ade0 towards HS92G30M (->KNAS)
Jul 07 20:44:18-245412 cadet-p2p-8620 DEBUG Checking 0x511ade0 towards HS92G30M (->KNAS)
Jul 07 20:44:18-245591 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:18-245798 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `KNAS'
Jul 07 20:44:18-246014 util-scheduler-8620 DEBUG Adding task: 202 / 0x4d5c9e8
Jul 07 20:44:18-246194 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:18-246371 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:18-246570 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:18-246744 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:18-246919 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:18-247156 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-247349 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:18-247526 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:18-247787 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-247981 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:18-248157 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:18-248355 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:18-248560 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 196 bytes.
Jul 07 20:44:18-248743 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:18-248946 util-scheduler-8620 DEBUG Adding task: 203 / 0x4d5c9e8
Jul 07 20:44:18-249165 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:18-249384 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-249586 util-scheduler-8620 DEBUG Adding task: 204 / 0x46620a0
Jul 07 20:44:18-249786 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:18-251110 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-251320 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:18-251575 util-scheduler-8620 DEBUG Checking readiness of task: 204 / 0x46620a0
Jul 07 20:44:18-251769 util-scheduler-8620 DEBUG Checking readiness of task: 200 / 0x46620a0
Jul 07 20:44:18-251960 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-252151 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-252341 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-252531 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-252720 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-252911 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-253101 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-253398 util-scheduler-8620 DEBUG Running task: 204 / 0x46620a0
Jul 07 20:44:18-253588 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-253766 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-253938 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-254116 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:18-254309 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:18-254498 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:18-254796 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-255004 util-scheduler-8620 DEBUG Running task: 202 / 0x4d5c9e8
Jul 07 20:44:18-255197 util-scheduler-8620 DEBUG Canceling task: 203 / 0x4d5c9e8
Jul 07 20:44:18-255413 util-scheduler-8620 DEBUG Adding task: 205 / 0x4d5c9e8
Jul 07 20:44:18-255631 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:18-255826 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-256028 util-scheduler-8620 DEBUG Adding task: 206 / 0x46620a0
Jul 07 20:44:18-256267 util-scheduler-8620 DEBUG Checking readiness of task: 206 / 0x46620a0
Jul 07 20:44:18-256459 util-scheduler-8620 DEBUG Checking readiness of task: 200 / 0x46620a0
Jul 07 20:44:18-256651 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-256840 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-257029 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-257242 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-257445 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-257635 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-257824 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-258014 util-scheduler-8620 DEBUG Running task: 200 / 0x46620a0
Jul 07 20:44:18-258438 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:18-258667 util-scheduler-8620 DEBUG Adding task: 207 / 0x4662248
Jul 07 20:44:18-258876 util-scheduler-8620 DEBUG Running task: 206 / 0x46620a0
Jul 07 20:44:18-259060 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-259236 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-259405 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-259581 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:18-259770 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:18-259976 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:18-260273 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-260521 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-260713 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-260904 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-261093 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-261306 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-261496 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-261685 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-261874 util-scheduler-8620 DEBUG Running task: 207 / 0x4662248
Jul 07 20:44:18-262064 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:18-262258 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:18-262471 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:18-262651 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:18-262851 util-scheduler-8620 DEBUG Adding task: 208 / 0x46620a0
Jul 07 20:44:18-263091 util-scheduler-8620 DEBUG Checking readiness of task: 208 / 0x46620a0
Jul 07 20:44:18-263285 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-263474 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-263663 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-263852 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-264041 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-264231 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-264419 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-264609 util-scheduler-8620 DEBUG Running task: 208 / 0x46620a0
Jul 07 20:44:18-265007 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:18-265250 util-scheduler-8620 DEBUG Adding task: 209 / 0x4662248
Jul 07 20:44:18-265497 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-265688 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-265880 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-266069 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-266351 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-266544 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-266735 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-266925 util-scheduler-8620 DEBUG Running task: 209 / 0x4662248
Jul 07 20:44:18-267113 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:18-267304 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:18-267529 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:18-267725 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-267922 util-scheduler-8620 DEBUG Adding task: 210 / 0x46620a0
Jul 07 20:44:18-268105 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:18-268310 util-scheduler-8620 DEBUG Adding task: 211 / 0x46620a0
Jul 07 20:44:18-268549 util-scheduler-8620 DEBUG Checking readiness of task: 211 / 0x46620a0
Jul 07 20:44:18-268740 util-scheduler-8620 DEBUG Checking readiness of task: 210 / 0x46620a0
Jul 07 20:44:18-268930 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-269230 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-269426 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-269616 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-269805 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-269994 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-270184 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-270375 util-scheduler-8620 DEBUG Running task: 210 / 0x46620a0
Jul 07 20:44:18-270559 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-270733 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-270903 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-271085 util-scheduler-8620 DEBUG Canceling task: 205 / 0x4d5c9e8
Jul 07 20:44:18-271303 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 80 bytes.
Jul 07 20:44:18-271518 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:18-271750 cadet-p2p-8620 DEBUG Checking 0x511ade0 towards HS92G30M (->KNAS)
Jul 07 20:44:18-271980 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:18-272158 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:44:18-272343 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:18-272618 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 80)
Jul 07 20:44:18-272812 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:18-272989 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:18-273175 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:18-273387 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:18-273564 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:18-273746 util-scheduler-8620 DEBUG Canceling task: 201 / 0x4d61c30
Jul 07 20:44:18-273955 util-scheduler-8620 DEBUG Adding task: 212 / 0x4d61c30
Jul 07 20:44:18-274197 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:18-274368 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:18-274587 cadet-p2p-8620 DEBUG Checking 0x5129048 towards HS92G30M (->KNAS)
Jul 07 20:44:18-274823 cadet-p2p-8620 DEBUG Checking 0x5129048 towards HS92G30M (->KNAS)
Jul 07 20:44:18-275001 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:18-275204 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `KNAS'
Jul 07 20:44:18-275413 util-scheduler-8620 DEBUG Adding task: 213 / 0x4d5c9e8
Jul 07 20:44:18-275591 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:18-275766 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:44:18-275966 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:18-276140 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:18-276314 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:18-276549 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:18-276742 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:18-276918 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:18-277128 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:18-277357 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 80 bytes.
Jul 07 20:44:18-277539 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:44:18-277753 util-scheduler-8620 DEBUG Adding task: 214 / 0x4d5c9e8
Jul 07 20:44:18-277967 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:18-278159 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-278358 util-scheduler-8620 DEBUG Adding task: 215 / 0x46620a0
Jul 07 20:44:18-278555 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:44:18-278894 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-279092 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:18-279331 util-scheduler-8620 DEBUG Checking readiness of task: 215 / 0x46620a0
Jul 07 20:44:18-279524 util-scheduler-8620 DEBUG Checking readiness of task: 211 / 0x46620a0
Jul 07 20:44:18-279715 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-279904 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-280094 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-280283 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-280472 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-280661 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-280850 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-281039 util-scheduler-8620 DEBUG Running task: 215 / 0x46620a0
Jul 07 20:44:18-281245 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-281422 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-281591 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-281767 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:18-281957 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:18-282144 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:18-282423 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:18-282631 util-scheduler-8620 DEBUG Running task: 213 / 0x4d5c9e8
Jul 07 20:44:18-282822 util-scheduler-8620 DEBUG Canceling task: 214 / 0x4d5c9e8
Jul 07 20:44:18-283033 util-scheduler-8620 DEBUG Adding task: 216 / 0x4d5c9e8
Jul 07 20:44:18-283248 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:18-283441 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:18-283638 util-scheduler-8620 DEBUG Adding task: 217 / 0x46620a0
Jul 07 20:44:18-283876 util-scheduler-8620 DEBUG Checking readiness of task: 217 / 0x46620a0
Jul 07 20:44:18-284068 util-scheduler-8620 DEBUG Checking readiness of task: 211 / 0x46620a0
Jul 07 20:44:18-284258 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:18-284448 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:18-284637 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:18-284826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:18-285015 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:18-285227 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:18-285418 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:18-285609 util-scheduler-8620 DEBUG Running task: 217 / 0x46620a0
Jul 07 20:44:18-285793 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:18-285982 util-8620 DEBUG process_notify is running
Jul 07 20:44:18-286150 util-8620 DEBUG client_notify is running
Jul 07 20:44:18-286326 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:18-286514 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:18-286701 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:18-286994 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:19-425012 util-scheduler-8620 DEBUG Checking readiness of task: 211 / 0x46620a0
Jul 07 20:44:19-425437 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-425634 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-425826 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-426018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-426211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-426402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-426592 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-426788 util-scheduler-8620 DEBUG Running task: 211 / 0x46620a0
Jul 07 20:44:19-427211 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:19-427467 util-scheduler-8620 DEBUG Adding task: 218 / 0x4662248
Jul 07 20:44:19-427746 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-427939 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-428129 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-428319 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-428509 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-428698 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-428888 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-429077 util-scheduler-8620 DEBUG Running task: 218 / 0x4662248
Jul 07 20:44:19-429692 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:19-429899 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:19-430134 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:19-430342 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:19-430550 util-scheduler-8620 DEBUG Adding task: 219 / 0x46620a0
Jul 07 20:44:19-430739 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:19-430946 util-scheduler-8620 DEBUG Adding task: 220 / 0x46620a0
Jul 07 20:44:19-431192 util-scheduler-8620 DEBUG Checking readiness of task: 220 / 0x46620a0
Jul 07 20:44:19-431387 util-scheduler-8620 DEBUG Checking readiness of task: 219 / 0x46620a0
Jul 07 20:44:19-431579 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-431768 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-431957 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-432146 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-432335 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-432524 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-432713 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-432904 util-scheduler-8620 DEBUG Running task: 219 / 0x46620a0
Jul 07 20:44:19-433089 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:19-433294 util-8620 DEBUG process_notify is running
Jul 07 20:44:19-433467 util-8620 DEBUG client_notify is running
Jul 07 20:44:19-433656 util-scheduler-8620 DEBUG Canceling task: 216 / 0x4d5c9e8
Jul 07 20:44:19-433880 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 48 bytes.
Jul 07 20:44:19-434100 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:19-434341 cadet-p2p-8620 DEBUG Checking 0x5129048 towards HS92G30M (->KNAS)
Jul 07 20:44:19-434594 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:19-434854 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:44:19-435047 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:19-435331 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 48)
Jul 07 20:44:19-435526 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:19-435707 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:19-435897 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:19-436086 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:19-436269 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:19-436454 util-scheduler-8620 DEBUG Canceling task: 212 / 0x4d61c30
Jul 07 20:44:19-436666 util-scheduler-8620 DEBUG Adding task: 221 / 0x4d61c30
Jul 07 20:44:19-436918 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:19-437089 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:19-437294 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:44:19-437496 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:19-437671 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:19-437847 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:19-438047 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:19-438252 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 48 bytes.
Jul 07 20:44:19-438436 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:44:19-438615 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:19-438806 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:44:19-439981 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:19-611984 util-scheduler-8620 DEBUG Checking readiness of task: 220 / 0x46620a0
Jul 07 20:44:19-612368 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-612564 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-612755 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-612947 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-613138 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-613355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-613546 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-613739 util-scheduler-8620 DEBUG Running task: 183 / 0x4d707d0
Jul 07 20:44:19-614016 cadet-con-8620 DEBUG FWD keepalive for CMHCKRVP (->V8XX)
Jul 07 20:44:19-614195 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:19-614447 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection CMHCKRVP (->V8XX)  (100 bytes)
Jul 07 20:44:19-614639 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0 (create)
Jul 07 20:44:19-614871 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:19-615082 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:19-615387 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:44:19-615587 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:19-615814 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:19-615998 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:19-616174 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:19-616402 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:44:19-616618 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:44:19-616844 util-scheduler-8620 DEBUG Adding task: 222 / 0x4d6ff98
Jul 07 20:44:19-617026 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:19-617253 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:19-617430 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:19-617606 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:19-617877 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:19-618061 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:19-618237 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:19-618438 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:19-618694 util-scheduler-8620 DEBUG Checking readiness of task: 220 / 0x46620a0
Jul 07 20:44:19-618887 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-619077 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-619266 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-619455 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-619643 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-619832 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-620020 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-620224 util-scheduler-8620 DEBUG Running task: 222 / 0x4d6ff98
Jul 07 20:44:19-620433 util-scheduler-8620 DEBUG Adding task: 223 / 0x4d6ff98
Jul 07 20:44:19-620657 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:19-620863 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:19-621073 util-scheduler-8620 DEBUG Adding task: 224 / 0x46620a0
Jul 07 20:44:19-621340 util-scheduler-8620 DEBUG Checking readiness of task: 224 / 0x46620a0
Jul 07 20:44:19-621534 util-scheduler-8620 DEBUG Checking readiness of task: 220 / 0x46620a0
Jul 07 20:44:19-621857 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:19-622050 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:19-622241 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:19-622430 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:19-622619 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:19-622809 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:19-622999 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:19-623191 util-scheduler-8620 DEBUG Running task: 224 / 0x46620a0
Jul 07 20:44:19-623377 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:19-623556 util-8620 DEBUG process_notify is running
Jul 07 20:44:19-623728 util-8620 DEBUG client_notify is running
Jul 07 20:44:19-623911 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:19-624109 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:19-624301 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:19-624623 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:20-841140 util-scheduler-8620 DEBUG Checking readiness of task: 220 / 0x46620a0
Jul 07 20:44:20-841563 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:20-841761 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:20-841953 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:20-842144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:20-842356 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:20-842545 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:20-842735 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:20-842929 util-scheduler-8620 DEBUG Running task: 220 / 0x46620a0
Jul 07 20:44:20-843353 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:20-843610 util-scheduler-8620 DEBUG Adding task: 225 / 0x4662248
Jul 07 20:44:20-843888 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:20-844112 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:20-844303 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:20-844493 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:20-844682 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:20-844871 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:20-845060 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:20-851777 util-scheduler-8620 DEBUG Running task: 225 / 0x4662248
Jul 07 20:44:20-852007 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:20-852211 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:20-852449 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:20-852657 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:20-852866 util-scheduler-8620 DEBUG Adding task: 226 / 0x46620a0
Jul 07 20:44:20-853054 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:20-853286 util-scheduler-8620 DEBUG Adding task: 227 / 0x46620a0
Jul 07 20:44:20-853543 util-scheduler-8620 DEBUG Checking readiness of task: 227 / 0x46620a0
Jul 07 20:44:20-853736 util-scheduler-8620 DEBUG Checking readiness of task: 226 / 0x46620a0
Jul 07 20:44:20-853927 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:20-854121 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:20-854312 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:20-854501 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:20-854691 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:20-854879 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:20-855068 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:20-855260 util-scheduler-8620 DEBUG Running task: 226 / 0x46620a0
Jul 07 20:44:20-855445 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:20-855624 util-8620 DEBUG process_notify is running
Jul 07 20:44:20-855796 util-8620 DEBUG client_notify is running
Jul 07 20:44:20-855984 util-scheduler-8620 DEBUG Canceling task: 223 / 0x4d6ff98
Jul 07 20:44:20-856208 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:44:20-856429 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:20-856670 cadet-p2p-8620 DEBUG Checking 0x5130fc0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:20-856905 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:20-857083 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:20-857277 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:20-857449 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:20-857630 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:20-857900 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:44:20-858094 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:20-858274 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:20-858461 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:20-858641 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:20-858870 util-scheduler-8620 DEBUG Adding task: 228 / 0x4d707d0
Jul 07 20:44:20-859108 cadet-con-8620 DEBUG next keepalive in 8 s
Jul 07 20:44:20-859279 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:20-859459 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:20-859658 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:20-859833 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:20-860007 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:20-860206 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:20-860412 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:44:20-860618 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:20-860798 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:20-860990 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:20-865175 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:21-032954 util-scheduler-8620 DEBUG Checking readiness of task: 227 / 0x46620a0
Jul 07 20:44:21-033370 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:21-033569 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:21-033764 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:21-033958 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:21-034154 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:21-034347 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:21-034540 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:21-034735 util-scheduler-8620 DEBUG Running task: 185 / 0x4d61838
Jul 07 20:44:21-034978 cadet-tun-8620 INFO Re-key Tunnel KNAS
Jul 07 20:44:21-035505 cadet-tun-8620 DEBUG  kx started 10 s ago
Jul 07 20:44:21-035722 cadet-tun-8620 INFO ===> EPHM for KNAS
Jul 07 20:44:21-035929 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:21-036134 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:21-036372 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:21-036558 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:21-036783 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:21-037090 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (196 bytes)
Jul 07 20:44:21-037316 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:21-037559 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:21-037769 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:21-038089 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 196)
Jul 07 20:44:21-038308 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:21-038536 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:21-038721 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:21-038899 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:21-039109 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 196 bytes
Jul 07 20:44:21-039325 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `KNAS'
Jul 07 20:44:21-039551 util-scheduler-8620 DEBUG Adding task: 229 / 0x4d5c9e8
Jul 07 20:44:21-039734 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:21-039940 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:21-040118 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:21-040295 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:21-040536 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:21-040733 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:21-040913 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:21-041114 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:21-041975 cadet-tun-8620 INFO ===> PING for KNAS
Jul 07 20:44:21-042452 cadet-tun-8620 DEBUG   sending 1463304033
Jul 07 20:44:21-042816 cadet-tun-8620 DEBUG   towards KNAS
Jul 07 20:44:21-043000 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:21-043188 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:21-047280 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:21-048087 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:21-048456 cadet-tun-8620 DEBUG   e sending 1153738418
Jul 07 20:44:21-048840 cadet-tun-8620 DEBUG   e towards CJFF
Jul 07 20:44:21-049050 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:21-049312 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:21-049547 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:21-049730 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:21-049954 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:21-050234 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (80 bytes)
Jul 07 20:44:21-050437 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:21-050675 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:21-050886 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:21-051197 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 80)
Jul 07 20:44:21-051397 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:21-051623 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:21-051807 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:21-051985 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:21-052191 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:21-052395 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:21-052573 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:21-052750 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:21-052989 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:21-053186 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:21-053391 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:21-053628 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:21-053823 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:21-054001 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:21-054223 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:21-054706 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:21-054922 util-scheduler-8620 DEBUG Adding task: 230 / 0x4d61838
Jul 07 20:44:21-055194 util-scheduler-8620 DEBUG Checking readiness of task: 227 / 0x46620a0
Jul 07 20:44:21-055391 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:21-055584 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:21-055776 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:21-055967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:21-056158 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:21-056349 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:21-056541 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:21-056734 util-scheduler-8620 DEBUG Running task: 229 / 0x4d5c9e8
Jul 07 20:44:21-056945 util-scheduler-8620 DEBUG Adding task: 231 / 0x4d5c9e8
Jul 07 20:44:21-057170 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:21-057402 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:21-057615 util-scheduler-8620 DEBUG Adding task: 232 / 0x46620a0
Jul 07 20:44:21-057861 util-scheduler-8620 DEBUG Checking readiness of task: 232 / 0x46620a0
Jul 07 20:44:21-058056 util-scheduler-8620 DEBUG Checking readiness of task: 227 / 0x46620a0
Jul 07 20:44:21-058248 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:21-058439 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:21-058629 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:21-058820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:21-059011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:21-059201 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:21-059392 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:21-059601 util-scheduler-8620 DEBUG Running task: 232 / 0x46620a0
Jul 07 20:44:21-059790 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:21-059971 util-8620 DEBUG process_notify is running
Jul 07 20:44:21-060144 util-8620 DEBUG client_notify is running
Jul 07 20:44:21-060325 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:21-060522 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:21-060714 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:21-061061 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:21-941826 util-scheduler-8620 DEBUG Checking readiness of task: 227 / 0x46620a0
Jul 07 20:44:21-942204 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:21-942401 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:21-942594 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:21-942785 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:21-942975 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:21-943166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:21-943356 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:21-943566 util-scheduler-8620 DEBUG Running task: 227 / 0x46620a0
Jul 07 20:44:21-943989 util-8620 DEBUG receive_ready read 348/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:21-944930 util-scheduler-8620 DEBUG Adding task: 233 / 0x4662248
Jul 07 20:44:21-945240 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:21-945463 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:21-945654 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:21-945845 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:21-946035 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:21-946224 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:21-946414 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:21-946604 util-scheduler-8620 DEBUG Running task: 233 / 0x4662248
Jul 07 20:44:21-946797 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:44:21-946998 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:44:21-947230 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `KNAS'
Jul 07 20:44:21-947497 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:21-947739 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:21-947969 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:21-948177 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:21-948425 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:21-948633 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:21-948820 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:21-949009 util-scheduler-8620 DEBUG Canceling task: 196 / 0x4d61c30
Jul 07 20:44:21-949256 util-scheduler-8620 DEBUG Adding task: 234 / 0x4d61c30
Jul 07 20:44:21-949436 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:21-949693 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:21-949907 util-scheduler-8620 DEBUG Adding task: 235 / 0x4d5e5d8
Jul 07 20:44:21-950089 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:21-950395 cadet-tun-8620 INFO <=== EPHM for KNAS
Jul 07 20:44:22-544262 util-scheduler-8620 DEBUG Adding task: 236 / 0x4662248
Jul 07 20:44:22-544700 util-scheduler-8620 DEBUG Checking readiness of task: 235 / 0x4d5e5d8
Jul 07 20:44:22-544903 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:22-545125 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:22-545344 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:22-545535 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:22-545725 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:22-545914 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:22-546103 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:22-546298 util-scheduler-8620 DEBUG Running task: 235 / 0x4d5e5d8
Jul 07 20:44:22-546485 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:22-546666 util-8620 DEBUG process_notify is running
Jul 07 20:44:22-546839 util-8620 DEBUG client_notify is running
Jul 07 20:44:22-547076 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:22-547459 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:22-547671 util-scheduler-8620 DEBUG Running task: 236 / 0x4662248
Jul 07 20:44:22-547862 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:44:22-548061 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:44:22-548289 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `KNAS'
Jul 07 20:44:22-548550 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:22-548790 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:22-549020 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:22-549252 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:22-549502 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:22-549710 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:22-549897 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:22-550085 util-scheduler-8620 DEBUG Canceling task: 234 / 0x4d61c30
Jul 07 20:44:22-550305 util-scheduler-8620 DEBUG Adding task: 237 / 0x4d61c30
Jul 07 20:44:22-550496 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:22-550746 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:22-550961 util-scheduler-8620 DEBUG Adding task: 238 / 0x4d5e5d8
Jul 07 20:44:22-551143 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:22-551447 cadet-tun-8620 INFO <=== PING for KNAS
Jul 07 20:44:22-551808 cadet-tun-8620 DEBUG   t_decrypt with 7VEEVN5W
Jul 07 20:44:22-552143 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:22-552470 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:22-556295 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:22-557902 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:22-558224 cadet-tun-8620 INFO ===> PONG for KNAS
Jul 07 20:44:22-558616 cadet-tun-8620 DEBUG   sending 2249405204
Jul 07 20:44:22-558796 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:22-558985 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:22-562112 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:22-562735 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:22-563015 cadet-tun-8620 DEBUG   e sending 1043037537
Jul 07 20:44:22-563230 cadet-tun-8620 DEBUG GMT KX on Tunnel KNAS
Jul 07 20:44:22-563433 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:22-563663 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:22-563844 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:22-564065 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:22-564345 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (48 bytes)
Jul 07 20:44:22-564547 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:22-564783 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:22-564990 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:22-565326 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 48)
Jul 07 20:44:22-565552 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:22-565779 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:22-565962 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:22-566139 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:22-566342 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:22-566544 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:22-566719 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:22-566899 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:22-567156 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:22-567352 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:22-567529 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:22-567763 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:22-567956 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:22-568145 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:22-568377 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:22-568569 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:22-568745 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:22-568943 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:22-569126 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:22-569371 util-scheduler-8620 DEBUG Adding task: 239 / 0x46620a0
Jul 07 20:44:22-569651 util-scheduler-8620 DEBUG Checking readiness of task: 239 / 0x46620a0
Jul 07 20:44:22-569849 util-scheduler-8620 DEBUG Checking readiness of task: 238 / 0x4d5e5d8
Jul 07 20:44:22-570041 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:22-570230 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:22-570419 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:22-570609 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:22-570797 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:22-570986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:22-571176 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:22-571492 util-scheduler-8620 DEBUG Running task: 238 / 0x4d5e5d8
Jul 07 20:44:22-571682 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:22-571861 util-8620 DEBUG process_notify is running
Jul 07 20:44:22-572032 util-8620 DEBUG client_notify is running
Jul 07 20:44:22-572259 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:22-572558 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:22-572772 util-scheduler-8620 DEBUG Running task: 239 / 0x46620a0
Jul 07 20:44:22-573179 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:22-573444 util-scheduler-8620 DEBUG Adding task: 240 / 0x4662248
Jul 07 20:44:22-573696 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:22-573888 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:22-574077 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:22-574266 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:22-574455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:22-574647 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:22-574836 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:22-575026 util-scheduler-8620 DEBUG Running task: 240 / 0x4662248
Jul 07 20:44:22-575217 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:22-575431 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:22-575649 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:22-575853 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:22-576054 util-scheduler-8620 DEBUG Adding task: 241 / 0x46620a0
Jul 07 20:44:22-576238 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:22-576435 util-scheduler-8620 DEBUG Adding task: 242 / 0x46620a0
Jul 07 20:44:22-576674 util-scheduler-8620 DEBUG Checking readiness of task: 242 / 0x46620a0
Jul 07 20:44:22-576865 util-scheduler-8620 DEBUG Checking readiness of task: 241 / 0x46620a0
Jul 07 20:44:22-577057 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:22-577269 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:22-577460 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:22-577649 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:22-577838 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:22-578027 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:22-578228 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:22-578418 util-scheduler-8620 DEBUG Running task: 241 / 0x46620a0
Jul 07 20:44:22-578602 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:22-578787 util-8620 DEBUG process_notify is running
Jul 07 20:44:22-578956 util-8620 DEBUG client_notify is running
Jul 07 20:44:22-579142 util-scheduler-8620 DEBUG Canceling task: 194 / 0x4d683b0
Jul 07 20:44:22-579363 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:22-579581 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:44:22-579813 cadet-p2p-8620 DEBUG Checking 0x511bf18 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:22-580046 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:22-580223 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:22-580393 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:22-580562 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:22-580741 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:22-581004 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:22-581221 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:22-581403 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:22-581592 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:22-581774 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:22-581983 util-scheduler-8620 DEBUG Adding task: 243 / 0x4d68be8
Jul 07 20:44:22-582221 cadet-con-8620 DEBUG next keepalive in 8 s
Jul 07 20:44:22-582392 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:22-582574 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:22-582774 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:22-582948 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:22-583121 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:22-583320 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:22-583525 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:22-583794 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:22-583976 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:22-584166 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:22-585519 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-062112 util-scheduler-8620 DEBUG Checking readiness of task: 242 / 0x46620a0
Jul 07 20:44:23-062522 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-065324 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-065525 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-065759 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-065954 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-066147 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-066340 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-066537 util-scheduler-8620 DEBUG Running task: 242 / 0x46620a0
Jul 07 20:44:23-066964 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:23-067223 util-scheduler-8620 DEBUG Adding task: 244 / 0x4662248
Jul 07 20:44:23-067509 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-067703 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-067896 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-068088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-068279 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-068470 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-068662 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-068854 util-scheduler-8620 DEBUG Running task: 244 / 0x4662248
Jul 07 20:44:23-069068 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:23-069293 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:23-069526 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:23-069735 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-069945 util-scheduler-8620 DEBUG Adding task: 245 / 0x46620a0
Jul 07 20:44:23-070135 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:23-070344 util-scheduler-8620 DEBUG Adding task: 246 / 0x46620a0
Jul 07 20:44:23-070591 util-scheduler-8620 DEBUG Checking readiness of task: 246 / 0x46620a0
Jul 07 20:44:23-070784 util-scheduler-8620 DEBUG Checking readiness of task: 245 / 0x46620a0
Jul 07 20:44:23-070978 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-071169 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-071361 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-071552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-071743 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-071933 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-072124 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-072317 util-scheduler-8620 DEBUG Running task: 245 / 0x46620a0
Jul 07 20:44:23-072504 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-072685 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-072859 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-073048 util-scheduler-8620 DEBUG Canceling task: 231 / 0x4d5c9e8
Jul 07 20:44:23-073423 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 196 bytes.
Jul 07 20:44:23-073698 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:23-073971 cadet-p2p-8620 DEBUG Checking 0x51341b0 towards HS92G30M (->KNAS)
Jul 07 20:44:23-074210 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:23-074390 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:23-074582 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:23-074873 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 196)
Jul 07 20:44:23-075071 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:23-075253 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:23-075443 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:23-075653 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:23-075835 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:23-076022 util-scheduler-8620 DEBUG Canceling task: 221 / 0x4d61c30
Jul 07 20:44:23-076237 util-scheduler-8620 DEBUG Adding task: 247 / 0x4d61c30
Jul 07 20:44:23-076491 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:23-076664 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:23-076889 cadet-p2p-8620 DEBUG Checking 0x513ab90 towards HS92G30M (->KNAS)
Jul 07 20:44:23-077129 cadet-p2p-8620 DEBUG Checking 0x513ab90 towards HS92G30M (->KNAS)
Jul 07 20:44:23-077336 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:23-077548 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `KNAS'
Jul 07 20:44:23-077773 util-scheduler-8620 DEBUG Adding task: 248 / 0x4d5c9e8
Jul 07 20:44:23-077955 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:23-078135 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:23-078338 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:23-078515 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:23-078692 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:23-078933 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:23-079129 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:44:23-079308 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:44:23-079544 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:23-079739 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:23-079917 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:23-080117 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:23-080338 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 196 bytes.
Jul 07 20:44:23-080524 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:23-080727 util-scheduler-8620 DEBUG Adding task: 249 / 0x4d5c9e8
Jul 07 20:44:23-080949 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:23-081147 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-081377 util-scheduler-8620 DEBUG Adding task: 250 / 0x46620a0
Jul 07 20:44:23-081580 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:23-082508 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-082714 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:23-082967 util-scheduler-8620 DEBUG Checking readiness of task: 250 / 0x46620a0
Jul 07 20:44:23-083163 util-scheduler-8620 DEBUG Checking readiness of task: 246 / 0x46620a0
Jul 07 20:44:23-083517 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-083840 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-084035 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-084227 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-084418 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-084610 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-084805 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-084998 util-scheduler-8620 DEBUG Running task: 250 / 0x46620a0
Jul 07 20:44:23-085185 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-085389 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-085562 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-085742 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:23-085940 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:23-086131 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:23-086440 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-086667 util-scheduler-8620 DEBUG Running task: 248 / 0x4d5c9e8
Jul 07 20:44:23-086863 util-scheduler-8620 DEBUG Canceling task: 249 / 0x4d5c9e8
Jul 07 20:44:23-087081 util-scheduler-8620 DEBUG Adding task: 251 / 0x4d5c9e8
Jul 07 20:44:23-087301 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:23-087509 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-087710 util-scheduler-8620 DEBUG Adding task: 252 / 0x46620a0
Jul 07 20:44:23-087952 util-scheduler-8620 DEBUG Checking readiness of task: 252 / 0x46620a0
Jul 07 20:44:23-088145 util-scheduler-8620 DEBUG Checking readiness of task: 246 / 0x46620a0
Jul 07 20:44:23-088338 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-088529 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-088720 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-088911 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-089102 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-089316 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-089508 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-089700 util-scheduler-8620 DEBUG Running task: 246 / 0x46620a0
Jul 07 20:44:23-090104 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:23-090331 util-scheduler-8620 DEBUG Adding task: 253 / 0x4662248
Jul 07 20:44:23-090542 util-scheduler-8620 DEBUG Running task: 252 / 0x46620a0
Jul 07 20:44:23-090728 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-090905 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-091076 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-091254 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:23-091445 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:23-091634 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:23-091933 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-092183 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-092377 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-092570 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-092761 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-092951 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-093142 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-093357 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-093549 util-scheduler-8620 DEBUG Running task: 253 / 0x4662248
Jul 07 20:44:23-093741 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:23-093937 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:23-094153 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:23-094336 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:23-094540 util-scheduler-8620 DEBUG Adding task: 254 / 0x46620a0
Jul 07 20:44:23-094784 util-scheduler-8620 DEBUG Checking readiness of task: 254 / 0x46620a0
Jul 07 20:44:23-094978 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-095170 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-095364 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-095555 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-095746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-095952 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-096143 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-096336 util-scheduler-8620 DEBUG Running task: 254 / 0x46620a0
Jul 07 20:44:23-096736 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:23-096960 util-scheduler-8620 DEBUG Adding task: 255 / 0x4662248
Jul 07 20:44:23-097227 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-097423 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-097615 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-097806 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-097996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-098187 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-098377 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-098568 util-scheduler-8620 DEBUG Running task: 255 / 0x4662248
Jul 07 20:44:23-098770 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:23-098963 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:23-099175 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:23-099372 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-099571 util-scheduler-8620 DEBUG Adding task: 256 / 0x46620a0
Jul 07 20:44:23-099757 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:23-099956 util-scheduler-8620 DEBUG Adding task: 257 / 0x46620a0
Jul 07 20:44:23-100199 util-scheduler-8620 DEBUG Checking readiness of task: 257 / 0x46620a0
Jul 07 20:44:23-100391 util-scheduler-8620 DEBUG Checking readiness of task: 256 / 0x46620a0
Jul 07 20:44:23-100583 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-100772 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-100962 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-101152 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-101363 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-101553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-101742 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-101933 util-scheduler-8620 DEBUG Running task: 256 / 0x46620a0
Jul 07 20:44:23-102117 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-102292 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-102461 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-102642 util-scheduler-8620 DEBUG Canceling task: 251 / 0x4d5c9e8
Jul 07 20:44:23-102873 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 80 bytes.
Jul 07 20:44:23-103088 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:23-103319 cadet-p2p-8620 DEBUG Checking 0x513ab90 towards HS92G30M (->KNAS)
Jul 07 20:44:23-103550 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:23-103727 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:44:23-103912 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:23-104188 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 80)
Jul 07 20:44:23-104381 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:23-104559 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:23-104747 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:23-104934 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:23-105110 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:23-105317 util-scheduler-8620 DEBUG Canceling task: 247 / 0x4d61c30
Jul 07 20:44:23-105541 util-scheduler-8620 DEBUG Adding task: 258 / 0x4d61c30
Jul 07 20:44:23-105785 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:23-105954 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:23-106174 cadet-p2p-8620 DEBUG Checking 0x5378be0 towards HS92G30M (->KNAS)
Jul 07 20:44:23-106412 cadet-p2p-8620 DEBUG Checking 0x5378be0 towards HS92G30M (->KNAS)
Jul 07 20:44:23-106589 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:23-106790 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `KNAS'
Jul 07 20:44:23-107008 util-scheduler-8620 DEBUG Adding task: 259 / 0x4d5c9e8
Jul 07 20:44:23-107186 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:23-107362 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:44:23-107560 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:23-107735 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:23-107909 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:23-108146 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on HS92G30M (->KNAS)
Jul 07 20:44:23-108339 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:44:23-108516 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:44:23-108713 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:23-108915 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 80 bytes.
Jul 07 20:44:23-109097 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:44:23-109318 util-scheduler-8620 DEBUG Adding task: 260 / 0x4d5c9e8
Jul 07 20:44:23-109534 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:23-109728 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-109926 util-scheduler-8620 DEBUG Adding task: 261 / 0x46620a0
Jul 07 20:44:23-110123 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:44:23-110465 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-110665 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:23-110903 util-scheduler-8620 DEBUG Checking readiness of task: 261 / 0x46620a0
Jul 07 20:44:23-111093 util-scheduler-8620 DEBUG Checking readiness of task: 257 / 0x46620a0
Jul 07 20:44:23-111283 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-111473 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-111662 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-111851 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-112039 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-112228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-112416 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-112606 util-scheduler-8620 DEBUG Running task: 261 / 0x46620a0
Jul 07 20:44:23-112790 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-112965 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-113134 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-113336 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:23-113526 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:23-113713 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:23-113993 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:23-114201 util-scheduler-8620 DEBUG Running task: 259 / 0x4d5c9e8
Jul 07 20:44:23-114392 util-scheduler-8620 DEBUG Canceling task: 260 / 0x4d5c9e8
Jul 07 20:44:23-114602 util-scheduler-8620 DEBUG Adding task: 262 / 0x4d5c9e8
Jul 07 20:44:23-114821 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:23-115015 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:23-115236 util-scheduler-8620 DEBUG Adding task: 263 / 0x46620a0
Jul 07 20:44:23-115538 util-scheduler-8620 DEBUG Checking readiness of task: 263 / 0x46620a0
Jul 07 20:44:23-115731 util-scheduler-8620 DEBUG Checking readiness of task: 257 / 0x46620a0
Jul 07 20:44:23-115921 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:23-116110 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:23-116300 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:23-116489 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:23-116678 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:23-116867 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:23-117055 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:23-117270 util-scheduler-8620 DEBUG Running task: 263 / 0x46620a0
Jul 07 20:44:23-117455 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:23-117631 util-8620 DEBUG process_notify is running
Jul 07 20:44:23-117799 util-8620 DEBUG client_notify is running
Jul 07 20:44:23-117975 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:23-118165 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:23-118353 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:23-118633 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:24-488048 util-scheduler-8620 DEBUG Checking readiness of task: 257 / 0x46620a0
Jul 07 20:44:24-488431 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-488627 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-488820 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-489012 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-489227 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-489419 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-489610 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-489805 util-scheduler-8620 DEBUG Running task: 257 / 0x46620a0
Jul 07 20:44:24-490228 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:24-490483 util-scheduler-8620 DEBUG Adding task: 264 / 0x4662248
Jul 07 20:44:24-490762 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-490955 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-491145 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-491335 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-491524 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-491713 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-491902 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-492092 util-scheduler-8620 DEBUG Running task: 264 / 0x4662248
Jul 07 20:44:24-492284 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:24-492484 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:24-492717 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:24-492923 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:24-493130 util-scheduler-8620 DEBUG Adding task: 265 / 0x46620a0
Jul 07 20:44:24-493727 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:24-493952 util-scheduler-8620 DEBUG Adding task: 266 / 0x46620a0
Jul 07 20:44:24-494199 util-scheduler-8620 DEBUG Checking readiness of task: 266 / 0x46620a0
Jul 07 20:44:24-494423 util-scheduler-8620 DEBUG Checking readiness of task: 265 / 0x46620a0
Jul 07 20:44:24-494616 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-494806 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-494999 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-495189 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-495378 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-495567 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-495756 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-495948 util-scheduler-8620 DEBUG Running task: 265 / 0x46620a0
Jul 07 20:44:24-496134 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:24-496312 util-8620 DEBUG process_notify is running
Jul 07 20:44:24-496503 util-8620 DEBUG client_notify is running
Jul 07 20:44:24-496691 util-scheduler-8620 DEBUG Canceling task: 262 / 0x4d5c9e8
Jul 07 20:44:24-496917 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 48 bytes.
Jul 07 20:44:24-497138 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:24-497403 cadet-p2p-8620 DEBUG Checking 0x5378be0 towards HS92G30M (->KNAS)
Jul 07 20:44:24-497637 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:24-497815 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:44:24-498005 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:24-498289 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 48)
Jul 07 20:44:24-498485 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:24-498666 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:24-498855 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:24-499044 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:24-499222 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:24-499408 util-scheduler-8620 DEBUG Canceling task: 258 / 0x4d61c30
Jul 07 20:44:24-499619 util-scheduler-8620 DEBUG Adding task: 267 / 0x4d61c30
Jul 07 20:44:24-499870 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:24-500041 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:24-500222 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:44:24-500510 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:24-500687 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:24-500862 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:24-501062 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:24-501293 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 48 bytes.
Jul 07 20:44:24-501477 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:44:24-501657 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:24-501848 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:44:24-502963 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:24-509073 util-scheduler-8620 DEBUG Checking readiness of task: 266 / 0x46620a0
Jul 07 20:44:24-509310 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-509506 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-509699 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-509891 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-510082 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-510273 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-510464 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-510656 util-scheduler-8620 DEBUG Running task: 266 / 0x46620a0
Jul 07 20:44:24-511060 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:24-511311 util-scheduler-8620 DEBUG Adding task: 268 / 0x4662248
Jul 07 20:44:24-511563 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-511755 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-511946 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-512135 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-512324 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-512513 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-512703 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-512892 util-scheduler-8620 DEBUG Running task: 268 / 0x4662248
Jul 07 20:44:24-513082 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:44:24-513317 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:44:24-513537 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `KNAS'
Jul 07 20:44:24-513792 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:24-514030 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:24-514261 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:24-514468 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:24-514715 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:24-514923 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:24-515113 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:24-515298 util-scheduler-8620 DEBUG Canceling task: 237 / 0x4d61c30
Jul 07 20:44:24-515517 util-scheduler-8620 DEBUG Adding task: 269 / 0x4d61c30
Jul 07 20:44:24-515697 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:24-515953 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:24-516166 util-scheduler-8620 DEBUG Adding task: 270 / 0x4d5e5d8
Jul 07 20:44:24-516348 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:24-517738 cadet-tun-8620 INFO <=== PONG for KNAS
Jul 07 20:44:24-518578 cadet-tun-8620 DEBUG   t_decrypt with 7VEEVN5W
Jul 07 20:44:24-518852 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:24-519023 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:24-522708 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:24-524149 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:24-524940 util-scheduler-8620 DEBUG Canceling task: 230 / 0x4d61838
Jul 07 20:44:24-526952 util-scheduler-8620 DEBUG Adding task: 271 / 0x4d61838
Jul 07 20:44:24-528919 cadet-tun-8620 DEBUG Tunnel KNAS estate was CADET_TUNNEL_KEY_PING
Jul 07 20:44:24-530330 cadet-tun-8620 DEBUG Tunnel KNAS estate is now CADET_TUNNEL_KEY_OK
Jul 07 20:44:24-532672 cadet-tun-8620 DEBUG GCT_send_queued_data on tunnel KNAS
Jul 07 20:44:24-533683 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:24-533874 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:24-534062 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:24-534247 cadet-tun-8620 DEBUG TTT  tq_head 0x4d64510, tq_tail 0x4d64510
Jul 07 20:44:24-534429 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:24-534599 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:24-534821 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:24-535005 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:24-535248 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:24-535435 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:24-536308 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:24-536494 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:24-536680 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:24-536862 cadet-tun-8620 DEBUG TTT  tq_head 0x4d64510, tq_tail 0x4d64510
Jul 07 20:44:24-537046 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:24-537265 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:24-537483 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:24-537655 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:24-537884 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:24-538068 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:24-540279 cadet-tun-8620 DEBUG   buffer space: 11
Jul 07 20:44:24-541288 cadet-tun-8620 DEBUG   tq head: 0x4d64510
Jul 07 20:44:24-542431 cadet-tun-8620 DEBUG  sending queued data
Jul 07 20:44:24-543123 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:24-543331 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:24-543512 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:24-543695 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:24-543886 cadet-tun-8620 DEBUG TTT  tq_head 0x4d64510, tq_tail 0x4d64510
Jul 07 20:44:24-544065 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:24-544234 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:24-544450 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:24-544621 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:24-544851 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:24-545046 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:24-546455 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:24-547771 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:24-548294 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:24-551502 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:24-552277 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:24-553004 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:24-554569 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:24-565867 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:24-566140 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:24-566324 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:24-566557 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:24-569071 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:44:24-571006 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection HS92G30M (->KNAS) (96 bytes)
Jul 07 20:44:24-572892 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:24-573905 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:44:24-574879 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:44:24-575923 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:24-576826 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:24-577077 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:24-577312 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:24-577630 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 96)
Jul 07 20:44:24-577830 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:24-578057 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:24-578242 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:24-578419 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:24-578628 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 96 bytes
Jul 07 20:44:24-579007 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:44:24-579242 util-scheduler-8620 DEBUG Adding task: 272 / 0x4d5c9e8
Jul 07 20:44:24-579427 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:24-579634 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:24-579812 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:24-579988 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:24-580230 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:24-580440 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:24-580619 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:24-580840 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:24-583685 cadet-tun-8620 DEBUG GCT_send_queued_data end
Jul 07 20:44:24-584310 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:24-584532 util-scheduler-8620 DEBUG Adding task: 273 / 0x46620a0
Jul 07 20:44:24-584810 util-scheduler-8620 DEBUG Checking readiness of task: 273 / 0x46620a0
Jul 07 20:44:24-585008 util-scheduler-8620 DEBUG Checking readiness of task: 270 / 0x4d5e5d8
Jul 07 20:44:24-585224 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-585417 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-585607 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-585797 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-585987 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-586176 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-586365 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-586560 util-scheduler-8620 DEBUG Running task: 270 / 0x4d5e5d8
Jul 07 20:44:24-586746 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:24-586924 util-8620 DEBUG process_notify is running
Jul 07 20:44:24-587098 util-8620 DEBUG client_notify is running
Jul 07 20:44:24-587329 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:24-587677 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:24-587890 util-scheduler-8620 DEBUG Running task: 272 / 0x4d5c9e8
Jul 07 20:44:24-588099 util-scheduler-8620 DEBUG Adding task: 274 / 0x4d5c9e8
Jul 07 20:44:24-588323 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:24-588524 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:24-588726 util-scheduler-8620 DEBUG Adding task: 275 / 0x46620a0
Jul 07 20:44:24-588969 util-scheduler-8620 DEBUG Checking readiness of task: 275 / 0x46620a0
Jul 07 20:44:24-589162 util-scheduler-8620 DEBUG Checking readiness of task: 273 / 0x46620a0
Jul 07 20:44:24-589376 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:24-589566 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:24-589756 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:24-590012 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:24-590205 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:24-590395 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:24-590584 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:24-590788 util-scheduler-8620 DEBUG Running task: 275 / 0x46620a0
Jul 07 20:44:24-590971 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:24-591145 util-8620 DEBUG process_notify is running
Jul 07 20:44:24-591325 util-8620 DEBUG client_notify is running
Jul 07 20:44:24-591503 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:24-591699 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:24-591887 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:24-592193 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:25-901232 util-scheduler-8620 DEBUG Checking readiness of task: 273 / 0x46620a0
Jul 07 20:44:25-901619 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:25-901815 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-902007 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-902197 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-902417 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-902608 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-902797 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-902993 util-scheduler-8620 DEBUG Running task: 273 / 0x46620a0
Jul 07 20:44:25-903415 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:25-903673 util-scheduler-8620 DEBUG Adding task: 276 / 0x4662248
Jul 07 20:44:25-903952 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:25-904144 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-904334 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-904523 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-904716 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-904908 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-905104 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-906266 util-scheduler-8620 DEBUG Running task: 276 / 0x4662248
Jul 07 20:44:25-906486 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:25-906690 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:25-906930 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:25-907140 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:25-907348 util-scheduler-8620 DEBUG Adding task: 277 / 0x46620a0
Jul 07 20:44:25-907536 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:25-907741 util-scheduler-8620 DEBUG Adding task: 278 / 0x46620a0
Jul 07 20:44:25-914387 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-914644 util-scheduler-8620 DEBUG Checking readiness of task: 277 / 0x46620a0
Jul 07 20:44:25-914839 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:25-915030 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-915220 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-915413 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-915603 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-915792 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-915981 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-916175 util-scheduler-8620 DEBUG Running task: 277 / 0x46620a0
Jul 07 20:44:25-918735 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:25-918953 util-8620 DEBUG process_notify is running
Jul 07 20:44:25-919129 util-8620 DEBUG client_notify is running
Jul 07 20:44:25-919323 util-scheduler-8620 DEBUG Canceling task: 274 / 0x4d5c9e8
Jul 07 20:44:25-919652 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:44:25-919876 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:25-920118 cadet-p2p-8620 DEBUG Checking 0x5391f00 towards HS92G30M (->KNAS)
Jul 07 20:44:25-920943 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:25-921146 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:25-921367 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:25-921765 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:25-921958 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:44:25-923427 cadet-p2p-8620 DEBUG   payload ID 0
Jul 07 20:44:25-924545 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 96)
Jul 07 20:44:25-924781 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:25-924973 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:25-925228 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:25-926194 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:25-927679 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:25-929963 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:44:25-931559 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:44:25-933827 cadet-chn-8620 DEBUG !!! STD BACKOFF 250 ms
Jul 07 20:44:25-936482 util-scheduler-8620 DEBUG Adding task: 279 / 0x4d63a48
Jul 07 20:44:25-937504 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:25-939459 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:25-940803 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:25-941935 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:25-943197 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:25-945057 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:25-946050 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:25-947149 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:25-948002 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:25-948189 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:25-948375 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:25-948559 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:25-948737 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:25-948918 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:25-949137 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:25-949331 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:25-949565 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:25-949750 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:25-954670 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:25-955693 cadet-chn-8620 DEBUG  channel not ready yet!
Jul 07 20:44:25-956752 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:25-956953 util-scheduler-8620 DEBUG Canceling task: 267 / 0x4d61c30
Jul 07 20:44:25-957176 util-scheduler-8620 DEBUG Adding task: 280 / 0x4d61c30
Jul 07 20:44:25-957447 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:25-958500 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:25-959599 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:44:25-959897 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:25-960092 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:44:25-960298 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:25-960476 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:25-960650 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:25-960863 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:25-961070 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 96 bytes.
Jul 07 20:44:25-961277 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:44:25-961459 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:25-961653 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:44:25-962409 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:25-962693 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-962888 util-scheduler-8620 DEBUG Checking readiness of task: 112 / 0x4665be0
Jul 07 20:44:25-963080 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-963283 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-963472 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-963661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-963848 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-964036 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-964228 util-scheduler-8620 DEBUG Running task: 112 / 0x4665be0
Jul 07 20:44:25-964656 util-8620 DEBUG receive_ready read 619/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:44:25-964931 util-scheduler-8620 DEBUG Adding task: 281 / 0x4665d88
Jul 07 20:44:25-965181 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-965395 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-965584 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-965773 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-965961 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-966149 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-966337 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-966526 util-scheduler-8620 DEBUG Running task: 281 / 0x4665d88
Jul 07 20:44:25-966717 util-8620 DEBUG Received message of type 145 and size 619 from dht service.
Jul 07 20:44:25-966915 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:25-967127 util-scheduler-8620 DEBUG Adding task: 282 / 0x4665be0
Jul 07 20:44:25-967450 dht-api-8620 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46642c0
Jul 07 20:44:25-967766 dht-api-8620 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 20:44:25-971231 cadet-dht-8620 DEBUG    GET has 1 hops.
Jul 07 20:44:25-971656 cadet-dht-8620 DEBUG    Adding from GET: V8XX.
Jul 07 20:44:25-972005 cadet-dht-8620 DEBUG    PUT has 0 hops.
Jul 07 20:44:25-972446 cadet-dht-8620 DEBUG    (first of GET: V8XX)
Jul 07 20:44:25-972852 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:44:25-973066 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:44:25-973294 cadet-dht-8620 DEBUG        4: V8XX
Jul 07 20:44:25-973761 cadet-dht-8620 INFO Got path from DHT:  GN10 V8XX
Jul 07 20:44:25-974143 cadet-dht-8620 DEBUG Got HELLO for V8XX
Jul 07 20:44:25-974379 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:25-974560 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:25-974793 cadet-p2p-8620 DEBUG set hello for V8XX
Jul 07 20:44:25-975922 cadet-p2p-8620 DEBUG  merge into 0x53969f8 (491 bytes)
Jul 07 20:44:25-976307 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:44:25-976507 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:44:25-976727 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:25-976948 util-scheduler-8620 DEBUG Adding task: 283 / 0x46624e8
Jul 07 20:44:25-977263 util-scheduler-8620 DEBUG Checking readiness of task: 282 / 0x4665be0
Jul 07 20:44:25-977459 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-977677 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-977868 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-978061 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-978255 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-978447 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-978649 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-978844 util-scheduler-8620 DEBUG Running task: 282 / 0x4665be0
Jul 07 20:44:25-979273 util-8620 DEBUG receive_ready read 282/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:44:25-979519 util-scheduler-8620 DEBUG Adding task: 284 / 0x4665d88
Jul 07 20:44:25-979738 util-scheduler-8620 DEBUG Running task: 283 / 0x46624e8
Jul 07 20:44:25-979927 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:44:25-980128 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:44:25-980336 util-scheduler-8620 DEBUG Adding task: 285 / 0x4663d68
Jul 07 20:44:25-980585 util-scheduler-8620 DEBUG Checking readiness of task: 285 / 0x4663d68
Jul 07 20:44:25-980804 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-980994 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-981184 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-981405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-981596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-981784 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-981971 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-982163 util-scheduler-8620 DEBUG Running task: 285 / 0x4663d68
Jul 07 20:44:25-982348 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:44:25-982538 util-8620 DEBUG process_notify is running
Jul 07 20:44:25-982710 util-8620 DEBUG client_notify is running
Jul 07 20:44:25-983092 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:44:25-983313 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:44:25-983529 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:25-983729 util-scheduler-8620 DEBUG Adding task: 286 / 0x46624e8
Jul 07 20:44:25-983928 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:44:25-984129 util-scheduler-8620 DEBUG Canceling task: 286 / 0x46624e8
Jul 07 20:44:25-984349 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:25-984545 util-scheduler-8620 DEBUG Adding task: 287 / 0x46624e8
Jul 07 20:44:25-984728 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:44:25-984924 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:44:25-985373 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:44:25-985592 util-scheduler-8620 DEBUG Running task: 284 / 0x4665d88
Jul 07 20:44:25-985782 util-8620 DEBUG Received message of type 145 and size 282 from dht service.
Jul 07 20:44:25-985977 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:25-986194 util-scheduler-8620 DEBUG Adding task: 288 / 0x4665be0
Jul 07 20:44:25-986399 dht-api-8620 DEBUG Received reply for `P00PHXNA' from DHT service 0x46642c0
Jul 07 20:44:25-986604 dht-api-8620 DEBUG Giving 90 byte reply for P00PHXNA to application
Jul 07 20:44:25-987353 cadet-dht-8620 DEBUG    GET has 1 hops.
Jul 07 20:44:25-987570 cadet-dht-8620 DEBUG    Adding from GET: V8XX.
Jul 07 20:44:25-987756 cadet-dht-8620 DEBUG    PUT has 2 hops.
Jul 07 20:44:25-987977 cadet-dht-8620 DEBUG    Adding from PUT: GN10.
Jul 07 20:44:25-988186 cadet-dht-8620 DEBUG    Adding from PUT: P00P.
Jul 07 20:44:25-988389 cadet-dht-8620 DEBUG    (first of GET: V8XX)
Jul 07 20:44:25-988838 cadet-dht-8620 DEBUG    (first of PUT: P00P)
Jul 07 20:44:25-989021 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:44:25-989247 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:44:25-989450 cadet-dht-8620 DEBUG        3: P00P
Jul 07 20:44:25-989748 cadet-dht-8620 INFO Got path from DHT:  GN10 P00P
Jul 07 20:44:25-989974 cadet-dht-8620 DEBUG Got HELLO for P00P
Jul 07 20:44:25-990199 cadet-p2p-8620 DEBUG adding path [2] to peer P00P
Jul 07 20:44:25-990377 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:25-990600 cadet-p2p-8620 DEBUG set hello for P00P
Jul 07 20:44:25-991038 cadet-p2p-8620 DEBUG  merge into 0x5399300 (90 bytes)
Jul 07 20:44:25-991292 transport-api-8620 DEBUG Offering `HELLO' message of `P00P' to transport for validation.
Jul 07 20:44:25-991497 transport-api-8620 DEBUG Control transmit of 90 bytes requested
Jul 07 20:44:25-991996 util-scheduler-8620 DEBUG Canceling task: 287 / 0x46624e8
Jul 07 20:44:25-992234 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:25-992441 util-scheduler-8620 DEBUG Adding task: 289 / 0x46624e8
Jul 07 20:44:25-992701 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:25-992919 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-993110 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-993322 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-993511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-993700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-993888 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-994075 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-994264 util-scheduler-8620 DEBUG Running task: 289 / 0x46624e8
Jul 07 20:44:25-994446 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:44:25-994638 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:44:25-994839 util-scheduler-8620 DEBUG Adding task: 290 / 0x4663d68
Jul 07 20:44:25-995078 util-scheduler-8620 DEBUG Checking readiness of task: 290 / 0x4663d68
Jul 07 20:44:25-995269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:25-995460 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:25-995649 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:25-995837 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:25-996025 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:25-996212 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:25-996400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:25-996588 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:25-996777 util-scheduler-8620 DEBUG Running task: 290 / 0x4663d68
Jul 07 20:44:25-996961 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:44:25-997137 util-8620 DEBUG process_notify is running
Jul 07 20:44:25-997327 util-8620 DEBUG client_notify is running
Jul 07 20:44:25-998098 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:44:25-998309 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:44:25-998503 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:44:25-998706 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:44:25-998929 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:44:25-999125 util-scheduler-8620 DEBUG Adding task: 291 / 0x46624e8
Jul 07 20:44:25-999322 transport-api-8620 DEBUG Added 90 bytes of control message at 40
Jul 07 20:44:25-999535 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `P00P'.
Jul 07 20:44:25-999729 transport-api-8620 DEBUG Added 40 bytes of control message at 130
Jul 07 20:44:25-999924 util-scheduler-8620 DEBUG Canceling task: 291 / 0x46624e8
Jul 07 20:44:26-000119 transport-api-8620 DEBUG Transmitting 170 bytes to transport service
Jul 07 20:44:26-000317 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:44:26-000774 util-8620 DEBUG Connection transmitted 170/170 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:44:26-435117 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:26-435520 util-scheduler-8620 DEBUG Checking readiness of task: 278 / 0x46620a0
Jul 07 20:44:26-435736 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:26-435937 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:26-436132 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:26-436324 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:26-436515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:26-436705 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:26-436933 util-scheduler-8620 DEBUG Running task: 278 / 0x46620a0
Jul 07 20:44:26-437387 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:26-437647 util-scheduler-8620 DEBUG Adding task: 292 / 0x4662248
Jul 07 20:44:26-437929 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:26-438120 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:26-438309 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:26-438497 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:26-438684 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:26-438873 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:26-439060 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:26-439248 util-scheduler-8620 DEBUG Running task: 292 / 0x4662248
Jul 07 20:44:26-439438 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:26-439637 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:26-439870 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:44:26-440133 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection CMHCKRVP from V8XX
Jul 07 20:44:26-440349 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:44:26-440589 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:26-440798 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:26-440979 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:26-441231 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:44:26-441430 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:26-441637 util-scheduler-8620 DEBUG Adding task: 293 / 0x4d707d0
Jul 07 20:44:26-441886 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:26-442064 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:26-442255 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:26-442427 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:26-442617 util-scheduler-8620 DEBUG Canceling task: 228 / 0x4d707d0
Jul 07 20:44:26-442843 util-scheduler-8620 DEBUG Adding task: 294 / 0x4d707d0
Jul 07 20:44:26-443081 cadet-con-8620 DEBUG next keepalive in 16 s
Jul 07 20:44:26-443314 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:44:26-443551 cadet-con-8620 INFO ===> {           BCK ACK} on connection CMHCKRVP (->V8XX)
Jul 07 20:44:26-443784 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:26-443988 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:26-444281 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 36)
Jul 07 20:44:26-444478 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:26-444704 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:26-444885 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:26-445060 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:26-445288 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:44:26-445505 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:44:26-445721 util-scheduler-8620 DEBUG Adding task: 295 / 0x4d6ff98
Jul 07 20:44:26-445900 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:26-446103 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:26-446279 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:26-446453 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:26-446689 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:26-446872 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:26-447046 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:26-447245 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:26-447472 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:44:26-447823 cadet-tun-8620 DEBUG   cstate triggered rekey
Jul 07 20:44:26-448038 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:26-448348 cadet-tun-8620 INFO   new kx ctx for V8XX
Jul 07 20:44:26-574010 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:44:26-574372 cadet-tun-8620 INFO PE: 00000000
Jul 07 20:44:26-574574 cadet-tun-8620 INFO KM: SY1Y2DBY
Jul 07 20:44:26-574768 cadet-tun-8620 INFO EK: 65Y43XST
Jul 07 20:44:26-574955 cadet-tun-8620 INFO DK: 9J1RHJ8Z
Jul 07 20:44:26-575191 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:26-575392 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:26-575600 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:26-575833 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:26-576014 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:26-576235 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:26-576539 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:26-576739 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:44:26-576976 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:26-577183 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:26-577537 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:26-577742 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:26-577969 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:26-578153 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:26-578328 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:26-578531 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:44:26-578734 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:26-578908 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:26-579083 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:26-579323 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:26-579505 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:26-579680 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:26-579918 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:26-580110 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:26-580286 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:26-580484 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:26-580739 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:26-580946 util-scheduler-8620 DEBUG Adding task: 296 / 0x4d64a70
Jul 07 20:44:26-581139 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:26-581375 util-scheduler-8620 DEBUG Adding task: 297 / 0x46620a0
Jul 07 20:44:26-581589 util-scheduler-8620 DEBUG Running task: 279 / 0x4d63a48
Jul 07 20:44:26-582881 cadet-chn-8620 DEBUG !!! RE-CREATE
Jul 07 20:44:26-583404 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:26-583622 util-scheduler-8620 DEBUG Adding task: 298 / 0x4d5e5d8
Jul 07 20:44:26-584796 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:26-585027 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:26-585261 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:26-585444 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:26-585631 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:26-585814 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:26-585992 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:26-586162 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:26-586388 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:26-586561 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:26-586796 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:26-587009 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:26-587310 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:26-587483 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:26-587668 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:26-591313 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:26-592215 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:26-592429 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:26-592852 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:26-597226 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:26-597553 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:26-597737 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:26-597961 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:26-598261 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:44:26-599156 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection HS92G30M (->KNAS) (96 bytes)
Jul 07 20:44:26-599453 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:26-599736 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:44:26-600006 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:44:26-600275 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:26-601936 cadet-con-8620 DEBUG  *** POLL FWD requested
Jul 07 20:44:26-603099 cadet-con-8620 DEBUG  *** POLL started on request
Jul 07 20:44:26-603582 util-scheduler-8620 DEBUG Adding task: 299 / 0x4d61c34
Jul 07 20:44:26-604132 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:26-604382 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:26-604593 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:26-604912 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 96)
Jul 07 20:44:26-605111 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:26-605359 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:26-605543 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:26-606459 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:26-607798 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS not needed
Jul 07 20:44:26-608325 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:26-608510 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:26-608688 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:26-608934 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:26-609135 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:26-609342 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:26-609551 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:26-609843 util-scheduler-8620 DEBUG Checking readiness of task: 298 / 0x4d5e5d8
Jul 07 20:44:26-610058 util-scheduler-8620 DEBUG Checking readiness of task: 297 / 0x46620a0
Jul 07 20:44:26-610254 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:26-610448 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:26-610645 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:26-610840 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:26-611048 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:26-611239 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:26-611436 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:26-613319 util-scheduler-8620 DEBUG Running task: 298 / 0x4d5e5d8
Jul 07 20:44:26-613515 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:26-613712 util-8620 DEBUG process_notify is running
Jul 07 20:44:26-613886 util-8620 DEBUG client_notify is running
Jul 07 20:44:26-614127 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:26-614437 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:26-614681 util-scheduler-8620 DEBUG Running task: 295 / 0x4d6ff98
Jul 07 20:44:26-614902 util-scheduler-8620 DEBUG Adding task: 300 / 0x4d6ff98
Jul 07 20:44:26-615130 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:26-615333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:26-615540 util-scheduler-8620 DEBUG Adding task: 301 / 0x46620a0
Jul 07 20:44:26-615797 util-scheduler-8620 DEBUG Checking readiness of task: 301 / 0x46620a0
Jul 07 20:44:26-615990 util-scheduler-8620 DEBUG Checking readiness of task: 297 / 0x46620a0
Jul 07 20:44:26-616179 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:26-616368 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:26-616557 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:26-616745 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:26-616934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:26-617123 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:26-617333 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:26-617523 util-scheduler-8620 DEBUG Running task: 301 / 0x46620a0
Jul 07 20:44:26-617706 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:26-617880 util-8620 DEBUG process_notify is running
Jul 07 20:44:26-618049 util-8620 DEBUG client_notify is running
Jul 07 20:44:26-618227 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:26-618422 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:26-618609 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:26-618896 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:27-043886 util-scheduler-8620 DEBUG Checking readiness of task: 297 / 0x46620a0
Jul 07 20:44:27-044266 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-044463 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-044657 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-044850 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-045042 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-045256 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-045449 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-045647 util-scheduler-8620 DEBUG Running task: 297 / 0x46620a0
Jul 07 20:44:27-046073 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:27-046334 util-scheduler-8620 DEBUG Adding task: 302 / 0x4662248
Jul 07 20:44:27-046614 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-046808 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-046999 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-047190 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-047381 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-047572 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-047763 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-047954 util-scheduler-8620 DEBUG Running task: 302 / 0x4662248
Jul 07 20:44:27-048149 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:27-048350 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:27-048604 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:27-048840 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:27-049050 util-scheduler-8620 DEBUG Adding task: 303 / 0x46620a0
Jul 07 20:44:27-059364 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:27-059726 util-scheduler-8620 DEBUG Adding task: 304 / 0x46620a0
Jul 07 20:44:27-060008 util-scheduler-8620 DEBUG Checking readiness of task: 304 / 0x46620a0
Jul 07 20:44:27-060206 util-scheduler-8620 DEBUG Checking readiness of task: 303 / 0x46620a0
Jul 07 20:44:27-060401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-060593 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-060785 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-060976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-061168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-061381 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-061573 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-061769 util-scheduler-8620 DEBUG Running task: 303 / 0x46620a0
Jul 07 20:44:27-061958 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:27-062152 util-8620 DEBUG process_notify is running
Jul 07 20:44:27-062326 util-8620 DEBUG client_notify is running
Jul 07 20:44:27-062517 util-scheduler-8620 DEBUG Canceling task: 300 / 0x4d6ff98
Jul 07 20:44:27-062752 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:44:27-062982 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:27-063237 cadet-p2p-8620 DEBUG Checking 0x539b650 towards CMHCKRVP (->V8XX)
Jul 07 20:44:27-063488 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:27-063672 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:27-063848 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:27-064024 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:27-064202 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:27-064472 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 36)
Jul 07 20:44:27-064669 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:27-064852 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:27-065044 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:27-065936 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:44:27-066122 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:27-066778 cadet-p2p-8620 DEBUG Checking 0x54194a8 towards CMHCKRVP (->V8XX)
Jul 07 20:44:27-067032 cadet-p2p-8620 DEBUG Checking 0x54194a8 towards CMHCKRVP (->V8XX)
Jul 07 20:44:27-067215 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:27-067438 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:27-068042 util-scheduler-8620 DEBUG Adding task: 305 / 0x4d6ff98
Jul 07 20:44:27-068227 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:27-068406 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:27-068978 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:27-069159 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:27-069376 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:27-069621 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:27-070192 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:27-070374 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:27-070577 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:27-071156 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:44:27-071346 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:27-071559 util-scheduler-8620 DEBUG Adding task: 306 / 0x4d6ff98
Jul 07 20:44:27-071782 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:27-072361 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:27-072598 util-scheduler-8620 DEBUG Adding task: 307 / 0x46620a0
Jul 07 20:44:27-072804 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:27-073448 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:27-073653 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:27-073912 util-scheduler-8620 DEBUG Checking readiness of task: 307 / 0x46620a0
Jul 07 20:44:27-075769 util-scheduler-8620 DEBUG Checking readiness of task: 304 / 0x46620a0
Jul 07 20:44:27-075973 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-076168 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-076758 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-076953 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-077147 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-077360 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-077925 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-078129 util-scheduler-8620 DEBUG Running task: 307 / 0x46620a0
Jul 07 20:44:27-078322 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:27-078875 util-8620 DEBUG process_notify is running
Jul 07 20:44:27-079055 util-8620 DEBUG client_notify is running
Jul 07 20:44:27-079239 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:27-079442 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:27-080006 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:27-080246 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:27-080456 util-scheduler-8620 DEBUG Running task: 305 / 0x4d6ff98
Jul 07 20:44:27-081118 util-scheduler-8620 DEBUG Canceling task: 306 / 0x4d6ff98
Jul 07 20:44:27-081404 util-scheduler-8620 DEBUG Adding task: 308 / 0x4d6ff98
Jul 07 20:44:27-081653 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:27-082280 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:27-082520 util-scheduler-8620 DEBUG Adding task: 309 / 0x46620a0
Jul 07 20:44:27-082793 util-scheduler-8620 DEBUG Checking readiness of task: 309 / 0x46620a0
Jul 07 20:44:27-083405 util-scheduler-8620 DEBUG Checking readiness of task: 304 / 0x46620a0
Jul 07 20:44:27-083621 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-083828 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-084025 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-084653 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-084856 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-085056 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-085664 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-085880 util-scheduler-8620 DEBUG Running task: 304 / 0x46620a0
Jul 07 20:44:27-086742 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:27-087072 util-scheduler-8620 DEBUG Adding task: 310 / 0x4662248
Jul 07 20:44:27-087297 util-scheduler-8620 DEBUG Running task: 309 / 0x46620a0
Jul 07 20:44:27-087860 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:27-088045 util-8620 DEBUG process_notify is running
Jul 07 20:44:27-088220 util-8620 DEBUG client_notify is running
Jul 07 20:44:27-088401 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:27-088968 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:27-089163 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:27-089448 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:27-090335 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-090533 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-091100 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-091297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-091490 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-091682 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-092244 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-092439 util-scheduler-8620 DEBUG Running task: 310 / 0x4662248
Jul 07 20:44:27-092633 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:27-092834 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:27-093455 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:27-093642 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:27-093855 util-scheduler-8620 DEBUG Adding task: 311 / 0x46620a0
Jul 07 20:44:27-094472 util-scheduler-8620 DEBUG Checking readiness of task: 311 / 0x46620a0
Jul 07 20:44:27-094669 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-094863 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-095054 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-095618 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-095815 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-096007 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-096563 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-096761 util-scheduler-8620 DEBUG Running task: 311 / 0x46620a0
Jul 07 20:44:27-097785 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:27-098023 util-scheduler-8620 DEBUG Adding task: 312 / 0x4662248
Jul 07 20:44:27-098279 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-098866 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-099073 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-099268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-099461 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-100046 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-100248 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-100445 util-scheduler-8620 DEBUG Running task: 312 / 0x4662248
Jul 07 20:44:27-101072 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:27-101304 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:27-101532 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:27-102104 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:27-102317 util-scheduler-8620 DEBUG Adding task: 313 / 0x46620a0
Jul 07 20:44:27-102503 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:27-102722 util-scheduler-8620 DEBUG Adding task: 314 / 0x46620a0
Jul 07 20:44:27-103346 util-scheduler-8620 DEBUG Checking readiness of task: 314 / 0x46620a0
Jul 07 20:44:27-103545 util-scheduler-8620 DEBUG Checking readiness of task: 313 / 0x46620a0
Jul 07 20:44:27-103738 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-103929 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-104513 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-104705 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-104895 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-105470 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-105666 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-105862 util-scheduler-8620 DEBUG Running task: 313 / 0x46620a0
Jul 07 20:44:27-106048 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:27-106601 util-8620 DEBUG process_notify is running
Jul 07 20:44:27-106776 util-8620 DEBUG client_notify is running
Jul 07 20:44:27-106964 util-scheduler-8620 DEBUG Canceling task: 308 / 0x4d6ff98
Jul 07 20:44:27-107188 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:27-107407 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:27-107645 cadet-p2p-8620 DEBUG Checking 0x54194a8 towards CMHCKRVP (->V8XX)
Jul 07 20:44:27-107878 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:27-108055 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:27-108243 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:27-108532 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:27-108726 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:27-108905 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:27-109092 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:27-109302 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:27-109480 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:27-109666 util-scheduler-8620 DEBUG Canceling task: 294 / 0x4d707d0
Jul 07 20:44:27-109880 util-scheduler-8620 DEBUG Adding task: 315 / 0x4d707d0
Jul 07 20:44:27-110130 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:27-110300 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:27-110480 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:27-110680 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:27-110854 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:27-111028 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:27-111227 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:27-111430 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:27-111611 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:27-111793 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:27-111993 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:27-112241 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:27-604228 util-scheduler-8620 DEBUG Checking readiness of task: 314 / 0x46620a0
Jul 07 20:44:27-604603 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-604799 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-604990 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-605180 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-605396 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-605590 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-605803 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-605998 util-scheduler-8620 DEBUG Running task: 299 / 0x4d61c34
Jul 07 20:44:27-607924 cadet-con-8620 DEBUG  *** Polling connection HS92G30M (->KNAS) FWD
Jul 07 20:44:27-609257 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:44:27-610236 cadet-con-8620 INFO --> {              POLL} ( 0) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:27-611702 cadet-con-8620 DEBUG  poll 0
Jul 07 20:44:27-612070 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:27-612333 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:27-612550 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:27-612862 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:27-613063 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:27-613746 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:27-613942 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:27-614431 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:27-615484 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:27-615714 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:27-615949 util-scheduler-8620 DEBUG Adding task: 316 / 0x4d5c9e8
Jul 07 20:44:27-616133 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:27-616340 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:27-616517 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:27-616693 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:27-616937 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on HS92G30M (->KNAS)
Jul 07 20:44:27-617122 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:27-617323 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:27-617560 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:27-617753 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:27-617929 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:27-618129 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:27-618744 util-scheduler-8620 DEBUG Checking readiness of task: 314 / 0x46620a0
Jul 07 20:44:27-618944 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-619136 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-619326 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-619516 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-619705 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-619894 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-620083 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-620275 util-scheduler-8620 DEBUG Running task: 316 / 0x4d5c9e8
Jul 07 20:44:27-620497 util-scheduler-8620 DEBUG Adding task: 317 / 0x4d5c9e8
Jul 07 20:44:27-620719 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:27-620936 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:27-621144 util-scheduler-8620 DEBUG Adding task: 318 / 0x46620a0
Jul 07 20:44:27-621405 util-scheduler-8620 DEBUG Checking readiness of task: 318 / 0x46620a0
Jul 07 20:44:27-621598 util-scheduler-8620 DEBUG Checking readiness of task: 314 / 0x46620a0
Jul 07 20:44:27-621788 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:27-621976 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:27-622165 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:27-622353 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:27-622541 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:27-622729 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:27-622917 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:27-623108 util-scheduler-8620 DEBUG Running task: 318 / 0x46620a0
Jul 07 20:44:27-623293 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:27-623472 util-8620 DEBUG process_notify is running
Jul 07 20:44:27-623645 util-8620 DEBUG client_notify is running
Jul 07 20:44:27-623824 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:27-624046 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:27-624237 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:27-624560 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:28-723704 util-scheduler-8620 DEBUG Checking readiness of task: 314 / 0x46620a0
Jul 07 20:44:28-758767 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:28-759056 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:28-759250 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:28-759441 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:28-759631 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:28-759821 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:28-760010 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:28-760206 util-scheduler-8620 DEBUG Running task: 314 / 0x46620a0
Jul 07 20:44:28-760629 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:28-760885 util-scheduler-8620 DEBUG Adding task: 319 / 0x4662248
Jul 07 20:44:28-761167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:28-761531 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:28-761723 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:28-761913 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:28-762348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:28-762648 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:28-762886 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:28-763082 util-scheduler-8620 DEBUG Running task: 319 / 0x4662248
Jul 07 20:44:28-763280 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:28-763596 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:28-763844 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:28-764058 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:28-764275 util-scheduler-8620 DEBUG Adding task: 320 / 0x46620a0
Jul 07 20:44:28-764472 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:28-764689 util-scheduler-8620 DEBUG Adding task: 321 / 0x46620a0
Jul 07 20:44:28-764965 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:28-765220 util-scheduler-8620 DEBUG Checking readiness of task: 320 / 0x46620a0
Jul 07 20:44:28-765418 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:28-765610 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:28-765805 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:28-765998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:28-766191 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:28-766385 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:28-766577 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:28-766773 util-scheduler-8620 DEBUG Running task: 320 / 0x46620a0
Jul 07 20:44:28-766963 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:28-767146 util-8620 DEBUG process_notify is running
Jul 07 20:44:28-767323 util-8620 DEBUG client_notify is running
Jul 07 20:44:28-767516 util-scheduler-8620 DEBUG Canceling task: 317 / 0x4d5c9e8
Jul 07 20:44:28-767750 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:28-768080 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:28-768351 cadet-p2p-8620 DEBUG Checking 0x5428728 towards HS92G30M (->KNAS)
Jul 07 20:44:28-768587 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:28-768768 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:28-768959 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:44:28-769254 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:28-769635 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:28-769822 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:28-770012 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:44:28-770358 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:28-771548 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:44:28-773504 util-scheduler-8620 DEBUG Adding task: 322 / 0x4d61c34
Jul 07 20:44:28-774661 cadet-con-8620 DEBUG  task 322
Jul 07 20:44:28-774856 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:28-775182 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:28-775414 cadet-p2p-8620 DEBUG Checking 0x5422aa0 towards HS92G30M (->KNAS)
Jul 07 20:44:28-775650 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:28-775833 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:28-776008 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:28-776473 cadet-p2p-8620 DEBUG Checking 0x5422aa0 towards HS92G30M (->KNAS)
Jul 07 20:44:28-776710 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:28-776893 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:28-777066 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:28-777257 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:28-777458 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:28-777632 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:28-777808 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:28-778046 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:28-778242 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:28-778423 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:28-778638 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:28-778850 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:28-779035 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:28-779217 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:28-779410 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:28-780689 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:30-583975 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-584356 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-584553 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-584745 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-584936 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-585127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-585343 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-585534 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-585728 util-scheduler-8620 DEBUG Running task: 243 / 0x4d68be8
Jul 07 20:44:30-586017 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:44:30-586195 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:30-586449 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:30-586642 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:30-586875 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:30-587085 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:30-587422 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:30-587624 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:30-587851 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:30-588035 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:30-588211 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:30-588420 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:30-588636 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:30-588862 util-scheduler-8620 DEBUG Adding task: 323 / 0x4d683b0
Jul 07 20:44:30-589043 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:30-589271 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:30-589448 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:30-589625 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:30-589865 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:30-590048 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:30-590225 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:30-590425 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:30-590680 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-590889 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-591079 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-591269 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-591458 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-591734 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-591926 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-592115 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-592305 util-scheduler-8620 DEBUG Running task: 323 / 0x4d683b0
Jul 07 20:44:30-592516 util-scheduler-8620 DEBUG Adding task: 324 / 0x4d683b0
Jul 07 20:44:30-592738 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:30-592942 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:30-593150 util-scheduler-8620 DEBUG Adding task: 325 / 0x46620a0
Jul 07 20:44:30-593418 util-scheduler-8620 DEBUG Checking readiness of task: 325 / 0x46620a0
Jul 07 20:44:30-593610 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-593800 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-593988 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-594178 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-594367 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-594555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-594744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-594932 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-595124 util-scheduler-8620 DEBUG Running task: 325 / 0x46620a0
Jul 07 20:44:30-595309 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:30-595487 util-8620 DEBUG process_notify is running
Jul 07 20:44:30-595659 util-8620 DEBUG client_notify is running
Jul 07 20:44:30-595838 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:30-596036 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:30-596227 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:30-596529 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:30-773832 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-774225 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-774423 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-774615 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-774806 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-774996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-775186 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-775376 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-775569 util-scheduler-8620 DEBUG Running task: 322 / 0x4d61c34
Jul 07 20:44:30-776091 cadet-con-8620 DEBUG  *** Polling connection HS92G30M (->KNAS) FWD
Jul 07 20:44:30-776432 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:44:30-776718 cadet-con-8620 INFO --> {              POLL} ( 0) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:30-777003 cadet-con-8620 DEBUG  poll 0
Jul 07 20:44:30-777187 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:30-777455 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:30-777668 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:30-777983 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:30-778183 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:30-778410 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:30-778593 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:30-778768 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:30-778978 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:30-779196 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:30-779421 util-scheduler-8620 DEBUG Adding task: 326 / 0x4d5c9e8
Jul 07 20:44:30-779603 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:30-779807 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:30-779983 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:30-780158 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:30-780397 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on HS92G30M (->KNAS)
Jul 07 20:44:30-780580 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:30-780755 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:30-780989 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:30-781183 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:30-781386 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:30-781585 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:30-781840 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-782031 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-782220 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-782409 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-782597 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-782786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-782974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-783162 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-783351 util-scheduler-8620 DEBUG Running task: 326 / 0x4d5c9e8
Jul 07 20:44:30-783561 util-scheduler-8620 DEBUG Adding task: 327 / 0x4d5c9e8
Jul 07 20:44:30-783783 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:30-783985 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:30-784192 util-scheduler-8620 DEBUG Adding task: 328 / 0x46620a0
Jul 07 20:44:30-784434 util-scheduler-8620 DEBUG Checking readiness of task: 328 / 0x46620a0
Jul 07 20:44:30-784626 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:30-784833 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:30-785037 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:30-785243 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:30-785434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:30-785624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:30-785812 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:30-786010 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:30-786202 util-scheduler-8620 DEBUG Running task: 328 / 0x46620a0
Jul 07 20:44:30-786387 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:30-786568 util-8620 DEBUG process_notify is running
Jul 07 20:44:30-786740 util-8620 DEBUG client_notify is running
Jul 07 20:44:30-786919 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:30-787113 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:30-787304 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:30-787626 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:31-581391 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:31-581777 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-581973 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-582165 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-582357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-582547 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-582737 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-582927 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-583121 util-scheduler-8620 DEBUG Running task: 296 / 0x4d64a70
Jul 07 20:44:31-583362 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:31-583611 cadet-tun-8620 DEBUG  kx started 5 s ago
Jul 07 20:44:31-583818 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:31-584019 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:31-584221 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:31-584457 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:31-584638 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:31-584859 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:31-585153 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:31-585380 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:31-585620 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:31-585827 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:31-586146 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:31-586346 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:31-586572 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:31-586755 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:31-586936 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:31-587143 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:31-587385 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:31-587611 util-scheduler-8620 DEBUG Adding task: 329 / 0x4d6ff98
Jul 07 20:44:31-587792 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:31-587996 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:31-588171 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:31-588347 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:31-588615 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:31-588811 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:31-588990 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:31-589211 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:31-589492 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:31-589691 util-scheduler-8620 DEBUG Adding task: 330 / 0x4d64a70
Jul 07 20:44:31-589952 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:31-590144 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-590333 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-590523 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-590712 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-590900 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-591089 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-591277 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-591465 util-scheduler-8620 DEBUG Running task: 329 / 0x4d6ff98
Jul 07 20:44:31-591674 util-scheduler-8620 DEBUG Adding task: 331 / 0x4d6ff98
Jul 07 20:44:31-591896 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:31-592100 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:31-592307 util-scheduler-8620 DEBUG Adding task: 332 / 0x46620a0
Jul 07 20:44:31-592550 util-scheduler-8620 DEBUG Checking readiness of task: 332 / 0x46620a0
Jul 07 20:44:31-592743 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:31-592932 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-593121 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-593335 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-593524 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-593715 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-593904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-594093 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-594286 util-scheduler-8620 DEBUG Running task: 332 / 0x46620a0
Jul 07 20:44:31-594471 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:31-594649 util-8620 DEBUG process_notify is running
Jul 07 20:44:31-594821 util-8620 DEBUG client_notify is running
Jul 07 20:44:31-595001 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:31-595197 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:31-595389 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:31-595718 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:31-708694 util-scheduler-8620 DEBUG Checking readiness of task: 321 / 0x46620a0
Jul 07 20:44:31-709051 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-709276 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-709470 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-709680 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-709920 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-710113 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-710303 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-710499 util-scheduler-8620 DEBUG Running task: 321 / 0x46620a0
Jul 07 20:44:31-710922 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:31-711205 util-scheduler-8620 DEBUG Adding task: 333 / 0x4662248
Jul 07 20:44:31-711484 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-711678 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-711869 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-712059 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-712249 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-712438 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-712628 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-712818 util-scheduler-8620 DEBUG Running task: 333 / 0x4662248
Jul 07 20:44:31-713010 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:31-713262 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:31-713513 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:31-713719 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:31-713926 util-scheduler-8620 DEBUG Adding task: 334 / 0x46620a0
Jul 07 20:44:31-714114 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:31-714321 util-scheduler-8620 DEBUG Adding task: 335 / 0x46620a0
Jul 07 20:44:31-714568 util-scheduler-8620 DEBUG Checking readiness of task: 335 / 0x46620a0
Jul 07 20:44:31-714761 util-scheduler-8620 DEBUG Checking readiness of task: 334 / 0x46620a0
Jul 07 20:44:31-714954 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-715144 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-715336 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-715527 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-715717 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-715907 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-716096 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-716288 util-scheduler-8620 DEBUG Running task: 334 / 0x46620a0
Jul 07 20:44:31-716474 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:31-716653 util-8620 DEBUG process_notify is running
Jul 07 20:44:31-716827 util-8620 DEBUG client_notify is running
Jul 07 20:44:31-717017 util-scheduler-8620 DEBUG Canceling task: 324 / 0x4d683b0
Jul 07 20:44:31-717265 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:31-717486 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:44:31-717726 cadet-p2p-8620 DEBUG Checking 0x542ba48 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:31-717961 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:31-718139 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:31-718310 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:31-718482 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:31-718663 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:31-718928 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:31-719123 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:31-719304 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:31-719493 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:31-719688 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:31-719901 util-scheduler-8620 DEBUG Adding task: 336 / 0x4d68be8
Jul 07 20:44:31-720139 cadet-con-8620 DEBUG next keepalive in 16 s
Jul 07 20:44:31-720311 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:31-720493 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:31-720694 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:31-720869 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:31-721062 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:31-721928 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:31-722147 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:31-722334 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:31-722515 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:31-722706 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:31-723498 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:31-784803 util-scheduler-8620 DEBUG Checking readiness of task: 335 / 0x46620a0
Jul 07 20:44:31-785509 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-785709 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-785902 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-786442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-786637 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-786832 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-787023 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-787570 util-scheduler-8620 DEBUG Running task: 335 / 0x46620a0
Jul 07 20:44:31-787992 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:31-788601 util-scheduler-8620 DEBUG Adding task: 337 / 0x4662248
Jul 07 20:44:31-788878 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-789437 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-789636 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-789828 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-790018 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-790564 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-790757 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-790948 util-scheduler-8620 DEBUG Running task: 337 / 0x4662248
Jul 07 20:44:31-791489 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:31-791696 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:31-791924 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:31-792479 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:31-792691 util-scheduler-8620 DEBUG Adding task: 338 / 0x46620a0
Jul 07 20:44:31-792878 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:31-793082 util-scheduler-8620 DEBUG Adding task: 339 / 0x46620a0
Jul 07 20:44:31-793702 util-scheduler-8620 DEBUG Checking readiness of task: 339 / 0x46620a0
Jul 07 20:44:31-793899 util-scheduler-8620 DEBUG Checking readiness of task: 338 / 0x46620a0
Jul 07 20:44:31-794514 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:31-794759 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:31-794961 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:31-795608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:31-795832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:31-796031 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:31-796681 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:31-796908 util-scheduler-8620 DEBUG Running task: 338 / 0x46620a0
Jul 07 20:44:31-797670 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:31-797863 util-8620 DEBUG process_notify is running
Jul 07 20:44:31-798067 util-8620 DEBUG client_notify is running
Jul 07 20:44:31-798644 util-scheduler-8620 DEBUG Canceling task: 327 / 0x4d5c9e8
Jul 07 20:44:31-798893 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:31-799115 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:31-799741 cadet-p2p-8620 DEBUG Checking 0x542d228 towards HS92G30M (->KNAS)
Jul 07 20:44:31-799978 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:31-800155 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:31-800731 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:44:31-801007 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:31-801595 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:31-801782 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:31-801972 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:44:31-802146 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:31-802949 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:44:31-803179 util-scheduler-8620 DEBUG Adding task: 340 / 0x4d61c34
Jul 07 20:44:31-803912 cadet-con-8620 DEBUG  task 340
Jul 07 20:44:31-804105 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:31-804660 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:31-804891 cadet-p2p-8620 DEBUG Checking 0x5422aa0 towards HS92G30M (->KNAS)
Jul 07 20:44:31-805126 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:31-805704 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:31-805884 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:31-806114 cadet-p2p-8620 DEBUG Checking 0x5422aa0 towards HS92G30M (->KNAS)
Jul 07 20:44:31-806739 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:31-806926 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:44:31-807099 cadet-con-8620 DEBUG  not sendable
Jul 07 20:44:31-807658 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:31-807865 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:31-808041 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:31-808216 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:31-808456 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:31-808651 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:44:31-808828 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:44:31-809027 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:31-809252 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:31-809436 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:31-809616 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:31-809807 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:31-811022 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:33-041745 util-scheduler-8620 DEBUG Checking readiness of task: 339 / 0x46620a0
Jul 07 20:44:33-042132 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:33-042332 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:33-042526 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:33-042734 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:33-042928 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:33-043121 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:33-043313 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:33-043510 util-scheduler-8620 DEBUG Running task: 339 / 0x46620a0
Jul 07 20:44:33-043935 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:33-044195 util-scheduler-8620 DEBUG Adding task: 341 / 0x4662248
Jul 07 20:44:33-044503 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:33-044699 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:33-044891 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:33-045083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:33-045773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:33-045972 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:33-046165 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:33-046358 util-scheduler-8620 DEBUG Running task: 341 / 0x4662248
Jul 07 20:44:33-046552 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:44:33-046755 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:44:33-046989 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `KNAS'
Jul 07 20:44:33-047256 cadet-con-8620 INFO <-- {                KX} on connection HS92G30M from KNAS
Jul 07 20:44:33-047503 cadet-con-8620 DEBUG  on connection HS92G30M (->KNAS)
Jul 07 20:44:33-047735 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:33-047948 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:33-048199 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:33-048410 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:33-048600 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:33-048792 util-scheduler-8620 DEBUG Canceling task: 269 / 0x4d61c30
Jul 07 20:44:33-049019 util-scheduler-8620 DEBUG Adding task: 342 / 0x4d61c30
Jul 07 20:44:33-049225 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:33-049491 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:33-049713 util-scheduler-8620 DEBUG Adding task: 343 / 0x4d5e5d8
Jul 07 20:44:33-049897 cadet-tun-8620 DEBUG kx message received
Jul 07 20:44:33-050275 cadet-tun-8620 INFO <=== PONG for KNAS
Jul 07 20:44:33-050988 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:33-051207 util-scheduler-8620 DEBUG Adding task: 344 / 0x46620a0
Jul 07 20:44:33-051469 util-scheduler-8620 DEBUG Checking readiness of task: 344 / 0x46620a0
Jul 07 20:44:33-051666 util-scheduler-8620 DEBUG Checking readiness of task: 343 / 0x4d5e5d8
Jul 07 20:44:33-051861 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:33-052053 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:33-052246 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:33-052438 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:33-052629 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:33-052821 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:33-053013 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:33-053233 util-scheduler-8620 DEBUG Running task: 343 / 0x4d5e5d8
Jul 07 20:44:33-053514 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:33-053699 util-8620 DEBUG process_notify is running
Jul 07 20:44:33-053876 util-8620 DEBUG client_notify is running
Jul 07 20:44:33-054116 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:33-054328 util-scheduler-8620 DEBUG Adding task: 345 / 0x4d5e5d8
Jul 07 20:44:33-054533 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:33-054849 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:33-055050 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:33-055295 util-scheduler-8620 DEBUG Checking readiness of task: 345 / 0x4d5e5d8
Jul 07 20:44:33-055490 util-scheduler-8620 DEBUG Checking readiness of task: 344 / 0x46620a0
Jul 07 20:44:33-055682 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:33-055893 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:33-056086 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:33-056276 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:33-056467 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:33-056657 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:33-056848 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:33-057041 util-scheduler-8620 DEBUG Running task: 345 / 0x4d5e5d8
Jul 07 20:44:33-057253 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:33-057445 util-8620 DEBUG process_notify is running
Jul 07 20:44:33-057617 util-8620 DEBUG client_notify is running
Jul 07 20:44:33-057832 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:44:33-058126 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:34-095893 util-scheduler-8620 DEBUG Checking readiness of task: 344 / 0x46620a0
Jul 07 20:44:34-096288 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:34-096708 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:34-096914 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:34-097167 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:34-097399 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:34-097594 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:34-097786 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:34-097984 util-scheduler-8620 DEBUG Running task: 344 / 0x46620a0
Jul 07 20:44:34-098410 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:34-098669 util-scheduler-8620 DEBUG Adding task: 346 / 0x4662248
Jul 07 20:44:34-098951 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:34-099145 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:34-099337 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:34-099529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:34-099720 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:34-099925 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:34-100116 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:34-100305 util-scheduler-8620 DEBUG Running task: 346 / 0x4662248
Jul 07 20:44:34-100496 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:34-100695 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:34-100943 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:34-101150 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:34-101380 util-scheduler-8620 DEBUG Adding task: 347 / 0x46620a0
Jul 07 20:44:34-101567 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:34-101773 util-scheduler-8620 DEBUG Adding task: 348 / 0x46620a0
Jul 07 20:44:34-102017 util-scheduler-8620 DEBUG Checking readiness of task: 348 / 0x46620a0
Jul 07 20:44:34-102208 util-scheduler-8620 DEBUG Checking readiness of task: 347 / 0x46620a0
Jul 07 20:44:34-102399 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:34-102589 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:34-102778 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:34-102967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:34-103181 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:34-103372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:34-103561 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:34-103753 util-scheduler-8620 DEBUG Running task: 347 / 0x46620a0
Jul 07 20:44:34-103939 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:34-104117 util-8620 DEBUG process_notify is running
Jul 07 20:44:34-104289 util-8620 DEBUG client_notify is running
Jul 07 20:44:34-104478 util-scheduler-8620 DEBUG Canceling task: 331 / 0x4d6ff98
Jul 07 20:44:34-104703 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:34-104924 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:34-105163 cadet-p2p-8620 DEBUG Checking 0x542ef18 towards CMHCKRVP (->V8XX)
Jul 07 20:44:34-105417 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:34-105594 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:34-105784 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:34-106066 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:34-106263 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:34-106443 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:34-106632 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:34-106820 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:34-106998 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:34-107181 util-scheduler-8620 DEBUG Canceling task: 315 / 0x4d707d0
Jul 07 20:44:34-107396 util-scheduler-8620 DEBUG Adding task: 349 / 0x4d707d0
Jul 07 20:44:34-107647 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:34-107819 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:34-108002 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:34-108202 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:34-108376 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:34-108551 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:34-108751 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:34-108955 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:34-109137 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:34-109338 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:34-109529 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:34-109791 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:35-043262 util-scheduler-8620 DEBUG Checking readiness of task: 348 / 0x46620a0
Jul 07 20:44:35-043655 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-043855 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-044050 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-044244 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-044437 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-044630 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-044824 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:35-045033 util-scheduler-8620 DEBUG Running task: 348 / 0x46620a0
Jul 07 20:44:35-045489 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:35-045752 util-scheduler-8620 DEBUG Adding task: 350 / 0x4662248
Jul 07 20:44:35-046034 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-046229 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-046421 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-046612 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-046833 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-047026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-047218 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:35-047409 util-scheduler-8620 DEBUG Running task: 350 / 0x4662248
Jul 07 20:44:35-047607 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:35-047812 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:35-048045 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:35-048942 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:35-050440 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-050667 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-051843 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:35-053136 cadet-con-8620 DEBUG   ACK 64 (was 0)
Jul 07 20:44:35-054945 cadet-con-8620 DEBUG   Cancel poll
Jul 07 20:44:35-055373 util-scheduler-8620 DEBUG Canceling task: 340 / 0x4d61c34
Jul 07 20:44:35-057065 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-057739 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-057968 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-059005 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:35-059199 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:35-059379 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:35-060344 cadet-p2p-8620 DEBUG   sendable!!
Jul 07 20:44:35-061581 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:44:35-061812 util-scheduler-8620 DEBUG Adding task: 351 / 0x4d5c9e8
Jul 07 20:44:35-061998 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:35-062693 util-scheduler-8620 DEBUG Adding task: 352 / 0x4662248
Jul 07 20:44:35-062951 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-063148 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-063341 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-063543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-063735 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-063927 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-064118 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:35-064310 util-scheduler-8620 DEBUG Running task: 352 / 0x4662248
Jul 07 20:44:35-064513 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:44:35-064712 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:44:35-064931 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:44:35-065497 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:35-067407 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:35-067924 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-068145 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:35-069044 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-069284 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-070822 cadet-con-8620 DEBUG  PID 0 (expected 0+)
Jul 07 20:44:35-072082 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:35-072284 util-scheduler-8620 DEBUG Canceling task: 342 / 0x4d61c30
Jul 07 20:44:35-072513 util-scheduler-8620 DEBUG Adding task: 353 / 0x4d61c30
Jul 07 20:44:35-073659 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:35-074183 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:35-074414 util-scheduler-8620 DEBUG Adding task: 354 / 0x4d5e5d8
Jul 07 20:44:35-075786 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:35-075989 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:35-079596 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:35-081399 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:35-082175 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:35-088102 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on KNAS
Jul 07 20:44:35-092473 cadet-chn-8620 DEBUG   channel confirm FWD KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-094792 cadet-chn-8620 DEBUG   !! retry timer confirm 500 ms
Jul 07 20:44:35-095308 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:35-095500 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:35-095691 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:35-095876 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:35-096057 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:35-096230 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:35-096451 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-096628 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:35-096868 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:35-097055 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:35-099077 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-100691 cadet-loc-8620 DEBUG send local FWD ack on 80000001 towards 0x4d5c6d8
Jul 07 20:44:35-104603 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:44:35-108027 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:44:35-108266 util-scheduler-8620 DEBUG Adding task: 355 / 0x4d5c418
Jul 07 20:44:35-110622 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:44:35-112438 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:44:35-113320 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:35-113514 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:35-114007 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:44:35-114192 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:35-114519 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:35-114871 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:44:35-115171 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:44:35-115694 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:35-116055 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:35-116333 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:44:35-116515 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:35-118488 core-api-8620 DEBUG Aborting transmission request to core for 96 bytes to `KNAS'
Jul 07 20:44:35-120464 util-scheduler-8620 DEBUG Canceling task: 351 / 0x4d5c9e8
Jul 07 20:44:35-123056 cadet-chn-8620 DEBUG   sending channel BCK ack for channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-124450 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-125454 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:35-125664 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:35-125846 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:35-126029 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:35-126212 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:35-126390 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:35-126561 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:35-126777 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-126961 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:35-127196 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:35-127576 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:35-127886 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:35-128061 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:35-128275 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:35-131891 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:35-133069 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:35-133284 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:35-133477 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:35-136953 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:35-137359 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:35-137549 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:35-137779 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:35-137974 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:44:35-139140 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (88 bytes)
Jul 07 20:44:35-139355 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:35-139536 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:44:35-139712 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:35-139885 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:35-140064 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:35-140311 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-140641 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-140958 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 88)
Jul 07 20:44:35-141158 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:35-141410 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:35-141592 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:35-141768 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:35-141975 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 88 bytes
Jul 07 20:44:35-142192 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:35-142419 util-scheduler-8620 DEBUG Adding task: 356 / 0x4d5c9e8
Jul 07 20:44:35-142601 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:35-142817 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:35-142994 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:35-143170 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:35-143410 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-143605 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:35-143783 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:35-144104 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:35-146038 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:35-147051 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:35-148842 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:35-150056 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:35-152275 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:35-153579 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:44:35-155074 cadet-con-8620 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 20:44:35-164415 cadet-con-8620 INFO --> {               ACK} ( 64) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:35-166098 cadet-con-8620 DEBUG  ack 64
Jul 07 20:44:35-166443 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:35-166692 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-166904 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-167206 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:35-167406 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:35-167637 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:35-167821 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:35-167996 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:35-168204 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:35-168407 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:35-168608 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:35-168784 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:35-169023 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-169238 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:44:35-169417 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:35-169652 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-169846 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:35-170022 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:35-170228 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:35-170963 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:35-171192 util-scheduler-8620 DEBUG Adding task: 357 / 0x46620a0
Jul 07 20:44:35-171602 util-scheduler-8620 DEBUG Checking readiness of task: 357 / 0x46620a0
Jul 07 20:44:35-171805 util-scheduler-8620 DEBUG Checking readiness of task: 355 / 0x4d5c418
Jul 07 20:44:35-172095 util-scheduler-8620 DEBUG Checking readiness of task: 354 / 0x4d5e5d8
Jul 07 20:44:35-172288 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-172480 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-172670 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-172860 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-173051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-173266 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-173458 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:35-173653 util-scheduler-8620 DEBUG Running task: 354 / 0x4d5e5d8
Jul 07 20:44:35-173840 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:35-174021 util-8620 DEBUG process_notify is running
Jul 07 20:44:35-174193 util-8620 DEBUG client_notify is running
Jul 07 20:44:35-174539 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:35-174874 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:35-175089 util-scheduler-8620 DEBUG Running task: 355 / 0x4d5c418
Jul 07 20:44:35-175432 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:44:35-175625 util-8620 DEBUG process_notify is running
Jul 07 20:44:35-179232 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:44:35-180856 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:44:35-181185 util-scheduler-8620 DEBUG Running task: 356 / 0x4d5c9e8
Jul 07 20:44:35-181430 util-scheduler-8620 DEBUG Adding task: 358 / 0x4d5c9e8
Jul 07 20:44:35-181660 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:35-181865 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:35-182069 util-scheduler-8620 DEBUG Adding task: 359 / 0x46620a0
Jul 07 20:44:35-182322 util-scheduler-8620 DEBUG Checking readiness of task: 359 / 0x46620a0
Jul 07 20:44:35-182516 util-scheduler-8620 DEBUG Checking readiness of task: 357 / 0x46620a0
Jul 07 20:44:35-182708 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-182899 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-183090 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-183281 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-183470 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-183660 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-183849 util-scheduler-8620 DEBUG Checking readiness of task: 35 / 0x4d5c418
Jul 07 20:44:35-184041 util-scheduler-8620 DEBUG Running task: 35 / 0x4d5c418
Jul 07 20:44:35-184547 util-8620 DEBUG receive_ready read 88/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:44:35-184779 util-8620 DEBUG Server receives 88 bytes from `<unbound UNIX client>'.
Jul 07 20:44:35-184976 util-8620 DEBUG Server-mst receives 88 bytes with 0 bytes already in private buffer
Jul 07 20:44:35-185164 util-8620 DEBUG Server-mst has 88 bytes left in inbound buffer
Jul 07 20:44:35-185375 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:44:35-185566 util-8620 DEBUG Server schedules transmission of 88-byte message of type 285 to client.
Jul 07 20:44:35-185783 util-scheduler-8620 DEBUG Adding task: 360 / 0x4d5c578
Jul 07 20:44:35-186898 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:44:35-188234 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:35-189582 cadet-loc-8620 DEBUG   on channel 80000001
Jul 07 20:44:35-193264 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:44:35-194508 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-196027 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:44:35-198472 cadet-chn-8620 DEBUG !!! SAVE 0 {              DATA}
Jul 07 20:44:35-200126 cadet-chn-8620 DEBUG   at 0x544b120
Jul 07 20:44:35-202466 cadet-chn-8620 DEBUG   new chq: 0x544b0a0
Jul 07 20:44:35-203120 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:35-203329 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:35-203512 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:35-203696 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:35-203894 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:35-204073 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:35-204270 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:35-204604 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-204780 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:35-205018 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:35-205226 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:35-205525 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:35-205698 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:35-205881 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:35-209686 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:35-211042 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:35-211232 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:35-211424 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:35-214715 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:35-214959 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:35-215142 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:35-215364 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:35-216158 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:35-216449 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (172 bytes)
Jul 07 20:44:35-216651 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:35-216831 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:44:35-217005 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:35-217665 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:35-217913 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:35-218133 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:35-218469 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 172)
Jul 07 20:44:35-218721 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:35-218950 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:35-219135 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:35-219311 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:35-219513 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:35-219716 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:35-219915 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:35-220092 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:35-220332 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-220517 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:44:35-220693 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:35-220936 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-221130 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:35-221333 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:35-221566 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:35-221758 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:35-221935 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:35-222133 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:35-223306 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:35-223493 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:35-223679 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:35-223861 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:35-224038 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:35-224207 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:35-224423 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-224596 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:35-224828 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:35-225022 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:35-225814 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:35-227350 cadet-chn-8620 DEBUG  gap ok: 0 - 1
Jul 07 20:44:35-228182 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:35-228368 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:35-228553 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:35-228734 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:35-228910 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:35-229079 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:35-229320 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-229494 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:35-229722 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:35-229906 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:35-230930 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:44:35-231749 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:35-232116 cadet-loc-8620 DEBUG send local FWD ack on 80000001 towards 0x4d5c6d8
Jul 07 20:44:35-232504 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:44:35-232716 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:44:35-232932 util-scheduler-8620 DEBUG Adding task: 361 / 0x4d5c418
Jul 07 20:44:35-234415 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:44:35-234943 util-scheduler-8620 DEBUG Canceling task: 360 / 0x4d5c578
Jul 07 20:44:35-235155 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:35-235347 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:44:35-235559 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:44:35-235776 util-scheduler-8620 DEBUG Adding task: 362 / 0x4d5c418
Jul 07 20:44:35-235979 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:44:35-236215 util-scheduler-8620 DEBUG Running task: 359 / 0x46620a0
Jul 07 20:44:35-236406 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:35-236587 util-8620 DEBUG process_notify is running
Jul 07 20:44:35-236775 util-8620 DEBUG client_notify is running
Jul 07 20:44:35-236956 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:35-237179 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:35-237405 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:35-237750 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:35-238031 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:35-238226 util-scheduler-8620 DEBUG Checking readiness of task: 361 / 0x4d5c418
Jul 07 20:44:35-238420 util-scheduler-8620 DEBUG Checking readiness of task: 357 / 0x46620a0
Jul 07 20:44:35-238623 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:35-238814 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:35-239003 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:35-239194 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:35-239384 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:35-239573 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:35-239764 util-scheduler-8620 DEBUG Running task: 361 / 0x4d5c418
Jul 07 20:44:35-239949 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:44:35-240124 util-8620 DEBUG process_notify is running
Jul 07 20:44:35-240552 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:44:35-240850 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:44:36-546594 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-546985 util-scheduler-8620 DEBUG Checking readiness of task: 357 / 0x46620a0
Jul 07 20:44:36-547184 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-547376 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-547598 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-547791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-547984 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-548175 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-548371 util-scheduler-8620 DEBUG Running task: 357 / 0x46620a0
Jul 07 20:44:36-548794 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:36-549054 util-scheduler-8620 DEBUG Adding task: 363 / 0x4662248
Jul 07 20:44:36-549358 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-549551 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-549741 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-549931 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-550121 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-550311 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-550501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-550690 util-scheduler-8620 DEBUG Running task: 363 / 0x4662248
Jul 07 20:44:36-550883 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:36-551084 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:36-551316 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `KNAS'
Jul 07 20:44:36-551956 cadet-con-8620 INFO <-- {              POLL} on connection HS92G30M from KNAS
Jul 07 20:44:36-553145 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:36-554649 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:36-558405 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:44:36-559677 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:44:36-560458 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:36-560732 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:36-560916 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:36-561184 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:36-561593 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:36-561931 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:44:36-562280 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:44:36-563607 cadet-con-8620 DEBUG  same ACK already in queue
Jul 07 20:44:36-564235 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:36-564461 util-scheduler-8620 DEBUG Adding task: 364 / 0x46620a0
Jul 07 20:44:36-589836 util-scheduler-8620 DEBUG Checking readiness of task: 364 / 0x46620a0
Jul 07 20:44:36-590086 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-590280 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-590500 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-590691 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-590882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-591072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-591262 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-591453 util-scheduler-8620 DEBUG Running task: 330 / 0x4d64a70
Jul 07 20:44:36-591675 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:36-591919 cadet-tun-8620 DEBUG  kx started 10 s ago
Jul 07 20:44:36-592125 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:36-592326 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:36-592529 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:36-592760 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:36-592940 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:36-593160 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:36-593475 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:36-593672 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:36-593909 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:36-594116 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:36-594429 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:36-594630 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:36-594855 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:36-595038 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:36-595215 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:36-595422 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:36-595638 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:36-595866 util-scheduler-8620 DEBUG Adding task: 365 / 0x4d6ff98
Jul 07 20:44:36-596047 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:36-596251 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:36-596427 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:36-596603 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:36-596841 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:36-597037 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:36-597237 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:36-597438 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:36-597681 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:36-597879 util-scheduler-8620 DEBUG Adding task: 366 / 0x4d64a70
Jul 07 20:44:36-598128 util-scheduler-8620 DEBUG Checking readiness of task: 364 / 0x46620a0
Jul 07 20:44:36-598320 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-598533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-598810 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-599083 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-599277 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-599468 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-599659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-599851 util-scheduler-8620 DEBUG Running task: 365 / 0x4d6ff98
Jul 07 20:44:36-600062 util-scheduler-8620 DEBUG Adding task: 367 / 0x4d6ff98
Jul 07 20:44:36-600287 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:36-600492 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:36-600698 util-scheduler-8620 DEBUG Adding task: 368 / 0x46620a0
Jul 07 20:44:36-600942 util-scheduler-8620 DEBUG Checking readiness of task: 368 / 0x46620a0
Jul 07 20:44:36-601135 util-scheduler-8620 DEBUG Checking readiness of task: 364 / 0x46620a0
Jul 07 20:44:36-601351 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-601554 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-601744 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-601933 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-602124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-602314 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-602504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-602696 util-scheduler-8620 DEBUG Running task: 368 / 0x46620a0
Jul 07 20:44:36-602882 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:36-603061 util-8620 DEBUG process_notify is running
Jul 07 20:44:36-603234 util-8620 DEBUG client_notify is running
Jul 07 20:44:36-603415 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:36-603611 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:36-603803 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:36-604116 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:36-971683 util-scheduler-8620 DEBUG Checking readiness of task: 364 / 0x46620a0
Jul 07 20:44:36-972069 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-972293 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-972497 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-972690 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-972882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-973074 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-973307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-973523 util-scheduler-8620 DEBUG Running task: 364 / 0x46620a0
Jul 07 20:44:36-973948 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:36-974203 util-scheduler-8620 DEBUG Adding task: 369 / 0x4662248
Jul 07 20:44:36-974483 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-974676 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-974880 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-975080 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-975271 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-975462 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-975681 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-975872 util-scheduler-8620 DEBUG Running task: 369 / 0x4662248
Jul 07 20:44:36-976064 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:36-976266 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:36-976511 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:36-976719 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:36-976926 util-scheduler-8620 DEBUG Adding task: 370 / 0x46620a0
Jul 07 20:44:36-977137 util-scheduler-8620 DEBUG Adding task: 371 / 0x4662248
Jul 07 20:44:36-977403 util-scheduler-8620 DEBUG Checking readiness of task: 370 / 0x46620a0
Jul 07 20:44:36-977597 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-977786 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-977977 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-978179 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-978369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-978558 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-978747 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-978938 util-scheduler-8620 DEBUG Running task: 370 / 0x46620a0
Jul 07 20:44:36-979124 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:36-979302 util-8620 DEBUG process_notify is running
Jul 07 20:44:36-979473 util-8620 DEBUG client_notify is running
Jul 07 20:44:36-979663 util-scheduler-8620 DEBUG Canceling task: 367 / 0x4d6ff98
Jul 07 20:44:36-979931 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:36-980154 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:36-980393 cadet-p2p-8620 DEBUG Checking 0x5456e28 towards CMHCKRVP (->V8XX)
Jul 07 20:44:36-980628 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:36-980806 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:36-980998 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:36-981318 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:36-981516 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:36-981698 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:36-981886 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:36-982075 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:36-982255 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:36-982438 util-scheduler-8620 DEBUG Canceling task: 349 / 0x4d707d0
Jul 07 20:44:36-982649 util-scheduler-8620 DEBUG Adding task: 372 / 0x4d707d0
Jul 07 20:44:36-982909 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:36-983083 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:36-983277 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:36-983478 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:36-983653 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:36-983827 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:36-984027 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:36-984232 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:36-984416 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:36-984606 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:36-984798 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:36-985630 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:36-985847 util-scheduler-8620 DEBUG Running task: 371 / 0x4662248
Jul 07 20:44:36-986039 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:36-986264 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:36-986480 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:36-986679 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:36-986883 util-scheduler-8620 DEBUG Adding task: 373 / 0x46620a0
Jul 07 20:44:36-987068 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:36-987271 util-scheduler-8620 DEBUG Adding task: 374 / 0x46620a0
Jul 07 20:44:36-987521 util-scheduler-8620 DEBUG Checking readiness of task: 374 / 0x46620a0
Jul 07 20:44:36-987721 util-scheduler-8620 DEBUG Checking readiness of task: 373 / 0x46620a0
Jul 07 20:44:36-987914 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:36-988105 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:36-988295 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:36-988484 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:36-988672 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:36-988860 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:36-989049 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:36-989264 util-scheduler-8620 DEBUG Running task: 373 / 0x46620a0
Jul 07 20:44:36-989459 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:36-989635 util-8620 DEBUG process_notify is running
Jul 07 20:44:36-989805 util-8620 DEBUG client_notify is running
Jul 07 20:44:36-989988 util-scheduler-8620 DEBUG Canceling task: 358 / 0x4d5c9e8
Jul 07 20:44:36-990206 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:36-990420 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:36-990651 cadet-p2p-8620 DEBUG Checking 0x5449b28 towards HS92G30M (->KNAS)
Jul 07 20:44:36-990890 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:36-991068 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:36-991255 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:36-991531 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:36-991723 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:36-991899 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:36-992084 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:36-992257 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:36-992639 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:36-992982 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:36-993250 cadet-p2p-8620 DEBUG Checking 0x5448d78 towards HS92G30M (->KNAS)
Jul 07 20:44:36-993489 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:36-993673 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:36-993859 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:36-994090 cadet-p2p-8620 DEBUG Checking 0x5448d78 towards HS92G30M (->KNAS)
Jul 07 20:44:36-994320 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:36-994502 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:36-994675 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:36-994841 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:36-995048 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:36-995264 util-scheduler-8620 DEBUG Adding task: 375 / 0x4d5c9e8
Jul 07 20:44:36-995454 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:36-995632 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:36-995830 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:36-996004 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:36-996178 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:36-996417 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:36-996612 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:36-996809 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:36-997055 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:36-997275 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:36-997453 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:36-997651 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:36-997853 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:36-998036 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:36-998241 util-scheduler-8620 DEBUG Adding task: 376 / 0x4d5c9e8
Jul 07 20:44:36-998460 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:36-998665 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:36-998869 util-scheduler-8620 DEBUG Adding task: 377 / 0x46620a0
Jul 07 20:44:36-999068 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:37-000855 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-001070 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:37-001352 util-scheduler-8620 DEBUG Checking readiness of task: 377 / 0x46620a0
Jul 07 20:44:37-001549 util-scheduler-8620 DEBUG Checking readiness of task: 374 / 0x46620a0
Jul 07 20:44:37-001992 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-002188 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-002381 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-002584 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-002777 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-002968 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-003160 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-003597 util-scheduler-8620 DEBUG Running task: 377 / 0x46620a0
Jul 07 20:44:37-003788 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-003968 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-004140 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-004321 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:37-004519 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:37-004709 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:37-005293 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-005510 util-scheduler-8620 DEBUG Running task: 375 / 0x4d5c9e8
Jul 07 20:44:37-005707 util-scheduler-8620 DEBUG Canceling task: 376 / 0x4d5c9e8
Jul 07 20:44:37-005927 util-scheduler-8620 DEBUG Adding task: 378 / 0x4d5c9e8
Jul 07 20:44:37-006150 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:37-006348 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:37-006798 util-scheduler-8620 DEBUG Adding task: 379 / 0x46620a0
Jul 07 20:44:37-007045 util-scheduler-8620 DEBUG Checking readiness of task: 379 / 0x46620a0
Jul 07 20:44:37-007240 util-scheduler-8620 DEBUG Checking readiness of task: 374 / 0x46620a0
Jul 07 20:44:37-007433 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-007625 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-007817 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-008009 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-008452 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-008647 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-008858 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-009052 util-scheduler-8620 DEBUG Running task: 374 / 0x46620a0
Jul 07 20:44:37-009483 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:37-009713 util-scheduler-8620 DEBUG Adding task: 380 / 0x4662248
Jul 07 20:44:37-009925 util-scheduler-8620 DEBUG Running task: 379 / 0x46620a0
Jul 07 20:44:37-010112 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-010290 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-010461 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-010639 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:37-010830 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:37-011020 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:37-011321 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-011570 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-011764 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-011957 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-012148 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-012340 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-012531 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-012722 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-012914 util-scheduler-8620 DEBUG Running task: 380 / 0x4662248
Jul 07 20:44:37-013105 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:37-013325 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:37-013551 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:37-013735 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:37-013942 util-scheduler-8620 DEBUG Adding task: 381 / 0x46620a0
Jul 07 20:44:37-014193 util-scheduler-8620 DEBUG Checking readiness of task: 381 / 0x46620a0
Jul 07 20:44:37-014387 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-014579 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-014770 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-014962 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-015163 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-015355 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-015547 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-015739 util-scheduler-8620 DEBUG Running task: 381 / 0x46620a0
Jul 07 20:44:37-016153 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:37-016377 util-scheduler-8620 DEBUG Adding task: 382 / 0x4662248
Jul 07 20:44:37-016625 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-016819 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-017012 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-020688 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-020899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-021093 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-021314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-021508 util-scheduler-8620 DEBUG Running task: 382 / 0x4662248
Jul 07 20:44:37-021700 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:37-021916 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:37-022134 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:37-022335 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:37-022538 util-scheduler-8620 DEBUG Adding task: 383 / 0x46620a0
Jul 07 20:44:37-022724 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:37-022925 util-scheduler-8620 DEBUG Adding task: 384 / 0x46620a0
Jul 07 20:44:37-023171 util-scheduler-8620 DEBUG Checking readiness of task: 384 / 0x46620a0
Jul 07 20:44:37-023364 util-scheduler-8620 DEBUG Checking readiness of task: 383 / 0x46620a0
Jul 07 20:44:37-023557 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-023748 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-023940 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-024131 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-024322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-024512 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-024703 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-024896 util-scheduler-8620 DEBUG Running task: 383 / 0x46620a0
Jul 07 20:44:37-025083 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-025299 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-025473 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-025658 util-scheduler-8620 DEBUG Canceling task: 378 / 0x4d5c9e8
Jul 07 20:44:37-025879 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:37-026096 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:37-026332 cadet-p2p-8620 DEBUG Checking 0x5448d78 towards HS92G30M (->KNAS)
Jul 07 20:44:37-026565 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:37-026749 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:44:37-026926 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:37-027149 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:37-027326 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:44:37-027652 cadet-p2p-8620 DEBUG   payload ID 1
Jul 07 20:44:37-027945 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 88)
Jul 07 20:44:37-028147 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:37-028328 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:37-028518 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:37-028707 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:37-028942 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:37-029237 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:37-029423 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:44:37-029691 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:37-030062 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:37-030488 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:37-030884 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:37-031098 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:37-031282 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:37-031468 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:37-031652 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:37-031832 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:37-032004 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:37-032225 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:37-032400 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:37-032636 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:37-032823 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:37-033123 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:37-033344 util-scheduler-8620 DEBUG Canceling task: 280 / 0x4d61c30
Jul 07 20:44:37-033562 util-scheduler-8620 DEBUG Adding task: 385 / 0x4d61c30
Jul 07 20:44:37-033813 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:37-034098 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:44:37-034292 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 1
Jul 07 20:44:37-034467 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:37-034694 cadet-p2p-8620 DEBUG Checking 0x5453c88 towards HS92G30M (->KNAS)
Jul 07 20:44:37-034929 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:37-035113 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:44:37-035289 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:37-035519 cadet-p2p-8620 DEBUG Checking 0x5453c88 towards HS92G30M (->KNAS)
Jul 07 20:44:37-035750 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:37-035933 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:44:37-036107 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:37-036276 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:37-036482 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `KNAS'
Jul 07 20:44:37-036698 util-scheduler-8620 DEBUG Adding task: 386 / 0x4d5c9e8
Jul 07 20:44:37-036879 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:37-037057 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:44:37-037296 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:37-037473 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:37-037650 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:37-037891 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:37-038091 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:37-038271 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:37-038471 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:37-038676 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 88 bytes.
Jul 07 20:44:37-038860 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:44:37-039063 util-scheduler-8620 DEBUG Adding task: 387 / 0x4d5c9e8
Jul 07 20:44:37-039285 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:37-039508 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:37-040147 util-scheduler-8620 DEBUG Adding task: 388 / 0x46620a0
Jul 07 20:44:37-040355 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:44:37-046548 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-046780 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:37-047045 util-scheduler-8620 DEBUG Checking readiness of task: 388 / 0x46620a0
Jul 07 20:44:37-047242 util-scheduler-8620 DEBUG Checking readiness of task: 384 / 0x46620a0
Jul 07 20:44:37-047884 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-048086 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-048281 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-048475 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-048668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-048872 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-049064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-049284 util-scheduler-8620 DEBUG Running task: 384 / 0x46620a0
Jul 07 20:44:37-049693 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:37-049932 util-scheduler-8620 DEBUG Adding task: 389 / 0x4662248
Jul 07 20:44:37-050145 util-scheduler-8620 DEBUG Running task: 388 / 0x46620a0
Jul 07 20:44:37-050355 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-050905 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-051083 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-051503 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:37-051708 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:37-051901 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:37-052198 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-052409 util-scheduler-8620 DEBUG Running task: 386 / 0x4d5c9e8
Jul 07 20:44:37-052605 util-scheduler-8620 DEBUG Canceling task: 387 / 0x4d5c9e8
Jul 07 20:44:37-052821 util-scheduler-8620 DEBUG Adding task: 390 / 0x4d5c9e8
Jul 07 20:44:37-053046 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:37-053269 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:37-053485 util-scheduler-8620 DEBUG Adding task: 391 / 0x46620a0
Jul 07 20:44:37-054136 util-scheduler-8620 DEBUG Checking readiness of task: 391 / 0x46620a0
Jul 07 20:44:37-054334 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-054528 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-054721 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-054913 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-055105 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-055297 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-055488 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-055682 util-scheduler-8620 DEBUG Running task: 391 / 0x46620a0
Jul 07 20:44:37-055868 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-056046 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-056217 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-056396 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:37-056588 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:37-057157 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:37-057469 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:37-057680 util-scheduler-8620 DEBUG Running task: 389 / 0x4662248
Jul 07 20:44:37-057874 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:37-058075 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:37-058296 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:37-058553 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:37-058809 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:37-059019 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:37-059401 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:37-060141 cadet-con-8620 DEBUG   ACK 64 (was 64)
Jul 07 20:44:37-060756 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:37-060997 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:37-061232 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:37-062161 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:44:37-062574 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:37-062794 util-scheduler-8620 DEBUG Adding task: 392 / 0x46620a0
Jul 07 20:44:37-777755 util-scheduler-8620 DEBUG Checking readiness of task: 392 / 0x46620a0
Jul 07 20:44:37-778162 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-778359 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-778585 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-778778 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-778969 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-779161 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-779352 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-779549 util-scheduler-8620 DEBUG Running task: 392 / 0x46620a0
Jul 07 20:44:37-779973 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:37-780229 util-scheduler-8620 DEBUG Adding task: 393 / 0x4662248
Jul 07 20:44:37-780508 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-780704 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-780895 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-781084 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-781326 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-781574 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-781765 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-781955 util-scheduler-8620 DEBUG Running task: 393 / 0x4662248
Jul 07 20:44:37-782147 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:37-782347 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:37-782581 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:37-782790 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:37-782997 util-scheduler-8620 DEBUG Adding task: 394 / 0x46620a0
Jul 07 20:44:37-783184 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:37-783390 util-scheduler-8620 DEBUG Adding task: 395 / 0x46620a0
Jul 07 20:44:37-783634 util-scheduler-8620 DEBUG Checking readiness of task: 395 / 0x46620a0
Jul 07 20:44:37-783825 util-scheduler-8620 DEBUG Checking readiness of task: 394 / 0x46620a0
Jul 07 20:44:37-784017 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:37-784206 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:37-784396 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:37-784584 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:37-784773 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:37-784962 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:37-785151 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:37-785380 util-scheduler-8620 DEBUG Running task: 394 / 0x46620a0
Jul 07 20:44:37-785566 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:37-785745 util-8620 DEBUG process_notify is running
Jul 07 20:44:37-785918 util-8620 DEBUG client_notify is running
Jul 07 20:44:37-786106 util-scheduler-8620 DEBUG Canceling task: 390 / 0x4d5c9e8
Jul 07 20:44:37-786330 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 172 bytes.
Jul 07 20:44:37-786549 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:37-786789 cadet-p2p-8620 DEBUG Checking 0x5453c88 towards HS92G30M (->KNAS)
Jul 07 20:44:37-787023 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:37-787205 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:44:37-787380 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:37-787603 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:37-787780 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:44:37-787954 cadet-p2p-8620 DEBUG   payload ID 2
Jul 07 20:44:37-788242 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 172)
Jul 07 20:44:37-788454 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:37-788636 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:37-788825 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:37-788999 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:37-789180 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:37-789394 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:37-790521 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:44:37-792296 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:44:37-793402 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:37-794986 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:44:37-795455 util-scheduler-8620 DEBUG Adding task: 396 / 0x4d63a48
Jul 07 20:44:37-796025 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:37-796276 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:37-796454 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:37-796627 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:44:37-796800 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:37-796999 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:37-797175 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:37-797372 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:37-797573 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:37-797753 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:37-797935 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:37-798117 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:37-798294 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:37-798464 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:37-798681 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:37-798853 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:37-799085 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:37-799270 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:37-799450 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:37-799637 util-scheduler-8620 DEBUG Canceling task: 385 / 0x4d61c30
Jul 07 20:44:37-799849 util-scheduler-8620 DEBUG Adding task: 397 / 0x4d61c30
Jul 07 20:44:37-800093 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:37-800271 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:44:37-801358 cadet-con-8620 DEBUG !   accounting pid 2
Jul 07 20:44:37-801660 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:37-801852 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:44:37-802057 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:37-802234 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:37-802410 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:37-802610 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:37-802816 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 172 bytes.
Jul 07 20:44:37-802999 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:44:37-803180 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:37-803371 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:44:37-804627 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:38-548109 util-scheduler-8620 DEBUG Checking readiness of task: 395 / 0x46620a0
Jul 07 20:44:38-548492 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:38-548688 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:38-548881 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:38-549072 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:38-549289 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:38-549480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:38-549701 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:38-549899 util-scheduler-8620 DEBUG Running task: 395 / 0x46620a0
Jul 07 20:44:38-550322 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:38-550581 util-scheduler-8620 DEBUG Adding task: 398 / 0x4662248
Jul 07 20:44:38-550860 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:38-551056 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:38-551268 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:38-551458 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:38-551648 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:38-551837 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:38-552026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:38-552216 util-scheduler-8620 DEBUG Running task: 398 / 0x4662248
Jul 07 20:44:38-552407 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:38-552607 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:38-552836 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `KNAS'
Jul 07 20:44:38-553099 cadet-con-8620 INFO <-- {              POLL} on connection HS92G30M from KNAS
Jul 07 20:44:38-553378 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:38-553586 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:38-554022 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:44:38-554356 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:44:38-554595 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:38-554772 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:38-554948 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:38-555120 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:38-555343 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:38-555521 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:44:38-555701 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:44:38-555970 cadet-con-8620 INFO --> {               ACK} ( 64) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:38-556256 cadet-con-8620 DEBUG  ack 64
Jul 07 20:44:38-556442 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:38-556681 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:38-556888 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:38-557184 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:38-557513 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:38-557742 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:38-557937 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:44:38-558113 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:38-558485 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:38-558709 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:38-558930 util-scheduler-8620 DEBUG Adding task: 399 / 0x4d5c9e8
Jul 07 20:44:38-559111 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:38-559406 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:38-559589 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:38-559766 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:38-560007 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:38-560191 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:44:38-560368 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:38-560567 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:38-560752 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:38-560969 util-scheduler-8620 DEBUG Adding task: 400 / 0x46620a0
Jul 07 20:44:38-561261 util-scheduler-8620 DEBUG Checking readiness of task: 400 / 0x46620a0
Jul 07 20:44:38-561455 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:38-561645 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:38-561834 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:38-562024 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:38-562213 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:38-562415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:38-562604 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:38-562794 util-scheduler-8620 DEBUG Running task: 399 / 0x4d5c9e8
Jul 07 20:44:38-563003 util-scheduler-8620 DEBUG Adding task: 401 / 0x4d5c9e8
Jul 07 20:44:38-563227 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:38-563431 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:38-563631 util-scheduler-8620 DEBUG Adding task: 402 / 0x46620a0
Jul 07 20:44:38-563873 util-scheduler-8620 DEBUG Checking readiness of task: 402 / 0x46620a0
Jul 07 20:44:38-564065 util-scheduler-8620 DEBUG Checking readiness of task: 400 / 0x46620a0
Jul 07 20:44:38-564255 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:38-564444 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:38-564633 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:38-564822 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:38-565011 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:38-565223 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:38-565413 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:38-565605 util-scheduler-8620 DEBUG Running task: 402 / 0x46620a0
Jul 07 20:44:38-565791 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:38-565969 util-8620 DEBUG process_notify is running
Jul 07 20:44:38-566142 util-8620 DEBUG client_notify is running
Jul 07 20:44:38-566320 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:38-566515 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:38-566705 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:38-567005 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:39-382838 util-scheduler-8620 DEBUG Checking readiness of task: 400 / 0x46620a0
Jul 07 20:44:39-383231 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-383428 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-383622 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-383814 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-384005 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-384195 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-384386 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-384583 util-scheduler-8620 DEBUG Running task: 400 / 0x46620a0
Jul 07 20:44:39-385007 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:39-385308 util-scheduler-8620 DEBUG Adding task: 403 / 0x4662248
Jul 07 20:44:39-385592 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-385785 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-385976 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-386166 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-386385 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-386575 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-386765 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-386955 util-scheduler-8620 DEBUG Running task: 403 / 0x4662248
Jul 07 20:44:39-387146 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:39-387346 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:39-387578 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:39-387845 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:39-388104 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:39-388315 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:39-388499 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:39-388673 cadet-con-8620 DEBUG   ACK 64 (was 64)
Jul 07 20:44:39-388903 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:39-389133 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:39-393345 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:39-393827 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:44:39-394016 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:39-394236 util-scheduler-8620 DEBUG Adding task: 404 / 0x46620a0
Jul 07 20:44:39-779256 util-scheduler-8620 DEBUG Checking readiness of task: 404 / 0x46620a0
Jul 07 20:44:39-779639 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-779835 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-780028 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-780219 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-780410 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-780600 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-780791 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-780987 util-scheduler-8620 DEBUG Running task: 404 / 0x46620a0
Jul 07 20:44:39-781443 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:39-781700 util-scheduler-8620 DEBUG Adding task: 405 / 0x4662248
Jul 07 20:44:39-781981 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-782173 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-782364 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-782553 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-782743 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-782932 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-783121 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-783310 util-scheduler-8620 DEBUG Running task: 405 / 0x4662248
Jul 07 20:44:39-783501 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:39-783701 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:39-783938 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:39-784145 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:39-784381 util-scheduler-8620 DEBUG Adding task: 406 / 0x46620a0
Jul 07 20:44:39-784567 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:39-784773 util-scheduler-8620 DEBUG Adding task: 407 / 0x46620a0
Jul 07 20:44:39-785017 util-scheduler-8620 DEBUG Checking readiness of task: 407 / 0x46620a0
Jul 07 20:44:39-785232 util-scheduler-8620 DEBUG Checking readiness of task: 406 / 0x46620a0
Jul 07 20:44:39-785458 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-785649 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-785839 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-786028 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-786217 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-786406 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-786596 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-786787 util-scheduler-8620 DEBUG Running task: 406 / 0x46620a0
Jul 07 20:44:39-786973 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:39-787152 util-8620 DEBUG process_notify is running
Jul 07 20:44:39-787325 util-8620 DEBUG client_notify is running
Jul 07 20:44:39-787515 util-scheduler-8620 DEBUG Canceling task: 401 / 0x4d5c9e8
Jul 07 20:44:39-787740 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:39-787960 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:39-788199 cadet-p2p-8620 DEBUG Checking 0x5462d50 towards HS92G30M (->KNAS)
Jul 07 20:44:39-788433 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:39-788610 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:39-788802 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:39-789070 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:39-789308 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:39-789489 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:39-789677 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:39-789853 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:39-790036 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:39-790211 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:39-790391 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:39-790591 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:39-790766 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:39-790940 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:39-791140 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:39-791346 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:39-791530 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:39-791710 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:39-791901 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:39-793704 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:39-795568 util-scheduler-8620 DEBUG Checking readiness of task: 407 / 0x46620a0
Jul 07 20:44:39-795763 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-795954 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-796144 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-796334 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-796524 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-796713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-796902 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-797105 util-scheduler-8620 DEBUG Running task: 396 / 0x4d63a48
Jul 07 20:44:39-798675 cadet-chn-8620 DEBUG !!! RETRANSMIT 0
Jul 07 20:44:39-799566 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:39-799866 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:44:39-801166 cadet-chn-8620 DEBUG   using existing copy: 0x544b120 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:44:39-801583 cadet-chn-8620 DEBUG   new chq: 0x54661b8
Jul 07 20:44:39-801820 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:39-802026 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:39-802208 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:39-802392 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:39-802573 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:39-802750 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:39-802921 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:39-803149 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:39-803323 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:39-803560 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:39-803746 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:39-804060 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:39-804232 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:39-804418 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:39-808522 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:39-809901 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:39-810082 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:39-810273 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:39-813506 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:39-813749 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:39-813931 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:39-814155 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:39-814351 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:39-814633 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (172 bytes)
Jul 07 20:44:39-814833 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:39-815011 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:44:39-815185 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:39-815358 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:39-815536 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:39-815773 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:39-815982 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:39-816304 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 172)
Jul 07 20:44:39-816505 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:39-816732 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:39-816919 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:44:39-817095 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:39-817327 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 172 bytes
Jul 07 20:44:39-817544 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `KNAS'
Jul 07 20:44:39-817773 util-scheduler-8620 DEBUG Adding task: 408 / 0x4d5c9e8
Jul 07 20:44:39-817954 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:39-818194 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:39-818379 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:39-818555 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:39-818795 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:39-818992 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:39-819170 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:39-819370 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:39-819899 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:39-820123 util-scheduler-8620 DEBUG Adding task: 409 / 0x4d5e5d8
Jul 07 20:44:39-820580 util-scheduler-8620 DEBUG Checking readiness of task: 409 / 0x4d5e5d8
Jul 07 20:44:39-820782 util-scheduler-8620 DEBUG Checking readiness of task: 407 / 0x46620a0
Jul 07 20:44:39-820975 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-821167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-821407 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-821599 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-821789 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-821979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-822169 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-822363 util-scheduler-8620 DEBUG Running task: 409 / 0x4d5e5d8
Jul 07 20:44:39-822550 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:39-822729 util-8620 DEBUG process_notify is running
Jul 07 20:44:39-822902 util-8620 DEBUG client_notify is running
Jul 07 20:44:39-823128 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:39-823488 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:39-823700 util-scheduler-8620 DEBUG Running task: 408 / 0x4d5c9e8
Jul 07 20:44:39-823911 util-scheduler-8620 DEBUG Adding task: 410 / 0x4d5c9e8
Jul 07 20:44:39-824254 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:39-824560 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:39-824764 util-scheduler-8620 DEBUG Adding task: 411 / 0x46620a0
Jul 07 20:44:39-825006 util-scheduler-8620 DEBUG Checking readiness of task: 411 / 0x46620a0
Jul 07 20:44:39-825223 util-scheduler-8620 DEBUG Checking readiness of task: 407 / 0x46620a0
Jul 07 20:44:39-825414 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-825607 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-825797 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-825987 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-826177 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-826366 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-826555 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-826746 util-scheduler-8620 DEBUG Running task: 411 / 0x46620a0
Jul 07 20:44:39-826930 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:39-827106 util-8620 DEBUG process_notify is running
Jul 07 20:44:39-827275 util-8620 DEBUG client_notify is running
Jul 07 20:44:39-827454 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:39-827649 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:39-827837 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:39-828158 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:39-828418 util-scheduler-8620 DEBUG Checking readiness of task: 407 / 0x46620a0
Jul 07 20:44:39-828660 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-828852 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-829041 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-829254 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-829445 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-829635 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-829823 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-830014 util-scheduler-8620 DEBUG Running task: 407 / 0x46620a0
Jul 07 20:44:39-830417 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:39-830649 util-scheduler-8620 DEBUG Adding task: 412 / 0x4662248
Jul 07 20:44:39-830896 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-831104 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-831298 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-831487 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-831676 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-831864 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-832052 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-832241 util-scheduler-8620 DEBUG Running task: 412 / 0x4662248
Jul 07 20:44:39-832432 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:39-832627 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:39-832844 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:39-833040 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:39-833261 util-scheduler-8620 DEBUG Adding task: 413 / 0x46620a0
Jul 07 20:44:39-833446 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:39-833651 util-scheduler-8620 DEBUG Adding task: 414 / 0x46620a0
Jul 07 20:44:39-833891 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:39-834082 util-scheduler-8620 DEBUG Checking readiness of task: 413 / 0x46620a0
Jul 07 20:44:39-834272 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:39-834461 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:39-834650 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:39-834838 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:39-835027 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:39-835216 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:39-835404 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:39-835594 util-scheduler-8620 DEBUG Running task: 413 / 0x46620a0
Jul 07 20:44:39-835778 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:39-835952 util-8620 DEBUG process_notify is running
Jul 07 20:44:39-836121 util-8620 DEBUG client_notify is running
Jul 07 20:44:39-836306 util-scheduler-8620 DEBUG Canceling task: 410 / 0x4d5c9e8
Jul 07 20:44:39-836526 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 172 bytes.
Jul 07 20:44:39-836740 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:39-836972 cadet-p2p-8620 DEBUG Checking 0x546ecf0 towards HS92G30M (->KNAS)
Jul 07 20:44:39-837230 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:39-837415 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:44:39-837589 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:39-837810 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:39-837987 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:44:39-838173 cadet-p2p-8620 DEBUG   payload ID 3
Jul 07 20:44:39-838457 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 172)
Jul 07 20:44:39-838651 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:39-838830 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:39-839018 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:39-839193 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:39-839361 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:39-839548 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:39-839840 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:44:39-840167 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:44:39-840433 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:39-840758 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:44:39-840961 util-scheduler-8620 DEBUG Adding task: 415 / 0x4d63a48
Jul 07 20:44:39-841166 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:39-841440 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:39-841616 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:39-841789 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:39-841961 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:39-845572 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:39-845752 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:39-845929 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:39-846131 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:39-846311 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:39-846494 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:39-846676 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:39-846854 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:39-847024 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:39-847242 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:39-847415 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:39-847651 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:39-847835 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:39-848017 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:39-848207 util-scheduler-8620 DEBUG Canceling task: 397 / 0x4d61c30
Jul 07 20:44:39-848424 util-scheduler-8620 DEBUG Adding task: 416 / 0x4d61c30
Jul 07 20:44:39-848672 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:39-848866 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:39-849045 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 3
Jul 07 20:44:39-849244 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:39-849431 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:44:39-849633 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:39-849809 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:39-849984 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:39-850184 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:39-850390 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 172 bytes.
Jul 07 20:44:39-850573 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:44:39-850753 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:39-850958 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:44:39-851840 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:41-599810 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-600202 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-600399 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-600592 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-600783 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-600973 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-601165 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-601380 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-601574 util-scheduler-8620 DEBUG Running task: 366 / 0x4d64a70
Jul 07 20:44:41-601814 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:41-602061 cadet-tun-8620 DEBUG  kx started 15 s ago
Jul 07 20:44:41-602267 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:41-602467 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:41-602670 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:41-602907 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:41-603087 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:41-603309 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:41-603602 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:41-603831 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:41-604071 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:41-604279 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:41-604598 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:41-604799 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:41-605025 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:41-605232 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:41-605410 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:41-605618 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:41-605833 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:41-606058 util-scheduler-8620 DEBUG Adding task: 417 / 0x4d6ff98
Jul 07 20:44:41-606239 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:41-606459 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:41-606636 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:41-606811 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:41-607050 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:41-607245 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:41-607423 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:41-607622 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:41-607865 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:41-608064 util-scheduler-8620 DEBUG Adding task: 418 / 0x4d64a70
Jul 07 20:44:41-608323 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-608515 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-608704 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-608893 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-609082 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-609299 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-609489 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-609678 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-609867 util-scheduler-8620 DEBUG Running task: 417 / 0x4d6ff98
Jul 07 20:44:41-610076 util-scheduler-8620 DEBUG Adding task: 419 / 0x4d6ff98
Jul 07 20:44:41-610299 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:41-610504 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:41-610712 util-scheduler-8620 DEBUG Adding task: 420 / 0x46620a0
Jul 07 20:44:41-611020 util-scheduler-8620 DEBUG Checking readiness of task: 420 / 0x46620a0
Jul 07 20:44:41-611214 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-611404 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-611594 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-611783 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-611973 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-612163 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-612352 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-612542 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-612733 util-scheduler-8620 DEBUG Running task: 420 / 0x46620a0
Jul 07 20:44:41-612918 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:41-613097 util-8620 DEBUG process_notify is running
Jul 07 20:44:41-613290 util-8620 DEBUG client_notify is running
Jul 07 20:44:41-613471 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:41-613686 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:41-613877 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:41-614194 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:41-841347 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-841699 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-841895 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-842088 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-842280 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-842471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-842661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-842852 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-843043 util-scheduler-8620 DEBUG Running task: 415 / 0x4d63a48
Jul 07 20:44:41-843475 cadet-chn-8620 DEBUG !!! RETRANSMIT 0
Jul 07 20:44:41-843787 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:41-843990 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:44:41-844288 cadet-chn-8620 DEBUG   using existing copy: 0x544b120 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:44:41-844485 cadet-chn-8620 DEBUG   new chq: 0x54740b8
Jul 07 20:44:41-844693 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:41-844895 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:41-845076 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:41-845286 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:41-845469 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:41-845646 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:41-845816 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:41-846031 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:41-846218 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:41-846454 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:41-846639 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:41-846951 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:41-847122 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:41-847307 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:41-850887 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:41-851711 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:41-851889 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:41-852080 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:41-855284 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:41-855528 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:41-855712 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:41-855936 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:41-856131 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:41-856412 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (172 bytes)
Jul 07 20:44:41-856613 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:41-856791 cadet-con-8620 DEBUG last pid sent 3
Jul 07 20:44:41-856966 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:41-857138 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:41-857342 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:41-857578 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:41-857787 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:41-858101 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 172)
Jul 07 20:44:41-858300 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:41-858526 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:41-858739 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 3
Jul 07 20:44:41-858916 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:41-859123 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 172 bytes
Jul 07 20:44:41-859344 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `KNAS'
Jul 07 20:44:41-859573 util-scheduler-8620 DEBUG Adding task: 421 / 0x4d5c9e8
Jul 07 20:44:41-859755 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:41-859960 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:41-860135 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:41-860309 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:41-860556 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:41-860752 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:41-860931 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:41-861130 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:41-861427 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:41-861646 util-scheduler-8620 DEBUG Adding task: 422 / 0x4d5e5d8
Jul 07 20:44:41-861919 util-scheduler-8620 DEBUG Checking readiness of task: 422 / 0x4d5e5d8
Jul 07 20:44:41-862115 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-862306 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-862496 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-862686 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-862877 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-863067 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-863258 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-863448 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-863641 util-scheduler-8620 DEBUG Running task: 422 / 0x4d5e5d8
Jul 07 20:44:41-863828 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:41-864008 util-8620 DEBUG process_notify is running
Jul 07 20:44:41-864180 util-8620 DEBUG client_notify is running
Jul 07 20:44:41-864408 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:41-864792 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:41-865009 util-scheduler-8620 DEBUG Running task: 421 / 0x4d5c9e8
Jul 07 20:44:41-865245 util-scheduler-8620 DEBUG Adding task: 423 / 0x4d5c9e8
Jul 07 20:44:41-865471 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:41-865668 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:41-865868 util-scheduler-8620 DEBUG Adding task: 424 / 0x46620a0
Jul 07 20:44:41-866113 util-scheduler-8620 DEBUG Checking readiness of task: 424 / 0x46620a0
Jul 07 20:44:41-866306 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:41-866497 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:41-866687 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:41-866876 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:41-867066 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:41-867256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:41-867445 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:41-867634 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:41-867824 util-scheduler-8620 DEBUG Running task: 424 / 0x46620a0
Jul 07 20:44:41-868008 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:41-868182 util-8620 DEBUG process_notify is running
Jul 07 20:44:41-868351 util-8620 DEBUG client_notify is running
Jul 07 20:44:41-868544 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:41-868739 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:41-868926 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:41-869257 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:42-137519 util-scheduler-8620 DEBUG Checking readiness of task: 414 / 0x46620a0
Jul 07 20:44:42-137930 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-138136 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-138328 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-138540 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-138731 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-138921 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-139111 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-139306 util-scheduler-8620 DEBUG Running task: 414 / 0x46620a0
Jul 07 20:44:42-139731 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:42-139988 util-scheduler-8620 DEBUG Adding task: 425 / 0x4662248
Jul 07 20:44:42-140264 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-140455 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-140658 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-140847 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-141036 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-141250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-141443 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-141632 util-scheduler-8620 DEBUG Running task: 425 / 0x4662248
Jul 07 20:44:42-141824 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:42-142024 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:42-142255 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:42-142461 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:42-142668 util-scheduler-8620 DEBUG Adding task: 426 / 0x46620a0
Jul 07 20:44:42-142854 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:42-143061 util-scheduler-8620 DEBUG Adding task: 427 / 0x46620a0
Jul 07 20:44:42-143304 util-scheduler-8620 DEBUG Checking readiness of task: 427 / 0x46620a0
Jul 07 20:44:42-143496 util-scheduler-8620 DEBUG Checking readiness of task: 426 / 0x46620a0
Jul 07 20:44:42-143687 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-143878 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-144067 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-144256 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-144445 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-144634 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-144822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-145013 util-scheduler-8620 DEBUG Running task: 426 / 0x46620a0
Jul 07 20:44:42-145222 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:42-145404 util-8620 DEBUG process_notify is running
Jul 07 20:44:42-145576 util-8620 DEBUG client_notify is running
Jul 07 20:44:42-145765 util-scheduler-8620 DEBUG Canceling task: 423 / 0x4d5c9e8
Jul 07 20:44:42-145989 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 172 bytes.
Jul 07 20:44:42-146237 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:42-146478 cadet-p2p-8620 DEBUG Checking 0x547cbf0 towards HS92G30M (->KNAS)
Jul 07 20:44:42-146714 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:42-146897 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 3
Jul 07 20:44:42-147073 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:42-147296 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:42-147473 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:44:42-147650 cadet-p2p-8620 DEBUG   payload ID 4
Jul 07 20:44:42-147938 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 172)
Jul 07 20:44:42-148132 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:42-148323 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:42-148512 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:42-148686 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:42-148854 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:42-149042 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:42-149242 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:44:42-149476 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:44:42-149648 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:42-149877 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:44:42-150072 util-scheduler-8620 DEBUG Adding task: 428 / 0x4d63a48
Jul 07 20:44:42-150275 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:42-150504 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:42-150680 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:42-150852 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:42-151023 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:42-151220 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:42-151394 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:42-151567 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:42-151767 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:42-151945 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:42-152126 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:42-152307 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:42-152482 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:42-152652 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:42-152867 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:42-153039 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:42-153293 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:42-153479 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:42-153659 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:42-153843 util-scheduler-8620 DEBUG Canceling task: 416 / 0x4d61c30
Jul 07 20:44:42-154054 util-scheduler-8620 DEBUG Adding task: 429 / 0x4d61c30
Jul 07 20:44:42-154296 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:42-154476 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:42-154654 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 4
Jul 07 20:44:42-154827 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:42-155009 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:44:42-155209 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:42-155383 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:42-155556 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:42-155755 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:42-155960 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 172 bytes.
Jul 07 20:44:42-156142 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:44:42-156324 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:42-156515 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:44:42-158068 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:42-518454 util-scheduler-8620 DEBUG Checking readiness of task: 427 / 0x46620a0
Jul 07 20:44:42-518835 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-519053 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-519303 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-519497 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-519691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-519881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-520072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-520268 util-scheduler-8620 DEBUG Running task: 427 / 0x46620a0
Jul 07 20:44:42-520692 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:42-520950 util-scheduler-8620 DEBUG Adding task: 430 / 0x4662248
Jul 07 20:44:42-521257 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-521452 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-521642 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-521832 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-522022 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-522211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-522400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-522589 util-scheduler-8620 DEBUG Running task: 430 / 0x4662248
Jul 07 20:44:42-522780 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:42-522980 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:42-523210 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:44:42-523477 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection CMHCKRVP from V8XX
Jul 07 20:44:42-523704 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:44:42-523946 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:42-524155 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:42-524337 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:42-524509 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:42-524696 util-scheduler-8620 DEBUG Canceling task: 293 / 0x4d707d0
Jul 07 20:44:42-524918 util-scheduler-8620 DEBUG Adding task: 431 / 0x4d707d0
Jul 07 20:44:42-525168 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:42-525375 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:42-525569 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:42-525802 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:44:42-526040 cadet-con-8620 INFO ===> {           BCK ACK} on connection CMHCKRVP (->V8XX)
Jul 07 20:44:42-526274 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:42-526479 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:42-526773 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 36)
Jul 07 20:44:42-526971 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:42-527197 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:42-527392 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:42-527568 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:42-527772 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:44:42-527974 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:42-528149 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:42-528324 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:42-528592 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:42-528789 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:42-528967 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:42-529223 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:42-529407 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:42-529586 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:42-529783 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:42-529966 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:42-530178 util-scheduler-8620 DEBUG Adding task: 432 / 0x46620a0
Jul 07 20:44:42-552527 util-scheduler-8620 DEBUG Checking readiness of task: 432 / 0x46620a0
Jul 07 20:44:42-552778 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-552975 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-553168 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-553384 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-553576 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-553767 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-553957 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-554149 util-scheduler-8620 DEBUG Running task: 432 / 0x46620a0
Jul 07 20:44:42-554560 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:42-554798 util-scheduler-8620 DEBUG Adding task: 433 / 0x4662248
Jul 07 20:44:42-555058 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-555249 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-555439 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-555629 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-555819 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-556008 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-556197 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-556387 util-scheduler-8620 DEBUG Running task: 433 / 0x4662248
Jul 07 20:44:42-556576 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:42-556772 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:42-556992 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `KNAS'
Jul 07 20:44:42-557271 cadet-con-8620 INFO <-- {              POLL} on connection HS92G30M from KNAS
Jul 07 20:44:42-557524 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:42-557732 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:42-557915 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:44:42-558087 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:44:42-558316 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:42-558507 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:42-558683 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:42-558855 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:42-559075 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:42-559254 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:44:42-559433 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:44:42-559705 cadet-con-8620 INFO --> {               ACK} ( 64) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:42-559896 cadet-con-8620 DEBUG  ack 64
Jul 07 20:44:42-560076 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:42-560310 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:42-560515 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:42-560805 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:42-561024 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:42-561270 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:42-561453 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 4
Jul 07 20:44:42-561628 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:42-561833 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:42-562047 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:42-562261 util-scheduler-8620 DEBUG Adding task: 434 / 0x4d5c9e8
Jul 07 20:44:42-562441 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:42-562644 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:42-562819 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:42-562994 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:42-563230 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:42-563413 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:44:42-563588 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:42-563785 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:42-563966 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:42-564171 util-scheduler-8620 DEBUG Adding task: 435 / 0x46620a0
Jul 07 20:44:42-564413 util-scheduler-8620 DEBUG Checking readiness of task: 435 / 0x46620a0
Jul 07 20:44:42-564604 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-564793 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-564982 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-565171 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-565384 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-565572 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-565761 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-565961 util-scheduler-8620 DEBUG Running task: 434 / 0x4d5c9e8
Jul 07 20:44:42-566168 util-scheduler-8620 DEBUG Adding task: 436 / 0x4d5c9e8
Jul 07 20:44:42-566391 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:42-566593 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:42-566794 util-scheduler-8620 DEBUG Adding task: 437 / 0x46620a0
Jul 07 20:44:42-567046 util-scheduler-8620 DEBUG Checking readiness of task: 437 / 0x46620a0
Jul 07 20:44:42-567238 util-scheduler-8620 DEBUG Checking readiness of task: 435 / 0x46620a0
Jul 07 20:44:42-567427 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:42-567616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:42-567805 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:42-567994 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:42-568182 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:42-568371 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:42-568560 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:42-568751 util-scheduler-8620 DEBUG Running task: 437 / 0x46620a0
Jul 07 20:44:42-568936 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:42-569114 util-8620 DEBUG process_notify is running
Jul 07 20:44:42-569310 util-8620 DEBUG client_notify is running
Jul 07 20:44:42-569491 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:42-569688 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:42-569878 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:42-570198 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:43-566600 util-scheduler-8620 DEBUG Checking readiness of task: 435 / 0x46620a0
Jul 07 20:44:43-566983 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-567179 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-567386 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-567578 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-567769 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-567959 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-568149 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-568345 util-scheduler-8620 DEBUG Running task: 435 / 0x46620a0
Jul 07 20:44:43-568768 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:43-569024 util-scheduler-8620 DEBUG Adding task: 438 / 0x4662248
Jul 07 20:44:43-569333 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-569526 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-569716 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-569909 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-570099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-570288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-570477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-570667 util-scheduler-8620 DEBUG Running task: 438 / 0x4662248
Jul 07 20:44:43-570859 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:43-571061 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:43-571299 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:43-571506 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:43-571715 util-scheduler-8620 DEBUG Adding task: 439 / 0x46620a0
Jul 07 20:44:43-571928 util-scheduler-8620 DEBUG Adding task: 440 / 0x4662248
Jul 07 20:44:43-572169 util-scheduler-8620 DEBUG Checking readiness of task: 439 / 0x46620a0
Jul 07 20:44:43-572379 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-572572 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-572761 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-572950 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-573138 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-574493 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-574695 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-574972 util-scheduler-8620 DEBUG Running task: 439 / 0x46620a0
Jul 07 20:44:43-575161 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:43-575341 util-8620 DEBUG process_notify is running
Jul 07 20:44:43-575514 util-8620 DEBUG client_notify is running
Jul 07 20:44:43-575705 util-scheduler-8620 DEBUG Canceling task: 436 / 0x4d5c9e8
Jul 07 20:44:43-575935 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:43-576158 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:43-576398 cadet-p2p-8620 DEBUG Checking 0x54827b8 towards HS92G30M (->KNAS)
Jul 07 20:44:43-576632 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:43-577213 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:43-577411 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:43-577685 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:43-577878 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:43-578059 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:43-578276 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:43-578452 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:43-578636 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:43-578810 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:43-578991 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:43-579189 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:43-579364 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:43-579540 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:43-580123 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:43-580334 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:43-580518 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:43-580700 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:43-580891 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:43-582095 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:43-582313 util-scheduler-8620 DEBUG Running task: 440 / 0x4662248
Jul 07 20:44:43-582506 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:43-583102 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:43-583321 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:43-583523 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:43-583728 util-scheduler-8620 DEBUG Adding task: 441 / 0x46620a0
Jul 07 20:44:43-583915 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:43-584120 util-scheduler-8620 DEBUG Adding task: 442 / 0x46620a0
Jul 07 20:44:43-584438 util-scheduler-8620 DEBUG Checking readiness of task: 442 / 0x46620a0
Jul 07 20:44:43-584645 util-scheduler-8620 DEBUG Checking readiness of task: 441 / 0x46620a0
Jul 07 20:44:43-584838 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-585028 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-585242 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-585434 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-585992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-586184 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-586375 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-586566 util-scheduler-8620 DEBUG Running task: 441 / 0x46620a0
Jul 07 20:44:43-586752 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:43-586928 util-8620 DEBUG process_notify is running
Jul 07 20:44:43-587100 util-8620 DEBUG client_notify is running
Jul 07 20:44:43-587283 util-scheduler-8620 DEBUG Canceling task: 419 / 0x4d6ff98
Jul 07 20:44:43-587504 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:43-587718 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:43-587950 cadet-p2p-8620 DEBUG Checking 0x5472d38 towards CMHCKRVP (->V8XX)
Jul 07 20:44:43-588179 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:43-588723 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:43-588919 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:43-589239 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:43-589434 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:43-589612 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:43-589802 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:43-589990 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:44:43-590167 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:43-590351 util-scheduler-8620 DEBUG Canceling task: 372 / 0x4d707d0
Jul 07 20:44:43-590566 util-scheduler-8620 DEBUG Adding task: 443 / 0x4d707d0
Jul 07 20:44:43-590832 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:43-591004 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:43-591224 cadet-p2p-8620 DEBUG Checking 0x54810c0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:43-591838 cadet-p2p-8620 DEBUG Checking 0x54810c0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:43-592020 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:43-592228 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:44:43-592442 util-scheduler-8620 DEBUG Adding task: 444 / 0x4d6ff98
Jul 07 20:44:43-592622 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:43-592798 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:43-592997 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:43-593171 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:43-593833 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:43-594083 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:43-594667 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:43-594847 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:43-595048 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:43-595265 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:43-595448 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:43-595659 util-scheduler-8620 DEBUG Adding task: 445 / 0x4d6ff98
Jul 07 20:44:43-595879 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:43-596077 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:43-596281 util-scheduler-8620 DEBUG Adding task: 446 / 0x46620a0
Jul 07 20:44:43-596481 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:43-597646 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:43-597851 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:43-598105 util-scheduler-8620 DEBUG Checking readiness of task: 446 / 0x46620a0
Jul 07 20:44:43-598300 util-scheduler-8620 DEBUG Checking readiness of task: 442 / 0x46620a0
Jul 07 20:44:43-598490 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-598681 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-598870 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-599060 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-599250 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-599439 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-599629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-599824 util-scheduler-8620 DEBUG Running task: 446 / 0x46620a0
Jul 07 20:44:43-600010 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:43-600566 util-8620 DEBUG process_notify is running
Jul 07 20:44:43-600741 util-8620 DEBUG client_notify is running
Jul 07 20:44:43-600921 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:43-601118 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:43-601328 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:43-601610 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:43-601876 util-scheduler-8620 DEBUG Running task: 444 / 0x4d6ff98
Jul 07 20:44:43-602074 util-scheduler-8620 DEBUG Canceling task: 445 / 0x4d6ff98
Jul 07 20:44:43-602291 util-scheduler-8620 DEBUG Adding task: 447 / 0x4d6ff98
Jul 07 20:44:43-602510 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:43-602704 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:43-602903 util-scheduler-8620 DEBUG Adding task: 448 / 0x46620a0
Jul 07 20:44:43-603541 util-scheduler-8620 DEBUG Checking readiness of task: 448 / 0x46620a0
Jul 07 20:44:43-603736 util-scheduler-8620 DEBUG Checking readiness of task: 442 / 0x46620a0
Jul 07 20:44:43-603927 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-604117 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-604307 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-604496 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-604685 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-604875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-605064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-605281 util-scheduler-8620 DEBUG Running task: 448 / 0x46620a0
Jul 07 20:44:43-605467 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:43-605642 util-8620 DEBUG process_notify is running
Jul 07 20:44:43-605811 util-8620 DEBUG client_notify is running
Jul 07 20:44:43-606365 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:43-606568 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:43-606756 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:43-607036 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:43-702838 util-scheduler-8620 DEBUG Checking readiness of task: 442 / 0x46620a0
Jul 07 20:44:43-703201 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-703398 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-703590 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-703783 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-703975 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-704166 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-704357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-704554 util-scheduler-8620 DEBUG Running task: 442 / 0x46620a0
Jul 07 20:44:43-704975 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:43-705257 util-scheduler-8620 DEBUG Adding task: 449 / 0x4662248
Jul 07 20:44:43-705537 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-705740 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-705932 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-706123 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-706314 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-706504 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-706695 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-706885 util-scheduler-8620 DEBUG Running task: 449 / 0x4662248
Jul 07 20:44:43-707077 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:43-707277 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:43-707508 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:43-707715 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:43-707922 util-scheduler-8620 DEBUG Adding task: 450 / 0x46620a0
Jul 07 20:44:43-708110 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:43-708314 util-scheduler-8620 DEBUG Adding task: 451 / 0x46620a0
Jul 07 20:44:43-708557 util-scheduler-8620 DEBUG Checking readiness of task: 451 / 0x46620a0
Jul 07 20:44:43-708751 util-scheduler-8620 DEBUG Checking readiness of task: 450 / 0x46620a0
Jul 07 20:44:43-708972 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:43-709164 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:43-710572 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:43-710769 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:43-710975 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:43-711248 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:43-711442 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:43-711636 util-scheduler-8620 DEBUG Running task: 450 / 0x46620a0
Jul 07 20:44:43-711824 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:43-712004 util-8620 DEBUG process_notify is running
Jul 07 20:44:43-712177 util-8620 DEBUG client_notify is running
Jul 07 20:44:43-712402 util-scheduler-8620 DEBUG Canceling task: 447 / 0x4d6ff98
Jul 07 20:44:43-712631 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:44:43-712853 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:43-713092 cadet-p2p-8620 DEBUG Checking 0x54810c0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:43-713373 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:43-713552 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:43-713724 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:43-713907 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:43-714079 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:43-714339 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 36)
Jul 07 20:44:43-714534 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:43-714717 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:43-714906 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:43-715087 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:43-715262 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:43-715978 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:43-716189 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:43-716367 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:43-716543 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:43-716745 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:43-716950 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:44:43-717134 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:43-717343 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:43-717536 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:43-718816 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:44-150669 util-scheduler-8620 DEBUG Checking readiness of task: 451 / 0x46620a0
Jul 07 20:44:44-151044 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:44-151240 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:44-151434 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:44-151625 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:44-151815 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:44-152005 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:44-152195 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:44-152388 util-scheduler-8620 DEBUG Running task: 428 / 0x4d63a48
Jul 07 20:44:44-152574 cadet-chn-8620 DEBUG !!! RETRANSMIT 0
Jul 07 20:44:44-152863 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:44-153064 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:44:44-153294 cadet-chn-8620 DEBUG   using existing copy: 0x544b120 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:44:44-153513 cadet-chn-8620 DEBUG   new chq: 0x54889b0
Jul 07 20:44:44-153721 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:44-153923 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:44-154102 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:44-154289 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:44-154525 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:44-154703 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:44-154874 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:44-155090 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:44-155263 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:44-155501 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:44-155685 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:44-155997 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:44-156170 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:44-156355 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:44-159937 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:44-160774 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:44-160951 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:44-161141 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:44-164409 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:44-164654 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:44-164837 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:44-165060 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:44-165280 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:44-165561 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (172 bytes)
Jul 07 20:44:44-165761 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:44-165938 cadet-con-8620 DEBUG last pid sent 4
Jul 07 20:44:44-166121 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:44-166293 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:44-166470 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:44-166706 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:44-166913 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:44-167229 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 172)
Jul 07 20:44:44-167429 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:44-167655 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:44-167837 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 4
Jul 07 20:44:44-168013 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:44-168220 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 172 bytes
Jul 07 20:44:44-168436 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `KNAS'
Jul 07 20:44:44-168664 util-scheduler-8620 DEBUG Adding task: 452 / 0x4d5c9e8
Jul 07 20:44:44-168847 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:44-169052 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:44-169252 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:44-169428 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:44-169667 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:44-169861 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:44-170043 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:44-170255 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:44-170527 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:44-170744 util-scheduler-8620 DEBUG Adding task: 453 / 0x4d5e5d8
Jul 07 20:44:44-171017 util-scheduler-8620 DEBUG Checking readiness of task: 453 / 0x4d5e5d8
Jul 07 20:44:44-171212 util-scheduler-8620 DEBUG Checking readiness of task: 451 / 0x46620a0
Jul 07 20:44:44-171403 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:44-171616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:44-171807 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:44-172076 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:44-172268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:44-172458 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:44-172646 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:44-172840 util-scheduler-8620 DEBUG Running task: 453 / 0x4d5e5d8
Jul 07 20:44:44-173053 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:44-173262 util-8620 DEBUG process_notify is running
Jul 07 20:44:44-173436 util-8620 DEBUG client_notify is running
Jul 07 20:44:44-173663 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:44-174019 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:44-174232 util-scheduler-8620 DEBUG Running task: 452 / 0x4d5c9e8
Jul 07 20:44:44-174443 util-scheduler-8620 DEBUG Adding task: 454 / 0x4d5c9e8
Jul 07 20:44:44-174666 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:44-174862 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:44-175062 util-scheduler-8620 DEBUG Adding task: 455 / 0x46620a0
Jul 07 20:44:44-175304 util-scheduler-8620 DEBUG Checking readiness of task: 455 / 0x46620a0
Jul 07 20:44:44-175496 util-scheduler-8620 DEBUG Checking readiness of task: 451 / 0x46620a0
Jul 07 20:44:44-175686 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:44-175875 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:44-176065 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:44-176254 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:44-176442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:44-176631 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:44-176820 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:44-177039 util-scheduler-8620 DEBUG Running task: 455 / 0x46620a0
Jul 07 20:44:44-177247 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:44-177424 util-8620 DEBUG process_notify is running
Jul 07 20:44:44-177593 util-8620 DEBUG client_notify is running
Jul 07 20:44:44-177772 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:44-177967 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:44-178155 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:44-178460 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:45-385842 util-scheduler-8620 DEBUG Checking readiness of task: 451 / 0x46620a0
Jul 07 20:44:45-386287 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-386490 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-386684 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-386877 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-387069 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-387259 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-387449 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-387646 util-scheduler-8620 DEBUG Running task: 451 / 0x46620a0
Jul 07 20:44:45-388079 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:45-388338 util-scheduler-8620 DEBUG Adding task: 456 / 0x4662248
Jul 07 20:44:45-388652 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-388844 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-389035 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-389250 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-389441 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-389630 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-389818 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-390006 util-scheduler-8620 DEBUG Running task: 456 / 0x4662248
Jul 07 20:44:45-390197 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:45-390398 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:45-390642 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:45-390849 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:45-391056 util-scheduler-8620 DEBUG Adding task: 457 / 0x46620a0
Jul 07 20:44:45-391243 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:45-391465 util-scheduler-8620 DEBUG Adding task: 458 / 0x46620a0
Jul 07 20:44:45-391709 util-scheduler-8620 DEBUG Checking readiness of task: 458 / 0x46620a0
Jul 07 20:44:45-391900 util-scheduler-8620 DEBUG Checking readiness of task: 457 / 0x46620a0
Jul 07 20:44:45-392090 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-392278 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-392466 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-392656 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-392844 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-393033 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-393242 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-393445 util-scheduler-8620 DEBUG Running task: 457 / 0x46620a0
Jul 07 20:44:45-393630 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:45-393808 util-8620 DEBUG process_notify is running
Jul 07 20:44:45-393980 util-8620 DEBUG client_notify is running
Jul 07 20:44:45-394168 util-scheduler-8620 DEBUG Canceling task: 454 / 0x4d5c9e8
Jul 07 20:44:45-394399 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 172 bytes.
Jul 07 20:44:45-394626 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:45-394870 cadet-p2p-8620 DEBUG Checking 0x54914e8 towards HS92G30M (->KNAS)
Jul 07 20:44:45-395107 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:45-395291 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 4
Jul 07 20:44:45-395467 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:45-395692 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:45-395871 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:44:45-396051 cadet-p2p-8620 DEBUG   payload ID 5
Jul 07 20:44:45-396359 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 172)
Jul 07 20:44:45-396559 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:45-396745 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:45-396937 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:45-397114 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:45-397308 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:45-397505 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:45-397693 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:44:45-397926 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:44:45-398097 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:45-398327 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:44:45-398555 util-scheduler-8620 DEBUG Adding task: 459 / 0x4d63a48
Jul 07 20:44:45-398761 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:45-398997 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:45-399173 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:45-399345 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:45-399516 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:45-399723 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:45-399897 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:45-400071 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:45-400276 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:45-400466 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:45-400650 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:45-400849 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:45-401025 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:45-401215 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:45-401435 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:45-401607 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:45-401839 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:45-402023 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:45-402203 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:45-402392 util-scheduler-8620 DEBUG Canceling task: 429 / 0x4d61c30
Jul 07 20:44:45-402605 util-scheduler-8620 DEBUG Adding task: 460 / 0x4d61c30
Jul 07 20:44:45-402851 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:45-403030 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:45-403216 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 5
Jul 07 20:44:45-403389 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:45-403572 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:44:45-403773 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:45-403947 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:45-404120 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:45-404319 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:45-404523 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 172 bytes.
Jul 07 20:44:45-404705 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:44:45-404886 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:45-405076 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:44:45-406393 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:45-804825 util-scheduler-8620 DEBUG Checking readiness of task: 458 / 0x46620a0
Jul 07 20:44:45-805232 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-805430 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-805622 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-805813 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-806004 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-806194 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-806384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-806580 util-scheduler-8620 DEBUG Running task: 458 / 0x46620a0
Jul 07 20:44:45-807002 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:45-807264 util-scheduler-8620 DEBUG Adding task: 461 / 0x4662248
Jul 07 20:44:45-807557 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-807759 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-807954 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-808178 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-808370 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-808561 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-808752 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-808943 util-scheduler-8620 DEBUG Running task: 461 / 0x4662248
Jul 07 20:44:45-809135 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:44:45-809370 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:44:45-809610 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:44:45-809884 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:45-810318 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:45-810586 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:45-810796 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:45-811043 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:45-811252 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:45-811539 cadet-con-8620 DEBUG  PID 1 (expected 1+)
Jul 07 20:44:45-811728 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:45-811923 util-scheduler-8620 DEBUG Canceling task: 353 / 0x4d61c30
Jul 07 20:44:45-812151 util-scheduler-8620 DEBUG Adding task: 462 / 0x4d61c30
Jul 07 20:44:45-812423 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:45-812741 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:45-812961 util-scheduler-8620 DEBUG Adding task: 463 / 0x4d5e5d8
Jul 07 20:44:45-813146 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:45-813442 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:45-817496 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:45-818254 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:45-818457 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:45-821921 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on KNAS
Jul 07 20:44:45-822373 cadet-chn-8620 DEBUG   channel confirm FWD KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:45-823055 cadet-chn-8620 DEBUG   sending channel BCK ack for channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:45-823331 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:45-823546 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:45-823752 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:45-823935 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:45-824122 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:45-824304 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:45-824480 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:45-824651 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:45-824867 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:45-825039 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:45-825301 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:45-825487 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:45-825790 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:45-825960 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:45-826144 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:45-829462 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:45-830153 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:45-830329 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:45-830516 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:45-833652 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:45-833891 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:45-834073 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:45-834295 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:45-834492 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:44:45-834806 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (88 bytes)
Jul 07 20:44:45-835013 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:45-835196 cadet-con-8620 DEBUG last pid sent 5
Jul 07 20:44:45-835373 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:45-835552 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:45-835733 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:45-835976 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:45-836195 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:45-836516 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 88)
Jul 07 20:44:45-836718 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:45-836942 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:45-837125 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 5
Jul 07 20:44:45-837329 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:45-837549 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 88 bytes
Jul 07 20:44:45-837766 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:45-837995 util-scheduler-8620 DEBUG Adding task: 464 / 0x4d5c9e8
Jul 07 20:44:45-838176 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:45-838379 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:45-838555 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:45-838730 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:45-838969 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:45-839163 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:45-839340 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:45-839537 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:45-839769 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:45-839944 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:45-840117 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:45-840287 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:45-840506 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:45-840816 cadet-con-8620 DEBUG  ACK 65
Jul 07 20:44:45-841000 cadet-con-8620 DEBUG  last pid 1, last ack 64, qmax 11, q 0
Jul 07 20:44:45-841292 cadet-con-8620 INFO --> {               ACK} ( 65) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:45-841483 cadet-con-8620 DEBUG  ack 65
Jul 07 20:44:45-841661 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:45-841895 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:45-842100 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:45-842388 cadet-p2p-8620 INFO que {               ACK} ( 65) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:45-842584 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:45-842808 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:45-842988 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 5
Jul 07 20:44:45-843162 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:45-843362 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:45-843562 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:45-843735 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:45-843909 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:45-844144 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:45-844325 cadet-p2p-8620 DEBUG QQQ    payload , 65
Jul 07 20:44:45-844509 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:45-844741 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:45-844933 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:45-845108 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:45-845324 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:45-845528 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:45-845744 util-scheduler-8620 DEBUG Adding task: 465 / 0x46620a0
Jul 07 20:44:45-846022 util-scheduler-8620 DEBUG Checking readiness of task: 465 / 0x46620a0
Jul 07 20:44:45-846218 util-scheduler-8620 DEBUG Checking readiness of task: 463 / 0x4d5e5d8
Jul 07 20:44:45-846408 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-846598 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-849095 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-849388 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-849590 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-849786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-849985 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-850190 util-scheduler-8620 DEBUG Running task: 463 / 0x4d5e5d8
Jul 07 20:44:45-850388 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:45-850575 util-8620 DEBUG process_notify is running
Jul 07 20:44:45-850762 util-8620 DEBUG client_notify is running
Jul 07 20:44:45-851007 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:45-851355 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:45-851589 util-scheduler-8620 DEBUG Running task: 464 / 0x4d5c9e8
Jul 07 20:44:45-851821 util-scheduler-8620 DEBUG Adding task: 466 / 0x4d5c9e8
Jul 07 20:44:45-852066 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:45-852279 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:45-852493 util-scheduler-8620 DEBUG Adding task: 467 / 0x46620a0
Jul 07 20:44:45-852771 util-scheduler-8620 DEBUG Checking readiness of task: 467 / 0x46620a0
Jul 07 20:44:45-852972 util-scheduler-8620 DEBUG Checking readiness of task: 465 / 0x46620a0
Jul 07 20:44:45-853170 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:45-853408 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:45-853599 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:45-853787 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:45-853976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:45-854164 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:45-854352 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:45-854544 util-scheduler-8620 DEBUG Running task: 467 / 0x46620a0
Jul 07 20:44:45-854731 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:45-854920 util-8620 DEBUG process_notify is running
Jul 07 20:44:45-855091 util-8620 DEBUG client_notify is running
Jul 07 20:44:45-855270 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:45-855468 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:45-855657 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:45-855981 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-396337 util-scheduler-8620 DEBUG Checking readiness of task: 465 / 0x46620a0
Jul 07 20:44:46-396761 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-396962 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-397156 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-397375 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-397566 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-397757 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-397997 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-398203 util-scheduler-8620 DEBUG Running task: 465 / 0x46620a0
Jul 07 20:44:46-398625 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:46-398883 util-scheduler-8620 DEBUG Adding task: 468 / 0x4662248
Jul 07 20:44:46-399164 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-399356 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-399545 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-399734 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-399923 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-400112 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-400300 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-400488 util-scheduler-8620 DEBUG Running task: 468 / 0x4662248
Jul 07 20:44:46-400679 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:46-400878 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:46-401110 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:46-401338 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-401545 util-scheduler-8620 DEBUG Adding task: 469 / 0x46620a0
Jul 07 20:44:46-401732 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:46-401937 util-scheduler-8620 DEBUG Adding task: 470 / 0x46620a0
Jul 07 20:44:46-402183 util-scheduler-8620 DEBUG Checking readiness of task: 470 / 0x46620a0
Jul 07 20:44:46-402381 util-scheduler-8620 DEBUG Checking readiness of task: 469 / 0x46620a0
Jul 07 20:44:46-402575 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-402767 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-402961 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-403152 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-403342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-403532 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-403722 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-403922 util-scheduler-8620 DEBUG Running task: 469 / 0x46620a0
Jul 07 20:44:46-404113 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-404296 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-404470 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-404663 util-scheduler-8620 DEBUG Canceling task: 466 / 0x4d5c9e8
Jul 07 20:44:46-404902 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:46-405129 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:46-405400 cadet-p2p-8620 DEBUG Checking 0x54a6d00 towards HS92G30M (->KNAS)
Jul 07 20:44:46-405634 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:46-405812 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:46-406003 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:46-406274 cadet-p2p-8620 INFO snd {               ACK} ( 65) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:46-406468 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:46-406647 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:46-406835 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:46-407009 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:46-407191 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:46-407364 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:46-407600 cadet-p2p-8620 DEBUG Checking 0x54a5f50 towards HS92G30M (->KNAS)
Jul 07 20:44:46-407832 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:46-408036 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 5
Jul 07 20:44:46-408212 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-408438 cadet-p2p-8620 DEBUG Checking 0x54a5f50 towards HS92G30M (->KNAS)
Jul 07 20:44:46-408667 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:46-408847 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 5
Jul 07 20:44:46-409019 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-409184 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:46-409411 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:46-409632 util-scheduler-8620 DEBUG Adding task: 471 / 0x4d5c9e8
Jul 07 20:44:46-409810 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:46-409986 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:46-410184 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:46-410358 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:46-410532 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:46-410770 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:46-410963 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:46-411140 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:46-411338 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:46-411542 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:46-411723 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:46-411925 util-scheduler-8620 DEBUG Adding task: 472 / 0x4d5c9e8
Jul 07 20:44:46-412142 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:46-412339 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-412541 util-scheduler-8620 DEBUG Adding task: 473 / 0x46620a0
Jul 07 20:44:46-412743 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:46-413720 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-413925 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:46-414183 util-scheduler-8620 DEBUG Checking readiness of task: 473 / 0x46620a0
Jul 07 20:44:46-414377 util-scheduler-8620 DEBUG Checking readiness of task: 470 / 0x46620a0
Jul 07 20:44:46-414566 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-414755 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-414944 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-415133 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-415322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-415510 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-415698 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-415889 util-scheduler-8620 DEBUG Running task: 473 / 0x46620a0
Jul 07 20:44:46-416076 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-416254 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-416441 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-416624 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:46-416827 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:46-417022 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:46-417366 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-417601 util-scheduler-8620 DEBUG Running task: 471 / 0x4d5c9e8
Jul 07 20:44:46-417800 util-scheduler-8620 DEBUG Canceling task: 472 / 0x4d5c9e8
Jul 07 20:44:46-418033 util-scheduler-8620 DEBUG Adding task: 474 / 0x4d5c9e8
Jul 07 20:44:46-418262 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:46-418487 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-418691 util-scheduler-8620 DEBUG Adding task: 475 / 0x46620a0
Jul 07 20:44:46-418939 util-scheduler-8620 DEBUG Checking readiness of task: 475 / 0x46620a0
Jul 07 20:44:46-419133 util-scheduler-8620 DEBUG Checking readiness of task: 470 / 0x46620a0
Jul 07 20:44:46-419324 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-419513 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-419702 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-419890 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-420078 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-420266 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-420454 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-420644 util-scheduler-8620 DEBUG Running task: 470 / 0x46620a0
Jul 07 20:44:46-421049 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:46-421303 util-scheduler-8620 DEBUG Adding task: 476 / 0x4662248
Jul 07 20:44:46-421513 util-scheduler-8620 DEBUG Running task: 475 / 0x46620a0
Jul 07 20:44:46-421696 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-421871 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-422040 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-422216 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:46-422406 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:46-422594 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:46-422894 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-423141 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-423333 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-423522 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-423711 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-423900 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-424088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-424276 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-424465 util-scheduler-8620 DEBUG Running task: 476 / 0x4662248
Jul 07 20:44:46-424655 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:46-424851 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:46-425065 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:46-425267 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:46-428266 util-scheduler-8620 DEBUG Adding task: 477 / 0x46620a0
Jul 07 20:44:46-428531 util-scheduler-8620 DEBUG Checking readiness of task: 477 / 0x46620a0
Jul 07 20:44:46-428732 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-428923 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-429112 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-429324 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-429514 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-429713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-429922 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-430183 util-scheduler-8620 DEBUG Running task: 477 / 0x46620a0
Jul 07 20:44:46-430590 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:46-430843 util-scheduler-8620 DEBUG Adding task: 478 / 0x4662248
Jul 07 20:44:46-431097 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-431289 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-431479 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-431667 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-431856 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-432044 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-432233 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-432425 util-scheduler-8620 DEBUG Running task: 478 / 0x4662248
Jul 07 20:44:46-432619 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:46-432819 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:46-433050 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:46-433295 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-433505 util-scheduler-8620 DEBUG Adding task: 479 / 0x46620a0
Jul 07 20:44:46-433697 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:46-433904 util-scheduler-8620 DEBUG Adding task: 480 / 0x46620a0
Jul 07 20:44:46-434172 util-scheduler-8620 DEBUG Checking readiness of task: 480 / 0x46620a0
Jul 07 20:44:46-434371 util-scheduler-8620 DEBUG Checking readiness of task: 479 / 0x46620a0
Jul 07 20:44:46-434567 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-434762 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-434959 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-435156 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-435351 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-435550 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-435746 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-435941 util-scheduler-8620 DEBUG Running task: 479 / 0x46620a0
Jul 07 20:44:46-436131 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-436317 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-436493 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-436691 util-scheduler-8620 DEBUG Canceling task: 474 / 0x4d5c9e8
Jul 07 20:44:46-436934 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:46-437163 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:46-437442 cadet-p2p-8620 DEBUG Checking 0x54a5f50 towards HS92G30M (->KNAS)
Jul 07 20:44:46-437680 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:46-437869 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 5
Jul 07 20:44:46-438052 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-438283 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:46-438466 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:44:46-438645 cadet-p2p-8620 DEBUG   payload ID 6
Jul 07 20:44:46-438942 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 88)
Jul 07 20:44:46-439137 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:46-439319 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:46-439511 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:46-439718 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:46-439954 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:46-440134 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:46-440309 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:46-440481 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:46-440714 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:46-440896 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:46-441072 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:46-441299 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:46-441478 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:46-441659 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:46-441841 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:46-442017 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:46-442185 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:46-442415 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:46-442587 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:46-442820 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:46-443006 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:46-443187 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:46-443380 util-scheduler-8620 DEBUG Canceling task: 460 / 0x4d61c30
Jul 07 20:44:46-443602 util-scheduler-8620 DEBUG Adding task: 481 / 0x4d61c30
Jul 07 20:44:46-443860 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:46-444041 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:46-444220 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 6
Jul 07 20:44:46-444395 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:46-444582 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:44:46-444784 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:46-444958 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:46-445131 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:46-445353 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:46-445558 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 88 bytes.
Jul 07 20:44:46-445740 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:44:46-445919 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:46-446110 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:44:46-446442 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-608395 util-scheduler-8620 DEBUG Checking readiness of task: 480 / 0x46620a0
Jul 07 20:44:46-608764 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-608960 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-609152 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-609365 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-609556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-609748 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-609941 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-610137 util-scheduler-8620 DEBUG Running task: 418 / 0x4d64a70
Jul 07 20:44:46-610385 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:46-610640 cadet-tun-8620 DEBUG  kx started 20 s ago
Jul 07 20:44:46-610871 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:46-611078 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:46-611287 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:46-611530 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:46-611716 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:46-611945 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:46-612288 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:46-612497 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:46-612748 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:46-612965 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:46-613318 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:46-613559 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:46-613795 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:46-613985 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:46-614167 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-614381 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:46-614602 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:46-614839 util-scheduler-8620 DEBUG Adding task: 482 / 0x4d6ff98
Jul 07 20:44:46-615028 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:46-615238 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:46-615419 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:46-615601 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:46-615850 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:46-616047 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:46-616224 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:46-616525 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:46-616782 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:46-616987 util-scheduler-8620 DEBUG Adding task: 483 / 0x4d64a70
Jul 07 20:44:46-617277 util-scheduler-8620 DEBUG Checking readiness of task: 480 / 0x46620a0
Jul 07 20:44:46-617471 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-617671 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-617860 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-618048 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-618236 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-618424 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-618612 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-618801 util-scheduler-8620 DEBUG Running task: 482 / 0x4d6ff98
Jul 07 20:44:46-619010 util-scheduler-8620 DEBUG Adding task: 484 / 0x4d6ff98
Jul 07 20:44:46-619232 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:46-619435 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-619643 util-scheduler-8620 DEBUG Adding task: 485 / 0x46620a0
Jul 07 20:44:46-619885 util-scheduler-8620 DEBUG Checking readiness of task: 485 / 0x46620a0
Jul 07 20:44:46-620077 util-scheduler-8620 DEBUG Checking readiness of task: 480 / 0x46620a0
Jul 07 20:44:46-620266 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-620453 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-620641 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-620830 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-621018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-621225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-621415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-621605 util-scheduler-8620 DEBUG Running task: 485 / 0x46620a0
Jul 07 20:44:46-621790 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-621967 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-622139 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-622318 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:46-622513 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:46-622702 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:46-623016 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:46-933223 util-scheduler-8620 DEBUG Checking readiness of task: 480 / 0x46620a0
Jul 07 20:44:46-933600 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-933796 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-933988 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-934179 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-934369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-934559 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-934749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-934944 util-scheduler-8620 DEBUG Running task: 480 / 0x46620a0
Jul 07 20:44:46-935365 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:46-935623 util-scheduler-8620 DEBUG Adding task: 486 / 0x4662248
Jul 07 20:44:46-935932 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-936124 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-936536 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-936732 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-936921 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-937109 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-937320 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-937511 util-scheduler-8620 DEBUG Running task: 486 / 0x4662248
Jul 07 20:44:46-937702 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:44:46-937902 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:44:46-938133 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:44:46-938396 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:46-938651 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:46-938879 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:46-939093 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:46-939346 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:46-939567 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:46-939759 cadet-con-8620 DEBUG  PID 2 (expected 2+)
Jul 07 20:44:46-939948 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:46-940148 util-scheduler-8620 DEBUG Canceling task: 462 / 0x4d61c30
Jul 07 20:44:46-940383 util-scheduler-8620 DEBUG Adding task: 487 / 0x4d61c30
Jul 07 20:44:46-940565 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:46-940845 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:46-941071 util-scheduler-8620 DEBUG Adding task: 488 / 0x4d5e5d8
Jul 07 20:44:46-941384 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:46-941556 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:46-945149 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:46-946448 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:46-946645 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:46-949343 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on KNAS
Jul 07 20:44:46-949595 cadet-chn-8620 DEBUG   channel confirm FWD KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:46-949833 cadet-chn-8620 DEBUG   sending channel BCK ack for channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:46-950084 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:46-950294 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:46-950492 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:46-950672 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:46-950855 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:46-951065 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:46-951242 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:46-951412 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:46-951627 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:46-951803 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:46-952046 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:46-952235 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:46-952551 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:46-952739 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:46-952929 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:46-957040 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:46-957918 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:46-958126 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:46-958323 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:46-961871 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:46-962159 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:46-962342 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:46-962563 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:46-962757 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:44:46-963036 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (88 bytes)
Jul 07 20:44:46-963235 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:46-963412 cadet-con-8620 DEBUG last pid sent 6
Jul 07 20:44:46-963584 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:46-963755 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:46-963932 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:46-964166 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:46-964372 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:46-964686 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 88)
Jul 07 20:44:46-964885 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:46-965109 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:46-965313 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:46-965489 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-965754 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 88 bytes
Jul 07 20:44:46-965974 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:46-966205 util-scheduler-8620 DEBUG Adding task: 489 / 0x4d5c9e8
Jul 07 20:44:46-966386 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:46-966589 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:46-966764 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:46-966939 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:46-967180 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:46-967374 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:46-967551 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:46-967761 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:46-967995 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:46-968169 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:46-968342 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:46-968513 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:46-968732 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:46-968908 cadet-con-8620 DEBUG  ACK 66
Jul 07 20:44:46-969087 cadet-con-8620 DEBUG  last pid 2, last ack 65, qmax 11, q 0
Jul 07 20:44:46-969432 cadet-con-8620 INFO --> {               ACK} ( 66) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:46-969622 cadet-con-8620 DEBUG  ack 66
Jul 07 20:44:46-969799 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:46-970032 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:46-970263 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:46-970551 cadet-p2p-8620 INFO que {               ACK} ( 66) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:46-970747 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:46-970970 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:46-971150 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:46-971323 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:46-971523 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:46-971724 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:46-971898 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:46-972071 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:46-972316 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:46-972497 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:44:46-972671 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:46-972902 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:46-973098 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:46-973304 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:46-973507 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:46-973693 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:46-973913 util-scheduler-8620 DEBUG Adding task: 490 / 0x46620a0
Jul 07 20:44:46-974199 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:46-974398 util-scheduler-8620 DEBUG Checking readiness of task: 488 / 0x4d5e5d8
Jul 07 20:44:46-974591 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-974783 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-974981 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-975174 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-975367 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-975558 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-975750 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-975949 util-scheduler-8620 DEBUG Running task: 488 / 0x4d5e5d8
Jul 07 20:44:46-976139 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:46-976319 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-976490 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-976723 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:46-977028 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:46-977267 util-scheduler-8620 DEBUG Running task: 489 / 0x4d5c9e8
Jul 07 20:44:46-977615 util-scheduler-8620 DEBUG Adding task: 491 / 0x4d5c9e8
Jul 07 20:44:46-977843 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:46-978045 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:46-978249 util-scheduler-8620 DEBUG Adding task: 492 / 0x46620a0
Jul 07 20:44:46-978500 util-scheduler-8620 DEBUG Checking readiness of task: 492 / 0x46620a0
Jul 07 20:44:46-978691 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:46-978881 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:46-979070 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:46-979257 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:46-979446 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:46-979635 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:46-979822 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:46-980010 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:46-980223 util-scheduler-8620 DEBUG Running task: 492 / 0x46620a0
Jul 07 20:44:46-980408 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:46-980583 util-8620 DEBUG process_notify is running
Jul 07 20:44:46-980752 util-8620 DEBUG client_notify is running
Jul 07 20:44:46-980930 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:46-981125 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:46-981333 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:46-981641 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:47-399131 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:47-399517 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:47-399714 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:47-399910 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:47-400114 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:47-400320 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:47-400511 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:47-400702 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:47-400901 util-scheduler-8620 DEBUG Running task: 459 / 0x4d63a48
Jul 07 20:44:47-401088 cadet-chn-8620 DEBUG !!! RETRANSMIT 0
Jul 07 20:44:47-401410 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:47-401616 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:44:47-401823 cadet-chn-8620 DEBUG   using existing copy: 0x544b120 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:44:47-402014 cadet-chn-8620 DEBUG   new chq: 0x54c2278
Jul 07 20:44:47-402224 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:47-402428 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:47-402607 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:47-402789 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:47-402969 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:47-403146 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:47-403316 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:47-403531 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:47-403703 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:47-403940 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:47-404123 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:47-404433 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:47-404605 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:47-404790 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:47-408897 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:47-409767 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:47-409960 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:47-410150 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:47-413345 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:47-413605 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:47-413795 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:47-414024 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:47-414225 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:47-414515 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (172 bytes)
Jul 07 20:44:47-414722 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:47-414903 cadet-con-8620 DEBUG last pid sent 6
Jul 07 20:44:47-415078 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:47-415250 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:47-415428 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:47-415699 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:47-415908 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:47-416224 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 172)
Jul 07 20:44:47-416424 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:47-416649 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:47-416831 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:47-417006 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:47-417235 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:47-417440 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:47-417615 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:47-417789 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:47-418040 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:47-418223 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:44:47-418398 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:47-418631 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:47-418822 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:47-418998 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:47-419229 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:47-419420 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:47-419596 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:47-419802 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:47-420078 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:47-420299 util-scheduler-8620 DEBUG Adding task: 493 / 0x4d5e5d8
Jul 07 20:44:47-420576 util-scheduler-8620 DEBUG Checking readiness of task: 493 / 0x4d5e5d8
Jul 07 20:44:47-420772 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:47-420966 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:47-421154 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:47-421364 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:47-421553 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:47-421741 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:47-421929 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:47-422118 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:47-422311 util-scheduler-8620 DEBUG Running task: 493 / 0x4d5e5d8
Jul 07 20:44:47-422496 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:47-422674 util-8620 DEBUG process_notify is running
Jul 07 20:44:47-422845 util-8620 DEBUG client_notify is running
Jul 07 20:44:47-423072 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:47-423381 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:47-720361 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:47-720743 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:47-720939 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:47-721132 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:47-721349 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:47-721540 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:47-721730 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:47-721921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:47-722115 util-scheduler-8620 DEBUG Running task: 336 / 0x4d68be8
Jul 07 20:44:47-722390 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:44:47-722597 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:44:47-722852 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:44:47-723042 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:44:47-723279 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:44:47-723488 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:44:47-723821 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:44:47-724022 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:47-724249 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:44:47-724433 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:47-724609 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:47-724818 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:44:47-725037 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:44:47-725290 util-scheduler-8620 DEBUG Adding task: 494 / 0x4d683b0
Jul 07 20:44:47-725474 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:47-725680 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:47-725855 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:47-726030 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:44:47-726269 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:44:47-726451 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:47-726627 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:47-726827 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:47-727082 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:47-727273 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:47-727463 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:47-727652 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:47-727840 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:47-728029 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:47-728218 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:47-728407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:47-728596 util-scheduler-8620 DEBUG Running task: 494 / 0x4d683b0
Jul 07 20:44:47-728805 util-scheduler-8620 DEBUG Adding task: 495 / 0x4d683b0
Jul 07 20:44:47-729027 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:44:47-729252 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:47-729462 util-scheduler-8620 DEBUG Adding task: 496 / 0x46620a0
Jul 07 20:44:47-729703 util-scheduler-8620 DEBUG Checking readiness of task: 496 / 0x46620a0
Jul 07 20:44:47-729896 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:47-730099 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:47-730288 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:47-730477 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:47-730666 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:47-730855 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:47-731043 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:47-731231 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:47-731422 util-scheduler-8620 DEBUG Running task: 496 / 0x46620a0
Jul 07 20:44:47-731607 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:47-731787 util-8620 DEBUG process_notify is running
Jul 07 20:44:47-731958 util-8620 DEBUG client_notify is running
Jul 07 20:44:47-732138 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:47-732359 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:47-732550 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:47-732865 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:48-126386 util-scheduler-8620 DEBUG Checking readiness of task: 490 / 0x46620a0
Jul 07 20:44:48-126784 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-126980 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-127173 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-127366 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-127559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-127749 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-127939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-128135 util-scheduler-8620 DEBUG Running task: 490 / 0x46620a0
Jul 07 20:44:48-128564 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:48-128829 util-scheduler-8620 DEBUG Adding task: 497 / 0x4662248
Jul 07 20:44:48-129109 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-129333 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-129524 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-129713 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-129903 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-130093 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-130282 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-130471 util-scheduler-8620 DEBUG Running task: 497 / 0x4662248
Jul 07 20:44:48-130663 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:48-130866 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:48-131099 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:48-131305 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:48-131512 util-scheduler-8620 DEBUG Adding task: 498 / 0x46620a0
Jul 07 20:44:48-131725 util-scheduler-8620 DEBUG Adding task: 499 / 0x4662248
Jul 07 20:44:48-131967 util-scheduler-8620 DEBUG Checking readiness of task: 498 / 0x46620a0
Jul 07 20:44:48-132161 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-132355 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-132545 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-132734 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-132923 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-133111 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-135545 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-135762 util-scheduler-8620 DEBUG Running task: 498 / 0x46620a0
Jul 07 20:44:48-135953 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:48-136134 util-8620 DEBUG process_notify is running
Jul 07 20:44:48-136306 util-8620 DEBUG client_notify is running
Jul 07 20:44:48-136498 util-scheduler-8620 DEBUG Canceling task: 484 / 0x4d6ff98
Jul 07 20:44:48-136733 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:48-136955 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:48-137225 cadet-p2p-8620 DEBUG Checking 0x54ad920 towards CMHCKRVP (->V8XX)
Jul 07 20:44:48-137463 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:48-137673 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:48-137867 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:48-138174 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:48-138370 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:48-138552 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:48-138741 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:48-138931 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:48-139110 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:48-139294 util-scheduler-8620 DEBUG Canceling task: 443 / 0x4d707d0
Jul 07 20:44:48-139508 util-scheduler-8620 DEBUG Adding task: 500 / 0x4d707d0
Jul 07 20:44:48-139761 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:48-139935 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:48-140118 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:48-140319 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:48-140494 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:48-140669 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:48-140869 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:48-141073 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:48-141281 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:48-141462 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:48-141653 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:48-142676 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:48-142895 util-scheduler-8620 DEBUG Running task: 499 / 0x4662248
Jul 07 20:44:48-143088 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:48-143284 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:48-143502 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:44:48-143704 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:48-143909 util-scheduler-8620 DEBUG Adding task: 501 / 0x46620a0
Jul 07 20:44:48-144096 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:48-144302 util-scheduler-8620 DEBUG Adding task: 502 / 0x46620a0
Jul 07 20:44:48-144558 util-scheduler-8620 DEBUG Checking readiness of task: 502 / 0x46620a0
Jul 07 20:44:48-144750 util-scheduler-8620 DEBUG Checking readiness of task: 501 / 0x46620a0
Jul 07 20:44:48-144942 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-145401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-145596 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-145787 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-145976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-146166 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-146355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-146546 util-scheduler-8620 DEBUG Running task: 501 / 0x46620a0
Jul 07 20:44:48-146730 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:48-146905 util-8620 DEBUG process_notify is running
Jul 07 20:44:48-147077 util-8620 DEBUG client_notify is running
Jul 07 20:44:48-147259 util-scheduler-8620 DEBUG Canceling task: 495 / 0x4d683b0
Jul 07 20:44:48-147479 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:44:48-147756 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:44:48-147990 cadet-p2p-8620 DEBUG Checking 0x54cc1e0 towards KT5Q8VM8 (->P00P)
Jul 07 20:44:48-148232 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:44:48-148423 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:48-148593 cadet-p2p-8620 DEBUG   path create
Jul 07 20:44:48-148781 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:44:48-149276 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:44:48-149543 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:44:48-149735 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:48-149914 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:48-150102 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:44:48-150282 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:44:48-150494 util-scheduler-8620 DEBUG Adding task: 503 / 0x4d68be8
Jul 07 20:44:48-150727 cadet-con-8620 DEBUG next keepalive in 32 s
Jul 07 20:44:48-150899 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:48-151078 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:48-151277 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:44:48-151452 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:48-151626 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:48-151824 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:44:48-152028 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:44:48-152211 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:48-152389 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:48-152577 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:48-153306 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:48-809792 util-scheduler-8620 DEBUG Checking readiness of task: 502 / 0x46620a0
Jul 07 20:44:48-810173 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-810371 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-810564 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-810755 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-810946 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-811136 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-811326 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-811521 util-scheduler-8620 DEBUG Running task: 502 / 0x46620a0
Jul 07 20:44:48-811948 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:48-812204 util-scheduler-8620 DEBUG Adding task: 504 / 0x4662248
Jul 07 20:44:48-812483 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-812675 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-812865 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-813055 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-813272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-813463 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-813655 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-813844 util-scheduler-8620 DEBUG Running task: 504 / 0x4662248
Jul 07 20:44:48-814036 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:44:48-814237 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:44:48-814468 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:44:48-814736 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:48-814979 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:48-815207 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:48-815491 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:48-815739 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:48-815977 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:48-816166 cadet-con-8620 DEBUG  PID 3 (expected 3+)
Jul 07 20:44:48-816348 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:48-816536 util-scheduler-8620 DEBUG Canceling task: 487 / 0x4d61c30
Jul 07 20:44:48-816759 util-scheduler-8620 DEBUG Adding task: 505 / 0x4d61c30
Jul 07 20:44:48-816939 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:48-817227 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:48-817448 util-scheduler-8620 DEBUG Adding task: 506 / 0x4d5e5d8
Jul 07 20:44:48-817632 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:48-817800 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:48-821383 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:48-822662 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:48-822856 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:48-825573 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on KNAS
Jul 07 20:44:48-825824 cadet-chn-8620 DEBUG   channel confirm FWD KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:48-826062 cadet-chn-8620 DEBUG   sending channel BCK ack for channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:48-826314 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:48-826525 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:48-826726 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:48-826906 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:48-827090 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:48-827272 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:48-827450 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:48-827620 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:48-827836 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:48-828009 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:48-828245 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:48-828429 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:48-828721 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:48-828892 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:48-829076 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:48-832633 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:48-833266 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:48-833445 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:48-833636 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:48-836805 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:48-837045 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:48-837251 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:48-837475 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:48-837667 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:44:48-837940 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (88 bytes)
Jul 07 20:44:48-838137 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:48-838314 cadet-con-8620 DEBUG last pid sent 6
Jul 07 20:44:48-838487 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:44:48-838663 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:48-838850 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 3
Jul 07 20:44:48-839094 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:48-839311 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:48-839638 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 88)
Jul 07 20:44:48-839846 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:48-840077 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:48-840261 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:48-840443 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:48-840655 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:48-840906 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:48-841088 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:48-841293 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:48-841540 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-841724 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:44:48-841898 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:48-842133 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-842325 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:48-842501 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:48-842734 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-842927 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:48-843103 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:48-843336 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-843530 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:48-843706 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:48-843902 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:48-844135 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:48-844310 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:48-844483 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:48-844654 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:48-844874 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:48-845051 cadet-con-8620 DEBUG  ACK 67
Jul 07 20:44:48-845249 cadet-con-8620 DEBUG  last pid 3, last ack 66, qmax 11, q 0
Jul 07 20:44:48-846289 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:44:48-846838 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:44:48-847123 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:44:48-847316 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:48-847498 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:48-847688 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:44:48-847863 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:48-848056 cadet-con-8620 DEBUG  C_P- 0x4d61c30 4
Jul 07 20:44:48-848231 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:48-848456 cadet-p2p-8620 DEBUG Checking 0x54bfff0 towards HS92G30M (->KNAS)
Jul 07 20:44:48-848688 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:48-848870 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:48-849043 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:48-850484 cadet-con-8620 INFO --> {               ACK} ( 67) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:48-850685 cadet-con-8620 DEBUG  ack 67
Jul 07 20:44:48-850865 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 3
Jul 07 20:44:48-851102 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:48-851309 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:48-851617 cadet-p2p-8620 INFO que {               ACK} ( 67) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:48-851821 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:48-852047 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:48-852231 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 6
Jul 07 20:44:48-852406 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:48-852609 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:48-852811 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:48-852987 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:48-853167 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:48-853429 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-853617 cadet-p2p-8620 DEBUG QQQ    payload , 67
Jul 07 20:44:48-853794 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:48-854030 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-854247 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:48-854426 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:48-854662 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-854856 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:48-855035 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:48-855271 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:48-855471 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:48-855651 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:48-855858 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:48-856057 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:48-856288 util-scheduler-8620 DEBUG Adding task: 507 / 0x46620a0
Jul 07 20:44:48-856582 util-scheduler-8620 DEBUG Checking readiness of task: 507 / 0x46620a0
Jul 07 20:44:48-856787 util-scheduler-8620 DEBUG Checking readiness of task: 506 / 0x4d5e5d8
Jul 07 20:44:48-856985 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:48-857178 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:48-857399 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:48-857588 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:48-857777 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:48-857966 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:48-858154 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:48-858346 util-scheduler-8620 DEBUG Running task: 506 / 0x4d5e5d8
Jul 07 20:44:48-858532 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:48-858711 util-8620 DEBUG process_notify is running
Jul 07 20:44:48-858883 util-8620 DEBUG client_notify is running
Jul 07 20:44:48-859116 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:48-859439 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:49-794249 util-scheduler-8620 DEBUG Checking readiness of task: 507 / 0x46620a0
Jul 07 20:44:49-794631 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-794828 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-795024 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-795222 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-795417 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-795609 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-795815 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-796016 util-scheduler-8620 DEBUG Running task: 507 / 0x46620a0
Jul 07 20:44:49-796447 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:49-796711 util-scheduler-8620 DEBUG Adding task: 508 / 0x4662248
Jul 07 20:44:49-796992 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-797184 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-797402 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-797592 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-797780 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-797970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-798158 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-798348 util-scheduler-8620 DEBUG Running task: 508 / 0x4662248
Jul 07 20:44:49-798539 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:49-798768 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:49-799000 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:49-799266 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:49-799522 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:49-799731 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:49-799914 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:49-800087 cadet-con-8620 DEBUG   ACK 65 (was 64)
Jul 07 20:44:49-800324 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:49-800554 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:49-800759 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:49-800940 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:44:49-801118 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:49-801351 util-scheduler-8620 DEBUG Adding task: 509 / 0x46620a0
Jul 07 20:44:49-947558 util-scheduler-8620 DEBUG Checking readiness of task: 509 / 0x46620a0
Jul 07 20:44:49-947927 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-948124 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-948316 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-948508 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-948699 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-948890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-949081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-949301 util-scheduler-8620 DEBUG Running task: 509 / 0x46620a0
Jul 07 20:44:49-949721 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:49-949976 util-scheduler-8620 DEBUG Adding task: 510 / 0x4662248
Jul 07 20:44:49-950252 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-950443 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-950633 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-950822 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-951011 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-951231 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-951421 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-951610 util-scheduler-8620 DEBUG Running task: 510 / 0x4662248
Jul 07 20:44:49-951804 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:49-952003 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:49-952244 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:49-952450 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:49-952657 util-scheduler-8620 DEBUG Adding task: 511 / 0x46620a0
Jul 07 20:44:49-952844 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:49-953048 util-scheduler-8620 DEBUG Adding task: 512 / 0x46620a0
Jul 07 20:44:49-953313 util-scheduler-8620 DEBUG Checking readiness of task: 512 / 0x46620a0
Jul 07 20:44:49-953507 util-scheduler-8620 DEBUG Checking readiness of task: 511 / 0x46620a0
Jul 07 20:44:49-953697 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-953888 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-954076 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-954264 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-954452 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-954668 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-954857 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-955048 util-scheduler-8620 DEBUG Running task: 511 / 0x46620a0
Jul 07 20:44:49-955232 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:49-955410 util-8620 DEBUG process_notify is running
Jul 07 20:44:49-955584 util-8620 DEBUG client_notify is running
Jul 07 20:44:49-955772 util-scheduler-8620 DEBUG Canceling task: 491 / 0x4d5c9e8
Jul 07 20:44:49-955995 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:49-956214 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:49-956453 cadet-p2p-8620 DEBUG Checking 0x54e2258 towards HS92G30M (->KNAS)
Jul 07 20:44:49-956685 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:49-956861 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:49-957052 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:49-957340 cadet-p2p-8620 INFO snd {               ACK} ( 67) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:49-957534 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:49-957714 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:49-957903 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:49-958081 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:49-958269 cadet-con-8620 DEBUG  C_P- 0x4d61c30 4
Jul 07 20:44:49-958445 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:49-958686 cadet-p2p-8620 DEBUG Checking 0x54bfff0 towards HS92G30M (->KNAS)
Jul 07 20:44:49-958930 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:49-959117 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 6
Jul 07 20:44:49-959298 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:49-959538 cadet-p2p-8620 DEBUG Checking 0x54bfff0 towards HS92G30M (->KNAS)
Jul 07 20:44:49-959777 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:49-959964 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 6
Jul 07 20:44:49-960142 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:49-960313 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:49-960531 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:49-960784 util-scheduler-8620 DEBUG Adding task: 513 / 0x4d5c9e8
Jul 07 20:44:49-960973 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:49-961156 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:49-961393 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:49-961572 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:44:49-961755 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:49-962027 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:49-962231 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:49-962415 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:49-962657 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:49-962858 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:49-963038 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:49-963279 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:49-963475 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:49-963655 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:49-963861 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:49-964069 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:49-964253 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:49-964472 util-scheduler-8620 DEBUG Adding task: 514 / 0x4d5c9e8
Jul 07 20:44:49-964809 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:49-965013 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:49-965243 util-scheduler-8620 DEBUG Adding task: 515 / 0x46620a0
Jul 07 20:44:49-965476 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:49-966242 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:49-966443 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:49-966708 util-scheduler-8620 DEBUG Checking readiness of task: 515 / 0x46620a0
Jul 07 20:44:49-966903 util-scheduler-8620 DEBUG Checking readiness of task: 512 / 0x46620a0
Jul 07 20:44:49-967093 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-967283 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-967471 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-967660 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-967848 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-968036 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-968224 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-968415 util-scheduler-8620 DEBUG Running task: 515 / 0x46620a0
Jul 07 20:44:49-968600 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:49-968778 util-8620 DEBUG process_notify is running
Jul 07 20:44:49-968950 util-8620 DEBUG client_notify is running
Jul 07 20:44:49-969127 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:49-969346 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:49-969534 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:49-969813 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:49-970020 util-scheduler-8620 DEBUG Running task: 513 / 0x4d5c9e8
Jul 07 20:44:49-970213 util-scheduler-8620 DEBUG Canceling task: 514 / 0x4d5c9e8
Jul 07 20:44:49-970439 util-scheduler-8620 DEBUG Adding task: 516 / 0x4d5c9e8
Jul 07 20:44:49-970655 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:49-970850 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:49-971047 util-scheduler-8620 DEBUG Adding task: 517 / 0x46620a0
Jul 07 20:44:49-971286 util-scheduler-8620 DEBUG Checking readiness of task: 517 / 0x46620a0
Jul 07 20:44:49-971476 util-scheduler-8620 DEBUG Checking readiness of task: 512 / 0x46620a0
Jul 07 20:44:49-971665 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:49-971854 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:49-972042 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:49-972231 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:49-972420 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:49-972608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:49-972796 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:49-972986 util-scheduler-8620 DEBUG Running task: 517 / 0x46620a0
Jul 07 20:44:49-973169 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:49-973365 util-8620 DEBUG process_notify is running
Jul 07 20:44:49-973533 util-8620 DEBUG client_notify is running
Jul 07 20:44:49-973708 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:49-973899 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:49-974086 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:49-974363 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-274922 util-scheduler-8620 DEBUG Checking readiness of task: 512 / 0x46620a0
Jul 07 20:44:50-275295 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-275520 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-275713 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-275904 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-276095 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-276285 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-276475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-276669 util-scheduler-8620 DEBUG Running task: 512 / 0x46620a0
Jul 07 20:44:50-277090 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:50-277377 util-scheduler-8620 DEBUG Adding task: 518 / 0x4662248
Jul 07 20:44:50-277656 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-277852 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-278042 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-278231 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-278421 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-278609 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-278797 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-278986 util-scheduler-8620 DEBUG Running task: 518 / 0x4662248
Jul 07 20:44:50-279177 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:50-279376 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:50-279607 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:50-279813 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-280018 util-scheduler-8620 DEBUG Adding task: 519 / 0x46620a0
Jul 07 20:44:50-280204 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:50-280408 util-scheduler-8620 DEBUG Adding task: 520 / 0x46620a0
Jul 07 20:44:50-280650 util-scheduler-8620 DEBUG Checking readiness of task: 520 / 0x46620a0
Jul 07 20:44:50-280853 util-scheduler-8620 DEBUG Checking readiness of task: 519 / 0x46620a0
Jul 07 20:44:50-281043 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-281258 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-281447 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-281635 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-281823 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-282011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-282199 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-282390 util-scheduler-8620 DEBUG Running task: 519 / 0x46620a0
Jul 07 20:44:50-282575 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-282752 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-282923 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-283111 util-scheduler-8620 DEBUG Canceling task: 516 / 0x4d5c9e8
Jul 07 20:44:50-283334 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:50-283553 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:50-283794 cadet-p2p-8620 DEBUG Checking 0x54bfff0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-284026 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-284207 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 6
Jul 07 20:44:50-284383 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-284617 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:50-284793 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:44:50-284968 cadet-p2p-8620 DEBUG   payload ID 7
Jul 07 20:44:50-285294 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 88)
Jul 07 20:44:50-285490 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:50-285670 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:50-285858 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:50-286046 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:50-286275 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:50-286449 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:50-286620 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:50-286791 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:50-286987 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:50-287162 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:50-287335 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:50-287536 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:50-287714 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:50-287895 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:50-288080 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:50-288260 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:50-288431 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:50-288651 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:50-288826 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:50-289059 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:50-289265 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:50-289446 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:50-289634 util-scheduler-8620 DEBUG Canceling task: 481 / 0x4d61c30
Jul 07 20:44:50-289859 util-scheduler-8620 DEBUG Adding task: 521 / 0x4d61c30
Jul 07 20:44:50-290108 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:50-290287 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:50-290464 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 7
Jul 07 20:44:50-290637 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:50-290858 cadet-p2p-8620 DEBUG Checking 0x54cadb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-291087 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-291267 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 7
Jul 07 20:44:50-291439 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-291668 cadet-p2p-8620 DEBUG Checking 0x54cadb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-291896 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-292076 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 7
Jul 07 20:44:50-292247 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-292413 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:50-292617 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `KNAS'
Jul 07 20:44:50-292829 util-scheduler-8620 DEBUG Adding task: 522 / 0x4d5c9e8
Jul 07 20:44:50-293008 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:50-293185 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:44:50-293404 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:50-293578 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:50-293752 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:50-293993 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:50-294187 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:44:50-294364 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:44:50-294596 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:50-294788 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:50-294962 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:50-295159 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:50-295364 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 88 bytes.
Jul 07 20:44:50-295564 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:44:50-295766 util-scheduler-8620 DEBUG Adding task: 523 / 0x4d5c9e8
Jul 07 20:44:50-295986 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:50-296181 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-296385 util-scheduler-8620 DEBUG Adding task: 524 / 0x46620a0
Jul 07 20:44:50-296585 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:44:50-297724 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-297939 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:50-298193 util-scheduler-8620 DEBUG Checking readiness of task: 524 / 0x46620a0
Jul 07 20:44:50-298387 util-scheduler-8620 DEBUG Checking readiness of task: 520 / 0x46620a0
Jul 07 20:44:50-298576 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-298765 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-298954 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-299142 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-299332 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-299521 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-299709 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-299902 util-scheduler-8620 DEBUG Running task: 524 / 0x46620a0
Jul 07 20:44:50-300090 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-300268 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-300448 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-300636 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:50-300841 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:50-301038 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:50-301393 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-301620 util-scheduler-8620 DEBUG Running task: 522 / 0x4d5c9e8
Jul 07 20:44:50-301822 util-scheduler-8620 DEBUG Canceling task: 523 / 0x4d5c9e8
Jul 07 20:44:50-302053 util-scheduler-8620 DEBUG Adding task: 525 / 0x4d5c9e8
Jul 07 20:44:50-302288 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:50-302493 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-302705 util-scheduler-8620 DEBUG Adding task: 526 / 0x46620a0
Jul 07 20:44:50-302973 util-scheduler-8620 DEBUG Checking readiness of task: 526 / 0x46620a0
Jul 07 20:44:50-303172 util-scheduler-8620 DEBUG Checking readiness of task: 520 / 0x46620a0
Jul 07 20:44:50-303371 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-303567 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-303762 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-303961 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-304155 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-304350 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-304545 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-304740 util-scheduler-8620 DEBUG Running task: 520 / 0x46620a0
Jul 07 20:44:50-305159 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:50-305441 util-scheduler-8620 DEBUG Adding task: 527 / 0x4662248
Jul 07 20:44:50-305664 util-scheduler-8620 DEBUG Running task: 526 / 0x46620a0
Jul 07 20:44:50-305853 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-306056 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-306228 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-306409 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:50-307012 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:50-307221 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:50-307478 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-307744 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-307937 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-308128 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-308318 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-308506 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-308695 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-308883 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-309073 util-scheduler-8620 DEBUG Running task: 527 / 0x4662248
Jul 07 20:44:50-309285 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:50-309482 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:50-309723 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:50-310441 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:50-310665 util-scheduler-8620 DEBUG Adding task: 528 / 0x46620a0
Jul 07 20:44:50-310915 util-scheduler-8620 DEBUG Checking readiness of task: 528 / 0x46620a0
Jul 07 20:44:50-311107 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-311296 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-311485 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-311674 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-311862 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-312050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-312238 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-312428 util-scheduler-8620 DEBUG Running task: 528 / 0x46620a0
Jul 07 20:44:50-312831 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:50-313061 util-scheduler-8620 DEBUG Adding task: 529 / 0x4662248
Jul 07 20:44:50-313329 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-313520 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-313709 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-313899 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-314087 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-314276 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-314464 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-314652 util-scheduler-8620 DEBUG Running task: 529 / 0x4662248
Jul 07 20:44:50-314841 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:50-315032 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:50-315244 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:50-315446 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-315644 util-scheduler-8620 DEBUG Adding task: 530 / 0x46620a0
Jul 07 20:44:50-315827 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:50-316022 util-scheduler-8620 DEBUG Adding task: 531 / 0x46620a0
Jul 07 20:44:50-316280 util-scheduler-8620 DEBUG Checking readiness of task: 531 / 0x46620a0
Jul 07 20:44:50-316471 util-scheduler-8620 DEBUG Checking readiness of task: 530 / 0x46620a0
Jul 07 20:44:50-316661 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-316849 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-317038 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-317244 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-317434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-317622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-317810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-318000 util-scheduler-8620 DEBUG Running task: 530 / 0x46620a0
Jul 07 20:44:50-318184 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-318360 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-318529 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-318714 util-scheduler-8620 DEBUG Canceling task: 525 / 0x4d5c9e8
Jul 07 20:44:50-318934 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 172 bytes.
Jul 07 20:44:50-319151 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:50-319387 cadet-p2p-8620 DEBUG Checking 0x54cadb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-319628 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-319810 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 7
Jul 07 20:44:50-319984 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-320204 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:50-320380 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:44:50-320554 cadet-p2p-8620 DEBUG   payload ID 8
Jul 07 20:44:50-320839 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 172)
Jul 07 20:44:50-321040 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:50-321241 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:50-321511 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:50-321691 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:50-321860 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:50-322048 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:50-322225 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:44:50-322453 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:44:50-322625 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:50-322853 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:44:50-323050 util-scheduler-8620 DEBUG Adding task: 532 / 0x4d63a48
Jul 07 20:44:50-323253 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:50-323483 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:50-323657 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:50-323831 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:50-324002 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:50-324197 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:50-324371 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:50-324544 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:50-324742 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:50-324919 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:50-325099 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:50-325301 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:50-325477 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:50-325646 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:50-325862 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:50-326033 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:50-326263 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:50-326447 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:50-326642 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:50-326829 util-scheduler-8620 DEBUG Canceling task: 521 / 0x4d61c30
Jul 07 20:44:50-327038 util-scheduler-8620 DEBUG Adding task: 533 / 0x4d61c30
Jul 07 20:44:50-327279 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:50-327457 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:50-327634 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 8
Jul 07 20:44:50-327806 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:50-328026 cadet-p2p-8620 DEBUG Checking 0x54e0eb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-328254 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-328434 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 8
Jul 07 20:44:50-328619 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-328848 cadet-p2p-8620 DEBUG Checking 0x54e0eb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-329077 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-329291 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 8
Jul 07 20:44:50-329463 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-329628 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:50-329832 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `KNAS'
Jul 07 20:44:50-330043 util-scheduler-8620 DEBUG Adding task: 534 / 0x4d5c9e8
Jul 07 20:44:50-330221 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:50-330398 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:44:50-330596 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:50-330770 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:50-330944 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:50-331180 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:50-331374 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:44:50-331549 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:44:50-331746 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:50-331948 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 172 bytes.
Jul 07 20:44:50-332187 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:44:50-332397 util-scheduler-8620 DEBUG Adding task: 535 / 0x4d5c9e8
Jul 07 20:44:50-332621 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:50-332832 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-333046 util-scheduler-8620 DEBUG Adding task: 536 / 0x46620a0
Jul 07 20:44:50-333278 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:44:50-334316 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-334553 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:50-334829 util-scheduler-8620 DEBUG Checking readiness of task: 536 / 0x46620a0
Jul 07 20:44:50-335031 util-scheduler-8620 DEBUG Checking readiness of task: 531 / 0x46620a0
Jul 07 20:44:50-335234 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-335429 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-335623 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-335817 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-336014 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-336208 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-336403 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-336600 util-scheduler-8620 DEBUG Running task: 536 / 0x46620a0
Jul 07 20:44:50-336794 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-336977 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-337155 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-337388 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:50-337622 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:50-337819 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:50-338161 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-338389 util-scheduler-8620 DEBUG Running task: 534 / 0x4d5c9e8
Jul 07 20:44:50-338587 util-scheduler-8620 DEBUG Canceling task: 535 / 0x4d5c9e8
Jul 07 20:44:50-338882 util-scheduler-8620 DEBUG Adding task: 537 / 0x4d5c9e8
Jul 07 20:44:50-339115 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:50-339317 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-339521 util-scheduler-8620 DEBUG Adding task: 538 / 0x46620a0
Jul 07 20:44:50-339775 util-scheduler-8620 DEBUG Checking readiness of task: 538 / 0x46620a0
Jul 07 20:44:50-339967 util-scheduler-8620 DEBUG Checking readiness of task: 531 / 0x46620a0
Jul 07 20:44:50-340157 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-340345 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-340534 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-340721 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-340910 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-341098 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-341309 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-341499 util-scheduler-8620 DEBUG Running task: 531 / 0x46620a0
Jul 07 20:44:50-341904 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:50-342136 util-scheduler-8620 DEBUG Adding task: 539 / 0x4662248
Jul 07 20:44:50-342345 util-scheduler-8620 DEBUG Running task: 538 / 0x46620a0
Jul 07 20:44:50-342528 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-342704 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-342873 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-343049 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:50-343238 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:50-343426 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:50-343724 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:50-343973 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-344164 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-344352 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-344541 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-344729 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-344917 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-345105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-345313 util-scheduler-8620 DEBUG Running task: 539 / 0x4662248
Jul 07 20:44:50-345503 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:50-345698 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:50-345914 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:50-346094 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:50-346298 util-scheduler-8620 DEBUG Adding task: 540 / 0x46620a0
Jul 07 20:44:50-346536 util-scheduler-8620 DEBUG Checking readiness of task: 540 / 0x46620a0
Jul 07 20:44:50-346726 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-346934 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-347123 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-347313 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-347501 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-347689 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-347877 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-348066 util-scheduler-8620 DEBUG Running task: 540 / 0x46620a0
Jul 07 20:44:50-348463 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:50-348694 util-scheduler-8620 DEBUG Adding task: 541 / 0x4662248
Jul 07 20:44:50-348939 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-349129 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-349339 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-349531 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-349723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-349915 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-350104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-350295 util-scheduler-8620 DEBUG Running task: 541 / 0x4662248
Jul 07 20:44:50-350486 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:50-350680 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:50-350892 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:50-351091 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:50-351290 util-scheduler-8620 DEBUG Adding task: 542 / 0x46620a0
Jul 07 20:44:50-351473 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:50-351670 util-scheduler-8620 DEBUG Adding task: 543 / 0x46620a0
Jul 07 20:44:50-351924 util-scheduler-8620 DEBUG Checking readiness of task: 543 / 0x46620a0
Jul 07 20:44:50-352115 util-scheduler-8620 DEBUG Checking readiness of task: 542 / 0x46620a0
Jul 07 20:44:50-352304 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:50-352492 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:50-352681 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:50-352869 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:50-353057 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:50-353266 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:50-353455 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:50-353645 util-scheduler-8620 DEBUG Running task: 542 / 0x46620a0
Jul 07 20:44:50-353831 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:50-354005 util-8620 DEBUG process_notify is running
Jul 07 20:44:50-354173 util-8620 DEBUG client_notify is running
Jul 07 20:44:50-354356 util-scheduler-8620 DEBUG Canceling task: 537 / 0x4d5c9e8
Jul 07 20:44:50-354574 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 88 bytes.
Jul 07 20:44:50-354789 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:50-355025 cadet-p2p-8620 DEBUG Checking 0x54e0eb0 towards HS92G30M (->KNAS)
Jul 07 20:44:50-355256 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:50-355436 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 8
Jul 07 20:44:50-355610 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:50-355831 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:50-356007 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:44:50-356181 cadet-p2p-8620 DEBUG   payload ID 9
Jul 07 20:44:50-356481 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 88)
Jul 07 20:44:50-356676 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:50-356854 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:50-357040 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:50-357247 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:50-357476 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:50-357650 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:50-357832 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:44:50-358003 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:50-358199 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:50-358372 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:50-358544 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:50-358742 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:50-358919 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:50-359099 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:50-359278 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:50-359453 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:50-359622 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:50-359836 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:50-360007 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:50-360236 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:50-360419 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:50-360598 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:50-360782 util-scheduler-8620 DEBUG Canceling task: 533 / 0x4d61c30
Jul 07 20:44:50-360992 util-scheduler-8620 DEBUG Adding task: 544 / 0x4d61c30
Jul 07 20:44:50-361261 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:50-361446 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:44:50-361629 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 9
Jul 07 20:44:50-361804 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:50-361990 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:44:50-362200 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:50-362385 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:50-362563 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:50-362770 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:50-362981 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 88 bytes.
Jul 07 20:44:50-363170 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:44:50-363359 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:50-363554 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:44:50-366254 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:51-618409 util-scheduler-8620 DEBUG Checking readiness of task: 543 / 0x46620a0
Jul 07 20:44:51-618789 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-618985 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-619177 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-619366 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-619557 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-619747 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-619937 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-620130 util-scheduler-8620 DEBUG Running task: 483 / 0x4d64a70
Jul 07 20:44:51-620371 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:51-620619 cadet-tun-8620 DEBUG  kx started 25 s ago
Jul 07 20:44:51-620825 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:51-621025 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:51-621353 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:51-621593 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:51-621775 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:51-622000 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:51-622295 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:51-622494 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:51-622735 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:51-622944 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:51-623264 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:51-623470 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:51-623701 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:51-623886 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:51-624065 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:51-624278 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:51-624497 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:51-624729 util-scheduler-8620 DEBUG Adding task: 545 / 0x4d6ff98
Jul 07 20:44:51-624911 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:51-625118 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:51-625320 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:51-625497 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:51-625739 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:51-625936 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:51-626115 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:51-626316 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:51-626564 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:51-626766 util-scheduler-8620 DEBUG Adding task: 546 / 0x4d64a70
Jul 07 20:44:51-627030 util-scheduler-8620 DEBUG Checking readiness of task: 543 / 0x46620a0
Jul 07 20:44:51-627224 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-627415 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-627619 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-627809 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-627999 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-628189 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-628393 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-628582 util-scheduler-8620 DEBUG Running task: 545 / 0x4d6ff98
Jul 07 20:44:51-628791 util-scheduler-8620 DEBUG Adding task: 547 / 0x4d6ff98
Jul 07 20:44:51-629015 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:51-629237 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:51-629448 util-scheduler-8620 DEBUG Adding task: 548 / 0x46620a0
Jul 07 20:44:51-629692 util-scheduler-8620 DEBUG Checking readiness of task: 548 / 0x46620a0
Jul 07 20:44:51-629884 util-scheduler-8620 DEBUG Checking readiness of task: 543 / 0x46620a0
Jul 07 20:44:51-630072 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-630261 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-630449 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-630637 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-630825 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-631013 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-631201 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-631413 util-scheduler-8620 DEBUG Running task: 548 / 0x46620a0
Jul 07 20:44:51-631598 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:51-631777 util-8620 DEBUG process_notify is running
Jul 07 20:44:51-631949 util-8620 DEBUG client_notify is running
Jul 07 20:44:51-632128 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:51-632323 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:51-632512 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:51-632809 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:51-790310 util-scheduler-8620 DEBUG Checking readiness of task: 543 / 0x46620a0
Jul 07 20:44:51-790610 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-790810 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-791002 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-791193 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-791383 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-791573 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-791764 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-791957 util-scheduler-8620 DEBUG Running task: 543 / 0x46620a0
Jul 07 20:44:51-792372 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:51-792622 util-scheduler-8620 DEBUG Adding task: 549 / 0x4662248
Jul 07 20:44:51-792888 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-793080 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-793295 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-793488 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-793682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-793873 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-794064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-794258 util-scheduler-8620 DEBUG Running task: 549 / 0x4662248
Jul 07 20:44:51-794451 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:51-794655 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:51-794885 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:51-795152 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:51-795413 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:51-795625 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:51-795827 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:51-796003 cadet-con-8620 DEBUG   ACK 66 (was 65)
Jul 07 20:44:51-796235 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:51-796467 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:51-796672 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:51-797735 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:44:51-798183 util-scheduler-8620 DEBUG Adding task: 550 / 0x4662248
Jul 07 20:44:51-798441 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-798637 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-798828 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-799018 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-799207 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-799396 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-799609 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-799800 util-scheduler-8620 DEBUG Running task: 550 / 0x4662248
Jul 07 20:44:51-799990 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:44:51-800186 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:44:51-800402 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:44:51-800646 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:51-800883 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:51-801110 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:51-801337 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:51-801578 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:51-801782 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:51-801969 cadet-con-8620 DEBUG  PID 4 (expected 4+)
Jul 07 20:44:51-802147 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:51-802335 util-scheduler-8620 DEBUG Canceling task: 505 / 0x4d61c30
Jul 07 20:44:51-802554 util-scheduler-8620 DEBUG Adding task: 551 / 0x4d61c30
Jul 07 20:44:51-802734 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:51-802991 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:51-803205 util-scheduler-8620 DEBUG Adding task: 552 / 0x4d5e5d8
Jul 07 20:44:51-803389 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:51-803556 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:51-807143 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:51-810423 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:51-810682 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:51-814502 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:44:51-817448 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:44:51-819188 cadet-chn-8620 DEBUG   id 0
Jul 07 20:44:51-820386 cadet-chn-8620 DEBUG !!! Freeing 0
Jul 07 20:44:51-822730 cadet-chn-8620 INFO !!!  took 1498454 µs, new delay 1498454 µs
Jul 07 20:44:51-824490 cadet-chn-8620 DEBUG  COPYFREE 0x544b120
Jul 07 20:44:51-825734 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:51-826657 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:44:51-827054 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:51-827245 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:51-827433 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:51-827619 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:51-827798 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:51-827975 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:51-828201 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:51-828378 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:51-828685 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:51-828876 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:51-829163 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:44:51-829428 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:51-830348 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:44:51-831120 util-scheduler-8620 DEBUG Canceling task: 532 / 0x4d63a48
Jul 07 20:44:51-831963 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:51-832146 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:51-832324 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:51-832496 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:51-832717 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:51-832895 cadet-con-8620 DEBUG  ACK 68
Jul 07 20:44:51-833074 cadet-con-8620 DEBUG  last pid 4, last ack 67, qmax 11, q 0
Jul 07 20:44:51-833369 cadet-con-8620 INFO --> {               ACK} ( 68) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:51-833561 cadet-con-8620 DEBUG  ack 68
Jul 07 20:44:51-833739 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:51-834000 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:51-834210 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:51-834508 cadet-p2p-8620 INFO que {               ACK} ( 68) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:51-834706 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:51-834930 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:51-835112 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:51-835287 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:51-835493 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:51-835709 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:51-835932 util-scheduler-8620 DEBUG Adding task: 553 / 0x4d5c9e8
Jul 07 20:44:51-836113 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:51-836317 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:51-836493 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:51-836667 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:51-836904 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:51-837086 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:44:51-837282 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:51-837481 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:51-837674 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:51-837888 util-scheduler-8620 DEBUG Adding task: 554 / 0x46620a0
Jul 07 20:44:51-838158 util-scheduler-8620 DEBUG Checking readiness of task: 554 / 0x46620a0
Jul 07 20:44:51-838353 util-scheduler-8620 DEBUG Checking readiness of task: 552 / 0x4d5e5d8
Jul 07 20:44:51-838544 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-838732 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-838921 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-839109 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-839297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-839485 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-839675 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-839870 util-scheduler-8620 DEBUG Running task: 552 / 0x4d5e5d8
Jul 07 20:44:51-840058 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:51-840238 util-8620 DEBUG process_notify is running
Jul 07 20:44:51-840412 util-8620 DEBUG client_notify is running
Jul 07 20:44:51-840640 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:51-840946 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:51-841160 util-scheduler-8620 DEBUG Running task: 553 / 0x4d5c9e8
Jul 07 20:44:51-841395 util-scheduler-8620 DEBUG Adding task: 555 / 0x4d5c9e8
Jul 07 20:44:51-841620 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:51-841823 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:51-842027 util-scheduler-8620 DEBUG Adding task: 556 / 0x46620a0
Jul 07 20:44:51-842273 util-scheduler-8620 DEBUG Checking readiness of task: 556 / 0x46620a0
Jul 07 20:44:51-842468 util-scheduler-8620 DEBUG Checking readiness of task: 554 / 0x46620a0
Jul 07 20:44:51-842659 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:51-842850 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:51-843040 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:51-843231 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:51-843420 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:51-843610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:51-843820 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:51-844014 util-scheduler-8620 DEBUG Running task: 556 / 0x46620a0
Jul 07 20:44:51-844203 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:51-844379 util-8620 DEBUG process_notify is running
Jul 07 20:44:51-844549 util-8620 DEBUG client_notify is running
Jul 07 20:44:51-844729 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:51-844926 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:51-845153 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:51-845483 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:52-043268 util-scheduler-8620 DEBUG Checking readiness of task: 554 / 0x46620a0
Jul 07 20:44:52-043621 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:52-043819 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-044012 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-044208 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-044400 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-044592 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-044787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-044987 util-scheduler-8620 DEBUG Running task: 554 / 0x46620a0
Jul 07 20:44:52-045473 util-8620 DEBUG receive_ready read 16192/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:52-046354 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:52-046594 util-scheduler-8620 DEBUG Adding task: 557 / 0x46620a0
Jul 07 20:44:52-047309 util-scheduler-8620 DEBUG Checking readiness of task: 557 / 0x46620a0
Jul 07 20:44:52-047537 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:52-047733 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-047926 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-048143 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-048335 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-048525 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-048716 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-048909 util-scheduler-8620 DEBUG Running task: 557 / 0x46620a0
Jul 07 20:44:52-049344 util-8620 DEBUG receive_ready read 17220/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:52-050066 util-scheduler-8620 DEBUG Adding task: 558 / 0x4662248
Jul 07 20:44:52-050322 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:52-050515 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-050707 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-050897 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-051088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-051278 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-051469 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-051659 util-scheduler-8620 DEBUG Running task: 558 / 0x4662248
Jul 07 20:44:52-051871 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:44:52-052271 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:44:52-052503 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `KNAS'
Jul 07 20:44:52-052766 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:52-053035 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:52-053547 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:52-053759 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:52-054008 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:52-054221 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:52-054411 cadet-con-8620 DEBUG  PID 5 (expected 5+)
Jul 07 20:44:52-054596 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:52-054786 util-scheduler-8620 DEBUG Canceling task: 551 / 0x4d61c30
Jul 07 20:44:52-055010 util-scheduler-8620 DEBUG Adding task: 559 / 0x4d61c30
Jul 07 20:44:52-055191 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:52-055450 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:52-055664 util-scheduler-8620 DEBUG Adding task: 560 / 0x4d5e5d8
Jul 07 20:44:52-055867 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:52-056075 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:52-059661 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:52-077984 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:52-078254 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:52-126214 cadet-tun-8620 INFO <=== {              DATA} on KNAS
Jul 07 20:44:52-128125 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:44:52-131833 cadet-chn-8620 INFO <=== DATA 0 BCK on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-133852 cadet-chn-8620 DEBUG RECV 0 (33296)
Jul 07 20:44:52-134994 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:44:52-137583 util-server-nc-8620 DEBUG Adding message of type 285 and size 33292 to pending queue (which has 1 entries)
Jul 07 20:44:52-138002 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:44:52-138229 util-scheduler-8620 DEBUG Adding task: 561 / 0x4d5c418
Jul 07 20:44:52-140130 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:44:52-142373 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:44:52-143375 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-143602 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:52-143805 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:52-143988 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:52-144171 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:52-144357 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:52-144534 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:52-144705 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:52-144921 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-145105 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:52-145364 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:52-145551 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:52-145855 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:52-146027 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:52-146212 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:52-150043 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:52-150863 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:52-151047 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:52-151243 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:52-154586 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:52-154856 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:52-155038 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:52-155260 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:52-155914 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:44:52-156205 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (100 bytes)
Jul 07 20:44:52-156406 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:52-156584 cadet-con-8620 DEBUG last pid sent 9
Jul 07 20:44:52-156758 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:44:52-156963 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:52-157142 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:52-157400 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:52-157608 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:52-157934 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:44:52-158136 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:52-158362 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:52-158544 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:52-158718 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:52-158922 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:52-159124 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:52-159299 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:52-159483 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:52-159723 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-159907 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:44:52-160082 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:52-160318 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-160510 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:44:52-160685 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:52-160883 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:52-161852 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:44:52-162521 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:52-162704 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:52-162881 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:52-163054 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:52-163274 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:52-163455 cadet-con-8620 DEBUG  ACK 69
Jul 07 20:44:52-163637 cadet-con-8620 DEBUG  last pid 5, last ack 68, qmax 11, q 0
Jul 07 20:44:52-163917 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:44:52-164092 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:44:52-164284 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:44:52-164471 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:52-164653 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:52-164842 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:44:52-165019 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:52-165232 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:52-165412 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:52-165656 cadet-p2p-8620 DEBUG Checking 0x5522e40 towards HS92G30M (->KNAS)
Jul 07 20:44:52-165890 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:52-166074 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:52-166251 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:52-166517 cadet-con-8620 INFO --> {               ACK} ( 69) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:52-166707 cadet-con-8620 DEBUG  ack 69
Jul 07 20:44:52-166885 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:52-167117 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:52-167322 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:52-167615 cadet-p2p-8620 INFO que {               ACK} ( 69) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:52-167812 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:52-168034 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:52-168215 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:52-168388 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:52-168599 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:52-168800 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:52-168974 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:52-169168 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:52-169427 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-169608 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:44:52-169783 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:52-170016 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-170208 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:44:52-170384 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:52-170580 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:52-170765 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:52-170982 util-scheduler-8620 DEBUG Adding task: 562 / 0x46620a0
Jul 07 20:44:52-171268 util-scheduler-8620 DEBUG Checking readiness of task: 562 / 0x46620a0
Jul 07 20:44:52-171464 util-scheduler-8620 DEBUG Checking readiness of task: 561 / 0x4d5c418
Jul 07 20:44:52-171657 util-scheduler-8620 DEBUG Checking readiness of task: 560 / 0x4d5e5d8
Jul 07 20:44:52-171846 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:52-172035 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-172223 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-172412 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-172600 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-172789 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-172977 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-173170 util-scheduler-8620 DEBUG Running task: 560 / 0x4d5e5d8
Jul 07 20:44:52-173378 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:52-173557 util-8620 DEBUG process_notify is running
Jul 07 20:44:52-173728 util-8620 DEBUG client_notify is running
Jul 07 20:44:52-173977 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:52-174186 util-scheduler-8620 DEBUG Adding task: 563 / 0x4d5e5d8
Jul 07 20:44:52-174393 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:52-174701 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:52-174902 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:44:52-175102 util-scheduler-8620 DEBUG Running task: 561 / 0x4d5c418
Jul 07 20:44:52-175286 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:44:52-175489 util-8620 DEBUG process_notify is running
Jul 07 20:44:52-175683 util-server-nc-8620 DEBUG Copying message of type 285 and size 33292 from pending queue to transmission buffer
Jul 07 20:44:52-176797 util-8620 DEBUG Connection transmitted 33292/33292 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:44:52-177077 util-scheduler-8620 DEBUG Checking readiness of task: 563 / 0x4d5e5d8
Jul 07 20:44:52-177299 util-scheduler-8620 DEBUG Checking readiness of task: 562 / 0x46620a0
Jul 07 20:44:52-177492 util-scheduler-8620 DEBUG Checking readiness of task: 362 / 0x4d5c418
Jul 07 20:44:52-177685 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-177876 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-178078 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-178268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-178463 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-178655 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-178850 util-scheduler-8620 DEBUG Running task: 362 / 0x4d5c418
Jul 07 20:44:52-179327 util-8620 DEBUG receive_ready read 80/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:44:52-179546 util-8620 DEBUG Server receives 80 bytes from `<unbound UNIX client>'.
Jul 07 20:44:52-179762 util-8620 DEBUG Server-mst receives 80 bytes with 0 bytes already in private buffer
Jul 07 20:44:52-179949 util-8620 DEBUG Server-mst has 80 bytes left in inbound buffer
Jul 07 20:44:52-180132 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:44:52-180321 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:44:52-180549 util-scheduler-8620 DEBUG Adding task: 564 / 0x4d5c578
Jul 07 20:44:52-181740 cadet-loc-8620 DEBUG 
Jul 07 20:44:52-182671 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:44:52-183877 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:52-185026 cadet-loc-8620 DEBUG   on channel 80000001
Jul 07 20:44:52-186323 cadet-loc-8620 DEBUG    -- ch 0x4d638d8
Jul 07 20:44:52-187850 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:44:52-189086 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:44:52-191044 cadet-tun-8620 DEBUG Tunnel send connection ACKs on KNAS
Jul 07 20:44:52-192544 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:44:52-195252 cadet-tun-8620 DEBUG   allowed 64
Jul 07 20:44:52-197107 util-scheduler-8620 DEBUG Canceling task: 564 / 0x4d5c578
Jul 07 20:44:52-197334 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:52-197518 util-8620 DEBUG Server-mst has 72 bytes left in inbound buffer
Jul 07 20:44:52-197990 util-8620 DEBUG Server-mst leaves 72 bytes in private buffer
Jul 07 20:44:52-198178 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:44:52-198364 util-8620 DEBUG Server-mst receives 0 bytes with 72 bytes already in private buffer
Jul 07 20:44:52-198552 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:44:52-198739 util-8620 DEBUG Server schedules transmission of 72-byte message of type 285 to client.
Jul 07 20:44:52-198954 util-scheduler-8620 DEBUG Adding task: 565 / 0x4d5c578
Jul 07 20:44:52-199292 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:44:52-199626 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:44:52-199961 cadet-loc-8620 DEBUG   on channel 80000001
Jul 07 20:44:52-200239 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:44:52-200497 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-200699 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:44:52-200994 cadet-chn-8620 DEBUG !!! SAVE 1 {              DATA}
Jul 07 20:44:52-201306 cadet-chn-8620 DEBUG   at 0x552db98
Jul 07 20:44:52-201497 cadet-chn-8620 DEBUG   new chq: 0x552db18
Jul 07 20:44:52-201704 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:52-201904 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:52-202085 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:52-202267 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:52-202448 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:52-202625 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:52-202794 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:52-203022 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-203198 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:52-203448 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:52-203634 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:52-203933 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:52-204107 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:52-204294 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:52-207875 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:52-208691 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:52-208870 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:52-209059 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:52-212241 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:52-212484 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:52-212666 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:52-212912 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:52-213107 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:52-213414 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:44:52-213614 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:52-213791 cadet-con-8620 DEBUG last pid sent 9
Jul 07 20:44:52-213964 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:44:52-214141 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:44:52-214377 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:52-214585 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:52-214897 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:44:52-215097 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:52-215321 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:52-215503 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:52-215678 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:52-215880 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:52-216081 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:52-216255 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:52-216429 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:52-216667 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-216852 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:44:52-217031 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:52-217289 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-217486 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:44:52-217663 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:52-217898 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:52-218092 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:52-218269 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:52-218473 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:52-218683 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:52-218865 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:52-219049 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:52-219231 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:52-219409 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:52-219581 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:52-219800 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-219972 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:52-220216 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:52-220405 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:52-220577 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:52-220896 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:44:52-221109 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:52-221311 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:52-221494 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:52-221677 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:52-221852 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:52-222020 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:52-222233 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-222404 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:52-222631 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:52-222814 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:52-222987 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:44:52-223214 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:52-223402 cadet-loc-8620 DEBUG send local FWD ack on 80000001 towards 0x4d5c6d8
Jul 07 20:44:52-223633 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:44:52-223838 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:44:52-224049 util-scheduler-8620 DEBUG Adding task: 566 / 0x4d5c418
Jul 07 20:44:52-224333 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:44:52-224523 util-scheduler-8620 DEBUG Canceling task: 565 / 0x4d5c578
Jul 07 20:44:52-224718 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:44:52-224899 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:44:52-225105 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:44:52-225334 util-scheduler-8620 DEBUG Adding task: 567 / 0x4d5c418
Jul 07 20:44:52-225535 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:44:52-225767 util-scheduler-8620 DEBUG Running task: 563 / 0x4d5e5d8
Jul 07 20:44:52-225957 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:52-226135 util-8620 DEBUG process_notify is running
Jul 07 20:44:52-226305 util-8620 DEBUG client_notify is running
Jul 07 20:44:52-226534 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:44:52-226867 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:52-227147 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:52-227340 util-scheduler-8620 DEBUG Checking readiness of task: 566 / 0x4d5c418
Jul 07 20:44:52-227532 util-scheduler-8620 DEBUG Checking readiness of task: 562 / 0x46620a0
Jul 07 20:44:52-227721 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-227910 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-228099 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-228287 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-228475 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-228663 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-228866 util-scheduler-8620 DEBUG Running task: 566 / 0x4d5c418
Jul 07 20:44:52-229049 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:44:52-229243 util-8620 DEBUG process_notify is running
Jul 07 20:44:52-229435 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:44:52-229717 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:44:52-918501 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:52-918886 util-scheduler-8620 DEBUG Checking readiness of task: 562 / 0x46620a0
Jul 07 20:44:52-919086 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-919280 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-919472 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-919687 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-919879 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-920070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-920267 util-scheduler-8620 DEBUG Running task: 562 / 0x46620a0
Jul 07 20:44:52-920694 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:52-920955 util-scheduler-8620 DEBUG Adding task: 568 / 0x4662248
Jul 07 20:44:52-921261 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:52-921456 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:52-921646 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:52-921865 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:52-922055 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:52-922245 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:52-922435 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:52-922624 util-scheduler-8620 DEBUG Running task: 568 / 0x4662248
Jul 07 20:44:52-922818 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:52-923020 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:52-923251 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:44:52-923518 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection CMHCKRVP from V8XX
Jul 07 20:44:52-923734 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:44:52-923975 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:52-924184 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:52-924365 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:52-924537 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:52-924726 util-scheduler-8620 DEBUG Canceling task: 431 / 0x4d707d0
Jul 07 20:44:52-924949 util-scheduler-8620 DEBUG Adding task: 569 / 0x4d707d0
Jul 07 20:44:52-925227 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:52-925409 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:52-925600 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:52-925835 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:44:52-926073 cadet-con-8620 INFO ===> {           BCK ACK} on connection CMHCKRVP (->V8XX)
Jul 07 20:44:52-926305 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:52-926511 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:52-926805 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 36)
Jul 07 20:44:52-927003 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:52-927229 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:52-927411 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:52-927586 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:52-927801 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:44:52-928003 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:52-928178 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:52-928353 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:52-928593 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:52-928788 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:52-928966 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:52-929224 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:52-929407 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:52-929581 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:52-929779 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:52-929962 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:52-930174 util-scheduler-8620 DEBUG Adding task: 570 / 0x46620a0
Jul 07 20:44:53-938894 util-scheduler-8620 DEBUG Checking readiness of task: 570 / 0x46620a0
Jul 07 20:44:53-939280 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:53-939477 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:53-939670 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:53-939861 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:53-940052 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:53-940242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:53-940432 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:53-940672 util-scheduler-8620 DEBUG Running task: 570 / 0x46620a0
Jul 07 20:44:53-941096 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:53-941386 util-scheduler-8620 DEBUG Adding task: 571 / 0x4662248
Jul 07 20:44:53-941665 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:53-941858 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:53-942048 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:53-942238 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:53-942428 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:53-942617 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:53-942807 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:53-942996 util-scheduler-8620 DEBUG Running task: 571 / 0x4662248
Jul 07 20:44:53-943188 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:53-943387 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:53-943618 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:53-943825 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:53-944033 util-scheduler-8620 DEBUG Adding task: 572 / 0x46620a0
Jul 07 20:44:53-944221 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:53-944426 util-scheduler-8620 DEBUG Adding task: 573 / 0x46620a0
Jul 07 20:44:53-944673 util-scheduler-8620 DEBUG Checking readiness of task: 573 / 0x46620a0
Jul 07 20:44:53-944864 util-scheduler-8620 DEBUG Checking readiness of task: 572 / 0x46620a0
Jul 07 20:44:53-945056 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:53-945268 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:53-945459 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:53-945647 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:53-945851 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:53-946040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:53-946229 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:53-946420 util-scheduler-8620 DEBUG Running task: 572 / 0x46620a0
Jul 07 20:44:53-946606 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:53-946784 util-8620 DEBUG process_notify is running
Jul 07 20:44:53-946955 util-8620 DEBUG client_notify is running
Jul 07 20:44:53-947145 util-scheduler-8620 DEBUG Canceling task: 555 / 0x4d5c9e8
Jul 07 20:44:53-947368 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:53-947591 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:53-947829 cadet-p2p-8620 DEBUG Checking 0x5523fd8 towards HS92G30M (->KNAS)
Jul 07 20:44:53-948076 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:53-948255 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:53-948445 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:53-948715 cadet-p2p-8620 INFO snd {               ACK} ( 69) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:53-948910 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:53-949091 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:53-949299 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:53-949474 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:53-949659 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:44:53-949833 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:53-950055 cadet-p2p-8620 DEBUG Checking 0x5522e40 towards HS92G30M (->KNAS)
Jul 07 20:44:53-950287 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:53-950470 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:53-950661 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:53-950890 cadet-p2p-8620 DEBUG Checking 0x5522e40 towards HS92G30M (->KNAS)
Jul 07 20:44:53-951119 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:53-951300 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:53-951473 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:53-951640 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:53-951847 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:44:53-952059 util-scheduler-8620 DEBUG Adding task: 574 / 0x4d5c9e8
Jul 07 20:44:53-952237 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:53-952414 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:53-952613 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:53-952788 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:44:53-952962 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:53-953221 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:53-953418 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:44:53-953596 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:44:53-953830 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:53-954023 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:53-954209 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:53-954407 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:53-954615 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:53-954799 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:53-955002 util-scheduler-8620 DEBUG Adding task: 575 / 0x4d5c9e8
Jul 07 20:44:53-955223 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:53-955417 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:53-955619 util-scheduler-8620 DEBUG Adding task: 576 / 0x46620a0
Jul 07 20:44:53-955821 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:53-956071 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:53-956268 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:53-956512 util-scheduler-8620 DEBUG Checking readiness of task: 576 / 0x46620a0
Jul 07 20:44:53-956705 util-scheduler-8620 DEBUG Checking readiness of task: 573 / 0x46620a0
Jul 07 20:44:53-956896 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:53-957085 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:53-957300 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:53-957491 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:53-957680 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:53-957869 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:53-958057 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:53-958246 util-scheduler-8620 DEBUG Running task: 576 / 0x46620a0
Jul 07 20:44:53-958449 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:53-958627 util-8620 DEBUG process_notify is running
Jul 07 20:44:53-958797 util-8620 DEBUG client_notify is running
Jul 07 20:44:53-958974 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:53-959167 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:53-959356 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:53-959586 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:53-959791 util-scheduler-8620 DEBUG Running task: 574 / 0x4d5c9e8
Jul 07 20:44:53-959982 util-scheduler-8620 DEBUG Canceling task: 575 / 0x4d5c9e8
Jul 07 20:44:53-960210 util-scheduler-8620 DEBUG Adding task: 577 / 0x4d5c9e8
Jul 07 20:44:53-960427 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:53-960620 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:53-960819 util-scheduler-8620 DEBUG Adding task: 578 / 0x46620a0
Jul 07 20:44:53-961058 util-scheduler-8620 DEBUG Checking readiness of task: 578 / 0x46620a0
Jul 07 20:44:53-961269 util-scheduler-8620 DEBUG Checking readiness of task: 573 / 0x46620a0
Jul 07 20:44:53-961459 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:53-961648 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:53-961837 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:53-962026 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:53-962215 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:53-962403 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:53-962591 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:53-962782 util-scheduler-8620 DEBUG Running task: 578 / 0x46620a0
Jul 07 20:44:53-962975 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:53-963149 util-8620 DEBUG process_notify is running
Jul 07 20:44:53-963317 util-8620 DEBUG client_notify is running
Jul 07 20:44:53-963492 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:53-963679 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:53-963866 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:53-964107 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-058094 util-scheduler-8620 DEBUG Checking readiness of task: 573 / 0x46620a0
Jul 07 20:44:54-058486 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-058685 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-058881 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-059074 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-059269 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-059463 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-059655 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-059853 util-scheduler-8620 DEBUG Running task: 573 / 0x46620a0
Jul 07 20:44:54-060282 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:54-060542 util-scheduler-8620 DEBUG Adding task: 579 / 0x4662248
Jul 07 20:44:54-060824 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-061018 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-061242 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-061438 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-061631 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-061823 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-062016 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-062209 util-scheduler-8620 DEBUG Running task: 579 / 0x4662248
Jul 07 20:44:54-062404 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:54-062607 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:54-062843 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:54-063066 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-063278 util-scheduler-8620 DEBUG Adding task: 580 / 0x46620a0
Jul 07 20:44:54-063497 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:54-063708 util-scheduler-8620 DEBUG Adding task: 581 / 0x46620a0
Jul 07 20:44:54-063957 util-scheduler-8620 DEBUG Checking readiness of task: 581 / 0x46620a0
Jul 07 20:44:54-064151 util-scheduler-8620 DEBUG Checking readiness of task: 580 / 0x46620a0
Jul 07 20:44:54-064347 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-064540 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-064732 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-064924 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-065115 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-065337 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-065532 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-065727 util-scheduler-8620 DEBUG Running task: 580 / 0x46620a0
Jul 07 20:44:54-065915 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-066097 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-066272 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-066465 util-scheduler-8620 DEBUG Canceling task: 547 / 0x4d6ff98
Jul 07 20:44:54-066694 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:54-066918 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:54-067160 cadet-p2p-8620 DEBUG Checking 0x54f07f0 towards CMHCKRVP (->V8XX)
Jul 07 20:44:54-067415 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:54-067595 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:54-067789 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:54-068074 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:54-068273 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:54-068457 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:54-068648 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:54-068841 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:44:54-069022 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:54-069244 util-scheduler-8620 DEBUG Canceling task: 500 / 0x4d707d0
Jul 07 20:44:54-069463 util-scheduler-8620 DEBUG Adding task: 582 / 0x4d707d0
Jul 07 20:44:54-069718 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:54-069893 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:54-070118 cadet-p2p-8620 DEBUG Checking 0x5539008 towards CMHCKRVP (->V8XX)
Jul 07 20:44:54-070359 cadet-p2p-8620 DEBUG Checking 0x5539008 towards CMHCKRVP (->V8XX)
Jul 07 20:44:54-070540 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:54-070749 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:44:54-070965 util-scheduler-8620 DEBUG Adding task: 583 / 0x4d6ff98
Jul 07 20:44:54-071147 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:54-071327 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:54-071530 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:54-071708 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:54-071886 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:54-072128 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:54-072314 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:54-072492 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:54-072693 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:54-072901 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:54-073087 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:54-073317 util-scheduler-8620 DEBUG Adding task: 584 / 0x4d6ff98
Jul 07 20:44:54-073540 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:54-073736 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-073957 util-scheduler-8620 DEBUG Adding task: 585 / 0x46620a0
Jul 07 20:44:54-074162 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:54-074407 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-074607 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:54-074854 util-scheduler-8620 DEBUG Checking readiness of task: 585 / 0x46620a0
Jul 07 20:44:54-075050 util-scheduler-8620 DEBUG Checking readiness of task: 581 / 0x46620a0
Jul 07 20:44:54-075258 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-075454 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-075646 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-075838 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-076030 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-076221 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-076413 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-076606 util-scheduler-8620 DEBUG Running task: 585 / 0x46620a0
Jul 07 20:44:54-076794 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-076972 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-077147 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-077352 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:54-077550 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:54-077741 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:54-078053 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-078264 util-scheduler-8620 DEBUG Running task: 583 / 0x4d6ff98
Jul 07 20:44:54-078459 util-scheduler-8620 DEBUG Canceling task: 584 / 0x4d6ff98
Jul 07 20:44:54-078675 util-scheduler-8620 DEBUG Adding task: 586 / 0x4d6ff98
Jul 07 20:44:54-078895 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:54-079091 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-079292 util-scheduler-8620 DEBUG Adding task: 587 / 0x46620a0
Jul 07 20:44:54-079535 util-scheduler-8620 DEBUG Checking readiness of task: 587 / 0x46620a0
Jul 07 20:44:54-079731 util-scheduler-8620 DEBUG Checking readiness of task: 581 / 0x46620a0
Jul 07 20:44:54-079923 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-080116 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-080308 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-080500 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-080691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-080883 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-081075 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-081295 util-scheduler-8620 DEBUG Running task: 587 / 0x46620a0
Jul 07 20:44:54-081483 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-081661 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-081833 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-082012 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:54-082204 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:54-082394 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:54-082741 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-189142 util-scheduler-8620 DEBUG Checking readiness of task: 581 / 0x46620a0
Jul 07 20:44:54-189508 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-189704 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-189896 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-190087 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-190278 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-190468 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-190659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-190868 util-scheduler-8620 DEBUG Running task: 581 / 0x46620a0
Jul 07 20:44:54-191289 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:54-191537 util-scheduler-8620 DEBUG Adding task: 588 / 0x4662248
Jul 07 20:44:54-191806 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-191998 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-192188 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-192378 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-192567 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-192773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-192963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-193153 util-scheduler-8620 DEBUG Running task: 588 / 0x4662248
Jul 07 20:44:54-193366 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:54-193565 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:54-193790 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:54-193994 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-194198 util-scheduler-8620 DEBUG Adding task: 589 / 0x46620a0
Jul 07 20:44:54-194384 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:54-194588 util-scheduler-8620 DEBUG Adding task: 590 / 0x46620a0
Jul 07 20:44:54-194832 util-scheduler-8620 DEBUG Checking readiness of task: 590 / 0x46620a0
Jul 07 20:44:54-195024 util-scheduler-8620 DEBUG Checking readiness of task: 589 / 0x46620a0
Jul 07 20:44:54-195216 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-195405 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-195596 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-195785 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-195974 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-196164 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-196352 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-196544 util-scheduler-8620 DEBUG Running task: 589 / 0x46620a0
Jul 07 20:44:54-196729 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-196906 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-197078 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-197286 util-scheduler-8620 DEBUG Canceling task: 586 / 0x4d6ff98
Jul 07 20:44:54-197508 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:44:54-197727 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:54-197965 cadet-p2p-8620 DEBUG Checking 0x5539008 towards CMHCKRVP (->V8XX)
Jul 07 20:44:54-198197 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:54-198375 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:54-198545 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:54-198716 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:54-198887 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:54-199162 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 36)
Jul 07 20:44:54-199356 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:54-199535 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:54-199722 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:54-199903 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:54-200076 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:54-200256 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:54-200455 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:54-200629 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:54-200802 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:54-201000 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:54-201253 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:44:54-201437 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:54-201626 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:54-201868 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:54-202117 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-266863 util-scheduler-8620 DEBUG Checking readiness of task: 590 / 0x46620a0
Jul 07 20:44:54-267100 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-267305 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-267497 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-267688 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-267878 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-268068 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-268258 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-268450 util-scheduler-8620 DEBUG Running task: 590 / 0x46620a0
Jul 07 20:44:54-268853 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:54-269089 util-scheduler-8620 DEBUG Adding task: 591 / 0x4662248
Jul 07 20:44:54-269373 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-269566 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-269756 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-269945 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-270135 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-270325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-270514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-270704 util-scheduler-8620 DEBUG Running task: 591 / 0x4662248
Jul 07 20:44:54-270894 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:54-271088 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:54-271304 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:54-271504 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-271707 util-scheduler-8620 DEBUG Adding task: 592 / 0x46620a0
Jul 07 20:44:54-271892 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:54-272094 util-scheduler-8620 DEBUG Adding task: 593 / 0x46620a0
Jul 07 20:44:54-272333 util-scheduler-8620 DEBUG Checking readiness of task: 593 / 0x46620a0
Jul 07 20:44:54-272525 util-scheduler-8620 DEBUG Checking readiness of task: 592 / 0x46620a0
Jul 07 20:44:54-272715 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-272904 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-273094 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-273326 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-273517 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-273706 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-273895 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-274086 util-scheduler-8620 DEBUG Running task: 592 / 0x46620a0
Jul 07 20:44:54-274269 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-274446 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-274617 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-274802 util-scheduler-8620 DEBUG Canceling task: 577 / 0x4d5c9e8
Jul 07 20:44:54-275022 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:44:54-275238 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:54-275493 cadet-p2p-8620 DEBUG Checking 0x5522e40 towards HS92G30M (->KNAS)
Jul 07 20:44:54-275726 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:54-275908 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 9
Jul 07 20:44:54-276082 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:54-276314 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:54-276490 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:44:54-276666 cadet-p2p-8620 DEBUG   payload ID 10
Jul 07 20:44:54-276947 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:44:54-277153 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:54-277349 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:54-277536 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:54-277709 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:54-277877 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:54-278066 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:44:54-278262 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:44:54-278457 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:54-278685 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:54-278860 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:54-279032 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:44:54-279205 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:54-279401 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:54-279576 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:54-279750 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:54-279951 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:54-280130 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:54-280312 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:54-280492 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:54-280669 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:54-280838 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:54-281055 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:54-281252 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:54-281488 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:54-281672 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:54-281852 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:54-282039 util-scheduler-8620 DEBUG Canceling task: 544 / 0x4d61c30
Jul 07 20:44:54-282250 util-scheduler-8620 DEBUG Adding task: 594 / 0x4d61c30
Jul 07 20:44:54-282500 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:54-282679 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:44:54-282858 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 10
Jul 07 20:44:54-283031 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:54-283252 cadet-p2p-8620 DEBUG Checking 0x55366e0 towards HS92G30M (->KNAS)
Jul 07 20:44:54-283481 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:54-283678 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 10
Jul 07 20:44:54-283853 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:54-284080 cadet-p2p-8620 DEBUG Checking 0x55366e0 towards HS92G30M (->KNAS)
Jul 07 20:44:54-284310 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:54-284491 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 10
Jul 07 20:44:54-284666 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:54-284832 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:54-285046 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:44:54-285278 util-scheduler-8620 DEBUG Adding task: 595 / 0x4d5c9e8
Jul 07 20:44:54-285458 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:54-285633 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:44:54-285832 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:54-286007 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:54-286182 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:54-286420 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:54-286615 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:54-286792 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:54-286990 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:54-287193 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:44:54-287376 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:44:54-287577 util-scheduler-8620 DEBUG Adding task: 596 / 0x4d5c9e8
Jul 07 20:44:54-287797 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:54-287991 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-288192 util-scheduler-8620 DEBUG Adding task: 597 / 0x46620a0
Jul 07 20:44:54-288391 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:44:54-288642 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-288839 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:54-289083 util-scheduler-8620 DEBUG Checking readiness of task: 597 / 0x46620a0
Jul 07 20:44:54-289301 util-scheduler-8620 DEBUG Checking readiness of task: 593 / 0x46620a0
Jul 07 20:44:54-289493 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-289684 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-289874 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-290064 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-290254 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-290443 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-290632 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-290822 util-scheduler-8620 DEBUG Running task: 597 / 0x46620a0
Jul 07 20:44:54-291007 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-291183 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-291354 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-291532 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:54-291725 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:54-291912 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:54-292142 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:54-292347 util-scheduler-8620 DEBUG Running task: 595 / 0x4d5c9e8
Jul 07 20:44:54-292538 util-scheduler-8620 DEBUG Canceling task: 596 / 0x4d5c9e8
Jul 07 20:44:54-292748 util-scheduler-8620 DEBUG Adding task: 598 / 0x4d5c9e8
Jul 07 20:44:54-292963 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:54-293185 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:54-293409 util-scheduler-8620 DEBUG Adding task: 599 / 0x46620a0
Jul 07 20:44:54-293650 util-scheduler-8620 DEBUG Checking readiness of task: 599 / 0x46620a0
Jul 07 20:44:54-293843 util-scheduler-8620 DEBUG Checking readiness of task: 593 / 0x46620a0
Jul 07 20:44:54-294032 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:54-294221 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:54-294411 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:54-294600 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:54-294792 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:54-294981 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:54-295170 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:54-295360 util-scheduler-8620 DEBUG Running task: 599 / 0x46620a0
Jul 07 20:44:54-295544 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:54-295718 util-8620 DEBUG process_notify is running
Jul 07 20:44:54-295887 util-8620 DEBUG client_notify is running
Jul 07 20:44:54-296063 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:54-296251 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:54-296441 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:54-296683 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:56-628365 util-scheduler-8620 DEBUG Checking readiness of task: 593 / 0x46620a0
Jul 07 20:44:56-628757 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:56-628955 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:56-629149 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:56-629366 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:56-629558 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:56-629763 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:56-629954 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:56-630150 util-scheduler-8620 DEBUG Running task: 593 / 0x46620a0
Jul 07 20:44:56-630575 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:56-630834 util-scheduler-8620 DEBUG Adding task: 600 / 0x4662248
Jul 07 20:44:56-631053 util-scheduler-8620 DEBUG Running task: 546 / 0x4d64a70
Jul 07 20:44:56-631280 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:44:56-631526 cadet-tun-8620 DEBUG  kx started 30 s ago
Jul 07 20:44:56-631732 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:44:56-631933 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:44:56-632136 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:44:56-632372 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:44:56-632554 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:56-632775 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:44:56-633062 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:44:56-633288 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:44:56-633548 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:56-633756 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:56-634071 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:44:56-634272 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:56-634497 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:56-634717 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:56-634895 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:56-635104 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:44:56-635318 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:44:56-635533 util-scheduler-8620 DEBUG Adding task: 601 / 0x4d6ff98
Jul 07 20:44:56-635713 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:56-635917 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:56-636094 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:56-636269 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:56-636510 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:56-636705 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:44:56-636883 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:44:56-637083 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:56-637354 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:44:56-637552 util-scheduler-8620 DEBUG Adding task: 602 / 0x4d64a70
Jul 07 20:44:56-637810 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:56-638002 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:56-638191 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:56-638380 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:56-638569 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:56-638758 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:56-638947 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:56-639137 util-scheduler-8620 DEBUG Running task: 601 / 0x4d6ff98
Jul 07 20:44:56-639345 util-scheduler-8620 DEBUG Adding task: 603 / 0x4d6ff98
Jul 07 20:44:56-639567 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:56-639772 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:56-639979 util-scheduler-8620 DEBUG Adding task: 604 / 0x46620a0
Jul 07 20:44:56-640178 util-scheduler-8620 DEBUG Running task: 600 / 0x4662248
Jul 07 20:44:56-640369 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:56-640568 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:56-640796 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:56-641049 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:56-641324 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:56-641531 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:56-641713 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:56-641886 cadet-con-8620 DEBUG   ACK 67 (was 66)
Jul 07 20:44:56-642115 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:56-642345 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:56-642550 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:56-642730 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:44:56-642933 util-scheduler-8620 DEBUG Adding task: 605 / 0x4662248
Jul 07 20:44:56-643175 util-scheduler-8620 DEBUG Checking readiness of task: 604 / 0x46620a0
Jul 07 20:44:56-643368 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:56-643559 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:56-643748 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:56-643938 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:56-644127 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:56-644315 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:56-644504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:56-644695 util-scheduler-8620 DEBUG Running task: 604 / 0x46620a0
Jul 07 20:44:56-644921 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:56-645100 util-8620 DEBUG process_notify is running
Jul 07 20:44:56-645296 util-8620 DEBUG client_notify is running
Jul 07 20:44:56-645477 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:56-645673 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:56-645863 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:56-646191 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:56-646401 util-scheduler-8620 DEBUG Running task: 605 / 0x4662248
Jul 07 20:44:56-646589 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:44:56-646782 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:44:56-646999 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:44:56-647242 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:56-647479 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:56-647706 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:56-647915 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:56-648156 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:56-648361 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:56-648548 cadet-con-8620 DEBUG  PID 6 (expected 6+)
Jul 07 20:44:56-648728 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:56-648915 util-scheduler-8620 DEBUG Canceling task: 559 / 0x4d61c30
Jul 07 20:44:56-649148 util-scheduler-8620 DEBUG Adding task: 606 / 0x4d61c30
Jul 07 20:44:56-649353 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:56-649608 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:56-649821 util-scheduler-8620 DEBUG Adding task: 607 / 0x4d5e5d8
Jul 07 20:44:56-650006 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:56-650175 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:56-653777 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:56-655072 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:56-655269 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:56-658513 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:44:56-658971 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:44:56-660023 cadet-chn-8620 DEBUG   head 1, out!
Jul 07 20:44:56-661339 cadet-chn-8620 DEBUG free_sent_reliable 0 0
Jul 07 20:44:56-662409 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x552db98
Jul 07 20:44:56-663498 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:44:56-664083 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:56-664269 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:44:56-664485 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:56-664669 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:56-664854 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:56-665038 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:56-665238 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:56-665411 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:56-665633 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:56-665807 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:56-666045 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:56-666231 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:56-666410 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:44:56-666649 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:56-666923 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:44:56-667479 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:56-667662 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:56-667840 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:56-668035 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:56-668260 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:56-668439 cadet-con-8620 DEBUG  ACK 70
Jul 07 20:44:56-668620 cadet-con-8620 DEBUG  last pid 6, last ack 69, qmax 11, q 0
Jul 07 20:44:56-668888 cadet-con-8620 INFO --> {               ACK} ( 70) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:56-669079 cadet-con-8620 DEBUG  ack 70
Jul 07 20:44:56-669281 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:44:56-669518 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:56-669726 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:56-670024 cadet-p2p-8620 INFO que {               ACK} ( 70) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:56-670222 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:56-670447 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:56-670629 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 10
Jul 07 20:44:56-670803 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:56-671005 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:44:56-671207 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:56-671394 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:56-671569 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:56-671806 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:56-671990 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:44:56-672165 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:56-672400 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:56-672593 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:56-672769 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:56-672968 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:56-673155 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:56-673392 util-scheduler-8620 DEBUG Adding task: 608 / 0x46620a0
Jul 07 20:44:56-673664 util-scheduler-8620 DEBUG Checking readiness of task: 608 / 0x46620a0
Jul 07 20:44:56-673860 util-scheduler-8620 DEBUG Checking readiness of task: 607 / 0x4d5e5d8
Jul 07 20:44:56-674052 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:56-674241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:56-674430 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:56-674619 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:56-674809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:56-674997 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:56-675185 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:56-675378 util-scheduler-8620 DEBUG Running task: 607 / 0x4d5e5d8
Jul 07 20:44:56-675563 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:56-675740 util-8620 DEBUG process_notify is running
Jul 07 20:44:56-675911 util-8620 DEBUG client_notify is running
Jul 07 20:44:56-676138 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:56-676499 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:57-042877 util-scheduler-8620 DEBUG Checking readiness of task: 608 / 0x46620a0
Jul 07 20:44:57-043248 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-043449 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-043644 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-043837 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-044030 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-044224 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-044445 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-044645 util-scheduler-8620 DEBUG Running task: 608 / 0x46620a0
Jul 07 20:44:57-045067 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-045355 util-scheduler-8620 DEBUG Adding task: 609 / 0x4662248
Jul 07 20:44:57-045635 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-045829 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-046022 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-046213 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-046405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-046596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-046788 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-046979 util-scheduler-8620 DEBUG Running task: 609 / 0x4662248
Jul 07 20:44:57-047173 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:57-047374 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:57-047607 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:57-047815 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-048026 util-scheduler-8620 DEBUG Adding task: 610 / 0x46620a0
Jul 07 20:44:57-048214 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-048496 util-scheduler-8620 DEBUG Adding task: 611 / 0x46620a0
Jul 07 20:44:57-048754 util-scheduler-8620 DEBUG Checking readiness of task: 611 / 0x46620a0
Jul 07 20:44:57-048948 util-scheduler-8620 DEBUG Checking readiness of task: 610 / 0x46620a0
Jul 07 20:44:57-049141 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-049934 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-050135 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-050328 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-050520 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-050712 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-050904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-051099 util-scheduler-8620 DEBUG Running task: 610 / 0x46620a0
Jul 07 20:44:57-051287 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-051468 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-051642 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-051918 util-scheduler-8620 DEBUG Canceling task: 598 / 0x4d5c9e8
Jul 07 20:44:57-052147 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:44:57-052371 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:57-052613 cadet-p2p-8620 DEBUG Checking 0x554ee98 towards HS92G30M (->KNAS)
Jul 07 20:44:57-052847 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:57-053027 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:57-053245 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:57-053522 cadet-p2p-8620 INFO snd {               ACK} ( 70) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:57-054172 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:57-054362 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:57-054555 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:57-054733 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:57-054920 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:44:57-055098 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:57-055323 cadet-p2p-8620 DEBUG Checking 0x55366e0 towards HS92G30M (->KNAS)
Jul 07 20:44:57-055559 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:57-055765 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 10
Jul 07 20:44:57-055944 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:57-056174 cadet-p2p-8620 DEBUG Checking 0x55366e0 towards HS92G30M (->KNAS)
Jul 07 20:44:57-056406 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:57-056589 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 10
Jul 07 20:44:57-056764 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:57-056932 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:44:57-057142 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:44:57-057386 util-scheduler-8620 DEBUG Adding task: 612 / 0x4d5c9e8
Jul 07 20:44:57-057569 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:57-057749 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:57-057951 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:57-058127 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:57-058317 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:57-058557 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:57-058753 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:57-058932 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:57-059133 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:57-059340 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:57-059525 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:57-059731 util-scheduler-8620 DEBUG Adding task: 613 / 0x4d5c9e8
Jul 07 20:44:57-059954 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:57-060151 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-060355 util-scheduler-8620 DEBUG Adding task: 614 / 0x46620a0
Jul 07 20:44:57-060558 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:57-061572 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-061778 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:44:57-062033 util-scheduler-8620 DEBUG Checking readiness of task: 614 / 0x46620a0
Jul 07 20:44:57-062230 util-scheduler-8620 DEBUG Checking readiness of task: 611 / 0x46620a0
Jul 07 20:44:57-062423 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-062615 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-062808 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-063000 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-063191 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-063385 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-063577 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-063770 util-scheduler-8620 DEBUG Running task: 614 / 0x46620a0
Jul 07 20:44:57-063957 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-064135 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-064308 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-064488 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:57-064685 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-064875 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:57-065175 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-065407 util-scheduler-8620 DEBUG Running task: 612 / 0x4d5c9e8
Jul 07 20:44:57-065602 util-scheduler-8620 DEBUG Canceling task: 613 / 0x4d5c9e8
Jul 07 20:44:57-065818 util-scheduler-8620 DEBUG Adding task: 615 / 0x4d5c9e8
Jul 07 20:44:57-066037 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:57-066251 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-066452 util-scheduler-8620 DEBUG Adding task: 616 / 0x46620a0
Jul 07 20:44:57-066693 util-scheduler-8620 DEBUG Checking readiness of task: 616 / 0x46620a0
Jul 07 20:44:57-066887 util-scheduler-8620 DEBUG Checking readiness of task: 611 / 0x46620a0
Jul 07 20:44:57-067080 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-067272 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-067464 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-067665 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-067939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-068136 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-068384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-068579 util-scheduler-8620 DEBUG Running task: 611 / 0x46620a0
Jul 07 20:44:57-068984 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-069240 util-scheduler-8620 DEBUG Adding task: 617 / 0x4662248
Jul 07 20:44:57-069454 util-scheduler-8620 DEBUG Running task: 616 / 0x46620a0
Jul 07 20:44:57-069641 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-069818 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-069988 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-070167 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:57-070358 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-070548 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:57-070857 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-071108 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-071303 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-071495 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-071687 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-071879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-072070 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-072277 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-072468 util-scheduler-8620 DEBUG Running task: 617 / 0x4662248
Jul 07 20:44:57-072660 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:57-072857 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:57-073073 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:57-073282 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-073488 util-scheduler-8620 DEBUG Adding task: 618 / 0x46620a0
Jul 07 20:44:57-073728 util-scheduler-8620 DEBUG Checking readiness of task: 618 / 0x46620a0
Jul 07 20:44:57-073922 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-074114 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-074306 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-074497 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-074688 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-074879 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-075070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-075262 util-scheduler-8620 DEBUG Running task: 618 / 0x46620a0
Jul 07 20:44:57-075662 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-075900 util-scheduler-8620 DEBUG Adding task: 619 / 0x4662248
Jul 07 20:44:57-076147 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-076341 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-076534 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-076725 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-076916 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-077108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-077321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-077513 util-scheduler-8620 DEBUG Running task: 619 / 0x4662248
Jul 07 20:44:57-077703 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:57-077896 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:57-078107 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:57-078305 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-078503 util-scheduler-8620 DEBUG Adding task: 620 / 0x46620a0
Jul 07 20:44:57-078688 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-078896 util-scheduler-8620 DEBUG Adding task: 621 / 0x46620a0
Jul 07 20:44:57-079137 util-scheduler-8620 DEBUG Checking readiness of task: 621 / 0x46620a0
Jul 07 20:44:57-079330 util-scheduler-8620 DEBUG Checking readiness of task: 620 / 0x46620a0
Jul 07 20:44:57-079522 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-079714 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-079905 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-080096 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-080287 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-080477 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-080669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-080862 util-scheduler-8620 DEBUG Running task: 620 / 0x46620a0
Jul 07 20:44:57-081049 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-081252 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-081424 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-081606 util-scheduler-8620 DEBUG Canceling task: 615 / 0x4d5c9e8
Jul 07 20:44:57-081826 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:44:57-082042 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:57-082274 cadet-p2p-8620 DEBUG Checking 0x55366e0 towards HS92G30M (->KNAS)
Jul 07 20:44:57-082506 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:57-082689 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 10
Jul 07 20:44:57-082864 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:57-083085 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:57-083264 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:44:57-083443 cadet-p2p-8620 DEBUG   payload ID 11
Jul 07 20:44:57-083723 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 156)
Jul 07 20:44:57-083917 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:57-084096 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:57-084284 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:44:57-084458 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:57-084628 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:44:57-084818 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:44:57-084997 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:44:57-085250 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 624 ms
Jul 07 20:44:57-085441 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:44:57-085650 cadet-chn-8620 DEBUG !! using delay 2499224 µs
Jul 07 20:44:57-085848 util-scheduler-8620 DEBUG Adding task: 622 / 0x4d63a48
Jul 07 20:44:57-086051 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:57-086281 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:44:57-086458 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:44:57-086632 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:44:57-086805 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:44:57-087004 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:44:57-087180 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:44:57-087357 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:44:57-087560 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:57-087740 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:57-087934 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:57-088116 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:57-088294 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:57-088465 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:57-088684 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:57-088858 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:57-089092 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:44:57-089302 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:57-089486 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:57-089673 util-scheduler-8620 DEBUG Canceling task: 594 / 0x4d61c30
Jul 07 20:44:57-089885 util-scheduler-8620 DEBUG Adding task: 623 / 0x4d61c30
Jul 07 20:44:57-090132 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:57-090311 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:44:57-090660 cadet-con-8620 DEBUG !   accounting pid 11
Jul 07 20:44:57-090840 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:57-091025 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:44:57-091229 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:57-091406 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:57-091584 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:57-091784 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:57-091990 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 156 bytes.
Jul 07 20:44:57-092175 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:44:57-092355 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-092546 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:44:57-095017 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-681054 util-scheduler-8620 DEBUG Checking readiness of task: 621 / 0x46620a0
Jul 07 20:44:57-681472 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-681671 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-681876 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-682081 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-682274 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-682474 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-682665 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-682860 util-scheduler-8620 DEBUG Running task: 621 / 0x46620a0
Jul 07 20:44:57-683283 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-683545 util-scheduler-8620 DEBUG Adding task: 624 / 0x4662248
Jul 07 20:44:57-683828 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-684022 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-684254 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-684446 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-684637 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-684827 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-685016 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-685232 util-scheduler-8620 DEBUG Running task: 624 / 0x4662248
Jul 07 20:44:57-685426 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:57-685627 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:57-685857 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:57-686065 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-686294 util-scheduler-8620 DEBUG Adding task: 625 / 0x46620a0
Jul 07 20:44:57-686483 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-686691 util-scheduler-8620 DEBUG Adding task: 626 / 0x46620a0
Jul 07 20:44:57-686948 util-scheduler-8620 DEBUG Checking readiness of task: 626 / 0x46620a0
Jul 07 20:44:57-687140 util-scheduler-8620 DEBUG Checking readiness of task: 625 / 0x46620a0
Jul 07 20:44:57-687332 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-687521 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-687711 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-687902 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-688091 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-688280 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-688470 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-688662 util-scheduler-8620 DEBUG Running task: 625 / 0x46620a0
Jul 07 20:44:57-688848 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-689026 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-689224 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-689425 util-scheduler-8620 DEBUG Canceling task: 603 / 0x4d6ff98
Jul 07 20:44:57-689650 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:44:57-689871 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:57-690110 cadet-p2p-8620 DEBUG Checking 0x5544390 towards CMHCKRVP (->V8XX)
Jul 07 20:44:57-690344 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:57-690521 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:44:57-690711 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:44:57-690995 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:44:57-691190 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:57-691370 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:57-691558 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:44:57-691756 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:57-691938 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:44:57-692122 util-scheduler-8620 DEBUG Canceling task: 582 / 0x4d707d0
Jul 07 20:44:57-692333 util-scheduler-8620 DEBUG Adding task: 627 / 0x4d707d0
Jul 07 20:44:57-692584 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:44:57-692755 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:57-692936 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:44:57-693137 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:57-693338 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:57-693516 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:57-693716 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:57-693920 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:44:57-694104 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:44:57-694306 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-694509 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:44:57-695296 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-783289 util-scheduler-8620 DEBUG Checking readiness of task: 626 / 0x46620a0
Jul 07 20:44:57-783656 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-783852 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-784045 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-784252 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-784444 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-784634 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-784825 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-785021 util-scheduler-8620 DEBUG Running task: 626 / 0x46620a0
Jul 07 20:44:57-785468 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-785725 util-scheduler-8620 DEBUG Adding task: 628 / 0x4662248
Jul 07 20:44:57-786002 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-786195 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-786385 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-786574 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-786763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-786953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-787143 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-787343 util-scheduler-8620 DEBUG Running task: 628 / 0x4662248
Jul 07 20:44:57-787535 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:44:57-787737 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:44:57-787965 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:44:57-788231 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection CMHCKRVP from V8XX
Jul 07 20:44:57-788447 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:44:57-788689 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:57-788900 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:57-789082 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:44:57-789282 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:57-789471 util-scheduler-8620 DEBUG Canceling task: 569 / 0x4d707d0
Jul 07 20:44:57-789697 util-scheduler-8620 DEBUG Adding task: 629 / 0x4d707d0
Jul 07 20:44:57-789947 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:44:57-790128 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:44:57-790320 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:44:57-790554 cadet-con-8620 DEBUG Connection CMHCKRVP (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:44:57-790792 cadet-con-8620 INFO ===> {           BCK ACK} on connection CMHCKRVP (->V8XX)
Jul 07 20:44:57-791025 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:44:57-791231 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:44:57-791527 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 36)
Jul 07 20:44:57-791726 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:57-791952 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:44:57-792151 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:44:57-792337 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:57-792585 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:44:57-792803 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:44:57-793017 util-scheduler-8620 DEBUG Adding task: 630 / 0x4d6ff98
Jul 07 20:44:57-793221 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:57-793429 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:57-793609 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:57-793785 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:44:57-794025 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:44:57-794210 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:44:57-794388 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:44:57-794588 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:57-794771 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-794983 util-scheduler-8620 DEBUG Adding task: 631 / 0x46620a0
Jul 07 20:44:57-795229 util-scheduler-8620 DEBUG Checking readiness of task: 631 / 0x46620a0
Jul 07 20:44:57-795421 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-795611 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-795800 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-795990 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-796179 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-796368 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-796557 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-796745 util-scheduler-8620 DEBUG Running task: 630 / 0x4d6ff98
Jul 07 20:44:57-796952 util-scheduler-8620 DEBUG Adding task: 632 / 0x4d6ff98
Jul 07 20:44:57-797176 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:44:57-797411 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-797613 util-scheduler-8620 DEBUG Adding task: 633 / 0x46620a0
Jul 07 20:44:57-797854 util-scheduler-8620 DEBUG Checking readiness of task: 633 / 0x46620a0
Jul 07 20:44:57-798046 util-scheduler-8620 DEBUG Checking readiness of task: 631 / 0x46620a0
Jul 07 20:44:57-798236 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-798425 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-798614 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-798803 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-798992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-799181 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-799368 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-799559 util-scheduler-8620 DEBUG Running task: 633 / 0x46620a0
Jul 07 20:44:57-799744 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-799921 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-800093 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-800272 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:57-800467 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-800657 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:57-800960 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:57-933066 util-scheduler-8620 DEBUG Checking readiness of task: 631 / 0x46620a0
Jul 07 20:44:57-933458 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-933658 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-933851 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-934044 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-934264 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-934470 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-934662 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-934871 util-scheduler-8620 DEBUG Running task: 631 / 0x46620a0
Jul 07 20:44:57-935291 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-935544 util-scheduler-8620 DEBUG Adding task: 634 / 0x4662248
Jul 07 20:44:57-935820 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-936013 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-936203 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-936393 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-936582 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-936793 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-936983 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-937212 util-scheduler-8620 DEBUG Running task: 634 / 0x4662248
Jul 07 20:44:57-937635 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:44:57-937971 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:44:57-938234 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:44:57-939205 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:44:57-939550 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:57-939764 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:57-939949 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:44:57-940124 cadet-con-8620 DEBUG   ACK 68 (was 67)
Jul 07 20:44:57-940354 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:44:57-940586 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:57-940791 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:57-941163 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:44:57-941403 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-941622 util-scheduler-8620 DEBUG Adding task: 635 / 0x46620a0
Jul 07 20:44:57-941873 util-scheduler-8620 DEBUG Checking readiness of task: 635 / 0x46620a0
Jul 07 20:44:57-942066 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-942309 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-942500 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-942690 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-942879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-943068 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-943258 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-943449 util-scheduler-8620 DEBUG Running task: 635 / 0x46620a0
Jul 07 20:44:57-943873 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:57-944103 util-scheduler-8620 DEBUG Adding task: 636 / 0x4662248
Jul 07 20:44:57-944351 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-944543 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-944734 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-944933 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-945123 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-945338 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-945544 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-945757 util-scheduler-8620 DEBUG Running task: 636 / 0x4662248
Jul 07 20:44:57-945948 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:44:57-946142 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:44:57-946359 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:44:57-946621 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:44:57-946859 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:44:57-947101 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:57-947323 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:44:57-947563 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:57-947768 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:57-947955 cadet-con-8620 DEBUG  PID 7 (expected 7+)
Jul 07 20:44:57-948136 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:44:57-948322 util-scheduler-8620 DEBUG Canceling task: 606 / 0x4d61c30
Jul 07 20:44:57-948543 util-scheduler-8620 DEBUG Adding task: 637 / 0x4d61c30
Jul 07 20:44:57-948723 cadet-con-8620 DEBUG   message for us!
Jul 07 20:44:57-948982 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:57-949216 util-scheduler-8620 DEBUG Adding task: 638 / 0x4d5e5d8
Jul 07 20:44:57-949478 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:44:57-949648 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:44:57-953599 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:44:57-954747 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:44:57-954946 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:44:57-959323 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:44:57-959551 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:44:57-959876 cadet-chn-8620 DEBUG   head 1, out!
Jul 07 20:44:57-960156 cadet-chn-8620 DEBUG free_sent_reliable 0 0
Jul 07 20:44:57-960435 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x552db98
Jul 07 20:44:57-960718 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:44:57-960893 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:44:57-961070 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:44:57-961463 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:57-961646 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:57-961831 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:57-962015 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:57-962192 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:57-962362 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:57-962580 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:57-962753 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:57-962988 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:57-963173 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:57-963350 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:44:57-963580 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:57-963758 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:44:57-963981 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:44:57-964157 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:44:57-964332 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:44:57-964503 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:44:57-964724 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:44:57-964903 cadet-con-8620 DEBUG  ACK 71
Jul 07 20:44:57-965082 cadet-con-8620 DEBUG  last pid 7, last ack 70, qmax 11, q 0
Jul 07 20:44:57-965386 cadet-con-8620 INFO --> {               ACK} ( 71) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:44:57-965578 cadet-con-8620 DEBUG  ack 71
Jul 07 20:44:57-965757 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:57-965992 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:57-966222 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:57-966663 cadet-p2p-8620 INFO que {               ACK} ( 71) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:44:57-966864 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:44:57-967090 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:57-967273 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 11
Jul 07 20:44:57-967449 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:57-967656 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:44:57-967872 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:44:57-968098 util-scheduler-8620 DEBUG Adding task: 639 / 0x4d5c9e8
Jul 07 20:44:57-968279 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:57-968484 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:57-968661 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:57-968837 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:57-969076 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:44:57-969285 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:44:57-969462 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:44:57-969661 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:57-969844 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:57-970055 util-scheduler-8620 DEBUG Adding task: 640 / 0x46620a0
Jul 07 20:44:57-970325 util-scheduler-8620 DEBUG Checking readiness of task: 640 / 0x46620a0
Jul 07 20:44:57-970520 util-scheduler-8620 DEBUG Checking readiness of task: 638 / 0x4d5e5d8
Jul 07 20:44:57-970711 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-970901 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-971090 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-971396 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-971589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-971779 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-971968 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-972162 util-scheduler-8620 DEBUG Running task: 638 / 0x4d5e5d8
Jul 07 20:44:57-972349 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:57-972528 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-972701 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-972929 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:44:57-973266 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:57-973481 util-scheduler-8620 DEBUG Running task: 639 / 0x4d5c9e8
Jul 07 20:44:57-973705 util-scheduler-8620 DEBUG Adding task: 641 / 0x4d5c9e8
Jul 07 20:44:57-973928 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:57-974128 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:57-974331 util-scheduler-8620 DEBUG Adding task: 642 / 0x46620a0
Jul 07 20:44:57-974572 util-scheduler-8620 DEBUG Checking readiness of task: 642 / 0x46620a0
Jul 07 20:44:57-974765 util-scheduler-8620 DEBUG Checking readiness of task: 640 / 0x46620a0
Jul 07 20:44:57-974955 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:57-975144 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:57-975333 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:57-975523 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:57-975712 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:57-975901 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:57-976244 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:57-976459 util-scheduler-8620 DEBUG Running task: 642 / 0x46620a0
Jul 07 20:44:57-976645 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:57-976820 util-8620 DEBUG process_notify is running
Jul 07 20:44:57-976990 util-8620 DEBUG client_notify is running
Jul 07 20:44:57-977168 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:57-977389 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:57-977577 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:57-977883 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:58-970339 util-scheduler-8620 DEBUG Checking readiness of task: 640 / 0x46620a0
Jul 07 20:44:58-970764 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:58-970974 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:58-971167 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:58-971358 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:58-971552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:58-971744 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:58-971936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:58-972135 util-scheduler-8620 DEBUG Running task: 640 / 0x46620a0
Jul 07 20:44:58-972560 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:44:58-972821 util-scheduler-8620 DEBUG Adding task: 643 / 0x4662248
Jul 07 20:44:58-973103 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:58-973333 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:58-973526 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:58-973718 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:58-973908 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:58-974096 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:58-974285 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:58-974473 util-scheduler-8620 DEBUG Running task: 643 / 0x4662248
Jul 07 20:44:58-974665 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:58-974867 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:58-975098 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:44:58-975304 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:58-975510 util-scheduler-8620 DEBUG Adding task: 644 / 0x46620a0
Jul 07 20:44:58-975730 util-scheduler-8620 DEBUG Adding task: 645 / 0x4662248
Jul 07 20:44:58-975972 util-scheduler-8620 DEBUG Checking readiness of task: 644 / 0x46620a0
Jul 07 20:44:58-976180 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:58-976371 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:58-976560 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:58-976750 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:58-976938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:58-977127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:58-977337 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:58-977529 util-scheduler-8620 DEBUG Running task: 644 / 0x46620a0
Jul 07 20:44:58-977714 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:58-977892 util-8620 DEBUG process_notify is running
Jul 07 20:44:58-978066 util-8620 DEBUG client_notify is running
Jul 07 20:44:58-978264 util-scheduler-8620 DEBUG Canceling task: 632 / 0x4d6ff98
Jul 07 20:44:58-978519 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:44:58-978741 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:44:58-978979 cadet-p2p-8620 DEBUG Checking 0x5557038 towards CMHCKRVP (->V8XX)
Jul 07 20:44:58-979213 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:44:58-979389 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:44:58-979560 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:44:58-979730 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:44:58-979900 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:44:58-980160 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 36)
Jul 07 20:44:58-980354 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:58-980544 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:58-980732 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:44:58-980912 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:44:58-981086 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:58-981289 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:44:58-981488 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:44:58-981662 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:58-981836 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:58-982034 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:44:58-982238 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:44:58-982420 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:44:58-982599 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:58-982790 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:44:58-983496 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:58-983714 util-scheduler-8620 DEBUG Running task: 645 / 0x4662248
Jul 07 20:44:58-983904 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:44:58-984097 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:44:58-984310 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:44:58-984511 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:58-984719 util-scheduler-8620 DEBUG Adding task: 646 / 0x46620a0
Jul 07 20:44:58-984907 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:44:58-985114 util-scheduler-8620 DEBUG Adding task: 647 / 0x46620a0
Jul 07 20:44:58-985400 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:44:58-985607 util-scheduler-8620 DEBUG Checking readiness of task: 646 / 0x46620a0
Jul 07 20:44:58-985801 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:58-985994 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:58-986186 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:58-986383 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:58-986576 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:58-986774 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:58-986970 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:58-987166 util-scheduler-8620 DEBUG Running task: 646 / 0x46620a0
Jul 07 20:44:58-987358 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:58-987539 util-8620 DEBUG process_notify is running
Jul 07 20:44:58-987717 util-8620 DEBUG client_notify is running
Jul 07 20:44:58-987915 util-scheduler-8620 DEBUG Canceling task: 641 / 0x4d5c9e8
Jul 07 20:44:58-988153 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:44:58-988376 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:44:58-988612 cadet-p2p-8620 DEBUG Checking 0x55625d0 towards HS92G30M (->KNAS)
Jul 07 20:44:58-988867 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:44:58-989108 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:44:58-989324 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:44:58-989594 cadet-p2p-8620 INFO snd {               ACK} ( 71) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:44:58-989787 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:44:58-989965 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:44:58-990152 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:44:58-990335 cadet-con-8620 DEBUG  calling cont
Jul 07 20:44:58-990517 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:44:58-990690 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:44:58-990882 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:44:58-991080 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:58-991254 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:44:58-991428 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:44:58-991626 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:58-991828 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:44:58-992010 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:44:58-992188 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:58-992377 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:44:58-993118 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:44:59-585379 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:44:59-585772 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:59-585979 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:59-586178 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:59-586376 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:59-586575 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:59-586769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:59-586964 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:59-587164 util-scheduler-8620 DEBUG Running task: 622 / 0x4d63a48
Jul 07 20:44:59-587357 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:44:59-587659 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:59-587870 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:44:59-588090 cadet-chn-8620 DEBUG   using existing copy: 0x552db98 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:44:59-588285 cadet-chn-8620 DEBUG   new chq: 0x5565fe8
Jul 07 20:44:59-588499 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:44:59-588706 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:44:59-588896 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:44:59-589085 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:44:59-589300 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:44:59-589483 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:44:59-589655 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:44:59-589876 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:44:59-590049 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:44:59-590290 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:44:59-590479 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:44:59-590796 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:44:59-590973 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:59-591160 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:44:59-594732 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:44:59-595553 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:44:59-595731 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:44:59-595920 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:44:59-599147 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:44:59-599391 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:44:59-599574 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:44:59-599796 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:44:59-599991 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:44:59-600272 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:44:59-600472 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:44:59-600648 cadet-con-8620 DEBUG last pid sent 11
Jul 07 20:44:59-600821 cadet-con-8620 DEBUG      ack recv 68
Jul 07 20:44:59-600993 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:44:59-601171 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:44:59-601435 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:44:59-601649 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:44:59-601978 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:44:59-602186 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:44:59-602420 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:44:59-602611 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 11
Jul 07 20:44:59-602788 cadet-con-8620 DEBUG  sendable
Jul 07 20:44:59-603000 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 156 bytes
Jul 07 20:44:59-603226 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:44:59-603466 util-scheduler-8620 DEBUG Adding task: 648 / 0x4d5c9e8
Jul 07 20:44:59-603652 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:44:59-603867 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:44:59-604046 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:44:59-604226 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:44:59-604480 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:44:59-604681 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:44:59-604864 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:44:59-605093 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:44:59-605412 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:44:59-605643 util-scheduler-8620 DEBUG Adding task: 649 / 0x4d5e5d8
Jul 07 20:44:59-605932 util-scheduler-8620 DEBUG Checking readiness of task: 649 / 0x4d5e5d8
Jul 07 20:44:59-606138 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:44:59-606336 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:59-606533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:59-606733 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:59-606928 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:59-607122 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:59-607318 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:59-607514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:59-607716 util-scheduler-8620 DEBUG Running task: 649 / 0x4d5e5d8
Jul 07 20:44:59-607911 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:44:59-608098 util-8620 DEBUG process_notify is running
Jul 07 20:44:59-608279 util-8620 DEBUG client_notify is running
Jul 07 20:44:59-608521 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:44:59-608886 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:44:59-609121 util-scheduler-8620 DEBUG Running task: 648 / 0x4d5c9e8
Jul 07 20:44:59-609380 util-scheduler-8620 DEBUG Adding task: 650 / 0x4d5c9e8
Jul 07 20:44:59-609620 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:44:59-609857 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:44:59-610079 util-scheduler-8620 DEBUG Adding task: 651 / 0x46620a0
Jul 07 20:44:59-610339 util-scheduler-8620 DEBUG Checking readiness of task: 651 / 0x46620a0
Jul 07 20:44:59-610632 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:44:59-610831 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:44:59-611025 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:44:59-611216 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:44:59-611406 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:44:59-611595 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:44:59-611785 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:44:59-611974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:44:59-612165 util-scheduler-8620 DEBUG Running task: 651 / 0x46620a0
Jul 07 20:44:59-612350 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:44:59-612527 util-8620 DEBUG process_notify is running
Jul 07 20:44:59-612698 util-8620 DEBUG client_notify is running
Jul 07 20:44:59-612878 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:44:59-613076 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:44:59-613290 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:44:59-613578 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:01-639747 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:45:01-640139 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-641568 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-641768 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-642033 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-642247 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-642439 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-642629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-642898 util-scheduler-8620 DEBUG Running task: 602 / 0x4d64a70
Jul 07 20:45:01-643140 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:01-643387 cadet-tun-8620 DEBUG  kx started 35 s ago
Jul 07 20:45:01-643593 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:01-643793 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:01-643997 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:01-644234 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:01-644417 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:01-644640 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:01-644933 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:01-645130 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:01-645398 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:01-645607 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:01-645924 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:01-646126 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:01-646352 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:01-646536 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:01-646712 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:01-646920 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:45:01-647138 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:01-647363 util-scheduler-8620 DEBUG Adding task: 652 / 0x4d6ff98
Jul 07 20:45:01-647576 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:01-647784 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:01-647960 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:01-648136 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:01-648375 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:01-648570 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:01-648748 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:01-648958 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:01-649224 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:01-649424 util-scheduler-8620 DEBUG Adding task: 653 / 0x4d64a70
Jul 07 20:45:01-649683 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:45:01-649876 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-650066 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-650255 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-650445 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-650634 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-650823 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-651012 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-651201 util-scheduler-8620 DEBUG Running task: 652 / 0x4d6ff98
Jul 07 20:45:01-651411 util-scheduler-8620 DEBUG Adding task: 654 / 0x4d6ff98
Jul 07 20:45:01-651633 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:01-651836 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:01-652043 util-scheduler-8620 DEBUG Adding task: 655 / 0x46620a0
Jul 07 20:45:01-652286 util-scheduler-8620 DEBUG Checking readiness of task: 655 / 0x46620a0
Jul 07 20:45:01-652478 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:45:01-652668 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-652857 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-653047 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-653255 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-653447 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-653636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-653825 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-654016 util-scheduler-8620 DEBUG Running task: 655 / 0x46620a0
Jul 07 20:45:01-654202 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:01-654384 util-8620 DEBUG process_notify is running
Jul 07 20:45:01-654556 util-8620 DEBUG client_notify is running
Jul 07 20:45:01-654735 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:01-654930 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:01-655120 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:01-655379 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:01-722882 util-scheduler-8620 DEBUG Checking readiness of task: 647 / 0x46620a0
Jul 07 20:45:01-723083 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-723275 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-723466 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-723656 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-723847 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-724036 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-724243 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-724438 util-scheduler-8620 DEBUG Running task: 647 / 0x46620a0
Jul 07 20:45:01-724846 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:01-725080 util-scheduler-8620 DEBUG Adding task: 656 / 0x4662248
Jul 07 20:45:01-725366 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-725559 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-725749 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-725939 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-726128 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-726541 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-726732 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-726923 util-scheduler-8620 DEBUG Running task: 656 / 0x4662248
Jul 07 20:45:01-727129 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:01-727326 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:01-727547 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:01-727746 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:01-727947 util-scheduler-8620 DEBUG Adding task: 657 / 0x46620a0
Jul 07 20:45:01-728133 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:01-728339 util-scheduler-8620 DEBUG Adding task: 658 / 0x46620a0
Jul 07 20:45:01-728583 util-scheduler-8620 DEBUG Checking readiness of task: 658 / 0x46620a0
Jul 07 20:45:01-728774 util-scheduler-8620 DEBUG Checking readiness of task: 657 / 0x46620a0
Jul 07 20:45:01-728966 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-729155 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-729365 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-729555 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-729744 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-729932 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-730121 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-730312 util-scheduler-8620 DEBUG Running task: 657 / 0x46620a0
Jul 07 20:45:01-730496 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:01-730673 util-8620 DEBUG process_notify is running
Jul 07 20:45:01-730842 util-8620 DEBUG client_notify is running
Jul 07 20:45:01-731029 util-scheduler-8620 DEBUG Canceling task: 650 / 0x4d5c9e8
Jul 07 20:45:01-731252 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:45:01-731468 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:01-731701 cadet-p2p-8620 DEBUG Checking 0x556eb10 towards HS92G30M (->KNAS)
Jul 07 20:45:01-731935 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:01-732117 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 11
Jul 07 20:45:01-732291 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:01-732513 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:01-732690 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:45:01-732866 cadet-p2p-8620 DEBUG   payload ID 12
Jul 07 20:45:01-733151 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 156)
Jul 07 20:45:01-733367 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:01-733547 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:01-733735 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:01-733909 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:01-734096 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:01-734284 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:01-734467 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:45:01-734692 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 624 ms
Jul 07 20:45:01-734865 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:01-735070 cadet-chn-8620 DEBUG !! using delay 2499224 µs
Jul 07 20:45:01-735266 util-scheduler-8620 DEBUG Adding task: 659 / 0x4d63a48
Jul 07 20:45:01-735469 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:01-735698 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:01-735874 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:01-736057 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:01-736229 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:01-736426 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:01-736601 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:01-736776 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:01-736977 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:01-737156 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:01-737358 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:01-737540 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:01-737717 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:01-737886 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:01-738103 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:01-738275 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:01-738508 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:01-738692 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:01-738872 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:01-739056 util-scheduler-8620 DEBUG Canceling task: 623 / 0x4d61c30
Jul 07 20:45:01-739267 util-scheduler-8620 DEBUG Adding task: 660 / 0x4d61c30
Jul 07 20:45:01-739510 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:01-739690 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:01-739885 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 12
Jul 07 20:45:01-740059 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:01-740240 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:45:01-740439 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:01-740615 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:01-740788 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:01-740986 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:01-741207 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 156 bytes.
Jul 07 20:45:01-741393 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:45:01-741572 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:01-741764 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:45:01-742015 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:01-938801 util-scheduler-8620 DEBUG Checking readiness of task: 658 / 0x46620a0
Jul 07 20:45:01-939182 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-939380 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-939574 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-940041 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-940594 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-941039 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-941284 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-941485 util-scheduler-8620 DEBUG Running task: 658 / 0x46620a0
Jul 07 20:45:01-942104 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:01-942395 util-scheduler-8620 DEBUG Adding task: 661 / 0x4662248
Jul 07 20:45:01-942678 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-942872 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-943119 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-943312 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-943574 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-943866 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-944075 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-944266 util-scheduler-8620 DEBUG Running task: 661 / 0x4662248
Jul 07 20:45:01-944458 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:01-944658 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:01-945001 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:01-945348 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:01-945865 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:01-946079 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:01-946267 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:01-946455 cadet-con-8620 DEBUG   ACK 69 (was 68)
Jul 07 20:45:01-946690 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:01-946922 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:01-947129 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:01-947313 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:01-947490 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:01-947703 util-scheduler-8620 DEBUG Adding task: 662 / 0x46620a0
Jul 07 20:45:01-947953 util-scheduler-8620 DEBUG Checking readiness of task: 662 / 0x46620a0
Jul 07 20:45:01-948147 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-948338 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-948529 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-948719 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-948910 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-949099 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-949314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-949506 util-scheduler-8620 DEBUG Running task: 662 / 0x46620a0
Jul 07 20:45:01-949909 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:01-950138 util-scheduler-8620 DEBUG Adding task: 663 / 0x4662248
Jul 07 20:45:01-950385 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-950577 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-950768 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-950958 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-951148 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-951338 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-951527 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-951718 util-scheduler-8620 DEBUG Running task: 663 / 0x4662248
Jul 07 20:45:01-951908 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:01-952102 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:01-952318 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:01-952563 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:01-952816 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:01-953045 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:01-953277 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:01-953531 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:01-953738 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:01-953927 cadet-con-8620 DEBUG  PID 8 (expected 8+)
Jul 07 20:45:01-954108 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:01-954297 util-scheduler-8620 DEBUG Canceling task: 637 / 0x4d61c30
Jul 07 20:45:01-954520 util-scheduler-8620 DEBUG Adding task: 664 / 0x4d61c30
Jul 07 20:45:01-954701 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:01-954960 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:01-955174 util-scheduler-8620 DEBUG Adding task: 665 / 0x4d5e5d8
Jul 07 20:45:01-955360 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:01-955528 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:01-959110 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:01-960403 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:01-960601 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:01-963832 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:01-964034 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:45:01-964219 cadet-chn-8620 DEBUG   head 1, out!
Jul 07 20:45:01-964402 cadet-chn-8620 DEBUG free_sent_reliable 0 0
Jul 07 20:45:01-964587 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x552db98
Jul 07 20:45:01-964765 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:01-964935 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:01-965111 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:45:01-965344 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:01-965525 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:01-965709 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:01-965892 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:01-966070 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:01-966240 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:01-966459 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:01-966637 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:01-966872 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:01-967058 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:01-967237 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:45:01-967465 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:01-967643 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:01-967868 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:01-968043 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:01-968220 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:01-968392 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:01-968617 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:01-968796 cadet-con-8620 DEBUG  ACK 72
Jul 07 20:45:01-968977 cadet-con-8620 DEBUG  last pid 8, last ack 71, qmax 11, q 0
Jul 07 20:45:01-969271 cadet-con-8620 INFO --> {               ACK} ( 72) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:01-969464 cadet-con-8620 DEBUG  ack 72
Jul 07 20:45:01-969644 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:01-969881 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:01-970089 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:01-970384 cadet-p2p-8620 INFO que {               ACK} ( 72) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:01-970584 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:01-970820 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:01-971005 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 12
Jul 07 20:45:01-971181 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:01-971386 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:45:01-971623 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:45:01-971845 util-scheduler-8620 DEBUG Adding task: 666 / 0x4d5c9e8
Jul 07 20:45:01-972025 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:01-972230 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:01-972407 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:01-972598 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:01-972840 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:01-973024 cadet-p2p-8620 DEBUG QQQ    payload , 72
Jul 07 20:45:01-973225 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:01-973429 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:01-973611 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:01-973821 util-scheduler-8620 DEBUG Adding task: 667 / 0x46620a0
Jul 07 20:45:01-974086 util-scheduler-8620 DEBUG Checking readiness of task: 667 / 0x46620a0
Jul 07 20:45:01-974282 util-scheduler-8620 DEBUG Checking readiness of task: 665 / 0x4d5e5d8
Jul 07 20:45:01-974475 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-974665 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-974855 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-975045 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-975234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-975423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-975612 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-975805 util-scheduler-8620 DEBUG Running task: 665 / 0x4d5e5d8
Jul 07 20:45:01-975991 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:01-976170 util-8620 DEBUG process_notify is running
Jul 07 20:45:01-976343 util-8620 DEBUG client_notify is running
Jul 07 20:45:01-976574 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:01-976924 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:01-977138 util-scheduler-8620 DEBUG Running task: 666 / 0x4d5c9e8
Jul 07 20:45:01-977429 util-scheduler-8620 DEBUG Adding task: 668 / 0x4d5c9e8
Jul 07 20:45:01-977656 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:01-977859 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:01-978061 util-scheduler-8620 DEBUG Adding task: 669 / 0x46620a0
Jul 07 20:45:01-978304 util-scheduler-8620 DEBUG Checking readiness of task: 669 / 0x46620a0
Jul 07 20:45:01-978496 util-scheduler-8620 DEBUG Checking readiness of task: 667 / 0x46620a0
Jul 07 20:45:01-978686 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:01-978876 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:01-979066 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:01-979255 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:01-979445 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:01-979647 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:01-979836 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:01-980026 util-scheduler-8620 DEBUG Running task: 669 / 0x46620a0
Jul 07 20:45:01-980210 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:01-980385 util-8620 DEBUG process_notify is running
Jul 07 20:45:01-980555 util-8620 DEBUG client_notify is running
Jul 07 20:45:01-980734 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:01-980929 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:01-981117 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:01-981467 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:02-260243 util-scheduler-8620 DEBUG Checking readiness of task: 667 / 0x46620a0
Jul 07 20:45:02-260603 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:02-260800 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:02-260993 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:02-261185 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:02-261403 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:02-261595 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:02-261787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:02-261982 util-scheduler-8620 DEBUG Running task: 667 / 0x46620a0
Jul 07 20:45:02-262403 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:02-262659 util-scheduler-8620 DEBUG Adding task: 670 / 0x4662248
Jul 07 20:45:02-262935 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:02-263127 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:02-263318 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:02-263508 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:02-263698 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:02-263888 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:02-264078 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:02-264268 util-scheduler-8620 DEBUG Running task: 670 / 0x4662248
Jul 07 20:45:02-264463 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:02-264662 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:02-264891 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:02-265096 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:02-265331 util-scheduler-8620 DEBUG Adding task: 671 / 0x46620a0
Jul 07 20:45:02-265519 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:02-265724 util-scheduler-8620 DEBUG Adding task: 672 / 0x46620a0
Jul 07 20:45:02-265968 util-scheduler-8620 DEBUG Checking readiness of task: 672 / 0x46620a0
Jul 07 20:45:02-266198 util-scheduler-8620 DEBUG Checking readiness of task: 671 / 0x46620a0
Jul 07 20:45:02-266390 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:02-266580 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:02-266769 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:02-266959 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:02-267148 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:02-267338 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:02-267527 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:02-267719 util-scheduler-8620 DEBUG Running task: 671 / 0x46620a0
Jul 07 20:45:02-267905 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:02-268084 util-8620 DEBUG process_notify is running
Jul 07 20:45:02-268256 util-8620 DEBUG client_notify is running
Jul 07 20:45:02-268445 util-scheduler-8620 DEBUG Canceling task: 668 / 0x4d5c9e8
Jul 07 20:45:02-268667 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:45:02-268887 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:02-269186 cadet-p2p-8620 DEBUG Checking 0x557e0f0 towards HS92G30M (->KNAS)
Jul 07 20:45:02-269523 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:02-269730 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:02-269923 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:02-270193 cadet-p2p-8620 INFO snd {               ACK} ( 72) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:02-270388 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:02-270569 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:02-270758 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:02-270932 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:02-271115 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:02-271290 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:02-271473 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:02-271672 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:02-271847 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:02-272022 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:02-272221 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:02-272426 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:02-272609 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:02-272789 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:02-272981 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:02-273796 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:04-236620 util-scheduler-8620 DEBUG Checking readiness of task: 672 / 0x46620a0
Jul 07 20:45:04-237011 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-237233 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-237428 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-237620 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-237811 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-238005 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-238196 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-238389 util-scheduler-8620 DEBUG Running task: 659 / 0x4d63a48
Jul 07 20:45:04-238577 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:45:04-238871 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:04-239074 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:45:04-239276 cadet-chn-8620 DEBUG   using existing copy: 0x552db98 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:04-239467 cadet-chn-8620 DEBUG   new chq: 0x5580b30
Jul 07 20:45:04-239673 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:04-239874 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:04-240054 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:04-240237 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:04-240417 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:04-240595 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:04-240765 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:04-241062 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:04-241265 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:04-241506 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:04-241692 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:04-242024 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:04-242197 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:04-242384 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:04-245946 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:04-246774 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:04-246952 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:04-247143 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:04-250351 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:04-250624 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:04-250807 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:04-251031 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:04-251227 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:04-251519 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:45:04-251721 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:04-251900 cadet-con-8620 DEBUG last pid sent 12
Jul 07 20:45:04-252074 cadet-con-8620 DEBUG      ack recv 69
Jul 07 20:45:04-252247 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:04-252425 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:04-252660 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:04-252868 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:04-253316 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:45:04-253523 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:04-253750 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:04-253933 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 12
Jul 07 20:45:04-254109 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:04-254316 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 156 bytes
Jul 07 20:45:04-254532 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:45:04-254761 util-scheduler-8620 DEBUG Adding task: 673 / 0x4d5c9e8
Jul 07 20:45:04-254943 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:04-255148 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:04-255325 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:04-255500 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:04-255738 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:04-255933 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:04-256111 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:04-256310 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:04-256582 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:04-256799 util-scheduler-8620 DEBUG Adding task: 674 / 0x4d5e5d8
Jul 07 20:45:04-257071 util-scheduler-8620 DEBUG Checking readiness of task: 674 / 0x4d5e5d8
Jul 07 20:45:04-257291 util-scheduler-8620 DEBUG Checking readiness of task: 672 / 0x46620a0
Jul 07 20:45:04-257484 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-257675 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-257865 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-258058 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-258248 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-258437 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-258636 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-258830 util-scheduler-8620 DEBUG Running task: 674 / 0x4d5e5d8
Jul 07 20:45:04-259016 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:04-259196 util-8620 DEBUG process_notify is running
Jul 07 20:45:04-259369 util-8620 DEBUG client_notify is running
Jul 07 20:45:04-259596 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:04-259909 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:04-260121 util-scheduler-8620 DEBUG Running task: 673 / 0x4d5c9e8
Jul 07 20:45:04-260332 util-scheduler-8620 DEBUG Adding task: 675 / 0x4d5c9e8
Jul 07 20:45:04-260554 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:04-260750 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:04-260967 util-scheduler-8620 DEBUG Adding task: 676 / 0x46620a0
Jul 07 20:45:04-261233 util-scheduler-8620 DEBUG Checking readiness of task: 676 / 0x46620a0
Jul 07 20:45:04-261428 util-scheduler-8620 DEBUG Checking readiness of task: 672 / 0x46620a0
Jul 07 20:45:04-261618 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-261808 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-261997 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-262187 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-262377 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-262578 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-262767 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-262958 util-scheduler-8620 DEBUG Running task: 676 / 0x46620a0
Jul 07 20:45:04-263142 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:04-263317 util-8620 DEBUG process_notify is running
Jul 07 20:45:04-263487 util-8620 DEBUG client_notify is running
Jul 07 20:45:04-263667 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:04-263863 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:04-264051 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:04-264364 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:04-291147 util-scheduler-8620 DEBUG Checking readiness of task: 672 / 0x46620a0
Jul 07 20:45:04-291447 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-291643 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-291835 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-292040 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-292231 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-292422 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-292614 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-292809 util-scheduler-8620 DEBUG Running task: 672 / 0x46620a0
Jul 07 20:45:04-293251 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:04-293503 util-scheduler-8620 DEBUG Adding task: 677 / 0x4662248
Jul 07 20:45:04-293767 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-293959 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-294149 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-294339 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-294529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-294719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-294908 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-295098 util-scheduler-8620 DEBUG Running task: 677 / 0x4662248
Jul 07 20:45:04-295290 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:04-295488 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:04-295715 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:04-295932 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:04-296136 util-scheduler-8620 DEBUG Adding task: 678 / 0x46620a0
Jul 07 20:45:04-296323 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:04-296530 util-scheduler-8620 DEBUG Adding task: 679 / 0x46620a0
Jul 07 20:45:04-296773 util-scheduler-8620 DEBUG Checking readiness of task: 679 / 0x46620a0
Jul 07 20:45:04-296987 util-scheduler-8620 DEBUG Checking readiness of task: 678 / 0x46620a0
Jul 07 20:45:04-297179 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-300184 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-300383 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-300575 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-300767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-300958 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-301148 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-301367 util-scheduler-8620 DEBUG Running task: 678 / 0x46620a0
Jul 07 20:45:04-301554 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:04-301734 util-8620 DEBUG process_notify is running
Jul 07 20:45:04-301905 util-8620 DEBUG client_notify is running
Jul 07 20:45:04-302096 util-scheduler-8620 DEBUG Canceling task: 654 / 0x4d6ff98
Jul 07 20:45:04-302329 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:04-302923 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:04-303166 cadet-p2p-8620 DEBUG Checking 0x5570ad8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:04-303401 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:04-303580 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:04-303773 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:04-304060 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:04-304256 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:04-304437 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:04-304626 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:04-304817 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:04-304995 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:04-305181 util-scheduler-8620 DEBUG Canceling task: 627 / 0x4d707d0
Jul 07 20:45:04-305421 util-scheduler-8620 DEBUG Adding task: 680 / 0x4d707d0
Jul 07 20:45:04-305675 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:04-305850 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:04-306033 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:04-306235 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:04-306410 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:04-306584 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:04-306783 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:04-307406 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:04-307594 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:04-307775 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:04-307971 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:04-308777 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:04-627221 util-scheduler-8620 DEBUG Checking readiness of task: 679 / 0x46620a0
Jul 07 20:45:04-627564 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-627780 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-627975 util-scheduler-8620 DEBUG Checking readiness of task: 102 / 0x465ee60
Jul 07 20:45:04-628174 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-628366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-628558 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-628749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-628944 util-scheduler-8620 DEBUG Running task: 102 / 0x465ee60
Jul 07 20:45:04-629596 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:45:04-629883 util-scheduler-8620 DEBUG Adding task: 681 / 0x465f008
Jul 07 20:45:04-630160 util-scheduler-8620 DEBUG Checking readiness of task: 679 / 0x46620a0
Jul 07 20:45:04-630353 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-630543 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-630734 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-630924 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-631114 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-631304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-631496 util-scheduler-8620 DEBUG Running task: 681 / 0x465f008
Jul 07 20:45:04-631689 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:45:04-631931 nse-api-8620 DEBUG Received information about peer `4YCN' from peerinfo database
Jul 07 20:45:04-632450 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:45:04-632671 util-scheduler-8620 DEBUG Adding task: 682 / 0x465f008
Jul 07 20:45:04-632913 util-scheduler-8620 DEBUG Checking readiness of task: 679 / 0x46620a0
Jul 07 20:45:04-633106 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:04-633410 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:04-633606 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:04-633797 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:04-633987 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:04-634191 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:04-634381 util-scheduler-8620 DEBUG Running task: 682 / 0x465f008
Jul 07 20:45:04-634572 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:45:04-634792 nse-api-8620 DEBUG Received information about peer `4YCN' from peerinfo database
Jul 07 20:45:04-635066 cadet-hll-8620 DEBUG  hello for 4YCN (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:45:04-635325 cadet-p2p-8620 DEBUG set hello for 4YCN
Jul 07 20:45:04-635502 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:45:04-635692 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:04-635902 util-scheduler-8620 DEBUG Adding task: 683 / 0x465ee60
Jul 07 20:45:05-364852 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:05-365248 util-scheduler-8620 DEBUG Checking readiness of task: 679 / 0x46620a0
Jul 07 20:45:05-365449 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:05-365643 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:05-365835 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:05-366026 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:05-366217 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:05-366408 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:05-366604 util-scheduler-8620 DEBUG Running task: 679 / 0x46620a0
Jul 07 20:45:05-367026 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:05-367303 util-scheduler-8620 DEBUG Adding task: 684 / 0x4662248
Jul 07 20:45:05-367618 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:05-367811 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:05-368002 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:05-368195 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:05-368384 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:05-368604 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:05-368795 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:05-368985 util-scheduler-8620 DEBUG Running task: 684 / 0x4662248
Jul 07 20:45:05-369177 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:05-369399 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:05-369630 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:05-369895 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:05-370140 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:05-370371 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:05-370679 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:05-370928 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:05-371139 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:05-371327 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:05-371517 util-scheduler-8620 DEBUG Canceling task: 629 / 0x4d707d0
Jul 07 20:45:05-371742 util-scheduler-8620 DEBUG Adding task: 685 / 0x4d707d0
Jul 07 20:45:05-371923 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:05-372182 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:05-372399 util-scheduler-8620 DEBUG Adding task: 686 / 0x4d5e5d8
Jul 07 20:45:05-372581 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:05-372782 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:06-206831 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:45:06-207179 cadet-tun-8620 INFO PE: H9RZ635J
Jul 07 20:45:06-207368 cadet-tun-8620 INFO KM: 053NA9Q1
Jul 07 20:45:06-207554 cadet-tun-8620 INFO EK: WNEQZBYQ
Jul 07 20:45:06-207749 cadet-tun-8620 INFO DK: VJ50N9K4
Jul 07 20:45:06-208101 cadet-tun-8620 DEBUG   our key was sent, sending ping
Jul 07 20:45:06-208338 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:06-208640 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:06-208843 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:06-209014 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:06-209225 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:06-212288 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:06-213091 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:06-213299 cadet-tun-8620 DEBUG   e sending 2846118667
Jul 07 20:45:06-213510 cadet-tun-8620 DEBUG   e towards WPXC
Jul 07 20:45:06-213711 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:06-213913 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:06-214144 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:06-214325 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:06-214547 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:06-214834 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:06-215033 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:06-215269 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:06-215479 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:06-215793 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:06-215993 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:06-216219 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:06-216402 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:06-216578 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:06-216796 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 80 bytes
Jul 07 20:45:06-217014 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:06-217272 util-scheduler-8620 DEBUG Adding task: 687 / 0x4d6ff98
Jul 07 20:45:06-217456 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:06-217663 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-217869 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:06-218046 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:06-218286 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-218481 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-218659 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-218858 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-219043 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-219259 util-scheduler-8620 DEBUG Adding task: 688 / 0x46620a0
Jul 07 20:45:06-219547 util-scheduler-8620 DEBUG Checking readiness of task: 688 / 0x46620a0
Jul 07 20:45:06-219745 util-scheduler-8620 DEBUG Checking readiness of task: 686 / 0x4d5e5d8
Jul 07 20:45:06-219964 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-220155 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-220344 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-220533 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-220723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-220911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-221099 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-221316 util-scheduler-8620 DEBUG Running task: 686 / 0x4d5e5d8
Jul 07 20:45:06-221504 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:06-221685 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-221857 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-222090 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:06-222360 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:06-222576 util-scheduler-8620 DEBUG Running task: 688 / 0x46620a0
Jul 07 20:45:06-222985 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:06-223218 util-scheduler-8620 DEBUG Adding task: 689 / 0x4662248
Jul 07 20:45:06-223427 util-scheduler-8620 DEBUG Running task: 687 / 0x4d6ff98
Jul 07 20:45:06-223636 util-scheduler-8620 DEBUG Adding task: 690 / 0x4d6ff98
Jul 07 20:45:06-223858 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:06-224062 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-224265 util-scheduler-8620 DEBUG Adding task: 691 / 0x46620a0
Jul 07 20:45:06-224507 util-scheduler-8620 DEBUG Checking readiness of task: 691 / 0x46620a0
Jul 07 20:45:06-224699 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-224888 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-225078 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-225290 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-225483 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-225683 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-225872 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-226062 util-scheduler-8620 DEBUG Running task: 691 / 0x46620a0
Jul 07 20:45:06-226247 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-226423 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-226592 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-226771 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:06-226967 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-227156 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:06-227399 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-227622 util-scheduler-8620 DEBUG Running task: 689 / 0x4662248
Jul 07 20:45:06-227816 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:06-228016 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:06-228234 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:06-228488 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:06-228740 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:06-228948 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:06-229130 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:06-229326 cadet-con-8620 DEBUG   ACK 70 (was 69)
Jul 07 20:45:06-229555 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:06-229787 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:06-229992 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:06-230174 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:06-230375 util-scheduler-8620 DEBUG Adding task: 692 / 0x4662248
Jul 07 20:45:06-230613 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-230804 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-230995 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-231184 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-231385 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-231575 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-231764 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-231953 util-scheduler-8620 DEBUG Running task: 692 / 0x4662248
Jul 07 20:45:06-232141 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:06-232332 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:06-232546 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:06-232744 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-232942 util-scheduler-8620 DEBUG Adding task: 693 / 0x46620a0
Jul 07 20:45:06-233126 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-233347 util-scheduler-8620 DEBUG Adding task: 694 / 0x46620a0
Jul 07 20:45:06-233586 util-scheduler-8620 DEBUG Checking readiness of task: 694 / 0x46620a0
Jul 07 20:45:06-233778 util-scheduler-8620 DEBUG Checking readiness of task: 693 / 0x46620a0
Jul 07 20:45:06-233970 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-234159 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-234348 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-234538 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-234738 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-234976 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-235165 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-235356 util-scheduler-8620 DEBUG Running task: 693 / 0x46620a0
Jul 07 20:45:06-235544 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-235719 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-235889 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-236076 util-scheduler-8620 DEBUG Canceling task: 675 / 0x4d5c9e8
Jul 07 20:45:06-236298 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:45:06-236513 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:06-236744 cadet-p2p-8620 DEBUG Checking 0x5589658 towards HS92G30M (->KNAS)
Jul 07 20:45:06-236976 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:06-237176 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 12
Jul 07 20:45:06-237375 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:06-237599 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:06-237777 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:45:06-237953 cadet-p2p-8620 DEBUG   payload ID 13
Jul 07 20:45:06-238237 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 156)
Jul 07 20:45:06-238432 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:06-238612 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:06-238801 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:06-238976 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:06-239145 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:06-239333 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:06-239511 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:45:06-239739 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 624 ms
Jul 07 20:45:06-239910 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:06-240116 cadet-chn-8620 DEBUG !! using delay 2499224 µs
Jul 07 20:45:06-240313 util-scheduler-8620 DEBUG Adding task: 695 / 0x4d63a48
Jul 07 20:45:06-240516 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:06-240746 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:06-240922 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:06-241095 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:06-241290 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:06-241490 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:06-241665 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:06-241839 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:06-242041 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:06-242220 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:06-242403 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:06-242583 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:06-242760 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:06-242930 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:06-243147 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:06-243320 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:06-243561 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:06-243746 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:06-243927 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:06-244113 util-scheduler-8620 DEBUG Canceling task: 660 / 0x4d61c30
Jul 07 20:45:06-244323 util-scheduler-8620 DEBUG Adding task: 696 / 0x4d61c30
Jul 07 20:45:06-244568 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:06-244748 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:06-244927 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 13
Jul 07 20:45:06-245099 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:06-245303 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:45:06-245507 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:06-245682 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:06-245855 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:06-246054 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:06-246264 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 156 bytes.
Jul 07 20:45:06-246447 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:45:06-246626 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-246815 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:45:06-247064 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-649918 util-scheduler-8620 DEBUG Checking readiness of task: 694 / 0x46620a0
Jul 07 20:45:06-650160 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-653601 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-653811 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-654003 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-654194 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-654384 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-654575 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-654766 util-scheduler-8620 DEBUG Running task: 653 / 0x4d64a70
Jul 07 20:45:06-654994 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:06-655234 cadet-tun-8620 DEBUG  kx started 40 s ago
Jul 07 20:45:06-655440 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:06-655643 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:06-655844 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:06-656076 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:06-656255 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:06-656477 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:06-656763 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:06-656960 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:06-657226 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:06-657452 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:06-657765 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:06-657966 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:06-658191 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:06-658387 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:06-658563 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:06-658769 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:06-658972 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-659148 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:06-659323 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:06-659561 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-659756 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-659933 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-660166 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-660360 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:06-660536 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:06-660734 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-660937 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:06-661253 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:06-661455 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:06-661626 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:06-661808 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:06-665256 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:06-666530 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:06-666712 cadet-tun-8620 DEBUG   e sending 359434915
Jul 07 20:45:06-666919 cadet-tun-8620 DEBUG   e towards WTQG
Jul 07 20:45:06-667120 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:06-667320 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:06-667547 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:06-667727 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:06-667948 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:06-668221 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:06-668417 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:06-668652 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:06-668878 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:06-669185 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:06-669408 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:06-669632 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:06-669816 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:06-669991 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:06-670193 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:06-670394 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-670570 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:06-670745 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:06-670981 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-671175 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-671353 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-671596 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-671790 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:06-671966 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:06-672199 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-672391 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-672567 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-672764 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-673011 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:06-673241 util-scheduler-8620 DEBUG Adding task: 697 / 0x4d64a70
Jul 07 20:45:06-820802 util-scheduler-8620 DEBUG Checking readiness of task: 694 / 0x46620a0
Jul 07 20:45:06-821027 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-821277 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-821473 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-821664 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-821853 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-822046 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-822236 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-822428 util-scheduler-8620 DEBUG Running task: 694 / 0x46620a0
Jul 07 20:45:06-822849 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:06-823095 util-scheduler-8620 DEBUG Adding task: 698 / 0x4662248
Jul 07 20:45:06-824716 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-824914 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-825107 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-825322 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-825513 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-825705 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-825896 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-826091 util-scheduler-8620 DEBUG Running task: 698 / 0x4662248
Jul 07 20:45:06-826291 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:06-826489 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:06-826716 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:06-826923 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-827131 util-scheduler-8620 DEBUG Adding task: 699 / 0x46620a0
Jul 07 20:45:06-827320 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-827525 util-scheduler-8620 DEBUG Adding task: 700 / 0x46620a0
Jul 07 20:45:06-827796 util-scheduler-8620 DEBUG Checking readiness of task: 700 / 0x46620a0
Jul 07 20:45:06-827988 util-scheduler-8620 DEBUG Checking readiness of task: 699 / 0x46620a0
Jul 07 20:45:06-828181 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-828371 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-828563 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-828752 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-828953 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-829148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-829365 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-829561 util-scheduler-8620 DEBUG Running task: 699 / 0x46620a0
Jul 07 20:45:06-829750 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-829930 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-830105 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-830296 util-scheduler-8620 DEBUG Canceling task: 690 / 0x4d6ff98
Jul 07 20:45:06-830544 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:06-830767 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:06-831007 cadet-p2p-8620 DEBUG Checking 0x589dfd8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-831262 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:06-831442 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:06-831640 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:06-831937 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:06-832137 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:06-832322 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:06-832511 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:06-832702 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:06-832882 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:06-833073 util-scheduler-8620 DEBUG Canceling task: 680 / 0x4d707d0
Jul 07 20:45:06-833318 util-scheduler-8620 DEBUG Adding task: 701 / 0x4d707d0
Jul 07 20:45:06-833572 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:06-833745 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:06-833971 cadet-p2p-8620 DEBUG Checking 0x58a2348 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-834214 cadet-p2p-8620 DEBUG Checking 0x58a2348 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-834395 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:06-834606 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:06-834824 util-scheduler-8620 DEBUG Adding task: 702 / 0x4d6ff98
Jul 07 20:45:06-835005 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:06-835185 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:06-835387 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-835563 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:06-835739 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:06-835981 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-836178 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:06-836356 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:06-836592 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-836786 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-836963 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-837162 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-837392 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:06-837577 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:06-837784 util-scheduler-8620 DEBUG Adding task: 703 / 0x4d6ff98
Jul 07 20:45:06-838022 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:06-838241 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-838448 util-scheduler-8620 DEBUG Adding task: 704 / 0x46620a0
Jul 07 20:45:06-838656 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:06-840512 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-840821 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:06-841087 util-scheduler-8620 DEBUG Checking readiness of task: 704 / 0x46620a0
Jul 07 20:45:06-841310 util-scheduler-8620 DEBUG Checking readiness of task: 700 / 0x46620a0
Jul 07 20:45:06-841503 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-841695 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-841887 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-842079 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-842271 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-842463 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-842654 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-842849 util-scheduler-8620 DEBUG Running task: 704 / 0x46620a0
Jul 07 20:45:06-843037 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-843217 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-843392 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-843573 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:06-843774 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-843965 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:06-844254 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-844464 util-scheduler-8620 DEBUG Running task: 702 / 0x4d6ff98
Jul 07 20:45:06-844661 util-scheduler-8620 DEBUG Canceling task: 703 / 0x4d6ff98
Jul 07 20:45:06-844883 util-scheduler-8620 DEBUG Adding task: 705 / 0x4d6ff98
Jul 07 20:45:06-845107 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:06-845333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-845536 util-scheduler-8620 DEBUG Adding task: 706 / 0x46620a0
Jul 07 20:45:06-845781 util-scheduler-8620 DEBUG Checking readiness of task: 706 / 0x46620a0
Jul 07 20:45:06-845974 util-scheduler-8620 DEBUG Checking readiness of task: 700 / 0x46620a0
Jul 07 20:45:06-846164 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-846355 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-846546 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-846736 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-846927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-847116 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-847307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-847500 util-scheduler-8620 DEBUG Running task: 706 / 0x46620a0
Jul 07 20:45:06-847685 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-847862 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-848033 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-848210 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:06-848402 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-848595 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:06-848883 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-854892 util-scheduler-8620 DEBUG Checking readiness of task: 700 / 0x46620a0
Jul 07 20:45:06-855144 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-855340 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-855533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-855726 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-856001 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-856205 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-856397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-856592 util-scheduler-8620 DEBUG Running task: 700 / 0x46620a0
Jul 07 20:45:06-857005 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:06-857273 util-scheduler-8620 DEBUG Adding task: 707 / 0x4662248
Jul 07 20:45:06-857537 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-857731 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-857923 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-858114 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-858306 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-858496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-858690 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-858881 util-scheduler-8620 DEBUG Running task: 707 / 0x4662248
Jul 07 20:45:06-859073 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:06-859272 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:06-859498 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:06-859700 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-859903 util-scheduler-8620 DEBUG Adding task: 708 / 0x46620a0
Jul 07 20:45:06-860090 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-860310 util-scheduler-8620 DEBUG Adding task: 709 / 0x46620a0
Jul 07 20:45:06-860556 util-scheduler-8620 DEBUG Checking readiness of task: 709 / 0x46620a0
Jul 07 20:45:06-860749 util-scheduler-8620 DEBUG Checking readiness of task: 708 / 0x46620a0
Jul 07 20:45:06-860941 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-861132 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-861347 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-861538 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-861885 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-862080 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-862272 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-862467 util-scheduler-8620 DEBUG Running task: 708 / 0x46620a0
Jul 07 20:45:06-862654 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-862832 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-863005 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-863193 util-scheduler-8620 DEBUG Canceling task: 705 / 0x4d6ff98
Jul 07 20:45:06-863420 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:06-863640 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:06-863879 cadet-p2p-8620 DEBUG Checking 0x58a2348 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-864114 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:06-864293 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:06-864484 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:06-864792 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:06-864989 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:06-865170 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:06-865382 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:06-865573 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:06-865751 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:06-865939 util-scheduler-8620 DEBUG Canceling task: 701 / 0x4d707d0
Jul 07 20:45:06-866162 util-scheduler-8620 DEBUG Adding task: 710 / 0x4d707d0
Jul 07 20:45:06-866413 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:06-866586 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:06-866810 cadet-p2p-8620 DEBUG Checking 0x58a8cc0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-867049 cadet-p2p-8620 DEBUG Checking 0x58a8cc0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-867229 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:06-867437 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:06-867650 util-scheduler-8620 DEBUG Adding task: 711 / 0x4d6ff98
Jul 07 20:45:06-867831 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:06-868009 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:06-868211 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-868391 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:06-868570 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:06-868814 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:06-869016 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:06-869219 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:06-869422 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-869628 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:06-869812 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:06-870019 util-scheduler-8620 DEBUG Adding task: 712 / 0x4d6ff98
Jul 07 20:45:06-870239 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:06-870436 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-870639 util-scheduler-8620 DEBUG Adding task: 713 / 0x46620a0
Jul 07 20:45:06-870839 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:06-871683 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-871887 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:06-872239 util-scheduler-8620 DEBUG Checking readiness of task: 713 / 0x46620a0
Jul 07 20:45:06-872437 util-scheduler-8620 DEBUG Checking readiness of task: 709 / 0x46620a0
Jul 07 20:45:06-872630 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-872821 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-873011 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-873225 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-873418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-873608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-873799 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-873992 util-scheduler-8620 DEBUG Running task: 713 / 0x46620a0
Jul 07 20:45:06-874179 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-874357 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-874530 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-874710 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:06-874906 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-875095 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:06-875416 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-875626 util-scheduler-8620 DEBUG Running task: 711 / 0x4d6ff98
Jul 07 20:45:06-875819 util-scheduler-8620 DEBUG Canceling task: 712 / 0x4d6ff98
Jul 07 20:45:06-876583 util-scheduler-8620 DEBUG Adding task: 714 / 0x4d6ff98
Jul 07 20:45:06-876814 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:06-877011 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-877235 util-scheduler-8620 DEBUG Adding task: 715 / 0x46620a0
Jul 07 20:45:06-877481 util-scheduler-8620 DEBUG Checking readiness of task: 715 / 0x46620a0
Jul 07 20:45:06-877759 util-scheduler-8620 DEBUG Checking readiness of task: 709 / 0x46620a0
Jul 07 20:45:06-877952 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-878144 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-878335 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-878526 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-878724 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-878915 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-879105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-879296 util-scheduler-8620 DEBUG Running task: 709 / 0x46620a0
Jul 07 20:45:06-879699 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:06-879929 util-scheduler-8620 DEBUG Adding task: 716 / 0x4662248
Jul 07 20:45:06-880139 util-scheduler-8620 DEBUG Running task: 715 / 0x46620a0
Jul 07 20:45:06-880326 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-880502 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-880673 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-880850 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:06-881041 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-881254 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:06-881561 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:06-881812 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-882005 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-882197 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-882388 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-882578 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-882769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-882959 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-883150 util-scheduler-8620 DEBUG Running task: 716 / 0x4662248
Jul 07 20:45:06-883352 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:06-883549 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:06-883765 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:06-883947 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-884151 util-scheduler-8620 DEBUG Adding task: 717 / 0x46620a0
Jul 07 20:45:06-884395 util-scheduler-8620 DEBUG Checking readiness of task: 717 / 0x46620a0
Jul 07 20:45:06-884588 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-884779 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-884969 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-885175 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-885393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-885583 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-885772 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-885963 util-scheduler-8620 DEBUG Running task: 717 / 0x46620a0
Jul 07 20:45:06-886362 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:06-886596 util-scheduler-8620 DEBUG Adding task: 718 / 0x4662248
Jul 07 20:45:06-886843 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-887036 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-887227 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-887418 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-887608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-887798 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-887988 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-888178 util-scheduler-8620 DEBUG Running task: 718 / 0x4662248
Jul 07 20:45:06-888368 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:06-888563 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:06-888775 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:06-888971 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:06-889170 util-scheduler-8620 DEBUG Adding task: 719 / 0x46620a0
Jul 07 20:45:06-889377 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:06-889574 util-scheduler-8620 DEBUG Adding task: 720 / 0x46620a0
Jul 07 20:45:06-889815 util-scheduler-8620 DEBUG Checking readiness of task: 720 / 0x46620a0
Jul 07 20:45:06-890008 util-scheduler-8620 DEBUG Checking readiness of task: 719 / 0x46620a0
Jul 07 20:45:06-890199 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:06-890390 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:06-890580 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:06-890770 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:06-890960 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:06-891150 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:06-891339 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:06-891531 util-scheduler-8620 DEBUG Running task: 719 / 0x46620a0
Jul 07 20:45:06-891716 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:06-891892 util-8620 DEBUG process_notify is running
Jul 07 20:45:06-892062 util-8620 DEBUG client_notify is running
Jul 07 20:45:06-892244 util-scheduler-8620 DEBUG Canceling task: 714 / 0x4d6ff98
Jul 07 20:45:06-892463 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:06-892677 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:06-892910 cadet-p2p-8620 DEBUG Checking 0x58a8cc0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:06-893142 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:06-893344 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:06-893531 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:06-893809 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:06-894004 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:06-894183 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:06-894370 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:06-894559 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:06-894752 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:06-894938 util-scheduler-8620 DEBUG Canceling task: 710 / 0x4d707d0
Jul 07 20:45:06-895149 util-scheduler-8620 DEBUG Adding task: 721 / 0x4d707d0
Jul 07 20:45:06-895394 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:06-895565 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:06-895747 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:06-896009 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:06-896185 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:06-896360 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:06-896558 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:06-896762 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:06-896945 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:06-897124 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:06-897337 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:06-898790 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:07-926330 util-scheduler-8620 DEBUG Checking readiness of task: 720 / 0x46620a0
Jul 07 20:45:07-926721 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:07-926920 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:07-927113 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:07-927306 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:07-927498 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:07-927689 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:07-927880 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:07-928076 util-scheduler-8620 DEBUG Running task: 720 / 0x46620a0
Jul 07 20:45:07-928521 util-8620 DEBUG receive_ready read 33488/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:07-929507 util-scheduler-8620 DEBUG Adding task: 722 / 0x4662248
Jul 07 20:45:07-929847 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:07-930043 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:07-930234 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:07-930424 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:07-930615 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:07-930804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:07-930994 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:07-931184 util-scheduler-8620 DEBUG Running task: 722 / 0x4662248
Jul 07 20:45:07-931382 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:45:07-931768 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:45:07-932014 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `KNAS'
Jul 07 20:45:07-932281 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:07-932524 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:07-932755 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:07-932965 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:07-933307 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:07-933521 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:07-933710 cadet-con-8620 DEBUG  PID 9 (expected 9+)
Jul 07 20:45:07-933891 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:07-934081 util-scheduler-8620 DEBUG Canceling task: 664 / 0x4d61c30
Jul 07 20:45:07-934305 util-scheduler-8620 DEBUG Adding task: 723 / 0x4d61c30
Jul 07 20:45:07-934485 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:07-934779 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:07-934998 util-scheduler-8620 DEBUG Adding task: 724 / 0x4d5e5d8
Jul 07 20:45:07-935190 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:07-935360 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:07-938958 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:07-959117 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:07-959362 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:08-007781 cadet-tun-8620 INFO <=== {              DATA} on KNAS
Jul 07 20:45:08-008261 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:45:08-008658 cadet-chn-8620 INFO <=== DATA 0 BCK on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-010531 cadet-chn-8620 WARNING MID 0 on channel KNAS:19 gid:40000000 (80000001 / 0) not expected (window: 1 - 64). Dropping!
Jul 07 20:45:08-011245 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:45:08-011592 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:45:08-011853 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-012078 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:08-012283 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:08-012468 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:08-012657 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:08-012844 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:08-013025 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:08-013221 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:08-013443 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-013620 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:08-013872 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:08-014061 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:08-014361 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:08-014535 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:08-014723 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:08-017868 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:08-019074 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:08-019256 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:08-019447 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:08-022155 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:08-022397 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:08-022596 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:08-022834 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:08-023042 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:45:08-023322 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (100 bytes)
Jul 07 20:45:08-023523 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:08-023703 cadet-con-8620 DEBUG last pid sent 13
Jul 07 20:45:08-023879 cadet-con-8620 DEBUG      ack recv 70
Jul 07 20:45:08-024053 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:08-024233 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:08-024482 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-024692 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-025263 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:45:08-025472 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:08-025716 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:08-025903 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 13
Jul 07 20:45:08-026085 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:08-026304 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 100 bytes
Jul 07 20:45:08-026523 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:08-026767 util-scheduler-8620 DEBUG Adding task: 725 / 0x4d5c9e8
Jul 07 20:45:08-026976 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:08-027184 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:08-027363 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:08-027542 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:08-027784 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-027983 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:45:08-028163 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:08-028366 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:08-028743 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:45:08-028990 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:08-029171 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:08-029391 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:08-029568 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:08-029793 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:08-029974 cadet-con-8620 DEBUG  ACK 73
Jul 07 20:45:08-030157 cadet-con-8620 DEBUG  last pid 9, last ack 72, qmax 11, q 0
Jul 07 20:45:08-030427 cadet-con-8620 INFO --> {               ACK} ( 73) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:08-030620 cadet-con-8620 DEBUG  ack 73
Jul 07 20:45:08-030800 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:08-031036 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-031246 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-031539 cadet-p2p-8620 INFO que {               ACK} ( 73) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:08-031739 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:08-031965 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:08-032149 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 13
Jul 07 20:45:08-032326 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:08-032545 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:08-032750 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:08-032929 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:08-033106 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:08-033393 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-033580 cadet-p2p-8620 DEBUG QQQ    payload , 73
Jul 07 20:45:08-033759 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:08-033996 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-034191 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:45:08-034370 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:08-034570 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:08-034785 util-scheduler-8620 DEBUG Adding task: 726 / 0x4662248
Jul 07 20:45:08-035069 util-scheduler-8620 DEBUG Checking readiness of task: 724 / 0x4d5e5d8
Jul 07 20:45:08-035286 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-035481 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-035673 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-035865 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-036060 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-036267 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-036460 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-036656 util-scheduler-8620 DEBUG Running task: 724 / 0x4d5e5d8
Jul 07 20:45:08-036844 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:08-037027 util-8620 DEBUG process_notify is running
Jul 07 20:45:08-037239 util-8620 DEBUG client_notify is running
Jul 07 20:45:08-037496 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:08-037714 util-scheduler-8620 DEBUG Adding task: 727 / 0x4d5e5d8
Jul 07 20:45:08-037939 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:08-038284 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:08-038487 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:08-038687 util-scheduler-8620 DEBUG Running task: 726 / 0x4662248
Jul 07 20:45:08-038880 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:08-039080 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:08-039299 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:08-039562 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:08-039814 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-040024 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-040208 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:08-040412 cadet-con-8620 DEBUG   ACK 71 (was 70)
Jul 07 20:45:08-040708 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-040962 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-041172 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-041382 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:08-041561 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:08-041771 util-scheduler-8620 DEBUG Adding task: 728 / 0x46620a0
Jul 07 20:45:08-041973 util-scheduler-8620 DEBUG Running task: 725 / 0x4d5c9e8
Jul 07 20:45:08-042193 util-scheduler-8620 DEBUG Adding task: 729 / 0x4d5c9e8
Jul 07 20:45:08-042418 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:08-042617 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:08-042817 util-scheduler-8620 DEBUG Adding task: 730 / 0x46620a0
Jul 07 20:45:08-043067 util-scheduler-8620 DEBUG Checking readiness of task: 730 / 0x46620a0
Jul 07 20:45:08-043262 util-scheduler-8620 DEBUG Checking readiness of task: 728 / 0x46620a0
Jul 07 20:45:08-043456 util-scheduler-8620 DEBUG Checking readiness of task: 727 / 0x4d5e5d8
Jul 07 20:45:08-043649 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-043842 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-044033 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-044225 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-044416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-044608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-044799 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-044991 util-scheduler-8620 DEBUG Running task: 727 / 0x4d5e5d8
Jul 07 20:45:08-045178 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:08-045395 util-8620 DEBUG process_notify is running
Jul 07 20:45:08-045568 util-8620 DEBUG client_notify is running
Jul 07 20:45:08-045784 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:45:08-046098 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:08-046311 util-scheduler-8620 DEBUG Running task: 728 / 0x46620a0
Jul 07 20:45:08-046720 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:08-046951 util-scheduler-8620 DEBUG Adding task: 731 / 0x4662248
Jul 07 20:45:08-047163 util-scheduler-8620 DEBUG Running task: 730 / 0x46620a0
Jul 07 20:45:08-047349 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:08-047541 util-8620 DEBUG process_notify is running
Jul 07 20:45:08-047713 util-8620 DEBUG client_notify is running
Jul 07 20:45:08-047907 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:08-048134 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:08-048327 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:08-048630 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:08-048882 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-049077 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-049290 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-049483 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-049674 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-049864 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-050055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-050246 util-scheduler-8620 DEBUG Running task: 731 / 0x4662248
Jul 07 20:45:08-050436 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:08-050633 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:08-050852 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:08-051097 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:08-051344 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-051552 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-051736 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:08-051911 cadet-con-8620 DEBUG   ACK 72 (was 71)
Jul 07 20:45:08-052149 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-052381 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-052589 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-052773 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:08-052974 util-scheduler-8620 DEBUG Adding task: 732 / 0x4662248
Jul 07 20:45:08-053237 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-053433 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-053626 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-053819 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-054009 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-054200 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-054391 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-054582 util-scheduler-8620 DEBUG Running task: 732 / 0x4662248
Jul 07 20:45:08-054773 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:08-054966 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:08-055596 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:08-055844 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:08-056085 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:08-056315 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-056525 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:08-056768 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-056977 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-057167 cadet-con-8620 DEBUG  PID 10 (expected 10+)
Jul 07 20:45:08-057374 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:08-057564 util-scheduler-8620 DEBUG Canceling task: 723 / 0x4d61c30
Jul 07 20:45:08-057786 util-scheduler-8620 DEBUG Adding task: 733 / 0x4d61c30
Jul 07 20:45:08-057968 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:08-058212 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:08-058425 util-scheduler-8620 DEBUG Adding task: 734 / 0x4d5e5d8
Jul 07 20:45:08-058625 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:08-058796 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:08-062639 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:08-063331 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:08-063526 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:08-066718 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:08-066920 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:45:08-067108 cadet-chn-8620 DEBUG   head 1, out!
Jul 07 20:45:08-067293 cadet-chn-8620 DEBUG free_sent_reliable 0 0
Jul 07 20:45:08-067480 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x552db98
Jul 07 20:45:08-067661 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:08-067834 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:08-068012 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:45:08-068220 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:08-068402 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:08-068588 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:08-068772 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:08-068952 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:08-069125 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:08-069371 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-069548 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:08-069783 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:08-069971 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:08-070152 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:45:08-070391 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-070575 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:08-070802 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:08-070979 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:08-071155 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:08-071328 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:08-071551 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:08-071731 cadet-con-8620 DEBUG  ACK 74
Jul 07 20:45:08-071913 cadet-con-8620 DEBUG  last pid 10, last ack 73, qmax 11, q 0
Jul 07 20:45:08-072096 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:45:08-072268 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:45:08-072457 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:45:08-072645 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:08-072828 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:08-073019 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:45:08-073220 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:08-073408 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:08-073587 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:08-073813 cadet-p2p-8620 DEBUG Checking 0x58c9fc0 towards HS92G30M (->KNAS)
Jul 07 20:45:08-074047 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:08-074232 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 13
Jul 07 20:45:08-074408 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:08-074672 cadet-con-8620 INFO --> {               ACK} ( 74) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:08-074865 cadet-con-8620 DEBUG  ack 74
Jul 07 20:45:08-075044 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:08-075281 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-075489 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-075784 cadet-p2p-8620 INFO que {               ACK} ( 74) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:08-075988 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:08-076214 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:08-076399 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 13
Jul 07 20:45:08-076576 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:08-076798 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:08-077003 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:08-077181 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:08-077383 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:08-077622 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-077807 cadet-p2p-8620 DEBUG QQQ    payload , 74
Jul 07 20:45:08-077994 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:08-078229 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-078424 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:45:08-078602 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:08-078802 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:08-078985 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:08-079195 util-scheduler-8620 DEBUG Adding task: 735 / 0x46620a0
Jul 07 20:45:08-079458 util-scheduler-8620 DEBUG Checking readiness of task: 735 / 0x46620a0
Jul 07 20:45:08-079652 util-scheduler-8620 DEBUG Checking readiness of task: 734 / 0x4d5e5d8
Jul 07 20:45:08-079847 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-080039 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-080230 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-080421 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-080613 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-080804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-080995 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-081209 util-scheduler-8620 DEBUG Running task: 734 / 0x4d5e5d8
Jul 07 20:45:08-081400 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:08-081579 util-8620 DEBUG process_notify is running
Jul 07 20:45:08-081753 util-8620 DEBUG client_notify is running
Jul 07 20:45:08-081973 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:08-082301 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:08-740364 util-scheduler-8620 DEBUG Checking readiness of task: 735 / 0x46620a0
Jul 07 20:45:08-740743 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-740940 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-741133 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-741354 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-741547 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-741738 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-741928 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-742122 util-scheduler-8620 DEBUG Running task: 695 / 0x4d63a48
Jul 07 20:45:08-742311 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:45:08-742602 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-742805 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:45:08-743009 cadet-chn-8620 DEBUG   using existing copy: 0x552db98 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:08-743199 cadet-chn-8620 DEBUG   new chq: 0x58d7a50
Jul 07 20:45:08-743406 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:08-743609 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:08-743874 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:08-744062 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:08-744244 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:08-744423 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:08-744593 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:08-744836 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:08-745011 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:08-745284 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:08-745471 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:08-745781 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:08-745953 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:08-746140 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:08-749716 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:08-750535 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:08-750713 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:08-750903 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:08-754104 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:08-754347 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:08-754531 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:08-754754 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:08-754950 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:08-755231 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:45:08-755441 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:08-755673 cadet-con-8620 DEBUG last pid sent 13
Jul 07 20:45:08-755848 cadet-con-8620 DEBUG      ack recv 72
Jul 07 20:45:08-756020 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:08-756203 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:45:08-756439 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:08-756649 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:08-756966 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:45:08-757167 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:08-757418 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:08-757602 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 13
Jul 07 20:45:08-757777 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:08-757981 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:08-758186 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:08-758361 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:08-758537 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:08-758777 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-758962 cadet-p2p-8620 DEBUG QQQ    payload , 74
Jul 07 20:45:08-759138 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:08-759371 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-759565 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:45:08-759741 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:08-759974 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:08-760166 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:08-760457 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:08-760660 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:08-760937 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:08-761159 util-scheduler-8620 DEBUG Adding task: 736 / 0x4d5e5d8
Jul 07 20:45:08-761462 util-scheduler-8620 DEBUG Checking readiness of task: 736 / 0x4d5e5d8
Jul 07 20:45:08-761658 util-scheduler-8620 DEBUG Checking readiness of task: 735 / 0x46620a0
Jul 07 20:45:08-761849 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:08-762039 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:08-762228 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:08-762417 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:08-762606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:08-762818 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:08-763008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:08-763216 util-scheduler-8620 DEBUG Running task: 736 / 0x4d5e5d8
Jul 07 20:45:08-763403 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:08-763582 util-8620 DEBUG process_notify is running
Jul 07 20:45:08-763754 util-8620 DEBUG client_notify is running
Jul 07 20:45:08-763981 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:08-764293 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:09-950302 util-scheduler-8620 DEBUG Checking readiness of task: 735 / 0x46620a0
Jul 07 20:45:09-950695 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:09-950894 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:09-951091 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:09-951286 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:09-951482 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:09-951677 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:09-951875 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:09-952077 util-scheduler-8620 DEBUG Running task: 735 / 0x46620a0
Jul 07 20:45:09-952511 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:09-952780 util-scheduler-8620 DEBUG Adding task: 737 / 0x4662248
Jul 07 20:45:09-953075 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:09-953306 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:09-953500 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:09-953692 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:09-953882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:09-954071 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:09-954260 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:09-954451 util-scheduler-8620 DEBUG Running task: 737 / 0x4662248
Jul 07 20:45:09-954643 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:09-954844 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:09-955076 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:09-955343 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:09-955598 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:09-955808 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:09-955992 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:09-956166 cadet-con-8620 DEBUG   ACK 73 (was 72)
Jul 07 20:45:09-956398 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:09-956629 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:09-956833 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:09-957015 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:09-957313 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:09-957549 util-scheduler-8620 DEBUG Adding task: 738 / 0x46620a0
Jul 07 20:45:10-109082 util-scheduler-8620 DEBUG Checking readiness of task: 738 / 0x46620a0
Jul 07 20:45:10-109473 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-109670 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-109861 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-110052 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-110272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-110462 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-110652 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-110846 util-scheduler-8620 DEBUG Running task: 738 / 0x46620a0
Jul 07 20:45:10-111267 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:10-111532 util-scheduler-8620 DEBUG Adding task: 739 / 0x4662248
Jul 07 20:45:10-111809 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-112000 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-112190 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-112379 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-112568 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-112757 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-112945 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-113134 util-scheduler-8620 DEBUG Running task: 739 / 0x4662248
Jul 07 20:45:10-113345 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:10-113544 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:10-113777 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:10-113983 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-114188 util-scheduler-8620 DEBUG Adding task: 740 / 0x46620a0
Jul 07 20:45:10-114374 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:10-114578 util-scheduler-8620 DEBUG Adding task: 741 / 0x46620a0
Jul 07 20:45:10-114820 util-scheduler-8620 DEBUG Checking readiness of task: 741 / 0x46620a0
Jul 07 20:45:10-115011 util-scheduler-8620 DEBUG Checking readiness of task: 740 / 0x46620a0
Jul 07 20:45:10-115202 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-115390 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-115578 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-115766 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-115955 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-116142 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-116331 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-116521 util-scheduler-8620 DEBUG Running task: 740 / 0x46620a0
Jul 07 20:45:10-116705 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-116883 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-117056 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-117263 util-scheduler-8620 DEBUG Canceling task: 729 / 0x4d5c9e8
Jul 07 20:45:10-117486 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:10-117706 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:10-117951 cadet-p2p-8620 DEBUG Checking 0x58d6d10 towards HS92G30M (->KNAS)
Jul 07 20:45:10-118192 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:10-118376 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:10-118573 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:10-118859 cadet-p2p-8620 INFO snd {               ACK} ( 74) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:10-119060 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:10-119277 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:10-119471 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:10-119649 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:10-119935 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:45:10-120110 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:10-120358 cadet-p2p-8620 DEBUG Checking 0x58c9fc0 towards HS92G30M (->KNAS)
Jul 07 20:45:10-120592 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-120787 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 13
Jul 07 20:45:10-120962 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-121212 cadet-p2p-8620 DEBUG Checking 0x58c9fc0 towards HS92G30M (->KNAS)
Jul 07 20:45:10-121444 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-121625 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 13
Jul 07 20:45:10-121817 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-121983 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:10-122191 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:10-122427 util-scheduler-8620 DEBUG Adding task: 742 / 0x4d5c9e8
Jul 07 20:45:10-122607 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:10-122799 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:10-123012 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:10-123186 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:10-123361 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:10-123600 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:10-123795 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:45:10-123987 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:10-124235 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:10-124428 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:10-124605 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:10-124802 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:10-125006 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:10-125207 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:10-125415 util-scheduler-8620 DEBUG Adding task: 743 / 0x4d5c9e8
Jul 07 20:45:10-125636 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:10-125862 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-126068 util-scheduler-8620 DEBUG Adding task: 744 / 0x46620a0
Jul 07 20:45:10-126270 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:10-127044 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-127263 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:10-127522 util-scheduler-8620 DEBUG Checking readiness of task: 744 / 0x46620a0
Jul 07 20:45:10-127716 util-scheduler-8620 DEBUG Checking readiness of task: 741 / 0x46620a0
Jul 07 20:45:10-127906 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-128095 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-128283 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-128473 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-128664 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-128852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-129040 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-129252 util-scheduler-8620 DEBUG Running task: 744 / 0x46620a0
Jul 07 20:45:10-129439 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-129627 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-129797 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-129976 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:10-130184 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:10-130374 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:10-130661 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-130956 util-scheduler-8620 DEBUG Running task: 742 / 0x4d5c9e8
Jul 07 20:45:10-131156 util-scheduler-8620 DEBUG Canceling task: 743 / 0x4d5c9e8
Jul 07 20:45:10-131392 util-scheduler-8620 DEBUG Adding task: 745 / 0x4d5c9e8
Jul 07 20:45:10-131615 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:10-131814 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-132016 util-scheduler-8620 DEBUG Adding task: 746 / 0x46620a0
Jul 07 20:45:10-132269 util-scheduler-8620 DEBUG Checking readiness of task: 746 / 0x46620a0
Jul 07 20:45:10-132465 util-scheduler-8620 DEBUG Checking readiness of task: 741 / 0x46620a0
Jul 07 20:45:10-132660 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-132852 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-133129 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-133350 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-133543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-133732 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-133921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-134112 util-scheduler-8620 DEBUG Running task: 746 / 0x46620a0
Jul 07 20:45:10-134297 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-134473 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-134663 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-134855 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:10-135048 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:10-135237 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:10-135520 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-426746 util-scheduler-8620 DEBUG Checking readiness of task: 741 / 0x46620a0
Jul 07 20:45:10-427125 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-427322 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-427515 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-427707 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-427899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-428089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-428279 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-428475 util-scheduler-8620 DEBUG Running task: 741 / 0x46620a0
Jul 07 20:45:10-428897 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:10-429153 util-scheduler-8620 DEBUG Adding task: 747 / 0x4662248
Jul 07 20:45:10-429455 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-429647 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-429837 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-430026 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-430215 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-430404 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-430592 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-430781 util-scheduler-8620 DEBUG Running task: 747 / 0x4662248
Jul 07 20:45:10-430972 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:10-431170 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:10-431433 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:10-431652 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-431860 util-scheduler-8620 DEBUG Adding task: 748 / 0x46620a0
Jul 07 20:45:10-432049 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:10-432260 util-scheduler-8620 DEBUG Adding task: 749 / 0x46620a0
Jul 07 20:45:10-432510 util-scheduler-8620 DEBUG Checking readiness of task: 749 / 0x46620a0
Jul 07 20:45:10-432704 util-scheduler-8620 DEBUG Checking readiness of task: 748 / 0x46620a0
Jul 07 20:45:10-432897 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-433087 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-433301 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-433491 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-433686 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-433877 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-434070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-434265 util-scheduler-8620 DEBUG Running task: 748 / 0x46620a0
Jul 07 20:45:10-434452 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-434633 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-434807 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-434998 util-scheduler-8620 DEBUG Canceling task: 745 / 0x4d5c9e8
Jul 07 20:45:10-435233 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:10-435453 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:10-435691 cadet-p2p-8620 DEBUG Checking 0x58c9fc0 towards HS92G30M (->KNAS)
Jul 07 20:45:10-435923 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-436105 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 13
Jul 07 20:45:10-436279 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-436500 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:10-436680 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:10-436855 cadet-p2p-8620 DEBUG   payload ID 14
Jul 07 20:45:10-437143 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 0) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:45:10-437362 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:10-437541 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:10-437729 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:10-437902 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:10-438070 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:10-438257 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:45:10-438445 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:45:10-438640 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:10-438868 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:10-439043 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:10-439214 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:10-439386 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:10-439583 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:10-439757 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:10-439930 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:10-440130 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:10-440309 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:10-440490 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:10-440685 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:10-440862 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:10-441031 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:10-441266 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:10-441440 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:10-441692 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:10-441876 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:10-442056 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:10-442241 util-scheduler-8620 DEBUG Canceling task: 696 / 0x4d61c30
Jul 07 20:45:10-442455 util-scheduler-8620 DEBUG Adding task: 750 / 0x4d61c30
Jul 07 20:45:10-442705 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:10-442883 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:10-443061 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 14
Jul 07 20:45:10-443232 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:10-443452 cadet-p2p-8620 DEBUG Checking 0x58e0578 towards HS92G30M (->KNAS)
Jul 07 20:45:10-443681 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-443861 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 14
Jul 07 20:45:10-444046 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-444273 cadet-p2p-8620 DEBUG Checking 0x58e0578 towards HS92G30M (->KNAS)
Jul 07 20:45:10-444502 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-444682 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 14
Jul 07 20:45:10-444853 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-445018 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:10-445247 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:45:10-445470 util-scheduler-8620 DEBUG Adding task: 751 / 0x4d5c9e8
Jul 07 20:45:10-445654 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:10-445834 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:10-446045 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:10-446227 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:10-446405 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:10-446659 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:10-446864 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:10-447048 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:10-447255 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:10-447467 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:45:10-447656 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:10-447876 util-scheduler-8620 DEBUG Adding task: 752 / 0x4d5c9e8
Jul 07 20:45:10-448124 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:10-448333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-448547 util-scheduler-8620 DEBUG Adding task: 753 / 0x46620a0
Jul 07 20:45:10-448764 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:10-449948 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-450199 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:10-450484 util-scheduler-8620 DEBUG Checking readiness of task: 753 / 0x46620a0
Jul 07 20:45:10-450692 util-scheduler-8620 DEBUG Checking readiness of task: 749 / 0x46620a0
Jul 07 20:45:10-450888 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-451085 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-451281 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-451477 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-451670 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-451862 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-452051 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-452244 util-scheduler-8620 DEBUG Running task: 753 / 0x46620a0
Jul 07 20:45:10-452506 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-452718 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-452895 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-453075 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:10-453302 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:10-453493 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:10-453797 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-454007 util-scheduler-8620 DEBUG Running task: 751 / 0x4d5c9e8
Jul 07 20:45:10-454203 util-scheduler-8620 DEBUG Canceling task: 752 / 0x4d5c9e8
Jul 07 20:45:10-454429 util-scheduler-8620 DEBUG Adding task: 754 / 0x4d5c9e8
Jul 07 20:45:10-454655 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:10-454854 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-455056 util-scheduler-8620 DEBUG Adding task: 755 / 0x46620a0
Jul 07 20:45:10-455305 util-scheduler-8620 DEBUG Checking readiness of task: 755 / 0x46620a0
Jul 07 20:45:10-455497 util-scheduler-8620 DEBUG Checking readiness of task: 749 / 0x46620a0
Jul 07 20:45:10-455687 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-455876 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-456065 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-456252 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-456441 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-456632 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-456820 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-457009 util-scheduler-8620 DEBUG Running task: 749 / 0x46620a0
Jul 07 20:45:10-457432 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:10-457664 util-scheduler-8620 DEBUG Adding task: 756 / 0x4662248
Jul 07 20:45:10-457873 util-scheduler-8620 DEBUG Running task: 755 / 0x46620a0
Jul 07 20:45:10-458258 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-458829 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-459003 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-459181 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:10-459372 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:10-459560 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:10-459856 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:10-460108 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-460300 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-460503 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-460693 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-460881 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-461070 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-461280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-461469 util-scheduler-8620 DEBUG Running task: 756 / 0x4662248
Jul 07 20:45:10-461659 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:10-461855 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:10-462074 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:10-462255 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:10-462460 util-scheduler-8620 DEBUG Adding task: 757 / 0x46620a0
Jul 07 20:45:10-462721 util-scheduler-8620 DEBUG Checking readiness of task: 757 / 0x46620a0
Jul 07 20:45:10-462920 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-463109 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-463296 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-463484 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-463672 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-463860 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-464048 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-464237 util-scheduler-8620 DEBUG Running task: 757 / 0x46620a0
Jul 07 20:45:10-464641 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:10-464883 util-scheduler-8620 DEBUG Adding task: 758 / 0x4662248
Jul 07 20:45:10-465149 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-465374 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-465569 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-465765 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-465956 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-466148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-466338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-466528 util-scheduler-8620 DEBUG Running task: 758 / 0x4662248
Jul 07 20:45:10-466720 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:10-466916 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:10-467143 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:10-467344 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:10-467558 util-scheduler-8620 DEBUG Adding task: 759 / 0x46620a0
Jul 07 20:45:10-467741 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:10-467941 util-scheduler-8620 DEBUG Adding task: 760 / 0x46620a0
Jul 07 20:45:10-468186 util-scheduler-8620 DEBUG Checking readiness of task: 760 / 0x46620a0
Jul 07 20:45:10-468377 util-scheduler-8620 DEBUG Checking readiness of task: 759 / 0x46620a0
Jul 07 20:45:10-468567 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:10-468756 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:10-468945 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:10-469133 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:10-469345 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:10-469534 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:10-469722 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:10-469913 util-scheduler-8620 DEBUG Running task: 759 / 0x46620a0
Jul 07 20:45:10-470097 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:10-470272 util-8620 DEBUG process_notify is running
Jul 07 20:45:10-470441 util-8620 DEBUG client_notify is running
Jul 07 20:45:10-470626 util-scheduler-8620 DEBUG Canceling task: 754 / 0x4d5c9e8
Jul 07 20:45:10-470859 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:45:10-471079 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:10-471323 cadet-p2p-8620 DEBUG Checking 0x58e0578 towards HS92G30M (->KNAS)
Jul 07 20:45:10-471555 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:10-471736 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 14
Jul 07 20:45:10-471910 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:10-472153 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:10-472330 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:45:10-472504 cadet-p2p-8620 DEBUG   payload ID 15
Jul 07 20:45:10-472788 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 156)
Jul 07 20:45:10-472982 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:10-473161 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:10-473370 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:10-473543 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:10-473711 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:10-473898 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:10-474074 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:45:10-474301 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 624 ms
Jul 07 20:45:10-474472 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:10-474676 cadet-chn-8620 DEBUG !! using delay 2499224 µs
Jul 07 20:45:10-474874 util-scheduler-8620 DEBUG Adding task: 761 / 0x4d63a48
Jul 07 20:45:10-475076 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:10-475306 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:10-475486 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:10-475658 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:10-475828 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:10-476023 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:10-476197 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:10-476371 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:10-476569 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:10-476750 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:10-476931 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:10-477110 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:10-477306 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:10-477476 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:10-477691 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:10-477863 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:10-478096 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:10-478284 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:10-478467 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:10-478658 util-scheduler-8620 DEBUG Canceling task: 750 / 0x4d61c30
Jul 07 20:45:10-478874 util-scheduler-8620 DEBUG Adding task: 762 / 0x4d61c30
Jul 07 20:45:10-479120 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:10-479300 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:10-479479 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 15
Jul 07 20:45:10-479671 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:10-479858 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:45:10-480065 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:10-480246 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:10-480420 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:10-480624 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:10-480838 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 156 bytes.
Jul 07 20:45:10-481024 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:45:10-481229 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:10-481424 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:45:10-482528 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:11-674584 util-scheduler-8620 DEBUG Checking readiness of task: 760 / 0x46620a0
Jul 07 20:45:11-674972 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:11-675169 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:11-675361 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:11-675582 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:11-675773 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:11-675962 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:11-676152 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:11-676345 util-scheduler-8620 DEBUG Running task: 697 / 0x4d64a70
Jul 07 20:45:11-676585 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:11-676834 cadet-tun-8620 DEBUG  kx started 45 s ago
Jul 07 20:45:11-677222 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:11-677430 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:11-677633 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:11-677869 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:11-678050 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:11-678271 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:11-678564 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:11-678762 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:11-679000 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:11-679208 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:11-679527 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:11-679728 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:11-679966 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:11-680150 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:11-680326 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:11-680534 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:45:11-680749 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:11-680975 util-scheduler-8620 DEBUG Adding task: 763 / 0x4d6ff98
Jul 07 20:45:11-681156 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:11-685136 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:11-685379 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:11-685571 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:11-685815 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:11-686013 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:11-686192 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:11-686392 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:11-686599 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:11-686917 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:11-687118 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:11-687290 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:11-687472 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:11-691069 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:11-692432 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:11-692617 cadet-tun-8620 DEBUG   e sending 3504134774
Jul 07 20:45:11-692830 cadet-tun-8620 DEBUG   e towards 712J
Jul 07 20:45:11-693032 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:11-693261 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:11-693492 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:11-693672 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:11-693892 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:11-694169 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:11-694367 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:11-694603 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:11-694811 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:11-695121 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:11-695344 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:11-695570 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:11-695753 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:11-695928 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:11-696133 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:11-696334 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:11-696509 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:11-696684 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:11-696924 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:11-697119 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:11-697322 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:11-697557 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:11-697749 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:11-697925 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:11-698123 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:11-698374 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:11-698591 util-scheduler-8620 DEBUG Adding task: 764 / 0x4d64a70
Jul 07 20:45:11-698861 util-scheduler-8620 DEBUG Checking readiness of task: 760 / 0x46620a0
Jul 07 20:45:11-699054 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:11-699245 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:11-699434 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:11-699623 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:11-699811 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:11-700000 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:11-700188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:11-700379 util-scheduler-8620 DEBUG Running task: 763 / 0x4d6ff98
Jul 07 20:45:11-700592 util-scheduler-8620 DEBUG Adding task: 765 / 0x4d6ff98
Jul 07 20:45:11-700815 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:11-701018 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:11-701250 util-scheduler-8620 DEBUG Adding task: 766 / 0x46620a0
Jul 07 20:45:11-701499 util-scheduler-8620 DEBUG Checking readiness of task: 766 / 0x46620a0
Jul 07 20:45:11-701692 util-scheduler-8620 DEBUG Checking readiness of task: 760 / 0x46620a0
Jul 07 20:45:11-701882 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:11-702071 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:11-702261 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:11-702451 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:11-702640 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:11-702829 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:11-703019 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:11-703211 util-scheduler-8620 DEBUG Running task: 766 / 0x46620a0
Jul 07 20:45:11-703396 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:11-703575 util-8620 DEBUG process_notify is running
Jul 07 20:45:11-703747 util-8620 DEBUG client_notify is running
Jul 07 20:45:11-703927 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:11-704122 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:11-704311 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:11-704575 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:12-003307 util-scheduler-8620 DEBUG Checking readiness of task: 760 / 0x46620a0
Jul 07 20:45:12-003720 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-003920 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-004116 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-004325 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-004518 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-004711 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-004903 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-005101 util-scheduler-8620 DEBUG Running task: 760 / 0x46620a0
Jul 07 20:45:12-005554 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:12-005815 util-scheduler-8620 DEBUG Adding task: 767 / 0x4662248
Jul 07 20:45:12-006096 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-006290 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-006482 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-006674 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-006870 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-007062 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-007254 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-007445 util-scheduler-8620 DEBUG Running task: 767 / 0x4662248
Jul 07 20:45:12-007639 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:12-007843 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:12-008097 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:12-008307 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:12-008516 util-scheduler-8620 DEBUG Adding task: 768 / 0x46620a0
Jul 07 20:45:12-008718 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:12-008926 util-scheduler-8620 DEBUG Adding task: 769 / 0x46620a0
Jul 07 20:45:12-009174 util-scheduler-8620 DEBUG Checking readiness of task: 769 / 0x46620a0
Jul 07 20:45:12-009765 util-scheduler-8620 DEBUG Checking readiness of task: 768 / 0x46620a0
Jul 07 20:45:12-009962 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-010154 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-010347 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-010539 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-010809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-011003 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-011195 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-011389 util-scheduler-8620 DEBUG Running task: 768 / 0x46620a0
Jul 07 20:45:12-011578 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:12-011758 util-8620 DEBUG process_notify is running
Jul 07 20:45:12-011932 util-8620 DEBUG client_notify is running
Jul 07 20:45:12-012123 util-scheduler-8620 DEBUG Canceling task: 765 / 0x4d6ff98
Jul 07 20:45:12-012352 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:12-012575 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:12-012816 cadet-p2p-8620 DEBUG Checking 0x58eb0d8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:12-013052 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:12-013257 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:12-013452 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:12-013739 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:12-013955 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:12-014139 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:12-014329 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:12-014520 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:12-014701 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:12-014886 util-scheduler-8620 DEBUG Canceling task: 721 / 0x4d707d0
Jul 07 20:45:12-015101 util-scheduler-8620 DEBUG Adding task: 770 / 0x4d707d0
Jul 07 20:45:12-015354 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:12-015527 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:12-015750 cadet-p2p-8620 DEBUG Checking 0x58f1ab8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:12-015989 cadet-p2p-8620 DEBUG Checking 0x58f1ab8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:12-016170 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:12-016378 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:12-016592 util-scheduler-8620 DEBUG Adding task: 771 / 0x4d6ff98
Jul 07 20:45:12-016774 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:12-016957 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:12-017171 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:12-017372 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:12-017549 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:12-017790 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:12-017987 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:12-018166 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:12-018367 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:12-018574 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:12-018758 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:12-018963 util-scheduler-8620 DEBUG Adding task: 772 / 0x4d6ff98
Jul 07 20:45:12-019184 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:12-019381 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:12-019585 util-scheduler-8620 DEBUG Adding task: 773 / 0x46620a0
Jul 07 20:45:12-019788 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:12-020608 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:12-020815 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:12-021069 util-scheduler-8620 DEBUG Checking readiness of task: 773 / 0x46620a0
Jul 07 20:45:12-021289 util-scheduler-8620 DEBUG Checking readiness of task: 769 / 0x46620a0
Jul 07 20:45:12-021482 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-021675 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-021868 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-022060 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-022252 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-022444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-022635 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-022828 util-scheduler-8620 DEBUG Running task: 773 / 0x46620a0
Jul 07 20:45:12-023015 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:12-023193 util-8620 DEBUG process_notify is running
Jul 07 20:45:12-023366 util-8620 DEBUG client_notify is running
Jul 07 20:45:12-023547 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:12-023745 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:12-023935 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:12-024227 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:12-024518 util-scheduler-8620 DEBUG Running task: 771 / 0x4d6ff98
Jul 07 20:45:12-024715 util-scheduler-8620 DEBUG Canceling task: 772 / 0x4d6ff98
Jul 07 20:45:12-024931 util-scheduler-8620 DEBUG Adding task: 774 / 0x4d6ff98
Jul 07 20:45:12-025150 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:12-025367 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:12-025568 util-scheduler-8620 DEBUG Adding task: 775 / 0x46620a0
Jul 07 20:45:12-025809 util-scheduler-8620 DEBUG Checking readiness of task: 775 / 0x46620a0
Jul 07 20:45:12-026003 util-scheduler-8620 DEBUG Checking readiness of task: 769 / 0x46620a0
Jul 07 20:45:12-026205 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-026397 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-026588 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-026780 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-026975 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-027166 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-027357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-027549 util-scheduler-8620 DEBUG Running task: 775 / 0x46620a0
Jul 07 20:45:12-027734 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:12-027911 util-8620 DEBUG process_notify is running
Jul 07 20:45:12-028082 util-8620 DEBUG client_notify is running
Jul 07 20:45:12-028260 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:12-028450 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:12-028639 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:12-028922 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:12-138792 util-scheduler-8620 DEBUG Checking readiness of task: 769 / 0x46620a0
Jul 07 20:45:12-139159 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-139355 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-139548 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-139739 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-139930 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-140120 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-140310 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-140505 util-scheduler-8620 DEBUG Running task: 769 / 0x46620a0
Jul 07 20:45:12-140926 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:12-141216 util-scheduler-8620 DEBUG Adding task: 776 / 0x4662248
Jul 07 20:45:12-141495 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-141688 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-141879 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-142069 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-142258 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-142449 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-142639 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-142828 util-scheduler-8620 DEBUG Running task: 776 / 0x4662248
Jul 07 20:45:12-143019 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:12-143219 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:12-143480 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:12-143688 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:12-143894 util-scheduler-8620 DEBUG Adding task: 777 / 0x46620a0
Jul 07 20:45:12-144081 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:12-144288 util-scheduler-8620 DEBUG Adding task: 778 / 0x46620a0
Jul 07 20:45:12-144531 util-scheduler-8620 DEBUG Checking readiness of task: 778 / 0x46620a0
Jul 07 20:45:12-144722 util-scheduler-8620 DEBUG Checking readiness of task: 777 / 0x46620a0
Jul 07 20:45:12-144914 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-145104 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-145834 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-146031 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-146223 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-146414 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-146688 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-146889 util-scheduler-8620 DEBUG Running task: 777 / 0x46620a0
Jul 07 20:45:12-147077 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:12-147256 util-8620 DEBUG process_notify is running
Jul 07 20:45:12-147428 util-8620 DEBUG client_notify is running
Jul 07 20:45:12-147617 util-scheduler-8620 DEBUG Canceling task: 774 / 0x4d6ff98
Jul 07 20:45:12-147860 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:12-148082 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:12-148323 cadet-p2p-8620 DEBUG Checking 0x58f1ab8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:12-148556 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:12-148733 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:12-148923 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:12-149230 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:12-149428 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:12-149608 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:12-149796 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:12-149984 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:12-150163 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:12-150348 util-scheduler-8620 DEBUG Canceling task: 770 / 0x4d707d0
Jul 07 20:45:12-150559 util-scheduler-8620 DEBUG Adding task: 779 / 0x4d707d0
Jul 07 20:45:12-150809 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:12-150980 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:12-151160 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:12-151359 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:12-151534 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:12-151708 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:12-151907 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:12-152110 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:12-152292 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:12-152471 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:12-152662 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:12-153893 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:12-209308 util-scheduler-8620 DEBUG Checking readiness of task: 778 / 0x46620a0
Jul 07 20:45:12-209655 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-209850 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-210042 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-210261 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-210452 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-210642 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-210832 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-211026 util-scheduler-8620 DEBUG Running task: 778 / 0x46620a0
Jul 07 20:45:12-211445 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:12-211695 util-scheduler-8620 DEBUG Adding task: 780 / 0x4662248
Jul 07 20:45:12-211966 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-212158 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-212349 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-212538 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-212727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-212916 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-213105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-213321 util-scheduler-8620 DEBUG Running task: 780 / 0x4662248
Jul 07 20:45:12-213513 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:12-213712 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:12-213957 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:12-214224 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:12-214479 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:12-214688 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:12-214871 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:12-215044 cadet-con-8620 DEBUG   ACK 74 (was 73)
Jul 07 20:45:12-215273 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:12-215502 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:12-215708 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:12-215890 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:12-216066 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:12-216276 util-scheduler-8620 DEBUG Adding task: 781 / 0x46620a0
Jul 07 20:45:12-975027 util-scheduler-8620 DEBUG Checking readiness of task: 781 / 0x46620a0
Jul 07 20:45:12-975409 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-975604 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-975796 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-975987 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-976177 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-976367 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-976557 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-976749 util-scheduler-8620 DEBUG Running task: 761 / 0x4d63a48
Jul 07 20:45:12-976934 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:45:12-977250 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:12-977452 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:45:12-977655 cadet-chn-8620 DEBUG   using existing copy: 0x552db98 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:12-977846 cadet-chn-8620 DEBUG   new chq: 0x58f7980
Jul 07 20:45:12-978056 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:12-978275 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:12-978464 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:12-978650 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:12-978836 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:12-979052 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:12-979230 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:12-979456 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:12-979635 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:12-979878 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:12-980067 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:12-980387 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:12-980565 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:12-980753 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:12-984552 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:12-985511 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:12-985690 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:12-985882 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:12-989074 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:12-989338 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:12-989521 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:12-989743 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:12-989940 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:12-990223 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:45:12-990422 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:12-990599 cadet-con-8620 DEBUG last pid sent 15
Jul 07 20:45:12-990772 cadet-con-8620 DEBUG      ack recv 74
Jul 07 20:45:12-990993 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:12-991171 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:12-991406 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:12-991614 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:12-991927 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:45:12-992127 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:12-992350 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:12-992533 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 15
Jul 07 20:45:12-992707 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:12-992912 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 156 bytes
Jul 07 20:45:12-993127 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:45:12-993387 util-scheduler-8620 DEBUG Adding task: 782 / 0x4d5c9e8
Jul 07 20:45:12-993577 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:12-993787 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:12-993967 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:12-994142 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:12-994385 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:12-994586 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:12-994769 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:12-995065 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:12-995347 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:12-995568 util-scheduler-8620 DEBUG Adding task: 783 / 0x4d5e5d8
Jul 07 20:45:12-995843 util-scheduler-8620 DEBUG Checking readiness of task: 783 / 0x4d5e5d8
Jul 07 20:45:12-996038 util-scheduler-8620 DEBUG Checking readiness of task: 781 / 0x46620a0
Jul 07 20:45:12-996228 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:12-996416 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:12-996605 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:12-996793 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:12-996982 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:12-997174 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:12-997415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:12-997609 util-scheduler-8620 DEBUG Running task: 783 / 0x4d5e5d8
Jul 07 20:45:12-997795 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:12-997974 util-8620 DEBUG process_notify is running
Jul 07 20:45:12-998145 util-8620 DEBUG client_notify is running
Jul 07 20:45:12-998373 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:12-998695 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:12-998907 util-scheduler-8620 DEBUG Running task: 782 / 0x4d5c9e8
Jul 07 20:45:12-999119 util-scheduler-8620 DEBUG Adding task: 784 / 0x4d5c9e8
Jul 07 20:45:12-999342 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:12-999539 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:12-999737 util-scheduler-8620 DEBUG Adding task: 785 / 0x46620a0
Jul 07 20:45:12-999978 util-scheduler-8620 DEBUG Checking readiness of task: 785 / 0x46620a0
Jul 07 20:45:13-000169 util-scheduler-8620 DEBUG Checking readiness of task: 781 / 0x46620a0
Jul 07 20:45:13-000362 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:13-000552 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:13-000742 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:13-000932 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:13-001121 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:13-001333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:13-001524 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:13-001715 util-scheduler-8620 DEBUG Running task: 785 / 0x46620a0
Jul 07 20:45:13-001901 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:13-002077 util-8620 DEBUG process_notify is running
Jul 07 20:45:13-002247 util-8620 DEBUG client_notify is running
Jul 07 20:45:13-002427 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:13-002624 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:13-002813 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:13-003120 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-004433 util-scheduler-8620 DEBUG Checking readiness of task: 781 / 0x46620a0
Jul 07 20:45:14-004817 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-005016 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-005237 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-005435 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-005628 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-005821 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-006028 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-006225 util-scheduler-8620 DEBUG Running task: 781 / 0x46620a0
Jul 07 20:45:14-006649 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-006910 util-scheduler-8620 DEBUG Adding task: 786 / 0x4662248
Jul 07 20:45:14-007190 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-007387 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-007579 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-007771 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-007963 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-008185 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-008377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-008569 util-scheduler-8620 DEBUG Running task: 786 / 0x4662248
Jul 07 20:45:14-008763 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:14-008965 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:14-009375 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:14-009649 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:14-009895 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:14-010128 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-010360 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:14-010608 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-010819 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:14-011009 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:14-011201 util-scheduler-8620 DEBUG Canceling task: 685 / 0x4d707d0
Jul 07 20:45:14-011427 util-scheduler-8620 DEBUG Adding task: 787 / 0x4d707d0
Jul 07 20:45:14-011610 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:14-011868 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:14-012085 util-scheduler-8620 DEBUG Adding task: 788 / 0x4d5e5d8
Jul 07 20:45:14-012269 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:14-012471 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:14-012659 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:14-012834 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:14-013001 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:14-016672 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:14-017558 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:14-017782 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:14-018080 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:14-018257 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:14-018444 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:14-022152 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:14-022747 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:14-022928 cadet-tun-8620 DEBUG   e sending 4068218752
Jul 07 20:45:14-023138 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:14-023343 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:14-023574 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:14-023756 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:14-023978 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:14-024257 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:14-024458 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:14-024695 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-024914 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:14-025252 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:14-025455 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:14-025681 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:14-025866 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:14-026045 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:14-026254 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 48 bytes
Jul 07 20:45:14-026472 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:14-026699 util-scheduler-8620 DEBUG Adding task: 789 / 0x4d6ff98
Jul 07 20:45:14-026882 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:14-027092 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:14-027269 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:14-027451 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:14-027715 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:14-027913 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:14-028093 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:14-028294 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:14-028479 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-028691 util-scheduler-8620 DEBUG Adding task: 790 / 0x46620a0
Jul 07 20:45:14-028962 util-scheduler-8620 DEBUG Checking readiness of task: 790 / 0x46620a0
Jul 07 20:45:14-029286 util-scheduler-8620 DEBUG Checking readiness of task: 788 / 0x4d5e5d8
Jul 07 20:45:14-029482 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-029674 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-029866 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-030058 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-030249 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-030440 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-030631 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-030826 util-scheduler-8620 DEBUG Running task: 788 / 0x4d5e5d8
Jul 07 20:45:14-031015 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:14-031196 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-031369 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-031598 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:14-031901 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:14-032118 util-scheduler-8620 DEBUG Running task: 790 / 0x46620a0
Jul 07 20:45:14-032523 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-032753 util-scheduler-8620 DEBUG Adding task: 791 / 0x4662248
Jul 07 20:45:14-032975 util-scheduler-8620 DEBUG Running task: 789 / 0x4d6ff98
Jul 07 20:45:14-033185 util-scheduler-8620 DEBUG Adding task: 792 / 0x4d6ff98
Jul 07 20:45:14-033444 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:14-033649 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-033853 util-scheduler-8620 DEBUG Adding task: 793 / 0x46620a0
Jul 07 20:45:14-034095 util-scheduler-8620 DEBUG Checking readiness of task: 793 / 0x46620a0
Jul 07 20:45:14-034289 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-034481 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-034673 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-034864 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-035055 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-035246 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-035436 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-035628 util-scheduler-8620 DEBUG Running task: 793 / 0x46620a0
Jul 07 20:45:14-035814 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-035992 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-036162 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-036343 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:14-036540 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:14-036730 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:14-037023 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-037255 util-scheduler-8620 DEBUG Running task: 791 / 0x4662248
Jul 07 20:45:14-037469 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:14-037667 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:14-037885 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:14-038085 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-038284 util-scheduler-8620 DEBUG Adding task: 794 / 0x46620a0
Jul 07 20:45:14-038469 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-038669 util-scheduler-8620 DEBUG Adding task: 795 / 0x46620a0
Jul 07 20:45:14-038911 util-scheduler-8620 DEBUG Checking readiness of task: 795 / 0x46620a0
Jul 07 20:45:14-039104 util-scheduler-8620 DEBUG Checking readiness of task: 794 / 0x46620a0
Jul 07 20:45:14-039298 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-039490 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-039680 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-039871 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-040061 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-040252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-040442 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-040635 util-scheduler-8620 DEBUG Running task: 794 / 0x46620a0
Jul 07 20:45:14-040821 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-040998 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-041276 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-041465 util-scheduler-8620 DEBUG Canceling task: 784 / 0x4d5c9e8
Jul 07 20:45:14-041688 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 156 bytes.
Jul 07 20:45:14-041906 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:14-042140 cadet-p2p-8620 DEBUG Checking 0x59004c0 towards HS92G30M (->KNAS)
Jul 07 20:45:14-042374 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:14-042558 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 15
Jul 07 20:45:14-042734 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:14-043017 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:14-043197 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:45:14-043375 cadet-p2p-8620 DEBUG   payload ID 16
Jul 07 20:45:14-043661 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 156)
Jul 07 20:45:14-043859 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:14-044040 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:14-044230 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:14-044407 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:14-044578 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:14-044767 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:14-044947 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:45:14-045178 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 624 ms
Jul 07 20:45:14-045379 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:14-045586 cadet-chn-8620 DEBUG !! using delay 2499224 µs
Jul 07 20:45:14-045785 util-scheduler-8620 DEBUG Adding task: 796 / 0x4d63a48
Jul 07 20:45:14-045990 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:14-046222 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:14-046399 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:14-046573 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:14-046746 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:14-046945 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:14-047122 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:14-047298 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:14-047504 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:14-047684 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:14-047886 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:14-048069 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:14-048247 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:14-048418 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:14-048636 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:14-048809 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:14-049044 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:14-049253 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:14-049437 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:14-049623 util-scheduler-8620 DEBUG Canceling task: 762 / 0x4d61c30
Jul 07 20:45:14-049836 util-scheduler-8620 DEBUG Adding task: 797 / 0x4d61c30
Jul 07 20:45:14-050083 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:14-050265 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:14-050445 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 16
Jul 07 20:45:14-050620 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:14-050804 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:45:14-051005 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:14-051181 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:14-051356 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:14-051556 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:14-051773 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 156 bytes.
Jul 07 20:45:14-051959 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:45:14-052139 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:14-052535 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:45:14-053364 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-288047 util-scheduler-8620 DEBUG Checking readiness of task: 795 / 0x46620a0
Jul 07 20:45:14-288401 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-288598 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-288790 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-288981 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-289172 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-289388 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-289579 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-289789 util-scheduler-8620 DEBUG Running task: 795 / 0x46620a0
Jul 07 20:45:14-290208 util-8620 DEBUG receive_ready read 348/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-290463 util-scheduler-8620 DEBUG Adding task: 798 / 0x4662248
Jul 07 20:45:14-290738 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-290930 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-291121 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-291310 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-291500 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-291689 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-291878 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-292068 util-scheduler-8620 DEBUG Running task: 798 / 0x4662248
Jul 07 20:45:14-292259 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:14-292462 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:14-292688 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:14-292979 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:14-296336 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:14-296576 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-296786 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:14-297033 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-297266 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:14-297459 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:14-297650 util-scheduler-8620 DEBUG Canceling task: 787 / 0x4d707d0
Jul 07 20:45:14-297876 util-scheduler-8620 DEBUG Adding task: 799 / 0x4d707d0
Jul 07 20:45:14-298057 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:14-298319 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:14-298536 util-scheduler-8620 DEBUG Adding task: 800 / 0x4d5e5d8
Jul 07 20:45:14-298719 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:14-298940 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:14-929710 util-scheduler-8620 DEBUG Adding task: 801 / 0x4662248
Jul 07 20:45:14-930168 util-scheduler-8620 DEBUG Checking readiness of task: 800 / 0x4d5e5d8
Jul 07 20:45:14-930371 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-930563 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-930753 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-930944 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-931144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-931334 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-931524 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-931719 util-scheduler-8620 DEBUG Running task: 800 / 0x4d5e5d8
Jul 07 20:45:14-931907 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:14-932090 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-932262 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-932500 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:14-932827 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:14-933040 util-scheduler-8620 DEBUG Running task: 801 / 0x4662248
Jul 07 20:45:14-933255 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:14-933456 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:14-933688 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:14-933952 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:14-934194 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:14-934422 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-934716 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:14-934965 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-935174 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:14-935361 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:14-935550 util-scheduler-8620 DEBUG Canceling task: 799 / 0x4d707d0
Jul 07 20:45:14-935773 util-scheduler-8620 DEBUG Adding task: 802 / 0x4d707d0
Jul 07 20:45:14-935952 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:14-936204 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:14-936421 util-scheduler-8620 DEBUG Adding task: 803 / 0x4d5e5d8
Jul 07 20:45:14-936603 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:14-936800 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:14-936986 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:14-937158 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:14-937349 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:14-940904 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:14-942300 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:14-942551 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:14-942849 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:14-943024 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:14-943210 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:14-946458 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:14-947063 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:14-947285 cadet-tun-8620 DEBUG   e sending 999275849
Jul 07 20:45:14-947494 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:14-947700 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:14-947929 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:14-948109 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:14-948330 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:14-948611 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:14-948808 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:14-949043 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:14-949274 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:14-949585 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:14-949784 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:14-950009 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:14-950192 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:14-950367 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:14-950570 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:14-950773 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:14-950948 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:14-951122 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:14-951360 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:14-951555 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:14-951733 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:14-951967 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:14-952159 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:14-952334 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:14-952532 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:14-952716 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-952931 util-scheduler-8620 DEBUG Adding task: 804 / 0x46620a0
Jul 07 20:45:14-953221 util-scheduler-8620 DEBUG Checking readiness of task: 804 / 0x46620a0
Jul 07 20:45:14-953420 util-scheduler-8620 DEBUG Checking readiness of task: 803 / 0x4d5e5d8
Jul 07 20:45:14-953612 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-953801 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-953991 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-954190 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-954379 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-954568 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-954756 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-954947 util-scheduler-8620 DEBUG Running task: 803 / 0x4d5e5d8
Jul 07 20:45:14-955133 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:14-955309 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-955480 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-955702 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:14-956018 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:14-956230 util-scheduler-8620 DEBUG Running task: 804 / 0x46620a0
Jul 07 20:45:14-956656 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-956894 util-scheduler-8620 DEBUG Adding task: 805 / 0x4662248
Jul 07 20:45:14-957144 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-957443 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-957640 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-957830 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-958020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-958211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-958400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-958590 util-scheduler-8620 DEBUG Running task: 805 / 0x4662248
Jul 07 20:45:14-958781 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:14-958975 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:14-959191 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:14-959394 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-959595 util-scheduler-8620 DEBUG Adding task: 806 / 0x46620a0
Jul 07 20:45:14-959779 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-959975 util-scheduler-8620 DEBUG Adding task: 807 / 0x46620a0
Jul 07 20:45:14-960214 util-scheduler-8620 DEBUG Checking readiness of task: 807 / 0x46620a0
Jul 07 20:45:14-960405 util-scheduler-8620 DEBUG Checking readiness of task: 806 / 0x46620a0
Jul 07 20:45:14-960596 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-960785 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-960974 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-961162 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-961376 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-961564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-961753 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-961943 util-scheduler-8620 DEBUG Running task: 806 / 0x46620a0
Jul 07 20:45:14-962127 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-962301 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-962470 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-962657 util-scheduler-8620 DEBUG Canceling task: 792 / 0x4d6ff98
Jul 07 20:45:14-962877 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:14-963095 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:14-963326 cadet-p2p-8620 DEBUG Checking 0x590e358 towards CMHCKRVP (->V8XX)
Jul 07 20:45:14-963558 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:14-963736 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:14-963923 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:14-964215 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:14-964411 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:14-964602 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:14-964790 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:14-964979 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:14-965158 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:14-965366 util-scheduler-8620 DEBUG Canceling task: 779 / 0x4d707d0
Jul 07 20:45:14-965577 util-scheduler-8620 DEBUG Adding task: 808 / 0x4d707d0
Jul 07 20:45:14-965827 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:14-965998 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:14-966219 cadet-p2p-8620 DEBUG Checking 0x5b608d8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:14-966473 cadet-p2p-8620 DEBUG Checking 0x5b608d8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:14-966652 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:14-966859 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:14-967070 util-scheduler-8620 DEBUG Adding task: 809 / 0x4d6ff98
Jul 07 20:45:14-967249 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:14-967426 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:14-967626 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:14-967801 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:14-967974 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:14-968210 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:14-968404 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:14-968580 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:14-968777 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:14-968981 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:14-969163 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:14-969392 util-scheduler-8620 DEBUG Adding task: 810 / 0x4d6ff98
Jul 07 20:45:14-969611 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:14-969806 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-970007 util-scheduler-8620 DEBUG Adding task: 811 / 0x46620a0
Jul 07 20:45:14-970205 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:14-971245 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-971583 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:14-971838 util-scheduler-8620 DEBUG Checking readiness of task: 811 / 0x46620a0
Jul 07 20:45:14-972032 util-scheduler-8620 DEBUG Checking readiness of task: 807 / 0x46620a0
Jul 07 20:45:14-972223 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-972412 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-972602 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-972792 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-972982 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-973171 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-973391 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-973583 util-scheduler-8620 DEBUG Running task: 811 / 0x46620a0
Jul 07 20:45:14-973767 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-973944 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-974114 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-974293 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:14-974487 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:14-974676 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:14-974984 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-975193 util-scheduler-8620 DEBUG Running task: 809 / 0x4d6ff98
Jul 07 20:45:14-975386 util-scheduler-8620 DEBUG Canceling task: 810 / 0x4d6ff98
Jul 07 20:45:14-975599 util-scheduler-8620 DEBUG Adding task: 812 / 0x4d6ff98
Jul 07 20:45:14-975816 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:14-976010 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-976208 util-scheduler-8620 DEBUG Adding task: 813 / 0x46620a0
Jul 07 20:45:14-976445 util-scheduler-8620 DEBUG Checking readiness of task: 813 / 0x46620a0
Jul 07 20:45:14-976637 util-scheduler-8620 DEBUG Checking readiness of task: 807 / 0x46620a0
Jul 07 20:45:14-976827 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-977032 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-977245 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-977436 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-977629 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-977817 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-978006 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-978196 util-scheduler-8620 DEBUG Running task: 807 / 0x46620a0
Jul 07 20:45:14-978598 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-978823 util-scheduler-8620 DEBUG Adding task: 814 / 0x4662248
Jul 07 20:45:14-979033 util-scheduler-8620 DEBUG Running task: 813 / 0x46620a0
Jul 07 20:45:14-979217 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-979391 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-979560 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-979736 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:14-979925 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:14-980113 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:14-980408 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:14-980655 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-980846 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-981036 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-981242 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-981433 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-981623 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-981811 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-982001 util-scheduler-8620 DEBUG Running task: 814 / 0x4662248
Jul 07 20:45:14-982189 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:14-982382 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:14-982594 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:14-982775 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-982975 util-scheduler-8620 DEBUG Adding task: 815 / 0x46620a0
Jul 07 20:45:14-983348 util-scheduler-8620 DEBUG Checking readiness of task: 815 / 0x46620a0
Jul 07 20:45:14-983544 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-983737 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-983938 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-984128 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-984318 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-984507 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-984697 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-984887 util-scheduler-8620 DEBUG Running task: 815 / 0x46620a0
Jul 07 20:45:14-985316 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:14-985538 util-scheduler-8620 DEBUG Adding task: 816 / 0x4662248
Jul 07 20:45:14-985785 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-985977 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-986167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-986371 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-986562 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-986751 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-986940 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-987140 util-scheduler-8620 DEBUG Running task: 816 / 0x4662248
Jul 07 20:45:14-987330 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:14-987520 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:14-987734 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:14-987929 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:14-988125 util-scheduler-8620 DEBUG Adding task: 817 / 0x46620a0
Jul 07 20:45:14-988308 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:14-988504 util-scheduler-8620 DEBUG Adding task: 818 / 0x46620a0
Jul 07 20:45:14-988741 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:14-988932 util-scheduler-8620 DEBUG Checking readiness of task: 817 / 0x46620a0
Jul 07 20:45:14-989123 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:14-989336 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:14-989526 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:14-989715 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:14-989903 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:14-990092 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:14-990280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:14-990470 util-scheduler-8620 DEBUG Running task: 817 / 0x46620a0
Jul 07 20:45:14-990654 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:14-990829 util-8620 DEBUG process_notify is running
Jul 07 20:45:14-990998 util-8620 DEBUG client_notify is running
Jul 07 20:45:14-991179 util-scheduler-8620 DEBUG Canceling task: 812 / 0x4d6ff98
Jul 07 20:45:14-991397 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:14-991610 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:14-991839 cadet-p2p-8620 DEBUG Checking 0x5b608d8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:14-992069 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:14-992245 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:14-992430 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:14-992704 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:14-992897 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:14-993074 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:14-993282 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:14-993470 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:14-993655 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:14-993839 util-scheduler-8620 DEBUG Canceling task: 808 / 0x4d707d0
Jul 07 20:45:14-994047 util-scheduler-8620 DEBUG Adding task: 819 / 0x4d707d0
Jul 07 20:45:14-994288 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:14-994459 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:14-994637 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:14-994835 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:14-995009 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:14-995182 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:14-995379 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:14-995582 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:14-995764 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:14-995941 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:14-996144 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:14-997483 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:16-546724 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-547102 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-547297 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-547489 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-547681 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-547871 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-548065 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-548255 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-548448 util-scheduler-8620 DEBUG Running task: 796 / 0x4d63a48
Jul 07 20:45:16-548636 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:45:16-548929 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:16-549132 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:45:16-549361 cadet-chn-8620 DEBUG   using existing copy: 0x552db98 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:16-549551 cadet-chn-8620 DEBUG   new chq: 0x5b65918
Jul 07 20:45:16-549759 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:16-549962 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:16-550143 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:16-550327 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:16-550507 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:16-550685 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:16-550855 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:16-551071 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:16-551244 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:16-551482 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:16-551667 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:16-551978 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:16-552150 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:16-552334 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:16-556023 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:16-557386 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:16-557569 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:16-557759 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:16-560449 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:16-560688 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:16-560871 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:16-561094 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:16-561311 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:16-561591 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (156 bytes)
Jul 07 20:45:16-561791 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:16-561968 cadet-con-8620 DEBUG last pid sent 16
Jul 07 20:45:16-562142 cadet-con-8620 DEBUG      ack recv 74
Jul 07 20:45:16-562313 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:16-562491 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:16-562737 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:16-562945 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:16-563273 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 156)
Jul 07 20:45:16-563475 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:16-563702 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:16-564042 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 16
Jul 07 20:45:16-564451 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:16-564709 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 156 bytes
Jul 07 20:45:16-564927 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `KNAS'
Jul 07 20:45:16-565157 util-scheduler-8620 DEBUG Adding task: 820 / 0x4d5c9e8
Jul 07 20:45:16-565365 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:16-565571 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:16-565747 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:16-565922 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:16-566161 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:16-566355 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:45:16-566532 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:45:16-566730 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:16-567003 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:16-567221 util-scheduler-8620 DEBUG Adding task: 821 / 0x4d5e5d8
Jul 07 20:45:16-567493 util-scheduler-8620 DEBUG Checking readiness of task: 821 / 0x4d5e5d8
Jul 07 20:45:16-567688 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-567879 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-568071 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-568261 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-568451 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-568640 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-568829 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-569018 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-569235 util-scheduler-8620 DEBUG Running task: 821 / 0x4d5e5d8
Jul 07 20:45:16-569423 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:16-569602 util-8620 DEBUG process_notify is running
Jul 07 20:45:16-569775 util-8620 DEBUG client_notify is running
Jul 07 20:45:16-570002 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:16-570309 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:16-570522 util-scheduler-8620 DEBUG Running task: 820 / 0x4d5c9e8
Jul 07 20:45:16-570867 util-scheduler-8620 DEBUG Adding task: 822 / 0x4d5c9e8
Jul 07 20:45:16-571094 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:16-571295 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:16-571496 util-scheduler-8620 DEBUG Adding task: 823 / 0x46620a0
Jul 07 20:45:16-571739 util-scheduler-8620 DEBUG Checking readiness of task: 823 / 0x46620a0
Jul 07 20:45:16-571932 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-572123 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-572312 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-572502 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-572691 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-572879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-573068 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-573281 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-573473 util-scheduler-8620 DEBUG Running task: 823 / 0x46620a0
Jul 07 20:45:16-573658 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:16-573833 util-8620 DEBUG process_notify is running
Jul 07 20:45:16-574003 util-8620 DEBUG client_notify is running
Jul 07 20:45:16-574198 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:16-574394 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:16-574582 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:16-574890 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:16-698885 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-699276 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-699473 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-699666 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-699859 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-700050 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-700240 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-700433 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-700628 util-scheduler-8620 DEBUG Running task: 764 / 0x4d64a70
Jul 07 20:45:16-700870 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:16-701119 cadet-tun-8620 DEBUG  kx started 50 s ago
Jul 07 20:45:16-701356 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:16-701559 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:16-701763 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:16-701998 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:16-702178 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:16-702399 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:16-702693 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:16-702890 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:16-703196 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:16-703405 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:16-703723 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:16-703925 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:16-704151 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:16-704333 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:16-704510 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:16-704717 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:45:16-704933 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:16-705157 util-scheduler-8620 DEBUG Adding task: 824 / 0x4d6ff98
Jul 07 20:45:16-706743 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:16-706988 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:16-707166 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:16-707342 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:16-707583 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:16-707779 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:16-707957 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:16-708156 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:16-708361 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:16-708672 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:16-708873 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:16-709044 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:16-709256 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:16-713361 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:16-714167 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:16-714348 cadet-tun-8620 DEBUG   e sending 3133019952
Jul 07 20:45:16-714557 cadet-tun-8620 DEBUG   e towards 23X4
Jul 07 20:45:16-714758 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:16-714984 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:16-715214 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:16-715392 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:16-715612 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:16-715888 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:16-716086 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:16-716320 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:16-716528 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:16-716837 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:16-717035 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:16-717320 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:16-717505 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:16-717681 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:16-717885 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:16-718087 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:16-718262 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:16-718436 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:16-718683 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:16-718878 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:16-719054 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:16-719289 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:16-719481 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:16-719657 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:16-719854 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:16-720103 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:16-720310 util-scheduler-8620 DEBUG Adding task: 825 / 0x4d64a70
Jul 07 20:45:16-720583 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-720777 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-720967 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-721156 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-721370 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-721559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-721748 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-721937 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-722127 util-scheduler-8620 DEBUG Running task: 824 / 0x4d6ff98
Jul 07 20:45:16-722337 util-scheduler-8620 DEBUG Adding task: 826 / 0x4d6ff98
Jul 07 20:45:16-722558 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:16-722761 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:16-722968 util-scheduler-8620 DEBUG Adding task: 827 / 0x46620a0
Jul 07 20:45:16-723212 util-scheduler-8620 DEBUG Checking readiness of task: 827 / 0x46620a0
Jul 07 20:45:16-723404 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:16-723594 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:16-723784 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:16-723973 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:16-724162 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:16-724351 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:16-724540 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:16-724728 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:16-724937 util-scheduler-8620 DEBUG Running task: 827 / 0x46620a0
Jul 07 20:45:16-725124 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:16-725329 util-8620 DEBUG process_notify is running
Jul 07 20:45:16-725500 util-8620 DEBUG client_notify is running
Jul 07 20:45:16-725679 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:16-725873 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:16-726064 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:16-726407 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:17-053685 util-scheduler-8620 DEBUG Checking readiness of task: 818 / 0x46620a0
Jul 07 20:45:17-054105 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-054307 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-054502 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-054696 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-054888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-055081 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-055273 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-055472 util-scheduler-8620 DEBUG Running task: 818 / 0x46620a0
Jul 07 20:45:17-055897 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:17-056178 util-scheduler-8620 DEBUG Adding task: 828 / 0x4662248
Jul 07 20:45:17-056457 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-056651 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-056843 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-057034 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-057255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-057541 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-057736 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-057930 util-scheduler-8620 DEBUG Running task: 828 / 0x4662248
Jul 07 20:45:17-058125 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:17-058330 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:17-058563 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:17-058830 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:17-059088 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-059299 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-059485 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:17-059661 cadet-con-8620 DEBUG   ACK 75 (was 74)
Jul 07 20:45:17-059893 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-060126 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-060334 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-060522 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:17-060729 util-scheduler-8620 DEBUG Adding task: 829 / 0x4662248
Jul 07 20:45:17-060971 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-061164 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-061384 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-061576 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-061768 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-061958 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-062162 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-062384 util-scheduler-8620 DEBUG Running task: 829 / 0x4662248
Jul 07 20:45:17-062577 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:17-062773 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:17-062989 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:17-063234 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:17-063471 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:17-063700 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-063909 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:17-064151 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-064369 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-064558 cadet-con-8620 DEBUG  PID 11 (expected 11+)
Jul 07 20:45:17-064741 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:17-064930 util-scheduler-8620 DEBUG Canceling task: 733 / 0x4d61c30
Jul 07 20:45:17-065153 util-scheduler-8620 DEBUG Adding task: 830 / 0x4d61c30
Jul 07 20:45:17-065382 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:17-065644 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:17-065863 util-scheduler-8620 DEBUG Adding task: 831 / 0x4d5e5d8
Jul 07 20:45:17-066049 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:17-066218 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:17-069768 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:17-070549 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:17-070746 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:17-074041 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:17-074250 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:45:17-074686 cadet-chn-8620 DEBUG   id 1
Jul 07 20:45:17-075029 cadet-chn-8620 DEBUG !!! Freeing 1
Jul 07 20:45:17-075383 cadet-chn-8620 INFO !!!  took 3030092 µs, new delay 3030092 µs
Jul 07 20:45:17-075852 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:45:17-076049 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:45:17-076240 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:17-076421 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:17-076613 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:45:17-076822 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:17-076997 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:17-077215 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:17-077399 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:45:17-077626 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 925 ms
Jul 07 20:45:17-077811 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:17-078017 cadet-chn-8620 DEBUG !! using delay 3701864 µs
Jul 07 20:45:17-078225 util-scheduler-8620 DEBUG Adding task: 832 / 0x4d63a48
Jul 07 20:45:17-078430 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:17-078616 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:17-078799 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 16
Jul 07 20:45:17-078976 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:17-079366 core-api-8620 DEBUG Aborting transmission request to core for 156 bytes to `KNAS'
Jul 07 20:45:17-080045 cadet-chn-8620 DEBUG  COPYFREE 0x552db98
Jul 07 20:45:17-080240 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:17-080510 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:45:17-080720 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:17-080905 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:17-081090 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:17-081300 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:17-081480 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:17-081652 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:17-081873 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-082070 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:17-082310 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:17-082497 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:17-082681 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:45:17-082911 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-083093 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:17-083278 util-scheduler-8620 DEBUG Canceling task: 832 / 0x4d63a48
Jul 07 20:45:17-083523 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:17-083701 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:17-083878 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:17-084051 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:17-084273 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:17-084452 cadet-con-8620 DEBUG  ACK 75
Jul 07 20:45:17-084634 cadet-con-8620 DEBUG  last pid 11, last ack 74, qmax 11, q 0
Jul 07 20:45:17-084918 cadet-con-8620 INFO --> {               ACK} ( 75) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:17-085111 cadet-con-8620 DEBUG  ack 75
Jul 07 20:45:17-085316 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:17-085554 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-085763 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-086060 cadet-p2p-8620 INFO que {               ACK} ( 75) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:17-086261 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:17-086488 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:17-086673 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:17-086850 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:17-087058 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:45:17-087274 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:45:17-087492 util-scheduler-8620 DEBUG Adding task: 833 / 0x4d5c9e8
Jul 07 20:45:17-087675 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:17-087882 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:17-088061 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:17-088239 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:17-088479 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-088665 cadet-p2p-8620 DEBUG QQQ    payload , 75
Jul 07 20:45:17-088843 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:17-089045 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:17-089253 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:17-089470 util-scheduler-8620 DEBUG Adding task: 834 / 0x46620a0
Jul 07 20:45:17-089751 util-scheduler-8620 DEBUG Checking readiness of task: 834 / 0x46620a0
Jul 07 20:45:17-089950 util-scheduler-8620 DEBUG Checking readiness of task: 831 / 0x4d5e5d8
Jul 07 20:45:17-090144 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-090338 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-090533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-090726 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-090919 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-091111 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-091303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-091499 util-scheduler-8620 DEBUG Running task: 831 / 0x4d5e5d8
Jul 07 20:45:17-091688 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:17-091869 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-092044 util-8620 DEBUG client_notify is running
Jul 07 20:45:17-092275 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:17-092644 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:17-092860 util-scheduler-8620 DEBUG Running task: 834 / 0x46620a0
Jul 07 20:45:17-093290 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:17-093532 util-scheduler-8620 DEBUG Adding task: 835 / 0x4662248
Jul 07 20:45:17-093743 util-scheduler-8620 DEBUG Running task: 833 / 0x4d5c9e8
Jul 07 20:45:17-093938 util-scheduler-8620 DEBUG Canceling task: 822 / 0x4d5c9e8
Jul 07 20:45:17-094154 util-scheduler-8620 DEBUG Adding task: 836 / 0x4d5c9e8
Jul 07 20:45:17-094380 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:17-094650 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:17-094858 util-scheduler-8620 DEBUG Adding task: 837 / 0x46620a0
Jul 07 20:45:17-095101 util-scheduler-8620 DEBUG Checking readiness of task: 837 / 0x46620a0
Jul 07 20:45:17-095296 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-095489 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-095680 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-095872 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-096064 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-096255 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-096446 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-096639 util-scheduler-8620 DEBUG Running task: 837 / 0x46620a0
Jul 07 20:45:17-096825 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:17-097002 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-097173 util-8620 DEBUG client_notify is running
Jul 07 20:45:17-097379 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:17-097576 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:17-097766 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:17-098076 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:17-098285 util-scheduler-8620 DEBUG Running task: 835 / 0x4662248
Jul 07 20:45:17-098478 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:45:17-098677 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:45:17-098895 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `KNAS'
Jul 07 20:45:17-099146 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:17-099385 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:17-099614 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-099823 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:17-100067 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-100274 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-100464 cadet-con-8620 DEBUG  PID 12 (expected 12+)
Jul 07 20:45:17-100644 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:17-100828 util-scheduler-8620 DEBUG Canceling task: 830 / 0x4d61c30
Jul 07 20:45:17-101162 util-scheduler-8620 DEBUG Adding task: 838 / 0x4d61c30
Jul 07 20:45:17-101389 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:17-101649 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:17-101859 util-scheduler-8620 DEBUG Adding task: 839 / 0x4d5e5d8
Jul 07 20:45:17-102043 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:17-102210 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:17-105484 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:17-106669 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:17-106863 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:17-110039 cadet-tun-8620 INFO <=== {              DATA} on KNAS
Jul 07 20:45:17-110259 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:45:17-110544 cadet-chn-8620 INFO <=== DATA 1 BCK on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-110871 cadet-chn-8620 DEBUG RECV 1 (16)
Jul 07 20:45:17-111152 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:45:17-111366 util-server-nc-8620 DEBUG Adding message of type 285 and size 12 to pending queue (which has 1 entries)
Jul 07 20:45:17-111570 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:45:17-111777 util-scheduler-8620 DEBUG Adding task: 840 / 0x4d5c418
Jul 07 20:45:17-111966 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:45:17-112144 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:45:17-112392 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-112614 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:17-112815 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:17-112994 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:17-113177 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:17-113402 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:17-113579 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:17-113749 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:17-113997 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-114170 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:17-114404 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:17-114588 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:17-114881 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:17-115052 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:17-115238 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:17-118360 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:17-119058 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:17-119237 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:17-119425 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:17-122567 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:17-122805 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:17-122987 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:17-123207 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:17-123398 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:45:17-123673 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (100 bytes)
Jul 07 20:45:17-123871 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:17-124049 cadet-con-8620 DEBUG last pid sent 16
Jul 07 20:45:17-124222 cadet-con-8620 DEBUG      ack recv 75
Jul 07 20:45:17-124393 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:17-124569 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:17-124802 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-125009 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-125341 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:45:17-125544 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:17-125779 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:17-125961 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:17-126135 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:17-126338 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:17-126539 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:17-126715 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:17-126890 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:17-127137 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-127322 cadet-p2p-8620 DEBUG QQQ    payload , 75
Jul 07 20:45:17-127498 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:17-127753 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-127948 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:17-128124 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:17-128321 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:17-128496 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:45:17-128721 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:17-128895 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:17-129069 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:17-129264 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:17-129487 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:17-129664 cadet-con-8620 DEBUG  ACK 76
Jul 07 20:45:17-129844 cadet-con-8620 DEBUG  last pid 12, last ack 75, qmax 11, q 0
Jul 07 20:45:17-130023 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:45:17-130191 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:45:17-130375 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:45:17-130561 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:17-130740 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:17-130927 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:45:17-131102 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:17-131282 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:17-131455 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:17-131677 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:17-131908 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:17-132089 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:17-132262 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:17-132522 cadet-con-8620 INFO --> {               ACK} ( 76) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:17-132714 cadet-con-8620 DEBUG  ack 76
Jul 07 20:45:17-132891 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:17-133125 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-133355 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-133645 cadet-p2p-8620 INFO que {               ACK} ( 76) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:17-133843 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:17-134067 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:17-134249 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:17-134423 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:17-134623 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:17-134834 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:17-135010 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:17-135185 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:17-135420 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-135603 cadet-p2p-8620 DEBUG QQQ    payload , 76
Jul 07 20:45:17-135778 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:17-136011 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-136203 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:17-136379 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:17-136576 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:17-136757 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:17-136968 util-scheduler-8620 DEBUG Adding task: 841 / 0x46620a0
Jul 07 20:45:17-137265 util-scheduler-8620 DEBUG Checking readiness of task: 841 / 0x46620a0
Jul 07 20:45:17-137464 util-scheduler-8620 DEBUG Checking readiness of task: 840 / 0x4d5c418
Jul 07 20:45:17-137657 util-scheduler-8620 DEBUG Checking readiness of task: 839 / 0x4d5e5d8
Jul 07 20:45:17-137848 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-138038 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-138246 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-138437 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-138627 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-138816 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-139006 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-139198 util-scheduler-8620 DEBUG Running task: 839 / 0x4d5e5d8
Jul 07 20:45:17-139385 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:17-139563 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-139733 util-8620 DEBUG client_notify is running
Jul 07 20:45:17-139974 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:17-140183 util-scheduler-8620 DEBUG Adding task: 842 / 0x4d5e5d8
Jul 07 20:45:17-140385 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:17-140726 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:17-140926 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:17-141137 util-scheduler-8620 DEBUG Running task: 840 / 0x4d5c418
Jul 07 20:45:17-141346 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:45:17-141522 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-141780 util-server-nc-8620 DEBUG Copying message of type 285 and size 12 from pending queue to transmission buffer
Jul 07 20:45:17-142110 util-8620 DEBUG Connection transmitted 12/12 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:45:17-142365 util-scheduler-8620 DEBUG Checking readiness of task: 842 / 0x4d5e5d8
Jul 07 20:45:17-142561 util-scheduler-8620 DEBUG Checking readiness of task: 841 / 0x46620a0
Jul 07 20:45:17-142751 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-142941 util-scheduler-8620 DEBUG Checking readiness of task: 567 / 0x4d5c418
Jul 07 20:45:17-143132 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-143322 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-143512 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-143701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-143890 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-144081 util-scheduler-8620 DEBUG Running task: 567 / 0x4d5c418
Jul 07 20:45:17-144463 util-8620 DEBUG receive_ready read 20/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:45:17-144672 util-8620 DEBUG Server receives 20 bytes from `<unbound UNIX client>'.
Jul 07 20:45:17-144865 util-8620 DEBUG Server-mst receives 20 bytes with 0 bytes already in private buffer
Jul 07 20:45:17-145050 util-8620 DEBUG Server-mst has 20 bytes left in inbound buffer
Jul 07 20:45:17-145260 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:45:17-145449 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:45:17-145680 util-scheduler-8620 DEBUG Adding task: 843 / 0x4d5c578
Jul 07 20:45:17-146063 cadet-loc-8620 DEBUG 
Jul 07 20:45:17-146400 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:45:17-146732 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:45:17-147066 cadet-loc-8620 DEBUG   on channel 80000001
Jul 07 20:45:17-147406 cadet-loc-8620 DEBUG    -- ch 0x4d638d8
Jul 07 20:45:17-147737 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:45:17-148142 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:45:17-148510 cadet-tun-8620 DEBUG Tunnel send connection ACKs on KNAS
Jul 07 20:45:17-148847 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:45:17-149184 cadet-tun-8620 DEBUG   allowed 64
Jul 07 20:45:17-149406 util-scheduler-8620 DEBUG Canceling task: 843 / 0x4d5c578
Jul 07 20:45:17-149601 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:45:17-149800 util-8620 DEBUG Server-mst has 12 bytes left in inbound buffer
Jul 07 20:45:17-149987 util-8620 DEBUG Server-mst leaves 12 bytes in private buffer
Jul 07 20:45:17-150163 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:45:17-150344 util-8620 DEBUG Server-mst receives 0 bytes with 12 bytes already in private buffer
Jul 07 20:45:17-150533 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:45:17-150720 util-8620 DEBUG Server schedules transmission of 12-byte message of type 285 to client.
Jul 07 20:45:17-150929 util-scheduler-8620 DEBUG Adding task: 844 / 0x4d5c578
Jul 07 20:45:17-151109 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:45:17-151282 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:45:17-151458 cadet-loc-8620 DEBUG   on channel 80000001
Jul 07 20:45:17-151639 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:45:17-151884 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-152082 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:45:17-152283 cadet-chn-8620 DEBUG !!! SAVE 2 {              DATA}
Jul 07 20:45:17-152469 cadet-chn-8620 DEBUG   at 0x5b978b8
Jul 07 20:45:17-152649 cadet-chn-8620 DEBUG   new chq: 0x5b97838
Jul 07 20:45:17-152851 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:17-153049 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:17-153251 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:17-153434 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:17-153614 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:17-153790 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:17-153959 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:17-154173 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-154344 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:17-154577 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:17-154762 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:17-155030 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:17-155203 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:17-155385 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:17-158619 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:17-159271 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:17-159447 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:17-159635 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:17-162774 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:17-163011 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:17-163192 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:17-163412 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:17-163602 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:17-163875 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (96 bytes)
Jul 07 20:45:17-164071 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:17-164248 cadet-con-8620 DEBUG last pid sent 16
Jul 07 20:45:17-164421 cadet-con-8620 DEBUG      ack recv 75
Jul 07 20:45:17-164598 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:45:17-164840 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:17-165090 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:17-165425 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 96)
Jul 07 20:45:17-165625 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:17-165850 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:17-166033 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:17-166209 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:17-166410 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:17-166611 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:17-166806 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:17-166981 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:17-167221 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-167410 cadet-p2p-8620 DEBUG QQQ    payload , 76
Jul 07 20:45:17-167587 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:17-167822 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-168028 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:17-168205 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:17-168439 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:17-168632 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:17-168809 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:17-169007 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:17-169234 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:17-169413 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:17-169595 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:17-169775 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:17-169952 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:17-170122 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:17-170337 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-170513 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:17-170743 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:17-170928 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:17-171101 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:17-171275 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:45:17-171478 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:17-171655 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:17-171836 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:17-172016 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:17-172191 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:17-172360 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:17-172586 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-172758 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:17-172986 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:17-173170 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:17-173371 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:45:17-173598 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:17-173788 cadet-loc-8620 DEBUG send local FWD ack on 80000001 towards 0x4d5c6d8
Jul 07 20:45:17-173997 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:45:17-174200 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:45:17-174410 util-scheduler-8620 DEBUG Adding task: 845 / 0x4d5c418
Jul 07 20:45:17-174593 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:45:17-174776 util-scheduler-8620 DEBUG Canceling task: 844 / 0x4d5c578
Jul 07 20:45:17-174969 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:45:17-175149 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:45:17-175354 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:45:17-175560 util-scheduler-8620 DEBUG Adding task: 846 / 0x4d5c418
Jul 07 20:45:17-175761 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:45:17-175989 util-scheduler-8620 DEBUG Running task: 842 / 0x4d5e5d8
Jul 07 20:45:17-176178 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:17-176355 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-176526 util-8620 DEBUG client_notify is running
Jul 07 20:45:17-176749 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:45:17-177132 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:17-177463 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:17-177660 util-scheduler-8620 DEBUG Checking readiness of task: 845 / 0x4d5c418
Jul 07 20:45:17-177853 util-scheduler-8620 DEBUG Checking readiness of task: 841 / 0x46620a0
Jul 07 20:45:17-178044 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:17-178235 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:17-178426 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:17-178617 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:17-178808 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:17-178999 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:17-179191 util-scheduler-8620 DEBUG Running task: 845 / 0x4d5c418
Jul 07 20:45:17-179378 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:45:17-179554 util-8620 DEBUG process_notify is running
Jul 07 20:45:17-179747 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:45:17-180092 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:45:18-711284 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:18-711666 util-scheduler-8620 DEBUG Checking readiness of task: 841 / 0x46620a0
Jul 07 20:45:18-711867 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:18-712061 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:18-712253 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:18-712444 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:18-712636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:18-712827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:18-713024 util-scheduler-8620 DEBUG Running task: 841 / 0x46620a0
Jul 07 20:45:18-713494 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:18-713757 util-scheduler-8620 DEBUG Adding task: 847 / 0x4662248
Jul 07 20:45:18-714039 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:18-714232 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:18-714424 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:18-714615 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:18-714806 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:18-714996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:18-715209 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:18-715400 util-scheduler-8620 DEBUG Running task: 847 / 0x4662248
Jul 07 20:45:18-715593 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:18-715793 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:18-716024 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:18-716288 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:18-716531 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:18-716763 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:18-716973 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:18-717286 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:18-717499 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:18-717687 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:18-717903 util-scheduler-8620 DEBUG Canceling task: 802 / 0x4d707d0
Jul 07 20:45:18-718128 util-scheduler-8620 DEBUG Adding task: 848 / 0x4d707d0
Jul 07 20:45:18-718308 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:18-718568 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:18-718783 util-scheduler-8620 DEBUG Adding task: 849 / 0x4d5e5d8
Jul 07 20:45:18-718965 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:18-719167 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:19-340991 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:19-341404 util-scheduler-8620 DEBUG Adding task: 850 / 0x46620a0
Jul 07 20:45:19-341701 util-scheduler-8620 DEBUG Checking readiness of task: 850 / 0x46620a0
Jul 07 20:45:19-341900 util-scheduler-8620 DEBUG Checking readiness of task: 849 / 0x4d5e5d8
Jul 07 20:45:19-342094 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-342284 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-342474 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-342664 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-342853 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-343042 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-343231 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-343426 util-scheduler-8620 DEBUG Running task: 849 / 0x4d5e5d8
Jul 07 20:45:19-343613 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:19-343793 util-8620 DEBUG process_notify is running
Jul 07 20:45:19-343966 util-8620 DEBUG client_notify is running
Jul 07 20:45:19-344204 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:19-344568 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:19-587406 util-scheduler-8620 DEBUG Checking readiness of task: 850 / 0x46620a0
Jul 07 20:45:19-587780 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-587975 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-588168 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-588360 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-588552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-588743 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-588933 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-589131 util-scheduler-8620 DEBUG Running task: 850 / 0x46620a0
Jul 07 20:45:19-589578 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:19-589839 util-scheduler-8620 DEBUG Adding task: 851 / 0x4662248
Jul 07 20:45:19-590115 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-590327 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-590517 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-590708 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-590897 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-591086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-591276 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-591466 util-scheduler-8620 DEBUG Running task: 851 / 0x4662248
Jul 07 20:45:19-591657 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:19-591857 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:19-592089 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:19-592330 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:19-592538 util-scheduler-8620 DEBUG Adding task: 852 / 0x46620a0
Jul 07 20:45:19-592725 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:19-592929 util-scheduler-8620 DEBUG Adding task: 853 / 0x46620a0
Jul 07 20:45:19-593172 util-scheduler-8620 DEBUG Checking readiness of task: 853 / 0x46620a0
Jul 07 20:45:19-593388 util-scheduler-8620 DEBUG Checking readiness of task: 852 / 0x46620a0
Jul 07 20:45:19-593580 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-593769 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-593958 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-594147 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-594336 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-594525 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-594713 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-594904 util-scheduler-8620 DEBUG Running task: 852 / 0x46620a0
Jul 07 20:45:19-595090 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:19-595267 util-8620 DEBUG process_notify is running
Jul 07 20:45:19-595438 util-8620 DEBUG client_notify is running
Jul 07 20:45:19-595627 util-scheduler-8620 DEBUG Canceling task: 826 / 0x4d6ff98
Jul 07 20:45:19-595849 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:19-596069 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:19-596310 cadet-p2p-8620 DEBUG Checking 0x5b70408 towards CMHCKRVP (->V8XX)
Jul 07 20:45:19-596543 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:19-596720 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:19-596912 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:19-597222 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:19-597420 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:19-597601 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:19-597789 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:19-597979 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:19-598159 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:19-598374 util-scheduler-8620 DEBUG Canceling task: 819 / 0x4d707d0
Jul 07 20:45:19-598586 util-scheduler-8620 DEBUG Adding task: 854 / 0x4d707d0
Jul 07 20:45:19-598838 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:19-599010 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:19-599235 cadet-p2p-8620 DEBUG Checking 0x5b76de8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:19-599485 cadet-p2p-8620 DEBUG Checking 0x5b76de8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:19-599663 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:19-599870 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:19-600097 util-scheduler-8620 DEBUG Adding task: 855 / 0x4d6ff98
Jul 07 20:45:19-600276 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:19-600453 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:19-600653 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:19-600829 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:19-601004 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:19-601265 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:19-601464 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:19-601642 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:19-601843 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:19-602050 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:19-602233 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:19-602436 util-scheduler-8620 DEBUG Adding task: 856 / 0x4d6ff98
Jul 07 20:45:19-602672 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:19-602867 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:19-603070 util-scheduler-8620 DEBUG Adding task: 857 / 0x46620a0
Jul 07 20:45:19-603270 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:19-604029 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:19-604231 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:19-604477 util-scheduler-8620 DEBUG Checking readiness of task: 857 / 0x46620a0
Jul 07 20:45:19-604670 util-scheduler-8620 DEBUG Checking readiness of task: 853 / 0x46620a0
Jul 07 20:45:19-604860 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-605050 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-605264 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-605456 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-605646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-605834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-606023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-606213 util-scheduler-8620 DEBUG Running task: 857 / 0x46620a0
Jul 07 20:45:19-606398 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:19-606574 util-8620 DEBUG process_notify is running
Jul 07 20:45:19-606745 util-8620 DEBUG client_notify is running
Jul 07 20:45:19-606923 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:19-607117 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:19-607306 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:19-607588 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:19-607796 util-scheduler-8620 DEBUG Running task: 855 / 0x4d6ff98
Jul 07 20:45:19-607989 util-scheduler-8620 DEBUG Canceling task: 856 / 0x4d6ff98
Jul 07 20:45:19-608202 util-scheduler-8620 DEBUG Adding task: 858 / 0x4d6ff98
Jul 07 20:45:19-608427 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:19-608621 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:19-608820 util-scheduler-8620 DEBUG Adding task: 859 / 0x46620a0
Jul 07 20:45:19-609058 util-scheduler-8620 DEBUG Checking readiness of task: 859 / 0x46620a0
Jul 07 20:45:19-609278 util-scheduler-8620 DEBUG Checking readiness of task: 853 / 0x46620a0
Jul 07 20:45:19-609469 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-609658 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-609847 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-610036 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-610224 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-610412 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-610601 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-610791 util-scheduler-8620 DEBUG Running task: 859 / 0x46620a0
Jul 07 20:45:19-610975 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:19-611149 util-8620 DEBUG process_notify is running
Jul 07 20:45:19-611318 util-8620 DEBUG client_notify is running
Jul 07 20:45:19-611494 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:19-611683 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:19-611869 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:19-612164 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:19-982358 util-scheduler-8620 DEBUG Checking readiness of task: 853 / 0x46620a0
Jul 07 20:45:19-982717 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-982930 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-983124 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-983316 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-983508 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-983700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-983891 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-984087 util-scheduler-8620 DEBUG Running task: 853 / 0x46620a0
Jul 07 20:45:19-984509 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:19-984762 util-scheduler-8620 DEBUG Adding task: 860 / 0x4662248
Jul 07 20:45:19-985038 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-985256 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-985448 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-985639 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-985830 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-986020 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-986211 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-986402 util-scheduler-8620 DEBUG Running task: 860 / 0x4662248
Jul 07 20:45:19-986594 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:19-986793 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:19-987023 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:19-987229 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:19-987437 util-scheduler-8620 DEBUG Adding task: 861 / 0x46620a0
Jul 07 20:45:19-987625 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:19-987831 util-scheduler-8620 DEBUG Adding task: 862 / 0x46620a0
Jul 07 20:45:19-988075 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:19-988268 util-scheduler-8620 DEBUG Checking readiness of task: 861 / 0x46620a0
Jul 07 20:45:19-988461 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:19-988652 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:19-988842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:19-989053 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:19-989928 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:19-990129 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:19-990322 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:19-990598 util-scheduler-8620 DEBUG Running task: 861 / 0x46620a0
Jul 07 20:45:19-990790 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:19-990970 util-8620 DEBUG process_notify is running
Jul 07 20:45:19-991144 util-8620 DEBUG client_notify is running
Jul 07 20:45:19-991334 util-scheduler-8620 DEBUG Canceling task: 836 / 0x4d5c9e8
Jul 07 20:45:19-991562 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:45:19-991783 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:19-992024 cadet-p2p-8620 DEBUG Checking 0x5b95f38 towards HS92G30M (->KNAS)
Jul 07 20:45:19-992258 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:19-992437 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:19-992654 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:19-992938 cadet-p2p-8620 INFO snd {               ACK} ( 76) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:19-993134 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:19-993796 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:19-994067 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:19-994247 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:19-994434 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:45:19-994610 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:19-994834 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:19-995068 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:19-995251 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:19-995428 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:19-995657 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:19-995887 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:19-996069 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 16
Jul 07 20:45:19-996243 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:19-996411 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:19-996618 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:19-996835 util-scheduler-8620 DEBUG Adding task: 863 / 0x4d5c9e8
Jul 07 20:45:19-997016 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:19-997664 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:19-997943 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:19-998122 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:19-998299 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:19-998540 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:19-998737 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:19-998916 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:19-999151 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:19-999362 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:19-999539 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:19-999738 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:19-999944 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:20-000127 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:20-000335 util-scheduler-8620 DEBUG Adding task: 864 / 0x4d5c9e8
Jul 07 20:45:20-000556 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:20-000755 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:20-000960 util-scheduler-8620 DEBUG Adding task: 865 / 0x46620a0
Jul 07 20:45:20-001647 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:20-002550 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:20-002756 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:20-003013 util-scheduler-8620 DEBUG Checking readiness of task: 865 / 0x46620a0
Jul 07 20:45:20-003210 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-003404 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-003597 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-003790 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-003983 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-004175 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-004367 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-004560 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-004772 util-scheduler-8620 DEBUG Running task: 865 / 0x46620a0
Jul 07 20:45:20-004962 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:20-005689 util-8620 DEBUG process_notify is running
Jul 07 20:45:20-005869 util-8620 DEBUG client_notify is running
Jul 07 20:45:20-006051 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:20-006250 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:20-006443 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:20-006797 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:20-007010 util-scheduler-8620 DEBUG Running task: 863 / 0x4d5c9e8
Jul 07 20:45:20-007208 util-scheduler-8620 DEBUG Canceling task: 864 / 0x4d5c9e8
Jul 07 20:45:20-007427 util-scheduler-8620 DEBUG Adding task: 866 / 0x4d5c9e8
Jul 07 20:45:20-007649 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:20-007846 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:20-008049 util-scheduler-8620 DEBUG Adding task: 867 / 0x46620a0
Jul 07 20:45:20-008294 util-scheduler-8620 DEBUG Checking readiness of task: 867 / 0x46620a0
Jul 07 20:45:20-008490 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-008683 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-008875 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-009565 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-009836 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-010031 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-010226 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-010418 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-010624 util-scheduler-8620 DEBUG Running task: 867 / 0x46620a0
Jul 07 20:45:20-010812 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:20-010990 util-8620 DEBUG process_notify is running
Jul 07 20:45:20-011162 util-8620 DEBUG client_notify is running
Jul 07 20:45:20-011345 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:20-011538 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:20-011729 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:20-012033 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:20-150804 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-151190 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-151386 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-151578 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-151771 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-151962 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-152154 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-152345 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-152538 util-scheduler-8620 DEBUG Running task: 503 / 0x4d68be8
Jul 07 20:45:20-152812 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:45:20-152991 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:45:20-153271 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:45:20-153463 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:45:20-153699 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:45:20-153908 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:45:20-154215 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:45:20-154447 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:20-154675 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:45:20-154860 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:20-155451 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:20-155667 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:45:20-155887 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:45:20-156115 util-scheduler-8620 DEBUG Adding task: 868 / 0x4d683b0
Jul 07 20:45:20-156297 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:20-156502 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:45:20-156691 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:20-156869 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:45:20-157109 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:45:20-157317 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:20-157494 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:20-157696 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:45:20-157953 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-158146 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-158347 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-158537 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-158726 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-158919 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-159108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-159297 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-159486 util-scheduler-8620 DEBUG Running task: 868 / 0x4d683b0
Jul 07 20:45:20-159696 util-scheduler-8620 DEBUG Adding task: 869 / 0x4d683b0
Jul 07 20:45:20-159918 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:45:20-160121 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:20-160328 util-scheduler-8620 DEBUG Adding task: 870 / 0x46620a0
Jul 07 20:45:20-160570 util-scheduler-8620 DEBUG Checking readiness of task: 870 / 0x46620a0
Jul 07 20:45:20-160763 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-160953 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-161142 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-161353 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-161542 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-161731 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-161919 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-162108 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-162299 util-scheduler-8620 DEBUG Running task: 870 / 0x46620a0
Jul 07 20:45:20-162485 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:20-163050 util-8620 DEBUG process_notify is running
Jul 07 20:45:20-163231 util-8620 DEBUG client_notify is running
Jul 07 20:45:20-163414 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:20-163614 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:20-163805 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:20-164123 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:20-479133 util-scheduler-8620 DEBUG Checking readiness of task: 862 / 0x46620a0
Jul 07 20:45:20-479511 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-479738 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-479933 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-480126 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-480318 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-480509 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-480700 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-480897 util-scheduler-8620 DEBUG Running task: 862 / 0x46620a0
Jul 07 20:45:20-481348 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:20-481607 util-scheduler-8620 DEBUG Adding task: 871 / 0x4662248
Jul 07 20:45:20-481887 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-482080 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-482271 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-482462 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-482652 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-482842 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-483031 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-483221 util-scheduler-8620 DEBUG Running task: 871 / 0x4662248
Jul 07 20:45:20-483412 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:20-483615 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:20-483847 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:20-484119 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:20-484392 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:20-484601 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:20-484786 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:20-484960 cadet-con-8620 DEBUG   ACK 76 (was 75)
Jul 07 20:45:20-485213 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:20-485447 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:20-485654 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:20-485836 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:20-486040 util-scheduler-8620 DEBUG Adding task: 872 / 0x4662248
Jul 07 20:45:20-486280 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-486472 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-486662 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-486850 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-487039 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-487227 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-487415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-487604 util-scheduler-8620 DEBUG Running task: 872 / 0x4662248
Jul 07 20:45:20-487792 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:20-487984 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:20-488198 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:20-488441 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:20-488675 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:20-488906 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:20-489115 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:20-489378 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:20-489601 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:20-489789 cadet-con-8620 DEBUG  PID 13 (expected 13+)
Jul 07 20:45:20-489969 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:20-490157 util-scheduler-8620 DEBUG Canceling task: 838 / 0x4d61c30
Jul 07 20:45:20-490380 util-scheduler-8620 DEBUG Adding task: 873 / 0x4d61c30
Jul 07 20:45:20-490559 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:20-490817 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:20-491034 util-scheduler-8620 DEBUG Adding task: 874 / 0x4d5e5d8
Jul 07 20:45:20-491219 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:20-491397 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:20-494971 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:20-495802 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:20-496011 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:20-499254 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:20-499461 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:45:20-499646 cadet-chn-8620 DEBUG   head 2, out!
Jul 07 20:45:20-499830 cadet-chn-8620 DEBUG free_sent_reliable 1 0
Jul 07 20:45:20-500016 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x5b978b8
Jul 07 20:45:20-500193 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:20-500363 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:20-500538 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:45:20-500745 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:20-500925 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:20-501108 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:20-501316 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:20-501494 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:20-501675 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:20-501894 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:20-502068 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:20-502304 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:20-502490 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:20-502669 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:45:20-502897 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:20-503078 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:20-503304 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:20-503480 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:20-503655 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:20-503827 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:20-504049 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:20-504230 cadet-con-8620 DEBUG  ACK 77
Jul 07 20:45:20-505452 cadet-con-8620 DEBUG  last pid 13, last ack 76, qmax 11, q 0
Jul 07 20:45:20-505810 cadet-con-8620 INFO --> {               ACK} ( 77) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:20-506005 cadet-con-8620 DEBUG  ack 77
Jul 07 20:45:20-506185 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:45:20-506423 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:20-506632 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:20-506930 cadet-p2p-8620 INFO que {               ACK} ( 77) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:20-507130 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:20-507356 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:20-507540 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 16
Jul 07 20:45:20-507716 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:20-507919 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:20-508122 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:20-508299 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:20-508476 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:20-508714 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:20-508925 cadet-p2p-8620 DEBUG QQQ    payload , 77
Jul 07 20:45:20-509104 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:20-509365 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:20-509560 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:20-509738 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:20-509986 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:20-510180 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:20-510357 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:20-510554 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:20-510739 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:20-510954 util-scheduler-8620 DEBUG Adding task: 875 / 0x46620a0
Jul 07 20:45:20-511225 util-scheduler-8620 DEBUG Checking readiness of task: 875 / 0x46620a0
Jul 07 20:45:20-511421 util-scheduler-8620 DEBUG Checking readiness of task: 874 / 0x4d5e5d8
Jul 07 20:45:20-511613 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:20-511803 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:20-511992 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:20-512182 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:20-512371 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:20-512560 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:20-512749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:20-512941 util-scheduler-8620 DEBUG Running task: 874 / 0x4d5e5d8
Jul 07 20:45:20-513128 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:20-513331 util-8620 DEBUG process_notify is running
Jul 07 20:45:20-513504 util-8620 DEBUG client_notify is running
Jul 07 20:45:20-513735 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:20-514046 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:21-253730 util-scheduler-8620 DEBUG Checking readiness of task: 875 / 0x46620a0
Jul 07 20:45:21-254118 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-254315 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-254510 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-254704 util-scheduler-8620 DEBUG Checking readiness of task: 82 / 0x4663d68
Jul 07 20:45:21-254899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-255091 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-255281 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-255478 util-scheduler-8620 DEBUG Running task: 82 / 0x4663d68
Jul 07 20:45:21-255907 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:21-256170 util-scheduler-8620 DEBUG Adding task: 876 / 0x4663f10
Jul 07 20:45:21-256451 util-scheduler-8620 DEBUG Checking readiness of task: 875 / 0x46620a0
Jul 07 20:45:21-256645 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-256836 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-257027 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-257245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-257437 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-257628 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-257818 util-scheduler-8620 DEBUG Running task: 875 / 0x46620a0
Jul 07 20:45:21-258221 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:21-258479 util-scheduler-8620 DEBUG Adding task: 877 / 0x4662248
Jul 07 20:45:21-258688 util-scheduler-8620 DEBUG Running task: 876 / 0x4663f10
Jul 07 20:45:21-258882 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:45:21-259115 util-scheduler-8620 DEBUG Adding task: 878 / 0x4663f10
Jul 07 20:45:21-259343 transport-api-8620 DEBUG Receiving `CONNECT' message for `D3TJ'.
Jul 07 20:45:21-259555 transport-api-8620 DEBUG Creating entry for neighbour `D3TJ'.
Jul 07 20:45:21-259749 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:45:21-259943 util-bandwidth-8620 DEBUG Tracker 0x5df6f20 initialized with 1024 Bps and max carry 5
Jul 07 20:45:21-260192 util-scheduler-8620 DEBUG Adding task: 879 / 0x5df6f20
Jul 07 20:45:21-260433 transport-api-8620 DEBUG Receiving `CONNECT' message for `D3TJ' with quota 11868
Jul 07 20:45:21-260625 util-bandwidth-8620 DEBUG Tracker 0x5df6f20 bandwidth changed to 11868 Bps
Jul 07 20:45:21-260863 util-bandwidth-8620 DEBUG Tracker 0x5df6f20 updated, have 1024 Bps, last update was 879 µs ago
Jul 07 20:45:21-261077 util-scheduler-8620 DEBUG Canceling task: 879 / 0x5df6f20
Jul 07 20:45:21-261316 util-scheduler-8620 DEBUG Adding task: 880 / 0x5df6f20
Jul 07 20:45:21-261556 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-261747 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-261937 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-262127 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-262317 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-262506 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-262695 util-scheduler-8620 DEBUG Running task: 878 / 0x4663f10
Jul 07 20:45:21-262886 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:21-263077 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:21-263293 util-scheduler-8620 DEBUG Adding task: 881 / 0x4663d68
Jul 07 20:45:21-264647 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:21-266660 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `D3TJ' with quota 11868
Jul 07 20:45:21-267129 util-bandwidth-8620 DEBUG Tracker 0x5df6f20 bandwidth changed to 11868 Bps
Jul 07 20:45:21-267381 util-bandwidth-8620 DEBUG Tracker 0x5df6f20 updated, have 11868 Bps, last update was 6 ms ago
Jul 07 20:45:21-267593 util-scheduler-8620 DEBUG Canceling task: 880 / 0x5df6f20
Jul 07 20:45:21-267807 util-scheduler-8620 DEBUG Adding task: 882 / 0x5df6f20
Jul 07 20:45:21-268236 util-scheduler-8620 DEBUG Running task: 877 / 0x4662248
Jul 07 20:45:21-268431 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:21-268630 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:21-268850 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:21-269116 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:21-269400 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:21-269610 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:21-269794 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:21-269968 cadet-con-8620 DEBUG   ACK 77 (was 76)
Jul 07 20:45:21-270198 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:21-270428 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:21-270634 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:21-270816 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:21-271018 util-scheduler-8620 DEBUG Adding task: 883 / 0x4662248
Jul 07 20:45:21-271260 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-271451 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-271660 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-271850 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-272040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-272240 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-272430 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-272619 util-scheduler-8620 DEBUG Running task: 883 / 0x4662248
Jul 07 20:45:21-272808 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:21-273000 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:21-273239 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:21-273483 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:21-273718 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:21-273946 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:21-274154 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:21-274395 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:21-274601 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:21-274789 cadet-con-8620 DEBUG  PID 14 (expected 14+)
Jul 07 20:45:21-274968 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:21-275151 util-scheduler-8620 DEBUG Canceling task: 873 / 0x4d61c30
Jul 07 20:45:21-275366 util-scheduler-8620 DEBUG Adding task: 884 / 0x4d61c30
Jul 07 20:45:21-275545 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:21-275804 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:21-276017 util-scheduler-8620 DEBUG Adding task: 885 / 0x4d5e5d8
Jul 07 20:45:21-276201 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:21-276367 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:21-279942 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:21-280734 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:21-280928 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:21-284238 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:21-284447 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:45:21-284629 cadet-chn-8620 DEBUG   head 2, out!
Jul 07 20:45:21-284812 cadet-chn-8620 DEBUG free_sent_reliable 1 0
Jul 07 20:45:21-284995 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x5b978b8
Jul 07 20:45:21-285172 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:21-285368 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:21-285542 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:45:21-285748 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:21-285929 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:21-286112 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:21-286293 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:21-286470 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:21-286639 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:21-286856 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:21-287028 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:21-287263 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:21-287448 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:21-287626 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:45:21-287853 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:21-288031 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:21-288253 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:21-288427 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:21-288603 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:21-288774 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:21-288995 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:21-289177 cadet-con-8620 DEBUG  ACK 78
Jul 07 20:45:21-289382 cadet-con-8620 DEBUG  last pid 14, last ack 77, qmax 11, q 0
Jul 07 20:45:21-289596 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:45:21-289777 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:45:21-289963 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:45:21-290148 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:21-290327 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:21-290515 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:45:21-290689 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:21-290872 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:45:21-291046 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:21-291269 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:21-291502 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:21-291683 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 16
Jul 07 20:45:21-291858 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:21-292120 cadet-con-8620 INFO --> {               ACK} ( 78) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:21-292313 cadet-con-8620 DEBUG  ack 78
Jul 07 20:45:21-292489 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 2
Jul 07 20:45:21-292724 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:21-292930 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:21-293253 cadet-p2p-8620 INFO que {               ACK} ( 78) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:21-293454 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:21-293679 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:21-293861 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 16
Jul 07 20:45:21-294036 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:21-294239 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:21-294442 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:21-294619 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:21-294795 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:21-295033 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:21-295217 cadet-p2p-8620 DEBUG QQQ    payload , 78
Jul 07 20:45:21-295394 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:21-295627 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:21-295820 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:21-295998 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:21-296231 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:21-296425 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:21-296603 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:21-296802 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:21-296986 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:21-297229 util-scheduler-8620 DEBUG Adding task: 886 / 0x46620a0
Jul 07 20:45:21-297499 util-scheduler-8620 DEBUG Checking readiness of task: 886 / 0x46620a0
Jul 07 20:45:21-297694 util-scheduler-8620 DEBUG Checking readiness of task: 885 / 0x4d5e5d8
Jul 07 20:45:21-297887 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-298077 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-298270 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-298461 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-298649 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-298839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-299030 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-299223 util-scheduler-8620 DEBUG Running task: 885 / 0x4d5e5d8
Jul 07 20:45:21-299409 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:21-299587 util-8620 DEBUG process_notify is running
Jul 07 20:45:21-299777 util-8620 DEBUG client_notify is running
Jul 07 20:45:21-300006 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:21-300363 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:21-447160 util-scheduler-8620 DEBUG Checking readiness of task: 886 / 0x46620a0
Jul 07 20:45:21-447531 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-447727 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-447919 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-448110 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-448301 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-448492 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-448682 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-448878 util-scheduler-8620 DEBUG Running task: 886 / 0x46620a0
Jul 07 20:45:21-449330 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:21-449589 util-scheduler-8620 DEBUG Adding task: 887 / 0x4662248
Jul 07 20:45:21-449867 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-450058 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-450248 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-450438 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-450629 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-450819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-451008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-451197 util-scheduler-8620 DEBUG Running task: 887 / 0x4662248
Jul 07 20:45:21-451390 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:21-451590 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:21-451818 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:21-452083 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:21-452328 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:21-452559 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:21-452768 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:21-453014 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:21-453248 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:21-453437 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:21-453626 util-scheduler-8620 DEBUG Canceling task: 848 / 0x4d707d0
Jul 07 20:45:21-453848 util-scheduler-8620 DEBUG Adding task: 888 / 0x4d707d0
Jul 07 20:45:21-454028 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:21-454314 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:21-454530 util-scheduler-8620 DEBUG Adding task: 889 / 0x4d5e5d8
Jul 07 20:45:21-454712 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:21-454911 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:21-455097 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:21-455269 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:21-455434 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:21-458981 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:21-460327 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:21-460557 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:21-460854 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:21-461028 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:21-461241 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:21-464306 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:21-464891 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:21-465096 cadet-tun-8620 DEBUG   e sending 2014888766
Jul 07 20:45:21-465331 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:21-465534 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:21-465763 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:21-465944 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:21-466165 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:21-466444 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:21-466643 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:21-466879 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:21-467086 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:21-467396 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:21-467596 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:21-467821 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:21-468003 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:21-468179 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:21-468391 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:21-468593 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:21-468769 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:21-468944 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:21-469187 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-469406 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:21-469584 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:21-469818 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-470011 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:21-470186 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:21-470384 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:21-470568 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:21-470780 util-scheduler-8620 DEBUG Adding task: 890 / 0x46620a0
Jul 07 20:45:21-471053 util-scheduler-8620 DEBUG Checking readiness of task: 890 / 0x46620a0
Jul 07 20:45:21-471248 util-scheduler-8620 DEBUG Checking readiness of task: 889 / 0x4d5e5d8
Jul 07 20:45:21-471441 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-471630 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-471820 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-472010 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-472201 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-472391 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-472581 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-472774 util-scheduler-8620 DEBUG Running task: 889 / 0x4d5e5d8
Jul 07 20:45:21-472960 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:21-473139 util-8620 DEBUG process_notify is running
Jul 07 20:45:21-473335 util-8620 DEBUG client_notify is running
Jul 07 20:45:21-473564 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:21-473917 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:21-720733 util-scheduler-8620 DEBUG Checking readiness of task: 890 / 0x46620a0
Jul 07 20:45:21-721130 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:21-721353 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:21-721546 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:21-721740 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:21-721964 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:21-722156 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:21-722346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:21-722540 util-scheduler-8620 DEBUG Running task: 825 / 0x4d64a70
Jul 07 20:45:21-722779 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:21-723027 cadet-tun-8620 DEBUG  kx started 55 s ago
Jul 07 20:45:21-723236 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:21-723437 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:21-723639 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:21-723875 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:21-724054 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:21-724296 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:21-724639 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:21-724837 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:21-725104 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:21-725339 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:21-725658 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:21-725860 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:21-726085 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:21-726269 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:21-726445 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:21-726649 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:21-726853 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:21-727029 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:21-727205 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:21-727444 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-727640 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:21-727818 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:21-728052 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-728245 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:21-728421 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:21-728654 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-728847 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:21-729024 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:21-729744 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:21-787414 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:21-787870 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:21-788076 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:21-788249 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:21-788437 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:21-792071 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:21-793400 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:21-793585 cadet-tun-8620 DEBUG   e sending 2770852602
Jul 07 20:45:21-793795 cadet-tun-8620 DEBUG   e towards WQQV
Jul 07 20:45:21-793997 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:21-794198 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:21-794433 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:21-794614 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:21-794836 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:21-795119 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:21-795319 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 3
Jul 07 20:45:21-795555 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:21-795763 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:21-796111 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:21-796312 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:21-796546 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:21-796730 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:21-796905 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:21-797110 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:21-797339 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:21-797516 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:21-797691 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:21-797929 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-798124 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:21-798300 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:21-798534 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-798726 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:21-798902 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:21-799134 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-799330 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:21-799507 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:21-799739 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:21-799931 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:21-800107 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:21-800304 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:21-800558 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:21-800768 util-scheduler-8620 DEBUG Adding task: 891 / 0x4d64a70
Jul 07 20:45:22-604713 util-scheduler-8620 DEBUG Checking readiness of task: 890 / 0x46620a0
Jul 07 20:45:22-605097 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-605323 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-605530 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-605723 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-605915 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-606105 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-606296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-606492 util-scheduler-8620 DEBUG Running task: 890 / 0x46620a0
Jul 07 20:45:22-606915 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-607172 util-scheduler-8620 DEBUG Adding task: 892 / 0x4662248
Jul 07 20:45:22-607452 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-607645 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-607836 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-608027 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-608217 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-608407 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-608596 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-608786 util-scheduler-8620 DEBUG Running task: 892 / 0x4662248
Jul 07 20:45:22-608979 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-609181 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-610617 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:45:22-610828 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-611086 util-scheduler-8620 DEBUG Adding task: 893 / 0x46620a0
Jul 07 20:45:22-611302 util-scheduler-8620 DEBUG Adding task: 894 / 0x4662248
Jul 07 20:45:22-611545 util-scheduler-8620 DEBUG Checking readiness of task: 893 / 0x46620a0
Jul 07 20:45:22-611738 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-611928 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-612118 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-612307 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-612497 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-612687 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-612876 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-613068 util-scheduler-8620 DEBUG Running task: 893 / 0x46620a0
Jul 07 20:45:22-613279 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-613836 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-614014 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-614206 util-scheduler-8620 DEBUG Canceling task: 869 / 0x4d683b0
Jul 07 20:45:22-614434 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:45:22-614655 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:45:22-614897 cadet-p2p-8620 DEBUG Checking 0x5deaa28 towards KT5Q8VM8 (->P00P)
Jul 07 20:45:22-615131 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:45:22-615309 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:22-615481 cadet-p2p-8620 DEBUG   path create
Jul 07 20:45:22-615652 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:45:22-615834 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:45:22-616103 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:45:22-616298 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-616479 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-616667 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:45:22-616848 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:45:22-617753 util-scheduler-8620 DEBUG Adding task: 895 / 0x4d68be8
Jul 07 20:45:22-618005 cadet-con-8620 DEBUG next keepalive in 64 s
Jul 07 20:45:22-618181 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-618365 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:22-618568 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:45:22-618742 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:22-618918 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:22-619131 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:45:22-619336 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:45:22-619523 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:22-619703 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-619896 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:22-620728 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-620946 util-scheduler-8620 DEBUG Running task: 894 / 0x4662248
Jul 07 20:45:22-621548 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-621750 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-621976 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-622176 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-622379 util-scheduler-8620 DEBUG Adding task: 896 / 0x46620a0
Jul 07 20:45:22-622591 util-scheduler-8620 DEBUG Adding task: 897 / 0x4662248
Jul 07 20:45:22-622838 util-scheduler-8620 DEBUG Checking readiness of task: 896 / 0x46620a0
Jul 07 20:45:22-623031 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-623241 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-623431 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-623620 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-623810 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-623999 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-624188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-624379 util-scheduler-8620 DEBUG Running task: 896 / 0x46620a0
Jul 07 20:45:22-624564 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-624739 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-625303 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-625492 util-scheduler-8620 DEBUG Canceling task: 858 / 0x4d6ff98
Jul 07 20:45:22-625715 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:22-625929 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:22-626161 cadet-p2p-8620 DEBUG Checking 0x5b76de8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-626392 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:22-626568 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:22-626756 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:22-627036 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:22-627229 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-627406 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-627592 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:22-627780 cadet-con-8620 DEBUG  C_P- 0x4d707d0 4
Jul 07 20:45:22-627961 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-628144 util-scheduler-8620 DEBUG Canceling task: 854 / 0x4d707d0
Jul 07 20:45:22-628353 util-scheduler-8620 DEBUG Adding task: 898 / 0x4d707d0
Jul 07 20:45:22-628598 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-629163 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-629413 cadet-p2p-8620 DEBUG Checking 0x5e0efe8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-629656 cadet-p2p-8620 DEBUG Checking 0x5e0efe8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-629836 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:22-630043 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:22-630255 util-scheduler-8620 DEBUG Adding task: 899 / 0x4d6ff98
Jul 07 20:45:22-630434 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:22-630610 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:22-630808 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:22-630991 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:22-631166 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:22-631404 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-631599 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:22-631776 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:22-632010 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-632203 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:22-632380 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:22-632992 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-633210 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:22-633391 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:22-633590 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:22-633848 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:22-634087 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:22-634292 util-scheduler-8620 DEBUG Adding task: 900 / 0x4d6ff98
Jul 07 20:45:22-634515 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-634728 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-634929 util-scheduler-8620 DEBUG Adding task: 901 / 0x46620a0
Jul 07 20:45:22-635129 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:22-635823 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-636024 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-636224 util-scheduler-8620 DEBUG Running task: 897 / 0x4662248
Jul 07 20:45:22-636781 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-636978 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-637211 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:22-638320 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:22-638509 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-638719 util-scheduler-8620 DEBUG Adding task: 902 / 0x46620a0
Jul 07 20:45:22-638972 util-scheduler-8620 DEBUG Checking readiness of task: 902 / 0x46620a0
Jul 07 20:45:22-639165 util-scheduler-8620 DEBUG Checking readiness of task: 901 / 0x46620a0
Jul 07 20:45:22-639357 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-639550 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-639740 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-639930 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-640504 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-640700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-640892 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-641085 util-scheduler-8620 DEBUG Running task: 901 / 0x46620a0
Jul 07 20:45:22-641295 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-641472 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-641643 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-641822 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-642035 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-642244 util-scheduler-8620 DEBUG Adding task: 903 / 0x46620a0
Jul 07 20:45:22-642442 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-642732 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-642927 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-643124 util-scheduler-8620 DEBUG Running task: 899 / 0x4d6ff98
Jul 07 20:45:22-643316 util-scheduler-8620 DEBUG Canceling task: 900 / 0x4d6ff98
Jul 07 20:45:22-643530 util-scheduler-8620 DEBUG Adding task: 904 / 0x4d6ff98
Jul 07 20:45:22-643748 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-644456 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:22-644703 util-scheduler-8620 DEBUG Checking readiness of task: 903 / 0x46620a0
Jul 07 20:45:22-644899 util-scheduler-8620 DEBUG Checking readiness of task: 902 / 0x46620a0
Jul 07 20:45:22-645102 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-645317 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-645508 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-645698 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-645888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-646078 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-646268 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-646477 util-scheduler-8620 DEBUG Running task: 903 / 0x46620a0
Jul 07 20:45:22-646662 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-646837 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-647006 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-647182 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-647389 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-647586 util-scheduler-8620 DEBUG Adding task: 905 / 0x46620a0
Jul 07 20:45:22-648194 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-648480 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-648677 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-648917 util-scheduler-8620 DEBUG Checking readiness of task: 905 / 0x46620a0
Jul 07 20:45:22-649110 util-scheduler-8620 DEBUG Checking readiness of task: 902 / 0x46620a0
Jul 07 20:45:22-649321 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-649514 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-649704 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-649894 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-650083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-650272 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-650461 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-650652 util-scheduler-8620 DEBUG Running task: 905 / 0x46620a0
Jul 07 20:45:22-650835 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-651010 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-651179 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-651360 util-scheduler-8620 DEBUG Canceling task: 866 / 0x4d5c9e8
Jul 07 20:45:22-651957 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:22-652177 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:22-652411 cadet-p2p-8620 DEBUG Checking 0x5e01980 towards HS92G30M (->KNAS)
Jul 07 20:45:22-652641 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:22-652818 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:22-653006 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:22-653302 cadet-p2p-8620 INFO snd {               ACK} ( 78) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:22-653496 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-653673 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-653940 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:22-654120 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:22-654305 cadet-con-8620 DEBUG  C_P- 0x4d61c30 3
Jul 07 20:45:22-654478 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-654700 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:22-654931 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-655114 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 16
Jul 07 20:45:22-655289 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-655895 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:22-656126 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-656308 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 16
Jul 07 20:45:22-656482 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-656648 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:22-656852 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:22-657063 util-scheduler-8620 DEBUG Adding task: 906 / 0x4d5c9e8
Jul 07 20:45:22-657269 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:22-657446 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:22-657660 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:22-657835 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:22-658009 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:22-658247 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:22-658441 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:22-658618 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:22-658851 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:22-659044 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:22-659601 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:22-659805 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:22-660009 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:22-660192 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:22-660394 util-scheduler-8620 DEBUG Adding task: 907 / 0x4d5c9e8
Jul 07 20:45:22-660609 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:22-660802 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-661001 util-scheduler-8620 DEBUG Adding task: 908 / 0x46620a0
Jul 07 20:45:22-661233 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:22-663510 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-663716 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-663962 util-scheduler-8620 DEBUG Checking readiness of task: 908 / 0x46620a0
Jul 07 20:45:22-664156 util-scheduler-8620 DEBUG Checking readiness of task: 902 / 0x46620a0
Jul 07 20:45:22-664347 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-664538 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-664728 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-664919 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-665109 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-665321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-665511 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-665703 util-scheduler-8620 DEBUG Running task: 908 / 0x46620a0
Jul 07 20:45:22-665888 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-666063 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-666233 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-666410 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-666601 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-667164 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-667464 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-667674 util-scheduler-8620 DEBUG Running task: 906 / 0x4d5c9e8
Jul 07 20:45:22-667866 util-scheduler-8620 DEBUG Canceling task: 907 / 0x4d5c9e8
Jul 07 20:45:22-668081 util-scheduler-8620 DEBUG Adding task: 909 / 0x4d5c9e8
Jul 07 20:45:22-668298 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:22-668492 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-668690 util-scheduler-8620 DEBUG Adding task: 910 / 0x46620a0
Jul 07 20:45:22-668930 util-scheduler-8620 DEBUG Checking readiness of task: 910 / 0x46620a0
Jul 07 20:45:22-669122 util-scheduler-8620 DEBUG Checking readiness of task: 902 / 0x46620a0
Jul 07 20:45:22-669334 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-669526 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-669716 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-669923 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-670124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-670314 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-670942 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-671190 util-scheduler-8620 DEBUG Running task: 902 / 0x46620a0
Jul 07 20:45:22-671595 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-671825 util-scheduler-8620 DEBUG Adding task: 911 / 0x4662248
Jul 07 20:45:22-672034 util-scheduler-8620 DEBUG Running task: 910 / 0x46620a0
Jul 07 20:45:22-672219 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-672395 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-672564 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-672740 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-672929 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-673117 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-673449 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-673698 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-673889 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-674079 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-674269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-674834 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-675027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-675218 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-675408 util-scheduler-8620 DEBUG Running task: 911 / 0x4662248
Jul 07 20:45:22-675608 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-675803 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-676017 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:22-676198 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-676400 util-scheduler-8620 DEBUG Adding task: 912 / 0x46620a0
Jul 07 20:45:22-676639 util-scheduler-8620 DEBUG Checking readiness of task: 912 / 0x46620a0
Jul 07 20:45:22-676831 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-677021 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-677234 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-677425 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-677614 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-677803 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-677993 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-678549 util-scheduler-8620 DEBUG Running task: 912 / 0x46620a0
Jul 07 20:45:22-678954 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-679177 util-scheduler-8620 DEBUG Adding task: 913 / 0x4662248
Jul 07 20:45:22-679424 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-679620 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-679810 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-679999 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-680188 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-680393 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-680584 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-680773 util-scheduler-8620 DEBUG Running task: 913 / 0x4662248
Jul 07 20:45:22-680961 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-681151 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-681385 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:22-681580 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-681777 util-scheduler-8620 DEBUG Adding task: 914 / 0x46620a0
Jul 07 20:45:22-682329 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-682533 util-scheduler-8620 DEBUG Adding task: 915 / 0x46620a0
Jul 07 20:45:22-682775 util-scheduler-8620 DEBUG Checking readiness of task: 915 / 0x46620a0
Jul 07 20:45:22-682967 util-scheduler-8620 DEBUG Checking readiness of task: 914 / 0x46620a0
Jul 07 20:45:22-683158 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-683348 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-683537 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-683727 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-683917 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-684108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-684297 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-684488 util-scheduler-8620 DEBUG Running task: 914 / 0x46620a0
Jul 07 20:45:22-684671 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-684846 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-685015 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-685217 util-scheduler-8620 DEBUG Canceling task: 909 / 0x4d5c9e8
Jul 07 20:45:22-685437 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:22-685651 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:22-686271 cadet-p2p-8620 DEBUG Checking 0x5b94da0 towards HS92G30M (->KNAS)
Jul 07 20:45:22-686515 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-686698 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 16
Jul 07 20:45:22-686873 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-687092 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:22-687269 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:22-687443 cadet-p2p-8620 DEBUG   payload ID 17
Jul 07 20:45:22-687722 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:45:22-687916 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-688092 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-688278 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:22-688450 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:22-688618 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:22-688807 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:45:22-688995 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:45:22-689208 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:22-689439 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:22-689992 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:22-690229 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:45:22-690406 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:22-690608 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:22-690785 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:22-690960 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:22-691161 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:22-691358 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:22-691542 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:22-691723 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:22-691900 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:22-692071 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:22-692289 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:22-692461 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:22-692697 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:22-692882 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:22-693062 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-693273 util-scheduler-8620 DEBUG Canceling task: 797 / 0x4d61c30
Jul 07 20:45:22-693849 util-scheduler-8620 DEBUG Adding task: 916 / 0x4d61c30
Jul 07 20:45:22-694100 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-694280 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:45:22-694472 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 17
Jul 07 20:45:22-694645 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-694868 cadet-p2p-8620 DEBUG Checking 0x5ba0380 towards HS92G30M (->KNAS)
Jul 07 20:45:22-695098 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-695279 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 17
Jul 07 20:45:22-695452 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-695679 cadet-p2p-8620 DEBUG Checking 0x5ba0380 towards HS92G30M (->KNAS)
Jul 07 20:45:22-695969 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-696152 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 17
Jul 07 20:45:22-696325 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-696490 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:22-696693 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:45:22-696904 util-scheduler-8620 DEBUG Adding task: 917 / 0x4d5c9e8
Jul 07 20:45:22-697082 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:22-697278 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:22-697477 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:22-697652 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:22-697826 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:22-698064 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:22-698257 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:22-698434 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:22-698632 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:22-698833 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:45:22-699015 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:22-699215 util-scheduler-8620 DEBUG Adding task: 918 / 0x4d5c9e8
Jul 07 20:45:22-699792 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:22-699991 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-700195 util-scheduler-8620 DEBUG Adding task: 919 / 0x46620a0
Jul 07 20:45:22-700394 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:22-703212 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-703497 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-703782 util-scheduler-8620 DEBUG Checking readiness of task: 919 / 0x46620a0
Jul 07 20:45:22-703986 util-scheduler-8620 DEBUG Checking readiness of task: 915 / 0x46620a0
Jul 07 20:45:22-704185 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-704384 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-704578 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-704776 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-704998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-705286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-705495 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-705697 util-scheduler-8620 DEBUG Running task: 919 / 0x46620a0
Jul 07 20:45:22-705893 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-706080 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-706263 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-706448 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-706655 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-707257 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-707629 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-707860 util-scheduler-8620 DEBUG Running task: 917 / 0x4d5c9e8
Jul 07 20:45:22-708067 util-scheduler-8620 DEBUG Canceling task: 918 / 0x4d5c9e8
Jul 07 20:45:22-708323 util-scheduler-8620 DEBUG Adding task: 920 / 0x4d5c9e8
Jul 07 20:45:22-708563 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:22-708771 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-708984 util-scheduler-8620 DEBUG Adding task: 921 / 0x46620a0
Jul 07 20:45:22-709288 util-scheduler-8620 DEBUG Checking readiness of task: 921 / 0x46620a0
Jul 07 20:45:22-709493 util-scheduler-8620 DEBUG Checking readiness of task: 915 / 0x46620a0
Jul 07 20:45:22-710104 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-710313 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-710573 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-710833 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-711038 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-711234 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-711424 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-711618 util-scheduler-8620 DEBUG Running task: 915 / 0x46620a0
Jul 07 20:45:22-712030 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-712275 util-scheduler-8620 DEBUG Adding task: 922 / 0x4662248
Jul 07 20:45:22-712491 util-scheduler-8620 DEBUG Running task: 921 / 0x46620a0
Jul 07 20:45:22-712676 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-712853 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-713024 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-713225 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-713421 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-713611 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-713844 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-714098 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-714289 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-714919 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-715454 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-715654 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-715906 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-716102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-716296 util-scheduler-8620 DEBUG Running task: 922 / 0x4662248
Jul 07 20:45:22-716515 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-716715 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-716946 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:22-717131 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-717370 util-scheduler-8620 DEBUG Adding task: 923 / 0x46620a0
Jul 07 20:45:22-717623 util-scheduler-8620 DEBUG Checking readiness of task: 923 / 0x46620a0
Jul 07 20:45:22-717815 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-718004 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-718193 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-718382 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-718570 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-718759 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-718947 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-719137 util-scheduler-8620 DEBUG Running task: 923 / 0x46620a0
Jul 07 20:45:22-719544 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-719773 util-scheduler-8620 DEBUG Adding task: 924 / 0x4662248
Jul 07 20:45:22-720019 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-720210 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-720399 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-720602 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-720791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-720979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-721180 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-721390 util-scheduler-8620 DEBUG Running task: 924 / 0x4662248
Jul 07 20:45:22-721577 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-721767 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-722351 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:22-722558 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-722763 util-scheduler-8620 DEBUG Adding task: 925 / 0x46620a0
Jul 07 20:45:22-722948 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-723144 util-scheduler-8620 DEBUG Adding task: 926 / 0x46620a0
Jul 07 20:45:22-723384 util-scheduler-8620 DEBUG Checking readiness of task: 926 / 0x46620a0
Jul 07 20:45:22-723575 util-scheduler-8620 DEBUG Checking readiness of task: 925 / 0x46620a0
Jul 07 20:45:22-723765 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-723954 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-724145 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-724335 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-724526 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-724715 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-724905 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-725096 util-scheduler-8620 DEBUG Running task: 925 / 0x46620a0
Jul 07 20:45:22-725302 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-725478 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-725648 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-725835 util-scheduler-8620 DEBUG Canceling task: 920 / 0x4d5c9e8
Jul 07 20:45:22-726056 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:45:22-726293 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:22-726534 cadet-p2p-8620 DEBUG Checking 0x5ba0380 towards HS92G30M (->KNAS)
Jul 07 20:45:22-726765 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:22-726946 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 17
Jul 07 20:45:22-727121 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:22-727350 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:22-727530 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:45:22-727706 cadet-p2p-8620 DEBUG   payload ID 18
Jul 07 20:45:22-728014 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 96)
Jul 07 20:45:22-728215 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-728401 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-728595 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:22-728778 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:22-728953 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:22-729148 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:22-729362 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:45:22-730088 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 925 ms
Jul 07 20:45:22-730286 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:22-730500 cadet-chn-8620 DEBUG !! using delay 3701864 µs
Jul 07 20:45:22-730727 util-scheduler-8620 DEBUG Adding task: 927 / 0x4d63a48
Jul 07 20:45:22-730943 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:22-731192 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:22-731374 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:22-731552 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:45:22-731729 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:22-731933 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:22-732112 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:22-732291 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:22-732494 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:22-733638 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:22-733843 cadet-tun-8620 DEBUG TTT  kx_ctx 0x4d89c80, rekey_task 0
Jul 07 20:45:22-734027 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:22-734285 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:22-734551 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:22-734785 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:22-734959 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:22-735195 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:22-735380 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:22-735561 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-735756 util-scheduler-8620 DEBUG Canceling task: 916 / 0x4d61c30
Jul 07 20:45:22-735974 util-scheduler-8620 DEBUG Adding task: 928 / 0x4d61c30
Jul 07 20:45:22-736222 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-736400 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 1
Jul 07 20:45:22-736577 cadet-con-8620 DEBUG !   accounting pid 18
Jul 07 20:45:22-736748 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-736934 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:45:22-737563 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:22-737744 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:22-737919 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:22-738120 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:22-738326 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 96 bytes.
Jul 07 20:45:22-738509 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:45:22-738689 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-738881 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:45:22-739700 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-739983 util-scheduler-8620 DEBUG Checking readiness of task: 926 / 0x46620a0
Jul 07 20:45:22-740180 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-740371 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-740560 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-740749 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-740938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-741127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-741339 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-741531 util-scheduler-8620 DEBUG Running task: 926 / 0x46620a0
Jul 07 20:45:22-741936 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-742173 util-scheduler-8620 DEBUG Adding task: 929 / 0x4662248
Jul 07 20:45:22-742422 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-742626 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-742816 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-743005 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-743193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-743382 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-743570 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-743759 util-scheduler-8620 DEBUG Running task: 929 / 0x4662248
Jul 07 20:45:22-743949 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-744145 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-744362 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-744946 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-745159 util-scheduler-8620 DEBUG Adding task: 930 / 0x46620a0
Jul 07 20:45:22-745420 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-745635 util-scheduler-8620 DEBUG Adding task: 931 / 0x46620a0
Jul 07 20:45:22-745890 util-scheduler-8620 DEBUG Checking readiness of task: 931 / 0x46620a0
Jul 07 20:45:22-746091 util-scheduler-8620 DEBUG Checking readiness of task: 930 / 0x46620a0
Jul 07 20:45:22-746303 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-746498 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-746694 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-746891 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-747086 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-747386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-747580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-747781 util-scheduler-8620 DEBUG Running task: 930 / 0x46620a0
Jul 07 20:45:22-747973 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-748160 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-748338 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-748535 util-scheduler-8620 DEBUG Canceling task: 904 / 0x4d6ff98
Jul 07 20:45:22-748774 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:22-748998 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:22-749272 cadet-p2p-8620 DEBUG Checking 0x5e0efe8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-749521 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:22-749730 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:22-749926 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:22-750225 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:22-750425 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-750609 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-750804 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:22-750997 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:22-751179 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-751372 util-scheduler-8620 DEBUG Canceling task: 898 / 0x4d707d0
Jul 07 20:45:22-751591 util-scheduler-8620 DEBUG Adding task: 932 / 0x4d707d0
Jul 07 20:45:22-751940 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-752524 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-752766 cadet-p2p-8620 DEBUG Checking 0x5e10658 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-753021 cadet-p2p-8620 DEBUG Checking 0x5e10658 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-753221 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:22-753432 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:22-753652 util-scheduler-8620 DEBUG Adding task: 933 / 0x4d6ff98
Jul 07 20:45:22-753831 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:22-754008 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:22-754206 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:22-754380 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:22-754553 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:22-754792 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-754987 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:22-755164 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:22-755397 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-755589 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:22-755765 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:22-755962 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:22-756165 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:22-756347 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:22-756550 util-scheduler-8620 DEBUG Adding task: 934 / 0x4d6ff98
Jul 07 20:45:22-756769 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-756968 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-757172 util-scheduler-8620 DEBUG Adding task: 935 / 0x46620a0
Jul 07 20:45:22-757410 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:22-761672 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-761892 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-762162 util-scheduler-8620 DEBUG Checking readiness of task: 935 / 0x46620a0
Jul 07 20:45:22-762357 util-scheduler-8620 DEBUG Checking readiness of task: 931 / 0x46620a0
Jul 07 20:45:22-762548 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-762738 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-762928 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-763118 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-763308 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-763498 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-763687 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-763880 util-scheduler-8620 DEBUG Running task: 935 / 0x46620a0
Jul 07 20:45:22-764065 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-764243 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-764438 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-764620 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-764820 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-765014 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-765340 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-765565 util-scheduler-8620 DEBUG Running task: 933 / 0x4d6ff98
Jul 07 20:45:22-765786 util-scheduler-8620 DEBUG Canceling task: 934 / 0x4d6ff98
Jul 07 20:45:22-766016 util-scheduler-8620 DEBUG Adding task: 936 / 0x4d6ff98
Jul 07 20:45:22-766248 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-766455 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-766663 util-scheduler-8620 DEBUG Adding task: 937 / 0x46620a0
Jul 07 20:45:22-766928 util-scheduler-8620 DEBUG Checking readiness of task: 937 / 0x46620a0
Jul 07 20:45:22-767128 util-scheduler-8620 DEBUG Checking readiness of task: 931 / 0x46620a0
Jul 07 20:45:22-767324 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-767520 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-768199 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-768409 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-768607 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-768803 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-768999 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-769224 util-scheduler-8620 DEBUG Running task: 931 / 0x46620a0
Jul 07 20:45:22-769651 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-769913 util-scheduler-8620 DEBUG Adding task: 938 / 0x4662248
Jul 07 20:45:22-770134 util-scheduler-8620 DEBUG Running task: 937 / 0x46620a0
Jul 07 20:45:22-770327 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-770508 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-770682 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-770865 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-771061 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-771251 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-771660 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-771944 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-772142 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-772332 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-772521 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-772710 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-772899 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-773087 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-773301 util-scheduler-8620 DEBUG Running task: 938 / 0x4662248
Jul 07 20:45:22-773504 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-773701 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-773926 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-774108 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-774319 util-scheduler-8620 DEBUG Adding task: 939 / 0x46620a0
Jul 07 20:45:22-774559 util-scheduler-8620 DEBUG Checking readiness of task: 939 / 0x46620a0
Jul 07 20:45:22-774780 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-774970 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-775158 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-775738 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-775930 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-776121 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-776310 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-776501 util-scheduler-8620 DEBUG Running task: 939 / 0x46620a0
Jul 07 20:45:22-776903 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-777132 util-scheduler-8620 DEBUG Adding task: 940 / 0x4662248
Jul 07 20:45:22-777406 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-777635 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-777825 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-778013 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-778201 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-778390 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-778579 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-778767 util-scheduler-8620 DEBUG Running task: 940 / 0x4662248
Jul 07 20:45:22-778954 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-779145 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-779356 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-779559 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-779758 util-scheduler-8620 DEBUG Adding task: 941 / 0x46620a0
Jul 07 20:45:22-779942 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-780138 util-scheduler-8620 DEBUG Adding task: 942 / 0x46620a0
Jul 07 20:45:22-780376 util-scheduler-8620 DEBUG Checking readiness of task: 942 / 0x46620a0
Jul 07 20:45:22-780567 util-scheduler-8620 DEBUG Checking readiness of task: 941 / 0x46620a0
Jul 07 20:45:22-780757 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-780945 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-781133 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-781346 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-781535 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-781724 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-781912 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-782101 util-scheduler-8620 DEBUG Running task: 941 / 0x46620a0
Jul 07 20:45:22-782285 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-782460 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-782629 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-783170 util-scheduler-8620 DEBUG Canceling task: 936 / 0x4d6ff98
Jul 07 20:45:22-783401 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:22-783623 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:22-783869 cadet-p2p-8620 DEBUG Checking 0x5e10658 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-784105 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:22-784291 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:22-784488 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:22-784784 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:22-785009 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-785227 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-785425 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:22-785619 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:22-785802 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-785998 util-scheduler-8620 DEBUG Canceling task: 932 / 0x4d707d0
Jul 07 20:45:22-786222 util-scheduler-8620 DEBUG Adding task: 943 / 0x4d707d0
Jul 07 20:45:22-786482 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-786660 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-786893 cadet-p2p-8620 DEBUG Checking 0x5e170f8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-787155 cadet-p2p-8620 DEBUG Checking 0x5e170f8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-787342 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:22-787555 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:22-787785 util-scheduler-8620 DEBUG Adding task: 944 / 0x4d6ff98
Jul 07 20:45:22-787970 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:22-788153 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:22-788359 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:22-788538 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:22-788717 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:22-788967 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:22-789166 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:22-789380 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:22-789590 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:22-789798 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:22-789982 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:22-790191 util-scheduler-8620 DEBUG Adding task: 945 / 0x4d6ff98
Jul 07 20:45:22-790953 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-791312 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-791633 util-scheduler-8620 DEBUG Adding task: 946 / 0x46620a0
Jul 07 20:45:22-791840 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:22-793874 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-794097 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:22-794370 util-scheduler-8620 DEBUG Checking readiness of task: 946 / 0x46620a0
Jul 07 20:45:22-794566 util-scheduler-8620 DEBUG Checking readiness of task: 942 / 0x46620a0
Jul 07 20:45:22-794834 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-795026 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-795216 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-795405 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-795595 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-795784 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-795973 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-796166 util-scheduler-8620 DEBUG Running task: 946 / 0x46620a0
Jul 07 20:45:22-796351 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-796529 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-796700 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-796879 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-797075 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-797285 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-797582 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-798167 util-scheduler-8620 DEBUG Running task: 944 / 0x4d6ff98
Jul 07 20:45:22-798366 util-scheduler-8620 DEBUG Canceling task: 945 / 0x4d6ff98
Jul 07 20:45:22-798588 util-scheduler-8620 DEBUG Adding task: 947 / 0x4d6ff98
Jul 07 20:45:22-798822 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:22-799033 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-800785 util-scheduler-8620 DEBUG Adding task: 948 / 0x46620a0
Jul 07 20:45:22-801036 util-scheduler-8620 DEBUG Checking readiness of task: 948 / 0x46620a0
Jul 07 20:45:22-801251 util-scheduler-8620 DEBUG Checking readiness of task: 942 / 0x46620a0
Jul 07 20:45:22-801444 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-801634 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-801823 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-802012 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-802202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-802392 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-802580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-802771 util-scheduler-8620 DEBUG Running task: 942 / 0x46620a0
Jul 07 20:45:22-803175 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-803406 util-scheduler-8620 DEBUG Adding task: 949 / 0x4662248
Jul 07 20:45:22-803616 util-scheduler-8620 DEBUG Running task: 948 / 0x46620a0
Jul 07 20:45:22-803800 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-803975 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-804149 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-804329 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:22-804524 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-804721 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:22-805049 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:22-805779 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-806000 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-806199 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-806395 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-806592 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-806789 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-806985 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-807184 util-scheduler-8620 DEBUG Running task: 949 / 0x4662248
Jul 07 20:45:22-807382 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-807584 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-807819 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-808008 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-808230 util-scheduler-8620 DEBUG Adding task: 950 / 0x46620a0
Jul 07 20:45:22-808497 util-scheduler-8620 DEBUG Checking readiness of task: 950 / 0x46620a0
Jul 07 20:45:22-808698 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-808893 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-809088 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-809311 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-809534 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-809731 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-809925 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-810120 util-scheduler-8620 DEBUG Running task: 950 / 0x46620a0
Jul 07 20:45:22-810537 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:22-810780 util-scheduler-8620 DEBUG Adding task: 951 / 0x4662248
Jul 07 20:45:22-811153 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-811358 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-811549 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-811738 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-811927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-812131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-812319 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-812510 util-scheduler-8620 DEBUG Running task: 951 / 0x4662248
Jul 07 20:45:22-812705 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:22-813355 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:22-813586 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:22-815733 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:22-815968 util-scheduler-8620 DEBUG Adding task: 952 / 0x46620a0
Jul 07 20:45:22-816156 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:22-816360 util-scheduler-8620 DEBUG Adding task: 953 / 0x46620a0
Jul 07 20:45:22-816613 util-scheduler-8620 DEBUG Checking readiness of task: 953 / 0x46620a0
Jul 07 20:45:22-816805 util-scheduler-8620 DEBUG Checking readiness of task: 952 / 0x46620a0
Jul 07 20:45:22-816996 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:22-817185 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:22-817396 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:22-817585 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:22-817774 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:22-817963 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:22-818152 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:22-818343 util-scheduler-8620 DEBUG Running task: 952 / 0x46620a0
Jul 07 20:45:22-818529 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:22-818706 util-8620 DEBUG process_notify is running
Jul 07 20:45:22-818877 util-8620 DEBUG client_notify is running
Jul 07 20:45:22-819065 util-scheduler-8620 DEBUG Canceling task: 947 / 0x4d6ff98
Jul 07 20:45:22-819288 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:22-819509 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:22-819799 cadet-p2p-8620 DEBUG Checking 0x5e170f8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:22-820036 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:22-820213 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:22-820403 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:22-820686 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:22-820880 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:22-821060 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:22-821267 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:22-821455 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:22-821633 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:22-821817 util-scheduler-8620 DEBUG Canceling task: 943 / 0x4d707d0
Jul 07 20:45:22-822050 util-scheduler-8620 DEBUG Adding task: 954 / 0x4d707d0
Jul 07 20:45:22-822299 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:22-822470 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:22-822650 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:22-822849 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:22-823023 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:22-823197 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:22-823396 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:22-823616 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:22-823799 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:22-823977 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:22-824167 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:22-825616 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:23-980672 util-scheduler-8620 DEBUG Checking readiness of task: 953 / 0x46620a0
Jul 07 20:45:23-981059 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:23-981284 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:23-981482 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:23-981909 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:23-982107 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:23-982300 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:23-982491 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:23-982689 util-scheduler-8620 DEBUG Running task: 953 / 0x46620a0
Jul 07 20:45:23-983117 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:23-983377 util-scheduler-8620 DEBUG Adding task: 955 / 0x4662248
Jul 07 20:45:23-983663 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:23-983857 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:23-984049 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:23-984240 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:23-984431 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:23-984622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:23-984813 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:23-985004 util-scheduler-8620 DEBUG Running task: 955 / 0x4662248
Jul 07 20:45:23-985854 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:45:23-986628 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:45:23-987124 core-api-8620 DEBUG Received notification about connection from `D3TJ'.
Jul 07 20:45:23-987454 cadet-p2p-8620 INFO CONNECTED GN10 <= D3TJ
Jul 07 20:45:23-987796 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:23-988068 util-scheduler-8620 DEBUG Adding task: 956 / 0x4d5e5d8
Jul 07 20:45:23-988386 cadet-p2p-8620 DEBUG adding path [2] to peer D3TJ
Jul 07 20:45:23-989263 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:45:23-989449 cadet-p2p-8620 DEBUG   added last
Jul 07 20:45:23-989808 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:23-990502 util-scheduler-8620 DEBUG Adding task: 957 / 0x46620a0
Jul 07 20:45:23-990863 util-scheduler-8620 DEBUG Checking readiness of task: 957 / 0x46620a0
Jul 07 20:45:23-991080 util-scheduler-8620 DEBUG Checking readiness of task: 956 / 0x4d5e5d8
Jul 07 20:45:23-991276 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:23-991468 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:23-991691 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:23-991883 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:23-992074 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:23-992264 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:23-992454 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:23-992650 util-scheduler-8620 DEBUG Running task: 956 / 0x4d5e5d8
Jul 07 20:45:23-992837 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:23-993017 util-8620 DEBUG process_notify is running
Jul 07 20:45:23-993220 util-8620 DEBUG client_notify is running
Jul 07 20:45:23-993454 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:45:23-993772 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:24-136476 util-scheduler-8620 DEBUG Checking readiness of task: 957 / 0x46620a0
Jul 07 20:45:24-136798 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-136994 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-137186 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-137402 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-137593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-137783 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-137973 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-138167 util-scheduler-8620 DEBUG Running task: 957 / 0x46620a0
Jul 07 20:45:24-138583 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:24-138833 util-scheduler-8620 DEBUG Adding task: 958 / 0x4662248
Jul 07 20:45:24-139103 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-139295 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-139485 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-139675 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-139865 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-140055 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-140244 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-140433 util-scheduler-8620 DEBUG Running task: 958 / 0x4662248
Jul 07 20:45:24-140624 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:24-140823 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:24-141052 core-api-8620 DEBUG Received message of type 256 and size 100 from peer `D3TJ'
Jul 07 20:45:24-142810 cadet-con-8620 DEBUG     path has 2 hops.
Jul 07 20:45:24-143465 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection BFARXZN9 from D3TJ
Jul 07 20:45:24-144895 cadet-con-8620 DEBUG     origin: D3TJ
Jul 07 20:45:24-147978 cadet-con-8620 DEBUG   Creating path...
Jul 07 20:45:24-150623 cadet-con-8620 DEBUG   - 0: taking D3TJ
Jul 07 20:45:24-152927 cadet-con-8620 DEBUG     storing at 0
Jul 07 20:45:24-154047 cadet-con-8620 DEBUG   - 1: taking GN10
Jul 07 20:45:24-155095 cadet-con-8620 DEBUG     storing at 1
Jul 07 20:45:24-159154 cadet-con-8620 DEBUG   Own position: 1
Jul 07 20:45:24-161703 cadet-con-8620 DEBUG   Creating connection
Jul 07 20:45:24-166128 cadet-con-8620 DEBUG  get next hop BFARXZN9 [1/2]
Jul 07 20:45:24-166949 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:24-167235 cadet-con-8620 DEBUG  get prev hop BFARXZN9 [1/2]
Jul 07 20:45:24-168166 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:24-168379 cadet-con-8620 DEBUG register neighbors for connection BFARXZN9
Jul 07 20:45:24-168572 cadet-8620 DEBUG PATH:
Jul 07 20:45:24-169184 cadet-8620 DEBUG   D3TJ
Jul 07 20:45:24-169394 cadet-8620 DEBUG   GN10
Jul 07 20:45:24-169550 cadet-8620 DEBUG END
Jul 07 20:45:24-169722 cadet-con-8620 DEBUG own pos 1
Jul 07 20:45:24-170270 cadet-con-8620 DEBUG putting connection BFARXZN9 to next peer 0x4d5be88
Jul 07 20:45:24-170489 cadet-con-8620 DEBUG next peer 0x4d5be88 GN10
Jul 07 20:45:24-170688 cadet-con-8620 DEBUG putting connection BFARXZN9 to prev peer 0x4d6bdf8
Jul 07 20:45:24-170901 cadet-con-8620 DEBUG prev peer 0x4d6bdf8 D3TJ
Jul 07 20:45:24-171600 cadet-p2p-8620 DEBUG adding connection BFARXZN9
Jul 07 20:45:24-171808 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:45:24-172020 cadet-p2p-8620 DEBUG peer GN10 ok, has 3 connections.
Jul 07 20:45:24-172216 cadet-p2p-8620 DEBUG  now has 4 connections.
Jul 07 20:45:24-172392 cadet-p2p-8620 DEBUG result 1
Jul 07 20:45:24-172579 cadet-p2p-8620 DEBUG adding connection BFARXZN9
Jul 07 20:45:24-172781 cadet-p2p-8620 DEBUG to peer D3TJ
Jul 07 20:45:24-172984 cadet-p2p-8620 DEBUG peer D3TJ ok, has 0 connections.
Jul 07 20:45:24-173173 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:45:24-173388 cadet-p2p-8620 DEBUG result 1
Jul 07 20:45:24-174525 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:24-175598 util-scheduler-8620 DEBUG Adding task: 959 / 0x5e2cf38
Jul 07 20:45:24-176218 cadet-con-8620 DEBUG Connection BFARXZN9 state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:45:24-178183 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:45:24-180419 cadet-p2p-8620 DEBUG adding path [2] to peer D3TJ
Jul 07 20:45:24-180609 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:45:24-182350 cadet-p2p-8620 DEBUG   already known
Jul 07 20:45:24-183847 cadet-tun-8620 DEBUG add connection BFARXZN9 (->D3TJ)
Jul 07 20:45:24-184074 cadet-tun-8620 DEBUG  to tunnel D3TJ
Jul 07 20:45:24-184305 util-scheduler-8620 DEBUG Adding task: 960 / 0x5e2de48
Jul 07 20:45:24-185220 cadet-tun-8620 DEBUG Tunnel D3TJ cstate CADET_TUNNEL_NEW => CADET_TUNNEL_WAITING
Jul 07 20:45:24-185800 cadet-con-8620 INFO ===> {           FWD ACK} on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:24-186251 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:24-186468 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:24-186778 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 36)
Jul 07 20:45:24-186979 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:24-187212 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:24-187486 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:24-187683 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:24-188157 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 36 bytes
Jul 07 20:45:24-188452 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:45:24-188674 util-scheduler-8620 DEBUG Adding task: 961 / 0x5e2b838
Jul 07 20:45:24-188857 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:24-189064 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:24-189263 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:24-189441 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:24-189687 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:24-189874 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:24-190052 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:24-190254 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:24-190877 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_SENT -> CADET_CONNECTION_SENT
Jul 07 20:45:24-191505 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:45:24-192166 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:24-192391 util-scheduler-8620 DEBUG Adding task: 962 / 0x46620a0
Jul 07 20:45:24-192659 util-scheduler-8620 DEBUG Checking readiness of task: 962 / 0x46620a0
Jul 07 20:45:24-192876 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-193069 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-193282 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-193474 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-193666 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-193866 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-194057 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-194249 util-scheduler-8620 DEBUG Running task: 961 / 0x5e2b838
Jul 07 20:45:24-194459 util-scheduler-8620 DEBUG Adding task: 963 / 0x5e2b838
Jul 07 20:45:24-194684 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:24-195050 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:24-195256 util-scheduler-8620 DEBUG Adding task: 964 / 0x46620a0
Jul 07 20:45:24-195457 util-scheduler-8620 DEBUG Running task: 960 / 0x5e2de48
Jul 07 20:45:24-195703 util-scheduler-8620 DEBUG Checking readiness of task: 964 / 0x46620a0
Jul 07 20:45:24-195901 util-scheduler-8620 DEBUG Checking readiness of task: 962 / 0x46620a0
Jul 07 20:45:24-196091 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-196282 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-196473 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-196664 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-196854 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-197045 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-197256 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-197451 util-scheduler-8620 DEBUG Running task: 964 / 0x46620a0
Jul 07 20:45:24-197637 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:24-197817 util-8620 DEBUG process_notify is running
Jul 07 20:45:24-197991 util-8620 DEBUG client_notify is running
Jul 07 20:45:24-198170 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:24-198369 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:24-198560 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:24-198873 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:24-199128 util-scheduler-8620 DEBUG Checking readiness of task: 962 / 0x46620a0
Jul 07 20:45:24-199321 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-199512 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-199703 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-199894 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-200084 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-200274 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-200465 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-200803 util-scheduler-8620 DEBUG Running task: 962 / 0x46620a0
Jul 07 20:45:24-201233 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:24-201468 util-scheduler-8620 DEBUG Adding task: 965 / 0x4662248
Jul 07 20:45:24-201718 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-201912 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-202102 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-202293 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-202500 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-202691 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-202881 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-203071 util-scheduler-8620 DEBUG Running task: 965 / 0x4662248
Jul 07 20:45:24-203264 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:24-203461 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:24-203678 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:24-203878 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:24-204078 util-scheduler-8620 DEBUG Adding task: 966 / 0x46620a0
Jul 07 20:45:24-204273 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:24-204523 util-scheduler-8620 DEBUG Adding task: 967 / 0x46620a0
Jul 07 20:45:24-204765 util-scheduler-8620 DEBUG Checking readiness of task: 967 / 0x46620a0
Jul 07 20:45:24-204958 util-scheduler-8620 DEBUG Checking readiness of task: 966 / 0x46620a0
Jul 07 20:45:24-205150 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-205364 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-205554 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-205744 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-205935 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-206125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-206314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-206506 util-scheduler-8620 DEBUG Running task: 966 / 0x46620a0
Jul 07 20:45:24-206691 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:24-206867 util-8620 DEBUG process_notify is running
Jul 07 20:45:24-207038 util-8620 DEBUG client_notify is running
Jul 07 20:45:24-207224 util-scheduler-8620 DEBUG Canceling task: 963 / 0x5e2b838
Jul 07 20:45:24-207448 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:45:24-207667 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:24-208186 cadet-p2p-8620 DEBUG Checking 0x5e2e6f0 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:24-208498 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:45:24-208680 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:45:24-208851 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:45:24-209025 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:45:24-209218 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:45:24-209492 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 36)
Jul 07 20:45:24-209688 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:24-209869 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:24-210167 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:45:24-210355 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 1
Jul 07 20:45:24-210929 util-scheduler-8620 DEBUG Adding task: 968 / 0x5e2cf38
Jul 07 20:45:24-211180 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:45:24-211355 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:24-211538 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:45:24-211740 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:24-211916 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:24-212091 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:24-212291 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:24-212497 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:45:24-212680 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:45:24-212860 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:24-213050 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:45:24-213328 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:24-527418 util-scheduler-8620 DEBUG Checking readiness of task: 967 / 0x46620a0
Jul 07 20:45:24-527786 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-527981 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-528172 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-528363 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-528553 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-528757 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-528948 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-529144 util-scheduler-8620 DEBUG Running task: 271 / 0x4d61838
Jul 07 20:45:24-530881 cadet-tun-8620 INFO finish KX for KNAS
Jul 07 20:45:24-986697 util-scheduler-8620 DEBUG Checking readiness of task: 967 / 0x46620a0
Jul 07 20:45:24-987027 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:24-987226 util-scheduler-8620 DEBUG Checking readiness of task: 846 / 0x4d5c418
Jul 07 20:45:24-987423 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:24-987616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:24-987809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:24-988004 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:24-988194 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:24-988391 util-scheduler-8620 DEBUG Running task: 846 / 0x4d5c418
Jul 07 20:45:24-988789 util-8620 DEBUG receive_ready read 48/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:45:24-989539 util-8620 DEBUG Server receives 48 bytes from `<unbound UNIX client>'.
Jul 07 20:45:24-990263 util-8620 DEBUG Server-mst receives 48 bytes with 0 bytes already in private buffer
Jul 07 20:45:24-990458 util-8620 DEBUG Server-mst has 48 bytes left in inbound buffer
Jul 07 20:45:24-990645 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:45:24-990837 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:45:24-991073 util-scheduler-8620 DEBUG Adding task: 969 / 0x4d5c578
Jul 07 20:45:24-991255 cadet-loc-8620 DEBUG 
Jul 07 20:45:24-991427 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:45:24-991602 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:45:24-991825 cadet-chn-8620 DEBUG   towards D3TJ:19
Jul 07 20:45:24-992259 cadet-p2p-8620 DEBUG peer_connect towards D3TJ
Jul 07 20:45:24-993866 cadet-p2p-8620 DEBUG  get - hello expired on Wed Dec 31 18:00:00 1969
Jul 07 20:45:24-994558 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:45:24-996585 cadet-p2p-8620 DEBUG   path to use:  GN10 D3TJ
Jul 07 20:45:24-997051 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:24-997294 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:24-997541 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:24-997755 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:24-997994 cadet-con-8620 DEBUG register neighbors for connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:24-998157 cadet-8620 DEBUG PATH:
Jul 07 20:45:24-998341 cadet-8620 DEBUG   GN10
Jul 07 20:45:24-998535 cadet-8620 DEBUG   D3TJ
Jul 07 20:45:24-998690 cadet-8620 DEBUG END
Jul 07 20:45:24-998859 cadet-con-8620 DEBUG own pos 0
Jul 07 20:45:24-999088 cadet-con-8620 DEBUG putting connection 1KSG9GE2 (->D3TJ) to next peer 0x4d6bdf8
Jul 07 20:45:24-999303 cadet-con-8620 DEBUG next peer 0x4d6bdf8 D3TJ
Jul 07 20:45:24-999546 cadet-con-8620 DEBUG putting connection 1KSG9GE2 (->D3TJ) to prev peer 0x4d5be88
Jul 07 20:45:24-999761 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:45:24-999995 cadet-p2p-8620 DEBUG adding connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-000234 cadet-p2p-8620 DEBUG to peer D3TJ
Jul 07 20:45:25-000441 cadet-p2p-8620 DEBUG peer D3TJ ok, has 1 connections.
Jul 07 20:45:25-000633 cadet-p2p-8620 DEBUG  now has 2 connections.
Jul 07 20:45:25-000808 cadet-p2p-8620 DEBUG result 1
Jul 07 20:45:25-001029 cadet-p2p-8620 DEBUG adding connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-001260 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:45:25-001465 cadet-p2p-8620 DEBUG peer GN10 ok, has 4 connections.
Jul 07 20:45:25-001656 cadet-p2p-8620 DEBUG  now has 5 connections.
Jul 07 20:45:25-001832 cadet-p2p-8620 DEBUG result 1
Jul 07 20:45:25-002059 cadet-tun-8620 DEBUG add connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-002263 cadet-tun-8620 DEBUG  to tunnel D3TJ
Jul 07 20:45:25-003194 util-scheduler-8620 DEBUG Adding task: 970 / 0x5e2de48
Jul 07 20:45:25-003484 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 1KSG9GE2 (->D3TJ)  (100 bytes)
Jul 07 20:45:25-003681 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0 (create)
Jul 07 20:45:25-003919 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:25-004129 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:25-004432 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 100)
Jul 07 20:45:25-004635 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:25-004868 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-005056 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:25-005272 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:25-005487 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 100 bytes
Jul 07 20:45:25-005707 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `D3TJ'
Jul 07 20:45:25-005928 util-scheduler-8620 DEBUG Adding task: 971 / 0x5e2b838
Jul 07 20:45:25-006112 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:25-006321 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:25-006500 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:25-006679 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:25-006924 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-007110 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:25-007291 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:25-007496 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:25-007739 cadet-con-8620 DEBUG Connection 1KSG9GE2 (->D3TJ) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:45:25-008029 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:25-008253 util-scheduler-8620 DEBUG Adding task: 972 / 0x4d5e5d8
Jul 07 20:45:25-008471 cadet-tun-8620 DEBUG Adding channel 0x5e336a0 to tunnel 0x5e2de48
Jul 07 20:45:25-008686 cadet-tun-8620 DEBUG  adding 0x5e339c8 to (nil)
Jul 07 20:45:25-008933 cadet-chn-8620 DEBUG CREATED CHANNEL D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:25-009185 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:25-009431 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:45:25-009637 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:25-009823 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:45:25-010013 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:25-010194 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:25-010374 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:25-010546 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:25-010765 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:25-010939 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:25-011188 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [1] buf: 11/11 (qn 0/0)
Jul 07 20:45:25-011551 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [2] buf: 11/11 (qn 0/0)
Jul 07 20:45:25-011744 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:25-011951 cadet-tun-8620 DEBUG queue data on Tunnel D3TJ
Jul 07 20:45:25-012155 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:25-012360 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:45:25-012546 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:25-012727 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:25-012906 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:25-013079 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:25-013323 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:25-013498 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:25-013732 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [1] buf: 11/11 (qn 0/0)
Jul 07 20:45:25-013981 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [2] buf: 11/11 (qn 0/0)
Jul 07 20:45:25-014168 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:25-014384 util-scheduler-8620 DEBUG Canceling task: 969 / 0x4d5c578
Jul 07 20:45:25-014582 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:45:25-014768 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:45:25-014979 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:45:25-015192 util-scheduler-8620 DEBUG Adding task: 973 / 0x4d5c418
Jul 07 20:45:25-015397 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:45:25-015699 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-015900 util-scheduler-8620 DEBUG Checking readiness of task: 972 / 0x4d5e5d8
Jul 07 20:45:25-016094 util-scheduler-8620 DEBUG Checking readiness of task: 967 / 0x46620a0
Jul 07 20:45:25-016288 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-016481 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-016677 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-016870 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-017062 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-017277 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-017474 util-scheduler-8620 DEBUG Running task: 967 / 0x46620a0
Jul 07 20:45:25-017891 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:25-018139 util-scheduler-8620 DEBUG Adding task: 974 / 0x4662248
Jul 07 20:45:25-018366 util-scheduler-8620 DEBUG Running task: 972 / 0x4d5e5d8
Jul 07 20:45:25-018561 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:25-018744 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-018922 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-019156 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:45:25-019465 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:25-019682 util-scheduler-8620 DEBUG Running task: 971 / 0x5e2b838
Jul 07 20:45:25-019897 util-scheduler-8620 DEBUG Adding task: 975 / 0x5e2b838
Jul 07 20:45:25-020128 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:25-020343 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:25-020549 util-scheduler-8620 DEBUG Adding task: 976 / 0x46620a0
Jul 07 20:45:25-020748 util-scheduler-8620 DEBUG Running task: 970 / 0x5e2de48
Jul 07 20:45:25-021312 util-scheduler-8620 DEBUG Checking readiness of task: 976 / 0x46620a0
Jul 07 20:45:25-021513 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-021707 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-021899 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-022091 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-022282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-022494 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-022686 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-022878 util-scheduler-8620 DEBUG Running task: 976 / 0x46620a0
Jul 07 20:45:25-023065 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:25-023242 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-023413 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-023593 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:25-023792 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:25-023984 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:25-024296 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:25-024506 util-scheduler-8620 DEBUG Running task: 974 / 0x4662248
Jul 07 20:45:25-024701 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:25-024901 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:25-025122 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:25-025405 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:25-025646 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:25-025876 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:25-026085 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:25-026331 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:25-026540 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:25-026728 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:25-026917 util-scheduler-8620 DEBUG Canceling task: 888 / 0x4d707d0
Jul 07 20:45:25-027137 util-scheduler-8620 DEBUG Adding task: 977 / 0x4d707d0
Jul 07 20:45:25-027317 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:25-027561 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:25-027769 util-scheduler-8620 DEBUG Adding task: 978 / 0x4d5e5d8
Jul 07 20:45:25-027951 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:25-028151 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:25-653721 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:25-654126 util-scheduler-8620 DEBUG Adding task: 979 / 0x46620a0
Jul 07 20:45:25-654428 util-scheduler-8620 DEBUG Checking readiness of task: 979 / 0x46620a0
Jul 07 20:45:25-654630 util-scheduler-8620 DEBUG Checking readiness of task: 978 / 0x4d5e5d8
Jul 07 20:45:25-654824 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-655016 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-655207 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-655398 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-655589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-655779 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-655969 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-656178 util-scheduler-8620 DEBUG Running task: 978 / 0x4d5e5d8
Jul 07 20:45:25-656366 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:25-656548 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-656723 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-656962 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:25-657245 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:25-657460 util-scheduler-8620 DEBUG Running task: 979 / 0x46620a0
Jul 07 20:45:25-657870 util-8620 DEBUG receive_ready read 156/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:25-658141 util-scheduler-8620 DEBUG Adding task: 980 / 0x4662248
Jul 07 20:45:25-658353 util-scheduler-8620 DEBUG Running task: 968 / 0x5e2cf38
Jul 07 20:45:25-659097 cadet-con-8620 DEBUG BCK keepalive for BFARXZN9 (->D3TJ)
Jul 07 20:45:25-659799 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-659999 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-660193 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-660386 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-660577 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-660769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-660964 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-661155 util-scheduler-8620 DEBUG Running task: 980 / 0x4662248
Jul 07 20:45:25-661377 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:25-661581 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:25-661799 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:25-662007 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:25-662211 util-scheduler-8620 DEBUG Adding task: 981 / 0x46620a0
Jul 07 20:45:25-662425 util-scheduler-8620 DEBUG Adding task: 982 / 0x4662248
Jul 07 20:45:25-662663 util-scheduler-8620 DEBUG Checking readiness of task: 981 / 0x46620a0
Jul 07 20:45:25-662856 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-663045 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-663234 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-663424 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-663614 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-663804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-663993 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-664184 util-scheduler-8620 DEBUG Running task: 981 / 0x46620a0
Jul 07 20:45:25-664370 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:25-664546 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-664718 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-664907 util-scheduler-8620 DEBUG Canceling task: 975 / 0x5e2b838
Jul 07 20:45:25-665131 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 100 bytes.
Jul 07 20:45:25-665378 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:25-665613 cadet-p2p-8620 DEBUG Checking 0x5e33060 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:25-665846 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:25-666024 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:25-666197 cadet-p2p-8620 DEBUG   path create
Jul 07 20:45:25-666367 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:45:25-666550 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:45:25-666817 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 100)
Jul 07 20:45:25-667023 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:25-667204 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:25-667392 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:45:25-667574 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:45:25-667785 util-scheduler-8620 DEBUG Adding task: 983 / 0x5e31aa0
Jul 07 20:45:25-668025 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:45:25-668198 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:25-668379 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:25-668581 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:25-668757 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:25-668933 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:25-669152 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:25-669386 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 100 bytes.
Jul 07 20:45:25-669570 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:25-669751 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:25-669942 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:25-670762 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:25-670981 util-scheduler-8620 DEBUG Running task: 982 / 0x4662248
Jul 07 20:45:25-671174 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:25-671369 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:25-671586 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:25-671840 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:25-672078 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:25-672324 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:25-672532 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:25-672780 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:25-672989 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:25-673176 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:25-673387 util-scheduler-8620 DEBUG Canceling task: 977 / 0x4d707d0
Jul 07 20:45:25-673607 util-scheduler-8620 DEBUG Adding task: 984 / 0x4d707d0
Jul 07 20:45:25-673787 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:25-674040 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:25-674253 util-scheduler-8620 DEBUG Adding task: 985 / 0x4d5e5d8
Jul 07 20:45:25-674435 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:25-674634 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:25-674821 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:25-675005 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:25-675173 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:25-678767 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:25-679616 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:25-679837 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:25-680133 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:25-680308 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:25-680494 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:25-684159 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:25-684748 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:25-684925 cadet-tun-8620 DEBUG   e sending 687858367
Jul 07 20:45:25-685135 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:25-685363 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:25-685593 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:25-685773 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:25-685995 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:25-686276 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:25-686474 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:25-686709 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:25-686916 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:25-687225 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:25-687424 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:25-687649 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:25-687833 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:25-688009 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:25-688216 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 48 bytes
Jul 07 20:45:25-688430 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:25-688676 util-scheduler-8620 DEBUG Adding task: 986 / 0x4d6ff98
Jul 07 20:45:25-688859 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:25-689064 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:25-689264 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:25-689451 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:25-689692 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:25-689888 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:25-690076 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:25-690281 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:25-690463 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:25-690672 util-scheduler-8620 DEBUG Adding task: 987 / 0x46620a0
Jul 07 20:45:25-690946 util-scheduler-8620 DEBUG Checking readiness of task: 987 / 0x46620a0
Jul 07 20:45:25-691143 util-scheduler-8620 DEBUG Checking readiness of task: 985 / 0x4d5e5d8
Jul 07 20:45:25-691340 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-691530 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-691720 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-692024 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-692431 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-692630 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-692823 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-693024 util-scheduler-8620 DEBUG Running task: 985 / 0x4d5e5d8
Jul 07 20:45:25-693244 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:25-693430 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-693608 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-693856 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:25-694114 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:25-694333 util-scheduler-8620 DEBUG Running task: 986 / 0x4d6ff98
Jul 07 20:45:25-694562 util-scheduler-8620 DEBUG Adding task: 988 / 0x4d6ff98
Jul 07 20:45:25-694799 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:25-695004 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:25-695213 util-scheduler-8620 DEBUG Adding task: 989 / 0x46620a0
Jul 07 20:45:25-695489 util-scheduler-8620 DEBUG Checking readiness of task: 989 / 0x46620a0
Jul 07 20:45:25-695685 util-scheduler-8620 DEBUG Checking readiness of task: 987 / 0x46620a0
Jul 07 20:45:25-695876 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-696131 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-696326 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-696517 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-696713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-696909 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-697103 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-697332 util-scheduler-8620 DEBUG Running task: 989 / 0x46620a0
Jul 07 20:45:25-697522 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:25-697707 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-697884 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-698066 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:25-698277 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:25-698472 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:25-698795 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:25-755667 util-scheduler-8620 DEBUG Checking readiness of task: 987 / 0x46620a0
Jul 07 20:45:25-755997 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-756192 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-756384 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-756576 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-756767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-756958 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-757166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-757384 util-scheduler-8620 DEBUG Running task: 987 / 0x46620a0
Jul 07 20:45:25-757802 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:25-758056 util-scheduler-8620 DEBUG Adding task: 990 / 0x4662248
Jul 07 20:45:25-758325 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-758516 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-758704 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-758894 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-759083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-759272 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-759460 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-759649 util-scheduler-8620 DEBUG Running task: 990 / 0x4662248
Jul 07 20:45:25-759841 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:25-760040 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:25-760273 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:25-760477 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:25-760683 util-scheduler-8620 DEBUG Adding task: 991 / 0x46620a0
Jul 07 20:45:25-760870 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:25-761075 util-scheduler-8620 DEBUG Adding task: 992 / 0x46620a0
Jul 07 20:45:25-763243 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:25-763454 util-scheduler-8620 DEBUG Checking readiness of task: 991 / 0x46620a0
Jul 07 20:45:25-763648 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:25-763839 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:25-764030 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:25-764220 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:25-764410 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:25-764600 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:25-764789 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:25-764981 util-scheduler-8620 DEBUG Running task: 991 / 0x46620a0
Jul 07 20:45:25-765167 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:25-765367 util-8620 DEBUG process_notify is running
Jul 07 20:45:25-765538 util-8620 DEBUG client_notify is running
Jul 07 20:45:25-765727 util-scheduler-8620 DEBUG Canceling task: 988 / 0x4d6ff98
Jul 07 20:45:25-765955 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:25-766177 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:25-766421 cadet-p2p-8620 DEBUG Checking 0x6085ca8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:25-766662 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:25-766842 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:25-767036 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:25-767357 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:25-767555 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:25-767738 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:25-767933 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:25-768128 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:25-768311 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:25-768504 util-scheduler-8620 DEBUG Canceling task: 954 / 0x4d707d0
Jul 07 20:45:25-768828 util-scheduler-8620 DEBUG Adding task: 993 / 0x4d707d0
Jul 07 20:45:25-769138 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:25-769341 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:25-769527 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:25-769732 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:25-769906 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:25-770080 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:25-770283 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:25-770487 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:25-770670 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:25-770850 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:25-771041 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:25-774636 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:26-433413 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-433782 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-433977 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-434169 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-434359 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-434551 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-434741 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-434931 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-435123 util-scheduler-8620 DEBUG Running task: 927 / 0x4d63a48
Jul 07 20:45:26-435311 cadet-chn-8620 DEBUG !!! RETRANSMIT 2
Jul 07 20:45:26-435602 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:26-435804 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:45:26-436006 cadet-chn-8620 DEBUG   using existing copy: 0x5b978b8 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:26-436195 cadet-chn-8620 DEBUG   new chq: 0x6088810
Jul 07 20:45:26-436401 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:26-436604 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:26-436784 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:26-436966 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:26-437145 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:26-437342 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:26-437512 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:26-437728 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:26-437900 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:26-438138 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:26-438322 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:26-438639 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:26-438821 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:26-439008 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:26-442759 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:26-443564 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:26-443746 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:26-443966 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:26-447234 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:26-447479 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:26-447661 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:26-447883 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:26-448077 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:26-448359 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (96 bytes)
Jul 07 20:45:26-448558 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:26-448735 cadet-con-8620 DEBUG last pid sent 18
Jul 07 20:45:26-448908 cadet-con-8620 DEBUG      ack recv 77
Jul 07 20:45:26-449080 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:26-449278 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:26-449514 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:26-449733 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:26-450049 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 96)
Jul 07 20:45:26-450247 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:26-450475 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:26-450657 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 18
Jul 07 20:45:26-450831 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:26-451042 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 96 bytes
Jul 07 20:45:26-451266 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:45:26-451504 util-scheduler-8620 DEBUG Adding task: 994 / 0x4d5c9e8
Jul 07 20:45:26-451694 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:26-451906 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:26-452090 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:26-452271 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:26-452517 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:26-452723 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:26-453002 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:26-453231 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:26-453511 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:26-453731 util-scheduler-8620 DEBUG Adding task: 995 / 0x4d5e5d8
Jul 07 20:45:26-454007 util-scheduler-8620 DEBUG Checking readiness of task: 995 / 0x4d5e5d8
Jul 07 20:45:26-454202 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-454392 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-454580 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-454769 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-454958 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-455146 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-455335 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-455523 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-455715 util-scheduler-8620 DEBUG Running task: 995 / 0x4d5e5d8
Jul 07 20:45:26-455901 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:26-456080 util-8620 DEBUG process_notify is running
Jul 07 20:45:26-456252 util-8620 DEBUG client_notify is running
Jul 07 20:45:26-456478 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:26-456789 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:26-457000 util-scheduler-8620 DEBUG Running task: 994 / 0x4d5c9e8
Jul 07 20:45:26-457232 util-scheduler-8620 DEBUG Adding task: 996 / 0x4d5c9e8
Jul 07 20:45:26-457493 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:26-457689 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:26-457888 util-scheduler-8620 DEBUG Adding task: 997 / 0x46620a0
Jul 07 20:45:26-458128 util-scheduler-8620 DEBUG Checking readiness of task: 997 / 0x46620a0
Jul 07 20:45:26-458320 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-458509 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-458697 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-458885 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-459074 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-459264 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-459452 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-459640 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-459829 util-scheduler-8620 DEBUG Running task: 997 / 0x46620a0
Jul 07 20:45:26-460012 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:26-460186 util-8620 DEBUG process_notify is running
Jul 07 20:45:26-460354 util-8620 DEBUG client_notify is running
Jul 07 20:45:26-460535 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:26-460729 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:26-460916 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:26-461235 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:26-668140 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-668498 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-668693 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-668885 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-669076 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-669288 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-669479 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-669669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-669861 util-scheduler-8620 DEBUG Running task: 983 / 0x5e31aa0
Jul 07 20:45:26-670130 cadet-con-8620 DEBUG FWD keepalive for 1KSG9GE2 (->D3TJ)
Jul 07 20:45:26-670306 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:45:26-670559 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 1KSG9GE2 (->D3TJ)  (100 bytes)
Jul 07 20:45:26-670751 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0 (create)
Jul 07 20:45:26-670988 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:26-671199 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:26-671508 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 100)
Jul 07 20:45:26-671709 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:26-671937 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:26-672127 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:26-672308 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:26-672520 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 100 bytes
Jul 07 20:45:26-672826 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `D3TJ'
Jul 07 20:45:26-673074 util-scheduler-8620 DEBUG Adding task: 998 / 0x5e2b838
Jul 07 20:45:26-673276 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:26-673481 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:26-673656 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:26-673832 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:26-674100 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:26-674283 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:26-674459 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:26-674673 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:26-674931 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-675123 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-675311 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-675500 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-675689 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-675877 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-676066 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-676253 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-676443 util-scheduler-8620 DEBUG Running task: 998 / 0x5e2b838
Jul 07 20:45:26-676651 util-scheduler-8620 DEBUG Adding task: 999 / 0x5e2b838
Jul 07 20:45:26-676872 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:26-677075 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:26-677301 util-scheduler-8620 DEBUG Adding task: 1000 / 0x46620a0
Jul 07 20:45:26-677543 util-scheduler-8620 DEBUG Checking readiness of task: 1000 / 0x46620a0
Jul 07 20:45:26-677736 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-677925 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-678113 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-678302 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-678489 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-678677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-678865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-679052 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-679243 util-scheduler-8620 DEBUG Running task: 1000 / 0x46620a0
Jul 07 20:45:26-679427 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:26-679605 util-8620 DEBUG process_notify is running
Jul 07 20:45:26-679775 util-8620 DEBUG client_notify is running
Jul 07 20:45:26-679954 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:26-680150 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:26-680341 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:26-680651 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:26-783277 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-783583 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-783783 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-783979 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-784175 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-784369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-784564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-784757 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-784950 util-scheduler-8620 DEBUG Running task: 882 / 0x5df6f20
Jul 07 20:45:26-800945 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-883890 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-884176 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-884429 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-884621 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-884811 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-885001 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-885372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-885571 util-scheduler-8620 DEBUG Running task: 891 / 0x4d64a70
Jul 07 20:45:26-885808 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:26-886066 cadet-tun-8620 DEBUG  kx started 1 m ago
Jul 07 20:45:26-887799 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:26-888129 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:26-888335 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:26-888569 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:26-888750 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:26-888971 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:26-889286 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:26-889485 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:26-889723 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:26-889930 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:26-890245 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:26-890550 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:26-890779 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:26-890963 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:26-891139 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:26-891346 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:45:26-891596 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:26-891825 util-scheduler-8620 DEBUG Adding task: 1001 / 0x4d6ff98
Jul 07 20:45:26-892005 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:26-892207 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:26-892382 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:26-892557 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:26-892806 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:26-893002 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:26-893179 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:26-893400 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:26-893605 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:26-893917 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:26-894117 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:26-894287 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:26-894468 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:26-897993 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:26-899320 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:26-899527 cadet-tun-8620 DEBUG   e sending 3497499373
Jul 07 20:45:26-899743 cadet-tun-8620 DEBUG   e towards 7KG4
Jul 07 20:45:26-899946 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:26-900149 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:26-900389 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:26-900575 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:26-900813 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:26-901222 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:26-901425 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:26-901661 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:26-901868 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:26-902191 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:26-902416 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:26-902640 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:26-902821 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:26-902996 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:26-903201 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:26-903402 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:26-903578 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:26-903753 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:26-903992 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:26-904186 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:26-904363 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:26-904596 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:26-904788 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:26-904964 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:26-905161 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:26-905434 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:26-905640 util-scheduler-8620 DEBUG Adding task: 1002 / 0x4d64a70
Jul 07 20:45:26-905907 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-906100 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-906289 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-906476 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-906665 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-906853 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-907040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-907228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-907418 util-scheduler-8620 DEBUG Running task: 1001 / 0x4d6ff98
Jul 07 20:45:26-907627 util-scheduler-8620 DEBUG Adding task: 1003 / 0x4d6ff98
Jul 07 20:45:26-907849 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:26-908061 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:26-908269 util-scheduler-8620 DEBUG Adding task: 1004 / 0x46620a0
Jul 07 20:45:26-908511 util-scheduler-8620 DEBUG Checking readiness of task: 1004 / 0x46620a0
Jul 07 20:45:26-908704 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-908892 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-909081 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-909290 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-909479 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-909668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-909857 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-910045 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-910234 util-scheduler-8620 DEBUG Running task: 1004 / 0x46620a0
Jul 07 20:45:26-910419 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:26-910597 util-8620 DEBUG process_notify is running
Jul 07 20:45:26-910768 util-8620 DEBUG client_notify is running
Jul 07 20:45:26-910946 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:26-911141 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:26-911330 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:26-911647 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:26-930754 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-931030 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-931224 util-scheduler-8620 DEBUG Checking readiness of task: 881 / 0x4663d68
Jul 07 20:45:26-931418 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-931608 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-931797 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-931988 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-932177 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-932368 util-scheduler-8620 DEBUG Running task: 881 / 0x4663d68
Jul 07 20:45:26-932781 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:26-933028 util-scheduler-8620 DEBUG Adding task: 1005 / 0x4663f10
Jul 07 20:45:26-933311 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:26-933503 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:26-933692 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:26-933881 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:26-934069 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:26-934259 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:26-934447 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:26-934636 util-scheduler-8620 DEBUG Running task: 1005 / 0x4663f10
Jul 07 20:45:26-934828 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:26-935024 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:26-935237 util-scheduler-8620 DEBUG Adding task: 1006 / 0x4663d68
Jul 07 20:45:26-935597 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:26-935930 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `P00P' with quota 33481
Jul 07 20:45:26-936127 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 bandwidth changed to 33481 Bps
Jul 07 20:45:26-936789 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 updated, have 16559 Bps, last update was 81 s ago
Jul 07 20:45:26-937027 util-scheduler-8620 DEBUG Adding task: 1007 / 0x4d6e518
Jul 07 20:45:27-203398 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-203767 util-scheduler-8620 DEBUG Checking readiness of task: 992 / 0x46620a0
Jul 07 20:45:27-203974 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-204179 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-204371 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-204562 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-204752 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-204942 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-205136 util-scheduler-8620 DEBUG Running task: 992 / 0x46620a0
Jul 07 20:45:27-205597 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:27-205851 util-scheduler-8620 DEBUG Adding task: 1008 / 0x4662248
Jul 07 20:45:27-206128 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-206320 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-206510 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-206701 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-206892 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-207084 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-207305 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-207502 util-scheduler-8620 DEBUG Running task: 1008 / 0x4662248
Jul 07 20:45:27-207694 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:27-207895 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:27-208130 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:27-208339 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:27-208550 util-scheduler-8620 DEBUG Adding task: 1009 / 0x46620a0
Jul 07 20:45:27-208739 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:27-208947 util-scheduler-8620 DEBUG Adding task: 1010 / 0x46620a0
Jul 07 20:45:27-210145 util-scheduler-8620 DEBUG Checking readiness of task: 1010 / 0x46620a0
Jul 07 20:45:27-210359 util-scheduler-8620 DEBUG Checking readiness of task: 1009 / 0x46620a0
Jul 07 20:45:27-210571 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-210764 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-210956 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-211146 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-211337 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-211528 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-211720 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-211914 util-scheduler-8620 DEBUG Running task: 1009 / 0x46620a0
Jul 07 20:45:27-212101 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:27-212281 util-8620 DEBUG process_notify is running
Jul 07 20:45:27-212743 util-8620 DEBUG client_notify is running
Jul 07 20:45:27-212944 util-scheduler-8620 DEBUG Canceling task: 999 / 0x5e2b838
Jul 07 20:45:27-213178 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 100 bytes.
Jul 07 20:45:27-213495 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:27-213740 cadet-p2p-8620 DEBUG Checking 0x6092e00 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:27-213979 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:27-214159 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:27-214337 cadet-p2p-8620 DEBUG   path create
Jul 07 20:45:27-214513 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:45:27-214697 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:45:27-214971 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 100)
Jul 07 20:45:27-215163 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:27-215343 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:27-215531 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:45:27-215716 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:45:27-215936 util-scheduler-8620 DEBUG Adding task: 1011 / 0x5e31aa0
Jul 07 20:45:27-216178 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:45:27-216365 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:27-216549 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:27-216751 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:27-216926 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:27-217103 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:27-217329 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:27-217537 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 100 bytes.
Jul 07 20:45:27-217722 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:27-217909 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:27-218105 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:27-218865 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:27-233882 util-scheduler-8620 DEBUG Checking readiness of task: 1010 / 0x46620a0
Jul 07 20:45:27-234172 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-234367 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-234558 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-234749 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-234939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-235129 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-235319 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-235513 util-scheduler-8620 DEBUG Running task: 1010 / 0x46620a0
Jul 07 20:45:27-235932 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:27-236180 util-scheduler-8620 DEBUG Adding task: 1012 / 0x4662248
Jul 07 20:45:27-236444 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-236636 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-236826 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-237015 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-237224 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-237415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-237603 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-237794 util-scheduler-8620 DEBUG Running task: 1012 / 0x4662248
Jul 07 20:45:27-237983 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:27-238181 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:27-238405 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:27-238669 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:27-238924 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-239132 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-239316 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:27-239488 cadet-con-8620 DEBUG   ACK 78 (was 77)
Jul 07 20:45:27-239717 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:27-239946 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-240151 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-240333 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:27-240509 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:27-240719 util-scheduler-8620 DEBUG Adding task: 1013 / 0x46620a0
Jul 07 20:45:27-246691 util-scheduler-8620 DEBUG Checking readiness of task: 1013 / 0x46620a0
Jul 07 20:45:27-246956 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-247152 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-247343 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-247533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-247722 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-247912 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-248101 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-248292 util-scheduler-8620 DEBUG Running task: 1013 / 0x46620a0
Jul 07 20:45:27-248700 util-8620 DEBUG receive_ready read 212/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:27-248934 util-scheduler-8620 DEBUG Adding task: 1014 / 0x4662248
Jul 07 20:45:27-249243 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-249437 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-249651 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-249842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-250031 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-250219 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-250408 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-250600 util-scheduler-8620 DEBUG Running task: 1014 / 0x4662248
Jul 07 20:45:27-250790 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:27-250989 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:27-251209 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:27-251458 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:27-251703 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-251910 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-252091 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:27-252263 cadet-con-8620 DEBUG   ACK 79 (was 78)
Jul 07 20:45:27-252488 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:27-252716 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-252921 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-253100 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:27-253321 util-scheduler-8620 DEBUG Adding task: 1015 / 0x4662248
Jul 07 20:45:27-253571 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-253762 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-253951 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-254142 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-254331 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-254519 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-254707 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-254895 util-scheduler-8620 DEBUG Running task: 1015 / 0x4662248
Jul 07 20:45:27-255083 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:27-255273 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:27-255486 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:27-255729 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:27-255962 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:27-256249 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-256459 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:27-256699 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-256906 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-257096 cadet-con-8620 DEBUG  PID 15 (expected 15+)
Jul 07 20:45:27-257299 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:27-257491 util-scheduler-8620 DEBUG Canceling task: 884 / 0x4d61c30
Jul 07 20:45:27-257716 util-scheduler-8620 DEBUG Adding task: 1016 / 0x4d61c30
Jul 07 20:45:27-257898 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:27-258160 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:27-258377 util-scheduler-8620 DEBUG Adding task: 1017 / 0x4d5e5d8
Jul 07 20:45:27-258563 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:27-258732 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:27-262448 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:27-263269 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:27-263472 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:27-266688 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:27-266899 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:45:27-267082 cadet-chn-8620 DEBUG   head 2, out!
Jul 07 20:45:27-267296 cadet-chn-8620 DEBUG free_sent_reliable 1 0
Jul 07 20:45:27-267481 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x5b978b8
Jul 07 20:45:27-267658 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:27-267826 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:27-267999 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:45:27-268205 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:27-268385 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:27-268569 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:27-268748 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:27-268924 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:27-269093 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:27-269332 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:27-269505 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:27-269740 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:27-269923 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:27-270101 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:45:27-270328 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:27-270506 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:27-270733 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:27-270907 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:27-271081 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:27-271253 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:27-271474 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:27-271651 cadet-con-8620 DEBUG  ACK 79
Jul 07 20:45:27-271830 cadet-con-8620 DEBUG  last pid 15, last ack 78, qmax 11, q 0
Jul 07 20:45:27-272097 cadet-con-8620 INFO --> {               ACK} ( 79) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:27-272293 cadet-con-8620 DEBUG  ack 79
Jul 07 20:45:27-272472 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:27-272711 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:27-272922 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:27-273262 cadet-p2p-8620 INFO que {               ACK} ( 79) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:27-273467 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:27-273695 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:27-273878 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 18
Jul 07 20:45:27-274054 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:27-274262 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:27-274470 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:27-274649 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:27-274826 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:27-275067 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:27-275252 cadet-p2p-8620 DEBUG QQQ    payload , 79
Jul 07 20:45:27-275428 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:27-275662 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:27-275855 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:27-276031 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:27-276229 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:27-276414 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:27-276626 util-scheduler-8620 DEBUG Adding task: 1018 / 0x46620a0
Jul 07 20:45:27-276898 util-scheduler-8620 DEBUG Checking readiness of task: 1018 / 0x46620a0
Jul 07 20:45:27-277095 util-scheduler-8620 DEBUG Checking readiness of task: 1017 / 0x4d5e5d8
Jul 07 20:45:27-277310 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-277500 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-277689 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-277898 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-278088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-278277 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-278465 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-278658 util-scheduler-8620 DEBUG Running task: 1017 / 0x4d5e5d8
Jul 07 20:45:27-278844 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:27-279022 util-8620 DEBUG process_notify is running
Jul 07 20:45:27-279194 util-8620 DEBUG client_notify is running
Jul 07 20:45:27-279648 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:27-279963 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:27-478296 util-scheduler-8620 DEBUG Checking readiness of task: 1018 / 0x46620a0
Jul 07 20:45:27-478648 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-478844 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-479037 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-479228 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-479419 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-479608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-479799 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-479994 util-scheduler-8620 DEBUG Running task: 1018 / 0x46620a0
Jul 07 20:45:27-480418 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:27-480677 util-scheduler-8620 DEBUG Adding task: 1019 / 0x4662248
Jul 07 20:45:27-480957 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-481152 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-481370 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-481562 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-481770 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-481963 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-482161 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-482358 util-scheduler-8620 DEBUG Running task: 1019 / 0x4662248
Jul 07 20:45:27-482555 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:27-482766 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:27-483004 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:27-483217 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:27-483441 util-scheduler-8620 DEBUG Adding task: 1020 / 0x46620a0
Jul 07 20:45:27-483632 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:27-483838 util-scheduler-8620 DEBUG Adding task: 1021 / 0x46620a0
Jul 07 20:45:27-484096 util-scheduler-8620 DEBUG Checking readiness of task: 1021 / 0x46620a0
Jul 07 20:45:27-484289 util-scheduler-8620 DEBUG Checking readiness of task: 1020 / 0x46620a0
Jul 07 20:45:27-484481 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-484670 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-484860 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-485048 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-485262 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-485451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-485667 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-485860 util-scheduler-8620 DEBUG Running task: 1020 / 0x46620a0
Jul 07 20:45:27-486045 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:27-486223 util-8620 DEBUG process_notify is running
Jul 07 20:45:27-486393 util-8620 DEBUG client_notify is running
Jul 07 20:45:27-486582 util-scheduler-8620 DEBUG Canceling task: 996 / 0x4d5c9e8
Jul 07 20:45:27-486807 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:45:27-487027 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:27-487267 cadet-p2p-8620 DEBUG Checking 0x60a9220 towards HS92G30M (->KNAS)
Jul 07 20:45:27-487505 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:27-487683 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:27-487874 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:27-488145 cadet-p2p-8620 INFO snd {               ACK} ( 79) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:27-488339 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:27-491421 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:27-491640 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:27-491818 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:27-492007 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:27-492182 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:27-492409 cadet-p2p-8620 DEBUG Checking 0x60912f8 towards HS92G30M (->KNAS)
Jul 07 20:45:27-492641 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:27-492824 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 18
Jul 07 20:45:27-492999 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:27-493249 cadet-p2p-8620 DEBUG Checking 0x60912f8 towards HS92G30M (->KNAS)
Jul 07 20:45:27-493491 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:27-493675 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 18
Jul 07 20:45:27-493849 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:27-494016 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:27-494225 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:45:27-494450 util-scheduler-8620 DEBUG Adding task: 1022 / 0x4d5c9e8
Jul 07 20:45:27-494630 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:27-494806 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:27-495004 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:27-495177 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:27-495352 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:27-495600 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:27-495799 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:27-495979 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:27-496182 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:27-496388 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:27-496573 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:27-496782 util-scheduler-8620 DEBUG Adding task: 1023 / 0x4d5c9e8
Jul 07 20:45:27-497006 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:27-497228 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:27-497435 util-scheduler-8620 DEBUG Adding task: 1024 / 0x46620a0
Jul 07 20:45:27-497640 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:27-498024 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:27-498227 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:27-498488 util-scheduler-8620 DEBUG Checking readiness of task: 1024 / 0x46620a0
Jul 07 20:45:27-498686 util-scheduler-8620 DEBUG Checking readiness of task: 1021 / 0x46620a0
Jul 07 20:45:27-498879 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-499096 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-499288 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-499479 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-499670 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-499860 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-500051 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-500245 util-scheduler-8620 DEBUG Running task: 1024 / 0x46620a0
Jul 07 20:45:27-500432 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:27-500610 util-8620 DEBUG process_notify is running
Jul 07 20:45:27-500786 util-8620 DEBUG client_notify is running
Jul 07 20:45:27-500967 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:27-501166 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:27-501381 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:27-501670 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:27-501882 util-scheduler-8620 DEBUG Running task: 1022 / 0x4d5c9e8
Jul 07 20:45:27-502078 util-scheduler-8620 DEBUG Canceling task: 1023 / 0x4d5c9e8
Jul 07 20:45:27-502296 util-scheduler-8620 DEBUG Adding task: 1025 / 0x4d5c9e8
Jul 07 20:45:27-502544 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:27-502742 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:27-502944 util-scheduler-8620 DEBUG Adding task: 1026 / 0x46620a0
Jul 07 20:45:27-503191 util-scheduler-8620 DEBUG Checking readiness of task: 1026 / 0x46620a0
Jul 07 20:45:27-503386 util-scheduler-8620 DEBUG Checking readiness of task: 1021 / 0x46620a0
Jul 07 20:45:27-503579 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:27-503771 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:27-503962 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:27-504153 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:27-504343 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:27-504533 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:27-504724 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:27-504916 util-scheduler-8620 DEBUG Running task: 1026 / 0x46620a0
Jul 07 20:45:27-505101 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:27-505299 util-8620 DEBUG process_notify is running
Jul 07 20:45:27-505470 util-8620 DEBUG client_notify is running
Jul 07 20:45:27-505648 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:27-505841 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:27-506029 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:27-506316 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:28-257767 util-scheduler-8620 DEBUG Checking readiness of task: 1021 / 0x46620a0
Jul 07 20:45:28-258146 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:28-258346 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:28-258539 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:28-258732 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:28-258924 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:28-259115 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:28-259307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:28-259533 util-scheduler-8620 DEBUG Running task: 1021 / 0x46620a0
Jul 07 20:45:28-259959 util-8620 DEBUG receive_ready read 512/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:28-260218 util-scheduler-8620 DEBUG Adding task: 1027 / 0x4662248
Jul 07 20:45:28-260498 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:28-260692 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:28-260883 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:28-261073 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:28-261289 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:28-261481 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:28-261671 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:28-261862 util-scheduler-8620 DEBUG Running task: 1027 / 0x4662248
Jul 07 20:45:28-262055 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:28-262259 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:28-262492 core-api-8620 DEBUG Received message of type 256 and size 100 from peer `D3TJ'
Jul 07 20:45:28-262867 cadet-con-8620 DEBUG     path has 2 hops.
Jul 07 20:45:28-263312 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection BFARXZN9 from D3TJ
Jul 07 20:45:28-263620 cadet-con-8620 DEBUG     origin: D3TJ
Jul 07 20:45:28-265245 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:45:28-265499 cadet-p2p-8620 DEBUG adding path [2] to peer D3TJ
Jul 07 20:45:28-265683 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:45:28-265953 cadet-p2p-8620 DEBUG   already known
Jul 07 20:45:28-266210 cadet-tun-8620 DEBUG add connection BFARXZN9 (->D3TJ)
Jul 07 20:45:28-266413 cadet-tun-8620 DEBUG  to tunnel D3TJ
Jul 07 20:45:28-267147 cadet-con-8620 INFO ===> {           FWD ACK} on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:28-267393 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:28-267604 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:28-267904 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 36)
Jul 07 20:45:28-268101 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:28-268329 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:28-268514 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:28-268690 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:28-268898 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 36 bytes
Jul 07 20:45:28-269114 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:45:28-269436 util-scheduler-8620 DEBUG Adding task: 1028 / 0x5e2b838
Jul 07 20:45:28-269670 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:28-269914 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:28-270091 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:28-270266 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:28-270506 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:28-270690 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:28-270866 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:28-271064 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:28-271298 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 20:45:28-271537 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:45:28-271768 util-scheduler-8620 DEBUG Adding task: 1029 / 0x4662248
Jul 07 20:45:28-272020 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:28-272213 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:28-272404 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:28-272615 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:28-272805 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:28-272994 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:28-273183 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:28-273408 util-scheduler-8620 DEBUG Running task: 1029 / 0x4662248
Jul 07 20:45:28-273597 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:45:28-273793 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:45:28-274007 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `D3TJ'
Jul 07 20:45:28-274256 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection BFARXZN9 from D3TJ
Jul 07 20:45:28-274468 cadet-con-8620 DEBUG   via peer D3TJ
Jul 07 20:45:28-274703 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:28-274910 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:28-275396 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:28-275609 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:28-276599 cadet-con-8620 DEBUG   ACK
Jul 07 20:45:28-277136 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:45:28-277591 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:28-277956 util-scheduler-8620 DEBUG Canceling task: 959 / 0x5e2cf38
Jul 07 20:45:28-278692 util-scheduler-8620 DEBUG Adding task: 1030 / 0x5e2cf38
Jul 07 20:45:28-279811 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:45:28-280320 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:28-280538 util-scheduler-8620 DEBUG Adding task: 1031 / 0x5e2cf38
Jul 07 20:45:28-280796 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:28-281260 cadet-tun-8620 DEBUG Tunnel D3TJ cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:45:28-281449 cadet-tun-8620 DEBUG   cstate triggered rekey
Jul 07 20:45:28-281651 cadet-tun-8620 INFO Re-key Tunnel D3TJ
Jul 07 20:45:28-281868 cadet-tun-8620 INFO   new kx ctx for D3TJ
Jul 07 20:45:28-408127 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:45:28-408857 cadet-tun-8620 INFO PE: 00000000
Jul 07 20:45:28-409129 cadet-tun-8620 INFO KM: SY1Y2DBY
Jul 07 20:45:28-409401 cadet-tun-8620 INFO EK: E7V1A0CE
Jul 07 20:45:28-409588 cadet-tun-8620 INFO DK: D3403W8W
Jul 07 20:45:28-409811 cadet-tun-8620 INFO ===> EPHM for D3TJ
Jul 07 20:45:28-410013 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:28-410217 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:28-410448 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 1
Jul 07 20:45:28-410909 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:28-411097 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:28-411321 cadet-tun-8620 DEBUG  selected: connection BFARXZN9 (->D3TJ)
Jul 07 20:45:28-411997 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection BFARXZN9 (->D3TJ) (196 bytes)
Jul 07 20:45:28-412204 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 1
Jul 07 20:45:28-412443 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:28-412651 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:28-412978 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) FWD towards D3TJ (size 196)
Jul 07 20:45:28-413178 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:28-413430 cadet-con-8620 DEBUG  checking sendability of FWD traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:28-413613 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:28-413789 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:28-413998 cadet-p2p-8620 DEBUG calling core tmt rdy towards GN10 for 196 bytes
Jul 07 20:45:28-414216 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `GN10'
Jul 07 20:45:28-414446 util-scheduler-8620 DEBUG Adding task: 1032 / 0x4d5bd30
Jul 07 20:45:28-414628 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:28-415237 cadet-p2p-8620 DEBUG QQQ Message queue towards GN10
Jul 07 20:45:28-415418 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:28-415595 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5bd5c
Jul 07 20:45:28-415837 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on BFARXZN9 (->D3TJ)
Jul 07 20:45:28-416031 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:28-416210 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:28-416409 cadet-p2p-8620 DEBUG QQQ End queue towards GN10
Jul 07 20:45:28-416658 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:28-416854 util-scheduler-8620 DEBUG Adding task: 1033 / 0x5e2de48
Jul 07 20:45:28-417070 util-scheduler-8620 DEBUG Adding task: 1034 / 0x4662248
Jul 07 20:45:28-417303 util-scheduler-8620 DEBUG Running task: 1028 / 0x5e2b838
Jul 07 20:45:28-417513 util-scheduler-8620 DEBUG Adding task: 1035 / 0x5e2b838
Jul 07 20:45:28-417735 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:28-417938 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:28-418523 util-scheduler-8620 DEBUG Adding task: 1036 / 0x46620a0
Jul 07 20:45:28-418795 util-scheduler-8620 DEBUG Checking readiness of task: 1036 / 0x46620a0
Jul 07 20:45:28-418994 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:28-419185 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:28-419375 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:28-419566 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:28-419757 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:28-419947 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:28-420137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:28-420329 util-scheduler-8620 DEBUG Running task: 1036 / 0x46620a0
Jul 07 20:45:28-420515 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:28-420695 util-8620 DEBUG process_notify is running
Jul 07 20:45:28-420867 util-8620 DEBUG client_notify is running
Jul 07 20:45:28-421047 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:28-421275 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:28-421886 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:28-422231 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:28-422443 util-scheduler-8620 DEBUG Running task: 1034 / 0x4662248
Jul 07 20:45:28-422636 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:28-422836 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:28-423056 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:28-423304 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from D3TJ
Jul 07 20:45:28-423541 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:28-423770 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:28-425300 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:28-425895 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:28-426096 util-scheduler-8620 DEBUG Canceling task: 1030 / 0x5e2cf38
Jul 07 20:45:28-426336 util-scheduler-8620 DEBUG Adding task: 1037 / 0x5e2cf38
Jul 07 20:45:28-426685 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:28-426949 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:28-427160 util-scheduler-8620 DEBUG Adding task: 1038 / 0x4d5e5d8
Jul 07 20:45:28-427343 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:28-427544 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:29-258654 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:45:29-259009 cadet-tun-8620 INFO PE: 7MSWP3MJ
Jul 07 20:45:29-259200 cadet-tun-8620 INFO KM: AQ4N22GZ
Jul 07 20:45:29-259415 cadet-tun-8620 INFO EK: QFKEV1JF
Jul 07 20:45:29-259602 cadet-tun-8620 INFO DK: V7H63X9N
Jul 07 20:45:29-259777 cadet-tun-8620 DEBUG   our key was sent, sending ping
Jul 07 20:45:29-260008 cadet-tun-8620 INFO ===> PING for D3TJ
Jul 07 20:45:29-260307 cadet-tun-8620 DEBUG   sending 1699275036
Jul 07 20:45:29-260511 cadet-tun-8620 DEBUG   towards D3TJ
Jul 07 20:45:29-260682 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:29-260867 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:29-263934 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:29-264950 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:29-265143 cadet-tun-8620 DEBUG   e sending 4079910074
Jul 07 20:45:29-265384 cadet-tun-8620 DEBUG   e towards 7DBT
Jul 07 20:45:29-265599 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:29-265801 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:29-266032 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 1
Jul 07 20:45:29-266260 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:29-266439 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:29-266659 cadet-tun-8620 DEBUG  selected: connection BFARXZN9 (->D3TJ)
Jul 07 20:45:29-266945 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection BFARXZN9 (->D3TJ) (80 bytes)
Jul 07 20:45:29-267144 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 2
Jul 07 20:45:29-267381 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:29-267587 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:29-267902 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) FWD towards D3TJ (size 80)
Jul 07 20:45:29-268101 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:29-268327 cadet-con-8620 DEBUG  checking sendability of FWD traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:29-268510 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:29-268686 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:29-268891 cadet-p2p-8620 DEBUG core tmt rdy towards GN10 already called
Jul 07 20:45:29-269094 cadet-p2p-8620 DEBUG QQQ Message queue towards GN10
Jul 07 20:45:29-269294 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:29-269470 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5bd5c
Jul 07 20:45:29-269707 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on BFARXZN9 (->D3TJ)
Jul 07 20:45:29-269903 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:29-270081 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:29-270377 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on BFARXZN9 (->D3TJ)
Jul 07 20:45:29-270573 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:29-270750 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:29-270947 cadet-p2p-8620 DEBUG QQQ End queue towards GN10
Jul 07 20:45:29-271180 util-scheduler-8620 DEBUG Adding task: 1039 / 0x4662248
Jul 07 20:45:29-271392 util-scheduler-8620 DEBUG Running task: 1032 / 0x4d5bd30
Jul 07 20:45:29-271616 util-scheduler-8620 DEBUG Adding task: 1040 / 0x4d5bd30
Jul 07 20:45:29-271839 core-api-8620 DEBUG Adding SEND REQUEST for peer `GN10' to message queue
Jul 07 20:45:29-272044 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-272251 util-scheduler-8620 DEBUG Adding task: 1041 / 0x46620a0
Jul 07 20:45:29-272528 util-scheduler-8620 DEBUG Checking readiness of task: 1041 / 0x46620a0
Jul 07 20:45:29-272726 util-scheduler-8620 DEBUG Checking readiness of task: 1038 / 0x4d5e5d8
Jul 07 20:45:29-272918 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-273110 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-273324 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-273514 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-273704 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-273893 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-274104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-274297 util-scheduler-8620 DEBUG Running task: 1038 / 0x4d5e5d8
Jul 07 20:45:29-274486 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:29-274666 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-274839 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-275070 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:29-275430 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:29-275646 util-scheduler-8620 DEBUG Running task: 1041 / 0x46620a0
Jul 07 20:45:29-275830 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-276005 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-276174 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-276353 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:29-276549 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:29-276737 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:29-277063 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-277296 util-scheduler-8620 DEBUG Running task: 1039 / 0x4662248
Jul 07 20:45:29-277490 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:45:29-277688 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:45:29-277908 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `D3TJ'
Jul 07 20:45:29-278161 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:29-278375 cadet-con-8620 DEBUG   via peer D3TJ
Jul 07 20:45:29-278611 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:29-278819 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:29-279000 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:45:29-279231 cadet-con-8620 DEBUG Connection 1KSG9GE2 (->D3TJ) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:45:29-279417 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:29-279626 util-scheduler-8620 DEBUG Adding task: 1042 / 0x5e31aa0
Jul 07 20:45:29-279874 cadet-p2p-8620 DEBUG adding path [2] to peer D3TJ
Jul 07 20:45:29-280064 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:45:29-280257 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:45:29-280429 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:29-280624 util-scheduler-8620 DEBUG Canceling task: 1011 / 0x5e31aa0
Jul 07 20:45:29-280837 util-scheduler-8620 DEBUG Adding task: 1043 / 0x5e31aa0
Jul 07 20:45:29-281077 cadet-con-8620 DEBUG next keepalive in 4 s
Jul 07 20:45:29-281335 cadet-con-8620 DEBUG Connection 1KSG9GE2 (->D3TJ) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:45:29-281573 cadet-con-8620 INFO ===> {           BCK ACK} on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-281808 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:29-282014 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:29-282306 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 36)
Jul 07 20:45:29-282504 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:29-282729 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-282912 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:29-283087 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:29-283289 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:29-283491 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:29-283667 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:29-283841 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:29-284079 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:29-284280 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:29-284503 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:29-284739 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-284922 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:29-285097 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:29-285319 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:29-285503 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:29-285714 util-scheduler-8620 DEBUG Adding task: 1044 / 0x46620a0
Jul 07 20:45:29-285962 util-scheduler-8620 DEBUG Checking readiness of task: 1044 / 0x46620a0
Jul 07 20:45:29-286156 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-286347 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-286536 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-286738 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-286927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-287117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-287306 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-287498 util-scheduler-8620 DEBUG Running task: 1044 / 0x46620a0
Jul 07 20:45:29-287912 util-8620 DEBUG receive_ready read 404/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:29-288154 util-scheduler-8620 DEBUG Adding task: 1045 / 0x4662248
Jul 07 20:45:29-288453 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-288646 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-288837 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-289026 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-289239 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-289430 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-289620 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-289809 util-scheduler-8620 DEBUG Running task: 1045 / 0x4662248
Jul 07 20:45:29-289997 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:29-290192 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:29-290406 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:29-290606 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-290805 util-scheduler-8620 DEBUG Adding task: 1046 / 0x46620a0
Jul 07 20:45:29-291013 util-scheduler-8620 DEBUG Adding task: 1047 / 0x4662248
Jul 07 20:45:29-291248 util-scheduler-8620 DEBUG Checking readiness of task: 1046 / 0x46620a0
Jul 07 20:45:29-291441 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-291631 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-291820 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-292010 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-292199 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-292388 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-292576 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-292767 util-scheduler-8620 DEBUG Running task: 1046 / 0x46620a0
Jul 07 20:45:29-292951 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-293126 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-293319 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-293502 util-scheduler-8620 DEBUG Canceling task: 1035 / 0x5e2b838
Jul 07 20:45:29-293723 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:45:29-293955 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:29-294187 cadet-p2p-8620 DEBUG Checking 0x60ad6d8 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:29-294423 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:45:29-294601 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:45:29-294772 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:45:29-294940 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:45:29-295111 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:45:29-295367 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 36)
Jul 07 20:45:29-295560 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:29-295740 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:29-295929 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:45:29-296110 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 3
Jul 07 20:45:29-296303 util-scheduler-8620 DEBUG Canceling task: 1031 / 0x5e2cf38
Jul 07 20:45:29-296514 util-scheduler-8620 DEBUG Adding task: 1048 / 0x5e2cf38
Jul 07 20:45:29-296758 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:29-296929 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:29-297150 cadet-p2p-8620 DEBUG Checking 0x642f720 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-297421 cadet-p2p-8620 DEBUG Checking 0x642f720 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-297600 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:29-297807 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:45:29-298019 util-scheduler-8620 DEBUG Adding task: 1049 / 0x5e2b838
Jul 07 20:45:29-298200 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:29-298378 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:45:29-298577 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:29-298752 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:29-298927 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:29-299163 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-299345 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:29-299520 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:29-299717 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:29-299922 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:45:29-300105 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:45:29-300307 util-scheduler-8620 DEBUG Adding task: 1050 / 0x5e2b838
Jul 07 20:45:29-300522 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:29-300715 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-300913 util-scheduler-8620 DEBUG Adding task: 1051 / 0x46620a0
Jul 07 20:45:29-301112 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:45:29-301496 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-301695 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:29-301894 util-scheduler-8620 DEBUG Running task: 1047 / 0x4662248
Jul 07 20:45:29-302084 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:45:29-302279 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:45:29-302495 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `D3TJ'
Jul 07 20:45:29-302740 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:29-302950 cadet-con-8620 DEBUG   via peer D3TJ
Jul 07 20:45:29-303186 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:29-303393 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:29-303574 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:45:29-303745 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:29-303928 util-scheduler-8620 DEBUG Canceling task: 1042 / 0x5e31aa0
Jul 07 20:45:29-304147 util-scheduler-8620 DEBUG Adding task: 1052 / 0x5e31aa0
Jul 07 20:45:29-304400 cadet-p2p-8620 DEBUG adding path [2] to peer D3TJ
Jul 07 20:45:29-304597 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:45:29-304784 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:45:29-305014 cadet-con-8620 DEBUG Connection 1KSG9GE2 (->D3TJ) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:45:29-305276 cadet-con-8620 INFO ===> {           BCK ACK} on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-305511 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:29-305720 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:29-306011 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 36)
Jul 07 20:45:29-306208 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:29-306432 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-306614 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:29-306788 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:29-306989 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:29-307189 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:29-307362 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:29-307536 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:29-307782 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-307964 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:29-308139 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:29-308372 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:29-308554 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:29-308730 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:29-308926 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:29-309132 util-scheduler-8620 DEBUG Adding task: 1053 / 0x4662248
Jul 07 20:45:29-309399 util-scheduler-8620 DEBUG Checking readiness of task: 1051 / 0x46620a0
Jul 07 20:45:29-309593 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-309783 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-309973 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-310162 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-310351 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-310540 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-310729 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-310920 util-scheduler-8620 DEBUG Running task: 1051 / 0x46620a0
Jul 07 20:45:29-311104 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-311279 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-311448 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-311625 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:29-311816 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:29-312003 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:29-312308 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-312516 util-scheduler-8620 DEBUG Running task: 1053 / 0x4662248
Jul 07 20:45:29-312705 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:29-312897 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:29-313110 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:29-313330 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-313529 util-scheduler-8620 DEBUG Adding task: 1054 / 0x46620a0
Jul 07 20:45:29-313738 util-scheduler-8620 DEBUG Adding task: 1055 / 0x4662248
Jul 07 20:45:29-313934 util-scheduler-8620 DEBUG Running task: 1049 / 0x5e2b838
Jul 07 20:45:29-314125 util-scheduler-8620 DEBUG Canceling task: 1050 / 0x5e2b838
Jul 07 20:45:29-314351 util-scheduler-8620 DEBUG Adding task: 1056 / 0x5e2b838
Jul 07 20:45:29-314571 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:29-314748 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:29-314976 util-scheduler-8620 DEBUG Checking readiness of task: 1054 / 0x46620a0
Jul 07 20:45:29-315169 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-315360 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-315550 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-315740 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-315929 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-316118 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-316306 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-316497 util-scheduler-8620 DEBUG Running task: 1054 / 0x46620a0
Jul 07 20:45:29-316681 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-316856 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-317024 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-317223 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:29-317430 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-317627 util-scheduler-8620 DEBUG Adding task: 1057 / 0x46620a0
Jul 07 20:45:29-317823 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:29-318103 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-318298 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:29-318494 util-scheduler-8620 DEBUG Running task: 1055 / 0x4662248
Jul 07 20:45:29-318681 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:29-318874 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:29-319088 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:29-319334 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:29-319581 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:29-319787 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:29-319969 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:29-320142 cadet-con-8620 DEBUG   ACK 80 (was 79)
Jul 07 20:45:29-320369 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:29-320609 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:29-320814 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:29-320995 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:29-321218 util-scheduler-8620 DEBUG Adding task: 1058 / 0x4662248
Jul 07 20:45:29-321459 util-scheduler-8620 DEBUG Checking readiness of task: 1057 / 0x46620a0
Jul 07 20:45:29-321653 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-321845 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-322036 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-322226 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-322416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-322607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-322796 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-322987 util-scheduler-8620 DEBUG Running task: 1057 / 0x46620a0
Jul 07 20:45:29-323172 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-323348 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-323518 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-323701 util-scheduler-8620 DEBUG Canceling task: 1003 / 0x4d6ff98
Jul 07 20:45:29-323935 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:29-324149 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:29-324380 cadet-p2p-8620 DEBUG Checking 0x6094c08 towards CMHCKRVP (->V8XX)
Jul 07 20:45:29-324614 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:29-324790 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:29-324976 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:29-325283 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:29-325478 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:29-325654 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:29-325841 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:29-326029 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:29-326206 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:29-326390 util-scheduler-8620 DEBUG Canceling task: 993 / 0x4d707d0
Jul 07 20:45:29-326600 util-scheduler-8620 DEBUG Adding task: 1059 / 0x4d707d0
Jul 07 20:45:29-326843 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:29-327013 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:29-327234 cadet-p2p-8620 DEBUG Checking 0x609b5e8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:29-327472 cadet-p2p-8620 DEBUG Checking 0x609b5e8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:29-327651 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:29-327855 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:29-328065 util-scheduler-8620 DEBUG Adding task: 1060 / 0x4d6ff98
Jul 07 20:45:29-328244 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:29-328421 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:29-328632 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:29-328817 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:29-328992 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:29-329254 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:29-329450 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:29-329628 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:29-329826 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:29-330030 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:29-330213 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:29-330412 util-scheduler-8620 DEBUG Adding task: 1061 / 0x4d6ff98
Jul 07 20:45:29-330628 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:29-330820 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-331021 util-scheduler-8620 DEBUG Adding task: 1062 / 0x46620a0
Jul 07 20:45:29-331219 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:29-335538 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-335765 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:29-335972 util-scheduler-8620 DEBUG Running task: 1058 / 0x4662248
Jul 07 20:45:29-336164 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:45:29-336442 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:45:29-336666 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `KNAS'
Jul 07 20:45:29-336915 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:29-337154 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:29-337408 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:29-337618 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:29-337862 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:29-338069 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:29-338275 cadet-con-8620 DEBUG  PID 16 (expected 16+)
Jul 07 20:45:29-338455 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:29-338642 util-scheduler-8620 DEBUG Canceling task: 1016 / 0x4d61c30
Jul 07 20:45:29-338862 util-scheduler-8620 DEBUG Adding task: 1063 / 0x4d61c30
Jul 07 20:45:29-339042 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:29-339294 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:29-339514 util-scheduler-8620 DEBUG Adding task: 1064 / 0x4d5e5d8
Jul 07 20:45:29-339698 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:29-339866 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:29-343250 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:29-344484 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:29-344680 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:29-347358 cadet-tun-8620 INFO <=== {          DATA_ACK} on KNAS
Jul 07 20:45:29-347557 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:45:29-347740 cadet-chn-8620 DEBUG   head 2, out!
Jul 07 20:45:29-347923 cadet-chn-8620 DEBUG free_sent_reliable 1 0
Jul 07 20:45:29-348108 cadet-chn-8620 DEBUG  rel 0x4d63a48, head 0x5b978b8
Jul 07 20:45:29-348286 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:45:29-348455 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:29-348629 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:45:29-348835 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:29-349016 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:29-349224 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:29-349416 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:29-349593 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:29-349762 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:29-349979 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:29-350152 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:29-350387 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:29-350571 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:29-350748 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:45:29-350975 cadet-chn-8620 DEBUG   sending FWD ack to client on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:29-351154 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:45:29-351378 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:29-351553 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:29-351727 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:29-351898 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:29-352119 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:29-352298 cadet-con-8620 DEBUG  ACK 80
Jul 07 20:45:29-352824 cadet-con-8620 DEBUG  last pid 16, last ack 79, qmax 11, q 0
Jul 07 20:45:29-353157 cadet-con-8620 INFO --> {               ACK} ( 80) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:29-353425 cadet-con-8620 DEBUG  ack 80
Jul 07 20:45:29-353606 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:29-353842 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:29-354049 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:29-354343 cadet-p2p-8620 INFO que {               ACK} ( 80) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:29-354545 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:29-354769 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:29-354951 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 18
Jul 07 20:45:29-355125 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:29-355327 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:29-355529 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:29-355704 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:29-355879 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:29-356115 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:29-356298 cadet-p2p-8620 DEBUG QQQ    payload , 80
Jul 07 20:45:29-356494 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:29-356728 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:29-356922 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:29-357108 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:29-357329 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:29-357548 util-scheduler-8620 DEBUG Adding task: 1065 / 0x4662248
Jul 07 20:45:29-357812 util-scheduler-8620 DEBUG Checking readiness of task: 1064 / 0x4d5e5d8
Jul 07 20:45:29-358009 util-scheduler-8620 DEBUG Checking readiness of task: 1062 / 0x46620a0
Jul 07 20:45:29-358201 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-358404 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-358595 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-358785 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-358976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-359166 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-359356 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-359548 util-scheduler-8620 DEBUG Running task: 1062 / 0x46620a0
Jul 07 20:45:29-359734 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-359912 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-360085 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-360262 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:29-360456 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:29-360645 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:29-360956 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-361167 util-scheduler-8620 DEBUG Running task: 1064 / 0x4d5e5d8
Jul 07 20:45:29-361376 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:29-361553 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-361723 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-361944 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:29-362242 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:29-362453 util-scheduler-8620 DEBUG Running task: 1065 / 0x4662248
Jul 07 20:45:29-362643 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:29-362837 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:29-363051 core-api-8620 DEBUG Received notification about transmission readiness to `GN10'.
Jul 07 20:45:29-363249 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-363453 util-scheduler-8620 DEBUG Adding task: 1066 / 0x46620a0
Jul 07 20:45:29-363638 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:29-363841 util-scheduler-8620 DEBUG Adding task: 1067 / 0x46620a0
Jul 07 20:45:29-364039 util-scheduler-8620 DEBUG Running task: 1060 / 0x4d6ff98
Jul 07 20:45:29-364233 util-scheduler-8620 DEBUG Canceling task: 1061 / 0x4d6ff98
Jul 07 20:45:29-364450 util-scheduler-8620 DEBUG Adding task: 1068 / 0x4d6ff98
Jul 07 20:45:29-364668 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:29-364845 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:29-365077 util-scheduler-8620 DEBUG Checking readiness of task: 1067 / 0x46620a0
Jul 07 20:45:29-365296 util-scheduler-8620 DEBUG Checking readiness of task: 1066 / 0x46620a0
Jul 07 20:45:29-365489 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-365682 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-365871 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-366077 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-366267 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-366457 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-366646 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-366836 util-scheduler-8620 DEBUG Running task: 1066 / 0x46620a0
Jul 07 20:45:29-367077 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-367253 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-367423 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-367599 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:29-367806 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-368003 util-scheduler-8620 DEBUG Adding task: 1069 / 0x46620a0
Jul 07 20:45:29-368199 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:29-368493 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-368689 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:29-368887 util-scheduler-8620 DEBUG Running task: 1067 / 0x46620a0
Jul 07 20:45:29-369313 util-8620 DEBUG receive_ready read 348/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:29-369542 util-scheduler-8620 DEBUG Adding task: 1070 / 0x4662248
Jul 07 20:45:29-369829 util-scheduler-8620 DEBUG Checking readiness of task: 1069 / 0x46620a0
Jul 07 20:45:29-370022 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:29-370213 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:29-370403 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:29-370592 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:29-370781 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:29-370970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:29-371159 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:29-371350 util-scheduler-8620 DEBUG Running task: 1069 / 0x46620a0
Jul 07 20:45:29-371534 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:29-371707 util-8620 DEBUG process_notify is running
Jul 07 20:45:29-371876 util-8620 DEBUG client_notify is running
Jul 07 20:45:29-372058 util-scheduler-8620 DEBUG Canceling task: 1040 / 0x4d5bd30
Jul 07 20:45:29-372277 core-api-8620 DEBUG Transmitting SEND request to `GN10' with 196 bytes.
Jul 07 20:45:29-372547 cadet-p2p-8620 DEBUG Queue send towards GN10 (max 196)
Jul 07 20:45:29-372859 cadet-p2p-8620 DEBUG Checking 0x612c290 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:29-373093 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) FWD
Jul 07 20:45:29-373302 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:29-373490 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:29-373772 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) FWD (size 196)
Jul 07 20:45:29-373968 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:29-374148 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:29-374336 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:29-374527 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 2
Jul 07 20:45:29-374705 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:29-374889 util-scheduler-8620 DEBUG Canceling task: 1037 / 0x5e2cf38
Jul 07 20:45:29-375108 util-scheduler-8620 DEBUG Adding task: 1071 / 0x5e2cf38
Jul 07 20:45:29-375287 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:29-375508 cadet-p2p-8620 DEBUG Checking 0x642da28 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:29-375745 cadet-p2p-8620 DEBUG Checking 0x642da28 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:29-375940 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:29-376147 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `GN10'
Jul 07 20:45:29-376374 util-scheduler-8620 DEBUG Adding task: 1072 / 0x4d5bd30
Jul 07 20:45:29-376554 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:29-376732 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:29-376931 cadet-p2p-8620 DEBUG QQQ Message queue towards GN10
Jul 07 20:45:29-377105 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:29-377304 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5bd5c
Jul 07 20:45:29-377541 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on BFARXZN9 (->D3TJ)
Jul 07 20:45:29-377734 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:29-377911 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:29-378109 cadet-p2p-8620 DEBUG QQQ End queue towards GN10
Jul 07 20:45:29-378313 core-api-8620 DEBUG Transmitting SEND request to `GN10' yielded 196 bytes.
Jul 07 20:45:29-378496 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:29-378695 util-scheduler-8620 DEBUG Adding task: 1073 / 0x4d5bd30
Jul 07 20:45:29-378910 core-api-8620 DEBUG Adding SEND REQUEST for peer `GN10' to message queue
Jul 07 20:45:29-379103 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:29-379304 util-scheduler-8620 DEBUG Adding task: 1074 / 0x46620a0
Jul 07 20:45:29-379503 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:29-379905 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:29-380113 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:29-380310 util-scheduler-8620 DEBUG Running task: 1070 / 0x4662248
Jul 07 20:45:29-380499 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:29-380696 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:29-380911 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:29-381157 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:29-381418 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:29-381647 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:29-381854 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:29-382096 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:29-382302 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:29-382487 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:29-382671 util-scheduler-8620 DEBUG Canceling task: 984 / 0x4d707d0
Jul 07 20:45:29-382887 util-scheduler-8620 DEBUG Adding task: 1075 / 0x4d707d0
Jul 07 20:45:29-383066 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:29-383316 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:29-383523 util-scheduler-8620 DEBUG Adding task: 1076 / 0x4d5e5d8
Jul 07 20:45:29-383703 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:29-383902 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:30-034636 util-scheduler-8620 DEBUG Adding task: 1077 / 0x4662248
Jul 07 20:45:30-035076 util-scheduler-8620 DEBUG Checking readiness of task: 1076 / 0x4d5e5d8
Jul 07 20:45:30-035281 util-scheduler-8620 DEBUG Checking readiness of task: 1074 / 0x46620a0
Jul 07 20:45:30-035477 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-035671 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-035863 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-036056 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-036248 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-036440 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-036631 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-036859 util-scheduler-8620 DEBUG Running task: 1074 / 0x46620a0
Jul 07 20:45:30-037049 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-037257 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-037434 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-037617 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:30-037818 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:30-038012 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:30-038367 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:30-038581 util-scheduler-8620 DEBUG Running task: 1076 / 0x4d5e5d8
Jul 07 20:45:30-038768 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:30-040119 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-040300 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-040532 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:30-040845 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:30-041060 util-scheduler-8620 DEBUG Running task: 1077 / 0x4662248
Jul 07 20:45:30-041297 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:30-041500 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:30-041733 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:30-041996 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:30-042239 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:30-042471 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:30-042766 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:30-043017 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:30-043228 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:30-043417 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:30-043608 util-scheduler-8620 DEBUG Canceling task: 1075 / 0x4d707d0
Jul 07 20:45:30-043832 util-scheduler-8620 DEBUG Adding task: 1078 / 0x4d707d0
Jul 07 20:45:30-044173 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:30-044432 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:30-044655 util-scheduler-8620 DEBUG Adding task: 1079 / 0x4d5e5d8
Jul 07 20:45:30-044839 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:30-045051 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:30-045262 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:30-045439 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:30-045608 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:30-049118 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:30-049977 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:30-050200 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:30-050499 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:30-050676 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:30-050864 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:30-054273 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:30-055437 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:30-055708 cadet-tun-8620 DEBUG   e sending 321508614
Jul 07 20:45:30-055924 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:30-056308 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:30-056544 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:30-056728 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:30-056952 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:30-057273 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:30-057476 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:30-057713 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:30-058071 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:30-058391 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:30-058593 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:30-058821 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:30-059007 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:30-059184 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:30-059389 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:30-059593 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:30-059771 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:30-059948 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:30-060197 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:30-060395 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:30-060575 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:30-060811 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:30-061005 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:30-061183 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:30-061411 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:30-061597 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:30-061815 util-scheduler-8620 DEBUG Adding task: 1080 / 0x46620a0
Jul 07 20:45:30-062024 util-scheduler-8620 DEBUG Running task: 1007 / 0x4d6e518
Jul 07 20:45:30-062225 util-scheduler-8620 DEBUG Running task: 1072 / 0x4d5bd30
Jul 07 20:45:30-062424 util-scheduler-8620 DEBUG Canceling task: 1073 / 0x4d5bd30
Jul 07 20:45:30-062647 util-scheduler-8620 DEBUG Adding task: 1081 / 0x4d5bd30
Jul 07 20:45:30-062870 core-api-8620 DEBUG Adding SEND REQUEST for peer `GN10' to message queue
Jul 07 20:45:30-063073 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:30-063275 util-scheduler-8620 DEBUG Adding task: 1082 / 0x46620a0
Jul 07 20:45:30-063541 util-scheduler-8620 DEBUG Checking readiness of task: 1082 / 0x46620a0
Jul 07 20:45:30-063739 util-scheduler-8620 DEBUG Checking readiness of task: 1080 / 0x46620a0
Jul 07 20:45:30-063933 util-scheduler-8620 DEBUG Checking readiness of task: 1079 / 0x4d5e5d8
Jul 07 20:45:30-064126 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-064319 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-064510 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-064706 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-065026 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-065254 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-065449 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-065644 util-scheduler-8620 DEBUG Running task: 1079 / 0x4d5e5d8
Jul 07 20:45:30-065831 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:30-066011 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-066184 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-066409 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:30-066720 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:30-066936 util-scheduler-8620 DEBUG Running task: 1080 / 0x46620a0
Jul 07 20:45:30-067398 util-8620 DEBUG receive_ready read 272/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:30-067637 util-scheduler-8620 DEBUG Adding task: 1083 / 0x4662248
Jul 07 20:45:30-067850 util-scheduler-8620 DEBUG Running task: 1082 / 0x46620a0
Jul 07 20:45:30-068037 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-068214 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-068402 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-068584 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:30-068861 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:30-069056 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:30-069403 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:30-069657 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-069853 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-070045 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-070237 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-070429 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-070621 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-070825 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-071017 util-scheduler-8620 DEBUG Running task: 1083 / 0x4662248
Jul 07 20:45:30-071209 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:30-071409 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:30-071751 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `GN10'
Jul 07 20:45:30-072006 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from GN10
Jul 07 20:45:30-072244 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:30-072475 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-072684 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:30-072929 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-073138 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:30-073352 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:30-073541 util-scheduler-8620 DEBUG Canceling task: 1048 / 0x5e2cf38
Jul 07 20:45:30-073771 util-scheduler-8620 DEBUG Adding task: 1084 / 0x5e2cf38
Jul 07 20:45:30-074026 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:30-075047 cadet-con-8620 DEBUG   not for us, retransmitting...
Jul 07 20:45:30-075574 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:30-075793 util-scheduler-8620 DEBUG Adding task: 1085 / 0x4d5e5d8
Jul 07 20:45:30-076900 cadet-con-8620 INFO --> {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (196 bytes)
Jul 07 20:45:30-077328 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 1
Jul 07 20:45:30-077579 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-077790 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:30-078085 cadet-p2p-8620 INFO que {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 196)
Jul 07 20:45:30-078286 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:30-078514 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:30-078829 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:30-079013 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:30-079229 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:30-079436 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:30-079614 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:30-079791 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:30-080034 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:30-080220 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-080399 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:30-080636 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:30-080818 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-080995 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:30-081257 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:30-081459 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-081637 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:30-081838 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:30-082358 util-scheduler-8620 DEBUG Adding task: 1086 / 0x4662248
Jul 07 20:45:30-082621 util-scheduler-8620 DEBUG Checking readiness of task: 1085 / 0x4d5e5d8
Jul 07 20:45:30-082820 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-083014 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-083207 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-083399 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-083591 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-083783 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-083974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-084168 util-scheduler-8620 DEBUG Running task: 1085 / 0x4d5e5d8
Jul 07 20:45:30-084355 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:30-084534 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-084710 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-084930 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:30-085417 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:30-085638 util-scheduler-8620 DEBUG Running task: 1086 / 0x4662248
Jul 07 20:45:30-085831 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:30-086027 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:30-086246 core-api-8620 DEBUG Received notification about transmission readiness to `GN10'.
Jul 07 20:45:30-086429 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:30-086635 util-scheduler-8620 DEBUG Adding task: 1087 / 0x46620a0
Jul 07 20:45:30-086877 util-scheduler-8620 DEBUG Checking readiness of task: 1087 / 0x46620a0
Jul 07 20:45:30-087073 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-087266 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-087458 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-087649 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-087841 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-088032 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-088223 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-088416 util-scheduler-8620 DEBUG Running task: 1087 / 0x46620a0
Jul 07 20:45:30-088819 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:30-089045 util-scheduler-8620 DEBUG Adding task: 1088 / 0x4662248
Jul 07 20:45:30-089319 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-089514 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-089706 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-089908 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-090100 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-090291 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-090482 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-090674 util-scheduler-8620 DEBUG Running task: 1088 / 0x4662248
Jul 07 20:45:30-090864 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:30-091057 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:30-091285 core-api-8620 DEBUG Received notification about transmission readiness to `GN10'.
Jul 07 20:45:30-091485 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:30-091685 util-scheduler-8620 DEBUG Adding task: 1089 / 0x46620a0
Jul 07 20:45:30-091871 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:30-092069 util-scheduler-8620 DEBUG Adding task: 1090 / 0x46620a0
Jul 07 20:45:30-092310 util-scheduler-8620 DEBUG Checking readiness of task: 1090 / 0x46620a0
Jul 07 20:45:30-092504 util-scheduler-8620 DEBUG Checking readiness of task: 1089 / 0x46620a0
Jul 07 20:45:30-092698 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-092891 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-093083 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-093300 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-093492 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-093682 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-093873 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-094066 util-scheduler-8620 DEBUG Running task: 1089 / 0x46620a0
Jul 07 20:45:30-094251 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-094429 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-094778 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-094970 util-scheduler-8620 DEBUG Canceling task: 1081 / 0x4d5bd30
Jul 07 20:45:30-095194 core-api-8620 DEBUG Transmitting SEND request to `GN10' with 80 bytes.
Jul 07 20:45:30-095414 cadet-p2p-8620 DEBUG Queue send towards GN10 (max 196)
Jul 07 20:45:30-095648 cadet-p2p-8620 DEBUG Checking 0x642da28 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:30-095883 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) FWD
Jul 07 20:45:30-096063 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:30-096251 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:30-096536 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) FWD (size 80)
Jul 07 20:45:30-096733 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:30-096915 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:30-097105 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:30-097321 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 2
Jul 07 20:45:30-097502 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:30-097687 util-scheduler-8620 DEBUG Canceling task: 1071 / 0x5e2cf38
Jul 07 20:45:30-097906 util-scheduler-8620 DEBUG Adding task: 1091 / 0x5e2cf38
Jul 07 20:45:30-098098 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:30-098283 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:30-098485 cadet-p2p-8620 DEBUG QQQ Message queue towards GN10
Jul 07 20:45:30-098661 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:30-098836 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:30-099045 cadet-p2p-8620 DEBUG QQQ End queue towards GN10
Jul 07 20:45:30-099252 core-api-8620 DEBUG Transmitting SEND request to `GN10' yielded 80 bytes.
Jul 07 20:45:30-099437 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:30-099618 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:30-099810 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:30-100248 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:30-100506 util-scheduler-8620 DEBUG Checking readiness of task: 1090 / 0x46620a0
Jul 07 20:45:30-100701 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-100893 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-101083 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-101297 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-101505 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-101696 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-101886 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-102077 util-scheduler-8620 DEBUG Running task: 1090 / 0x46620a0
Jul 07 20:45:30-102475 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:30-102699 util-scheduler-8620 DEBUG Adding task: 1092 / 0x4662248
Jul 07 20:45:30-102944 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-103137 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-103425 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-103830 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-104023 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-104213 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-104402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-104592 util-scheduler-8620 DEBUG Running task: 1092 / 0x4662248
Jul 07 20:45:30-104785 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:30-104978 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:30-105217 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `GN10'
Jul 07 20:45:30-105466 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from GN10
Jul 07 20:45:30-105701 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:30-105926 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-106132 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:30-106373 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-106579 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:30-106764 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:30-106948 util-scheduler-8620 DEBUG Canceling task: 1084 / 0x5e2cf38
Jul 07 20:45:30-107160 util-scheduler-8620 DEBUG Adding task: 1093 / 0x5e2cf38
Jul 07 20:45:30-107404 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:30-107689 cadet-con-8620 DEBUG   not for us, retransmitting...
Jul 07 20:45:30-107936 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:30-108155 util-scheduler-8620 DEBUG Adding task: 1094 / 0x4d5e5d8
Jul 07 20:45:30-108421 cadet-con-8620 INFO --> {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (80 bytes)
Jul 07 20:45:30-108614 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 1
Jul 07 20:45:30-108848 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:30-109052 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:30-109366 cadet-p2p-8620 INFO que {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 80)
Jul 07 20:45:30-109563 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:30-109785 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:45:30-109968 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:30-110142 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:30-110343 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:30-110545 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:30-110720 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:30-110895 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:30-111131 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:30-111313 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-111488 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:30-111720 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:30-111901 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-112091 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:30-112326 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:30-112506 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-112681 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:30-112914 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:30-113095 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:30-113293 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:30-113490 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:30-113667 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:30-113865 util-scheduler-8620 DEBUG Adding task: 1095 / 0x46620a0
Jul 07 20:45:30-114112 util-scheduler-8620 DEBUG Checking readiness of task: 1095 / 0x46620a0
Jul 07 20:45:30-114302 util-scheduler-8620 DEBUG Checking readiness of task: 1094 / 0x4d5e5d8
Jul 07 20:45:30-114494 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-114687 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-114877 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-115066 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-115255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-115444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-115644 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-115835 util-scheduler-8620 DEBUG Running task: 1094 / 0x4d5e5d8
Jul 07 20:45:30-116019 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:30-116194 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-116364 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-116578 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:30-116879 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:30-517082 util-scheduler-8620 DEBUG Checking readiness of task: 1095 / 0x46620a0
Jul 07 20:45:30-517484 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-517682 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-517876 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-518068 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-518259 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-518450 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-518640 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-518836 util-scheduler-8620 DEBUG Running task: 1095 / 0x46620a0
Jul 07 20:45:30-519258 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:30-519515 util-scheduler-8620 DEBUG Adding task: 1096 / 0x4662248
Jul 07 20:45:30-519796 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-519989 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-520194 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-520385 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-520633 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-520825 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-521075 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-521295 util-scheduler-8620 DEBUG Running task: 1096 / 0x4662248
Jul 07 20:45:30-521489 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:30-521689 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:30-521950 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:30-522159 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:30-522367 util-scheduler-8620 DEBUG Adding task: 1097 / 0x46620a0
Jul 07 20:45:30-522555 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:30-522762 util-scheduler-8620 DEBUG Adding task: 1098 / 0x46620a0
Jul 07 20:45:30-523006 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:30-523198 util-scheduler-8620 DEBUG Checking readiness of task: 1097 / 0x46620a0
Jul 07 20:45:30-523389 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-523579 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-523768 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-523959 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-524148 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-524337 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-524526 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-524717 util-scheduler-8620 DEBUG Running task: 1097 / 0x46620a0
Jul 07 20:45:30-524902 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-525081 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-525277 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-525470 util-scheduler-8620 DEBUG Canceling task: 1025 / 0x4d5c9e8
Jul 07 20:45:30-525696 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:45:30-525916 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:30-526156 cadet-p2p-8620 DEBUG Checking 0x643ebf8 towards HS92G30M (->KNAS)
Jul 07 20:45:30-526409 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:30-526588 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:30-526779 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:30-527048 cadet-p2p-8620 INFO snd {               ACK} ( 80) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:30-527242 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:30-527421 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:30-527610 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:30-527784 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:30-527969 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:30-528142 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:30-528363 cadet-p2p-8620 DEBUG Checking 0x60912f8 towards HS92G30M (->KNAS)
Jul 07 20:45:30-528596 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:30-528778 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 18
Jul 07 20:45:30-528953 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:30-529181 cadet-p2p-8620 DEBUG Checking 0x60912f8 towards HS92G30M (->KNAS)
Jul 07 20:45:30-529435 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:30-529617 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 18
Jul 07 20:45:30-529791 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:30-529957 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:30-530164 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:45:30-530379 util-scheduler-8620 DEBUG Adding task: 1099 / 0x4d5c9e8
Jul 07 20:45:30-530559 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:30-530734 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:30-530933 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:30-531108 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:30-531282 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:30-531520 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:30-531716 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:30-531894 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:30-532111 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:30-532317 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:30-532500 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:30-532705 util-scheduler-8620 DEBUG Adding task: 1100 / 0x4d5c9e8
Jul 07 20:45:30-532924 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:30-533119 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:30-533346 util-scheduler-8620 DEBUG Adding task: 1101 / 0x46620a0
Jul 07 20:45:30-533548 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:30-534393 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:30-534674 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:30-534928 util-scheduler-8620 DEBUG Checking readiness of task: 1101 / 0x46620a0
Jul 07 20:45:30-535121 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:30-535312 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-535503 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-535692 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-535882 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-536072 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-536261 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-536450 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-536640 util-scheduler-8620 DEBUG Running task: 1101 / 0x46620a0
Jul 07 20:45:30-536825 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-537001 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-537171 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-537376 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:30-537572 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:30-537760 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:30-538041 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:30-538250 util-scheduler-8620 DEBUG Running task: 1099 / 0x4d5c9e8
Jul 07 20:45:30-538443 util-scheduler-8620 DEBUG Canceling task: 1100 / 0x4d5c9e8
Jul 07 20:45:30-538658 util-scheduler-8620 DEBUG Adding task: 1102 / 0x4d5c9e8
Jul 07 20:45:30-538874 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:30-539068 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:30-539266 util-scheduler-8620 DEBUG Adding task: 1103 / 0x46620a0
Jul 07 20:45:30-539505 util-scheduler-8620 DEBUG Checking readiness of task: 1103 / 0x46620a0
Jul 07 20:45:30-539698 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:30-539888 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:30-540078 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:30-540267 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:30-540456 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:30-540645 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:30-540834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:30-541023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:30-541237 util-scheduler-8620 DEBUG Running task: 1103 / 0x46620a0
Jul 07 20:45:30-541421 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:30-541596 util-8620 DEBUG process_notify is running
Jul 07 20:45:30-541764 util-8620 DEBUG client_notify is running
Jul 07 20:45:30-541956 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:30-542370 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:30-542558 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:30-542847 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:31-251867 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:31-252246 util-scheduler-8620 DEBUG Checking readiness of task: 1006 / 0x4663d68
Jul 07 20:45:31-252446 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-252639 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-252831 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-253022 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-253241 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-253434 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-253631 util-scheduler-8620 DEBUG Running task: 1006 / 0x4663d68
Jul 07 20:45:31-254065 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:31-254325 util-scheduler-8620 DEBUG Adding task: 1104 / 0x4663f10
Jul 07 20:45:31-254663 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:31-254886 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-255078 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-255269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-255460 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-255650 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-255841 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-256034 util-scheduler-8620 DEBUG Running task: 1104 / 0x4663f10
Jul 07 20:45:31-256227 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:31-256425 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:31-256643 util-scheduler-8620 DEBUG Adding task: 1105 / 0x4663d68
Jul 07 20:45:31-256831 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:31-257062 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 11616
Jul 07 20:45:31-257290 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 11616 Bps
Jul 07 20:45:31-257556 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 14866 Bps, last update was 85 s ago
Jul 07 20:45:31-258159 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11616 Bps, last update was 629 µs ago
Jul 07 20:45:31-258904 util-scheduler-8620 DEBUG Adding task: 1106 / 0x4d6fa48
Jul 07 20:45:31-259158 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-259355 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:31-259548 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-259739 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-259931 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-260122 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-260313 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-260504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-260696 util-scheduler-8620 DEBUG Running task: 1106 / 0x4d6fa48
Jul 07 20:45:31-490681 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-491015 util-scheduler-8620 DEBUG Checking readiness of task: 1098 / 0x46620a0
Jul 07 20:45:31-491247 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-491440 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-491632 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-491822 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-492013 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-492203 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-492397 util-scheduler-8620 DEBUG Running task: 1098 / 0x46620a0
Jul 07 20:45:31-492821 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:31-493071 util-scheduler-8620 DEBUG Adding task: 1107 / 0x4662248
Jul 07 20:45:31-493370 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-493564 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-493754 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-493944 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-494136 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-494325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-494515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-494704 util-scheduler-8620 DEBUG Running task: 1107 / 0x4662248
Jul 07 20:45:31-494894 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:31-495092 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:31-495320 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:31-495527 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:31-495733 util-scheduler-8620 DEBUG Adding task: 1108 / 0x46620a0
Jul 07 20:45:31-495920 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:31-496125 util-scheduler-8620 DEBUG Adding task: 1109 / 0x46620a0
Jul 07 20:45:31-496387 util-scheduler-8620 DEBUG Checking readiness of task: 1109 / 0x46620a0
Jul 07 20:45:31-496580 util-scheduler-8620 DEBUG Checking readiness of task: 1108 / 0x46620a0
Jul 07 20:45:31-496773 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-496964 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-497154 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-497369 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-497559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-497748 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-497936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-498128 util-scheduler-8620 DEBUG Running task: 1108 / 0x46620a0
Jul 07 20:45:31-498312 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:31-498491 util-8620 DEBUG process_notify is running
Jul 07 20:45:31-498664 util-8620 DEBUG client_notify is running
Jul 07 20:45:31-498855 util-scheduler-8620 DEBUG Canceling task: 1102 / 0x4d5c9e8
Jul 07 20:45:31-499079 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:45:31-499302 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:31-499542 cadet-p2p-8620 DEBUG Checking 0x60912f8 towards HS92G30M (->KNAS)
Jul 07 20:45:31-499776 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:31-499958 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 18
Jul 07 20:45:31-500134 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:31-500356 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:31-500533 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:45:31-500709 cadet-p2p-8620 DEBUG   payload ID 19
Jul 07 20:45:31-501011 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 96)
Jul 07 20:45:31-501228 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:31-501410 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:31-501598 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:31-501772 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:31-501941 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:31-502130 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:31-502308 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:45:31-502534 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 925 ms
Jul 07 20:45:31-502706 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:31-502912 cadet-chn-8620 DEBUG !! using delay 3701864 µs
Jul 07 20:45:31-503109 util-scheduler-8620 DEBUG Adding task: 1110 / 0x4d63a48
Jul 07 20:45:31-503312 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:31-503543 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:31-503718 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:31-503903 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:31-504078 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:31-504276 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:31-504451 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:31-504625 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:31-504826 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:31-505005 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:31-505187 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:31-505391 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:31-505567 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:31-505749 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:31-505968 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:31-506141 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:31-506373 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:31-506557 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:31-506737 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:31-506922 util-scheduler-8620 DEBUG Canceling task: 928 / 0x4d61c30
Jul 07 20:45:31-507134 util-scheduler-8620 DEBUG Adding task: 1111 / 0x4d61c30
Jul 07 20:45:31-507378 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:31-507556 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:31-507734 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 19
Jul 07 20:45:31-507907 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:31-508088 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:45:31-508287 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:31-508463 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:31-508636 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:31-508835 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:31-509039 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 96 bytes.
Jul 07 20:45:31-509245 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:45:31-509426 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:31-509617 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:45:31-510499 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:31-763121 util-scheduler-8620 DEBUG Checking readiness of task: 1109 / 0x46620a0
Jul 07 20:45:31-763480 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-763677 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-763871 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-764062 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-764257 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-764477 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-764670 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-764865 util-scheduler-8620 DEBUG Running task: 1109 / 0x46620a0
Jul 07 20:45:31-765313 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:31-765567 util-scheduler-8620 DEBUG Adding task: 1112 / 0x4662248
Jul 07 20:45:31-765843 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-766036 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-766226 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-766416 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-766606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-766835 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-767026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-767215 util-scheduler-8620 DEBUG Running task: 1112 / 0x4662248
Jul 07 20:45:31-767406 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:31-767605 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:31-767833 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:31-768039 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:31-768246 util-scheduler-8620 DEBUG Adding task: 1113 / 0x46620a0
Jul 07 20:45:31-768434 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:31-768648 util-scheduler-8620 DEBUG Adding task: 1114 / 0x46620a0
Jul 07 20:45:31-768891 util-scheduler-8620 DEBUG Checking readiness of task: 1114 / 0x46620a0
Jul 07 20:45:31-769083 util-scheduler-8620 DEBUG Checking readiness of task: 1113 / 0x46620a0
Jul 07 20:45:31-775897 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-776101 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-776294 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-776485 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-776675 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-776865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-777055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-777272 util-scheduler-8620 DEBUG Running task: 1113 / 0x46620a0
Jul 07 20:45:31-777460 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:31-777638 util-8620 DEBUG process_notify is running
Jul 07 20:45:31-777812 util-8620 DEBUG client_notify is running
Jul 07 20:45:31-778003 util-scheduler-8620 DEBUG Canceling task: 1068 / 0x4d6ff98
Jul 07 20:45:31-778229 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:31-778450 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:31-778690 cadet-p2p-8620 DEBUG Checking 0x609b5e8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:31-778925 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:31-779102 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:31-779293 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:31-779576 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:31-779771 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:31-779951 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:31-780139 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:31-780327 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:31-780505 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:31-780688 util-scheduler-8620 DEBUG Canceling task: 1059 / 0x4d707d0
Jul 07 20:45:31-780923 util-scheduler-8620 DEBUG Adding task: 1115 / 0x4d707d0
Jul 07 20:45:31-781174 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:31-781371 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:31-781594 cadet-p2p-8620 DEBUG Checking 0x6690d88 towards CMHCKRVP (->V8XX)
Jul 07 20:45:31-781831 cadet-p2p-8620 DEBUG Checking 0x6690d88 towards CMHCKRVP (->V8XX)
Jul 07 20:45:31-782009 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:31-782215 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:31-782430 util-scheduler-8620 DEBUG Adding task: 1116 / 0x4d6ff98
Jul 07 20:45:31-782610 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:31-782786 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:31-782985 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:31-783159 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:31-783333 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:31-783571 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:31-783766 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:31-783943 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:31-784157 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:31-784362 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:31-784544 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:31-784747 util-scheduler-8620 DEBUG Adding task: 1117 / 0x4d6ff98
Jul 07 20:45:31-784967 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:31-785175 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:31-788212 util-scheduler-8620 DEBUG Adding task: 1118 / 0x46620a0
Jul 07 20:45:31-788419 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:31-789684 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:31-789893 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:31-790147 util-scheduler-8620 DEBUG Checking readiness of task: 1118 / 0x46620a0
Jul 07 20:45:31-790342 util-scheduler-8620 DEBUG Checking readiness of task: 1114 / 0x46620a0
Jul 07 20:45:31-790612 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-790806 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-790997 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-791187 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-791377 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-791567 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-791756 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-791948 util-scheduler-8620 DEBUG Running task: 1114 / 0x46620a0
Jul 07 20:45:31-792349 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:31-792578 util-scheduler-8620 DEBUG Adding task: 1119 / 0x4662248
Jul 07 20:45:31-792789 util-scheduler-8620 DEBUG Running task: 1118 / 0x46620a0
Jul 07 20:45:31-792977 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:31-793154 util-8620 DEBUG process_notify is running
Jul 07 20:45:31-793348 util-8620 DEBUG client_notify is running
Jul 07 20:45:31-793527 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:31-793722 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:31-793910 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:31-794209 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:31-794418 util-scheduler-8620 DEBUG Running task: 1116 / 0x4d6ff98
Jul 07 20:45:31-794629 util-scheduler-8620 DEBUG Canceling task: 1117 / 0x4d6ff98
Jul 07 20:45:31-794845 util-scheduler-8620 DEBUG Adding task: 1120 / 0x4d6ff98
Jul 07 20:45:31-795064 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:31-795260 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:31-795460 util-scheduler-8620 DEBUG Adding task: 1121 / 0x46620a0
Jul 07 20:45:31-795697 util-scheduler-8620 DEBUG Checking readiness of task: 1121 / 0x46620a0
Jul 07 20:45:31-795890 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:31-796080 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:31-796270 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:31-796459 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:31-796648 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:31-796850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:31-797039 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:31-797251 util-scheduler-8620 DEBUG Running task: 1121 / 0x46620a0
Jul 07 20:45:31-797436 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:31-797611 util-8620 DEBUG process_notify is running
Jul 07 20:45:31-797780 util-8620 DEBUG client_notify is running
Jul 07 20:45:31-797955 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:31-798144 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:31-798331 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:31-798627 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:31-798836 util-scheduler-8620 DEBUG Running task: 1119 / 0x4662248
Jul 07 20:45:31-799026 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:31-799221 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:31-799439 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:31-799691 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:31-799931 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:31-800161 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:31-800370 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:31-800617 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:31-800826 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:31-801013 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:31-801223 util-scheduler-8620 DEBUG Canceling task: 1078 / 0x4d707d0
Jul 07 20:45:31-801698 util-scheduler-8620 DEBUG Adding task: 1122 / 0x4d707d0
Jul 07 20:45:31-803428 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:31-803904 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:31-804133 util-scheduler-8620 DEBUG Adding task: 1123 / 0x4d5e5d8
Jul 07 20:45:31-804318 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:31-804541 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:32-440783 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:32-441175 util-scheduler-8620 DEBUG Adding task: 1124 / 0x46620a0
Jul 07 20:45:32-441501 util-scheduler-8620 DEBUG Checking readiness of task: 1124 / 0x46620a0
Jul 07 20:45:32-441703 util-scheduler-8620 DEBUG Checking readiness of task: 1123 / 0x4d5e5d8
Jul 07 20:45:32-441908 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-442099 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-442289 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-442480 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-442669 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-442896 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-443087 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-443283 util-scheduler-8620 DEBUG Running task: 1123 / 0x4d5e5d8
Jul 07 20:45:32-443470 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:32-443651 util-8620 DEBUG process_notify is running
Jul 07 20:45:32-443825 util-8620 DEBUG client_notify is running
Jul 07 20:45:32-444062 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:32-444424 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:32-444638 util-scheduler-8620 DEBUG Running task: 1124 / 0x46620a0
Jul 07 20:45:32-445048 util-8620 DEBUG receive_ready read 196/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:32-445314 util-scheduler-8620 DEBUG Adding task: 1125 / 0x4662248
Jul 07 20:45:32-445536 util-scheduler-8620 DEBUG Running task: 1002 / 0x4d64a70
Jul 07 20:45:32-445813 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:32-446059 cadet-tun-8620 DEBUG  kx started 65 s ago
Jul 07 20:45:32-446269 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:32-446469 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:32-446670 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:32-446945 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:32-447125 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:32-447348 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:32-447635 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:32-447831 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:32-448066 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:32-448274 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:32-448587 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:32-448787 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:32-449012 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:32-449220 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:32-449399 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:32-449604 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:32-449808 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:32-449985 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:32-450160 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:32-450400 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-450596 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:32-450774 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:32-451008 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-451201 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:32-451378 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:32-451576 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:32-451788 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:32-452097 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:32-452298 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:32-452469 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:32-452652 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:32-456203 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:32-457003 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:32-457184 cadet-tun-8620 DEBUG   e sending 2865303787
Jul 07 20:45:32-457423 cadet-tun-8620 DEBUG   e towards RF71
Jul 07 20:45:32-457624 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:32-457824 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:32-458051 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:32-458255 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:32-458477 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:32-458750 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:32-458947 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:32-459233 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:32-459443 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:32-459751 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:32-459950 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:32-460173 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:32-460355 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:32-460530 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:32-460732 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:32-460932 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:32-461108 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:32-461307 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:32-461544 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-461738 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:32-461915 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:32-462148 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-462400 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:32-462577 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:32-462809 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-463002 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:32-463178 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:32-463375 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:32-463623 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:32-463830 util-scheduler-8620 DEBUG Adding task: 1126 / 0x4d64a70
Jul 07 20:45:32-464091 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-464287 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-464477 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-464666 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-464856 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-465045 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-465257 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-465453 util-scheduler-8620 DEBUG Running task: 1125 / 0x4662248
Jul 07 20:45:32-465646 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:32-465859 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:32-466075 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:32-466282 util-scheduler-8620 DEBUG Adding task: 1127 / 0x4662248
Jul 07 20:45:32-466520 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-466712 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-466902 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-467091 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-467291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-467480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-467669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-467858 util-scheduler-8620 DEBUG Running task: 1127 / 0x4662248
Jul 07 20:45:32-468046 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:32-468254 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:32-468466 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:32-468672 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:32-468878 util-scheduler-8620 DEBUG Adding task: 1128 / 0x46620a0
Jul 07 20:45:32-469089 util-scheduler-8620 DEBUG Adding task: 1129 / 0x4662248
Jul 07 20:45:32-469352 util-scheduler-8620 DEBUG Checking readiness of task: 1128 / 0x46620a0
Jul 07 20:45:32-469546 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-469736 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-469925 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-470115 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-470303 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-470492 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-470680 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-470871 util-scheduler-8620 DEBUG Running task: 1128 / 0x46620a0
Jul 07 20:45:32-471055 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:32-471232 util-8620 DEBUG process_notify is running
Jul 07 20:45:32-471403 util-8620 DEBUG client_notify is running
Jul 07 20:45:32-471592 util-scheduler-8620 DEBUG Canceling task: 1120 / 0x4d6ff98
Jul 07 20:45:32-471815 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:32-472032 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:32-472264 cadet-p2p-8620 DEBUG Checking 0x6690d88 towards CMHCKRVP (->V8XX)
Jul 07 20:45:32-472497 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:32-472674 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:32-472861 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:32-473143 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:32-473362 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:32-473543 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:32-473730 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:32-473920 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:32-474100 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:32-474287 util-scheduler-8620 DEBUG Canceling task: 1115 / 0x4d707d0
Jul 07 20:45:32-474499 util-scheduler-8620 DEBUG Adding task: 1130 / 0x4d707d0
Jul 07 20:45:32-474743 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:32-474913 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:32-475135 cadet-p2p-8620 DEBUG Checking 0x68e2ab0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:32-475376 cadet-p2p-8620 DEBUG Checking 0x68e2ab0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:32-475554 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:32-475761 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:32-475983 util-scheduler-8620 DEBUG Adding task: 1131 / 0x4d6ff98
Jul 07 20:45:32-476162 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:32-476340 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:32-476539 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:32-476713 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:32-476887 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:32-477123 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-477341 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:32-477518 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:32-477751 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-477944 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:32-478121 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:32-478336 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:32-478545 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:32-478728 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:32-478931 util-scheduler-8620 DEBUG Adding task: 1132 / 0x4d6ff98
Jul 07 20:45:32-479152 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:32-479347 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:32-479549 util-scheduler-8620 DEBUG Adding task: 1133 / 0x46620a0
Jul 07 20:45:32-479750 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:32-480148 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:32-480349 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:32-480547 util-scheduler-8620 DEBUG Running task: 1129 / 0x4662248
Jul 07 20:45:32-480736 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:32-480929 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:32-481146 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:32-481422 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:32-481658 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:32-481887 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:32-482094 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:32-482337 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:32-482543 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:32-482729 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:32-482912 util-scheduler-8620 DEBUG Canceling task: 1122 / 0x4d707d0
Jul 07 20:45:32-483141 util-scheduler-8620 DEBUG Adding task: 1134 / 0x4d707d0
Jul 07 20:45:32-483321 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:32-483570 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:32-483776 util-scheduler-8620 DEBUG Adding task: 1135 / 0x4d5e5d8
Jul 07 20:45:32-483956 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:32-484154 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:32-484340 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:32-484512 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:32-484677 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:32-488585 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:32-489408 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:32-489640 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:32-489918 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:32-490092 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:32-490277 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:32-493348 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:32-493921 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:32-494100 cadet-tun-8620 DEBUG   e sending 1929337374
Jul 07 20:45:32-494305 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:32-494507 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:32-494733 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:32-494913 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:32-495133 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:32-495411 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:32-495609 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:32-495843 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:32-496049 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:32-496356 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:32-496554 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:32-496778 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:32-496991 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:32-497166 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:32-497394 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:32-497595 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:32-497771 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:32-497945 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:32-498182 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-498377 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:32-498553 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:32-498787 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-498979 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:32-499155 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:32-499387 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:32-499579 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:32-499754 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:32-499951 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:32-500133 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:32-500343 util-scheduler-8620 DEBUG Adding task: 1136 / 0x46620a0
Jul 07 20:45:32-500609 util-scheduler-8620 DEBUG Checking readiness of task: 1136 / 0x46620a0
Jul 07 20:45:32-500805 util-scheduler-8620 DEBUG Checking readiness of task: 1135 / 0x4d5e5d8
Jul 07 20:45:32-500997 util-scheduler-8620 DEBUG Checking readiness of task: 1133 / 0x46620a0
Jul 07 20:45:32-501188 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-501426 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-501616 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-501805 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-501994 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-502183 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-502371 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-502563 util-scheduler-8620 DEBUG Running task: 1133 / 0x46620a0
Jul 07 20:45:32-502748 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:32-502924 util-8620 DEBUG process_notify is running
Jul 07 20:45:32-503096 util-8620 DEBUG client_notify is running
Jul 07 20:45:32-503275 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:32-503470 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:32-503660 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:32-503975 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:32-504186 util-scheduler-8620 DEBUG Running task: 1135 / 0x4d5e5d8
Jul 07 20:45:32-504370 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:32-504544 util-8620 DEBUG process_notify is running
Jul 07 20:45:32-504713 util-8620 DEBUG client_notify is running
Jul 07 20:45:32-504932 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:32-505266 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:32-505482 util-scheduler-8620 DEBUG Running task: 1131 / 0x4d6ff98
Jul 07 20:45:32-505677 util-scheduler-8620 DEBUG Canceling task: 1132 / 0x4d6ff98
Jul 07 20:45:32-505896 util-scheduler-8620 DEBUG Adding task: 1137 / 0x4d6ff98
Jul 07 20:45:32-506115 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:32-506322 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:32-506606 util-scheduler-8620 DEBUG Adding task: 1138 / 0x46620a0
Jul 07 20:45:32-506869 util-scheduler-8620 DEBUG Checking readiness of task: 1138 / 0x46620a0
Jul 07 20:45:32-507063 util-scheduler-8620 DEBUG Checking readiness of task: 1136 / 0x46620a0
Jul 07 20:45:32-507254 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:32-507444 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:32-507633 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:32-507822 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:32-508011 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:32-508200 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:32-508389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:32-508579 util-scheduler-8620 DEBUG Running task: 1138 / 0x46620a0
Jul 07 20:45:32-508762 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:32-508937 util-8620 DEBUG process_notify is running
Jul 07 20:45:32-509106 util-8620 DEBUG client_notify is running
Jul 07 20:45:32-509309 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:32-509499 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:32-509686 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:32-509977 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:33-264342 util-scheduler-8620 DEBUG Checking readiness of task: 1136 / 0x46620a0
Jul 07 20:45:33-264726 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-264923 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-265116 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-265340 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-265536 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-265728 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-265919 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-266116 util-scheduler-8620 DEBUG Running task: 1136 / 0x46620a0
Jul 07 20:45:33-266541 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:33-266801 util-scheduler-8620 DEBUG Adding task: 1139 / 0x4662248
Jul 07 20:45:33-267098 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-267291 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-267481 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-267671 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-267861 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-268050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-268240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-268431 util-scheduler-8620 DEBUG Running task: 1139 / 0x4662248
Jul 07 20:45:33-268624 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:45:33-268824 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:45:33-269057 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `KNAS'
Jul 07 20:45:33-269348 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:33-269593 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:33-269823 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:33-270032 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:33-270280 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:33-270523 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:33-270714 cadet-con-8620 DEBUG  PID 17 (expected 17+)
Jul 07 20:45:33-270895 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:33-271086 util-scheduler-8620 DEBUG Canceling task: 1063 / 0x4d61c30
Jul 07 20:45:33-271311 util-scheduler-8620 DEBUG Adding task: 1140 / 0x4d61c30
Jul 07 20:45:33-271491 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:33-271752 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:33-271969 util-scheduler-8620 DEBUG Adding task: 1141 / 0x4d5e5d8
Jul 07 20:45:33-272153 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:33-272321 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:33-276518 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:33-277306 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:33-277502 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:33-280753 cadet-tun-8620 INFO <=== {              DATA} on KNAS
Jul 07 20:45:33-280957 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:45:33-281270 cadet-chn-8620 INFO <=== DATA 1 BCK on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:33-281697 cadet-chn-8620 WARNING MID 1 on channel KNAS:19 gid:40000000 (80000001 / 0) not expected (window: 2 - 65). Dropping!
Jul 07 20:45:33-281892 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:45:33-282075 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:45:33-282324 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:33-282542 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:33-282743 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:33-282924 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:33-283108 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:33-283288 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:33-283464 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:33-283634 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:33-283850 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:33-284024 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:33-284260 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:33-284446 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:33-284739 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:33-284911 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:33-285097 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:33-288201 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:33-288848 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:33-289026 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:33-289240 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:33-292393 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:33-292631 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:33-292817 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:33-293038 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:33-293254 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:45:33-293534 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (100 bytes)
Jul 07 20:45:33-293735 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:33-293914 cadet-con-8620 DEBUG last pid sent 19
Jul 07 20:45:33-294089 cadet-con-8620 DEBUG      ack recv 80
Jul 07 20:45:33-294261 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:33-294439 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:33-294674 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:33-294880 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:33-295192 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 100)
Jul 07 20:45:33-295393 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:33-295621 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:33-295832 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 19
Jul 07 20:45:33-296008 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:33-296215 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 100 bytes
Jul 07 20:45:33-296440 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:33-296667 util-scheduler-8620 DEBUG Adding task: 1142 / 0x4d5c9e8
Jul 07 20:45:33-296847 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:33-297051 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:33-297264 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:33-297440 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:33-297680 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:33-297875 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:33-298052 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:33-298250 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:33-298425 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:45:33-298650 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:33-298825 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:33-298999 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:33-299171 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:33-299392 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:33-299570 cadet-con-8620 DEBUG  ACK 81
Jul 07 20:45:33-299750 cadet-con-8620 DEBUG  last pid 17, last ack 80, qmax 11, q 0
Jul 07 20:45:33-300014 cadet-con-8620 INFO --> {               ACK} ( 81) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:33-300202 cadet-con-8620 DEBUG  ack 81
Jul 07 20:45:33-300378 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:33-300610 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:33-300816 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:33-301103 cadet-p2p-8620 INFO que {               ACK} ( 81) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:33-301325 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:33-301548 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:33-301729 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 19
Jul 07 20:45:33-301902 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:33-302106 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:33-302308 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:33-302483 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:33-302657 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:33-302893 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:33-303074 cadet-p2p-8620 DEBUG QQQ    payload , 81
Jul 07 20:45:33-303249 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:33-303493 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:33-303686 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:33-303862 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:33-304058 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:33-304240 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:33-304454 util-scheduler-8620 DEBUG Adding task: 1143 / 0x46620a0
Jul 07 20:45:33-304730 util-scheduler-8620 DEBUG Checking readiness of task: 1143 / 0x46620a0
Jul 07 20:45:33-304927 util-scheduler-8620 DEBUG Checking readiness of task: 1141 / 0x4d5e5d8
Jul 07 20:45:33-305120 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-305335 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-305528 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-305717 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-305906 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-306095 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-306303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-306496 util-scheduler-8620 DEBUG Running task: 1141 / 0x4d5e5d8
Jul 07 20:45:33-306682 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:33-306861 util-8620 DEBUG process_notify is running
Jul 07 20:45:33-307033 util-8620 DEBUG client_notify is running
Jul 07 20:45:33-307280 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:33-307489 util-scheduler-8620 DEBUG Adding task: 1144 / 0x4d5e5d8
Jul 07 20:45:33-307694 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:33-308048 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:33-308249 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:33-308448 util-scheduler-8620 DEBUG Running task: 1142 / 0x4d5c9e8
Jul 07 20:45:33-308658 util-scheduler-8620 DEBUG Adding task: 1145 / 0x4d5c9e8
Jul 07 20:45:33-308880 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:33-309076 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:33-309298 util-scheduler-8620 DEBUG Adding task: 1146 / 0x46620a0
Jul 07 20:45:33-309497 util-scheduler-8620 DEBUG Running task: 1043 / 0x5e31aa0
Jul 07 20:45:33-309733 cadet-con-8620 DEBUG FWD keepalive for 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-311349 cadet-con-8620 INFO keepalive FWD for connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-312517 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:45:33-312727 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:33-312912 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_PING
Jul 07 20:45:33-313098 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 1033
Jul 07 20:45:33-313306 cadet-tun-8620 DEBUG TTT  tq_head 0x5e34660, tq_tail 0x5e34660
Jul 07 20:45:33-313498 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:33-313669 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:33-313885 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:33-314057 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:33-314289 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:33-314535 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:33-314719 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:33-314923 cadet-tun-8620 DEBUG queue data on Tunnel D3TJ
Jul 07 20:45:33-315123 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:33-315300 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_PING
Jul 07 20:45:33-315486 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 1033
Jul 07 20:45:33-315668 cadet-tun-8620 DEBUG TTT  tq_head 0x5e34660, tq_tail 0x5e34660
Jul 07 20:45:33-315847 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:33-316016 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:33-316230 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:33-316399 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:33-316628 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:33-316873 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:33-317056 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:33-317613 util-scheduler-8620 DEBUG Checking readiness of task: 1146 / 0x46620a0
Jul 07 20:45:33-317813 util-scheduler-8620 DEBUG Checking readiness of task: 1144 / 0x4d5e5d8
Jul 07 20:45:33-318007 util-scheduler-8620 DEBUG Checking readiness of task: 1143 / 0x46620a0
Jul 07 20:45:33-318199 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-318390 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-318580 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-318771 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-318977 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-319168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-319358 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-319548 util-scheduler-8620 DEBUG Running task: 1144 / 0x4d5e5d8
Jul 07 20:45:33-319733 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:33-319909 util-8620 DEBUG process_notify is running
Jul 07 20:45:33-320079 util-8620 DEBUG client_notify is running
Jul 07 20:45:33-320308 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:33-320514 util-scheduler-8620 DEBUG Adding task: 1147 / 0x4d5e5d8
Jul 07 20:45:33-320715 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:45:33-321039 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:33-321261 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:33-321459 util-scheduler-8620 DEBUG Running task: 1146 / 0x46620a0
Jul 07 20:45:33-321643 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:33-321818 util-8620 DEBUG process_notify is running
Jul 07 20:45:33-321986 util-8620 DEBUG client_notify is running
Jul 07 20:45:33-322164 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:33-322359 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:33-322546 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:33-322848 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:33-323102 util-scheduler-8620 DEBUG Checking readiness of task: 1147 / 0x4d5e5d8
Jul 07 20:45:33-323306 util-scheduler-8620 DEBUG Checking readiness of task: 1143 / 0x46620a0
Jul 07 20:45:33-323497 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-323688 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-323878 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-324226 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-324420 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-324612 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-324802 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-324993 util-scheduler-8620 DEBUG Running task: 1147 / 0x4d5e5d8
Jul 07 20:45:33-325177 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:33-325374 util-8620 DEBUG process_notify is running
Jul 07 20:45:33-325547 util-8620 DEBUG client_notify is running
Jul 07 20:45:33-325758 util-8620 DEBUG Transmitting message of type 168 and size 40 to statistics service.
Jul 07 20:45:33-326060 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:33-417179 util-scheduler-8620 DEBUG Checking readiness of task: 1143 / 0x46620a0
Jul 07 20:45:33-417586 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:33-417784 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:33-417976 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:33-418168 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:33-418359 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:33-418550 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:33-418740 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:33-418934 util-scheduler-8620 DEBUG Running task: 1033 / 0x5e2de48
Jul 07 20:45:33-419174 cadet-tun-8620 INFO Re-key Tunnel D3TJ
Jul 07 20:45:33-419420 cadet-tun-8620 DEBUG  kx started 5 s ago
Jul 07 20:45:33-419655 cadet-tun-8620 INFO ===> EPHM for D3TJ
Jul 07 20:45:33-419858 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:33-420062 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:33-420297 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:33-420477 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:33-420707 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:33-420885 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:33-421302 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-421601 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (196 bytes)
Jul 07 20:45:33-421799 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:45:33-422038 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:33-422246 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:33-422565 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 196)
Jul 07 20:45:33-422857 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:33-423104 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-423289 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:33-423466 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:33-423671 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:33-423875 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:33-424050 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:33-424226 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:33-424467 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-424651 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-424828 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:33-425061 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-425266 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-425442 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:33-425676 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:33-425856 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-426031 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:33-426265 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:33-426446 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-426621 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:33-426854 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-427047 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:33-427223 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:33-427422 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:33-427626 cadet-tun-8620 INFO ===> PING for D3TJ
Jul 07 20:45:33-427938 cadet-tun-8620 DEBUG   sending 1699275036
Jul 07 20:45:33-428139 cadet-tun-8620 DEBUG   towards D3TJ
Jul 07 20:45:33-428310 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:33-428492 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:33-432108 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:33-432913 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:33-433094 cadet-tun-8620 DEBUG   e sending 839106922
Jul 07 20:45:33-433335 cadet-tun-8620 DEBUG   e towards J6Q9
Jul 07 20:45:33-433538 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:33-433738 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:33-433967 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:33-434146 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:33-434368 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:33-434546 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:33-434765 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-435153 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (80 bytes)
Jul 07 20:45:33-435373 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 3
Jul 07 20:45:33-435610 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:33-435818 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:33-436141 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 80)
Jul 07 20:45:33-436340 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:33-436563 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-436745 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:33-436919 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:33-437121 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:33-437359 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:33-437536 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:33-437710 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:33-437948 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-438130 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-438305 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:33-438537 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-438718 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-438892 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:33-439125 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:33-439305 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-439479 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:33-439712 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:33-439893 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:33-440067 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:33-440300 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-440492 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:33-440668 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:33-440900 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:33-441092 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:33-441291 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:33-441489 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:33-441738 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:33-441947 util-scheduler-8620 DEBUG Adding task: 1148 / 0x5e2de48
Jul 07 20:45:34-376229 util-scheduler-8620 DEBUG Checking readiness of task: 1143 / 0x46620a0
Jul 07 20:45:34-376631 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:34-376830 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:34-377025 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:34-377244 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:34-377440 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:34-377640 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:34-377834 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:34-378030 util-scheduler-8620 DEBUG Running task: 1143 / 0x46620a0
Jul 07 20:45:34-378455 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:34-378714 util-scheduler-8620 DEBUG Adding task: 1149 / 0x4662248
Jul 07 20:45:34-378995 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:34-379188 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:34-379380 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:34-379569 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:34-379760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:34-379983 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:34-380174 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:34-380364 util-scheduler-8620 DEBUG Running task: 1149 / 0x4662248
Jul 07 20:45:34-380557 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:34-380757 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:34-380990 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:34-381239 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:34-381450 util-scheduler-8620 DEBUG Adding task: 1150 / 0x46620a0
Jul 07 20:45:34-381640 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:34-381844 util-scheduler-8620 DEBUG Adding task: 1151 / 0x46620a0
Jul 07 20:45:34-382089 util-scheduler-8620 DEBUG Checking readiness of task: 1151 / 0x46620a0
Jul 07 20:45:34-382281 util-scheduler-8620 DEBUG Checking readiness of task: 1150 / 0x46620a0
Jul 07 20:45:34-382473 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:34-382663 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:34-382853 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:34-383043 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:34-383232 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:34-383420 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:34-383611 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:34-383803 util-scheduler-8620 DEBUG Running task: 1150 / 0x46620a0
Jul 07 20:45:34-383989 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:34-384167 util-8620 DEBUG process_notify is running
Jul 07 20:45:34-384339 util-8620 DEBUG client_notify is running
Jul 07 20:45:34-384529 util-scheduler-8620 DEBUG Canceling task: 1145 / 0x4d5c9e8
Jul 07 20:45:34-384753 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:34-384973 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:34-385237 cadet-p2p-8620 DEBUG Checking 0x690bce0 towards HS92G30M (->KNAS)
Jul 07 20:45:34-385474 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:34-385652 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:34-385845 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:34-386116 cadet-p2p-8620 INFO snd {               ACK} ( 81) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:34-386311 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:34-386492 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:34-386679 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:34-386853 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:34-387037 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:34-387212 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:34-387434 cadet-p2p-8620 DEBUG Checking 0x690aef0 towards HS92G30M (->KNAS)
Jul 07 20:45:34-387666 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:34-387848 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 19
Jul 07 20:45:34-388024 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:34-388251 cadet-p2p-8620 DEBUG Checking 0x690aef0 towards HS92G30M (->KNAS)
Jul 07 20:45:34-388480 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:34-388662 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 19
Jul 07 20:45:34-388834 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:34-389000 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:34-389230 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `KNAS'
Jul 07 20:45:34-389445 util-scheduler-8620 DEBUG Adding task: 1152 / 0x4d5c9e8
Jul 07 20:45:34-389636 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:34-389813 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:34-390029 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:34-390204 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:34-390378 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:34-390618 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:34-390813 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:34-390991 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:34-391190 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:34-391393 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:34-391576 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:34-391793 util-scheduler-8620 DEBUG Adding task: 1153 / 0x4d5c9e8
Jul 07 20:45:34-392013 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:34-392206 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:34-392408 util-scheduler-8620 DEBUG Adding task: 1154 / 0x46620a0
Jul 07 20:45:34-392609 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:34-393449 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:34-393658 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:34-393906 util-scheduler-8620 DEBUG Checking readiness of task: 1154 / 0x46620a0
Jul 07 20:45:34-394101 util-scheduler-8620 DEBUG Checking readiness of task: 1151 / 0x46620a0
Jul 07 20:45:34-394292 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:34-394483 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:34-394673 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:34-394862 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:34-395052 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:34-395244 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:34-395433 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:34-395625 util-scheduler-8620 DEBUG Running task: 1154 / 0x46620a0
Jul 07 20:45:34-395810 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:34-395986 util-8620 DEBUG process_notify is running
Jul 07 20:45:34-396157 util-8620 DEBUG client_notify is running
Jul 07 20:45:34-396335 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:34-396530 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:34-396719 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:34-397016 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:34-397247 util-scheduler-8620 DEBUG Running task: 1152 / 0x4d5c9e8
Jul 07 20:45:34-397441 util-scheduler-8620 DEBUG Canceling task: 1153 / 0x4d5c9e8
Jul 07 20:45:34-397658 util-scheduler-8620 DEBUG Adding task: 1155 / 0x4d5c9e8
Jul 07 20:45:34-397876 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:34-398071 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:34-398279 util-scheduler-8620 DEBUG Adding task: 1156 / 0x46620a0
Jul 07 20:45:34-398521 util-scheduler-8620 DEBUG Checking readiness of task: 1156 / 0x46620a0
Jul 07 20:45:34-398715 util-scheduler-8620 DEBUG Checking readiness of task: 1151 / 0x46620a0
Jul 07 20:45:34-398905 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:34-399094 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:34-399284 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:34-399472 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:34-399661 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:34-399849 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:34-400056 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:34-400246 util-scheduler-8620 DEBUG Running task: 1156 / 0x46620a0
Jul 07 20:45:34-400430 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:34-400605 util-8620 DEBUG process_notify is running
Jul 07 20:45:34-400773 util-8620 DEBUG client_notify is running
Jul 07 20:45:34-400948 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:34-401136 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:34-401349 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:34-401629 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-179906 util-scheduler-8620 DEBUG Checking readiness of task: 1151 / 0x46620a0
Jul 07 20:45:35-180327 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-180539 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-180739 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-180936 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-181134 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-181361 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-181560 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-181763 util-scheduler-8620 DEBUG Running task: 1151 / 0x46620a0
Jul 07 20:45:35-182205 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:35-182474 util-scheduler-8620 DEBUG Adding task: 1157 / 0x4662248
Jul 07 20:45:35-182769 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-182971 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-183170 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-183366 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-183560 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-183758 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-183952 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-184148 util-scheduler-8620 DEBUG Running task: 1157 / 0x4662248
Jul 07 20:45:35-184345 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:35-184549 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:35-184786 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:35-184999 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-186136 util-scheduler-8620 DEBUG Adding task: 1158 / 0x46620a0
Jul 07 20:45:35-186351 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:35-186564 util-scheduler-8620 DEBUG Adding task: 1159 / 0x46620a0
Jul 07 20:45:35-186878 util-scheduler-8620 DEBUG Checking readiness of task: 1159 / 0x46620a0
Jul 07 20:45:35-187073 util-scheduler-8620 DEBUG Checking readiness of task: 1158 / 0x46620a0
Jul 07 20:45:35-187505 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-187701 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-187892 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-188081 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-188286 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-188476 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-188665 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-188886 util-scheduler-8620 DEBUG Running task: 1158 / 0x46620a0
Jul 07 20:45:35-189074 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-189275 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-189470 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-189661 util-scheduler-8620 DEBUG Canceling task: 1137 / 0x4d6ff98
Jul 07 20:45:35-189893 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:35-190113 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:35-190353 cadet-p2p-8620 DEBUG Checking 0x68e2ab0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-190586 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:35-190763 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:35-190954 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:35-191240 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:35-191435 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:35-191615 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:35-191805 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:35-192000 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:35-192178 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:35-192363 util-scheduler-8620 DEBUG Canceling task: 1130 / 0x4d707d0
Jul 07 20:45:35-192578 util-scheduler-8620 DEBUG Adding task: 1160 / 0x4d707d0
Jul 07 20:45:35-192827 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:35-192998 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:35-194103 cadet-p2p-8620 DEBUG Checking 0x68e9428 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-194365 cadet-p2p-8620 DEBUG Checking 0x68e9428 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-194546 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:35-194754 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:35-194970 util-scheduler-8620 DEBUG Adding task: 1161 / 0x4d6ff98
Jul 07 20:45:35-195150 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:35-195326 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:35-195526 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:35-195700 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:35-195874 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:35-196113 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:35-196308 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:35-196862 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:35-197102 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:35-197320 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:35-197498 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:35-197699 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:35-197907 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:35-198142 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:35-198415 util-scheduler-8620 DEBUG Adding task: 1162 / 0x4d6ff98
Jul 07 20:45:35-198786 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:35-199499 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-199765 util-scheduler-8620 DEBUG Adding task: 1163 / 0x46620a0
Jul 07 20:45:35-200166 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:35-201167 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-201943 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:35-202227 util-scheduler-8620 DEBUG Checking readiness of task: 1163 / 0x46620a0
Jul 07 20:45:35-202434 util-scheduler-8620 DEBUG Checking readiness of task: 1159 / 0x46620a0
Jul 07 20:45:35-202635 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-202855 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-203049 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-203241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-203439 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-203707 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-204229 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-204431 util-scheduler-8620 DEBUG Running task: 1163 / 0x46620a0
Jul 07 20:45:35-204621 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-204803 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-204979 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-205161 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:35-205396 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:35-205595 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:35-205904 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-206125 util-scheduler-8620 DEBUG Running task: 1161 / 0x4d6ff98
Jul 07 20:45:35-206332 util-scheduler-8620 DEBUG Canceling task: 1162 / 0x4d6ff98
Jul 07 20:45:35-206568 util-scheduler-8620 DEBUG Adding task: 1164 / 0x4d6ff98
Jul 07 20:45:35-206803 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:35-207008 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-207221 util-scheduler-8620 DEBUG Adding task: 1165 / 0x46620a0
Jul 07 20:45:35-207489 util-scheduler-8620 DEBUG Checking readiness of task: 1165 / 0x46620a0
Jul 07 20:45:35-207692 util-scheduler-8620 DEBUG Checking readiness of task: 1159 / 0x46620a0
Jul 07 20:45:35-207890 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-208085 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-208286 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-208479 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-208673 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-208865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-209058 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-209284 util-scheduler-8620 DEBUG Running task: 1165 / 0x46620a0
Jul 07 20:45:35-209475 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-209656 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-209830 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-210013 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:35-210213 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:35-210409 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:35-210715 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-210935 util-scheduler-8620 DEBUG Running task: 1110 / 0x4d63a48
Jul 07 20:45:35-211124 cadet-chn-8620 DEBUG !!! RETRANSMIT 2
Jul 07 20:45:35-211509 cadet-chn-8620 INFO ===> {              DATA} FWD on channel KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:35-211720 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:45:35-211930 cadet-chn-8620 DEBUG   using existing copy: 0x5b978b8 {r:0x4d63a48 q:(nil) t:260}
Jul 07 20:45:35-212124 cadet-chn-8620 DEBUG   new chq: 0x691c0c8
Jul 07 20:45:35-212336 cadet-tun-8620 DEBUG GMT Send on Tunnel KNAS
Jul 07 20:45:35-213359 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:35-213947 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:35-214402 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:35-214822 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:35-215306 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:35-215732 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:35-216345 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:35-216903 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:35-217158 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:35-217370 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:35-217742 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:35-217924 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:35-218111 cadet-tun-8620 INFO   ENC with key 8G0G7MY3
Jul 07 20:45:35-222768 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:35-223975 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:35-224165 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:35-224354 cadet-tun-8620 INFO   HMAC with key 8G0G7MY3
Jul 07 20:45:35-227907 cadet-tun-8620 DEBUG tunnel_get_connection KNAS
Jul 07 20:45:35-228159 cadet-tun-8620 DEBUG   connection HS92G30M (->KNAS): 3
Jul 07 20:45:35-228342 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:35-228564 cadet-tun-8620 DEBUG  selected: connection HS92G30M (->KNAS)
Jul 07 20:45:35-228775 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:35-229061 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (96 bytes)
Jul 07 20:45:35-229283 cadet-con-8620 DEBUG   Q_N+ 0x4d61c34 0
Jul 07 20:45:35-229733 cadet-con-8620 DEBUG last pid sent 19
Jul 07 20:45:35-229912 cadet-con-8620 DEBUG      ack recv 80
Jul 07 20:45:35-230089 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:35-230267 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 1
Jul 07 20:45:35-230509 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:35-230721 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:35-231044 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 96)
Jul 07 20:45:35-231246 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:35-231474 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:35-231658 cadet-con-8620 DEBUG  last ack recv: 80, last pid sent: 19
Jul 07 20:45:35-231834 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:35-232039 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:45:35-232244 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:35-232421 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:35-232597 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:35-232847 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:35-233044 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:45:35-233247 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:45:35-233484 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:35-233679 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:35-233862 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:35-234075 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:35-234354 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:35-234578 util-scheduler-8620 DEBUG Adding task: 1166 / 0x4d5e5d8
Jul 07 20:45:35-234858 util-scheduler-8620 DEBUG Checking readiness of task: 1166 / 0x4d5e5d8
Jul 07 20:45:35-235060 util-scheduler-8620 DEBUG Checking readiness of task: 1159 / 0x46620a0
Jul 07 20:45:35-235257 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-235455 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-235647 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-235839 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-236036 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-236255 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-236445 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-236641 util-scheduler-8620 DEBUG Running task: 1159 / 0x46620a0
Jul 07 20:45:35-237062 util-8620 DEBUG receive_ready read 272/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:35-237338 util-scheduler-8620 DEBUG Adding task: 1167 / 0x4662248
Jul 07 20:45:35-237556 util-scheduler-8620 DEBUG Running task: 1166 / 0x4d5e5d8
Jul 07 20:45:35-237743 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:35-237923 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-238098 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-238334 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:35-238749 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:35-239063 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-239512 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-239716 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-239907 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-240097 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-240286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-240475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-240667 util-scheduler-8620 DEBUG Running task: 1167 / 0x4662248
Jul 07 20:45:35-240861 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:35-241065 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:35-241325 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:35-241590 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:35-241833 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:35-242067 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:35-242281 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:35-242533 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:35-242744 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:35-242932 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:35-243125 util-scheduler-8620 DEBUG Canceling task: 1134 / 0x4d707d0
Jul 07 20:45:35-243361 util-scheduler-8620 DEBUG Adding task: 1168 / 0x4d707d0
Jul 07 20:45:35-243560 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:35-243816 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:35-244032 util-scheduler-8620 DEBUG Adding task: 1169 / 0x4d5e5d8
Jul 07 20:45:35-244215 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:35-244418 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:35-861721 util-scheduler-8620 DEBUG Adding task: 1170 / 0x4662248
Jul 07 20:45:35-862175 util-scheduler-8620 DEBUG Checking readiness of task: 1169 / 0x4d5e5d8
Jul 07 20:45:35-862377 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-862570 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-862759 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-862949 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-863137 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-863326 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-863515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-863708 util-scheduler-8620 DEBUG Running task: 1169 / 0x4d5e5d8
Jul 07 20:45:35-863900 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:35-864108 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-864283 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-864520 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:35-864841 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:35-865057 util-scheduler-8620 DEBUG Running task: 1170 / 0x4662248
Jul 07 20:45:35-865269 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:35-865467 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:35-865696 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:35-865904 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-866113 util-scheduler-8620 DEBUG Adding task: 1171 / 0x46620a0
Jul 07 20:45:35-866299 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:35-866504 util-scheduler-8620 DEBUG Adding task: 1172 / 0x46620a0
Jul 07 20:45:35-866750 util-scheduler-8620 DEBUG Checking readiness of task: 1172 / 0x46620a0
Jul 07 20:45:35-866943 util-scheduler-8620 DEBUG Checking readiness of task: 1171 / 0x46620a0
Jul 07 20:45:35-867133 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-867323 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-867512 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-867700 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-867888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-868076 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-868264 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-868453 util-scheduler-8620 DEBUG Running task: 1171 / 0x46620a0
Jul 07 20:45:35-868636 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-868810 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-868978 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-869166 util-scheduler-8620 DEBUG Canceling task: 1164 / 0x4d6ff98
Jul 07 20:45:35-869415 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:35-869633 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:35-869873 cadet-p2p-8620 DEBUG Checking 0x68e9428 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-870105 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:35-870281 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:35-870471 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:35-870767 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:35-870964 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:35-871149 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:35-871342 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:35-871542 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:35-871725 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:35-871917 util-scheduler-8620 DEBUG Canceling task: 1160 / 0x4d707d0
Jul 07 20:45:35-872134 util-scheduler-8620 DEBUG Adding task: 1173 / 0x4d707d0
Jul 07 20:45:35-872385 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:35-872558 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:35-872786 cadet-p2p-8620 DEBUG Checking 0x68f80c0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-873028 cadet-p2p-8620 DEBUG Checking 0x68f80c0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:35-873232 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:35-873447 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:35-873664 util-scheduler-8620 DEBUG Adding task: 1174 / 0x4d6ff98
Jul 07 20:45:35-873845 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:35-874027 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:35-874229 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:35-874428 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:35-874603 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:35-874843 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:35-875038 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:35-875215 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:35-875413 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:35-875618 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:35-875800 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:35-876005 util-scheduler-8620 DEBUG Adding task: 1175 / 0x4d6ff98
Jul 07 20:45:35-876225 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:35-876421 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-876622 util-scheduler-8620 DEBUG Adding task: 1176 / 0x46620a0
Jul 07 20:45:35-876823 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:35-877168 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-877389 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:35-877590 util-scheduler-8620 DEBUG Running task: 1172 / 0x46620a0
Jul 07 20:45:35-877995 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:35-878227 util-scheduler-8620 DEBUG Adding task: 1177 / 0x4662248
Jul 07 20:45:35-878488 util-scheduler-8620 DEBUG Checking readiness of task: 1176 / 0x46620a0
Jul 07 20:45:35-878681 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-878870 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-879059 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-879258 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-879447 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-879634 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-879822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-880012 util-scheduler-8620 DEBUG Running task: 1176 / 0x46620a0
Jul 07 20:45:35-880195 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-880371 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-880540 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-880718 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:35-880911 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:35-881099 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:35-881400 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:35-881608 util-scheduler-8620 DEBUG Running task: 1177 / 0x4662248
Jul 07 20:45:35-881799 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:35-881994 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:35-882211 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:35-882461 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:35-882708 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:35-882937 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:35-883145 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:35-883390 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:35-883598 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:35-883783 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:35-883968 util-scheduler-8620 DEBUG Canceling task: 1168 / 0x4d707d0
Jul 07 20:45:35-884204 util-scheduler-8620 DEBUG Adding task: 1178 / 0x4d707d0
Jul 07 20:45:35-884384 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:35-884632 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:35-884840 util-scheduler-8620 DEBUG Adding task: 1179 / 0x4d5e5d8
Jul 07 20:45:35-885022 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:35-885244 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:35-885434 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:35-885609 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:35-885776 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:35-889557 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:35-891042 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:35-891274 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:35-891570 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:35-891744 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:35-891930 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:35-895024 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:35-895606 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:35-895784 cadet-tun-8620 DEBUG   e sending 2473832119
Jul 07 20:45:35-895991 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:35-896192 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:35-896421 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:35-896602 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:35-896823 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:35-897103 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:35-897323 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:35-897558 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:35-897763 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:35-898073 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:35-898272 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:35-898496 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:35-898678 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:35-898857 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:35-899064 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:35-899268 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:35-899446 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:35-899621 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:35-899862 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:35-900060 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:35-900239 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:35-900477 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:35-900671 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:35-900851 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:35-901052 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:35-901263 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:35-901485 util-scheduler-8620 DEBUG Adding task: 1180 / 0x46620a0
Jul 07 20:45:35-901696 util-scheduler-8620 DEBUG Running task: 1174 / 0x4d6ff98
Jul 07 20:45:35-901912 util-scheduler-8620 DEBUG Canceling task: 1175 / 0x4d6ff98
Jul 07 20:45:35-902135 util-scheduler-8620 DEBUG Adding task: 1181 / 0x4d6ff98
Jul 07 20:45:35-902361 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:35-902562 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:35-902763 util-scheduler-8620 DEBUG Adding task: 1182 / 0x46620a0
Jul 07 20:45:35-903034 util-scheduler-8620 DEBUG Checking readiness of task: 1182 / 0x46620a0
Jul 07 20:45:35-903239 util-scheduler-8620 DEBUG Checking readiness of task: 1180 / 0x46620a0
Jul 07 20:45:35-903432 util-scheduler-8620 DEBUG Checking readiness of task: 1179 / 0x4d5e5d8
Jul 07 20:45:35-903665 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:35-903871 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:35-904070 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:35-904266 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:35-904468 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:35-904662 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:35-904856 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:35-905056 util-scheduler-8620 DEBUG Running task: 1179 / 0x4d5e5d8
Jul 07 20:45:35-905278 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:35-905468 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-905646 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-905893 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:35-906244 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:35-906476 util-scheduler-8620 DEBUG Running task: 1182 / 0x46620a0
Jul 07 20:45:35-906665 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:35-906847 util-8620 DEBUG process_notify is running
Jul 07 20:45:35-907021 util-8620 DEBUG client_notify is running
Jul 07 20:45:35-907207 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:35-907409 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:35-907602 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:35-907913 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:37-465383 util-scheduler-8620 DEBUG Checking readiness of task: 1180 / 0x46620a0
Jul 07 20:45:37-465782 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:37-465994 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:37-467610 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:37-467835 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:37-468030 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:37-468234 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:37-468425 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:37-468618 util-scheduler-8620 DEBUG Running task: 1126 / 0x4d64a70
Jul 07 20:45:37-468858 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:45:37-469103 cadet-tun-8620 DEBUG  kx started 71 s ago
Jul 07 20:45:37-469338 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:45:37-469539 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:37-469741 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:37-469976 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:37-470156 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:37-470376 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:37-470684 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (196 bytes)
Jul 07 20:45:37-470880 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:37-471117 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:37-471325 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:37-471642 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 196)
Jul 07 20:45:37-471842 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:37-472066 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:37-472248 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:37-472448 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:37-472654 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:37-472856 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:37-473032 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:37-473242 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:37-473483 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-473678 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:37-473854 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:37-474088 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-474280 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:37-474455 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:37-474688 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-474879 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:37-475054 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:37-475251 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:37-475454 cadet-tun-8620 INFO ===> PING for V8XX
Jul 07 20:45:37-476166 cadet-tun-8620 DEBUG   sending 704158806
Jul 07 20:45:37-476373 cadet-tun-8620 DEBUG   towards V8XX
Jul 07 20:45:37-476544 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:37-476728 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:37-480625 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:37-482173 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:37-482404 cadet-tun-8620 DEBUG   e sending 2098016416
Jul 07 20:45:37-482639 cadet-tun-8620 DEBUG   e towards ZCB4
Jul 07 20:45:37-482851 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:37-483056 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:37-483290 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:37-483471 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:37-483806 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:37-484150 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (80 bytes)
Jul 07 20:45:37-484350 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 3
Jul 07 20:45:37-484586 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:37-484794 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:37-485107 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 80)
Jul 07 20:45:37-485818 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:37-486047 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:37-486244 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:37-486420 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:37-486624 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:37-486825 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:37-487001 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:37-487176 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:37-487412 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-487606 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:37-487783 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:37-488016 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-488208 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:37-488383 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:37-488616 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-488808 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:37-488983 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:37-489236 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:37-489429 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:37-489631 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:37-489828 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:37-490083 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:37-490293 util-scheduler-8620 DEBUG Adding task: 1183 / 0x4d64a70
Jul 07 20:45:37-768257 util-scheduler-8620 DEBUG Checking readiness of task: 1180 / 0x46620a0
Jul 07 20:45:37-768659 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:37-768859 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:37-769053 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:37-769269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:37-769462 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:37-769653 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:37-769843 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:37-770040 util-scheduler-8620 DEBUG Running task: 1180 / 0x46620a0
Jul 07 20:45:37-770534 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:37-770796 util-scheduler-8620 DEBUG Adding task: 1184 / 0x4662248
Jul 07 20:45:37-771076 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:37-771270 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:37-771462 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:37-771654 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:37-771845 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:37-772050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:37-772241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:37-772432 util-scheduler-8620 DEBUG Running task: 1184 / 0x4662248
Jul 07 20:45:37-772625 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:37-772826 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:37-773061 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:37-773402 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:37-773711 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:37-773944 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:37-774155 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:37-774402 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:37-774612 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:37-774798 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:37-774990 util-scheduler-8620 DEBUG Canceling task: 1178 / 0x4d707d0
Jul 07 20:45:37-775216 util-scheduler-8620 DEBUG Adding task: 1185 / 0x4d707d0
Jul 07 20:45:37-775395 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:37-775653 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:37-775874 util-scheduler-8620 DEBUG Adding task: 1186 / 0x4d5e5d8
Jul 07 20:45:37-776062 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:37-776266 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:38-418921 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:38-419331 util-scheduler-8620 DEBUG Adding task: 1187 / 0x46620a0
Jul 07 20:45:38-419629 util-scheduler-8620 DEBUG Checking readiness of task: 1187 / 0x46620a0
Jul 07 20:45:38-419830 util-scheduler-8620 DEBUG Checking readiness of task: 1186 / 0x4d5e5d8
Jul 07 20:45:38-420023 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:38-420214 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:38-420404 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:38-420594 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:38-420813 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:38-421003 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:38-421213 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:38-421410 util-scheduler-8620 DEBUG Running task: 1186 / 0x4d5e5d8
Jul 07 20:45:38-421597 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:38-421778 util-8620 DEBUG process_notify is running
Jul 07 20:45:38-421951 util-8620 DEBUG client_notify is running
Jul 07 20:45:38-422403 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:38-422714 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:38-422933 util-scheduler-8620 DEBUG Running task: 1187 / 0x46620a0
Jul 07 20:45:38-423343 util-8620 DEBUG receive_ready read 388/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:38-424560 util-scheduler-8620 DEBUG Adding task: 1188 / 0x4662248
Jul 07 20:45:38-424822 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:38-425016 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:38-425228 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:38-425419 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:38-425609 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:38-425797 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:38-425988 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:38-426177 util-scheduler-8620 DEBUG Running task: 1188 / 0x4662248
Jul 07 20:45:38-426367 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:38-426569 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:38-426799 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:38-427006 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:38-427209 util-scheduler-8620 DEBUG Adding task: 1189 / 0x46620a0
Jul 07 20:45:38-427435 util-scheduler-8620 DEBUG Adding task: 1190 / 0x4662248
Jul 07 20:45:38-427672 util-scheduler-8620 DEBUG Checking readiness of task: 1189 / 0x46620a0
Jul 07 20:45:38-427864 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:38-428055 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:38-428243 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:38-428431 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:38-428620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:38-428981 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:38-429177 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:38-429398 util-scheduler-8620 DEBUG Running task: 1189 / 0x46620a0
Jul 07 20:45:38-429588 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:38-429767 util-8620 DEBUG process_notify is running
Jul 07 20:45:38-429941 util-8620 DEBUG client_notify is running
Jul 07 20:45:38-430135 util-scheduler-8620 DEBUG Canceling task: 1181 / 0x4d6ff98
Jul 07 20:45:38-430371 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:38-430595 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:38-430851 cadet-p2p-8620 DEBUG Checking 0x68f80c0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:38-431098 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:38-431280 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:38-431475 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:38-431766 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:38-431993 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:38-432179 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:38-432370 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:38-432560 cadet-con-8620 DEBUG  C_P- 0x4d707d0 4
Jul 07 20:45:38-432737 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:38-432927 util-scheduler-8620 DEBUG Canceling task: 1173 / 0x4d707d0
Jul 07 20:45:38-433144 util-scheduler-8620 DEBUG Adding task: 1191 / 0x4d707d0
Jul 07 20:45:38-433420 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:38-433591 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:38-433815 cadet-p2p-8620 DEBUG Checking 0x6b769d0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:38-434054 cadet-p2p-8620 DEBUG Checking 0x6b769d0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:38-434232 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:38-434438 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:38-434654 util-scheduler-8620 DEBUG Adding task: 1192 / 0x4d6ff98
Jul 07 20:45:38-434832 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:38-435008 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:38-435207 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:38-435381 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:38-435556 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:38-435794 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-436200 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:38-436381 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:38-436630 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-436823 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:38-436999 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:38-437254 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-437449 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:38-437624 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:38-437822 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:38-438028 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:38-438209 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:38-438415 util-scheduler-8620 DEBUG Adding task: 1193 / 0x4d6ff98
Jul 07 20:45:38-438634 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:38-438833 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:38-439036 util-scheduler-8620 DEBUG Adding task: 1194 / 0x46620a0
Jul 07 20:45:38-439237 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:38-442999 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:38-443225 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:38-443435 util-scheduler-8620 DEBUG Running task: 1190 / 0x4662248
Jul 07 20:45:38-443627 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:38-443836 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:38-444066 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:38-444334 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:38-448485 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:38-448783 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:38-448995 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:38-449271 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:38-449481 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:38-449669 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:38-449865 util-scheduler-8620 DEBUG Canceling task: 1185 / 0x4d707d0
Jul 07 20:45:38-450125 util-scheduler-8620 DEBUG Adding task: 1195 / 0x4d707d0
Jul 07 20:45:38-450307 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:38-450569 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:38-450801 util-scheduler-8620 DEBUG Adding task: 1196 / 0x4d5e5d8
Jul 07 20:45:38-450983 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:38-451182 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:38-451367 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:38-451540 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:38-451705 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:38-455312 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:38-456165 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:38-456386 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:38-456682 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:38-456856 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:38-457042 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:38-460380 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:38-461872 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:38-462100 cadet-tun-8620 DEBUG   e sending 2807367047
Jul 07 20:45:38-462393 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:38-462608 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:38-462847 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:38-463036 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:38-463269 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:38-463567 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:38-463778 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 3
Jul 07 20:45:38-464025 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:38-464239 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:38-464563 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:38-464775 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:38-465012 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:38-465233 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:38-465436 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:38-465651 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:38-465863 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:38-466053 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:38-466230 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:38-466476 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-466675 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:38-466856 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:38-467095 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-467290 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:38-467468 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:38-467704 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-467899 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:38-468077 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:38-468312 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:38-468507 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:38-468685 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:38-468884 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:38-469115 util-scheduler-8620 DEBUG Adding task: 1197 / 0x4662248
Jul 07 20:45:38-469430 util-scheduler-8620 DEBUG Checking readiness of task: 1196 / 0x4d5e5d8
Jul 07 20:45:38-469630 util-scheduler-8620 DEBUG Checking readiness of task: 1194 / 0x46620a0
Jul 07 20:45:38-469821 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:38-470012 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:38-470230 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:38-470420 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:38-470610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:38-470802 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:38-470991 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:38-471185 util-scheduler-8620 DEBUG Running task: 1194 / 0x46620a0
Jul 07 20:45:38-471372 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:38-471551 util-8620 DEBUG process_notify is running
Jul 07 20:45:38-471724 util-8620 DEBUG client_notify is running
Jul 07 20:45:38-471904 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:38-472103 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:38-472294 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:38-472617 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:38-472831 util-scheduler-8620 DEBUG Running task: 1196 / 0x4d5e5d8
Jul 07 20:45:38-473014 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:38-473207 util-8620 DEBUG process_notify is running
Jul 07 20:45:38-473378 util-8620 DEBUG client_notify is running
Jul 07 20:45:38-473603 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:38-473889 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:38-474099 util-scheduler-8620 DEBUG Running task: 1197 / 0x4662248
Jul 07 20:45:38-474290 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:38-474488 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:38-474707 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:38-474958 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from D3TJ
Jul 07 20:45:38-475194 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:38-475421 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:38-475628 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:38-475832 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:38-476024 util-scheduler-8620 DEBUG Canceling task: 1091 / 0x5e2cf38
Jul 07 20:45:38-476248 util-scheduler-8620 DEBUG Adding task: 1198 / 0x5e2cf38
Jul 07 20:45:38-476426 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:38-476677 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:38-476892 util-scheduler-8620 DEBUG Adding task: 1199 / 0x4d5e5d8
Jul 07 20:45:38-477073 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:38-477291 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:39-112778 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:39-113184 util-scheduler-8620 DEBUG Adding task: 1200 / 0x46620a0
Jul 07 20:45:39-113439 util-scheduler-8620 DEBUG Running task: 1148 / 0x5e2de48
Jul 07 20:45:39-113673 cadet-tun-8620 INFO Re-key Tunnel D3TJ
Jul 07 20:45:39-113921 cadet-tun-8620 DEBUG  kx started 10 s ago
Jul 07 20:45:39-114130 cadet-tun-8620 INFO ===> EPHM for D3TJ
Jul 07 20:45:39-114332 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:39-114536 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:39-114772 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:39-114953 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:39-115179 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:39-115356 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:39-115579 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-115878 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (196 bytes)
Jul 07 20:45:39-116108 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 4
Jul 07 20:45:39-116349 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:39-116559 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:39-116899 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 196)
Jul 07 20:45:39-117118 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:39-117387 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-117584 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:39-117769 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:39-117989 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:39-118209 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:39-118396 cadet-p2p-8620 DEBUG QQQ  queue length: 7
Jul 07 20:45:39-118580 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:39-118845 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-119041 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-119223 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:39-119462 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-119647 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-119830 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:39-120079 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-120260 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-120434 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-120665 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-120845 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-121018 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-121732 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-121939 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-122118 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-122353 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-122546 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:39-122722 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-122954 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-123146 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-123322 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-123520 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:39-123727 cadet-tun-8620 INFO ===> PING for D3TJ
Jul 07 20:45:39-124041 cadet-tun-8620 DEBUG   sending 1699275036
Jul 07 20:45:39-124241 cadet-tun-8620 DEBUG   towards D3TJ
Jul 07 20:45:39-124411 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:39-124593 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:39-128147 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:39-129476 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:39-129661 cadet-tun-8620 DEBUG   e sending 3496647142
Jul 07 20:45:39-129873 cadet-tun-8620 DEBUG   e towards 69X6
Jul 07 20:45:39-130073 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:39-130274 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:39-130503 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:39-130682 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:39-130908 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:39-131084 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:39-131304 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-131579 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (80 bytes)
Jul 07 20:45:39-131778 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 5
Jul 07 20:45:39-132012 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:39-132228 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:39-132567 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 80)
Jul 07 20:45:39-132768 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:39-133000 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-133210 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:39-133391 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:39-134113 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:39-134335 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:39-134518 cadet-p2p-8620 DEBUG QQQ  queue length: 8
Jul 07 20:45:39-134704 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:39-134961 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-135152 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-135331 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:39-135590 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-135779 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-135958 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:39-136212 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-136401 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-136578 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-136819 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-137010 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-137220 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-137472 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-137672 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-137854 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-138096 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-138294 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:39-138474 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-138721 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-138921 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-139104 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-139346 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-139544 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:39-139720 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-140011 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:39-140349 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:39-140574 util-scheduler-8620 DEBUG Adding task: 1201 / 0x5e2de48
Jul 07 20:45:39-140782 util-scheduler-8620 DEBUG Running task: 1192 / 0x4d6ff98
Jul 07 20:45:39-140996 util-scheduler-8620 DEBUG Canceling task: 1193 / 0x4d6ff98
Jul 07 20:45:39-141241 util-scheduler-8620 DEBUG Adding task: 1202 / 0x4d6ff98
Jul 07 20:45:39-141468 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:39-141673 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-141881 util-scheduler-8620 DEBUG Adding task: 1203 / 0x46620a0
Jul 07 20:45:39-142156 util-scheduler-8620 DEBUG Checking readiness of task: 1203 / 0x46620a0
Jul 07 20:45:39-142355 util-scheduler-8620 DEBUG Checking readiness of task: 1200 / 0x46620a0
Jul 07 20:45:39-142546 util-scheduler-8620 DEBUG Checking readiness of task: 1199 / 0x4d5e5d8
Jul 07 20:45:39-142736 util-scheduler-8620 DEBUG Checking readiness of task: 1105 / 0x4663d68
Jul 07 20:45:39-143051 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-143280 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-143470 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-143659 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-143874 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-144063 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-144254 util-scheduler-8620 DEBUG Running task: 1105 / 0x4663d68
Jul 07 20:45:39-144674 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:39-144915 util-scheduler-8620 DEBUG Adding task: 1204 / 0x4663f10
Jul 07 20:45:39-145127 util-scheduler-8620 DEBUG Running task: 1199 / 0x4d5e5d8
Jul 07 20:45:39-145335 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:39-145515 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-146139 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-146376 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:39-146670 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:39-146884 util-scheduler-8620 DEBUG Running task: 1200 / 0x46620a0
Jul 07 20:45:39-147285 util-8620 DEBUG receive_ready read 156/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:39-147510 util-scheduler-8620 DEBUG Adding task: 1205 / 0x4662248
Jul 07 20:45:39-147718 util-scheduler-8620 DEBUG Running task: 1203 / 0x46620a0
Jul 07 20:45:39-147901 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-148076 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-148243 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-148422 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:39-148616 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:39-148804 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:39-149099 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-149390 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-149582 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-149772 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-149961 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-150150 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-150338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-150526 util-scheduler-8620 DEBUG Running task: 1205 / 0x4662248
Jul 07 20:45:39-150716 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:39-150916 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:39-151138 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:39-151337 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-151535 util-scheduler-8620 DEBUG Adding task: 1206 / 0x46620a0
Jul 07 20:45:39-151756 util-scheduler-8620 DEBUG Adding task: 1207 / 0x4662248
Jul 07 20:45:39-151954 util-scheduler-8620 DEBUG Running task: 1204 / 0x4663f10
Jul 07 20:45:39-152143 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:39-152333 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:39-152538 util-scheduler-8620 DEBUG Adding task: 1208 / 0x4663d68
Jul 07 20:45:39-152723 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:39-152942 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `P00P' with quota 34446
Jul 07 20:45:39-153139 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 bandwidth changed to 34446 Bps
Jul 07 20:45:39-153427 util-bandwidth-8620 DEBUG Tracker 0x4d6e518 updated, have 33481 Bps, last update was 12 s ago
Jul 07 20:45:39-153663 util-scheduler-8620 DEBUG Adding task: 1209 / 0x4d6e518
Jul 07 20:45:39-153911 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-154129 util-scheduler-8620 DEBUG Checking readiness of task: 1206 / 0x46620a0
Jul 07 20:45:39-154324 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-154515 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-154714 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-154908 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-155102 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-155292 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-155627 util-scheduler-8620 DEBUG Running task: 1206 / 0x46620a0
Jul 07 20:45:39-155823 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-156004 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-156179 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-156367 util-scheduler-8620 DEBUG Canceling task: 1056 / 0x5e2b838
Jul 07 20:45:39-156596 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:45:39-156815 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:39-157053 cadet-p2p-8620 DEBUG Checking 0x642f720 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-157311 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:39-157489 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:45:39-157660 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:45:39-158242 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:45:39-158417 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:45:39-158692 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 36)
Jul 07 20:45:39-158885 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:39-159065 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:39-159252 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:45:39-159434 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 6
Jul 07 20:45:39-159608 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:39-159829 cadet-p2p-8620 DEBUG Checking 0x64326b8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-160065 cadet-p2p-8620 DEBUG Checking 0x64326b8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-160243 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:39-160449 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:45:39-160668 util-scheduler-8620 DEBUG Adding task: 1210 / 0x5e2b838
Jul 07 20:45:39-160850 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:39-161027 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:45:39-161261 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:39-161437 cadet-p2p-8620 DEBUG QQQ  queue length: 7
Jul 07 20:45:39-161611 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:39-161847 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-162027 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-162201 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:45:39-162436 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-162616 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-162790 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-163022 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:39-163201 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:39-163375 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-163606 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-163798 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-163974 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-164206 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-164398 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:39-164574 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-164806 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-165018 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:39-165213 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:39-165449 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:39-165641 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:39-165816 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:39-166012 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:39-166220 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:45:39-166403 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:45:39-166612 util-scheduler-8620 DEBUG Adding task: 1211 / 0x5e2b838
Jul 07 20:45:39-166835 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:39-167042 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-167253 util-scheduler-8620 DEBUG Adding task: 1212 / 0x46620a0
Jul 07 20:45:39-167464 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:45:39-167868 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-168073 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:39-168286 util-scheduler-8620 DEBUG Running task: 1207 / 0x4662248
Jul 07 20:45:39-168559 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:39-168766 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:39-168986 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:39-169295 util-scheduler-8620 DEBUG Adding task: 1213 / 0x4662248
Jul 07 20:45:39-169555 util-scheduler-8620 DEBUG Checking readiness of task: 1212 / 0x46620a0
Jul 07 20:45:39-169749 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-170364 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-170559 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-170749 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-170939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-171128 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-171317 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-171508 util-scheduler-8620 DEBUG Running task: 1212 / 0x46620a0
Jul 07 20:45:39-171692 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-171870 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-172041 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-172219 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:39-172413 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:39-172601 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:39-172891 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-173098 util-scheduler-8620 DEBUG Running task: 1213 / 0x4662248
Jul 07 20:45:39-173312 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:39-173504 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:39-173722 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:39-173979 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:39-174232 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:39-174440 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:39-174623 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:39-174796 cadet-con-8620 DEBUG   ACK 81 (was 80)
Jul 07 20:45:39-175024 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:39-175276 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:39-175481 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:39-175662 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:39-175838 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:39-176046 util-scheduler-8620 DEBUG Adding task: 1214 / 0x46620a0
Jul 07 20:45:39-176244 util-scheduler-8620 DEBUG Running task: 1210 / 0x5e2b838
Jul 07 20:45:39-176437 util-scheduler-8620 DEBUG Canceling task: 1211 / 0x5e2b838
Jul 07 20:45:39-176650 util-scheduler-8620 DEBUG Adding task: 1215 / 0x5e2b838
Jul 07 20:45:39-176869 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:39-177065 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-177283 util-scheduler-8620 DEBUG Adding task: 1216 / 0x46620a0
Jul 07 20:45:39-177528 util-scheduler-8620 DEBUG Checking readiness of task: 1216 / 0x46620a0
Jul 07 20:45:39-177720 util-scheduler-8620 DEBUG Checking readiness of task: 1214 / 0x46620a0
Jul 07 20:45:39-177911 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-178112 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-178300 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-178489 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-178677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-178865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-179053 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-179246 util-scheduler-8620 DEBUG Running task: 1216 / 0x46620a0
Jul 07 20:45:39-179432 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-179612 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-179795 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-179979 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:39-180185 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:39-180398 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:39-180726 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-293760 util-scheduler-8620 DEBUG Checking readiness of task: 1214 / 0x46620a0
Jul 07 20:45:39-294139 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-294336 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-294528 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-294719 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-294918 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-295113 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-295316 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-295519 util-scheduler-8620 DEBUG Running task: 1209 / 0x4d6e518
Jul 07 20:45:39-376056 util-scheduler-8620 DEBUG Checking readiness of task: 1214 / 0x46620a0
Jul 07 20:45:39-376426 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-376623 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-376814 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-377006 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-377216 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-377408 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-377597 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-377792 util-scheduler-8620 DEBUG Running task: 1214 / 0x46620a0
Jul 07 20:45:39-378243 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:39-378499 util-scheduler-8620 DEBUG Adding task: 1217 / 0x4662248
Jul 07 20:45:39-378775 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-378968 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-379157 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-379346 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-379535 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-379724 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-379941 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-380131 util-scheduler-8620 DEBUG Running task: 1217 / 0x4662248
Jul 07 20:45:39-380322 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:39-380520 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:39-380752 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:39-380958 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-381164 util-scheduler-8620 DEBUG Adding task: 1218 / 0x46620a0
Jul 07 20:45:39-381373 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:39-381579 util-scheduler-8620 DEBUG Adding task: 1219 / 0x46620a0
Jul 07 20:45:39-381822 util-scheduler-8620 DEBUG Checking readiness of task: 1219 / 0x46620a0
Jul 07 20:45:39-382014 util-scheduler-8620 DEBUG Checking readiness of task: 1218 / 0x46620a0
Jul 07 20:45:39-382205 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-382394 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-382583 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-382772 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-382961 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-383162 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-383355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-383551 util-scheduler-8620 DEBUG Running task: 1218 / 0x46620a0
Jul 07 20:45:39-383738 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-383918 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-384092 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-384285 util-scheduler-8620 DEBUG Canceling task: 1155 / 0x4d5c9e8
Jul 07 20:45:39-384520 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 100 bytes.
Jul 07 20:45:39-384743 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:39-384996 cadet-p2p-8620 DEBUG Checking 0x690aef0 towards HS92G30M (->KNAS)
Jul 07 20:45:39-385748 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:39-385955 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 19
Jul 07 20:45:39-386134 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:39-386360 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:39-386539 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:45:39-386714 cadet-p2p-8620 DEBUG   payload ID 20
Jul 07 20:45:39-387005 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 1) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 100)
Jul 07 20:45:39-387200 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:39-387380 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:39-387567 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:39-387741 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:39-387909 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:39-388098 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:45:39-388286 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:45:39-388504 cadet-con-8620 DEBUG  C_P- 0x4d61c30 2
Jul 07 20:45:39-388733 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:39-388908 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:39-389081 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:39-389274 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:39-389473 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:39-389648 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:39-389821 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:39-390023 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:39-390202 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:39-390384 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:39-390562 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:39-390739 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:39-390907 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:39-391126 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:39-391298 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:39-391529 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:39-391712 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:39-391894 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:39-392085 util-scheduler-8620 DEBUG Canceling task: 1111 / 0x4d61c30
Jul 07 20:45:39-392314 util-scheduler-8620 DEBUG Adding task: 1220 / 0x4d61c30
Jul 07 20:45:39-392565 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:39-392744 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:39-392922 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 20
Jul 07 20:45:39-393095 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:39-393338 cadet-p2p-8620 DEBUG Checking 0x6924bb0 towards HS92G30M (->KNAS)
Jul 07 20:45:39-393567 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:39-393747 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 20
Jul 07 20:45:39-393919 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:39-394146 cadet-p2p-8620 DEBUG Checking 0x6924bb0 towards HS92G30M (->KNAS)
Jul 07 20:45:39-394375 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:39-394555 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 20
Jul 07 20:45:39-394728 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:39-394893 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:39-395100 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `KNAS'
Jul 07 20:45:39-395315 util-scheduler-8620 DEBUG Adding task: 1221 / 0x4d5c9e8
Jul 07 20:45:39-395493 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:39-395669 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:45:39-396094 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:39-396272 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:39-396447 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:39-396695 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on HS92G30M (->KNAS)
Jul 07 20:45:39-396893 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:45:39-397078 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:39-397310 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:39-398002 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 100 bytes.
Jul 07 20:45:39-398195 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:45:39-398423 util-scheduler-8620 DEBUG Adding task: 1222 / 0x4d5c9e8
Jul 07 20:45:39-398778 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:39-398981 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-399189 util-scheduler-8620 DEBUG Adding task: 1223 / 0x46620a0
Jul 07 20:45:39-399392 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:45:39-400181 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-400406 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:39-400673 util-scheduler-8620 DEBUG Checking readiness of task: 1223 / 0x46620a0
Jul 07 20:45:39-400870 util-scheduler-8620 DEBUG Checking readiness of task: 1219 / 0x46620a0
Jul 07 20:45:39-401061 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-401277 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-401468 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-401672 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-401862 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-402051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-402240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-402433 util-scheduler-8620 DEBUG Running task: 1223 / 0x46620a0
Jul 07 20:45:39-402618 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-402796 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-402967 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-403145 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:39-403342 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:39-403530 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:39-403811 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:39-404018 util-scheduler-8620 DEBUG Running task: 1221 / 0x4d5c9e8
Jul 07 20:45:39-404213 util-scheduler-8620 DEBUG Canceling task: 1222 / 0x4d5c9e8
Jul 07 20:45:39-404428 util-scheduler-8620 DEBUG Adding task: 1224 / 0x4d5c9e8
Jul 07 20:45:39-404645 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:39-404838 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:39-405040 util-scheduler-8620 DEBUG Adding task: 1225 / 0x46620a0
Jul 07 20:45:39-405300 util-scheduler-8620 DEBUG Checking readiness of task: 1225 / 0x46620a0
Jul 07 20:45:39-405493 util-scheduler-8620 DEBUG Checking readiness of task: 1219 / 0x46620a0
Jul 07 20:45:39-405683 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:39-405874 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:39-406063 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:39-406251 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:39-406439 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:39-406627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:39-406815 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:39-407004 util-scheduler-8620 DEBUG Running task: 1225 / 0x46620a0
Jul 07 20:45:39-407186 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:39-407360 util-8620 DEBUG process_notify is running
Jul 07 20:45:39-407527 util-8620 DEBUG client_notify is running
Jul 07 20:45:39-407703 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:39-407891 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:39-408077 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:39-408354 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:40-627413 util-scheduler-8620 DEBUG Checking readiness of task: 1219 / 0x46620a0
Jul 07 20:45:40-627797 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-627994 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-628186 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-628407 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-628623 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-628815 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-629004 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-629221 util-scheduler-8620 DEBUG Running task: 1219 / 0x46620a0
Jul 07 20:45:40-629644 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:40-629902 util-scheduler-8620 DEBUG Adding task: 1226 / 0x4662248
Jul 07 20:45:40-630180 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-630372 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-630562 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-630751 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-630940 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-631128 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-631316 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-631505 util-scheduler-8620 DEBUG Running task: 1226 / 0x4662248
Jul 07 20:45:40-631717 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:40-631917 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:40-632147 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:40-632410 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:40-632652 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:40-633431 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:40-633643 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:40-633890 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:40-634097 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:40-634284 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:40-634476 util-scheduler-8620 DEBUG Canceling task: 1195 / 0x4d707d0
Jul 07 20:45:40-634702 util-scheduler-8620 DEBUG Adding task: 1227 / 0x4d707d0
Jul 07 20:45:40-634883 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:40-635142 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:40-635356 util-scheduler-8620 DEBUG Adding task: 1228 / 0x4d5e5d8
Jul 07 20:45:40-635538 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:40-635738 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:40-635924 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:40-636097 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:40-636269 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:40-640033 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:40-640907 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:40-641142 util-scheduler-8620 DEBUG Canceling task: 1183 / 0x4d64a70
Jul 07 20:45:40-641422 util-scheduler-8620 DEBUG Adding task: 1229 / 0x4d64a70
Jul 07 20:45:40-641901 cadet-tun-8620 DEBUG Tunnel V8XX estate was CADET_TUNNEL_KEY_PING
Jul 07 20:45:40-642269 cadet-tun-8620 DEBUG Tunnel V8XX estate is now CADET_TUNNEL_KEY_OK
Jul 07 20:45:40-642636 cadet-tun-8620 DEBUG GCT_send_queued_data on tunnel V8XX
Jul 07 20:45:40-642845 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:40-643027 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:40-643211 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:40-643392 cadet-tun-8620 DEBUG TTT  tq_head 0x4d65b90, tq_tail 0x4d65b90
Jul 07 20:45:40-643571 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:40-643741 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:40-643961 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:40-644133 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:40-644397 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:40-644581 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:40-644780 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:40-644955 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:40-645136 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:40-645338 cadet-tun-8620 DEBUG TTT  tq_head 0x4d65b90, tq_tail 0x4d65b90
Jul 07 20:45:40-645516 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:40-645684 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:40-645896 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:40-646067 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:40-646294 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:40-646479 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:40-646749 cadet-tun-8620 DEBUG   buffer space: 11
Jul 07 20:45:40-647019 cadet-tun-8620 DEBUG   tq head: 0x4d65b90
Jul 07 20:45:40-647350 cadet-tun-8620 DEBUG  sending queued data
Jul 07 20:45:40-647559 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:45:40-647760 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:40-647937 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:40-648135 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:40-648316 cadet-tun-8620 DEBUG TTT  tq_head 0x4d65b90, tq_tail 0x4d65b90
Jul 07 20:45:40-648494 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:40-648662 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:40-648875 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:40-649046 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:40-649294 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:40-649479 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:40-649775 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:40-649947 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:40-650132 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:40-653508 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:40-654316 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:40-654509 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:40-654699 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:45:40-658104 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:40-658381 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:40-658566 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:40-658791 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:40-658990 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:45:40-659268 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection CMHCKRVP (->V8XX) (96 bytes)
Jul 07 20:45:40-659470 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:45:40-659650 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:45:40-659826 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:45:40-660000 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:40-660178 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 4
Jul 07 20:45:40-660417 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:40-660632 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:40-660957 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 96)
Jul 07 20:45:40-661161 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:40-661416 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:40-661599 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:40-661775 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:40-661985 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:40-662194 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:40-662370 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:40-662574 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:40-662822 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:40-663019 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:40-663198 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:40-663435 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:40-663629 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:40-663807 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:40-664043 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:40-664236 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:40-664414 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:40-664649 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:40-664843 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:40-665021 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:40-665277 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:40-665473 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:40-665663 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:40-665863 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:40-666233 cadet-tun-8620 DEBUG GCT_send_queued_data end
Jul 07 20:45:40-666426 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:40-666650 util-scheduler-8620 DEBUG Adding task: 1230 / 0x46620a0
Jul 07 20:45:40-666937 util-scheduler-8620 DEBUG Checking readiness of task: 1230 / 0x46620a0
Jul 07 20:45:40-667136 util-scheduler-8620 DEBUG Checking readiness of task: 1228 / 0x4d5e5d8
Jul 07 20:45:40-667330 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-667522 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-667712 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-667917 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-668107 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-668297 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-668487 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-668682 util-scheduler-8620 DEBUG Running task: 1228 / 0x4d5e5d8
Jul 07 20:45:40-668868 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:40-669048 util-8620 DEBUG process_notify is running
Jul 07 20:45:40-669241 util-8620 DEBUG client_notify is running
Jul 07 20:45:40-669476 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:40-669791 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:40-783140 util-scheduler-8620 DEBUG Checking readiness of task: 1230 / 0x46620a0
Jul 07 20:45:40-783494 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-783691 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-783882 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-784073 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-784264 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-784455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-784643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-784838 util-scheduler-8620 DEBUG Running task: 1230 / 0x46620a0
Jul 07 20:45:40-785278 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:40-785539 util-scheduler-8620 DEBUG Adding task: 1231 / 0x4662248
Jul 07 20:45:40-785815 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-786035 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-786226 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-786417 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-786606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-786795 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-786983 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-787172 util-scheduler-8620 DEBUG Running task: 1231 / 0x4662248
Jul 07 20:45:40-787363 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:40-787566 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:40-787801 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:40-788068 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:40-788312 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:40-788544 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:40-788753 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:40-789001 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:40-789403 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:40-789606 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:40-789803 util-scheduler-8620 DEBUG Canceling task: 1227 / 0x4d707d0
Jul 07 20:45:40-790113 util-scheduler-8620 DEBUG Adding task: 1232 / 0x4d707d0
Jul 07 20:45:40-790346 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:40-790609 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:40-790825 util-scheduler-8620 DEBUG Adding task: 1233 / 0x4d5e5d8
Jul 07 20:45:40-791008 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:40-791211 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:40-791429 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:40-791635 util-scheduler-8620 DEBUG Adding task: 1234 / 0x46620a0
Jul 07 20:45:40-791894 util-scheduler-8620 DEBUG Checking readiness of task: 1234 / 0x46620a0
Jul 07 20:45:40-792088 util-scheduler-8620 DEBUG Checking readiness of task: 1233 / 0x4d5e5d8
Jul 07 20:45:40-792281 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-792470 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-792659 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-792847 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-793036 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-793245 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-793436 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-793628 util-scheduler-8620 DEBUG Running task: 1233 / 0x4d5e5d8
Jul 07 20:45:40-793813 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:40-793990 util-8620 DEBUG process_notify is running
Jul 07 20:45:40-794161 util-8620 DEBUG client_notify is running
Jul 07 20:45:40-794395 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:40-794601 util-scheduler-8620 DEBUG Adding task: 1235 / 0x4d5e5d8
Jul 07 20:45:40-794803 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:40-795095 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:40-795294 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:40-795536 util-scheduler-8620 DEBUG Checking readiness of task: 1235 / 0x4d5e5d8
Jul 07 20:45:40-795729 util-scheduler-8620 DEBUG Checking readiness of task: 1234 / 0x46620a0
Jul 07 20:45:40-795920 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:40-796109 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:40-796320 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:40-796512 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:40-796702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:40-796891 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:40-797079 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:40-797290 util-scheduler-8620 DEBUG Running task: 1235 / 0x4d5e5d8
Jul 07 20:45:40-797475 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:40-797649 util-8620 DEBUG process_notify is running
Jul 07 20:45:40-797818 util-8620 DEBUG client_notify is running
Jul 07 20:45:40-798027 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:40-798318 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:41-031880 util-scheduler-8620 DEBUG Checking readiness of task: 1234 / 0x46620a0
Jul 07 20:45:41-032229 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:41-032431 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:41-032627 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:41-032824 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:41-033020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:41-033242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:41-033440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:41-033639 util-scheduler-8620 DEBUG Running task: 1234 / 0x46620a0
Jul 07 20:45:41-034060 util-8620 DEBUG receive_ready read 304/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:41-034316 util-scheduler-8620 DEBUG Adding task: 1236 / 0x4662248
Jul 07 20:45:41-034594 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:41-034788 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:41-034980 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:41-035171 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:41-035362 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:41-035553 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:41-035744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:41-035934 util-scheduler-8620 DEBUG Running task: 1236 / 0x4662248
Jul 07 20:45:41-036126 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:41-036377 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:41-036610 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:41-036902 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from D3TJ
Jul 07 20:45:41-037144 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:41-037395 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:41-037606 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:41-037801 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:41-037994 util-scheduler-8620 DEBUG Canceling task: 1198 / 0x5e2cf38
Jul 07 20:45:41-038220 util-scheduler-8620 DEBUG Adding task: 1237 / 0x5e2cf38
Jul 07 20:45:41-038401 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:41-038658 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:41-038874 util-scheduler-8620 DEBUG Adding task: 1238 / 0x4d5e5d8
Jul 07 20:45:41-039057 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:41-039257 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:41-673400 util-scheduler-8620 DEBUG Adding task: 1239 / 0x4662248
Jul 07 20:45:41-673883 util-scheduler-8620 DEBUG Checking readiness of task: 1238 / 0x4d5e5d8
Jul 07 20:45:41-674095 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:41-674373 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:41-674571 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:41-674761 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:41-674950 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:41-675140 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:41-675329 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:41-675523 util-scheduler-8620 DEBUG Running task: 1238 / 0x4d5e5d8
Jul 07 20:45:41-675713 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:41-675894 util-8620 DEBUG process_notify is running
Jul 07 20:45:41-676066 util-8620 DEBUG client_notify is running
Jul 07 20:45:41-676303 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:41-676622 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:41-676834 util-scheduler-8620 DEBUG Running task: 1239 / 0x4662248
Jul 07 20:45:41-677025 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:45:41-677244 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:45:41-677475 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `D3TJ'
Jul 07 20:45:41-677738 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection BFARXZN9 from D3TJ
Jul 07 20:45:41-678387 cadet-con-8620 DEBUG   via peer D3TJ
Jul 07 20:45:41-678667 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:41-678878 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:41-679118 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:41-679325 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:41-679688 cadet-con-8620 DEBUG   ACK
Jul 07 20:45:41-679934 cadet-con-8620 DEBUG Connection BFARXZN9 (->D3TJ) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:45:41-680121 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:41-680318 util-scheduler-8620 DEBUG Canceling task: 1237 / 0x5e2cf38
Jul 07 20:45:41-680547 util-scheduler-8620 DEBUG Adding task: 1240 / 0x5e2cf38
Jul 07 20:45:41-680852 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:45:41-681046 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:41-681291 util-scheduler-8620 DEBUG Adding task: 1241 / 0x46620a0
Jul 07 20:45:41-681564 util-scheduler-8620 DEBUG Checking readiness of task: 1241 / 0x46620a0
Jul 07 20:45:41-681761 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:41-681953 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:41-682145 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:41-682336 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:41-682527 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:41-682718 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:41-682909 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:41-683102 util-scheduler-8620 DEBUG Running task: 1241 / 0x46620a0
Jul 07 20:45:41-683522 util-8620 DEBUG receive_ready read 580/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:41-683765 util-scheduler-8620 DEBUG Adding task: 1242 / 0x4662248
Jul 07 20:45:41-684019 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:41-684213 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:41-684405 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:41-684621 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:41-684824 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:41-685015 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:41-685229 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:41-685422 util-scheduler-8620 DEBUG Running task: 1242 / 0x4662248
Jul 07 20:45:41-685618 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:41-685819 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:41-686043 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:41-686304 cadet-con-8620 INFO <-- {                KX} on connection BFARXZN9 from D3TJ
Jul 07 20:45:41-686556 cadet-con-8620 DEBUG  on connection BFARXZN9 (->D3TJ)
Jul 07 20:45:41-686791 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:45:41-687003 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:41-687196 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:41-687388 util-scheduler-8620 DEBUG Canceling task: 1240 / 0x5e2cf38
Jul 07 20:45:41-687609 util-scheduler-8620 DEBUG Adding task: 1243 / 0x5e2cf38
Jul 07 20:45:41-687789 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:41-688051 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:41-688266 util-scheduler-8620 DEBUG Adding task: 1244 / 0x4d5e5d8
Jul 07 20:45:41-688450 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:41-688651 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:42-307733 util-scheduler-8620 DEBUG Adding task: 1245 / 0x4662248
Jul 07 20:45:42-308193 util-scheduler-8620 DEBUG Checking readiness of task: 1244 / 0x4d5e5d8
Jul 07 20:45:42-308397 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:42-308591 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:42-308782 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:42-308972 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:42-309162 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:42-309377 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:42-309568 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:42-309763 util-scheduler-8620 DEBUG Running task: 1244 / 0x4d5e5d8
Jul 07 20:45:42-309950 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:42-310131 util-8620 DEBUG process_notify is running
Jul 07 20:45:42-310315 util-8620 DEBUG client_notify is running
Jul 07 20:45:42-310554 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:42-310897 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:42-311111 util-scheduler-8620 DEBUG Running task: 1245 / 0x4662248
Jul 07 20:45:42-311302 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:42-311505 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:42-311744 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:42-312007 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:42-312248 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:42-312479 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:42-312687 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:42-312934 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:42-313142 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:42-313355 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:42-313546 util-scheduler-8620 DEBUG Canceling task: 1232 / 0x4d707d0
Jul 07 20:45:42-313770 util-scheduler-8620 DEBUG Adding task: 1246 / 0x4d707d0
Jul 07 20:45:42-313978 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:42-314875 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:42-315102 util-scheduler-8620 DEBUG Adding task: 1247 / 0x4d5e5d8
Jul 07 20:45:42-315287 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:42-315489 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:42-966325 util-scheduler-8620 DEBUG Canceling task: 1229 / 0x4d64a70
Jul 07 20:45:42-967212 util-scheduler-8620 DEBUG Adding task: 1248 / 0x4d64a70
Jul 07 20:45:42-967550 util-scheduler-8620 DEBUG Adding task: 1249 / 0x4662248
Jul 07 20:45:42-967838 util-scheduler-8620 DEBUG Checking readiness of task: 1247 / 0x4d5e5d8
Jul 07 20:45:42-968039 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:42-968232 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:42-968422 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:42-968611 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:42-968800 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:42-968990 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:42-969178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:42-969397 util-scheduler-8620 DEBUG Running task: 1247 / 0x4d5e5d8
Jul 07 20:45:42-969583 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:42-969764 util-8620 DEBUG process_notify is running
Jul 07 20:45:42-969937 util-8620 DEBUG client_notify is running
Jul 07 20:45:42-970176 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:42-970501 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:42-970713 util-scheduler-8620 DEBUG Running task: 1249 / 0x4662248
Jul 07 20:45:42-970904 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:42-971104 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:42-971333 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:42-971596 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:42-972161 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:42-972813 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:42-973037 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:42-973324 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:42-973538 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:42-973728 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:42-973930 util-scheduler-8620 DEBUG Canceling task: 1246 / 0x4d707d0
Jul 07 20:45:42-974166 util-scheduler-8620 DEBUG Adding task: 1250 / 0x4d707d0
Jul 07 20:45:42-974349 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:42-974616 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:42-974837 util-scheduler-8620 DEBUG Adding task: 1251 / 0x4d5e5d8
Jul 07 20:45:42-975020 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:42-975222 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:42-975411 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:42-975585 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:42-975751 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:42-979360 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:42-980837 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:42-981070 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:42-981398 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:42-981574 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:42-981762 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:42-984894 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:42-985523 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:42-985762 cadet-tun-8620 DEBUG   e sending 1143861346
Jul 07 20:45:42-985971 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:42-986209 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:42-986440 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:42-986622 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:42-986844 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:42-987130 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:42-987330 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 5
Jul 07 20:45:42-987566 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:42-987774 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:42-988122 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:42-988324 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:42-988551 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:42-988735 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:42-988912 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:42-989118 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:42-989348 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:42-989525 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:42-989700 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:42-989941 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:42-990137 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:42-990314 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:42-990550 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:42-990745 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:42-990922 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:42-991157 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:42-991350 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:42-991527 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:42-991781 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:42-992006 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:42-992189 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-000665 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-000884 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:43-001067 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:43-001407 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-001608 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-001788 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-001991 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:43-002182 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-002406 util-scheduler-8620 DEBUG Adding task: 1252 / 0x46620a0
Jul 07 20:45:43-002693 util-scheduler-8620 DEBUG Checking readiness of task: 1252 / 0x46620a0
Jul 07 20:45:43-002896 util-scheduler-8620 DEBUG Checking readiness of task: 1251 / 0x4d5e5d8
Jul 07 20:45:43-003090 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-003283 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-003474 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-003666 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-003857 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-004049 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-004241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-004436 util-scheduler-8620 DEBUG Running task: 1251 / 0x4d5e5d8
Jul 07 20:45:43-004629 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:43-004832 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-005008 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-005270 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:43-005720 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:43-005993 util-scheduler-8620 DEBUG Running task: 1252 / 0x46620a0
Jul 07 20:45:43-006409 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-006656 util-scheduler-8620 DEBUG Adding task: 1253 / 0x4662248
Jul 07 20:45:43-006911 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-007621 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-007819 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-008013 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-008205 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-008398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-008589 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-008782 util-scheduler-8620 DEBUG Running task: 1253 / 0x4662248
Jul 07 20:45:43-008976 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-009179 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-009427 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-009636 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-009842 util-scheduler-8620 DEBUG Adding task: 1254 / 0x46620a0
Jul 07 20:45:43-010054 util-scheduler-8620 DEBUG Adding task: 1255 / 0x4662248
Jul 07 20:45:43-010295 util-scheduler-8620 DEBUG Checking readiness of task: 1254 / 0x46620a0
Jul 07 20:45:43-010491 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-010683 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-010876 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-011067 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-011259 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-011451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-011643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-011835 util-scheduler-8620 DEBUG Running task: 1254 / 0x46620a0
Jul 07 20:45:43-012022 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-012199 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-012372 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-012562 util-scheduler-8620 DEBUG Canceling task: 1202 / 0x4d6ff98
Jul 07 20:45:43-012790 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:43-013013 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:43-013285 cadet-p2p-8620 DEBUG Checking 0x6b769d0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-013523 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:43-013704 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:43-013894 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-014179 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:43-014377 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-014562 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-014754 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:43-014945 cadet-con-8620 DEBUG  C_P- 0x4d707d0 6
Jul 07 20:45:43-015126 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:43-015312 util-scheduler-8620 DEBUG Canceling task: 1191 / 0x4d707d0
Jul 07 20:45:43-015543 util-scheduler-8620 DEBUG Adding task: 1256 / 0x4d707d0
Jul 07 20:45:43-015798 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-015971 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-016197 cadet-p2p-8620 DEBUG Checking 0x6b78618 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-016439 cadet-p2p-8620 DEBUG Checking 0x6b78618 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-016622 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-016832 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:45:43-017047 util-scheduler-8620 DEBUG Adding task: 1257 / 0x4d6ff98
Jul 07 20:45:43-017252 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-017433 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:43-017634 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:43-017813 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:43-017989 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:43-018229 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-018427 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-018607 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-018844 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-019040 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-019218 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-019453 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-019649 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-019827 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-020064 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-020260 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:43-020439 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:43-020674 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-020870 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-021049 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-021272 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:43-021483 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:43-021670 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:43-021876 util-scheduler-8620 DEBUG Adding task: 1258 / 0x4d6ff98
Jul 07 20:45:43-022098 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-022299 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-022500 util-scheduler-8620 DEBUG Adding task: 1259 / 0x46620a0
Jul 07 20:45:43-022702 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:43-024194 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-024403 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-024612 util-scheduler-8620 DEBUG Running task: 1255 / 0x4662248
Jul 07 20:45:43-024805 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-025073 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-025319 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:43-025503 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-025710 util-scheduler-8620 DEBUG Adding task: 1260 / 0x4662248
Jul 07 20:45:43-025956 util-scheduler-8620 DEBUG Checking readiness of task: 1259 / 0x46620a0
Jul 07 20:45:43-026153 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-026347 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-026539 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-026731 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-026939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-027131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-027323 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-027515 util-scheduler-8620 DEBUG Running task: 1259 / 0x46620a0
Jul 07 20:45:43-027701 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-027880 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-028054 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-028234 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-028449 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-028650 util-scheduler-8620 DEBUG Adding task: 1261 / 0x46620a0
Jul 07 20:45:43-028849 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-029152 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-029374 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-029572 util-scheduler-8620 DEBUG Running task: 1260 / 0x4662248
Jul 07 20:45:43-029763 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-029957 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-030171 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:43-030728 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-030915 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-031123 util-scheduler-8620 DEBUG Adding task: 1262 / 0x46620a0
Jul 07 20:45:43-031325 util-scheduler-8620 DEBUG Running task: 1257 / 0x4d6ff98
Jul 07 20:45:43-031522 util-scheduler-8620 DEBUG Canceling task: 1258 / 0x4d6ff98
Jul 07 20:45:43-031739 util-scheduler-8620 DEBUG Adding task: 1263 / 0x4d6ff98
Jul 07 20:45:43-031959 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-032137 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-032375 util-scheduler-8620 DEBUG Checking readiness of task: 1262 / 0x46620a0
Jul 07 20:45:43-032572 util-scheduler-8620 DEBUG Checking readiness of task: 1261 / 0x46620a0
Jul 07 20:45:43-032765 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-032958 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-033149 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-033392 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-033584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-033777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-033967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-034160 util-scheduler-8620 DEBUG Running task: 1261 / 0x46620a0
Jul 07 20:45:43-034346 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-034524 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-034699 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-034880 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-035091 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-035290 util-scheduler-8620 DEBUG Adding task: 1264 / 0x46620a0
Jul 07 20:45:43-035488 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-035809 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-036008 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-036220 util-scheduler-8620 DEBUG Running task: 1262 / 0x46620a0
Jul 07 20:45:43-036624 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-036869 util-scheduler-8620 DEBUG Adding task: 1265 / 0x4662248
Jul 07 20:45:43-037121 util-scheduler-8620 DEBUG Checking readiness of task: 1264 / 0x46620a0
Jul 07 20:45:43-037342 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-037535 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-037728 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-037919 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-038111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-038302 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-038493 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-038685 util-scheduler-8620 DEBUG Running task: 1264 / 0x46620a0
Jul 07 20:45:43-038872 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-039049 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-039220 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-039669 util-scheduler-8620 DEBUG Canceling task: 1215 / 0x5e2b838
Jul 07 20:45:43-039918 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:45:43-040141 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:43-040378 cadet-p2p-8620 DEBUG Checking 0x64326b8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-040614 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:43-040795 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:45:43-040967 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:45:43-041140 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:45:43-041337 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:45:43-041597 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 36)
Jul 07 20:45:43-041792 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-041973 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-042162 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:45:43-042343 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 5
Jul 07 20:45:43-042519 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-042741 cadet-p2p-8620 DEBUG Checking 0x6692f88 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-042982 cadet-p2p-8620 DEBUG Checking 0x6692f88 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-043164 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-043370 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `D3TJ'
Jul 07 20:45:43-043587 util-scheduler-8620 DEBUG Adding task: 1266 / 0x5e2b838
Jul 07 20:45:43-043768 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-043946 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:45:43-044146 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:43-044325 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:43-044501 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:43-044745 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:43-044930 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:43-045107 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-045367 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:43-045550 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:43-045728 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-045964 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-046159 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-046339 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-046574 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-046769 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-046948 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-047183 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-047400 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-047580 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-047816 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-048014 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-048193 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-048392 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:43-048599 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:45:43-048785 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:45:43-049014 util-scheduler-8620 DEBUG Adding task: 1267 / 0x5e2b838
Jul 07 20:45:43-049256 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-049455 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-049659 util-scheduler-8620 DEBUG Adding task: 1268 / 0x46620a0
Jul 07 20:45:43-049861 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:45:43-052509 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-052720 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-052924 util-scheduler-8620 DEBUG Running task: 1265 / 0x4662248
Jul 07 20:45:43-053117 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-053341 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-053561 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-053773 util-scheduler-8620 DEBUG Adding task: 1269 / 0x4662248
Jul 07 20:45:43-054022 util-scheduler-8620 DEBUG Checking readiness of task: 1268 / 0x46620a0
Jul 07 20:45:43-054220 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-054413 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-054608 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-054800 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-054992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-055184 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-055375 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-055570 util-scheduler-8620 DEBUG Running task: 1268 / 0x46620a0
Jul 07 20:45:43-055757 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-055935 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-056107 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-056286 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-056499 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-056701 util-scheduler-8620 DEBUG Adding task: 1270 / 0x46620a0
Jul 07 20:45:43-056900 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-057224 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-057424 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-057623 util-scheduler-8620 DEBUG Running task: 1269 / 0x4662248
Jul 07 20:45:43-057813 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-058007 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-058220 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-058401 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-058577 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-058780 util-scheduler-8620 DEBUG Adding task: 1271 / 0x46620a0
Jul 07 20:45:43-058998 util-scheduler-8620 DEBUG Running task: 1266 / 0x5e2b838
Jul 07 20:45:43-059193 util-scheduler-8620 DEBUG Canceling task: 1267 / 0x5e2b838
Jul 07 20:45:43-059648 util-scheduler-8620 DEBUG Adding task: 1272 / 0x5e2b838
Jul 07 20:45:43-059956 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-060140 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-060377 util-scheduler-8620 DEBUG Checking readiness of task: 1271 / 0x46620a0
Jul 07 20:45:43-060585 util-scheduler-8620 DEBUG Checking readiness of task: 1270 / 0x46620a0
Jul 07 20:45:43-060779 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-060973 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-061167 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-061401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-061595 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-061787 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-061978 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-062171 util-scheduler-8620 DEBUG Running task: 1270 / 0x46620a0
Jul 07 20:45:43-062357 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-062534 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-062706 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-062884 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-063096 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-063295 util-scheduler-8620 DEBUG Adding task: 1273 / 0x46620a0
Jul 07 20:45:43-063494 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-063796 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-063994 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-064193 util-scheduler-8620 DEBUG Running task: 1271 / 0x46620a0
Jul 07 20:45:43-064601 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-064828 util-scheduler-8620 DEBUG Adding task: 1274 / 0x4662248
Jul 07 20:45:43-065079 util-scheduler-8620 DEBUG Checking readiness of task: 1273 / 0x46620a0
Jul 07 20:45:43-065300 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-065494 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-065686 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-065878 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-066070 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-066260 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-066452 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-066645 util-scheduler-8620 DEBUG Running task: 1273 / 0x46620a0
Jul 07 20:45:43-066831 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-067007 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-067179 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-067361 util-scheduler-8620 DEBUG Canceling task: 1263 / 0x4d6ff98
Jul 07 20:45:43-067582 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:45:43-067797 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:43-068029 cadet-p2p-8620 DEBUG Checking 0x6b78618 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-068262 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:43-068441 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:43-068628 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-068909 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 196)
Jul 07 20:45:43-069120 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-069338 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-069526 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:43-069716 cadet-con-8620 DEBUG  C_P- 0x4d707d0 5
Jul 07 20:45:43-069895 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:43-070081 util-scheduler-8620 DEBUG Canceling task: 1256 / 0x4d707d0
Jul 07 20:45:43-070292 util-scheduler-8620 DEBUG Adding task: 1275 / 0x4d707d0
Jul 07 20:45:43-070539 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-070710 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-070933 cadet-p2p-8620 DEBUG Checking 0x6b7f0b8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-071173 cadet-p2p-8620 DEBUG Checking 0x6b7f0b8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-071354 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-071557 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 20:45:43-071769 util-scheduler-8620 DEBUG Adding task: 1276 / 0x4d6ff98
Jul 07 20:45:43-071950 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-072128 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:43-072329 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:43-072506 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:43-072683 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:43-072921 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-073117 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-073321 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-073558 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-073753 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-073931 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-074165 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-074360 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:43-074538 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:43-074775 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-074972 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-075149 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-075348 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:43-075552 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:45:43-075738 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:43-075940 util-scheduler-8620 DEBUG Adding task: 1277 / 0x4d6ff98
Jul 07 20:45:43-076158 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-076353 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-076554 util-scheduler-8620 DEBUG Adding task: 1278 / 0x46620a0
Jul 07 20:45:43-076755 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:43-077944 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-078152 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-078352 util-scheduler-8620 DEBUG Running task: 1274 / 0x4662248
Jul 07 20:45:43-078545 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-078741 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-079030 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:43-079241 util-scheduler-8620 DEBUG Adding task: 1279 / 0x4662248
Jul 07 20:45:43-079484 util-scheduler-8620 DEBUG Checking readiness of task: 1278 / 0x46620a0
Jul 07 20:45:43-079680 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-079873 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-080081 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-080274 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-080466 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-080656 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-080848 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-081039 util-scheduler-8620 DEBUG Running task: 1278 / 0x46620a0
Jul 07 20:45:43-081247 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-081427 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-081598 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-081779 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-081989 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-082192 util-scheduler-8620 DEBUG Adding task: 1280 / 0x46620a0
Jul 07 20:45:43-082390 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-082698 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-082895 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-083093 util-scheduler-8620 DEBUG Running task: 1279 / 0x4662248
Jul 07 20:45:43-083283 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-083475 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-083687 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:43-083867 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-084044 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-084243 util-scheduler-8620 DEBUG Adding task: 1281 / 0x46620a0
Jul 07 20:45:43-084443 util-scheduler-8620 DEBUG Running task: 1276 / 0x4d6ff98
Jul 07 20:45:43-084640 util-scheduler-8620 DEBUG Canceling task: 1277 / 0x4d6ff98
Jul 07 20:45:43-084854 util-scheduler-8620 DEBUG Adding task: 1282 / 0x4d6ff98
Jul 07 20:45:43-085071 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-085288 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-085522 util-scheduler-8620 DEBUG Checking readiness of task: 1281 / 0x46620a0
Jul 07 20:45:43-085717 util-scheduler-8620 DEBUG Checking readiness of task: 1280 / 0x46620a0
Jul 07 20:45:43-085909 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-086102 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-086293 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-086484 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-086675 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-086867 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-087058 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-087252 util-scheduler-8620 DEBUG Running task: 1280 / 0x46620a0
Jul 07 20:45:43-087440 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-087616 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-087789 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-087967 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-088177 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-088375 util-scheduler-8620 DEBUG Adding task: 1283 / 0x46620a0
Jul 07 20:45:43-088573 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-088870 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-089067 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-089303 util-scheduler-8620 DEBUG Running task: 1281 / 0x46620a0
Jul 07 20:45:43-089706 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-089931 util-scheduler-8620 DEBUG Adding task: 1284 / 0x4662248
Jul 07 20:45:43-090180 util-scheduler-8620 DEBUG Checking readiness of task: 1283 / 0x46620a0
Jul 07 20:45:43-090378 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-090571 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-090764 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-090955 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-091146 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-091336 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-091526 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-091719 util-scheduler-8620 DEBUG Running task: 1283 / 0x46620a0
Jul 07 20:45:43-091904 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-092081 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-092252 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-092435 util-scheduler-8620 DEBUG Canceling task: 1272 / 0x5e2b838
Jul 07 20:45:43-092655 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 196 bytes.
Jul 07 20:45:43-092869 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:43-093100 cadet-p2p-8620 DEBUG Checking 0x6692f88 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-093356 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:45:43-093536 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:43-093722 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-093987 cadet-p2p-8620 INFO snd {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 196)
Jul 07 20:45:43-094181 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-094358 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-094545 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:45:43-094736 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 2
Jul 07 20:45:43-094913 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:43-095098 util-scheduler-8620 DEBUG Canceling task: 1093 / 0x5e2cf38
Jul 07 20:45:43-095309 util-scheduler-8620 DEBUG Adding task: 1285 / 0x5e2cf38
Jul 07 20:45:43-095552 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-095722 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-095944 cadet-p2p-8620 DEBUG Checking 0x66965d8 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-096184 cadet-p2p-8620 DEBUG Checking 0x66965d8 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-096365 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-096567 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `D3TJ'
Jul 07 20:45:43-096778 util-scheduler-8620 DEBUG Adding task: 1286 / 0x5e2b838
Jul 07 20:45:43-096958 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-097135 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:43-097358 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:43-097535 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:43-097711 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:43-098020 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:45:43-098205 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:43-098381 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-098616 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-098810 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-098988 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-099223 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-099417 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-099610 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-099845 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-100040 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-100216 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-100448 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-100642 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-100818 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-101014 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:43-101239 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 196 bytes.
Jul 07 20:45:43-101425 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:43-101624 util-scheduler-8620 DEBUG Adding task: 1287 / 0x5e2b838
Jul 07 20:45:43-101840 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-102033 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-102232 util-scheduler-8620 DEBUG Adding task: 1288 / 0x46620a0
Jul 07 20:45:43-102430 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:43-103866 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-104071 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-104269 util-scheduler-8620 DEBUG Running task: 1284 / 0x4662248
Jul 07 20:45:43-104466 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-104821 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-105293 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-105508 util-scheduler-8620 DEBUG Adding task: 1289 / 0x4662248
Jul 07 20:45:43-105753 util-scheduler-8620 DEBUG Checking readiness of task: 1288 / 0x46620a0
Jul 07 20:45:43-105947 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-106138 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-106327 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-106516 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-106706 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-106894 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-107083 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-107273 util-scheduler-8620 DEBUG Running task: 1288 / 0x46620a0
Jul 07 20:45:43-107459 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-107634 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-107805 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-107980 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-108188 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-108386 util-scheduler-8620 DEBUG Adding task: 1290 / 0x46620a0
Jul 07 20:45:43-108582 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-108879 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-109075 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-109294 util-scheduler-8620 DEBUG Running task: 1289 / 0x4662248
Jul 07 20:45:43-109484 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-109675 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-109884 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-110062 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-110235 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-110455 util-scheduler-8620 DEBUG Adding task: 1291 / 0x46620a0
Jul 07 20:45:43-110654 util-scheduler-8620 DEBUG Running task: 1286 / 0x5e2b838
Jul 07 20:45:43-110844 util-scheduler-8620 DEBUG Canceling task: 1287 / 0x5e2b838
Jul 07 20:45:43-111055 util-scheduler-8620 DEBUG Adding task: 1292 / 0x5e2b838
Jul 07 20:45:43-111269 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-111446 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-111676 util-scheduler-8620 DEBUG Checking readiness of task: 1291 / 0x46620a0
Jul 07 20:45:43-111870 util-scheduler-8620 DEBUG Checking readiness of task: 1290 / 0x46620a0
Jul 07 20:45:43-112060 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-112254 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-112443 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-112632 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-112821 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-113009 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-113221 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-113413 util-scheduler-8620 DEBUG Running task: 1290 / 0x46620a0
Jul 07 20:45:43-113598 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-113773 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-113942 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-114118 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-114326 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-114521 util-scheduler-8620 DEBUG Adding task: 1293 / 0x46620a0
Jul 07 20:45:43-114719 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-115014 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-115210 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-115405 util-scheduler-8620 DEBUG Running task: 1291 / 0x46620a0
Jul 07 20:45:43-115809 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-116033 util-scheduler-8620 DEBUG Adding task: 1294 / 0x4662248
Jul 07 20:45:43-116283 util-scheduler-8620 DEBUG Checking readiness of task: 1293 / 0x46620a0
Jul 07 20:45:43-116477 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-116667 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-116858 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-117048 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-117261 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-117452 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-117643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-117833 util-scheduler-8620 DEBUG Running task: 1293 / 0x46620a0
Jul 07 20:45:43-118017 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-118192 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-118361 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-118542 util-scheduler-8620 DEBUG Canceling task: 1282 / 0x4d6ff98
Jul 07 20:45:43-118760 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 20:45:43-118974 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:43-119205 cadet-p2p-8620 DEBUG Checking 0x6b7f0b8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-119435 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:43-119612 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:43-119796 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-120086 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 80)
Jul 07 20:45:43-120279 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-120455 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-120639 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:43-120868 cadet-con-8620 DEBUG  C_P- 0x4d707d0 4
Jul 07 20:45:43-121053 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:43-121259 util-scheduler-8620 DEBUG Canceling task: 1275 / 0x4d707d0
Jul 07 20:45:43-121470 util-scheduler-8620 DEBUG Adding task: 1295 / 0x4d707d0
Jul 07 20:45:43-121711 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-121880 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-122099 cadet-p2p-8620 DEBUG Checking 0x6dd0e60 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-122337 cadet-p2p-8620 DEBUG Checking 0x6dd0e60 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-122515 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-122716 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:43-122926 util-scheduler-8620 DEBUG Adding task: 1296 / 0x4d6ff98
Jul 07 20:45:43-123103 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-123278 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:43-123475 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:43-123649 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:43-123822 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:43-124057 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-124250 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-124427 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-124662 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-124856 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:43-125032 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:43-125289 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-125483 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-125658 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-125856 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:43-126058 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 20:45:43-126241 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:43-126450 util-scheduler-8620 DEBUG Adding task: 1297 / 0x4d6ff98
Jul 07 20:45:43-126665 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-126856 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-127054 util-scheduler-8620 DEBUG Adding task: 1298 / 0x46620a0
Jul 07 20:45:43-127251 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:43-128377 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-128582 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-128779 util-scheduler-8620 DEBUG Running task: 1294 / 0x4662248
Jul 07 20:45:43-128969 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-129162 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-129462 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:43-129669 util-scheduler-8620 DEBUG Adding task: 1299 / 0x4662248
Jul 07 20:45:43-129912 util-scheduler-8620 DEBUG Checking readiness of task: 1298 / 0x46620a0
Jul 07 20:45:43-130105 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-130295 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-130486 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-130676 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-130882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-131072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-131262 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-131454 util-scheduler-8620 DEBUG Running task: 1298 / 0x46620a0
Jul 07 20:45:43-131638 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-131814 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-131986 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-132163 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-132372 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-132570 util-scheduler-8620 DEBUG Adding task: 1300 / 0x46620a0
Jul 07 20:45:43-132767 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-133070 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-133295 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-133491 util-scheduler-8620 DEBUG Running task: 1299 / 0x4662248
Jul 07 20:45:43-133680 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-133872 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-134082 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:43-134262 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-134435 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-134637 util-scheduler-8620 DEBUG Adding task: 1301 / 0x46620a0
Jul 07 20:45:43-134836 util-scheduler-8620 DEBUG Running task: 1296 / 0x4d6ff98
Jul 07 20:45:43-135027 util-scheduler-8620 DEBUG Canceling task: 1297 / 0x4d6ff98
Jul 07 20:45:43-135239 util-scheduler-8620 DEBUG Adding task: 1302 / 0x4d6ff98
Jul 07 20:45:43-135454 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-135630 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-135862 util-scheduler-8620 DEBUG Checking readiness of task: 1301 / 0x46620a0
Jul 07 20:45:43-136056 util-scheduler-8620 DEBUG Checking readiness of task: 1300 / 0x46620a0
Jul 07 20:45:43-136247 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-136438 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-136628 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-136819 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-137009 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-137221 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-137412 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-137603 util-scheduler-8620 DEBUG Running task: 1300 / 0x46620a0
Jul 07 20:45:43-137785 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-137960 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-138129 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-138307 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-138983 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-139190 util-scheduler-8620 DEBUG Adding task: 1303 / 0x46620a0
Jul 07 20:45:43-139388 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-140075 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-140278 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-140479 util-scheduler-8620 DEBUG Running task: 1301 / 0x46620a0
Jul 07 20:45:43-140882 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-141126 util-scheduler-8620 DEBUG Adding task: 1304 / 0x4662248
Jul 07 20:45:43-141417 util-scheduler-8620 DEBUG Checking readiness of task: 1303 / 0x46620a0
Jul 07 20:45:43-141611 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-141802 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-141992 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-142181 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-142373 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-142564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-142753 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-142943 util-scheduler-8620 DEBUG Running task: 1303 / 0x46620a0
Jul 07 20:45:43-143128 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-143302 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-143473 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-143654 util-scheduler-8620 DEBUG Canceling task: 1292 / 0x5e2b838
Jul 07 20:45:43-143876 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 80 bytes.
Jul 07 20:45:43-144090 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:43-144321 cadet-p2p-8620 DEBUG Checking 0x66965d8 towards BFARXZN9 (->D3TJ)
Jul 07 20:45:43-144551 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:45:43-144731 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:43-144915 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-145177 cadet-p2p-8620 INFO snd {                KX} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 80)
Jul 07 20:45:43-145396 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-145573 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-145759 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:45:43-145945 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 1
Jul 07 20:45:43-146121 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:43-146303 util-scheduler-8620 DEBUG Canceling task: 1285 / 0x5e2cf38
Jul 07 20:45:43-146511 util-scheduler-8620 DEBUG Adding task: 1305 / 0x5e2cf38
Jul 07 20:45:43-146752 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-146921 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-147140 cadet-p2p-8620 DEBUG Checking 0x690f140 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-147377 cadet-p2p-8620 DEBUG Checking 0x690f140 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-147556 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-147758 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `D3TJ'
Jul 07 20:45:43-147967 util-scheduler-8620 DEBUG Adding task: 1306 / 0x5e2b838
Jul 07 20:45:43-148145 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-148320 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:43-148518 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:43-148692 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:43-148865 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:43-149100 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-149332 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-149733 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-150110 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-150444 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-150624 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-150861 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-151055 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:43-151232 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:43-151465 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:43-151677 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:43-151855 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:43-152053 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:43-152259 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 80 bytes.
Jul 07 20:45:43-152443 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:43-152647 util-scheduler-8620 DEBUG Adding task: 1307 / 0x5e2b838
Jul 07 20:45:43-152862 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-153058 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-153286 util-scheduler-8620 DEBUG Adding task: 1308 / 0x46620a0
Jul 07 20:45:43-153486 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:43-153723 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-153918 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-154115 util-scheduler-8620 DEBUG Running task: 1304 / 0x4662248
Jul 07 20:45:43-154304 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-154498 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-154712 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-154921 util-scheduler-8620 DEBUG Adding task: 1309 / 0x4662248
Jul 07 20:45:43-155168 util-scheduler-8620 DEBUG Checking readiness of task: 1308 / 0x46620a0
Jul 07 20:45:43-155364 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-155555 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-155745 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-155935 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-156124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-156314 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-156503 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-156694 util-scheduler-8620 DEBUG Running task: 1308 / 0x46620a0
Jul 07 20:45:43-156878 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-157055 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-157249 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-157430 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-157638 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-157836 util-scheduler-8620 DEBUG Adding task: 1310 / 0x46620a0
Jul 07 20:45:43-158032 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-158408 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-158606 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-158803 util-scheduler-8620 DEBUG Running task: 1309 / 0x4662248
Jul 07 20:45:43-158992 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:43-159183 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:43-159395 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:43-159574 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-159749 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-159948 util-scheduler-8620 DEBUG Adding task: 1311 / 0x46620a0
Jul 07 20:45:43-160149 util-scheduler-8620 DEBUG Running task: 1306 / 0x5e2b838
Jul 07 20:45:43-160341 util-scheduler-8620 DEBUG Canceling task: 1307 / 0x5e2b838
Jul 07 20:45:43-160553 util-scheduler-8620 DEBUG Adding task: 1312 / 0x5e2b838
Jul 07 20:45:43-160767 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:43-160959 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-161215 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-161410 util-scheduler-8620 DEBUG Checking readiness of task: 1310 / 0x46620a0
Jul 07 20:45:43-161601 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-161790 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-161979 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-162168 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-162357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-162546 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-162735 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-162929 util-scheduler-8620 DEBUG Running task: 1310 / 0x46620a0
Jul 07 20:45:43-163141 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-163335 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-163505 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-163682 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-163889 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-164085 util-scheduler-8620 DEBUG Adding task: 1313 / 0x46620a0
Jul 07 20:45:43-164298 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-164592 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-164789 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-165028 util-scheduler-8620 DEBUG Checking readiness of task: 1313 / 0x46620a0
Jul 07 20:45:43-165271 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-165481 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-165673 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-165861 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-166051 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-166239 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-166448 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-166637 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-166827 util-scheduler-8620 DEBUG Running task: 1313 / 0x46620a0
Jul 07 20:45:43-167010 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-167185 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-167353 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-167553 util-scheduler-8620 DEBUG Canceling task: 1302 / 0x4d6ff98
Jul 07 20:45:43-167773 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:43-167987 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:43-168216 cadet-p2p-8620 DEBUG Checking 0x6dd0e60 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-168446 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:43-168641 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:43-168826 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:43-169102 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:43-169318 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-169495 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-169698 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:43-169886 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:43-170063 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:43-170246 util-scheduler-8620 DEBUG Canceling task: 1295 / 0x4d707d0
Jul 07 20:45:43-170470 util-scheduler-8620 DEBUG Adding task: 1314 / 0x4d707d0
Jul 07 20:45:43-170731 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-170902 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-171132 cadet-p2p-8620 DEBUG Checking 0x7024878 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-171365 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:43-171548 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:43-171724 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:43-171970 cadet-p2p-8620 DEBUG Checking 0x7024878 towards CMHCKRVP (->V8XX)
Jul 07 20:45:43-172203 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:43-172385 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:43-172559 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:43-172725 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:43-172944 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `V8XX'
Jul 07 20:45:43-173156 util-scheduler-8620 DEBUG Adding task: 1315 / 0x4d6ff98
Jul 07 20:45:43-173361 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-173536 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:43-173736 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:43-173932 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:43-174107 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:43-174345 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-174540 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:43-174720 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:43-174974 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:43-175169 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:43-175346 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:43-175544 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:43-175747 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:43-175932 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:43-176153 util-scheduler-8620 DEBUG Adding task: 1316 / 0x4d6ff98
Jul 07 20:45:43-176370 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-176564 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-176764 util-scheduler-8620 DEBUG Adding task: 1317 / 0x46620a0
Jul 07 20:45:43-176963 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:43-179770 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-179982 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-180232 util-scheduler-8620 DEBUG Checking readiness of task: 1317 / 0x46620a0
Jul 07 20:45:43-180445 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-180697 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-180891 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-181081 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-181295 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-181507 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-181697 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-181887 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-182079 util-scheduler-8620 DEBUG Running task: 1317 / 0x46620a0
Jul 07 20:45:43-182264 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-182440 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-182637 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-182816 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-183063 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-183263 util-scheduler-8620 DEBUG Adding task: 1318 / 0x46620a0
Jul 07 20:45:43-183460 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-183763 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-183958 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-184154 util-scheduler-8620 DEBUG Running task: 1315 / 0x4d6ff98
Jul 07 20:45:43-184346 util-scheduler-8620 DEBUG Canceling task: 1316 / 0x4d6ff98
Jul 07 20:45:43-184559 util-scheduler-8620 DEBUG Adding task: 1319 / 0x4d6ff98
Jul 07 20:45:43-184799 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:43-184976 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:43-185233 util-scheduler-8620 DEBUG Checking readiness of task: 1318 / 0x46620a0
Jul 07 20:45:43-185427 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-185618 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-185826 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-186016 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-186204 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-186394 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-186583 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-186771 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-186978 util-scheduler-8620 DEBUG Running task: 1318 / 0x46620a0
Jul 07 20:45:43-187163 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-187338 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-187506 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-187683 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-187890 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-188103 util-scheduler-8620 DEBUG Adding task: 1320 / 0x46620a0
Jul 07 20:45:43-188301 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-188581 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-188776 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:43-189032 util-scheduler-8620 DEBUG Checking readiness of task: 1320 / 0x46620a0
Jul 07 20:45:43-189248 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-189441 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-189631 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-189821 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-190026 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-190216 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-190405 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-190593 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-190783 util-scheduler-8620 DEBUG Running task: 1320 / 0x46620a0
Jul 07 20:45:43-190966 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-191160 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-191329 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-191512 util-scheduler-8620 DEBUG Canceling task: 1224 / 0x4d5c9e8
Jul 07 20:45:43-191864 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 96 bytes.
Jul 07 20:45:43-192082 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:43-192334 cadet-p2p-8620 DEBUG Checking 0x6924bb0 towards HS92G30M (->KNAS)
Jul 07 20:45:43-192581 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:43-192765 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 20
Jul 07 20:45:43-192938 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:43-193159 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:43-193377 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:45:43-193552 cadet-p2p-8620 DEBUG   payload ID 21
Jul 07 20:45:43-193834 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 96)
Jul 07 20:45:43-194028 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:43-194207 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:43-194410 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:43-194586 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:43-194759 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:43-194948 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:43-195128 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:45:43-195383 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 925 ms
Jul 07 20:45:43-195558 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:43-195763 cadet-chn-8620 DEBUG !! using delay 3701864 µs
Jul 07 20:45:43-195964 util-scheduler-8620 DEBUG Adding task: 1321 / 0x4d63a48
Jul 07 20:45:43-196166 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:43-196416 cadet-con-8620 DEBUG GMC send FWD ACK on HS92G30M (->KNAS)
Jul 07 20:45:43-196595 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:43-196769 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:43-196943 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:43-197141 cadet-tun-8620 DEBUG GCT_unchoke_channels on KNAS
Jul 07 20:45:43-197343 cadet-tun-8620 DEBUG  head: 0x4d639c8
Jul 07 20:45:43-197538 cadet-tun-8620 DEBUG  head ch: 0x4d638d8
Jul 07 20:45:43-197742 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS KNAS
Jul 07 20:45:43-197922 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:43-198105 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:45:43-198283 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:43-198460 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:43-198646 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:43-198866 cadet-tun-8620 DEBUG TTT  - KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:43-199039 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:43-199273 cadet-tun-8620 DEBUG TTT  - HS92G30M (->KNAS) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:43-199458 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:43-199639 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:43-199842 util-scheduler-8620 DEBUG Canceling task: 1220 / 0x4d61c30
Jul 07 20:45:43-200053 util-scheduler-8620 DEBUG Adding task: 1322 / 0x4d61c30
Jul 07 20:45:43-200294 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:43-200473 cadet-con-8620 DEBUG !  Q_N- 0x4d61c34 0
Jul 07 20:45:43-200651 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 21
Jul 07 20:45:43-200843 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:43-201023 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:45:43-201245 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:43-201423 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:43-201595 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:43-201810 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:43-202015 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 96 bytes.
Jul 07 20:45:43-202201 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:45:43-202379 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:43-202567 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:45:43-203313 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-230459 util-scheduler-8620 DEBUG Checking readiness of task: 1311 / 0x46620a0
Jul 07 20:45:43-230734 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-230929 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-231120 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-231310 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-231500 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-231690 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-231879 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-232071 util-scheduler-8620 DEBUG Running task: 1311 / 0x46620a0
Jul 07 20:45:43-232478 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-232722 util-scheduler-8620 DEBUG Adding task: 1323 / 0x4662248
Jul 07 20:45:43-232980 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-233174 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-233408 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-233598 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-233820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-234011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-234215 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-234405 util-scheduler-8620 DEBUG Running task: 1323 / 0x4662248
Jul 07 20:45:43-234596 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:43-234813 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:43-235038 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:43-235298 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:43-235553 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:43-235761 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:43-235962 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:43-236136 cadet-con-8620 DEBUG   ACK 82 (was 81)
Jul 07 20:45:43-236364 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:43-236594 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:43-236799 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:43-236998 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:43-237227 util-scheduler-8620 DEBUG Adding task: 1324 / 0x4662248
Jul 07 20:45:43-237469 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-237799 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-237993 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-238201 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-238390 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-238580 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-238773 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-238992 util-scheduler-8620 DEBUG Running task: 1324 / 0x4662248
Jul 07 20:45:43-239185 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:45:43-239376 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:45:43-239593 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:45:43-239836 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:43-240087 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:43-240315 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:43-240537 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:43-240795 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:43-241001 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:43-241211 cadet-con-8620 DEBUG  PID 18 (expected 18+)
Jul 07 20:45:43-241393 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:43-241578 util-scheduler-8620 DEBUG Canceling task: 1140 / 0x4d61c30
Jul 07 20:45:43-241799 util-scheduler-8620 DEBUG Adding task: 1325 / 0x4d61c30
Jul 07 20:45:43-241979 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:43-242231 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:43-242446 util-scheduler-8620 DEBUG Adding task: 1326 / 0x4d5e5d8
Jul 07 20:45:43-242632 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:43-242798 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:43-246336 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:43-247738 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:43-247946 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:43-251049 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on KNAS
Jul 07 20:45:43-253982 cadet-chn-8620 DEBUG Channel KNAS:40000000 (0x4d638d8)
Jul 07 20:45:43-255054 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x4d63a48
Jul 07 20:45:43-256520 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:45:43-257609 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:45:43-258692 cadet-chn-8620 DEBUG   id 80000001
Jul 07 20:45:43-259932 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:45:43-263705 util-server-nc-8620 DEBUG Adding message of type 274 and size 48 to pending queue (which has 1 entries)
Jul 07 20:45:43-263932 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:45:43-264152 util-scheduler-8620 DEBUG Adding task: 1327 / 0x4d5c418
Jul 07 20:45:43-266178 cadet-chn-8620 DEBUG destroying channel KNAS:1073741824
Jul 07 20:45:43-266799 cadet-chn-8620 DEBUG Channel KNAS:40000000 (0x4d638d8)
Jul 07 20:45:43-267146 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x4d63a48
Jul 07 20:45:43-267501 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:45:43-267831 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:45:43-268160 cadet-chn-8620 DEBUG   id 80000001
Jul 07 20:45:43-268493 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:45:43-272965 cadet-chn-8620 DEBUG  COPYFREE BATCH 0x5b978b8
Jul 07 20:45:43-273978 util-scheduler-8620 DEBUG Canceling task: 1321 / 0x4d63a48
Jul 07 20:45:43-275833 cadet-tun-8620 DEBUG Removing channel 0x4d638d8 from tunnel 0x4d61838
Jul 07 20:45:43-277341 cadet-tun-8620 DEBUG  found! KNAS:19 gid:40000000 (80000001 / 0)
Jul 07 20:45:43-280138 cadet-tun-8620 DEBUG Tunnel KNAS destroy if empty
Jul 07 20:45:43-281799 cadet-tun-8620 DEBUG Tunnel KNAS empty: destroying scheduled
Jul 07 20:45:43-282415 util-scheduler-8620 DEBUG Adding task: 1328 / 0x4d61838
Jul 07 20:45:43-283927 cadet-tun-8620 DEBUG Scheduled destroy of 0x4d61838 as 530
Jul 07 20:45:43-284572 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:43-284759 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:43-285095 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:43-285297 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:43-285522 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:43-285702 cadet-con-8620 DEBUG  ACK 82
Jul 07 20:45:43-285882 cadet-con-8620 DEBUG  last pid 18, last ack 81, qmax 11, q 0
Jul 07 20:45:43-286152 cadet-con-8620 INFO --> {               ACK} ( 82) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:43-286343 cadet-con-8620 DEBUG  ack 82
Jul 07 20:45:43-286522 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:43-286756 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:43-286965 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:43-287264 cadet-p2p-8620 INFO que {               ACK} ( 82) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:43-287464 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:43-287689 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:43-287871 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 21
Jul 07 20:45:43-288072 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:43-288280 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:45:43-288496 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:45:43-288713 util-scheduler-8620 DEBUG Adding task: 1329 / 0x4d5c9e8
Jul 07 20:45:43-288896 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:43-289100 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:43-289304 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:43-289480 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:43-289718 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:43-289903 cadet-p2p-8620 DEBUG QQQ    payload , 82
Jul 07 20:45:43-290078 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:43-290276 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:43-290460 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-290667 util-scheduler-8620 DEBUG Adding task: 1330 / 0x46620a0
Jul 07 20:45:43-290938 util-scheduler-8620 DEBUG Checking readiness of task: 1330 / 0x46620a0
Jul 07 20:45:43-291136 util-scheduler-8620 DEBUG Checking readiness of task: 1327 / 0x4d5c418
Jul 07 20:45:43-291328 util-scheduler-8620 DEBUG Checking readiness of task: 1326 / 0x4d5e5d8
Jul 07 20:45:43-291519 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-291709 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-291898 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-292087 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-292276 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-292466 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-292655 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-292850 util-scheduler-8620 DEBUG Running task: 1326 / 0x4d5e5d8
Jul 07 20:45:43-293036 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:43-293238 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-293412 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-293659 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:43-293867 util-scheduler-8620 DEBUG Adding task: 1331 / 0x4d5e5d8
Jul 07 20:45:43-294070 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:43-294402 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:43-294602 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:43-294803 util-scheduler-8620 DEBUG Running task: 1327 / 0x4d5c418
Jul 07 20:45:43-294987 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:45:43-295162 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-295355 util-server-nc-8620 DEBUG Copying message of type 274 and size 48 from pending queue to transmission buffer
Jul 07 20:45:43-295733 util-8620 DEBUG Connection transmitted 48/48 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:45:43-296010 util-scheduler-8620 DEBUG Running task: 1330 / 0x46620a0
Jul 07 20:45:43-296417 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:43-296649 util-scheduler-8620 DEBUG Adding task: 1332 / 0x4662248
Jul 07 20:45:43-296857 util-scheduler-8620 DEBUG Running task: 1329 / 0x4d5c9e8
Jul 07 20:45:43-297065 util-scheduler-8620 DEBUG Adding task: 1333 / 0x4d5c9e8
Jul 07 20:45:43-297314 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:43-297512 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:43-297710 util-scheduler-8620 DEBUG Adding task: 1334 / 0x46620a0
Jul 07 20:45:43-297955 util-scheduler-8620 DEBUG Checking readiness of task: 1334 / 0x46620a0
Jul 07 20:45:43-298148 util-scheduler-8620 DEBUG Checking readiness of task: 1331 / 0x4d5e5d8
Jul 07 20:45:43-298356 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-298547 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-298736 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-298926 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-299115 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-299304 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-299493 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-299684 util-scheduler-8620 DEBUG Running task: 1331 / 0x4d5e5d8
Jul 07 20:45:43-299879 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:43-300055 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-300224 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-300438 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:45:43-300724 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:43-300936 util-scheduler-8620 DEBUG Running task: 1334 / 0x46620a0
Jul 07 20:45:43-301120 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:43-301318 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-301487 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-301665 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:43-301859 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:43-302047 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:43-302343 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:43-302549 util-scheduler-8620 DEBUG Running task: 1332 / 0x4662248
Jul 07 20:45:43-302741 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:43-302937 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:43-303154 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 20:45:43-303406 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:43-303645 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:43-303875 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:43-304083 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:43-304328 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:43-304536 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:43-304726 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:43-304911 util-scheduler-8620 DEBUG Canceling task: 1250 / 0x4d707d0
Jul 07 20:45:43-305129 util-scheduler-8620 DEBUG Adding task: 1335 / 0x4d707d0
Jul 07 20:45:43-305335 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:43-305569 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:43-305776 util-scheduler-8620 DEBUG Adding task: 1336 / 0x4d5e5d8
Jul 07 20:45:43-305955 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:43-306155 cadet-tun-8620 INFO <=== EPHM for V8XX
Jul 07 20:45:43-914817 util-scheduler-8620 DEBUG Canceling task: 1248 / 0x4d64a70
Jul 07 20:45:43-915238 util-scheduler-8620 DEBUG Adding task: 1337 / 0x4d64a70
Jul 07 20:45:43-915436 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:43-915652 util-scheduler-8620 DEBUG Adding task: 1338 / 0x46620a0
Jul 07 20:45:43-915933 util-scheduler-8620 DEBUG Checking readiness of task: 1338 / 0x46620a0
Jul 07 20:45:43-916132 util-scheduler-8620 DEBUG Checking readiness of task: 1336 / 0x4d5e5d8
Jul 07 20:45:43-916326 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:43-916518 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:43-916736 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:43-916928 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:43-917116 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:43-917330 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:43-917519 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:43-917713 util-scheduler-8620 DEBUG Running task: 1336 / 0x4d5e5d8
Jul 07 20:45:43-917900 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:43-918080 util-8620 DEBUG process_notify is running
Jul 07 20:45:43-918252 util-8620 DEBUG client_notify is running
Jul 07 20:45:43-918488 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:43-918834 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:44-140934 util-scheduler-8620 DEBUG Checking readiness of task: 1338 / 0x46620a0
Jul 07 20:45:44-141323 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-141522 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-141715 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-141908 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-142100 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-142291 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-142481 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-142676 util-scheduler-8620 DEBUG Running task: 1201 / 0x5e2de48
Jul 07 20:45:44-142918 cadet-tun-8620 INFO Re-key Tunnel D3TJ
Jul 07 20:45:44-143167 cadet-tun-8620 DEBUG  kx started 15 s ago
Jul 07 20:45:44-143374 cadet-tun-8620 INFO ===> EPHM for D3TJ
Jul 07 20:45:44-143577 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:44-143781 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:44-144018 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:44-144202 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-144426 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:44-144605 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-144842 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-145139 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (196 bytes)
Jul 07 20:45:44-145446 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 4
Jul 07 20:45:44-145688 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:44-145899 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:44-146217 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 196)
Jul 07 20:45:44-146421 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:44-146647 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-146832 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:44-147009 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:44-147214 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:44-147420 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:44-147597 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:44-147774 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:44-148028 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-148235 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-148413 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-148651 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-148846 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:44-149024 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:44-149325 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-149521 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-149698 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-149932 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-150126 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:44-150303 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:44-150535 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-150728 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-150906 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-151104 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:44-151309 cadet-tun-8620 INFO ===> PING for D3TJ
Jul 07 20:45:44-151621 cadet-tun-8620 DEBUG   sending 1699275036
Jul 07 20:45:44-151822 cadet-tun-8620 DEBUG   towards D3TJ
Jul 07 20:45:44-151994 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:44-152178 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:44-155768 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:44-156604 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:44-156850 cadet-tun-8620 DEBUG   e sending 1381663504
Jul 07 20:45:44-157063 cadet-tun-8620 DEBUG   e towards SQSZ
Jul 07 20:45:44-157299 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:44-157502 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:44-157730 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:44-157911 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-158132 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:44-158311 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-158531 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-158808 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (80 bytes)
Jul 07 20:45:44-159006 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 5
Jul 07 20:45:44-159241 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:44-159449 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:44-159759 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 80)
Jul 07 20:45:44-159959 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:44-160185 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-160368 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:44-160544 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:44-160746 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:44-160948 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:44-161126 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:44-161326 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:44-161565 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-161761 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-161939 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-162172 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-162366 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:44-162543 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:44-162776 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-162970 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-163146 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-163381 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-163574 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:44-163750 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:44-163983 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-164178 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:44-164375 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:44-164610 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:44-164804 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:44-164983 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:44-165181 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:44-165458 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:44-165666 util-scheduler-8620 DEBUG Adding task: 1339 / 0x5e2de48
Jul 07 20:45:44-165935 util-scheduler-8620 DEBUG Checking readiness of task: 1338 / 0x46620a0
Jul 07 20:45:44-166134 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-166326 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-166516 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-166706 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-166896 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-167086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-167275 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-167467 util-scheduler-8620 DEBUG Running task: 1338 / 0x46620a0
Jul 07 20:45:44-167884 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-168124 util-scheduler-8620 DEBUG Adding task: 1340 / 0x4662248
Jul 07 20:45:44-168384 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-168578 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-168767 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-168959 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-169147 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-169364 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-169553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-169743 util-scheduler-8620 DEBUG Running task: 1340 / 0x4662248
Jul 07 20:45:44-169935 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:44-170134 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:44-170354 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 20:45:44-170606 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:44-170844 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:44-171075 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-171284 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:44-171529 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-171736 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:44-171923 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:44-172113 util-scheduler-8620 DEBUG Canceling task: 1335 / 0x4d707d0
Jul 07 20:45:44-172333 util-scheduler-8620 DEBUG Adding task: 1341 / 0x4d707d0
Jul 07 20:45:44-172513 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:44-172771 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:44-172987 util-scheduler-8620 DEBUG Adding task: 1342 / 0x4d5e5d8
Jul 07 20:45:44-173171 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:44-173398 cadet-tun-8620 INFO <=== PING for V8XX
Jul 07 20:45:44-173585 cadet-tun-8620 DEBUG   t_decrypt with VJ50N9K4
Jul 07 20:45:44-173757 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:44-173923 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:44-177131 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:44-178456 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:44-178686 cadet-tun-8620 INFO ===> PONG for V8XX
Jul 07 20:45:44-178955 cadet-tun-8620 DEBUG   sending 930566066
Jul 07 20:45:44-179149 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:44-179335 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:44-182438 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:44-183040 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:44-183292 cadet-tun-8620 DEBUG   e sending 2168049095
Jul 07 20:45:44-183500 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:45:44-183702 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:44-183930 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:44-184110 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-184329 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:44-184604 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (48 bytes)
Jul 07 20:45:44-184801 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:44-185040 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-185272 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:44-185583 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 48)
Jul 07 20:45:44-185782 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:44-186006 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:44-186189 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:44-186364 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:44-186566 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:44-186768 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:44-186945 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:44-187120 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:44-187361 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-187557 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:44-187736 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:44-187970 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-188164 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:44-188341 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:44-188574 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-188767 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:44-188943 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:44-189142 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:44-189385 util-scheduler-8620 DEBUG Adding task: 1343 / 0x4662248
Jul 07 20:45:44-189645 util-scheduler-8620 DEBUG Checking readiness of task: 1342 / 0x4d5e5d8
Jul 07 20:45:44-189842 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-190034 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-190224 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-190414 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-190604 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-190793 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-190982 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-191175 util-scheduler-8620 DEBUG Running task: 1342 / 0x4d5e5d8
Jul 07 20:45:44-191361 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:44-191540 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-191712 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-191940 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:44-192299 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:44-192512 util-scheduler-8620 DEBUG Running task: 1343 / 0x4662248
Jul 07 20:45:44-192704 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:44-192920 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:44-193137 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:44-193412 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:44-193648 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:44-193888 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-194095 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:44-194338 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-194546 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:44-194734 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:44-194924 util-scheduler-8620 DEBUG Canceling task: 1341 / 0x4d707d0
Jul 07 20:45:44-195148 util-scheduler-8620 DEBUG Adding task: 1344 / 0x4d707d0
Jul 07 20:45:44-195328 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:44-195575 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:44-195790 util-scheduler-8620 DEBUG Adding task: 1345 / 0x4d5e5d8
Jul 07 20:45:44-195972 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:44-196172 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:44-196388 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-196593 util-scheduler-8620 DEBUG Adding task: 1346 / 0x46620a0
Jul 07 20:45:44-196843 util-scheduler-8620 DEBUG Checking readiness of task: 1346 / 0x46620a0
Jul 07 20:45:44-197038 util-scheduler-8620 DEBUG Checking readiness of task: 1345 / 0x4d5e5d8
Jul 07 20:45:44-197255 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-197447 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-197638 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-197827 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-198018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-198208 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-198398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-198588 util-scheduler-8620 DEBUG Running task: 1345 / 0x4d5e5d8
Jul 07 20:45:44-198771 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:44-198947 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-199116 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-199343 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:44-199551 util-scheduler-8620 DEBUG Adding task: 1347 / 0x4d5e5d8
Jul 07 20:45:44-199750 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:44-200053 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:44-200253 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:44-200495 util-scheduler-8620 DEBUG Checking readiness of task: 1347 / 0x4d5e5d8
Jul 07 20:45:44-200689 util-scheduler-8620 DEBUG Checking readiness of task: 1346 / 0x46620a0
Jul 07 20:45:44-200880 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-201071 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-201284 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-201475 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-201665 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-201855 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-202044 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-202235 util-scheduler-8620 DEBUG Running task: 1347 / 0x4d5e5d8
Jul 07 20:45:44-202418 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:44-202593 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-202778 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-202989 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:44-203279 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:44-205339 util-scheduler-8620 DEBUG Checking readiness of task: 1346 / 0x46620a0
Jul 07 20:45:44-205559 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-205753 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-205944 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-206134 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-206325 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-206514 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-206705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-206897 util-scheduler-8620 DEBUG Running task: 1346 / 0x46620a0
Jul 07 20:45:44-207303 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-207538 util-scheduler-8620 DEBUG Adding task: 1348 / 0x4662248
Jul 07 20:45:44-207789 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-207983 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-208174 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-208365 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-208555 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-208746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-208936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-209126 util-scheduler-8620 DEBUG Running task: 1348 / 0x4662248
Jul 07 20:45:44-209342 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:44-209538 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:44-209758 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:44-209963 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-210165 util-scheduler-8620 DEBUG Adding task: 1349 / 0x46620a0
Jul 07 20:45:44-210351 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-210552 util-scheduler-8620 DEBUG Adding task: 1350 / 0x46620a0
Jul 07 20:45:44-210795 util-scheduler-8620 DEBUG Checking readiness of task: 1350 / 0x46620a0
Jul 07 20:45:44-210990 util-scheduler-8620 DEBUG Checking readiness of task: 1349 / 0x46620a0
Jul 07 20:45:44-211182 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-211374 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-211563 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-211752 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-211942 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-212131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-212321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-212512 util-scheduler-8620 DEBUG Running task: 1349 / 0x46620a0
Jul 07 20:45:44-212697 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-212873 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-213043 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-213250 util-scheduler-8620 DEBUG Canceling task: 1319 / 0x4d6ff98
Jul 07 20:45:44-213476 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 96 bytes.
Jul 07 20:45:44-213696 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:44-213954 cadet-p2p-8620 DEBUG Checking 0x7024878 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-214189 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:44-214373 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:44-214549 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:44-214772 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:44-214955 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:45:44-215131 cadet-p2p-8620 DEBUG   payload ID 0
Jul 07 20:45:44-215419 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 96)
Jul 07 20:45:44-215615 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:44-215795 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:44-215983 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:44-216159 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:44-216326 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:44-216515 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:45:44-216703 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:45:44-217100 cadet-chn-8620 DEBUG !!! STD BACKOFF 250 ms
Jul 07 20:45:44-217351 util-scheduler-8620 DEBUG Adding task: 1351 / 0x4d65218
Jul 07 20:45:44-217557 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:44-217790 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:44-217966 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:44-218139 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:44-218312 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:44-218511 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:45:44-218687 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:45:44-218862 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:45:44-219065 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:44-219246 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:44-219428 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:44-219610 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:44-219787 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:44-219957 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:44-220175 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:44-220350 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:44-220584 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:44-220769 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:44-220967 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:44-221328 cadet-chn-8620 DEBUG  channel not ready yet!
Jul 07 20:45:44-221510 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:44-221699 util-scheduler-8620 DEBUG Canceling task: 1314 / 0x4d707d0
Jul 07 20:45:44-221916 util-scheduler-8620 DEBUG Adding task: 1352 / 0x4d707d0
Jul 07 20:45:44-222163 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:44-222342 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:45:44-222522 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:45:44-222694 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:44-222918 cadet-p2p-8620 DEBUG Checking 0x751bda8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-223159 cadet-p2p-8620 DEBUG Checking 0x751bda8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-223338 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:44-223592 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:44-223808 util-scheduler-8620 DEBUG Adding task: 1353 / 0x4d6ff98
Jul 07 20:45:44-223988 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:44-224165 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:45:44-224367 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:44-224544 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:44-224719 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:44-224963 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-225177 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:44-225383 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:44-225618 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-225813 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:44-225992 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:44-226190 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:44-226397 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 96 bytes.
Jul 07 20:45:44-226582 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:45:44-226788 util-scheduler-8620 DEBUG Adding task: 1354 / 0x4d6ff98
Jul 07 20:45:44-227009 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:44-227207 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-227411 util-scheduler-8620 DEBUG Adding task: 1355 / 0x46620a0
Jul 07 20:45:44-227612 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:45:44-228888 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-229097 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:44-229400 util-scheduler-8620 DEBUG Checking readiness of task: 1355 / 0x46620a0
Jul 07 20:45:44-229599 util-scheduler-8620 DEBUG Checking readiness of task: 1350 / 0x46620a0
Jul 07 20:45:44-229871 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-230067 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-230259 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-230449 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-230639 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-230829 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-231018 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-231211 util-scheduler-8620 DEBUG Running task: 1355 / 0x46620a0
Jul 07 20:45:44-231395 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-231572 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-231744 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-231922 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:44-232119 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:44-232309 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:44-232612 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-232821 util-scheduler-8620 DEBUG Running task: 1353 / 0x4d6ff98
Jul 07 20:45:44-233016 util-scheduler-8620 DEBUG Canceling task: 1354 / 0x4d6ff98
Jul 07 20:45:44-233255 util-scheduler-8620 DEBUG Adding task: 1356 / 0x4d6ff98
Jul 07 20:45:44-233490 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:44-233705 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-233906 util-scheduler-8620 DEBUG Adding task: 1357 / 0x46620a0
Jul 07 20:45:44-234148 util-scheduler-8620 DEBUG Checking readiness of task: 1357 / 0x46620a0
Jul 07 20:45:44-234341 util-scheduler-8620 DEBUG Checking readiness of task: 1350 / 0x46620a0
Jul 07 20:45:44-234532 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-234724 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-234931 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-235122 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-235312 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-235502 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-235720 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-235913 util-scheduler-8620 DEBUG Running task: 1350 / 0x46620a0
Jul 07 20:45:44-236315 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-236543 util-scheduler-8620 DEBUG Adding task: 1358 / 0x4662248
Jul 07 20:45:44-236753 util-scheduler-8620 DEBUG Running task: 1357 / 0x46620a0
Jul 07 20:45:44-236938 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-237114 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-237308 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-237485 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:44-237675 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:44-237863 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:44-238162 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-238409 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-238603 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-238793 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-238997 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-239201 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-239391 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-239580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-239769 util-scheduler-8620 DEBUG Running task: 1358 / 0x4662248
Jul 07 20:45:44-239958 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:44-241883 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:44-242124 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:44-242309 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-242517 util-scheduler-8620 DEBUG Adding task: 1359 / 0x46620a0
Jul 07 20:45:44-242760 util-scheduler-8620 DEBUG Checking readiness of task: 1359 / 0x46620a0
Jul 07 20:45:44-242954 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-243145 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-243334 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-243524 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-243712 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-243901 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-244091 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-244282 util-scheduler-8620 DEBUG Running task: 1359 / 0x46620a0
Jul 07 20:45:44-244684 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-244916 util-scheduler-8620 DEBUG Adding task: 1360 / 0x4662248
Jul 07 20:45:44-245165 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-245384 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-245574 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-245764 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-245953 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-246142 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-246331 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-246522 util-scheduler-8620 DEBUG Running task: 1360 / 0x4662248
Jul 07 20:45:44-246728 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:44-246921 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:44-247132 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:44-247330 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-247529 util-scheduler-8620 DEBUG Adding task: 1361 / 0x46620a0
Jul 07 20:45:44-247713 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-247910 util-scheduler-8620 DEBUG Adding task: 1362 / 0x46620a0
Jul 07 20:45:44-248151 util-scheduler-8620 DEBUG Checking readiness of task: 1362 / 0x46620a0
Jul 07 20:45:44-248363 util-scheduler-8620 DEBUG Checking readiness of task: 1361 / 0x46620a0
Jul 07 20:45:44-248556 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-248746 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-248938 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-249127 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-249356 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-249546 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-249735 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-249927 util-scheduler-8620 DEBUG Running task: 1361 / 0x46620a0
Jul 07 20:45:44-250111 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-250287 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-250456 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-250641 util-scheduler-8620 DEBUG Canceling task: 1356 / 0x4d6ff98
Jul 07 20:45:44-250860 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:44-251077 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:44-251310 cadet-p2p-8620 DEBUG Checking 0x751bda8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-251541 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:44-251718 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:44-251905 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:44-252185 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:44-252379 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:44-252556 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:44-252743 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:44-252930 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:44-253107 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:44-253313 util-scheduler-8620 DEBUG Canceling task: 1352 / 0x4d707d0
Jul 07 20:45:44-254708 util-scheduler-8620 DEBUG Adding task: 1363 / 0x4d707d0
Jul 07 20:45:44-254966 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:44-255139 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:44-255361 cadet-p2p-8620 DEBUG Checking 0x46f0850 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-255602 cadet-p2p-8620 DEBUG Checking 0x46f0850 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-255780 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:44-255984 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 20:45:44-256212 util-scheduler-8620 DEBUG Adding task: 1364 / 0x4d6ff98
Jul 07 20:45:44-256391 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:44-256566 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:44-256763 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:44-256939 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:44-257112 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:44-257372 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-257566 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:44-257743 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:44-257958 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:44-258162 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:44-258345 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:44-258544 util-scheduler-8620 DEBUG Adding task: 1365 / 0x4d6ff98
Jul 07 20:45:44-258760 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:44-258957 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-259159 util-scheduler-8620 DEBUG Adding task: 1366 / 0x46620a0
Jul 07 20:45:44-259357 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:44-260761 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-261014 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:44-261355 util-scheduler-8620 DEBUG Checking readiness of task: 1366 / 0x46620a0
Jul 07 20:45:44-261569 util-scheduler-8620 DEBUG Checking readiness of task: 1362 / 0x46620a0
Jul 07 20:45:44-261762 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-261953 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-262142 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-262332 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-262521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-262711 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-262903 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-263094 util-scheduler-8620 DEBUG Running task: 1366 / 0x46620a0
Jul 07 20:45:44-263280 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-263457 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-263629 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-263812 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:44-264007 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:44-264198 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:44-264519 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-264730 util-scheduler-8620 DEBUG Running task: 1364 / 0x4d6ff98
Jul 07 20:45:44-264927 util-scheduler-8620 DEBUG Canceling task: 1365 / 0x4d6ff98
Jul 07 20:45:44-265144 util-scheduler-8620 DEBUG Adding task: 1367 / 0x4d6ff98
Jul 07 20:45:44-265382 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:44-265577 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-265787 util-scheduler-8620 DEBUG Adding task: 1368 / 0x46620a0
Jul 07 20:45:44-266030 util-scheduler-8620 DEBUG Checking readiness of task: 1368 / 0x46620a0
Jul 07 20:45:44-266224 util-scheduler-8620 DEBUG Checking readiness of task: 1362 / 0x46620a0
Jul 07 20:45:44-266416 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-266607 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-266798 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-266987 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-267179 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-267369 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-267559 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-267749 util-scheduler-8620 DEBUG Running task: 1362 / 0x46620a0
Jul 07 20:45:44-268150 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-268426 util-scheduler-8620 DEBUG Adding task: 1369 / 0x4662248
Jul 07 20:45:44-268655 util-scheduler-8620 DEBUG Running task: 1368 / 0x46620a0
Jul 07 20:45:44-268859 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-269058 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-269254 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-269432 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:44-269622 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:44-269812 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:44-270125 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-270374 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-270567 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-270757 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-270946 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-271136 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-271325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-271513 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-271702 util-scheduler-8620 DEBUG Running task: 1369 / 0x4662248
Jul 07 20:45:44-271891 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:44-272082 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:44-272294 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:44-272474 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-272675 util-scheduler-8620 DEBUG Adding task: 1370 / 0x46620a0
Jul 07 20:45:44-272914 util-scheduler-8620 DEBUG Checking readiness of task: 1370 / 0x46620a0
Jul 07 20:45:44-273109 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-273320 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-273510 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-273699 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-273888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-274077 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-274265 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-274454 util-scheduler-8620 DEBUG Running task: 1370 / 0x46620a0
Jul 07 20:45:44-274853 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:44-275077 util-scheduler-8620 DEBUG Adding task: 1371 / 0x4662248
Jul 07 20:45:44-275324 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-275516 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-275705 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-278079 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-278291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-278486 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-278677 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-278869 util-scheduler-8620 DEBUG Running task: 1371 / 0x4662248
Jul 07 20:45:44-279135 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:44-279330 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:44-279545 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:44-279744 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:44-279960 util-scheduler-8620 DEBUG Adding task: 1372 / 0x46620a0
Jul 07 20:45:44-280145 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:44-280344 util-scheduler-8620 DEBUG Adding task: 1373 / 0x46620a0
Jul 07 20:45:44-280586 util-scheduler-8620 DEBUG Checking readiness of task: 1373 / 0x46620a0
Jul 07 20:45:44-280780 util-scheduler-8620 DEBUG Checking readiness of task: 1372 / 0x46620a0
Jul 07 20:45:44-280971 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-281161 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-281378 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-281567 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-281756 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-281944 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-282134 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-282324 util-scheduler-8620 DEBUG Running task: 1372 / 0x46620a0
Jul 07 20:45:44-282507 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:44-282682 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-282852 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-283034 util-scheduler-8620 DEBUG Canceling task: 1367 / 0x4d6ff98
Jul 07 20:45:44-283254 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 20:45:44-283469 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:44-283700 cadet-p2p-8620 DEBUG Checking 0x46f0850 towards CMHCKRVP (->V8XX)
Jul 07 20:45:44-283931 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:44-284107 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:44-284295 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:44-284571 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 48)
Jul 07 20:45:44-284765 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:44-284947 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:44-285134 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:44-285387 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:44-285565 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:44-285750 util-scheduler-8620 DEBUG Canceling task: 1363 / 0x4d707d0
Jul 07 20:45:44-285963 util-scheduler-8620 DEBUG Adding task: 1374 / 0x4d707d0
Jul 07 20:45:44-286207 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:44-286377 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:44-286556 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:44-286755 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:44-286930 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:44-287104 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:44-287303 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:44-287507 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 20:45:44-287690 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:44-287868 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:44-288056 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:44-289282 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:44-717943 util-scheduler-8620 DEBUG Checking readiness of task: 1373 / 0x46620a0
Jul 07 20:45:44-718316 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-718513 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-718705 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-718897 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-719101 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-719320 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-719512 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-719704 util-scheduler-8620 DEBUG Running task: 1351 / 0x4d65218
Jul 07 20:45:44-720133 cadet-chn-8620 DEBUG !!! RE-CREATE
Jul 07 20:45:44-720424 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:44-720644 util-scheduler-8620 DEBUG Adding task: 1375 / 0x4d5e5d8
Jul 07 20:45:44-720936 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:44-721159 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:45:44-721444 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:44-721626 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:44-721810 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:44-721992 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:44-722169 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:44-722339 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:44-722554 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:44-722730 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:44-722969 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:44-723157 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:44-723462 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:44-723634 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:44-723820 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:44-727586 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:44-728888 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:44-729788 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:44-729986 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:45:44-733779 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:44-734034 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:44-734219 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:44-734442 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:44-734637 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:45:44-734919 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection CMHCKRVP (->V8XX) (96 bytes)
Jul 07 20:45:44-735122 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:45:44-735301 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:45:44-735475 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:45:44-735646 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:44-736030 cadet-con-8620 DEBUG  *** POLL FWD requested
Jul 07 20:45:44-736302 cadet-con-8620 DEBUG  *** POLL started on request
Jul 07 20:45:44-736522 util-scheduler-8620 DEBUG Adding task: 1376 / 0x4d707d4
Jul 07 20:45:44-736713 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:44-736952 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:44-737162 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:44-737505 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 96)
Jul 07 20:45:44-737705 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:44-737929 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:44-738112 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:44-738287 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:44-738589 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX not needed
Jul 07 20:45:44-739240 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:44-739427 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:44-739605 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:44-739843 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:44-740105 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:44-740287 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:44-740513 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:44-740793 util-scheduler-8620 DEBUG Checking readiness of task: 1375 / 0x4d5e5d8
Jul 07 20:45:44-740991 util-scheduler-8620 DEBUG Checking readiness of task: 1373 / 0x46620a0
Jul 07 20:45:44-741183 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:44-741397 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:44-741588 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:44-741778 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:44-741967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:44-742157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:44-742346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:44-742539 util-scheduler-8620 DEBUG Running task: 1375 / 0x4d5e5d8
Jul 07 20:45:44-742725 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:44-742904 util-8620 DEBUG process_notify is running
Jul 07 20:45:44-743077 util-8620 DEBUG client_notify is running
Jul 07 20:45:44-743308 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:44-743622 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:45-378144 util-scheduler-8620 DEBUG Checking readiness of task: 1373 / 0x46620a0
Jul 07 20:45:45-378526 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-378723 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-378915 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-379105 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-379296 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-379486 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-379677 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-379872 util-scheduler-8620 DEBUG Running task: 1373 / 0x46620a0
Jul 07 20:45:45-380293 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:45-380551 util-scheduler-8620 DEBUG Adding task: 1377 / 0x4662248
Jul 07 20:45:45-380833 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-381027 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-381246 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-381438 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-381627 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-381818 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-382007 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-382195 util-scheduler-8620 DEBUG Running task: 1377 / 0x4662248
Jul 07 20:45:45-382387 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:45-382585 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:45-382830 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:45-383038 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:45-383245 util-scheduler-8620 DEBUG Adding task: 1378 / 0x46620a0
Jul 07 20:45:45-383433 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:45-383640 util-scheduler-8620 DEBUG Adding task: 1379 / 0x46620a0
Jul 07 20:45:45-383883 util-scheduler-8620 DEBUG Checking readiness of task: 1379 / 0x46620a0
Jul 07 20:45:45-384077 util-scheduler-8620 DEBUG Checking readiness of task: 1378 / 0x46620a0
Jul 07 20:45:45-384269 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-384492 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-384684 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-384873 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-385062 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-385279 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-385470 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-385661 util-scheduler-8620 DEBUG Running task: 1378 / 0x46620a0
Jul 07 20:45:45-385847 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:45-386024 util-8620 DEBUG process_notify is running
Jul 07 20:45:45-386196 util-8620 DEBUG client_notify is running
Jul 07 20:45:45-386387 util-scheduler-8620 DEBUG Canceling task: 1333 / 0x4d5c9e8
Jul 07 20:45:45-386613 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:45:45-386834 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:45-387074 cadet-p2p-8620 DEBUG Checking 0x4723988 towards HS92G30M (->KNAS)
Jul 07 20:45:45-387320 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:45-387500 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:45-387693 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:45-387963 cadet-p2p-8620 INFO snd {               ACK} ( 82) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:45-388158 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:45-388339 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:45-388528 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:45-388702 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:45-388886 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:45-389060 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:45-389268 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:45-389470 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:45-389646 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:45-389821 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:45-390020 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:45-390224 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:45-390408 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:45-390587 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:45-390778 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:45-391689 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:45-737024 util-scheduler-8620 DEBUG Checking readiness of task: 1379 / 0x46620a0
Jul 07 20:45:45-737422 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-737619 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-737811 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-738001 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-738191 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-738380 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-738569 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-738764 util-scheduler-8620 DEBUG Running task: 1376 / 0x4d707d4
Jul 07 20:45:45-739038 cadet-con-8620 DEBUG  *** Polling connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:45-739218 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:45:45-739494 cadet-con-8620 INFO --> {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:45:45-739686 cadet-con-8620 DEBUG  poll 0
Jul 07 20:45:45-739863 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:45-740100 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:45-740344 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:45-740715 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:45:45-740924 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:45-741160 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:45-741374 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:45-741557 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:45-741774 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:45:45-741998 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:45:45-742238 util-scheduler-8620 DEBUG Adding task: 1380 / 0x4d6ff98
Jul 07 20:45:45-742512 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:45-742731 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:45-742911 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:45-743086 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:45-743331 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:45-743515 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:45-743691 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:45-743923 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:45-744118 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:45-744293 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:45-744490 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:45-744753 util-scheduler-8620 DEBUG Checking readiness of task: 1379 / 0x46620a0
Jul 07 20:45:45-744947 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-745136 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-745349 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-745536 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-745724 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-745912 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-746099 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-746289 util-scheduler-8620 DEBUG Running task: 1380 / 0x4d6ff98
Jul 07 20:45:45-746507 util-scheduler-8620 DEBUG Adding task: 1381 / 0x4d6ff98
Jul 07 20:45:45-746732 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:45-746935 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:45-747142 util-scheduler-8620 DEBUG Adding task: 1382 / 0x46620a0
Jul 07 20:45:45-747383 util-scheduler-8620 DEBUG Checking readiness of task: 1382 / 0x46620a0
Jul 07 20:45:45-747577 util-scheduler-8620 DEBUG Checking readiness of task: 1379 / 0x46620a0
Jul 07 20:45:45-747766 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:45-747955 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:45-748145 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:45-748333 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:45-748521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:45-748707 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:45-748899 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:45-749089 util-scheduler-8620 DEBUG Running task: 1382 / 0x46620a0
Jul 07 20:45:45-749295 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:45-749472 util-8620 DEBUG process_notify is running
Jul 07 20:45:45-749646 util-8620 DEBUG client_notify is running
Jul 07 20:45:45-749823 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:45-750022 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:45-750223 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:45-750553 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:46-844477 util-scheduler-8620 DEBUG Checking readiness of task: 1379 / 0x46620a0
Jul 07 20:45:46-844861 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:46-845058 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:46-845281 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:46-845486 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:46-845679 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:46-845869 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:46-846060 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:46-846258 util-scheduler-8620 DEBUG Running task: 1379 / 0x46620a0
Jul 07 20:45:46-846679 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:46-846936 util-scheduler-8620 DEBUG Adding task: 1383 / 0x4662248
Jul 07 20:45:46-847214 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:46-847408 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:46-847599 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:46-847788 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:46-847980 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:46-848168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:46-848357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:46-848546 util-scheduler-8620 DEBUG Running task: 1383 / 0x4662248
Jul 07 20:45:46-848738 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:46-848936 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:46-849167 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:46-849395 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:46-849603 util-scheduler-8620 DEBUG Adding task: 1384 / 0x46620a0
Jul 07 20:45:46-849790 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:46-849996 util-scheduler-8620 DEBUG Adding task: 1385 / 0x46620a0
Jul 07 20:45:46-850284 util-scheduler-8620 DEBUG Checking readiness of task: 1385 / 0x46620a0
Jul 07 20:45:46-850477 util-scheduler-8620 DEBUG Checking readiness of task: 1384 / 0x46620a0
Jul 07 20:45:46-850672 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:46-850872 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:46-851064 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:46-851255 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:46-851447 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:46-851638 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:46-851831 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:46-852025 util-scheduler-8620 DEBUG Running task: 1384 / 0x46620a0
Jul 07 20:45:46-852209 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:46-852390 util-8620 DEBUG process_notify is running
Jul 07 20:45:46-852561 util-8620 DEBUG client_notify is running
Jul 07 20:45:46-852754 util-scheduler-8620 DEBUG Canceling task: 1381 / 0x4d6ff98
Jul 07 20:45:46-852984 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:45:46-853230 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:46-853473 cadet-p2p-8620 DEBUG Checking 0x49b57f0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:46-853710 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:46-853918 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:46-854111 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:45:46-854383 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:45:46-854579 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:46-854759 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:46-854948 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:45:46-855123 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:46-855293 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:45:46-855508 util-scheduler-8620 DEBUG Adding task: 1386 / 0x4d707d4
Jul 07 20:45:46-855696 cadet-con-8620 DEBUG  task 1386
Jul 07 20:45:46-855881 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:46-856056 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:46-856279 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:46-856514 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:46-856698 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:46-856873 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:46-857103 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:46-857357 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:46-857540 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:46-857713 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:46-857883 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:46-858084 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:46-858260 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:46-858435 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:46-858674 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:46-858871 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:46-859050 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:46-859249 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:46-859455 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:45:46-859640 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:46-859820 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:46-860012 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:46-860250 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-574924 util-scheduler-8620 DEBUG Checking readiness of task: 1385 / 0x46620a0
Jul 07 20:45:48-575323 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-575522 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-575716 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-575909 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-576100 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-576291 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-576481 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-576675 util-scheduler-8620 DEBUG Running task: 1385 / 0x46620a0
Jul 07 20:45:48-577098 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:48-577382 util-scheduler-8620 DEBUG Adding task: 1387 / 0x4662248
Jul 07 20:45:48-577666 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-577863 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-578056 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-578248 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-578470 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-578663 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-578853 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-579044 util-scheduler-8620 DEBUG Running task: 1387 / 0x4662248
Jul 07 20:45:48-579236 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:48-579438 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:48-579681 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:48-579895 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-580104 util-scheduler-8620 DEBUG Adding task: 1388 / 0x46620a0
Jul 07 20:45:48-580291 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:48-580496 util-scheduler-8620 DEBUG Adding task: 1389 / 0x46620a0
Jul 07 20:45:48-580760 util-scheduler-8620 DEBUG Checking readiness of task: 1389 / 0x46620a0
Jul 07 20:45:48-580958 util-scheduler-8620 DEBUG Checking readiness of task: 1388 / 0x46620a0
Jul 07 20:45:48-581151 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-581369 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-581559 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-581749 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-581938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-582129 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-582319 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-582510 util-scheduler-8620 DEBUG Running task: 1388 / 0x46620a0
Jul 07 20:45:48-582697 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-582876 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-583563 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-583764 util-scheduler-8620 DEBUG Canceling task: 1312 / 0x5e2b838
Jul 07 20:45:48-583998 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 196 bytes.
Jul 07 20:45:48-584222 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:48-584465 cadet-p2p-8620 DEBUG Checking 0x690f140 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-584700 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:48-584880 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:48-585073 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:48-585388 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 196)
Jul 07 20:45:48-585587 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:48-585769 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:48-585962 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:48-586153 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 6
Jul 07 20:45:48-586332 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:48-586538 util-scheduler-8620 DEBUG Adding task: 1390 / 0x5e31aa0
Jul 07 20:45:48-586793 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:48-586970 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:48-587193 cadet-p2p-8620 DEBUG Checking 0x6915f18 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-587436 cadet-p2p-8620 DEBUG Checking 0x6915f18 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-587616 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:48-587824 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `D3TJ'
Jul 07 20:45:48-588041 util-scheduler-8620 DEBUG Adding task: 1391 / 0x5e2b838
Jul 07 20:45:48-588220 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:48-588398 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:48-588596 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:48-589758 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:48-589945 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:48-590218 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-590417 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:48-590596 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:48-590833 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-591029 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:48-591206 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:48-591441 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-591634 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:48-591813 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:48-592051 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-592246 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:48-592424 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:48-592660 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-592855 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:48-593032 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:48-593255 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:48-593464 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 196 bytes.
Jul 07 20:45:48-593651 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:48-593866 util-scheduler-8620 DEBUG Adding task: 1392 / 0x5e2b838
Jul 07 20:45:48-594088 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:48-594288 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-594496 util-scheduler-8620 DEBUG Adding task: 1393 / 0x46620a0
Jul 07 20:45:48-594699 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:48-597934 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-598181 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:48-598537 util-scheduler-8620 DEBUG Checking readiness of task: 1393 / 0x46620a0
Jul 07 20:45:48-598792 util-scheduler-8620 DEBUG Checking readiness of task: 1389 / 0x46620a0
Jul 07 20:45:48-598988 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-599180 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-599371 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-599562 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-599753 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-599943 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-600133 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-600328 util-scheduler-8620 DEBUG Running task: 1393 / 0x46620a0
Jul 07 20:45:48-600517 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-600696 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-600872 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-601054 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:48-601280 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:48-601472 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:48-602190 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-602409 util-scheduler-8620 DEBUG Running task: 1391 / 0x5e2b838
Jul 07 20:45:48-602609 util-scheduler-8620 DEBUG Canceling task: 1392 / 0x5e2b838
Jul 07 20:45:48-602840 util-scheduler-8620 DEBUG Adding task: 1394 / 0x5e2b838
Jul 07 20:45:48-603067 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:48-603267 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-603493 util-scheduler-8620 DEBUG Adding task: 1395 / 0x46620a0
Jul 07 20:45:48-603742 util-scheduler-8620 DEBUG Checking readiness of task: 1395 / 0x46620a0
Jul 07 20:45:48-603938 util-scheduler-8620 DEBUG Checking readiness of task: 1389 / 0x46620a0
Jul 07 20:45:48-604131 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-604321 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-604514 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-604712 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-604903 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-605091 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-605303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-605493 util-scheduler-8620 DEBUG Running task: 1389 / 0x46620a0
Jul 07 20:45:48-605903 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:48-606137 util-scheduler-8620 DEBUG Adding task: 1396 / 0x4662248
Jul 07 20:45:48-606349 util-scheduler-8620 DEBUG Running task: 1395 / 0x46620a0
Jul 07 20:45:48-606533 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-606709 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-606877 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-607054 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:48-607259 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:48-607448 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:48-607679 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-607927 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-608122 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-608313 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-608503 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-608694 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-609382 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-609580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-609773 util-scheduler-8620 DEBUG Running task: 1396 / 0x4662248
Jul 07 20:45:48-609965 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:48-610161 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:48-610383 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:48-610567 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:48-610776 util-scheduler-8620 DEBUG Adding task: 1397 / 0x46620a0
Jul 07 20:45:48-655803 util-scheduler-8620 DEBUG Checking readiness of task: 1397 / 0x46620a0
Jul 07 20:45:48-656116 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-656317 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-656510 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-656705 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-656899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-657090 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-657303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-657497 util-scheduler-8620 DEBUG Running task: 1397 / 0x46620a0
Jul 07 20:45:48-657916 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:48-658186 util-scheduler-8620 DEBUG Adding task: 1398 / 0x4662248
Jul 07 20:45:48-658455 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-658646 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-658836 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-659025 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-659212 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-659400 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-659588 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-659776 util-scheduler-8620 DEBUG Running task: 1398 / 0x4662248
Jul 07 20:45:48-659966 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:48-660162 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:48-660382 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:48-660586 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-660788 util-scheduler-8620 DEBUG Adding task: 1399 / 0x46620a0
Jul 07 20:45:48-660973 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:48-661175 util-scheduler-8620 DEBUG Adding task: 1400 / 0x46620a0
Jul 07 20:45:48-662151 util-scheduler-8620 DEBUG Checking readiness of task: 1400 / 0x46620a0
Jul 07 20:45:48-662346 util-scheduler-8620 DEBUG Checking readiness of task: 1399 / 0x46620a0
Jul 07 20:45:48-662538 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-662727 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-662916 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-663106 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-663295 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-663484 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-663672 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-663864 util-scheduler-8620 DEBUG Running task: 1399 / 0x46620a0
Jul 07 20:45:48-664048 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-664225 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-664394 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-664583 util-scheduler-8620 DEBUG Canceling task: 1394 / 0x5e2b838
Jul 07 20:45:48-664807 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 80 bytes.
Jul 07 20:45:48-665026 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:48-665283 cadet-p2p-8620 DEBUG Checking 0x6915f18 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-665517 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:48-665694 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:48-665883 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:48-666167 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 80)
Jul 07 20:45:48-666361 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:48-666541 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:48-666728 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:48-666916 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 5
Jul 07 20:45:48-667093 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:48-667282 util-scheduler-8620 DEBUG Canceling task: 1390 / 0x5e31aa0
Jul 07 20:45:48-667500 util-scheduler-8620 DEBUG Adding task: 1401 / 0x5e31aa0
Jul 07 20:45:48-667756 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:48-667931 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:48-668161 cadet-p2p-8620 DEBUG Checking 0x70052b0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-668408 cadet-p2p-8620 DEBUG Checking 0x70052b0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-668612 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:48-668823 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `D3TJ'
Jul 07 20:45:48-669046 util-scheduler-8620 DEBUG Adding task: 1402 / 0x5e2b838
Jul 07 20:45:48-669252 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:48-669428 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:48-669628 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:48-669802 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:48-669975 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:48-670214 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-670409 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:48-670585 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:48-670818 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-671010 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:48-671185 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:48-671415 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-671608 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:48-671783 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:48-672015 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:48-672207 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:48-672381 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:48-672578 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:48-672781 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 80 bytes.
Jul 07 20:45:48-672963 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:48-673164 util-scheduler-8620 DEBUG Adding task: 1403 / 0x5e2b838
Jul 07 20:45:48-673402 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:48-673599 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-673800 util-scheduler-8620 DEBUG Adding task: 1404 / 0x46620a0
Jul 07 20:45:48-673999 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:48-675109 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-675327 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:48-675578 util-scheduler-8620 DEBUG Checking readiness of task: 1404 / 0x46620a0
Jul 07 20:45:48-675773 util-scheduler-8620 DEBUG Checking readiness of task: 1400 / 0x46620a0
Jul 07 20:45:48-675966 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-676156 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-676344 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-676532 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-676721 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-676909 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-677097 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-677308 util-scheduler-8620 DEBUG Running task: 1404 / 0x46620a0
Jul 07 20:45:48-677494 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-677670 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-677840 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-678019 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:48-678213 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:48-678403 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:48-678683 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-678890 util-scheduler-8620 DEBUG Running task: 1402 / 0x5e2b838
Jul 07 20:45:48-679099 util-scheduler-8620 DEBUG Canceling task: 1403 / 0x5e2b838
Jul 07 20:45:48-679314 util-scheduler-8620 DEBUG Adding task: 1405 / 0x5e2b838
Jul 07 20:45:48-679530 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:48-679723 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-679923 util-scheduler-8620 DEBUG Adding task: 1406 / 0x46620a0
Jul 07 20:45:48-680168 util-scheduler-8620 DEBUG Checking readiness of task: 1406 / 0x46620a0
Jul 07 20:45:48-680367 util-scheduler-8620 DEBUG Checking readiness of task: 1400 / 0x46620a0
Jul 07 20:45:48-680560 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-680753 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-680947 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-681139 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-681352 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-681544 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-681737 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-681930 util-scheduler-8620 DEBUG Running task: 1406 / 0x46620a0
Jul 07 20:45:48-682115 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-682293 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-682462 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-682639 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:48-682832 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:48-683020 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:48-683302 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:48-796650 util-scheduler-8620 DEBUG Checking readiness of task: 1400 / 0x46620a0
Jul 07 20:45:48-797000 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-797224 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-797420 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-797614 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-797806 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-797997 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-798188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-798385 util-scheduler-8620 DEBUG Running task: 1400 / 0x46620a0
Jul 07 20:45:48-798804 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:48-799061 util-scheduler-8620 DEBUG Adding task: 1407 / 0x4662248
Jul 07 20:45:48-799339 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-799538 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-799730 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-799920 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-800111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-800301 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-800490 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-800683 util-scheduler-8620 DEBUG Running task: 1407 / 0x4662248
Jul 07 20:45:48-800873 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:48-801080 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:48-801341 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:48-801610 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:48-801892 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:48-802129 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:48-802340 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:48-802590 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:48-802800 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:48-802990 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:48-803184 util-scheduler-8620 DEBUG Canceling task: 1344 / 0x4d707d0
Jul 07 20:45:48-804433 util-scheduler-8620 DEBUG Adding task: 1408 / 0x4d707d0
Jul 07 20:45:48-804698 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:48-804965 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:48-805183 util-scheduler-8620 DEBUG Adding task: 1409 / 0x4d5e5d8
Jul 07 20:45:48-805391 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:48-805596 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:48-805816 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:48-806023 util-scheduler-8620 DEBUG Adding task: 1410 / 0x46620a0
Jul 07 20:45:48-806288 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:48-806486 util-scheduler-8620 DEBUG Checking readiness of task: 1409 / 0x4d5e5d8
Jul 07 20:45:48-806683 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-806878 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-807074 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-807270 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-807464 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-807664 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-807855 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-808052 util-scheduler-8620 DEBUG Running task: 1409 / 0x4d5e5d8
Jul 07 20:45:48-808241 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:48-808423 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-808597 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-808846 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:48-809056 util-scheduler-8620 DEBUG Adding task: 1411 / 0x4d5e5d8
Jul 07 20:45:48-809285 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:48-809587 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:48-809787 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:48-810040 util-scheduler-8620 DEBUG Checking readiness of task: 1411 / 0x4d5e5d8
Jul 07 20:45:48-810233 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:48-810424 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-810613 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-810801 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-810990 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-811179 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-811367 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-811568 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-811758 util-scheduler-8620 DEBUG Running task: 1411 / 0x4d5e5d8
Jul 07 20:45:48-811940 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:48-812115 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-812283 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-812493 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:48-812777 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:48-855678 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:48-855988 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-856182 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-856373 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-856563 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-856753 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-856943 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-857132 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-857345 util-scheduler-8620 DEBUG Running task: 1386 / 0x4d707d4
Jul 07 20:45:48-857606 cadet-con-8620 DEBUG  *** Polling connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:48-857787 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:45:48-858059 cadet-con-8620 INFO --> {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:45:48-858250 cadet-con-8620 DEBUG  poll 0
Jul 07 20:45:48-858426 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:48-858662 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:48-858872 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:48-859173 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:45:48-859370 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:48-859599 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:48-859781 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:48-859955 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:48-860163 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:45:48-860379 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:45:48-860600 util-scheduler-8620 DEBUG Adding task: 1412 / 0x4d6ff98
Jul 07 20:45:48-860778 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:48-860983 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:48-861159 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:48-861353 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:48-861593 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:48-862074 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:48-862252 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:48-862489 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:48-862683 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:48-862859 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:48-863056 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:48-863309 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:48-863503 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-863693 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-863882 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-864071 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-864258 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-864447 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-864634 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-864822 util-scheduler-8620 DEBUG Running task: 1412 / 0x4d6ff98
Jul 07 20:45:48-865033 util-scheduler-8620 DEBUG Adding task: 1413 / 0x4d6ff98
Jul 07 20:45:48-865293 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:48-865501 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:48-865713 util-scheduler-8620 DEBUG Adding task: 1414 / 0x46620a0
Jul 07 20:45:48-865992 util-scheduler-8620 DEBUG Checking readiness of task: 1414 / 0x46620a0
Jul 07 20:45:48-866193 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:48-866390 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:48-866586 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:48-866780 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:48-866975 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:48-867268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:48-867464 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:48-867655 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:48-867846 util-scheduler-8620 DEBUG Running task: 1414 / 0x46620a0
Jul 07 20:45:48-868032 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:48-868211 util-8620 DEBUG process_notify is running
Jul 07 20:45:48-868382 util-8620 DEBUG client_notify is running
Jul 07 20:45:48-868561 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:48-868760 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:48-868951 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:48-869274 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:49-166117 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:49-166468 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-166664 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-166855 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-167064 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-167254 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-167443 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-167633 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-167824 util-scheduler-8620 DEBUG Running task: 1339 / 0x5e2de48
Jul 07 20:45:49-168076 cadet-tun-8620 INFO Re-key Tunnel D3TJ
Jul 07 20:45:49-168322 cadet-tun-8620 DEBUG  kx started 20 s ago
Jul 07 20:45:49-168528 cadet-tun-8620 INFO ===> EPHM for D3TJ
Jul 07 20:45:49-168731 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:49-168939 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:49-169222 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:49-169408 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:49-169632 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:49-169811 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:49-170035 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-170432 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (196 bytes)
Jul 07 20:45:49-170643 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 4
Jul 07 20:45:49-170883 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:49-171090 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:49-171427 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 196)
Jul 07 20:45:49-171628 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:49-171853 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-172034 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:49-172229 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:49-172433 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:49-172649 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:49-172827 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:49-173029 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:49-173293 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-173508 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-173686 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-173918 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-174111 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:49-174287 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:49-174538 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-174730 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-174905 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-175136 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-175329 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:49-175521 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:49-175754 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-175946 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-176124 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-176321 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:49-176541 cadet-tun-8620 INFO ===> PING for D3TJ
Jul 07 20:45:49-176854 cadet-tun-8620 DEBUG   sending 1699275036
Jul 07 20:45:49-177054 cadet-tun-8620 DEBUG   towards D3TJ
Jul 07 20:45:49-177244 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:49-177426 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:49-181046 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:49-182459 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:49-182749 cadet-tun-8620 DEBUG   e sending 365706994
Jul 07 20:45:49-183076 cadet-tun-8620 DEBUG   e towards ZAGH
Jul 07 20:45:49-183292 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:49-183499 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:49-183735 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:49-183914 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:49-184157 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:49-184334 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:49-184552 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-184831 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (80 bytes)
Jul 07 20:45:49-185047 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 5
Jul 07 20:45:49-185307 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:49-185516 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:49-185829 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 80)
Jul 07 20:45:49-186031 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:49-186274 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-186457 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:49-186630 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:49-186832 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:49-187033 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:49-187226 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:49-187401 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:49-187636 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-187830 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-188007 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-188256 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-188450 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:49-188625 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:49-188858 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-189075 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-189273 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-189536 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-189728 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:49-189904 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:49-190135 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-190327 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:49-190520 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:49-190752 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:49-190944 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:49-191118 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:49-191315 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:49-191584 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:45:49-191792 util-scheduler-8620 DEBUG Adding task: 1415 / 0x5e2de48
Jul 07 20:45:49-770785 util-scheduler-8620 DEBUG Checking readiness of task: 1410 / 0x46620a0
Jul 07 20:45:49-771172 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-771370 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-771563 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-771757 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-771948 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-772140 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-772329 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-772527 util-scheduler-8620 DEBUG Running task: 1410 / 0x46620a0
Jul 07 20:45:49-772950 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:49-773240 util-scheduler-8620 DEBUG Adding task: 1416 / 0x4662248
Jul 07 20:45:49-773525 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-773719 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-773911 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-774102 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-774291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-774480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-774670 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-774861 util-scheduler-8620 DEBUG Running task: 1416 / 0x4662248
Jul 07 20:45:49-775053 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:49-775253 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:49-775484 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:49-775750 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:49-775991 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:49-776235 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:49-776443 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:49-776690 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:49-776898 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:49-777085 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:49-777301 util-scheduler-8620 DEBUG Canceling task: 1408 / 0x4d707d0
Jul 07 20:45:49-777526 util-scheduler-8620 DEBUG Adding task: 1417 / 0x4d707d0
Jul 07 20:45:49-777705 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:49-777964 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:49-778182 util-scheduler-8620 DEBUG Adding task: 1418 / 0x4d5e5d8
Jul 07 20:45:49-778396 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:49-778597 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:49-778813 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:49-779020 util-scheduler-8620 DEBUG Adding task: 1419 / 0x46620a0
Jul 07 20:45:49-779269 util-scheduler-8620 DEBUG Checking readiness of task: 1419 / 0x46620a0
Jul 07 20:45:49-779465 util-scheduler-8620 DEBUG Checking readiness of task: 1418 / 0x4d5e5d8
Jul 07 20:45:49-779659 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-779848 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-780038 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-780226 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-780416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-780604 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-780793 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-780985 util-scheduler-8620 DEBUG Running task: 1418 / 0x4d5e5d8
Jul 07 20:45:49-781169 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:49-781377 util-8620 DEBUG process_notify is running
Jul 07 20:45:49-781549 util-8620 DEBUG client_notify is running
Jul 07 20:45:49-781789 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:49-781998 util-scheduler-8620 DEBUG Adding task: 1420 / 0x4d5e5d8
Jul 07 20:45:49-782200 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:49-782526 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:49-782726 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:49-782969 util-scheduler-8620 DEBUG Checking readiness of task: 1420 / 0x4d5e5d8
Jul 07 20:45:49-783164 util-scheduler-8620 DEBUG Checking readiness of task: 1419 / 0x46620a0
Jul 07 20:45:49-783354 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-783544 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-783733 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-783922 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-784111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-784300 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-784487 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-784677 util-scheduler-8620 DEBUG Running task: 1420 / 0x4d5e5d8
Jul 07 20:45:49-784860 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:49-785035 util-8620 DEBUG process_notify is running
Jul 07 20:45:49-785226 util-8620 DEBUG client_notify is running
Jul 07 20:45:49-785439 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:49-785724 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:49-993070 util-scheduler-8620 DEBUG Checking readiness of task: 1419 / 0x46620a0
Jul 07 20:45:49-993459 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-993659 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-993851 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-994043 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-994235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-994425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-994615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-994809 util-scheduler-8620 DEBUG Running task: 1419 / 0x46620a0
Jul 07 20:45:49-995259 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:49-995511 util-scheduler-8620 DEBUG Adding task: 1421 / 0x4662248
Jul 07 20:45:49-995787 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:49-995980 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:49-996170 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:49-996359 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:49-996549 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:49-996738 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:49-996927 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:49-997116 util-scheduler-8620 DEBUG Running task: 1421 / 0x4662248
Jul 07 20:45:49-997333 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:49-997535 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:49-997763 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:49-998028 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:49-998394 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:49-998611 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:49-998796 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:49-998969 cadet-con-8620 DEBUG   ACK 83 (was 82)
Jul 07 20:45:49-999198 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:49-999429 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:49-999636 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:49-999818 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:50-000021 util-scheduler-8620 DEBUG Adding task: 1422 / 0x4662248
Jul 07 20:45:50-000263 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-000459 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-000650 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-000842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-001033 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-001247 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-001439 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-001630 util-scheduler-8620 DEBUG Running task: 1422 / 0x4662248
Jul 07 20:45:50-001821 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:45:50-002015 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:45:50-002232 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:45:50-002476 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:50-002713 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:50-002943 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:50-003153 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:50-003394 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:50-003601 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:50-003790 cadet-con-8620 DEBUG  PID 19 (expected 19+)
Jul 07 20:45:50-003973 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:50-004163 util-scheduler-8620 DEBUG Canceling task: 1325 / 0x4d61c30
Jul 07 20:45:50-004387 util-scheduler-8620 DEBUG Adding task: 1423 / 0x4d61c30
Jul 07 20:45:50-004569 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:50-004828 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:50-005048 util-scheduler-8620 DEBUG Adding task: 1424 / 0x4d5e5d8
Jul 07 20:45:50-005485 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:50-005685 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:50-009286 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:50-010134 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:50-010347 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:50-013658 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on KNAS
Jul 07 20:45:50-014189 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:50-014376 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:50-014555 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:50-014731 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:50-014955 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:50-015136 cadet-con-8620 DEBUG  ACK 83
Jul 07 20:45:50-015319 cadet-con-8620 DEBUG  last pid 19, last ack 82, qmax 11, q 0
Jul 07 20:45:50-015588 cadet-con-8620 INFO --> {               ACK} ( 83) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:50-015785 cadet-con-8620 DEBUG  ack 83
Jul 07 20:45:50-015968 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:50-016206 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:50-016416 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:50-016717 cadet-p2p-8620 INFO que {               ACK} ( 83) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:50-016919 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:50-017145 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:50-017358 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 21
Jul 07 20:45:50-017535 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:50-017742 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:45:50-017961 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:45:50-018186 util-scheduler-8620 DEBUG Adding task: 1425 / 0x4d5c9e8
Jul 07 20:45:50-018372 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:50-018579 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:50-018758 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:50-018936 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:50-019176 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:50-019362 cadet-p2p-8620 DEBUG QQQ    payload , 83
Jul 07 20:45:50-019539 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:50-019743 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:50-019929 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:50-020141 util-scheduler-8620 DEBUG Adding task: 1426 / 0x46620a0
Jul 07 20:45:50-020412 util-scheduler-8620 DEBUG Checking readiness of task: 1426 / 0x46620a0
Jul 07 20:45:50-020610 util-scheduler-8620 DEBUG Checking readiness of task: 1424 / 0x4d5e5d8
Jul 07 20:45:50-020804 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-020996 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-021187 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-021404 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-021595 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-021786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-021977 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-022172 util-scheduler-8620 DEBUG Running task: 1424 / 0x4d5e5d8
Jul 07 20:45:50-022359 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:50-022540 util-8620 DEBUG process_notify is running
Jul 07 20:45:50-022714 util-8620 DEBUG client_notify is running
Jul 07 20:45:50-022945 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:50-023304 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:50-023518 util-scheduler-8620 DEBUG Running task: 1425 / 0x4d5c9e8
Jul 07 20:45:50-023756 util-scheduler-8620 DEBUG Adding task: 1427 / 0x4d5c9e8
Jul 07 20:45:50-023981 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:50-024183 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:50-024387 util-scheduler-8620 DEBUG Adding task: 1428 / 0x46620a0
Jul 07 20:45:50-024632 util-scheduler-8620 DEBUG Checking readiness of task: 1428 / 0x46620a0
Jul 07 20:45:50-024828 util-scheduler-8620 DEBUG Checking readiness of task: 1426 / 0x46620a0
Jul 07 20:45:50-025020 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-025237 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-025430 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-025622 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-025813 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-026004 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-026194 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-026386 util-scheduler-8620 DEBUG Running task: 1428 / 0x46620a0
Jul 07 20:45:50-026570 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:50-026748 util-8620 DEBUG process_notify is running
Jul 07 20:45:50-026918 util-8620 DEBUG client_notify is running
Jul 07 20:45:50-027099 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:50-027295 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:50-027486 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:50-027795 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:50-302511 util-scheduler-8620 DEBUG Checking readiness of task: 1426 / 0x46620a0
Jul 07 20:45:50-302901 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-303109 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-303307 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-303500 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-303691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-303881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-304072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-304267 util-scheduler-8620 DEBUG Running task: 1426 / 0x46620a0
Jul 07 20:45:50-304690 util-8620 DEBUG receive_ready read 348/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:50-304948 util-scheduler-8620 DEBUG Adding task: 1429 / 0x4662248
Jul 07 20:45:50-305252 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-305447 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-305637 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-305826 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-306016 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-306204 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-306393 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-306582 util-scheduler-8620 DEBUG Running task: 1429 / 0x4662248
Jul 07 20:45:50-306786 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:50-306988 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:50-307220 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `D3TJ'
Jul 07 20:45:50-307486 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:50-309550 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-309802 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-310013 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:50-310261 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-310470 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-310658 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:50-310851 util-scheduler-8620 DEBUG Canceling task: 1052 / 0x5e31aa0
Jul 07 20:45:50-311079 util-scheduler-8620 DEBUG Adding task: 1430 / 0x5e31aa0
Jul 07 20:45:50-311258 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:50-311516 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:50-311730 util-scheduler-8620 DEBUG Adding task: 1431 / 0x4d5e5d8
Jul 07 20:45:50-311913 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:50-312112 cadet-tun-8620 INFO <=== PING for D3TJ
Jul 07 20:45:50-312298 cadet-tun-8620 DEBUG   t_decrypt with V7H63X9N
Jul 07 20:45:50-312469 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:50-312635 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:50-318929 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:50-320028 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:50-320297 cadet-tun-8620 INFO ===> PONG for D3TJ
Jul 07 20:45:50-322889 cadet-tun-8620 DEBUG   sending 2999538669
Jul 07 20:45:50-323089 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:50-323279 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:50-326791 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:50-329280 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:50-329609 cadet-tun-8620 DEBUG   e sending 3086980843
Jul 07 20:45:50-329824 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:50-330026 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:50-330259 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:50-330439 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:50-330660 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:50-330837 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:50-331055 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-331335 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (48 bytes)
Jul 07 20:45:50-331535 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 6
Jul 07 20:45:50-331777 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-331990 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-332310 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 48)
Jul 07 20:45:50-332526 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:50-332767 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-332955 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:50-333137 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:50-333387 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:50-333597 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:50-333777 cadet-p2p-8620 DEBUG QQQ  queue length: 7
Jul 07 20:45:50-333959 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:50-334208 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-334411 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-334596 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-334842 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-335040 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-335219 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-335459 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-335657 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-335840 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-336081 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-336310 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-336490 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-336731 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-336929 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-337110 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-337381 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-337585 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-337769 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-338007 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-338200 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:50-338379 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:50-338577 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:50-338806 util-scheduler-8620 DEBUG Adding task: 1432 / 0x4662248
Jul 07 20:45:50-339088 util-scheduler-8620 DEBUG Checking readiness of task: 1431 / 0x4d5e5d8
Jul 07 20:45:50-339287 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-339478 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-339667 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-339856 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-340044 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-340232 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-340419 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-340613 util-scheduler-8620 DEBUG Running task: 1431 / 0x4d5e5d8
Jul 07 20:45:50-340799 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:50-340978 util-8620 DEBUG process_notify is running
Jul 07 20:45:50-341149 util-8620 DEBUG client_notify is running
Jul 07 20:45:50-341407 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:50-341729 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:50-341943 util-scheduler-8620 DEBUG Running task: 1432 / 0x4662248
Jul 07 20:45:50-342135 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:50-342331 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:50-342548 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:50-342798 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:50-343034 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-343261 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-343467 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:50-343709 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-343916 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-344102 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:50-344290 util-scheduler-8620 DEBUG Canceling task: 1430 / 0x5e31aa0
Jul 07 20:45:50-344514 util-scheduler-8620 DEBUG Adding task: 1433 / 0x5e31aa0
Jul 07 20:45:50-344692 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:50-344942 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:50-345156 util-scheduler-8620 DEBUG Adding task: 1434 / 0x4d5e5d8
Jul 07 20:45:50-345358 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:50-345556 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:50-963202 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:50-963623 util-scheduler-8620 DEBUG Adding task: 1435 / 0x46620a0
Jul 07 20:45:50-963923 util-scheduler-8620 DEBUG Checking readiness of task: 1435 / 0x46620a0
Jul 07 20:45:50-964127 util-scheduler-8620 DEBUG Checking readiness of task: 1434 / 0x4d5e5d8
Jul 07 20:45:50-964349 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-964541 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-964733 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-964922 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-965111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-965325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-965516 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-965711 util-scheduler-8620 DEBUG Running task: 1434 / 0x4d5e5d8
Jul 07 20:45:50-965897 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:50-966078 util-8620 DEBUG process_notify is running
Jul 07 20:45:50-966251 util-8620 DEBUG client_notify is running
Jul 07 20:45:50-966490 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:50-966915 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:50-967133 util-scheduler-8620 DEBUG Running task: 1435 / 0x46620a0
Jul 07 20:45:50-967545 util-8620 DEBUG receive_ready read 280/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:50-967791 util-scheduler-8620 DEBUG Adding task: 1436 / 0x4662248
Jul 07 20:45:50-968048 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-968243 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-968434 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-968628 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-968818 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-969009 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-969235 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-969428 util-scheduler-8620 DEBUG Running task: 1436 / 0x4662248
Jul 07 20:45:50-969621 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:50-969823 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:50-970054 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `D3TJ'
Jul 07 20:45:50-970318 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:50-970559 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-970790 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-971000 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:50-971249 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-971458 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-971649 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:50-971840 util-scheduler-8620 DEBUG Canceling task: 1433 / 0x5e31aa0
Jul 07 20:45:50-972065 util-scheduler-8620 DEBUG Adding task: 1437 / 0x5e31aa0
Jul 07 20:45:50-972247 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:50-972500 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:50-972714 util-scheduler-8620 DEBUG Adding task: 1438 / 0x4d5e5d8
Jul 07 20:45:50-972896 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:50-973096 cadet-tun-8620 INFO <=== PING for D3TJ
Jul 07 20:45:50-973312 cadet-tun-8620 DEBUG   t_decrypt with V7H63X9N
Jul 07 20:45:50-973486 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:50-973653 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:50-977263 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:50-978204 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:50-978441 cadet-tun-8620 INFO ===> PONG for D3TJ
Jul 07 20:45:50-978744 cadet-tun-8620 DEBUG   sending 2999538669
Jul 07 20:45:50-978922 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:50-979134 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:50-982865 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:50-984057 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:50-984309 cadet-tun-8620 DEBUG   e sending 514382377
Jul 07 20:45:50-984525 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:50-984729 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:50-984962 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:50-985145 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:50-985406 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:50-985800 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:50-986185 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-986507 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (48 bytes)
Jul 07 20:45:50-986721 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 7
Jul 07 20:45:50-986972 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-987188 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-987507 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 48)
Jul 07 20:45:50-987706 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:50-987938 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-988123 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:50-988298 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:50-988502 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:50-988705 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:50-988881 cadet-p2p-8620 DEBUG QQQ  queue length: 8
Jul 07 20:45:50-989055 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:50-989327 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-989524 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-989702 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-989935 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-990129 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-990305 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-990537 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-990730 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-990906 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-991138 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-991331 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-991506 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-991740 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-991932 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:50-992108 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:50-992342 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-992535 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:50-992711 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:50-992942 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-993135 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:50-993333 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:50-993566 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-993759 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:50-993935 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:50-994133 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:50-994364 util-scheduler-8620 DEBUG Adding task: 1439 / 0x4662248
Jul 07 20:45:50-994651 util-scheduler-8620 DEBUG Checking readiness of task: 1438 / 0x4d5e5d8
Jul 07 20:45:50-994852 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:50-995076 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:50-995266 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:50-995456 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:50-995644 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:50-995831 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:50-996021 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:50-996214 util-scheduler-8620 DEBUG Running task: 1438 / 0x4d5e5d8
Jul 07 20:45:50-996412 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:50-996594 util-8620 DEBUG process_notify is running
Jul 07 20:45:50-996767 util-8620 DEBUG client_notify is running
Jul 07 20:45:50-997002 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:50-997335 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:50-997549 util-scheduler-8620 DEBUG Running task: 1439 / 0x4662248
Jul 07 20:45:50-997742 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:50-997942 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:50-998160 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `D3TJ'
Jul 07 20:45:50-998411 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:50-998649 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:50-998879 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-999087 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:50-999335 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:50-999548 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:50-999745 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:51-000025 util-scheduler-8620 DEBUG Canceling task: 1437 / 0x5e31aa0
Jul 07 20:45:51-000264 util-scheduler-8620 DEBUG Adding task: 1440 / 0x5e31aa0
Jul 07 20:45:51-000446 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:51-000707 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:51-000925 util-scheduler-8620 DEBUG Adding task: 1441 / 0x4d5e5d8
Jul 07 20:45:51-001109 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:51-001336 cadet-tun-8620 INFO <=== PONG for D3TJ
Jul 07 20:45:51-001527 cadet-tun-8620 DEBUG   t_decrypt with V7H63X9N
Jul 07 20:45:51-001700 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:51-001867 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:51-005458 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:51-008323 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:51-008544 util-scheduler-8620 DEBUG Canceling task: 1415 / 0x5e2de48
Jul 07 20:45:51-008792 util-scheduler-8620 DEBUG Adding task: 1442 / 0x5e2de48
Jul 07 20:45:51-009019 cadet-tun-8620 DEBUG Tunnel D3TJ estate was CADET_TUNNEL_KEY_PING
Jul 07 20:45:51-009252 cadet-tun-8620 DEBUG Tunnel D3TJ estate is now CADET_TUNNEL_KEY_OK
Jul 07 20:45:51-009463 cadet-tun-8620 DEBUG GCT_send_queued_data on tunnel D3TJ
Jul 07 20:45:51-009670 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:51-009853 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:51-010040 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:51-010224 cadet-tun-8620 DEBUG TTT  tq_head 0x5e34660, tq_tail 0x690d830
Jul 07 20:45:51-010407 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:51-010578 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:51-010801 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:51-010975 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:51-011216 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-011465 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-011678 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:51-011880 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:51-012059 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:51-012242 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:51-012427 cadet-tun-8620 DEBUG TTT  tq_head 0x5e34660, tq_tail 0x690d830
Jul 07 20:45:51-012606 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:51-012776 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:51-012991 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:51-013163 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:51-013420 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-013675 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-013868 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:51-014059 cadet-tun-8620 DEBUG   buffer space: 22
Jul 07 20:45:51-014241 cadet-tun-8620 DEBUG   tq head: 0x5e34660
Jul 07 20:45:51-014419 cadet-tun-8620 DEBUG  sending queued data
Jul 07 20:45:51-014624 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:45:51-014829 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:51-015011 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:51-015203 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:51-015390 cadet-tun-8620 DEBUG TTT  tq_head 0x5e34660, tq_tail 0x690d830
Jul 07 20:45:51-015578 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:51-015759 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:51-015981 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:51-016160 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:51-016402 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-016658 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-016845 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:51-017149 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:51-017350 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:51-017537 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:51-020930 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:51-021680 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:51-021942 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:51-022134 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:45:51-025367 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:51-025612 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:51-025798 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:51-026024 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:51-026205 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:51-026428 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-026628 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:45:51-026920 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (96 bytes)
Jul 07 20:45:51-027121 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:45:51-027308 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:45:51-027490 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:45:51-027665 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:51-027850 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 8
Jul 07 20:45:51-028094 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:51-028309 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:51-028626 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 96)
Jul 07 20:45:51-028828 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:51-029056 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-029269 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:51-029448 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:51-029653 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:51-029887 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-030067 cadet-p2p-8620 DEBUG QQQ  queue length: 9
Jul 07 20:45:51-030244 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-030487 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-030686 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-030865 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-031102 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-031297 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-031476 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-031711 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-031906 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-032085 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-032320 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-032515 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-032694 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-032929 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-033124 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-033324 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-033560 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-033755 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-033933 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-034169 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-034364 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-034541 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-034777 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-034972 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-035149 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-035385 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-035580 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-035758 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-035960 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-036620 cadet-tun-8620 DEBUG  sending queued data
Jul 07 20:45:51-037151 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:45:51-037383 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:51-037568 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:51-037754 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:51-037937 cadet-tun-8620 DEBUG TTT  tq_head 0x690d830, tq_tail 0x690d830
Jul 07 20:45:51-038118 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:51-038291 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:51-038508 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:51-038684 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:51-038922 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-039178 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:51-039373 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:51-039680 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:51-039859 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:51-040056 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:51-043708 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:51-045139 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:51-045472 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:51-045673 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:45:51-049059 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:51-049331 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:51-049553 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:51-049780 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:51-049960 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:51-050182 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-050686 cadet-tun-8620 DEBUG type {         KEEPALIVE}
Jul 07 20:45:51-050975 cadet-con-8620 INFO --> {         ENCRYPTED} ({         KEEPALIVE} 0) on connection 1KSG9GE2 (->D3TJ) (84 bytes)
Jul 07 20:45:51-051179 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:45:51-051362 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:45:51-051540 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:45:51-051715 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:51-051894 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 9
Jul 07 20:45:51-052134 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:51-052346 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:51-052665 cadet-p2p-8620 INFO que {         ENCRYPTED} ({         KEEPALIVE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 84)
Jul 07 20:45:51-052867 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:51-053096 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-053305 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:51-053483 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:51-053690 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:51-053896 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-055571 cadet-p2p-8620 DEBUG QQQ  queue length: 10
Jul 07 20:45:51-055773 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-056030 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-056237 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-056423 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-056707 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-056909 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-057095 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-057375 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-057615 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-057799 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-058047 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-058250 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-058433 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-058674 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-058871 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-059050 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-059285 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-059480 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-059659 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-059895 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-060091 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-060269 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-060504 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-060700 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-060878 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-061336 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-061537 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-061717 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-061953 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-062174 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:51-062353 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:51-062558 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-062775 cadet-tun-8620 DEBUG GCT_send_queued_data end
Jul 07 20:45:51-063005 util-scheduler-8620 DEBUG Adding task: 1443 / 0x4662248
Jul 07 20:45:51-063289 util-scheduler-8620 DEBUG Checking readiness of task: 1441 / 0x4d5e5d8
Jul 07 20:45:51-063491 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-063684 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-063876 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-064068 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-064260 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-064451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-064641 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-064838 util-scheduler-8620 DEBUG Running task: 1441 / 0x4d5e5d8
Jul 07 20:45:51-065027 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:51-065228 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-065404 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-065640 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:51-065950 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:51-066165 util-scheduler-8620 DEBUG Running task: 1443 / 0x4662248
Jul 07 20:45:51-066360 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-066564 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-066785 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-066995 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-067207 util-scheduler-8620 DEBUG Adding task: 1444 / 0x46620a0
Jul 07 20:45:51-067419 util-scheduler-8620 DEBUG Adding task: 1445 / 0x4662248
Jul 07 20:45:51-067659 util-scheduler-8620 DEBUG Checking readiness of task: 1444 / 0x46620a0
Jul 07 20:45:51-067855 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-068048 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-068238 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-068429 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-068619 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-068811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-069002 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-069232 util-scheduler-8620 DEBUG Running task: 1444 / 0x46620a0
Jul 07 20:45:51-069426 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-069611 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-069793 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-069992 util-scheduler-8620 DEBUG Canceling task: 1405 / 0x5e2b838
Jul 07 20:45:51-070238 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 196 bytes.
Jul 07 20:45:51-070565 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:51-070811 cadet-p2p-8620 DEBUG Checking 0x70052b0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-071047 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:51-071227 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:51-071420 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:51-071713 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 196)
Jul 07 20:45:51-071911 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:51-072094 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:51-072308 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:51-072501 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 10
Jul 07 20:45:51-072683 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:51-072873 util-scheduler-8620 DEBUG Canceling task: 1401 / 0x5e31aa0
Jul 07 20:45:51-073092 util-scheduler-8620 DEBUG Adding task: 1446 / 0x5e31aa0
Jul 07 20:45:51-073371 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:51-073545 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:51-073768 cadet-p2p-8620 DEBUG Checking 0x700c2d8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-074011 cadet-p2p-8620 DEBUG Checking 0x700c2d8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-074192 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:51-074403 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `D3TJ'
Jul 07 20:45:51-074621 util-scheduler-8620 DEBUG Adding task: 1447 / 0x5e2b838
Jul 07 20:45:51-074803 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:51-074981 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:51-075183 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-075361 cadet-p2p-8620 DEBUG QQQ  queue length: 9
Jul 07 20:45:51-075537 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-075780 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-075976 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-076155 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-076389 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-076587 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-076766 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-077000 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-077217 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-077410 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-077646 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-077841 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-078019 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-078254 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-078450 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-078628 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-078864 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-079059 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-079236 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-079472 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-079666 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-079843 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-080077 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-080274 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-080451 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-080686 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-080881 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:51-081059 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:51-081278 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-081487 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 196 bytes.
Jul 07 20:45:51-081674 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:51-081882 util-scheduler-8620 DEBUG Adding task: 1448 / 0x5e2b838
Jul 07 20:45:51-082104 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-082304 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-082513 util-scheduler-8620 DEBUG Adding task: 1449 / 0x46620a0
Jul 07 20:45:51-082736 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:51-085510 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-085754 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-085971 util-scheduler-8620 DEBUG Running task: 1445 / 0x4662248
Jul 07 20:45:51-086167 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-086369 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-086599 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:51-086784 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:51-086966 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-087190 util-scheduler-8620 DEBUG Adding task: 1450 / 0x46620a0
Jul 07 20:45:51-087465 util-scheduler-8620 DEBUG Checking readiness of task: 1450 / 0x46620a0
Jul 07 20:45:51-087669 util-scheduler-8620 DEBUG Checking readiness of task: 1449 / 0x46620a0
Jul 07 20:45:51-087866 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-088063 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-088260 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-088452 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-088643 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-088834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-089026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-089242 util-scheduler-8620 DEBUG Running task: 1449 / 0x46620a0
Jul 07 20:45:51-089432 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-089611 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-089786 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-089966 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-090189 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-090391 util-scheduler-8620 DEBUG Adding task: 1451 / 0x46620a0
Jul 07 20:45:51-090592 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-090906 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-091103 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-091302 util-scheduler-8620 DEBUG Running task: 1447 / 0x5e2b838
Jul 07 20:45:51-091498 util-scheduler-8620 DEBUG Canceling task: 1448 / 0x5e2b838
Jul 07 20:45:51-091720 util-scheduler-8620 DEBUG Adding task: 1452 / 0x5e2b838
Jul 07 20:45:51-091943 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-092122 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:45:51-092360 util-scheduler-8620 DEBUG Checking readiness of task: 1451 / 0x46620a0
Jul 07 20:45:51-092555 util-scheduler-8620 DEBUG Checking readiness of task: 1450 / 0x46620a0
Jul 07 20:45:51-092747 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-092939 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-093130 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-093348 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-093539 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-093730 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-093919 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-094112 util-scheduler-8620 DEBUG Running task: 1450 / 0x46620a0
Jul 07 20:45:51-094521 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-094780 util-scheduler-8620 DEBUG Adding task: 1453 / 0x4662248
Jul 07 20:45:51-094992 util-scheduler-8620 DEBUG Running task: 1451 / 0x46620a0
Jul 07 20:45:51-095179 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-095355 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-095526 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-095703 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-095912 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-096110 util-scheduler-8620 DEBUG Adding task: 1454 / 0x46620a0
Jul 07 20:45:51-096308 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-096609 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-096806 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-097043 util-scheduler-8620 DEBUG Checking readiness of task: 1454 / 0x46620a0
Jul 07 20:45:51-097259 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-097453 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-097645 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-097836 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-098027 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-098216 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-098407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-098601 util-scheduler-8620 DEBUG Running task: 1454 / 0x46620a0
Jul 07 20:45:51-098789 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-098967 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-099142 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-099329 util-scheduler-8620 DEBUG Canceling task: 1427 / 0x4d5c9e8
Jul 07 20:45:51-099561 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:45:51-099782 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:51-100022 cadet-p2p-8620 DEBUG Checking 0x49e7870 towards HS92G30M (->KNAS)
Jul 07 20:45:51-100257 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:51-100435 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:51-100625 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:51-100893 cadet-p2p-8620 INFO snd {               ACK} ( 83) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:51-101089 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:51-101305 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:51-101496 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:51-101671 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:51-101855 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:51-102029 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:51-102211 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:51-102410 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:51-102586 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:51-102762 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:51-102964 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:51-103176 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:51-103370 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:51-103552 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-103750 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:51-104984 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-105280 util-scheduler-8620 DEBUG Running task: 1453 / 0x4662248
Jul 07 20:45:51-105580 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-105828 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-106564 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-106768 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-106993 util-scheduler-8620 DEBUG Adding task: 1455 / 0x46620a0
Jul 07 20:45:51-107263 util-scheduler-8620 DEBUG Checking readiness of task: 1455 / 0x46620a0
Jul 07 20:45:51-107464 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-107662 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-107858 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-108052 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-108242 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-108512 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-108708 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-108903 util-scheduler-8620 DEBUG Running task: 1455 / 0x46620a0
Jul 07 20:45:51-109340 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-109585 util-scheduler-8620 DEBUG Adding task: 1456 / 0x4662248
Jul 07 20:45:51-109843 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-110037 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-110226 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-110415 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-110603 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-110794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-110982 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-111170 util-scheduler-8620 DEBUG Running task: 1456 / 0x4662248
Jul 07 20:45:51-111358 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-111553 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-111769 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-111972 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-112175 util-scheduler-8620 DEBUG Adding task: 1457 / 0x46620a0
Jul 07 20:45:51-112360 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-112559 util-scheduler-8620 DEBUG Adding task: 1458 / 0x46620a0
Jul 07 20:45:51-112799 util-scheduler-8620 DEBUG Checking readiness of task: 1458 / 0x46620a0
Jul 07 20:45:51-112990 util-scheduler-8620 DEBUG Checking readiness of task: 1457 / 0x46620a0
Jul 07 20:45:51-113181 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-113391 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-113579 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-113769 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-113957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-114146 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-114334 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-114523 util-scheduler-8620 DEBUG Running task: 1457 / 0x46620a0
Jul 07 20:45:51-114708 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-114884 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-115055 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-115244 util-scheduler-8620 DEBUG Canceling task: 1452 / 0x5e2b838
Jul 07 20:45:51-115466 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 80 bytes.
Jul 07 20:45:51-115705 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:51-115941 cadet-p2p-8620 DEBUG Checking 0x700c2d8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-116172 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:51-116349 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:51-116538 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:51-116818 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 80)
Jul 07 20:45:51-117011 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:51-117207 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:51-117396 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:51-117583 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 9
Jul 07 20:45:51-117760 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:51-117944 util-scheduler-8620 DEBUG Canceling task: 1446 / 0x5e31aa0
Jul 07 20:45:51-118154 util-scheduler-8620 DEBUG Adding task: 1459 / 0x5e31aa0
Jul 07 20:45:51-118403 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:51-118572 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:51-118790 cadet-p2p-8620 DEBUG Checking 0x4967670 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-119027 cadet-p2p-8620 DEBUG Checking 0x4967670 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-119204 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:51-119409 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `D3TJ'
Jul 07 20:45:51-119625 util-scheduler-8620 DEBUG Adding task: 1460 / 0x5e2b838
Jul 07 20:45:51-119805 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:51-119982 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:51-120183 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-120359 cadet-p2p-8620 DEBUG QQQ  queue length: 8
Jul 07 20:45:51-120535 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-120774 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-120974 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-121154 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-121414 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-121613 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-121791 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-122037 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-122235 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-122415 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-122658 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-122856 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-123034 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-123277 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-123473 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-123651 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-123887 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-124079 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-124267 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-124500 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-124694 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-124870 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-125101 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-125319 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:51-125495 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:51-125693 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-125897 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 80 bytes.
Jul 07 20:45:51-126081 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:51-126318 util-scheduler-8620 DEBUG Adding task: 1461 / 0x5e2b838
Jul 07 20:45:51-126544 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-126741 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-126944 util-scheduler-8620 DEBUG Adding task: 1462 / 0x46620a0
Jul 07 20:45:51-127145 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:51-128626 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-128833 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-129095 util-scheduler-8620 DEBUG Checking readiness of task: 1462 / 0x46620a0
Jul 07 20:45:51-129312 util-scheduler-8620 DEBUG Checking readiness of task: 1458 / 0x46620a0
Jul 07 20:45:51-129502 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-129693 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-129881 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-130069 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-130257 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-130447 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-130635 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-130828 util-scheduler-8620 DEBUG Running task: 1462 / 0x46620a0
Jul 07 20:45:51-131013 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-131190 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-131362 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-131539 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-131736 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-131925 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-132223 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-132431 util-scheduler-8620 DEBUG Running task: 1460 / 0x5e2b838
Jul 07 20:45:51-132625 util-scheduler-8620 DEBUG Canceling task: 1461 / 0x5e2b838
Jul 07 20:45:51-132841 util-scheduler-8620 DEBUG Adding task: 1463 / 0x5e2b838
Jul 07 20:45:51-133058 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-133270 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-133469 util-scheduler-8620 DEBUG Adding task: 1464 / 0x46620a0
Jul 07 20:45:51-133708 util-scheduler-8620 DEBUG Checking readiness of task: 1464 / 0x46620a0
Jul 07 20:45:51-133900 util-scheduler-8620 DEBUG Checking readiness of task: 1458 / 0x46620a0
Jul 07 20:45:51-134090 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-134280 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-134468 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-134655 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-134846 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-135038 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-135230 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-135431 util-scheduler-8620 DEBUG Running task: 1458 / 0x46620a0
Jul 07 20:45:51-135848 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-136096 util-scheduler-8620 DEBUG Adding task: 1465 / 0x4662248
Jul 07 20:45:51-136308 util-scheduler-8620 DEBUG Running task: 1464 / 0x46620a0
Jul 07 20:45:51-136493 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-136693 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-136863 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-137043 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-137262 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-137454 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-137764 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-138027 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-138223 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-138415 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-138606 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-138797 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-138992 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-139188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-139385 util-scheduler-8620 DEBUG Running task: 1465 / 0x4662248
Jul 07 20:45:51-139579 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-139777 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-140006 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-140193 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-140402 util-scheduler-8620 DEBUG Adding task: 1466 / 0x46620a0
Jul 07 20:45:51-140652 util-scheduler-8620 DEBUG Checking readiness of task: 1466 / 0x46620a0
Jul 07 20:45:51-140845 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-141034 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-141246 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-141436 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-141624 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-141814 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-142001 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-142193 util-scheduler-8620 DEBUG Running task: 1466 / 0x46620a0
Jul 07 20:45:51-142595 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-142823 util-scheduler-8620 DEBUG Adding task: 1467 / 0x4662248
Jul 07 20:45:51-143070 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-143261 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-143449 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-143637 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-143825 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-144113 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-144303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-144493 util-scheduler-8620 DEBUG Running task: 1467 / 0x4662248
Jul 07 20:45:51-144681 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-144872 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-145082 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-145372 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-145573 util-scheduler-8620 DEBUG Adding task: 1468 / 0x46620a0
Jul 07 20:45:51-145756 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-145953 util-scheduler-8620 DEBUG Adding task: 1469 / 0x46620a0
Jul 07 20:45:51-146214 util-scheduler-8620 DEBUG Checking readiness of task: 1469 / 0x46620a0
Jul 07 20:45:51-146407 util-scheduler-8620 DEBUG Checking readiness of task: 1468 / 0x46620a0
Jul 07 20:45:51-146601 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-146790 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-146978 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-147167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-147367 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-147555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-147744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-147934 util-scheduler-8620 DEBUG Running task: 1468 / 0x46620a0
Jul 07 20:45:51-148118 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-148292 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-148462 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-148647 util-scheduler-8620 DEBUG Canceling task: 1463 / 0x5e2b838
Jul 07 20:45:51-148871 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 196 bytes.
Jul 07 20:45:51-149087 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:51-149344 cadet-p2p-8620 DEBUG Checking 0x4967670 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-149575 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:51-149752 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:51-149938 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:51-150219 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 196)
Jul 07 20:45:51-150413 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:51-150594 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:51-150784 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:51-150973 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 8
Jul 07 20:45:51-151153 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:51-151340 util-scheduler-8620 DEBUG Canceling task: 1459 / 0x5e31aa0
Jul 07 20:45:51-151554 util-scheduler-8620 DEBUG Adding task: 1470 / 0x5e31aa0
Jul 07 20:45:51-151804 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:51-151977 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:51-152199 cadet-p2p-8620 DEBUG Checking 0x496d8c8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-152439 cadet-p2p-8620 DEBUG Checking 0x496d8c8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-152619 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:51-152825 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `D3TJ'
Jul 07 20:45:51-153040 util-scheduler-8620 DEBUG Adding task: 1471 / 0x5e2b838
Jul 07 20:45:51-153241 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:51-153422 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:51-153632 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-153813 cadet-p2p-8620 DEBUG QQQ  queue length: 7
Jul 07 20:45:51-153990 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-154233 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-154428 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-154603 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-154836 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-155028 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-155208 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-155443 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-155639 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-155816 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-156050 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-156242 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-156441 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-156681 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-156875 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-157052 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-157310 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-157506 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-157684 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-157918 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-158111 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:51-158288 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:51-158487 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-158694 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 196 bytes.
Jul 07 20:45:51-158882 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:51-159097 util-scheduler-8620 DEBUG Adding task: 1472 / 0x5e2b838
Jul 07 20:45:51-159321 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-159521 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-159725 util-scheduler-8620 DEBUG Adding task: 1473 / 0x46620a0
Jul 07 20:45:51-159927 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:51-161576 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-161814 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-162082 util-scheduler-8620 DEBUG Checking readiness of task: 1473 / 0x46620a0
Jul 07 20:45:51-162279 util-scheduler-8620 DEBUG Checking readiness of task: 1469 / 0x46620a0
Jul 07 20:45:51-162469 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-162660 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-162848 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-163038 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-163227 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-163415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-163603 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-163797 util-scheduler-8620 DEBUG Running task: 1473 / 0x46620a0
Jul 07 20:45:51-163981 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-164159 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-164330 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-164508 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-164704 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-164893 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-165215 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-165424 util-scheduler-8620 DEBUG Running task: 1471 / 0x5e2b838
Jul 07 20:45:51-165619 util-scheduler-8620 DEBUG Canceling task: 1472 / 0x5e2b838
Jul 07 20:45:51-165844 util-scheduler-8620 DEBUG Adding task: 1474 / 0x5e2b838
Jul 07 20:45:51-166064 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-166259 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-166459 util-scheduler-8620 DEBUG Adding task: 1475 / 0x46620a0
Jul 07 20:45:51-166702 util-scheduler-8620 DEBUG Checking readiness of task: 1475 / 0x46620a0
Jul 07 20:45:51-166895 util-scheduler-8620 DEBUG Checking readiness of task: 1469 / 0x46620a0
Jul 07 20:45:51-167085 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-167295 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-167484 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-167672 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-167860 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-168048 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-168235 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-168425 util-scheduler-8620 DEBUG Running task: 1469 / 0x46620a0
Jul 07 20:45:51-168828 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-169058 util-scheduler-8620 DEBUG Adding task: 1476 / 0x4662248
Jul 07 20:45:51-169286 util-scheduler-8620 DEBUG Running task: 1475 / 0x46620a0
Jul 07 20:45:51-169472 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-169646 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-169826 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-170002 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-170190 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-170376 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-170673 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-170919 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-171111 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-171300 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-171488 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-171676 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-171864 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-172052 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-172244 util-scheduler-8620 DEBUG Running task: 1476 / 0x4662248
Jul 07 20:45:51-172435 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-172633 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-172852 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-173034 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-173265 util-scheduler-8620 DEBUG Adding task: 1477 / 0x46620a0
Jul 07 20:45:51-173510 util-scheduler-8620 DEBUG Checking readiness of task: 1477 / 0x46620a0
Jul 07 20:45:51-173707 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-173899 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-174090 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-174283 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-174477 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-174667 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-174856 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-175050 util-scheduler-8620 DEBUG Running task: 1477 / 0x46620a0
Jul 07 20:45:51-175452 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:51-175680 util-scheduler-8620 DEBUG Adding task: 1478 / 0x4662248
Jul 07 20:45:51-175934 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-176127 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-176319 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-176533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-176723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-176919 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-177120 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-177337 util-scheduler-8620 DEBUG Running task: 1478 / 0x4662248
Jul 07 20:45:51-177527 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:51-177720 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:51-177937 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:51-178136 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-178335 util-scheduler-8620 DEBUG Adding task: 1479 / 0x46620a0
Jul 07 20:45:51-178519 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:51-178717 util-scheduler-8620 DEBUG Adding task: 1480 / 0x46620a0
Jul 07 20:45:51-178964 util-scheduler-8620 DEBUG Checking readiness of task: 1480 / 0x46620a0
Jul 07 20:45:51-179156 util-scheduler-8620 DEBUG Checking readiness of task: 1479 / 0x46620a0
Jul 07 20:45:51-179348 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-179537 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-179725 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-179913 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-180102 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-180290 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-180478 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-180668 util-scheduler-8620 DEBUG Running task: 1479 / 0x46620a0
Jul 07 20:45:51-180856 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-181612 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-181848 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-182045 util-scheduler-8620 DEBUG Canceling task: 1474 / 0x5e2b838
Jul 07 20:45:51-182278 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 80 bytes.
Jul 07 20:45:51-182498 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:51-182738 cadet-p2p-8620 DEBUG Checking 0x496d8c8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-182973 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:51-183152 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:51-183346 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:51-183634 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 80)
Jul 07 20:45:51-183829 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:51-184008 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:51-184195 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:51-184382 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 7
Jul 07 20:45:51-184559 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:51-184745 util-scheduler-8620 DEBUG Canceling task: 1470 / 0x5e31aa0
Jul 07 20:45:51-184960 util-scheduler-8620 DEBUG Adding task: 1481 / 0x5e31aa0
Jul 07 20:45:51-185233 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:51-185406 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:51-185626 cadet-p2p-8620 DEBUG Checking 0x49c05c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-185864 cadet-p2p-8620 DEBUG Checking 0x49c05c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-186044 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:51-186250 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `D3TJ'
Jul 07 20:45:51-186470 util-scheduler-8620 DEBUG Adding task: 1482 / 0x5e2b838
Jul 07 20:45:51-186659 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:51-186839 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:51-187079 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:51-187506 cadet-p2p-8620 DEBUG QQQ  queue length: 6
Jul 07 20:45:51-187690 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:51-187936 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-188134 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:45:51-188311 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:45:51-188544 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-188738 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:51-188915 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:51-189147 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-189364 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-189541 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-189773 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-190075 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:51-190260 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:51-190500 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-190694 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:51-190870 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:51-191103 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:51-191298 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:51-191477 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:51-191677 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:51-191888 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 80 bytes.
Jul 07 20:45:51-192093 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:51-192312 util-scheduler-8620 DEBUG Adding task: 1483 / 0x5e2b838
Jul 07 20:45:51-192537 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-192738 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-192945 util-scheduler-8620 DEBUG Adding task: 1484 / 0x46620a0
Jul 07 20:45:51-193148 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:51-193420 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-193619 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:51-193886 util-scheduler-8620 DEBUG Checking readiness of task: 1484 / 0x46620a0
Jul 07 20:45:51-194084 util-scheduler-8620 DEBUG Checking readiness of task: 1480 / 0x46620a0
Jul 07 20:45:51-194277 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-194474 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-194663 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-194851 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-195039 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-195229 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-195416 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-195608 util-scheduler-8620 DEBUG Running task: 1484 / 0x46620a0
Jul 07 20:45:51-195797 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-195975 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-196147 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-196325 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-196523 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-196711 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-196944 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:51-197176 util-scheduler-8620 DEBUG Running task: 1482 / 0x5e2b838
Jul 07 20:45:51-197396 util-scheduler-8620 DEBUG Canceling task: 1483 / 0x5e2b838
Jul 07 20:45:51-197617 util-scheduler-8620 DEBUG Adding task: 1485 / 0x5e2b838
Jul 07 20:45:51-197840 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:51-198045 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:51-198251 util-scheduler-8620 DEBUG Adding task: 1486 / 0x46620a0
Jul 07 20:45:51-198498 util-scheduler-8620 DEBUG Checking readiness of task: 1486 / 0x46620a0
Jul 07 20:45:51-198692 util-scheduler-8620 DEBUG Checking readiness of task: 1480 / 0x46620a0
Jul 07 20:45:51-198881 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:51-199074 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:51-199264 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:51-199454 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:51-199646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:51-199837 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:51-200029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:51-200224 util-scheduler-8620 DEBUG Running task: 1486 / 0x46620a0
Jul 07 20:45:51-200418 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:51-200607 util-8620 DEBUG process_notify is running
Jul 07 20:45:51-200782 util-8620 DEBUG client_notify is running
Jul 07 20:45:51-200965 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:51-201174 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:51-201404 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:51-201652 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:52-031311 util-scheduler-8620 DEBUG Checking readiness of task: 1480 / 0x46620a0
Jul 07 20:45:52-031701 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:52-031900 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:52-032093 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:52-032285 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:52-032477 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:52-032669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:52-032860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:52-033057 util-scheduler-8620 DEBUG Running task: 1480 / 0x46620a0
Jul 07 20:45:52-033503 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:52-033760 util-scheduler-8620 DEBUG Adding task: 1487 / 0x4662248
Jul 07 20:45:52-034040 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:52-034239 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:52-034435 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:52-034631 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:52-034826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:52-035019 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:52-035220 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:52-035421 util-scheduler-8620 DEBUG Running task: 1487 / 0x4662248
Jul 07 20:45:52-035623 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:52-035833 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:52-036120 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:52-036341 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:52-036561 util-scheduler-8620 DEBUG Adding task: 1488 / 0x46620a0
Jul 07 20:45:52-036761 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:52-036981 util-scheduler-8620 DEBUG Adding task: 1489 / 0x46620a0
Jul 07 20:45:52-039544 util-scheduler-8620 DEBUG Checking readiness of task: 1489 / 0x46620a0
Jul 07 20:45:52-040589 util-scheduler-8620 DEBUG Checking readiness of task: 1488 / 0x46620a0
Jul 07 20:45:52-040811 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:52-041008 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:52-041224 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:52-041418 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:52-041610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:52-041803 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:52-041993 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:52-042191 util-scheduler-8620 DEBUG Running task: 1488 / 0x46620a0
Jul 07 20:45:52-042379 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:52-042560 util-8620 DEBUG process_notify is running
Jul 07 20:45:52-042734 util-8620 DEBUG client_notify is running
Jul 07 20:45:52-042930 util-scheduler-8620 DEBUG Canceling task: 1413 / 0x4d6ff98
Jul 07 20:45:52-043177 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:45:52-043400 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:52-043642 cadet-p2p-8620 DEBUG Checking 0x49beca0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:52-043877 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:52-044056 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:52-044247 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:45:52-044521 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:45:52-044717 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:52-044900 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:52-045088 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:45:52-045285 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:52-045455 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:45:52-045677 util-scheduler-8620 DEBUG Adding task: 1490 / 0x4d707d4
Jul 07 20:45:52-045861 cadet-con-8620 DEBUG  task 1490
Jul 07 20:45:52-046048 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:52-046223 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:52-046446 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:52-046693 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:52-046882 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:52-047058 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:52-047289 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:52-047520 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:52-047702 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:52-047876 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:52-048047 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:52-048246 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:52-048422 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:52-048598 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:52-048835 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:52-049032 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:52-049229 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:52-049432 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:52-049638 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:45:52-049849 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:52-050032 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:52-050225 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:52-050960 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-140367 util-scheduler-8620 DEBUG Checking readiness of task: 1489 / 0x46620a0
Jul 07 20:45:53-140751 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:53-140948 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-141144 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-141365 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-141556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-141745 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-141934 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-142130 util-scheduler-8620 DEBUG Running task: 1489 / 0x46620a0
Jul 07 20:45:53-142563 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-142833 util-scheduler-8620 DEBUG Adding task: 1491 / 0x4662248
Jul 07 20:45:53-143121 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:53-143317 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-143509 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-143699 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-143895 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-144088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-144283 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-144475 util-scheduler-8620 DEBUG Running task: 1491 / 0x4662248
Jul 07 20:45:53-144667 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:53-144873 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:53-145112 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:53-145407 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:53-145649 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:53-145879 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:53-146086 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:53-146334 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:53-146545 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:53-146732 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:53-146925 util-scheduler-8620 DEBUG Canceling task: 1417 / 0x4d707d0
Jul 07 20:45:53-147155 util-scheduler-8620 DEBUG Adding task: 1492 / 0x4d707d0
Jul 07 20:45:53-147334 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:53-147595 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:53-147810 util-scheduler-8620 DEBUG Adding task: 1493 / 0x4d5e5d8
Jul 07 20:45:53-147994 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:53-148192 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:53-148408 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-148613 util-scheduler-8620 DEBUG Adding task: 1494 / 0x46620a0
Jul 07 20:45:53-148870 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-149064 util-scheduler-8620 DEBUG Checking readiness of task: 1493 / 0x4d5e5d8
Jul 07 20:45:53-149278 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:53-149469 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-149689 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-149878 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-150066 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-150255 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-150442 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-150634 util-scheduler-8620 DEBUG Running task: 1493 / 0x4d5e5d8
Jul 07 20:45:53-150819 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:53-150996 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-151171 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-151409 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:53-151616 util-scheduler-8620 DEBUG Adding task: 1495 / 0x4d5e5d8
Jul 07 20:45:53-151817 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:53-152122 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:53-152321 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:53-152564 util-scheduler-8620 DEBUG Checking readiness of task: 1495 / 0x4d5e5d8
Jul 07 20:45:53-152757 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-152947 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:53-153136 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-153347 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-153535 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-153723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-153913 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-154100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-154291 util-scheduler-8620 DEBUG Running task: 1495 / 0x4d5e5d8
Jul 07 20:45:53-154475 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:53-154648 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-154818 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-155028 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:53-155313 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:53-205710 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-206061 util-scheduler-8620 DEBUG Checking readiness of task: 1208 / 0x4663d68
Jul 07 20:45:53-206260 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-206452 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-206642 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-206834 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-207028 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-207219 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-207414 util-scheduler-8620 DEBUG Running task: 1208 / 0x4663d68
Jul 07 20:45:53-207835 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:53-208087 util-scheduler-8620 DEBUG Adding task: 1496 / 0x4663f10
Jul 07 20:45:53-208362 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-208633 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-208828 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-209074 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-209335 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-209529 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-209718 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-209907 util-scheduler-8620 DEBUG Running task: 1496 / 0x4663f10
Jul 07 20:45:53-210103 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:53-210299 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-210515 util-scheduler-8620 DEBUG Adding task: 1497 / 0x4663d68
Jul 07 20:45:53-210701 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:53-210928 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `TZQE' with quota 14036
Jul 07 20:45:53-212023 util-bandwidth-8620 DEBUG Tracker 0x4d73060 bandwidth changed to 14036 Bps
Jul 07 20:45:53-212308 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 13651 Bps, last update was 107 s ago
Jul 07 20:45:53-212546 util-scheduler-8620 DEBUG Adding task: 1498 / 0x4d73060
Jul 07 20:45:53-212794 util-scheduler-8620 DEBUG Checking readiness of task: 1497 / 0x4663d68
Jul 07 20:45:53-212990 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-213180 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-213397 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-213586 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-213776 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-213965 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-214154 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-214344 util-scheduler-8620 DEBUG Running task: 1497 / 0x4663d68
Jul 07 20:45:53-214747 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:53-214972 util-scheduler-8620 DEBUG Adding task: 1499 / 0x4663f10
Jul 07 20:45:53-215220 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-215413 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-215603 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-215791 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-215981 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-216169 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-216358 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-216546 util-scheduler-8620 DEBUG Running task: 1499 / 0x4663f10
Jul 07 20:45:53-216762 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:53-216952 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-217155 util-scheduler-8620 DEBUG Adding task: 1500 / 0x4663d68
Jul 07 20:45:53-217363 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:53-217574 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `KNAS' with quota 24114
Jul 07 20:45:53-217765 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 bandwidth changed to 24114 Bps
Jul 07 20:45:53-218013 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 updated, have 23365 Bps, last update was 107 s ago
Jul 07 20:45:53-218233 util-scheduler-8620 DEBUG Adding task: 1501 / 0x4d6c380
Jul 07 20:45:53-349712 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-350106 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-352228 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-352434 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-352628 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-352843 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-353040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-353255 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-353451 util-scheduler-8620 DEBUG Running task: 1498 / 0x4d73060
Jul 07 20:45:53-373474 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-373720 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-373915 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-374106 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-374296 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-374486 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-374678 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-374867 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-375070 util-scheduler-8620 DEBUG Running task: 1501 / 0x4d6c380
Jul 07 20:45:53-712899 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-713304 util-scheduler-8620 DEBUG Checking readiness of task: 1494 / 0x46620a0
Jul 07 20:45:53-713504 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-713698 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-713889 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-714080 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-714271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-714461 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-714657 util-scheduler-8620 DEBUG Running task: 1494 / 0x46620a0
Jul 07 20:45:53-715077 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-715334 util-scheduler-8620 DEBUG Adding task: 1502 / 0x4662248
Jul 07 20:45:53-715611 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-715806 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-715996 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-716185 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-716375 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-716563 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-716755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-716945 util-scheduler-8620 DEBUG Running task: 1502 / 0x4662248
Jul 07 20:45:53-717135 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:53-718166 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:53-718404 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:53-718615 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-718825 util-scheduler-8620 DEBUG Adding task: 1503 / 0x46620a0
Jul 07 20:45:53-719015 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-719288 util-scheduler-8620 DEBUG Adding task: 1504 / 0x46620a0
Jul 07 20:45:53-719539 util-scheduler-8620 DEBUG Checking readiness of task: 1504 / 0x46620a0
Jul 07 20:45:53-719738 util-scheduler-8620 DEBUG Checking readiness of task: 1503 / 0x46620a0
Jul 07 20:45:53-719931 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-720120 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-720309 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-720497 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-720716 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-720905 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-721094 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-721307 util-scheduler-8620 DEBUG Running task: 1503 / 0x46620a0
Jul 07 20:45:53-721494 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-721672 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-721845 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-722036 util-scheduler-8620 DEBUG Canceling task: 1485 / 0x5e2b838
Jul 07 20:45:53-722263 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 196 bytes.
Jul 07 20:45:53-722484 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:53-722724 cadet-p2p-8620 DEBUG Checking 0x49c05c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-722958 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:53-723135 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:45:53-723340 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:53-723626 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 196)
Jul 07 20:45:53-723821 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:53-724001 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:53-724188 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:53-724376 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 6
Jul 07 20:45:53-724554 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:53-724737 util-scheduler-8620 DEBUG Canceling task: 1481 / 0x5e31aa0
Jul 07 20:45:53-724951 util-scheduler-8620 DEBUG Adding task: 1505 / 0x5e31aa0
Jul 07 20:45:53-725228 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:53-725401 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:53-725818 cadet-p2p-8620 DEBUG Checking 0x49cf548 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-726063 cadet-p2p-8620 DEBUG Checking 0x49cf548 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-726243 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:53-726448 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `D3TJ'
Jul 07 20:45:53-726663 util-scheduler-8620 DEBUG Adding task: 1506 / 0x5e2b838
Jul 07 20:45:53-726842 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:53-727018 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:45:53-727216 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:53-727391 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:53-727565 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:53-727802 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-727998 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:45:53-728174 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:45:53-728407 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-728602 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:53-728778 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:53-729010 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-729228 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:53-729405 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:53-729641 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-729835 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:53-730011 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:53-730244 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-730437 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:53-730614 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:53-730811 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:53-731016 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 196 bytes.
Jul 07 20:45:53-731200 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:45:53-731419 util-scheduler-8620 DEBUG Adding task: 1507 / 0x5e2b838
Jul 07 20:45:53-731640 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-731897 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-732102 util-scheduler-8620 DEBUG Adding task: 1508 / 0x46620a0
Jul 07 20:45:53-732303 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:45:53-734746 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-735526 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:53-735782 util-scheduler-8620 DEBUG Checking readiness of task: 1508 / 0x46620a0
Jul 07 20:45:53-735978 util-scheduler-8620 DEBUG Checking readiness of task: 1504 / 0x46620a0
Jul 07 20:45:53-736170 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-736360 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-736551 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-736740 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-736929 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-737117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-737334 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-737525 util-scheduler-8620 DEBUG Running task: 1508 / 0x46620a0
Jul 07 20:45:53-737710 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-737886 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-738058 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-738298 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-738497 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-738687 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-738996 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-739209 util-scheduler-8620 DEBUG Running task: 1506 / 0x5e2b838
Jul 07 20:45:53-739407 util-scheduler-8620 DEBUG Canceling task: 1507 / 0x5e2b838
Jul 07 20:45:53-739628 util-scheduler-8620 DEBUG Adding task: 1509 / 0x5e2b838
Jul 07 20:45:53-739847 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-740042 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-740241 util-scheduler-8620 DEBUG Adding task: 1510 / 0x46620a0
Jul 07 20:45:53-740486 util-scheduler-8620 DEBUG Checking readiness of task: 1510 / 0x46620a0
Jul 07 20:45:53-740679 util-scheduler-8620 DEBUG Checking readiness of task: 1504 / 0x46620a0
Jul 07 20:45:53-740871 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-741217 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-741414 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-741604 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-741794 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-741982 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-742175 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-742365 util-scheduler-8620 DEBUG Running task: 1504 / 0x46620a0
Jul 07 20:45:53-742768 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-742996 util-scheduler-8620 DEBUG Adding task: 1511 / 0x4662248
Jul 07 20:45:53-743207 util-scheduler-8620 DEBUG Running task: 1510 / 0x46620a0
Jul 07 20:45:53-743392 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-743585 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-743756 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-743932 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-744123 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-744312 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-744622 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-744931 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-745125 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-745341 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-745532 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-745722 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-745911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-746100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-746289 util-scheduler-8620 DEBUG Running task: 1511 / 0x4662248
Jul 07 20:45:53-746479 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:53-746672 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:53-746886 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:53-747068 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-747270 util-scheduler-8620 DEBUG Adding task: 1512 / 0x46620a0
Jul 07 20:45:53-747511 util-scheduler-8620 DEBUG Checking readiness of task: 1512 / 0x46620a0
Jul 07 20:45:53-747714 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-747905 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-748094 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-748283 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-748472 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-748660 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-748848 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-749037 util-scheduler-8620 DEBUG Running task: 1512 / 0x46620a0
Jul 07 20:45:53-753133 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-753451 util-scheduler-8620 DEBUG Adding task: 1513 / 0x4662248
Jul 07 20:45:53-753707 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-753901 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-754092 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-754281 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-754471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-754661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-754850 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-755041 util-scheduler-8620 DEBUG Running task: 1513 / 0x4662248
Jul 07 20:45:53-755229 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:53-755422 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:53-755633 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:53-755831 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-756030 util-scheduler-8620 DEBUG Adding task: 1514 / 0x46620a0
Jul 07 20:45:53-756215 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-756412 util-scheduler-8620 DEBUG Adding task: 1515 / 0x46620a0
Jul 07 20:45:53-756668 util-scheduler-8620 DEBUG Checking readiness of task: 1515 / 0x46620a0
Jul 07 20:45:53-756861 util-scheduler-8620 DEBUG Checking readiness of task: 1514 / 0x46620a0
Jul 07 20:45:53-757052 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-757262 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-757452 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-757642 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-757894 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-758084 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-758272 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-758464 util-scheduler-8620 DEBUG Running task: 1514 / 0x46620a0
Jul 07 20:45:53-758647 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-758824 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-758992 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-759176 util-scheduler-8620 DEBUG Canceling task: 1509 / 0x5e2b838
Jul 07 20:45:53-759399 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 80 bytes.
Jul 07 20:45:53-759616 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:53-759915 cadet-p2p-8620 DEBUG Checking 0x49cf548 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-760149 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:53-760327 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:45:53-760514 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:53-760792 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 80)
Jul 07 20:45:53-760986 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:53-761165 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:53-761373 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:53-761560 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 5
Jul 07 20:45:53-761737 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:53-761921 util-scheduler-8620 DEBUG Canceling task: 1505 / 0x5e31aa0
Jul 07 20:45:53-762131 util-scheduler-8620 DEBUG Adding task: 1516 / 0x5e31aa0
Jul 07 20:45:53-762375 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:53-762545 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:53-762764 cadet-p2p-8620 DEBUG Checking 0x49301e8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-763002 cadet-p2p-8620 DEBUG Checking 0x49301e8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-763181 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:53-763383 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:45:53-763593 util-scheduler-8620 DEBUG Adding task: 1517 / 0x5e2b838
Jul 07 20:45:53-763771 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:53-763946 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:45:53-764143 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:53-764318 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:53-764491 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:53-764728 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-764922 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:53-765098 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:53-765357 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-765550 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:53-765725 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:53-765958 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-766151 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:53-766328 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:53-766560 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-766769 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:53-766946 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:53-767142 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:53-767347 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 80 bytes.
Jul 07 20:45:53-767529 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:45:53-767729 util-scheduler-8620 DEBUG Adding task: 1518 / 0x5e2b838
Jul 07 20:45:53-767944 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-768136 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-768336 util-scheduler-8620 DEBUG Adding task: 1519 / 0x46620a0
Jul 07 20:45:53-768533 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:45:53-770259 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-770821 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:53-771066 util-scheduler-8620 DEBUG Checking readiness of task: 1519 / 0x46620a0
Jul 07 20:45:53-771261 util-scheduler-8620 DEBUG Checking readiness of task: 1515 / 0x46620a0
Jul 07 20:45:53-771452 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-771643 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-771833 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-772021 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-772214 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-772402 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-772591 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-772783 util-scheduler-8620 DEBUG Running task: 1519 / 0x46620a0
Jul 07 20:45:53-772967 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-773143 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-773414 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-773649 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-773844 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-774035 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-774346 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-774567 util-scheduler-8620 DEBUG Running task: 1517 / 0x5e2b838
Jul 07 20:45:53-774761 util-scheduler-8620 DEBUG Canceling task: 1518 / 0x5e2b838
Jul 07 20:45:53-774975 util-scheduler-8620 DEBUG Adding task: 1520 / 0x5e2b838
Jul 07 20:45:53-775191 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-775386 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-775582 util-scheduler-8620 DEBUG Adding task: 1521 / 0x46620a0
Jul 07 20:45:53-775822 util-scheduler-8620 DEBUG Checking readiness of task: 1521 / 0x46620a0
Jul 07 20:45:53-776015 util-scheduler-8620 DEBUG Checking readiness of task: 1515 / 0x46620a0
Jul 07 20:45:53-776206 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-776397 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-776586 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-776777 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-776965 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-777153 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-777364 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-777556 util-scheduler-8620 DEBUG Running task: 1515 / 0x46620a0
Jul 07 20:45:53-777955 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-778197 util-scheduler-8620 DEBUG Adding task: 1522 / 0x4662248
Jul 07 20:45:53-778408 util-scheduler-8620 DEBUG Running task: 1521 / 0x46620a0
Jul 07 20:45:53-778592 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-778768 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-778938 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-779115 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-779304 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-779492 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-779792 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-780039 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-780233 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-780422 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-780613 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-780802 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-781265 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-781580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-781775 util-scheduler-8620 DEBUG Running task: 1522 / 0x4662248
Jul 07 20:45:53-782158 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:53-782423 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:53-782638 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:53-782891 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-783093 util-scheduler-8620 DEBUG Adding task: 1523 / 0x46620a0
Jul 07 20:45:53-783525 util-scheduler-8620 DEBUG Checking readiness of task: 1523 / 0x46620a0
Jul 07 20:45:53-783721 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-783912 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-784102 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-784292 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-784480 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-784669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-784860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-785049 util-scheduler-8620 DEBUG Running task: 1523 / 0x46620a0
Jul 07 20:45:53-785473 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-785698 util-scheduler-8620 DEBUG Adding task: 1524 / 0x4662248
Jul 07 20:45:53-785943 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-786137 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-786388 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-786689 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-787366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-787559 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-787750 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-787940 util-scheduler-8620 DEBUG Running task: 1524 / 0x4662248
Jul 07 20:45:53-788131 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:53-788322 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:53-788535 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:53-788745 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-788943 util-scheduler-8620 DEBUG Adding task: 1525 / 0x46620a0
Jul 07 20:45:53-789129 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:53-789352 util-scheduler-8620 DEBUG Adding task: 1526 / 0x46620a0
Jul 07 20:45:53-789592 util-scheduler-8620 DEBUG Checking readiness of task: 1526 / 0x46620a0
Jul 07 20:45:53-789788 util-scheduler-8620 DEBUG Checking readiness of task: 1525 / 0x46620a0
Jul 07 20:45:53-789980 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-790170 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-790361 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-790550 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-790738 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-790928 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-791117 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-791309 util-scheduler-8620 DEBUG Running task: 1525 / 0x46620a0
Jul 07 20:45:53-791493 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-791668 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-791837 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-792019 util-scheduler-8620 DEBUG Canceling task: 1520 / 0x5e2b838
Jul 07 20:45:53-792237 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:45:53-792452 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:53-792683 cadet-p2p-8620 DEBUG Checking 0x49301e8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-792913 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:53-793089 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:53-793298 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:53-793575 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 48)
Jul 07 20:45:53-793768 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:53-793944 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:53-794130 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:53-794315 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 4
Jul 07 20:45:53-794491 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:53-794674 util-scheduler-8620 DEBUG Canceling task: 1516 / 0x5e31aa0
Jul 07 20:45:53-794884 util-scheduler-8620 DEBUG Adding task: 1527 / 0x5e31aa0
Jul 07 20:45:53-795125 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:53-795295 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:53-795514 cadet-p2p-8620 DEBUG Checking 0x4701128 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-795754 cadet-p2p-8620 DEBUG Checking 0x4701128 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-795932 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:53-796135 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:45:53-796345 util-scheduler-8620 DEBUG Adding task: 1528 / 0x5e2b838
Jul 07 20:45:53-796522 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:53-796699 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:53-796896 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:53-797071 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:53-797274 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:53-797520 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-797715 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:53-797892 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:53-798126 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-798319 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:53-798496 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:53-798728 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-798937 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:53-799114 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:53-799313 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:53-799515 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 48 bytes.
Jul 07 20:45:53-799701 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:53-799901 util-scheduler-8620 DEBUG Adding task: 1529 / 0x5e2b838
Jul 07 20:45:53-800116 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-800309 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-800509 util-scheduler-8620 DEBUG Adding task: 1530 / 0x46620a0
Jul 07 20:45:53-800707 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:53-801048 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-801271 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:53-801511 util-scheduler-8620 DEBUG Checking readiness of task: 1530 / 0x46620a0
Jul 07 20:45:53-801705 util-scheduler-8620 DEBUG Checking readiness of task: 1526 / 0x46620a0
Jul 07 20:45:53-801895 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-802085 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-802277 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-802467 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-802656 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-802845 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-803034 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-803223 util-scheduler-8620 DEBUG Running task: 1530 / 0x46620a0
Jul 07 20:45:53-803409 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-803585 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-803756 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-803932 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-804124 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-804312 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-804606 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-804814 util-scheduler-8620 DEBUG Running task: 1528 / 0x5e2b838
Jul 07 20:45:53-805005 util-scheduler-8620 DEBUG Canceling task: 1529 / 0x5e2b838
Jul 07 20:45:53-805240 util-scheduler-8620 DEBUG Adding task: 1531 / 0x5e2b838
Jul 07 20:45:53-805456 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:53-805650 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:53-805847 util-scheduler-8620 DEBUG Adding task: 1532 / 0x46620a0
Jul 07 20:45:53-806087 util-scheduler-8620 DEBUG Checking readiness of task: 1532 / 0x46620a0
Jul 07 20:45:53-806281 util-scheduler-8620 DEBUG Checking readiness of task: 1526 / 0x46620a0
Jul 07 20:45:53-806471 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-806661 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-806850 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-807039 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-807227 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-807415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-807605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-807796 util-scheduler-8620 DEBUG Running task: 1532 / 0x46620a0
Jul 07 20:45:53-807995 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:53-808171 util-8620 DEBUG process_notify is running
Jul 07 20:45:53-808340 util-8620 DEBUG client_notify is running
Jul 07 20:45:53-808515 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:53-808705 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:53-808893 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:53-809174 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:53-828098 util-scheduler-8620 DEBUG Checking readiness of task: 1526 / 0x46620a0
Jul 07 20:45:53-828375 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-828570 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-828763 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-828954 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-829144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-829438 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-829631 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-829828 util-scheduler-8620 DEBUG Running task: 1526 / 0x46620a0
Jul 07 20:45:53-830241 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:53-830483 util-scheduler-8620 DEBUG Adding task: 1533 / 0x4662248
Jul 07 20:45:53-830744 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:53-831001 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:53-831193 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:53-831384 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:53-831576 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:53-831765 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:53-831954 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:53-832146 util-scheduler-8620 DEBUG Running task: 1533 / 0x4662248
Jul 07 20:45:53-832335 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:53-832533 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:53-832756 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:53-833013 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:53-833279 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:53-833510 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:53-833717 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:53-833963 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:53-834173 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:53-834360 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:53-834547 util-scheduler-8620 DEBUG Canceling task: 1440 / 0x5e31aa0
Jul 07 20:45:53-834768 util-scheduler-8620 DEBUG Adding task: 1534 / 0x5e31aa0
Jul 07 20:45:53-834947 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:53-835199 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:53-835791 util-scheduler-8620 DEBUG Adding task: 1535 / 0x4d5e5d8
Jul 07 20:45:53-835978 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:53-836180 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:54-425467 util-scheduler-8620 DEBUG Canceling task: 1442 / 0x5e2de48
Jul 07 20:45:54-425904 util-scheduler-8620 DEBUG Adding task: 1536 / 0x5e2de48
Jul 07 20:45:54-426102 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:54-426318 util-scheduler-8620 DEBUG Adding task: 1537 / 0x46620a0
Jul 07 20:45:54-426635 util-scheduler-8620 DEBUG Checking readiness of task: 1537 / 0x46620a0
Jul 07 20:45:54-426835 util-scheduler-8620 DEBUG Checking readiness of task: 1535 / 0x4d5e5d8
Jul 07 20:45:54-427029 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-427220 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-427410 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-427601 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-427790 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-427980 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-428168 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-428362 util-scheduler-8620 DEBUG Running task: 1535 / 0x4d5e5d8
Jul 07 20:45:54-428549 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-428730 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-428905 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-429143 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-429583 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-676547 util-scheduler-8620 DEBUG Checking readiness of task: 1537 / 0x46620a0
Jul 07 20:45:54-676934 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-677134 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-677359 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-677552 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-677744 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-677934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-678126 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-678322 util-scheduler-8620 DEBUG Running task: 1537 / 0x46620a0
Jul 07 20:45:54-678748 util-8620 DEBUG receive_ready read 368/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:54-679014 util-scheduler-8620 DEBUG Adding task: 1538 / 0x4662248
Jul 07 20:45:54-679301 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-679497 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-679687 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-679881 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-680071 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-680260 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-680449 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-680640 util-scheduler-8620 DEBUG Running task: 1538 / 0x4662248
Jul 07 20:45:54-680831 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:54-681035 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:54-681288 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `D3TJ'
Jul 07 20:45:54-681559 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:54-681803 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-682035 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-682245 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:54-682496 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-682708 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-682898 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:54-683089 util-scheduler-8620 DEBUG Canceling task: 1534 / 0x5e31aa0
Jul 07 20:45:54-683316 util-scheduler-8620 DEBUG Adding task: 1539 / 0x5e31aa0
Jul 07 20:45:54-684692 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:54-684968 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-685214 util-scheduler-8620 DEBUG Adding task: 1540 / 0x4d5e5d8
Jul 07 20:45:54-685400 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:54-685616 cadet-tun-8620 INFO <=== PING for D3TJ
Jul 07 20:45:54-685804 cadet-tun-8620 DEBUG   t_decrypt with V7H63X9N
Jul 07 20:45:54-685976 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:54-686142 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:54-690342 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:54-691279 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:54-691513 cadet-tun-8620 INFO ===> PONG for D3TJ
Jul 07 20:45:54-691812 cadet-tun-8620 DEBUG   sending 2999538669
Jul 07 20:45:54-691989 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:54-692176 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:54-695930 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:54-696563 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:54-696809 cadet-tun-8620 DEBUG   e sending 3356006744
Jul 07 20:45:54-697020 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:54-697248 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:54-697482 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:54-697664 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:54-697886 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:54-698063 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:54-698284 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-698568 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (48 bytes)
Jul 07 20:45:54-698767 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 3
Jul 07 20:45:54-699002 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-699211 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-699523 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 48)
Jul 07 20:45:54-699724 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:54-699953 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-700138 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:54-700315 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:54-700519 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:54-700723 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:54-700899 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:54-701075 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:54-701364 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-701688 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:54-701870 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:54-702685 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-702885 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:54-703064 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:54-703299 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-703495 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:54-703671 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:54-703905 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-704099 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:54-704276 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:54-704475 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:54-704701 util-scheduler-8620 DEBUG Adding task: 1541 / 0x4662248
Jul 07 20:45:54-704974 util-scheduler-8620 DEBUG Checking readiness of task: 1540 / 0x4d5e5d8
Jul 07 20:45:54-705173 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-705500 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-705716 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-705907 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-706097 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-706287 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-706476 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-706669 util-scheduler-8620 DEBUG Running task: 1540 / 0x4d5e5d8
Jul 07 20:45:54-706857 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-707037 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-707209 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-707441 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-707746 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-707960 util-scheduler-8620 DEBUG Running task: 1541 / 0x4662248
Jul 07 20:45:54-708152 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:54-708352 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:54-708570 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `D3TJ'
Jul 07 20:45:54-708822 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:54-709057 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-709308 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-709518 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:54-709762 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-709973 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-710160 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:54-710349 util-scheduler-8620 DEBUG Canceling task: 1539 / 0x5e31aa0
Jul 07 20:45:54-710572 util-scheduler-8620 DEBUG Adding task: 1542 / 0x5e31aa0
Jul 07 20:45:54-710751 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:54-710999 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-711213 util-scheduler-8620 DEBUG Adding task: 1543 / 0x4d5e5d8
Jul 07 20:45:54-711395 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:54-711592 cadet-tun-8620 INFO <=== PONG for D3TJ
Jul 07 20:45:54-711830 util-scheduler-8620 DEBUG Adding task: 1544 / 0x4662248
Jul 07 20:45:54-712075 util-scheduler-8620 DEBUG Checking readiness of task: 1543 / 0x4d5e5d8
Jul 07 20:45:54-712271 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-712462 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-712651 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-712840 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-713028 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-713238 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-713445 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-713635 util-scheduler-8620 DEBUG Running task: 1543 / 0x4d5e5d8
Jul 07 20:45:54-713819 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-713995 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-714164 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-714476 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-714737 util-scheduler-8620 DEBUG Adding task: 1545 / 0x4d5e5d8
Jul 07 20:45:54-714939 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-715222 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-715420 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-715635 util-scheduler-8620 DEBUG Running task: 1544 / 0x4662248
Jul 07 20:45:54-715825 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:54-716018 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:54-716233 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `D3TJ'
Jul 07 20:45:54-716477 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:54-716710 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-716936 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-717144 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:54-717408 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-717615 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-717800 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:54-717982 util-scheduler-8620 DEBUG Canceling task: 1542 / 0x5e31aa0
Jul 07 20:45:54-718199 util-scheduler-8620 DEBUG Adding task: 1546 / 0x5e31aa0
Jul 07 20:45:54-718378 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:54-718580 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:54-718776 cadet-tun-8620 INFO <=== PONG for D3TJ
Jul 07 20:45:54-719016 util-scheduler-8620 DEBUG Adding task: 1547 / 0x4662248
Jul 07 20:45:54-719257 util-scheduler-8620 DEBUG Checking readiness of task: 1545 / 0x4d5e5d8
Jul 07 20:45:54-719452 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-719643 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-719833 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-720025 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-720215 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-720404 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-720594 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-720784 util-scheduler-8620 DEBUG Running task: 1545 / 0x4d5e5d8
Jul 07 20:45:54-720968 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-721142 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-721336 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-721561 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-721769 util-scheduler-8620 DEBUG Adding task: 1548 / 0x4d5e5d8
Jul 07 20:45:54-721967 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:54-722254 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-722452 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-722649 util-scheduler-8620 DEBUG Running task: 1547 / 0x4662248
Jul 07 20:45:54-722838 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:54-723031 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:54-723244 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `D3TJ'
Jul 07 20:45:54-723487 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:54-723718 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-723945 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-724151 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:54-724389 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-724594 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-724778 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:54-724961 util-scheduler-8620 DEBUG Canceling task: 1546 / 0x5e31aa0
Jul 07 20:45:54-725176 util-scheduler-8620 DEBUG Adding task: 1549 / 0x5e31aa0
Jul 07 20:45:54-725379 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:54-725585 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:54-725779 cadet-tun-8620 INFO <=== PONG for D3TJ
Jul 07 20:45:54-725988 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:54-726194 util-scheduler-8620 DEBUG Adding task: 1550 / 0x46620a0
Jul 07 20:45:54-726438 util-scheduler-8620 DEBUG Checking readiness of task: 1550 / 0x46620a0
Jul 07 20:45:54-726633 util-scheduler-8620 DEBUG Checking readiness of task: 1548 / 0x4d5e5d8
Jul 07 20:45:54-726825 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-727016 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-727207 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-727397 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-727587 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-727775 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-727964 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-728155 util-scheduler-8620 DEBUG Running task: 1548 / 0x4d5e5d8
Jul 07 20:45:54-728339 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-728513 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-728682 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-728905 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-729112 util-scheduler-8620 DEBUG Adding task: 1551 / 0x4d5e5d8
Jul 07 20:45:54-729334 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-729632 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-729829 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-730031 util-scheduler-8620 DEBUG Running task: 1550 / 0x46620a0
Jul 07 20:45:54-730438 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:54-730665 util-scheduler-8620 DEBUG Adding task: 1552 / 0x4662248
Jul 07 20:45:54-730915 util-scheduler-8620 DEBUG Checking readiness of task: 1551 / 0x4d5e5d8
Jul 07 20:45:54-731110 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-731301 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-731491 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-731679 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-731869 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-732058 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-732247 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-732436 util-scheduler-8620 DEBUG Running task: 1551 / 0x4d5e5d8
Jul 07 20:45:54-732621 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-732796 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-732964 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-733212 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-733422 util-scheduler-8620 DEBUG Adding task: 1553 / 0x4d5e5d8
Jul 07 20:45:54-733619 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:54-733901 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-734099 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-734296 util-scheduler-8620 DEBUG Running task: 1552 / 0x4662248
Jul 07 20:45:54-734485 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:54-734677 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:54-734902 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `D3TJ'
Jul 07 20:45:54-735146 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:54-735393 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:54-735624 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-735831 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:54-736069 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:54-736276 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:54-736461 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:54-736644 util-scheduler-8620 DEBUG Canceling task: 1549 / 0x5e31aa0
Jul 07 20:45:54-736859 util-scheduler-8620 DEBUG Adding task: 1554 / 0x5e31aa0
Jul 07 20:45:54-737038 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:54-737265 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:54-737462 cadet-tun-8620 INFO <=== PONG for D3TJ
Jul 07 20:45:54-737674 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:54-737873 util-scheduler-8620 DEBUG Adding task: 1555 / 0x46620a0
Jul 07 20:45:54-738119 util-scheduler-8620 DEBUG Checking readiness of task: 1555 / 0x46620a0
Jul 07 20:45:54-738312 util-scheduler-8620 DEBUG Checking readiness of task: 1553 / 0x4d5e5d8
Jul 07 20:45:54-738504 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-738695 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-738886 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-739076 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-739268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-739460 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-739650 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-739842 util-scheduler-8620 DEBUG Running task: 1553 / 0x4d5e5d8
Jul 07 20:45:54-740028 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-740205 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-740374 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-740601 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-740807 util-scheduler-8620 DEBUG Adding task: 1556 / 0x4d5e5d8
Jul 07 20:45:54-741006 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-741331 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-741530 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-741773 util-scheduler-8620 DEBUG Checking readiness of task: 1556 / 0x4d5e5d8
Jul 07 20:45:54-741969 util-scheduler-8620 DEBUG Checking readiness of task: 1555 / 0x46620a0
Jul 07 20:45:54-742159 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-742351 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-742540 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-742731 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-742920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-743110 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-743299 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-743490 util-scheduler-8620 DEBUG Running task: 1556 / 0x4d5e5d8
Jul 07 20:45:54-743672 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-743848 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-744017 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-744240 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:54-744445 util-scheduler-8620 DEBUG Adding task: 1557 / 0x4d5e5d8
Jul 07 20:45:54-744644 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:54-744925 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:54-745138 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:54-745404 util-scheduler-8620 DEBUG Checking readiness of task: 1557 / 0x4d5e5d8
Jul 07 20:45:54-745599 util-scheduler-8620 DEBUG Checking readiness of task: 1555 / 0x46620a0
Jul 07 20:45:54-745790 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:54-745980 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:54-746169 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:54-746359 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:54-746547 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:54-746737 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:54-746926 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:54-747117 util-scheduler-8620 DEBUG Running task: 1557 / 0x4d5e5d8
Jul 07 20:45:54-747300 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:54-747475 util-8620 DEBUG process_notify is running
Jul 07 20:45:54-747642 util-8620 DEBUG client_notify is running
Jul 07 20:45:54-747852 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:54-748135 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:55-239283 util-scheduler-8620 DEBUG Checking readiness of task: 1555 / 0x46620a0
Jul 07 20:45:55-239684 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-239883 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-240080 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-240271 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-240461 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-240651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-240841 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-241038 util-scheduler-8620 DEBUG Running task: 1555 / 0x46620a0
Jul 07 20:45:55-241487 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:55-241745 util-scheduler-8620 DEBUG Adding task: 1558 / 0x4662248
Jul 07 20:45:55-242027 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-242222 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-242412 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-242603 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-242792 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-242983 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-243172 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-243362 util-scheduler-8620 DEBUG Running task: 1558 / 0x4662248
Jul 07 20:45:55-243553 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:55-243754 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:55-243985 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:55-244250 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:55-244493 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:55-244724 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:55-244934 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:55-245182 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:55-245814 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:55-246007 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:55-246232 util-scheduler-8620 DEBUG Canceling task: 1492 / 0x4d707d0
Jul 07 20:45:55-246458 util-scheduler-8620 DEBUG Adding task: 1559 / 0x4d707d0
Jul 07 20:45:55-246639 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:55-246898 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:55-247195 util-scheduler-8620 DEBUG Adding task: 1560 / 0x4d5e5d8
Jul 07 20:45:55-247383 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:55-247586 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:55-247805 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:55-248024 util-scheduler-8620 DEBUG Adding task: 1561 / 0x46620a0
Jul 07 20:45:55-248276 util-scheduler-8620 DEBUG Checking readiness of task: 1561 / 0x46620a0
Jul 07 20:45:55-248470 util-scheduler-8620 DEBUG Checking readiness of task: 1560 / 0x4d5e5d8
Jul 07 20:45:55-248662 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-248853 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-249042 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-249256 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-249446 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-249636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-249824 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-250020 util-scheduler-8620 DEBUG Running task: 1560 / 0x4d5e5d8
Jul 07 20:45:55-250204 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:55-250383 util-8620 DEBUG process_notify is running
Jul 07 20:45:55-250555 util-8620 DEBUG client_notify is running
Jul 07 20:45:55-250794 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:55-251001 util-scheduler-8620 DEBUG Adding task: 1562 / 0x4d5e5d8
Jul 07 20:45:55-251202 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:55-251511 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:55-251712 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:55-251956 util-scheduler-8620 DEBUG Checking readiness of task: 1562 / 0x4d5e5d8
Jul 07 20:45:55-252150 util-scheduler-8620 DEBUG Checking readiness of task: 1561 / 0x46620a0
Jul 07 20:45:55-252341 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-252532 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-252720 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-252910 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-253100 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-253314 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-253502 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-253694 util-scheduler-8620 DEBUG Running task: 1562 / 0x4d5e5d8
Jul 07 20:45:55-253878 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:55-254053 util-8620 DEBUG process_notify is running
Jul 07 20:45:55-254222 util-8620 DEBUG client_notify is running
Jul 07 20:45:55-254433 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:55-254718 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:55-659171 util-scheduler-8620 DEBUG Checking readiness of task: 1561 / 0x46620a0
Jul 07 20:45:55-659562 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-659761 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-659954 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-660150 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-660374 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-660567 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-660756 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-660952 util-scheduler-8620 DEBUG Running task: 1561 / 0x46620a0
Jul 07 20:45:55-661399 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:55-661657 util-scheduler-8620 DEBUG Adding task: 1563 / 0x4662248
Jul 07 20:45:55-661936 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:55-662131 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:55-662321 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:55-662511 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:55-662702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:55-662892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:55-663081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:55-663271 util-scheduler-8620 DEBUG Running task: 1563 / 0x4662248
Jul 07 20:45:55-663462 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:45:55-663665 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:45:55-663894 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `D3TJ'
Jul 07 20:45:55-664158 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:55-664402 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:55-664631 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:55-664840 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:55-665087 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:55-665806 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:55-666001 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:55-666195 util-scheduler-8620 DEBUG Canceling task: 1554 / 0x5e31aa0
Jul 07 20:45:55-666421 util-scheduler-8620 DEBUG Adding task: 1564 / 0x5e31aa0
Jul 07 20:45:55-666602 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:55-666859 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:55-667074 util-scheduler-8620 DEBUG Adding task: 1565 / 0x4d5e5d8
Jul 07 20:45:55-667257 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:55-667458 cadet-tun-8620 INFO <=== EPHM for D3TJ
Jul 07 20:45:56-259483 util-scheduler-8620 DEBUG Canceling task: 1536 / 0x5e2de48
Jul 07 20:45:56-259922 util-scheduler-8620 DEBUG Adding task: 1566 / 0x5e2de48
Jul 07 20:45:56-260120 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-260341 util-scheduler-8620 DEBUG Adding task: 1567 / 0x46620a0
Jul 07 20:45:56-260626 util-scheduler-8620 DEBUG Checking readiness of task: 1567 / 0x46620a0
Jul 07 20:45:56-260826 util-scheduler-8620 DEBUG Checking readiness of task: 1565 / 0x4d5e5d8
Jul 07 20:45:56-261020 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-261236 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-261428 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:56-261618 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-261808 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-261997 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-262187 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-262381 util-scheduler-8620 DEBUG Running task: 1565 / 0x4d5e5d8
Jul 07 20:45:56-262568 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:56-262748 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-262951 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-263191 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:56-263629 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:56-263860 util-scheduler-8620 DEBUG Running task: 1567 / 0x46620a0
Jul 07 20:45:56-264270 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:56-264514 util-scheduler-8620 DEBUG Adding task: 1568 / 0x4662248
Jul 07 20:45:56-264725 util-scheduler-8620 DEBUG Running task: 1490 / 0x4d707d4
Jul 07 20:45:56-264982 cadet-con-8620 DEBUG  *** Polling connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:56-265165 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:45:56-265463 cadet-con-8620 INFO --> {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:45:56-265654 cadet-con-8620 DEBUG  poll 0
Jul 07 20:45:56-265832 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:56-266071 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:56-266281 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:56-266590 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:45:56-266792 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:56-267020 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:56-267203 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:56-267378 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:56-267586 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:45:56-267803 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:45:56-268018 util-scheduler-8620 DEBUG Adding task: 1569 / 0x4d6ff98
Jul 07 20:45:56-268199 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:56-268406 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:56-268584 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:56-268760 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:56-269002 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:56-269210 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:56-269392 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:56-269631 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:56-269831 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:56-270011 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:56-270211 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:56-270465 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-270663 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-270855 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:56-271045 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-271235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-271425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-271616 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-271807 util-scheduler-8620 DEBUG Running task: 1569 / 0x4d6ff98
Jul 07 20:45:56-272017 util-scheduler-8620 DEBUG Adding task: 1570 / 0x4d6ff98
Jul 07 20:45:56-272239 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:56-272445 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:56-272652 util-scheduler-8620 DEBUG Adding task: 1571 / 0x46620a0
Jul 07 20:45:56-272852 util-scheduler-8620 DEBUG Running task: 1568 / 0x4662248
Jul 07 20:45:56-273044 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:45:56-273266 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:45:56-273506 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `D3TJ'
Jul 07 20:45:56-273760 cadet-con-8620 INFO <-- {                KX} on connection 1KSG9GE2 from D3TJ
Jul 07 20:45:56-273998 cadet-con-8620 DEBUG  on connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-274229 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:56-274438 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:56-274683 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:56-274890 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:56-275079 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:56-275266 util-scheduler-8620 DEBUG Canceling task: 1564 / 0x5e31aa0
Jul 07 20:45:56-275488 util-scheduler-8620 DEBUG Adding task: 1572 / 0x5e31aa0
Jul 07 20:45:56-275669 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:56-275914 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:56-276124 util-scheduler-8620 DEBUG Adding task: 1573 / 0x4d5e5d8
Jul 07 20:45:56-276306 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:56-276518 cadet-tun-8620 INFO <=== PING for D3TJ
Jul 07 20:45:56-276704 cadet-tun-8620 DEBUG   t_decrypt with V7H63X9N
Jul 07 20:45:56-276877 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:56-277044 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:56-280636 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:56-282024 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:56-282246 cadet-tun-8620 INFO ===> PONG for D3TJ
Jul 07 20:45:56-282545 cadet-tun-8620 DEBUG   sending 2999538669
Jul 07 20:45:56-282722 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:56-282907 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:56-285979 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:56-286587 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:56-286861 cadet-tun-8620 DEBUG   e sending 2500536716
Jul 07 20:45:56-287071 cadet-tun-8620 DEBUG GMT KX on Tunnel D3TJ
Jul 07 20:45:56-287275 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:56-287505 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:56-287687 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:56-287908 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:56-288087 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:56-288307 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-288584 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (48 bytes)
Jul 07 20:45:56-288785 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 4
Jul 07 20:45:56-289021 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:56-289257 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:56-289569 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 48)
Jul 07 20:45:56-289768 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:56-289994 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-290178 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:56-290359 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:56-290561 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:56-290764 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:56-290942 cadet-p2p-8620 DEBUG QQQ  queue length: 5
Jul 07 20:45:56-291116 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:56-291353 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-291549 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:56-291726 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:56-291959 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-292155 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:56-292332 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:56-292566 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-292784 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:56-292963 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:56-293220 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-293417 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:56-293596 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:56-293829 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:56-294024 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:56-294202 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:56-294400 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:56-294586 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-294800 util-scheduler-8620 DEBUG Adding task: 1574 / 0x46620a0
Jul 07 20:45:56-295072 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-295271 util-scheduler-8620 DEBUG Checking readiness of task: 1573 / 0x4d5e5d8
Jul 07 20:45:56-295466 util-scheduler-8620 DEBUG Checking readiness of task: 1571 / 0x46620a0
Jul 07 20:45:56-295657 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-295849 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-296040 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:56-296230 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-296420 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-296609 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-296797 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-296991 util-scheduler-8620 DEBUG Running task: 1571 / 0x46620a0
Jul 07 20:45:56-297175 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:56-297378 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-297550 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-297730 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:56-297926 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:56-298118 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:56-299830 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:56-300058 util-scheduler-8620 DEBUG Running task: 1573 / 0x4d5e5d8
Jul 07 20:45:56-300249 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:56-300425 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-300595 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-300819 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:56-301128 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:56-590975 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-591341 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-591550 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-591744 util-scheduler-8620 DEBUG Checking readiness of task: 683 / 0x465ee60
Jul 07 20:45:56-591938 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-592131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-592322 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-592512 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-592711 util-scheduler-8620 DEBUG Running task: 683 / 0x465ee60
Jul 07 20:45:56-593137 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:45:56-593435 util-scheduler-8620 DEBUG Adding task: 1575 / 0x465f008
Jul 07 20:45:56-593739 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-593947 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-594137 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-594328 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-594518 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-594707 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-594897 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-595086 util-scheduler-8620 DEBUG Running task: 1575 / 0x465f008
Jul 07 20:45:56-595279 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:45:56-595521 nse-api-8620 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 20:45:56-595813 cadet-hll-8620 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 08:45:56 2014
Jul 07 20:45:56-596040 cadet-p2p-8620 DEBUG set hello for STRN
Jul 07 20:45:56-596341 cadet-p2p-8620 DEBUG  merge into 0x513a4c8 (90 bytes)
Jul 07 20:45:56-596540 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-596757 util-scheduler-8620 DEBUG Adding task: 1576 / 0x465ee60
Jul 07 20:45:56-718237 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-718586 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-718784 util-scheduler-8620 DEBUG Checking readiness of task: 1500 / 0x4663d68
Jul 07 20:45:56-718980 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-719174 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-719366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-719557 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-719748 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-719942 util-scheduler-8620 DEBUG Running task: 1500 / 0x4663d68
Jul 07 20:45:56-720361 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:56-720613 util-scheduler-8620 DEBUG Adding task: 1577 / 0x4663f10
Jul 07 20:45:56-720885 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-721078 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-721565 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-721761 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-721952 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-722144 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-722334 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-722526 util-scheduler-8620 DEBUG Running task: 1577 / 0x4663f10
Jul 07 20:45:56-722719 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:56-722916 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-723129 util-scheduler-8620 DEBUG Adding task: 1578 / 0x4663d68
Jul 07 20:45:56-723317 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:56-723544 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 14443
Jul 07 20:45:56-723739 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 14443 Bps
Jul 07 20:45:56-732718 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11616 Bps, last update was 25 s ago
Jul 07 20:45:56-733070 util-scheduler-8620 DEBUG Adding task: 1579 / 0x4d6fa48
Jul 07 20:45:56-733360 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-733559 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-733750 util-scheduler-8620 DEBUG Checking readiness of task: 1574 / 0x46620a0
Jul 07 20:45:56-733973 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-734165 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-734355 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-734545 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-734734 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-734926 util-scheduler-8620 DEBUG Running task: 1574 / 0x46620a0
Jul 07 20:45:56-735338 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:56-735569 util-scheduler-8620 DEBUG Adding task: 1580 / 0x4662248
Jul 07 20:45:56-735818 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-736013 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-736204 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-736394 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-736585 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-736775 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-736963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-737154 util-scheduler-8620 DEBUG Running task: 1580 / 0x4662248
Jul 07 20:45:56-737368 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:56-737565 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:56-737789 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:56-738001 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:56-738203 util-scheduler-8620 DEBUG Adding task: 1581 / 0x46620a0
Jul 07 20:45:56-738391 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-738593 util-scheduler-8620 DEBUG Adding task: 1582 / 0x46620a0
Jul 07 20:45:56-738834 util-scheduler-8620 DEBUG Checking readiness of task: 1582 / 0x46620a0
Jul 07 20:45:56-739028 util-scheduler-8620 DEBUG Checking readiness of task: 1581 / 0x46620a0
Jul 07 20:45:56-739221 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-739417 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-739609 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-739799 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-739988 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-740178 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-740367 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-740559 util-scheduler-8620 DEBUG Running task: 1581 / 0x46620a0
Jul 07 20:45:56-740746 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:56-740924 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-741096 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-741313 util-scheduler-8620 DEBUG Canceling task: 1570 / 0x4d6ff98
Jul 07 20:45:56-741542 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:45:56-741764 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:56-742008 cadet-p2p-8620 DEBUG Checking 0x512ebf8 towards CMHCKRVP (->V8XX)
Jul 07 20:45:56-742243 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:56-742422 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:56-742613 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:45:56-742885 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:45:56-743080 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:56-743260 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:56-743470 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:45:56-743647 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:56-743818 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:45:56-744030 util-scheduler-8620 DEBUG Adding task: 1583 / 0x4d707d4
Jul 07 20:45:56-744213 cadet-con-8620 DEBUG  task 1583
Jul 07 20:45:56-744398 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:56-744575 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:56-744799 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:56-745034 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:56-745242 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:56-745419 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:56-745649 cadet-p2p-8620 DEBUG Checking 0x49b3600 towards CMHCKRVP (->V8XX)
Jul 07 20:45:56-745880 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:56-746063 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:56-746248 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:56-746418 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:56-746620 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:56-746800 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:56-746974 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:56-747214 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:56-747411 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:56-747590 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:56-747789 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:56-747999 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:45:56-748183 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:56-748363 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:56-748556 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:56-749890 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:56-881366 util-scheduler-8620 DEBUG Checking readiness of task: 1582 / 0x46620a0
Jul 07 20:45:56-881736 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-881933 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-882128 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-882319 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-882511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-882701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-882892 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-883087 util-scheduler-8620 DEBUG Running task: 1582 / 0x46620a0
Jul 07 20:45:56-883519 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:56-883774 util-scheduler-8620 DEBUG Adding task: 1584 / 0x4662248
Jul 07 20:45:56-884052 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-884245 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-884436 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-884627 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-884817 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-885007 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-885222 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-885415 util-scheduler-8620 DEBUG Running task: 1584 / 0x4662248
Jul 07 20:45:56-885606 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:56-885837 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:56-886066 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:56-886333 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:56-886591 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-886803 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-886988 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:56-887163 cadet-con-8620 DEBUG   ACK 84 (was 83)
Jul 07 20:45:56-887392 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:56-887624 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-887831 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-888019 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:56-888197 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-888407 util-scheduler-8620 DEBUG Adding task: 1585 / 0x46620a0
Jul 07 20:45:56-921421 util-scheduler-8620 DEBUG Checking readiness of task: 1585 / 0x46620a0
Jul 07 20:45:56-921733 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-921931 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-922125 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-922317 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-922510 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-922700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-922889 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-923082 util-scheduler-8620 DEBUG Running task: 1585 / 0x46620a0
Jul 07 20:45:56-923497 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:56-923737 util-scheduler-8620 DEBUG Adding task: 1586 / 0x4662248
Jul 07 20:45:56-923996 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-924190 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-924382 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-924572 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-924763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-924952 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-925142 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-925359 util-scheduler-8620 DEBUG Running task: 1586 / 0x4662248
Jul 07 20:45:56-925551 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:56-925752 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:56-925974 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:45:56-926229 cadet-con-8620 INFO <-- {               ACK} on connection HS92G30M from KNAS
Jul 07 20:45:56-926479 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-926689 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-926874 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:56-927047 cadet-con-8620 DEBUG   ACK 85 (was 84)
Jul 07 20:45:56-927274 cadet-con-8620 DEBUG connection_unlock_queue FWD on HS92G30M (->KNAS)
Jul 07 20:45:56-927505 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-927712 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-927896 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:45:56-928100 util-scheduler-8620 DEBUG Adding task: 1587 / 0x4662248
Jul 07 20:45:56-928339 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-928533 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-928726 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-928938 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-929130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-929347 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-929537 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-929725 util-scheduler-8620 DEBUG Running task: 1587 / 0x4662248
Jul 07 20:45:56-929914 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:45:56-930107 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:45:56-930319 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `KNAS'
Jul 07 20:45:56-930564 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection HS92G30M from KNAS
Jul 07 20:45:56-930801 cadet-con-8620 DEBUG   connection HS92G30M (->KNAS)
Jul 07 20:45:56-931030 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-931238 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:56-931479 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-931685 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-931873 cadet-con-8620 DEBUG  PID 20 (expected 20+)
Jul 07 20:45:56-932053 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:56-932242 util-scheduler-8620 DEBUG Canceling task: 1423 / 0x4d61c30
Jul 07 20:45:56-932465 util-scheduler-8620 DEBUG Adding task: 1588 / 0x4d61c30
Jul 07 20:45:56-932645 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:56-932915 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:56-933130 util-scheduler-8620 DEBUG Adding task: 1589 / 0x4d5e5d8
Jul 07 20:45:56-933341 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:56-933511 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:56-937119 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:56-938552 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:56-938760 cadet-tun-8620 INFO   HMAC with key 7VEEVN5W
Jul 07 20:45:56-941519 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on KNAS
Jul 07 20:45:56-941769 cadet-con-8620 DEBUG GMC send BCK ACK on HS92G30M (->KNAS)
Jul 07 20:45:56-941961 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:56-942136 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:56-942309 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:56-942530 cadet-con-8620 DEBUG connection send BCK ack on HS92G30M (->KNAS)
Jul 07 20:45:56-942709 cadet-con-8620 DEBUG  ACK 84
Jul 07 20:45:56-942890 cadet-con-8620 DEBUG  last pid 20, last ack 83, qmax 11, q 0
Jul 07 20:45:56-943157 cadet-con-8620 INFO --> {               ACK} ( 84) on connection HS92G30M (->KNAS) (40 bytes)
Jul 07 20:45:56-943349 cadet-con-8620 DEBUG  ack 84
Jul 07 20:45:56-943528 cadet-con-8620 DEBUG   C_P+ 0x4d61c30 0
Jul 07 20:45:56-943763 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:45:56-943970 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:45:56-944268 cadet-p2p-8620 INFO que {               ACK} ( 84) on connection HS92G30M (->KNAS) (0x4d61c30) FWD towards KNAS (size 40)
Jul 07 20:45:56-944467 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:56-944692 cadet-con-8620 DEBUG  checking sendability of FWD traffic on HS92G30M (->KNAS)
Jul 07 20:45:56-944874 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:45:56-945051 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:56-945280 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:45:56-945500 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:45:56-945722 util-scheduler-8620 DEBUG Adding task: 1590 / 0x4d5c9e8
Jul 07 20:45:56-945903 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:56-946108 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:56-946287 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:56-946462 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:45:56-946701 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on HS92G30M (->KNAS)
Jul 07 20:45:56-946909 cadet-p2p-8620 DEBUG QQQ    payload , 84
Jul 07 20:45:56-947087 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:56-947285 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:56-947468 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-947677 util-scheduler-8620 DEBUG Adding task: 1591 / 0x46620a0
Jul 07 20:45:56-947942 util-scheduler-8620 DEBUG Checking readiness of task: 1591 / 0x46620a0
Jul 07 20:45:56-948142 util-scheduler-8620 DEBUG Checking readiness of task: 1589 / 0x4d5e5d8
Jul 07 20:45:56-948334 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-948525 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-948716 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-948907 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-949096 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-949310 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-949501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-949695 util-scheduler-8620 DEBUG Running task: 1589 / 0x4d5e5d8
Jul 07 20:45:56-949881 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:56-950061 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-950234 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-950463 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:56-950816 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:56-951029 util-scheduler-8620 DEBUG Running task: 1590 / 0x4d5c9e8
Jul 07 20:45:56-951240 util-scheduler-8620 DEBUG Adding task: 1592 / 0x4d5c9e8
Jul 07 20:45:56-951462 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:45:56-951661 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:56-951861 util-scheduler-8620 DEBUG Adding task: 1593 / 0x46620a0
Jul 07 20:45:56-952102 util-scheduler-8620 DEBUG Checking readiness of task: 1593 / 0x46620a0
Jul 07 20:45:56-952296 util-scheduler-8620 DEBUG Checking readiness of task: 1591 / 0x46620a0
Jul 07 20:45:56-952486 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-952676 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-952952 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-953145 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-953362 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-953552 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-953742 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-953932 util-scheduler-8620 DEBUG Running task: 1593 / 0x46620a0
Jul 07 20:45:56-954116 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:56-954292 util-8620 DEBUG process_notify is running
Jul 07 20:45:56-954460 util-8620 DEBUG client_notify is running
Jul 07 20:45:56-954639 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:56-955058 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:56-955253 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:56-955559 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:56-982416 util-scheduler-8620 DEBUG Checking readiness of task: 1591 / 0x46620a0
Jul 07 20:45:56-982701 util-scheduler-8620 DEBUG Checking readiness of task: 1578 / 0x4663d68
Jul 07 20:45:56-982899 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-983092 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-983304 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-983496 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-983687 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-983877 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-984069 util-scheduler-8620 DEBUG Running task: 1578 / 0x4663d68
Jul 07 20:45:56-984482 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:56-984748 util-scheduler-8620 DEBUG Adding task: 1594 / 0x4663f10
Jul 07 20:45:56-985005 util-scheduler-8620 DEBUG Checking readiness of task: 1591 / 0x46620a0
Jul 07 20:45:56-985219 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:56-985412 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:56-985603 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:56-985793 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:56-985982 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:56-986183 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:56-986372 util-scheduler-8620 DEBUG Running task: 1594 / 0x4663f10
Jul 07 20:45:56-986977 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:56-987178 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:56-987384 util-scheduler-8620 DEBUG Adding task: 1595 / 0x4663d68
Jul 07 20:45:56-987571 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:56-987848 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 14443
Jul 07 20:45:56-988049 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 14443 Bps
Jul 07 20:45:56-988300 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 14443 Bps, last update was 255 ms ago
Jul 07 20:45:56-988520 util-scheduler-8620 DEBUG Canceling task: 1579 / 0x4d6fa48
Jul 07 20:45:56-988737 util-scheduler-8620 DEBUG Adding task: 1596 / 0x4d6fa48
Jul 07 20:45:57-075474 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-075826 util-scheduler-8620 DEBUG Checking readiness of task: 1591 / 0x46620a0
Jul 07 20:45:57-076028 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-076223 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-076417 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-076610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-076804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-076996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-077225 util-scheduler-8620 DEBUG Running task: 1591 / 0x46620a0
Jul 07 20:45:57-077647 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:57-077899 util-scheduler-8620 DEBUG Adding task: 1597 / 0x4662248
Jul 07 20:45:57-078176 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-078370 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-078563 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-078754 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-078946 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-079136 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-079328 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-079518 util-scheduler-8620 DEBUG Running task: 1597 / 0x4662248
Jul 07 20:45:57-079711 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:57-079941 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:57-080175 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:57-080382 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-080589 util-scheduler-8620 DEBUG Adding task: 1598 / 0x46620a0
Jul 07 20:45:57-080778 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:57-080985 util-scheduler-8620 DEBUG Adding task: 1599 / 0x46620a0
Jul 07 20:45:57-081256 util-scheduler-8620 DEBUG Checking readiness of task: 1599 / 0x46620a0
Jul 07 20:45:57-081452 util-scheduler-8620 DEBUG Checking readiness of task: 1598 / 0x46620a0
Jul 07 20:45:57-081647 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-081839 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-082032 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-082225 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-082416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-082607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-082798 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-082991 util-scheduler-8620 DEBUG Running task: 1598 / 0x46620a0
Jul 07 20:45:57-083178 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-083358 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-083532 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-083723 util-scheduler-8620 DEBUG Canceling task: 1531 / 0x5e2b838
Jul 07 20:45:57-083951 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:45:57-084173 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:57-084415 cadet-p2p-8620 DEBUG Checking 0x4701128 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-084650 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:57-084830 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:45:57-085023 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:45:57-085332 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 48)
Jul 07 20:45:57-085532 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:57-085716 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:57-085905 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:45:57-086097 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 5
Jul 07 20:45:57-086276 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:57-086462 util-scheduler-8620 DEBUG Canceling task: 1527 / 0x5e31aa0
Jul 07 20:45:57-086677 util-scheduler-8620 DEBUG Adding task: 1600 / 0x5e31aa0
Jul 07 20:45:57-086927 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:57-087099 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:57-087323 cadet-p2p-8620 DEBUG Checking 0x4978aa8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-087556 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-087742 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:57-087920 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:57-088152 cadet-p2p-8620 DEBUG Checking 0x4978aa8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-088383 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-088567 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:57-088743 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:57-088911 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:57-089119 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `D3TJ'
Jul 07 20:45:57-089356 util-scheduler-8620 DEBUG Adding task: 1601 / 0x5e2b838
Jul 07 20:45:57-089539 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:57-089718 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:45:57-089918 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:57-090097 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:57-090291 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:57-090532 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-090730 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:57-090909 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:57-091144 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-091339 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:57-091517 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:57-091752 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-091946 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-092124 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-092358 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-092553 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-092731 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-092930 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:57-093136 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 48 bytes.
Jul 07 20:45:57-093347 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:45:57-093553 util-scheduler-8620 DEBUG Adding task: 1602 / 0x5e2b838
Jul 07 20:45:57-093774 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:57-093972 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-094176 util-scheduler-8620 DEBUG Adding task: 1603 / 0x46620a0
Jul 07 20:45:57-094380 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:45:57-096102 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-096313 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:57-096569 util-scheduler-8620 DEBUG Checking readiness of task: 1603 / 0x46620a0
Jul 07 20:45:57-096769 util-scheduler-8620 DEBUG Checking readiness of task: 1599 / 0x46620a0
Jul 07 20:45:57-096963 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-097156 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-097376 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-097569 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-097761 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-097953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-098150 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-098344 util-scheduler-8620 DEBUG Running task: 1603 / 0x46620a0
Jul 07 20:45:57-098532 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-098711 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-098885 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-099066 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:57-099265 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:57-099455 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:57-099770 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-099981 util-scheduler-8620 DEBUG Running task: 1601 / 0x5e2b838
Jul 07 20:45:57-100177 util-scheduler-8620 DEBUG Canceling task: 1602 / 0x5e2b838
Jul 07 20:45:57-100395 util-scheduler-8620 DEBUG Adding task: 1604 / 0x5e2b838
Jul 07 20:45:57-100611 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:57-100805 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-101002 util-scheduler-8620 DEBUG Adding task: 1605 / 0x46620a0
Jul 07 20:45:57-101284 util-scheduler-8620 DEBUG Checking readiness of task: 1605 / 0x46620a0
Jul 07 20:45:57-101481 util-scheduler-8620 DEBUG Checking readiness of task: 1599 / 0x46620a0
Jul 07 20:45:57-101674 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-101864 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-102055 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-102244 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-102432 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-102620 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-102810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-102999 util-scheduler-8620 DEBUG Running task: 1599 / 0x46620a0
Jul 07 20:45:57-103400 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:57-103626 util-scheduler-8620 DEBUG Adding task: 1606 / 0x4662248
Jul 07 20:45:57-103836 util-scheduler-8620 DEBUG Running task: 1605 / 0x46620a0
Jul 07 20:45:57-104020 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-104195 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-104364 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-104539 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:57-104728 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:57-104916 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:57-105252 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-105502 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-105696 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-105886 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-106171 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-106363 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-106553 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-106965 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-107160 util-scheduler-8620 DEBUG Running task: 1606 / 0x4662248
Jul 07 20:45:57-107352 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:57-107546 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:57-107760 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:57-107940 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:57-108210 util-scheduler-8620 DEBUG Adding task: 1607 / 0x46620a0
Jul 07 20:45:57-108475 util-scheduler-8620 DEBUG Checking readiness of task: 1607 / 0x46620a0
Jul 07 20:45:57-108691 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-108882 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-109073 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-109287 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-109477 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-110085 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-110279 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-110472 util-scheduler-8620 DEBUG Running task: 1607 / 0x46620a0
Jul 07 20:45:57-110872 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:57-111096 util-scheduler-8620 DEBUG Adding task: 1608 / 0x4662248
Jul 07 20:45:57-111361 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-111554 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-111771 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-111961 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-112151 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-112339 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-112529 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-112717 util-scheduler-8620 DEBUG Running task: 1608 / 0x4662248
Jul 07 20:45:57-112905 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:57-113129 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:57-113761 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:57-113965 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-114165 util-scheduler-8620 DEBUG Adding task: 1609 / 0x46620a0
Jul 07 20:45:57-114350 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:57-114548 util-scheduler-8620 DEBUG Adding task: 1610 / 0x46620a0
Jul 07 20:45:57-114791 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-114984 util-scheduler-8620 DEBUG Checking readiness of task: 1609 / 0x46620a0
Jul 07 20:45:57-115176 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-115367 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-115558 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-115747 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-115937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-116125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-116313 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-116503 util-scheduler-8620 DEBUG Running task: 1609 / 0x46620a0
Jul 07 20:45:57-116687 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-116861 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-117031 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-117237 util-scheduler-8620 DEBUG Canceling task: 1604 / 0x5e2b838
Jul 07 20:45:57-117460 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 96 bytes.
Jul 07 20:45:57-117676 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:57-117910 cadet-p2p-8620 DEBUG Checking 0x4978aa8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-118143 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-118325 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:45:57-118499 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:57-118719 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:57-118908 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:45:57-119082 cadet-p2p-8620 DEBUG   payload ID 0
Jul 07 20:45:57-119361 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 96)
Jul 07 20:45:57-119554 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:57-119731 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:57-119917 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:57-120090 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:57-120257 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:57-120444 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:45:57-120631 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:45:57-120850 cadet-chn-8620 DEBUG !!! STD BACKOFF 250 ms
Jul 07 20:45:57-121060 util-scheduler-8620 DEBUG Adding task: 1611 / 0x5e33a48
Jul 07 20:45:57-121284 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 4
Jul 07 20:45:57-121744 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-121928 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:57-122103 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:45:57-122274 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:57-122473 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:45:57-122649 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:45:57-122823 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:45:57-123023 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:57-123203 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:57-123386 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:57-123566 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:57-123743 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:57-123912 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:57-124128 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:57-124298 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:57-124531 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:57-124775 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:57-124959 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:57-125147 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:57-125338 cadet-chn-8620 DEBUG  channel not ready yet!
Jul 07 20:45:57-125510 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:57-125697 util-scheduler-8620 DEBUG Canceling task: 1600 / 0x5e31aa0
Jul 07 20:45:57-125909 util-scheduler-8620 DEBUG Adding task: 1612 / 0x5e31aa0
Jul 07 20:45:57-126151 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:57-126330 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:45:57-126508 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:45:57-126681 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:57-126901 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-127130 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-127311 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:57-127484 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:57-127716 cadet-p2p-8620 DEBUG Checking 0x4dbd080 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-127955 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-128187 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-128368 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:57-128539 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:57-128757 cadet-p2p-8620 DEBUG Checking 0x4dbd080 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-128935 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:57-129137 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:45:57-129378 util-scheduler-8620 DEBUG Adding task: 1613 / 0x5e2b838
Jul 07 20:45:57-129558 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:57-129733 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:45:57-129930 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:57-130106 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:45:57-130279 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:57-130515 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-130710 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:57-130886 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:57-131121 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-131314 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-131491 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-131723 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-131915 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-132091 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-132303 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:57-132508 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 96 bytes.
Jul 07 20:45:57-132690 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:45:57-132890 util-scheduler-8620 DEBUG Adding task: 1614 / 0x5e2b838
Jul 07 20:45:57-133108 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:57-133327 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-133529 util-scheduler-8620 DEBUG Adding task: 1615 / 0x46620a0
Jul 07 20:45:57-133729 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:45:57-134125 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-134326 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:57-134572 util-scheduler-8620 DEBUG Checking readiness of task: 1615 / 0x46620a0
Jul 07 20:45:57-134769 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-134960 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-135151 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-135343 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-135533 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-135945 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-136241 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-136434 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-136628 util-scheduler-8620 DEBUG Running task: 1615 / 0x46620a0
Jul 07 20:45:57-136813 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-136991 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-137162 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-137367 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:57-137559 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:57-137749 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:57-138067 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-138276 util-scheduler-8620 DEBUG Running task: 1613 / 0x5e2b838
Jul 07 20:45:57-138471 util-scheduler-8620 DEBUG Canceling task: 1614 / 0x5e2b838
Jul 07 20:45:57-138685 util-scheduler-8620 DEBUG Adding task: 1616 / 0x5e2b838
Jul 07 20:45:57-138899 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:57-139093 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-139291 util-scheduler-8620 DEBUG Adding task: 1617 / 0x46620a0
Jul 07 20:45:57-139536 util-scheduler-8620 DEBUG Checking readiness of task: 1617 / 0x46620a0
Jul 07 20:45:57-139748 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-139941 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-140131 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-140322 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-140523 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-140713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-140903 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-141092 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-141309 util-scheduler-8620 DEBUG Running task: 1617 / 0x46620a0
Jul 07 20:45:57-141494 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-141670 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-141838 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-142037 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:57-142228 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:57-142417 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:57-142712 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:57-195429 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-195810 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-196008 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-196201 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-196392 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-196584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-196773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-196963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-197157 util-scheduler-8620 DEBUG Running task: 1596 / 0x4d6fa48
Jul 07 20:45:57-621367 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-621742 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-621938 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-622130 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-622321 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-622513 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-622702 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-622891 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-623085 util-scheduler-8620 DEBUG Running task: 1611 / 0x5e33a48
Jul 07 20:45:57-623269 cadet-chn-8620 DEBUG !!! RE-CREATE
Jul 07 20:45:57-623560 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:57-623782 util-scheduler-8620 DEBUG Adding task: 1618 / 0x4d5e5d8
Jul 07 20:45:57-624077 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:57-624303 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:45:57-624507 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:45:57-624690 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:57-624874 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:45:57-625058 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:57-625260 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:57-625433 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:57-625651 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:45:57-625826 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:57-626066 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:57-626314 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:57-626505 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:57-626819 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:57-626992 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:57-627178 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:45:57-631452 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:57-632318 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:57-632572 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:57-632766 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:45:57-636473 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:45:57-636804 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:45:57-636987 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:57-637242 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:45:57-637454 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:57-637677 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-637873 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:45:57-638155 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (96 bytes)
Jul 07 20:45:57-638355 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:45:57-638532 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:45:57-638705 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:45:57-638876 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:57-639051 cadet-con-8620 DEBUG  *** POLL FWD requested
Jul 07 20:45:57-639223 cadet-con-8620 DEBUG  *** POLL started on request
Jul 07 20:45:57-639435 util-scheduler-8620 DEBUG Adding task: 1619 / 0x5e31aa4
Jul 07 20:45:57-639622 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 3
Jul 07 20:45:57-639858 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:57-640066 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:57-640383 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 96)
Jul 07 20:45:57-640583 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:57-640809 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-640992 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:57-641165 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:57-641398 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ not needed
Jul 07 20:45:57-641599 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:57-641776 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:57-641951 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:57-642189 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-642384 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:57-642560 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:57-642795 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-642986 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-643161 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-643392 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-643583 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:57-643759 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:57-643989 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:57-644182 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:57-644370 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:57-644567 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:57-644845 util-scheduler-8620 DEBUG Checking readiness of task: 1618 / 0x4d5e5d8
Jul 07 20:45:57-645042 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-645254 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-645444 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-645634 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-645822 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-646010 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-646198 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-646385 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-646576 util-scheduler-8620 DEBUG Running task: 1618 / 0x4d5e5d8
Jul 07 20:45:57-646761 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:57-646945 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-647118 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-647353 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:45:57-647670 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:57-754170 util-scheduler-8620 DEBUG Checking readiness of task: 1610 / 0x46620a0
Jul 07 20:45:57-754521 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-754722 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-754915 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-755106 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-755296 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-755486 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-755675 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-755870 util-scheduler-8620 DEBUG Running task: 1610 / 0x46620a0
Jul 07 20:45:57-756293 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:57-756548 util-scheduler-8620 DEBUG Adding task: 1620 / 0x4662248
Jul 07 20:45:57-756821 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-757014 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-757227 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-757417 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-757606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-757796 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-757992 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-758186 util-scheduler-8620 DEBUG Running task: 1620 / 0x4662248
Jul 07 20:45:57-758386 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:45:57-758591 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:45:57-758832 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 20:45:57-759106 cadet-con-8620 INFO <-- {                KX} on connection CMHCKRVP from V8XX
Jul 07 20:45:57-759357 cadet-con-8620 DEBUG  on connection CMHCKRVP (->V8XX)
Jul 07 20:45:57-759594 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:57-759807 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:57-760062 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:57-760274 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:57-760460 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:57-760654 util-scheduler-8620 DEBUG Canceling task: 1559 / 0x4d707d0
Jul 07 20:45:57-760886 util-scheduler-8620 DEBUG Adding task: 1621 / 0x4d707d0
Jul 07 20:45:57-761065 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:57-761447 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:57-762114 util-scheduler-8620 DEBUG Adding task: 1622 / 0x4d5e5d8
Jul 07 20:45:57-762300 cadet-tun-8620 DEBUG kx message received
Jul 07 20:45:57-762503 cadet-tun-8620 INFO <=== PONG for V8XX
Jul 07 20:45:57-762721 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:57-762928 util-scheduler-8620 DEBUG Adding task: 1623 / 0x46620a0
Jul 07 20:45:57-763188 util-scheduler-8620 DEBUG Checking readiness of task: 1623 / 0x46620a0
Jul 07 20:45:57-763383 util-scheduler-8620 DEBUG Checking readiness of task: 1622 / 0x4d5e5d8
Jul 07 20:45:57-763575 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-763764 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-763953 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-764141 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-764330 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-764518 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-764736 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-764931 util-scheduler-8620 DEBUG Running task: 1622 / 0x4d5e5d8
Jul 07 20:45:57-765118 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:57-765318 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-765581 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-765824 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:57-766033 util-scheduler-8620 DEBUG Adding task: 1624 / 0x4d5e5d8
Jul 07 20:45:57-766236 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:57-766539 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:57-767015 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:45:57-767514 util-scheduler-8620 DEBUG Checking readiness of task: 1624 / 0x4d5e5d8
Jul 07 20:45:57-767859 util-scheduler-8620 DEBUG Checking readiness of task: 1623 / 0x46620a0
Jul 07 20:45:57-768102 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-768294 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-768484 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-768675 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-768967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-769329 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-769570 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-769763 util-scheduler-8620 DEBUG Running task: 1624 / 0x4d5e5d8
Jul 07 20:45:57-769946 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:57-770122 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-770290 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-770506 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:45:57-770838 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:57-934457 util-scheduler-8620 DEBUG Checking readiness of task: 1623 / 0x46620a0
Jul 07 20:45:57-934814 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-935012 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-935205 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-935396 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-935588 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-935777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-935968 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-936162 util-scheduler-8620 DEBUG Running task: 1623 / 0x46620a0
Jul 07 20:45:57-936581 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:57-936834 util-scheduler-8620 DEBUG Adding task: 1625 / 0x4662248
Jul 07 20:45:57-937110 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-937330 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-937524 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-937717 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-937907 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-938111 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-938301 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-938492 util-scheduler-8620 DEBUG Running task: 1625 / 0x4662248
Jul 07 20:45:57-938713 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:57-938918 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:57-939150 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:45:57-939416 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:45:57-939676 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:57-939888 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:57-940073 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:57-940248 cadet-con-8620 DEBUG   ACK 64 (was 0)
Jul 07 20:45:57-940605 cadet-con-8620 DEBUG   Cancel poll
Jul 07 20:45:57-940809 util-scheduler-8620 DEBUG Canceling task: 1583 / 0x4d707d4
Jul 07 20:45:57-941079 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:57-941346 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:57-941561 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:57-941806 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:57-942000 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:57-942179 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:57-942458 cadet-p2p-8620 DEBUG   sendable!!
Jul 07 20:45:57-942683 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `V8XX'
Jul 07 20:45:57-942925 util-scheduler-8620 DEBUG Adding task: 1626 / 0x4d6ff98
Jul 07 20:45:57-943108 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:57-943287 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:57-943500 util-scheduler-8620 DEBUG Adding task: 1627 / 0x46620a0
Jul 07 20:45:57-943761 util-scheduler-8620 DEBUG Checking readiness of task: 1627 / 0x46620a0
Jul 07 20:45:57-943955 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-944145 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-944333 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-944521 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-944709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-944898 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-945085 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-945298 util-scheduler-8620 DEBUG Running task: 1626 / 0x4d6ff98
Jul 07 20:45:57-945509 util-scheduler-8620 DEBUG Adding task: 1628 / 0x4d6ff98
Jul 07 20:45:57-945732 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:57-945934 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:57-946134 util-scheduler-8620 DEBUG Adding task: 1629 / 0x46620a0
Jul 07 20:45:57-946375 util-scheduler-8620 DEBUG Checking readiness of task: 1629 / 0x46620a0
Jul 07 20:45:57-946567 util-scheduler-8620 DEBUG Checking readiness of task: 1627 / 0x46620a0
Jul 07 20:45:57-946757 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:57-946946 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:57-947135 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:57-947324 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:57-947512 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:57-947701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:57-947889 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:57-948080 util-scheduler-8620 DEBUG Running task: 1629 / 0x46620a0
Jul 07 20:45:57-948264 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:57-948442 util-8620 DEBUG process_notify is running
Jul 07 20:45:57-948613 util-8620 DEBUG client_notify is running
Jul 07 20:45:57-948791 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:57-949010 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:57-949223 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:57-949531 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-013056 util-scheduler-8620 DEBUG Checking readiness of task: 1627 / 0x46620a0
Jul 07 20:45:58-013417 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:58-013619 util-scheduler-8620 DEBUG Checking readiness of task: 1576 / 0x465ee60
Jul 07 20:45:58-013819 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-014013 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-014206 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-014398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-014590 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-014785 util-scheduler-8620 DEBUG Running task: 1576 / 0x465ee60
Jul 07 20:45:58-015207 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:45:58-015464 util-scheduler-8620 DEBUG Adding task: 1630 / 0x465f008
Jul 07 20:45:58-015744 util-scheduler-8620 DEBUG Checking readiness of task: 1627 / 0x46620a0
Jul 07 20:45:58-015955 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:58-016147 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-016339 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-016529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-016719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-016909 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-017101 util-scheduler-8620 DEBUG Running task: 1630 / 0x465f008
Jul 07 20:45:58-017317 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:45:58-017559 nse-api-8620 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 20:45:58-017848 cadet-hll-8620 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 08:45:58 2014
Jul 07 20:45:58-018074 cadet-p2p-8620 DEBUG set hello for STRN
Jul 07 20:45:58-018373 cadet-p2p-8620 DEBUG  merge into 0x51634d8 (90 bytes)
Jul 07 20:45:58-018569 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-018782 util-scheduler-8620 DEBUG Adding task: 1631 / 0x465ee60
Jul 07 20:45:58-093026 util-scheduler-8620 DEBUG Checking readiness of task: 1631 / 0x465ee60
Jul 07 20:45:58-093409 util-scheduler-8620 DEBUG Checking readiness of task: 1627 / 0x46620a0
Jul 07 20:45:58-093612 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:58-093810 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-094009 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-094207 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-094409 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-094812 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-095017 util-scheduler-8620 DEBUG Running task: 1627 / 0x46620a0
Jul 07 20:45:58-095441 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:58-095696 util-scheduler-8620 DEBUG Adding task: 1632 / 0x4662248
Jul 07 20:45:58-095918 util-scheduler-8620 DEBUG Running task: 1631 / 0x465ee60
Jul 07 20:45:58-096323 util-8620 DEBUG receive_ready read 104/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:45:58-096555 util-scheduler-8620 DEBUG Adding task: 1633 / 0x465f008
Jul 07 20:45:58-096852 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:58-097053 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-097275 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-097469 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-097663 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-097855 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-098051 util-scheduler-8620 DEBUG Running task: 1633 / 0x465f008
Jul 07 20:45:58-098247 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:45:58-098504 nse-api-8620 DEBUG Received information about peer `P00P' from peerinfo database
Jul 07 20:45:58-098789 cadet-hll-8620 DEBUG  hello for P00P (64 bytes), expires on Tue Jul 08 08:45:58 2014
Jul 07 20:45:58-099015 cadet-p2p-8620 DEBUG set hello for P00P
Jul 07 20:45:58-099307 cadet-p2p-8620 DEBUG  merge into 0x5184108 (64 bytes)
Jul 07 20:45:58-099510 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-099730 util-scheduler-8620 DEBUG Adding task: 1634 / 0x465ee60
Jul 07 20:45:58-099934 util-scheduler-8620 DEBUG Running task: 1632 / 0x4662248
Jul 07 20:45:58-100128 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:45:58-100332 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:45:58-100565 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `V8XX'
Jul 07 20:45:58-100836 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:45:58-101088 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:45:58-101361 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-101570 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:45:58-101814 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-102020 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-102209 cadet-con-8620 DEBUG  PID 0 (expected 0+)
Jul 07 20:45:58-102389 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:45:58-102582 util-scheduler-8620 DEBUG Canceling task: 1621 / 0x4d707d0
Jul 07 20:45:58-102808 util-scheduler-8620 DEBUG Adding task: 1635 / 0x4d707d0
Jul 07 20:45:58-102987 cadet-con-8620 DEBUG   message for us!
Jul 07 20:45:58-103245 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:45:58-103456 util-scheduler-8620 DEBUG Adding task: 1636 / 0x4d5e5d8
Jul 07 20:45:58-103641 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:45:58-103808 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:45:58-107767 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:45:58-108617 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:45:58-108823 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:45:58-112082 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on V8XX
Jul 07 20:45:58-112339 cadet-chn-8620 DEBUG   channel confirm FWD V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-112889 cadet-chn-8620 DEBUG   !! retry timer confirm 500 ms
Jul 07 20:45:58-113102 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:58-113310 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:58-113502 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:58-113688 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:58-113875 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:58-114142 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:58-114459 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-114672 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:58-114922 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:58-116197 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:58-116463 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-116657 cadet-loc-8620 DEBUG send local FWD ack on 80000002 towards 0x4d5c6d8
Jul 07 20:45:58-116899 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:45:58-117107 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:45:58-117345 util-scheduler-8620 DEBUG Adding task: 1637 / 0x4d5c418
Jul 07 20:45:58-117532 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:45:58-117721 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:45:58-117904 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:58-118084 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:58-118272 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:45:58-118446 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:58-118614 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:58-118801 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:45:58-118988 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:45:58-119184 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:58-119368 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:45:58-119545 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:45:58-119718 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:58-119923 core-api-8620 DEBUG Aborting transmission request to core for 96 bytes to `V8XX'
Jul 07 20:45:58-120168 cadet-chn-8620 DEBUG   sending channel BCK ack for channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-120419 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-120630 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:45:58-120829 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:58-121008 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:58-121208 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:58-121390 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:58-121564 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:58-121848 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:58-122068 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-122241 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:58-122473 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:58-122657 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:58-122960 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:58-123131 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:58-123314 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:58-126718 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:58-128060 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:58-128332 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:58-128531 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:45:58-132009 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:58-132272 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:58-132456 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:58-132676 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:58-132872 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:45:58-133145 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:45:58-133366 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:45:58-133543 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:45:58-133717 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:45:58-133887 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:45:58-134066 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:45:58-134298 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-134506 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-134819 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:45:58-135017 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:58-135241 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:58-135452 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:58-135627 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:58-135831 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:45:58-136244 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:45:58-136477 util-scheduler-8620 DEBUG Adding task: 1638 / 0x4d6ff98
Jul 07 20:45:58-136658 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:58-136863 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:58-137039 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:58-137233 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:58-137474 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-137669 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:45:58-137847 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:45:58-138044 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:58-138275 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:58-138451 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:58-138625 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:58-138796 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:58-139187 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:45:58-139370 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:45:58-140161 cadet-con-8620 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 20:45:58-140449 cadet-con-8620 INFO --> {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:45:58-140643 cadet-con-8620 DEBUG  ack 64
Jul 07 20:45:58-140828 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:45:58-141069 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-141304 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-141603 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:45:58-141804 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:58-142030 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:58-142213 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:58-142388 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:58-142591 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:58-142795 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:58-142972 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:58-143148 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:58-143386 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-143570 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:45:58-143745 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:58-143980 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-144174 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:45:58-144351 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:45:58-144550 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:58-144736 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-144954 util-scheduler-8620 DEBUG Adding task: 1639 / 0x46620a0
Jul 07 20:45:58-145269 util-scheduler-8620 DEBUG Checking readiness of task: 1639 / 0x46620a0
Jul 07 20:45:58-145469 util-scheduler-8620 DEBUG Checking readiness of task: 1637 / 0x4d5c418
Jul 07 20:45:58-145663 util-scheduler-8620 DEBUG Checking readiness of task: 1636 / 0x4d5e5d8
Jul 07 20:45:58-145855 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-146047 util-scheduler-8620 DEBUG Checking readiness of task: 1595 / 0x4663d68
Jul 07 20:45:58-146239 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-146429 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-146619 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-146833 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-147023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-147218 util-scheduler-8620 DEBUG Running task: 1595 / 0x4663d68
Jul 07 20:45:58-147640 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:45:58-147889 util-scheduler-8620 DEBUG Adding task: 1640 / 0x4663f10
Jul 07 20:45:58-148106 util-scheduler-8620 DEBUG Running task: 1636 / 0x4d5e5d8
Jul 07 20:45:58-148294 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:45:58-148476 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-148648 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-148884 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:45:58-149216 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:45:58-149484 util-scheduler-8620 DEBUG Running task: 1637 / 0x4d5c418
Jul 07 20:45:58-149679 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:45:58-149857 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-150051 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:45:58-150366 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:45:58-150578 util-scheduler-8620 DEBUG Running task: 1638 / 0x4d6ff98
Jul 07 20:45:58-150780 util-scheduler-8620 DEBUG Canceling task: 1628 / 0x4d6ff98
Jul 07 20:45:58-151010 util-scheduler-8620 DEBUG Adding task: 1641 / 0x4d6ff98
Jul 07 20:45:58-151246 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:58-151456 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:58-151664 util-scheduler-8620 DEBUG Adding task: 1642 / 0x46620a0
Jul 07 20:45:58-151921 util-scheduler-8620 DEBUG Checking readiness of task: 1642 / 0x46620a0
Jul 07 20:45:58-152121 util-scheduler-8620 DEBUG Checking readiness of task: 1639 / 0x46620a0
Jul 07 20:45:58-152314 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-152507 util-scheduler-8620 DEBUG Checking readiness of task: 973 / 0x4d5c418
Jul 07 20:45:58-152697 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-152886 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-153073 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-153287 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-153479 util-scheduler-8620 DEBUG Running task: 973 / 0x4d5c418
Jul 07 20:45:58-153863 util-8620 DEBUG receive_ready read 88/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:45:58-154071 util-8620 DEBUG Server receives 88 bytes from `<unbound UNIX client>'.
Jul 07 20:45:58-154276 util-8620 DEBUG Server-mst receives 88 bytes with 0 bytes already in private buffer
Jul 07 20:45:58-154462 util-8620 DEBUG Server-mst has 88 bytes left in inbound buffer
Jul 07 20:45:58-154643 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:45:58-154833 util-8620 DEBUG Server schedules transmission of 88-byte message of type 285 to client.
Jul 07 20:45:58-155049 util-scheduler-8620 DEBUG Adding task: 1643 / 0x4d5c578
Jul 07 20:45:58-155230 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:45:58-155403 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:45:58-155579 cadet-loc-8620 DEBUG   on channel 80000002
Jul 07 20:45:58-155798 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:45:58-156054 cadet-chn-8620 INFO ===> {              DATA} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-156253 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:45:58-156454 cadet-chn-8620 DEBUG !!! SAVE 0 {              DATA}
Jul 07 20:45:58-156640 cadet-chn-8620 DEBUG   at 0x51720d0
Jul 07 20:45:58-156842 cadet-chn-8620 DEBUG   new chq: 0x51ae240
Jul 07 20:45:58-157046 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:45:58-157265 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:58-157445 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:58-157626 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:58-157806 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:58-157982 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:58-158150 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:58-158364 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-158536 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:58-158770 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:45:58-158954 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:58-159252 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:45:58-159422 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:58-159606 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:45:58-163038 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:45:58-163871 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:45:58-164126 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:45:58-164318 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:45:58-167940 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:45:58-168240 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:45:58-168423 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:45:58-168667 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:45:58-168865 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:45:58-169145 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection CMHCKRVP (->V8XX) (172 bytes)
Jul 07 20:45:58-169370 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:45:58-169547 cadet-con-8620 DEBUG last pid sent 0
Jul 07 20:45:58-169756 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:45:58-169935 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:45:58-170169 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-170375 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-170689 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 172)
Jul 07 20:45:58-170915 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:45:58-171139 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:58-171321 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:58-171495 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:58-171695 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:45:58-171920 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:58-172097 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:58-172271 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:58-172509 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-172692 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:45:58-172889 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:58-173123 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-173344 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:45:58-173520 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:45:58-173751 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-173963 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:45:58-174142 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:45:58-174338 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:58-174544 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:58-174723 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:58-174903 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:58-175105 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:58-175304 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:58-175473 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:58-175689 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-175861 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:58-176114 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:58-176300 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:58-176471 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:45:58-176644 cadet-chn-8620 DEBUG  gap ok: 0 - 1
Jul 07 20:45:58-176847 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:58-177023 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:58-177244 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:58-177423 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:58-177598 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:58-177765 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:58-177984 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-178158 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:58-178413 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:58-178600 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:58-178774 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:45:58-179004 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:58-179194 cadet-loc-8620 DEBUG send local FWD ack on 80000002 towards 0x4d5c6d8
Jul 07 20:45:58-179438 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:45:58-179648 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:45:58-179869 util-scheduler-8620 DEBUG Adding task: 1644 / 0x4d5c418
Jul 07 20:45:58-180060 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:45:58-180250 util-scheduler-8620 DEBUG Canceling task: 1643 / 0x4d5c578
Jul 07 20:45:58-180502 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:45:58-180689 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:45:58-180905 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:45:58-181127 util-scheduler-8620 DEBUG Adding task: 1645 / 0x4d5c418
Jul 07 20:45:58-181362 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:45:58-181632 util-scheduler-8620 DEBUG Running task: 1642 / 0x46620a0
Jul 07 20:45:58-181826 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:58-182005 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-182175 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-182356 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:58-182577 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:58-182769 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:58-183065 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-183275 util-scheduler-8620 DEBUG Running task: 1640 / 0x4663f10
Jul 07 20:45:58-183468 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:45:58-183687 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-183890 util-scheduler-8620 DEBUG Adding task: 1646 / 0x4663d68
Jul 07 20:45:58-184075 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:45:58-184295 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 11601
Jul 07 20:45:58-184486 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 11601 Bps
Jul 07 20:45:58-184757 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 14443 Bps, last update was 1196 ms ago
Jul 07 20:45:58-184992 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11601 Bps, last update was 255 µs ago
Jul 07 20:45:58-185257 util-scheduler-8620 DEBUG Adding task: 1647 / 0x4d6fa48
Jul 07 20:45:58-185522 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-185739 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-185929 util-scheduler-8620 DEBUG Checking readiness of task: 1644 / 0x4d5c418
Jul 07 20:45:58-186120 util-scheduler-8620 DEBUG Checking readiness of task: 1639 / 0x46620a0
Jul 07 20:45:58-186309 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-186499 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-186686 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-186898 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-187085 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-187276 util-scheduler-8620 DEBUG Running task: 1644 / 0x4d5c418
Jul 07 20:45:58-187632 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:45:58-187811 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-188026 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:45:58-188310 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:45:58-188516 util-scheduler-8620 DEBUG Running task: 1647 / 0x4d6fa48
Jul 07 20:45:58-343645 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-343989 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-344184 util-scheduler-8620 DEBUG Checking readiness of task: 1639 / 0x46620a0
Jul 07 20:45:58-344378 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-344570 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-344760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-344950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-345138 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-345356 util-scheduler-8620 DEBUG Running task: 1639 / 0x46620a0
Jul 07 20:45:58-345774 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:58-346029 util-scheduler-8620 DEBUG Adding task: 1648 / 0x4662248
Jul 07 20:45:58-346303 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-346496 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-346685 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-346874 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-347062 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-347250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-347438 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-347626 util-scheduler-8620 DEBUG Running task: 1648 / 0x4662248
Jul 07 20:45:58-347815 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:58-348014 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:58-348243 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 20:45:58-348507 cadet-con-8620 INFO <-- {              POLL} on connection CMHCKRVP from V8XX
Jul 07 20:45:58-348760 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-348969 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-349154 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:45:58-350010 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:45:58-352011 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:58-352222 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:58-352398 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:58-352602 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:58-352833 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:45:58-353018 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:45:58-353226 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:45:58-353594 cadet-con-8620 DEBUG  same ACK already in queue
Jul 07 20:45:58-353789 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-354023 util-scheduler-8620 DEBUG Adding task: 1649 / 0x46620a0
Jul 07 20:45:58-639890 util-scheduler-8620 DEBUG Checking readiness of task: 1649 / 0x46620a0
Jul 07 20:45:58-640264 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-640460 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-640651 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-640843 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-641040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-641250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-641441 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-641632 util-scheduler-8620 DEBUG Running task: 1619 / 0x5e31aa4
Jul 07 20:45:58-641904 cadet-con-8620 DEBUG  *** Polling connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:58-642086 cadet-con-8620 DEBUG  *** last pid sent: 0!
Jul 07 20:45:58-642361 cadet-con-8620 INFO --> {              POLL} ( 0) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:45:58-642551 cadet-con-8620 DEBUG  poll 0
Jul 07 20:45:58-642727 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 4
Jul 07 20:45:58-642964 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:45:58-643174 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:45:58-643478 cadet-p2p-8620 INFO que {              POLL} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:45:58-643675 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:45:58-643900 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-644083 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:58-644257 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:58-644464 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:45:58-644673 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:58-644856 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:58-645036 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:58-645319 cadet-p2p-8620 DEBUG QQQ  - {              POLL} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-645516 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:45:58-645701 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:45:58-645964 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-646174 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:58-646359 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:58-646608 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-648081 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:58-648291 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:58-648695 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-649042 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:58-649395 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:58-649784 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-649987 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:58-650313 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:58-650662 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:58-650998 util-scheduler-8620 DEBUG Checking readiness of task: 1649 / 0x46620a0
Jul 07 20:45:58-651217 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-651444 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-651745 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-651944 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-652138 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-652326 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-652515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-652706 util-scheduler-8620 DEBUG Running task: 1649 / 0x46620a0
Jul 07 20:45:58-653125 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:58-653401 util-scheduler-8620 DEBUG Adding task: 1650 / 0x4662248
Jul 07 20:45:58-653664 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-653857 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-654046 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-654236 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-654425 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-654613 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-654801 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-654990 util-scheduler-8620 DEBUG Running task: 1650 / 0x4662248
Jul 07 20:45:58-655179 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:58-655378 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:58-655601 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:45:58-655807 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:58-656012 util-scheduler-8620 DEBUG Adding task: 1651 / 0x46620a0
Jul 07 20:45:58-656199 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-656401 util-scheduler-8620 DEBUG Adding task: 1652 / 0x46620a0
Jul 07 20:45:58-656643 util-scheduler-8620 DEBUG Checking readiness of task: 1652 / 0x46620a0
Jul 07 20:45:58-656835 util-scheduler-8620 DEBUG Checking readiness of task: 1651 / 0x46620a0
Jul 07 20:45:58-657025 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-657235 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-657425 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-657615 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-657802 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-657991 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-658178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-658368 util-scheduler-8620 DEBUG Running task: 1651 / 0x46620a0
Jul 07 20:45:58-658553 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:58-658730 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-658902 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-659092 util-scheduler-8620 DEBUG Canceling task: 1616 / 0x5e2b838
Jul 07 20:45:58-659317 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:45:58-659535 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:45:58-659769 cadet-p2p-8620 DEBUG Checking 0x51c4920 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-660002 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:45:58-660180 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:58-660368 cadet-p2p-8620 DEBUG   raw {              POLL}
Jul 07 20:45:58-660636 cadet-p2p-8620 INFO snd {              POLL} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:45:58-660829 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:58-661031 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:58-661240 cadet-con-8620 DEBUG  sent FWD {              POLL}
Jul 07 20:45:58-661414 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:58-661583 cadet-con-8620 DEBUG  *** POLL sent for , scheduling new one!
Jul 07 20:45:58-661794 util-scheduler-8620 DEBUG Adding task: 1653 / 0x5e31aa4
Jul 07 20:45:58-661975 cadet-con-8620 DEBUG  task 1653
Jul 07 20:45:58-662158 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 5
Jul 07 20:45:58-662334 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:58-662554 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-662785 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-662968 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:58-663141 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:58-663359 cadet-p2p-8620 DEBUG Checking 0x4dbd080 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-663596 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-663825 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-664006 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:45:58-664177 cadet-con-8620 DEBUG  not sendable
Jul 07 20:45:58-664395 cadet-p2p-8620 DEBUG Checking 0x4dbd080 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-664572 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:58-664776 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:45:58-664992 util-scheduler-8620 DEBUG Adding task: 1654 / 0x5e2b838
Jul 07 20:45:58-665175 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:58-665381 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:58-665587 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:45:58-665768 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:45:58-665949 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:45:58-666197 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-666401 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:45:58-666580 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:45:58-666819 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-667022 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:58-667200 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:58-667439 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-667631 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:45:58-667806 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:45:58-668038 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:45:58-668231 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:45:58-668406 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:45:58-668603 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:45:58-668809 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:45:58-668992 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:58-669228 util-scheduler-8620 DEBUG Adding task: 1655 / 0x5e2b838
Jul 07 20:45:58-669462 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:58-669660 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:58-669869 util-scheduler-8620 DEBUG Adding task: 1656 / 0x46620a0
Jul 07 20:45:58-670070 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:58-670849 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-671054 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:58-671311 util-scheduler-8620 DEBUG Checking readiness of task: 1656 / 0x46620a0
Jul 07 20:45:58-671507 util-scheduler-8620 DEBUG Checking readiness of task: 1652 / 0x46620a0
Jul 07 20:45:58-671698 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-671911 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-672101 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-672290 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-672479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-672667 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-672854 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-673046 util-scheduler-8620 DEBUG Running task: 1656 / 0x46620a0
Jul 07 20:45:58-673252 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:58-673430 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-673601 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-673778 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:58-673974 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:58-674162 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:58-674444 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-674650 util-scheduler-8620 DEBUG Running task: 1654 / 0x5e2b838
Jul 07 20:45:58-674844 util-scheduler-8620 DEBUG Canceling task: 1655 / 0x5e2b838
Jul 07 20:45:58-675060 util-scheduler-8620 DEBUG Adding task: 1657 / 0x5e2b838
Jul 07 20:45:58-675277 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:45:58-675471 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:58-675668 util-scheduler-8620 DEBUG Adding task: 1658 / 0x46620a0
Jul 07 20:45:58-675907 util-scheduler-8620 DEBUG Checking readiness of task: 1658 / 0x46620a0
Jul 07 20:45:58-676099 util-scheduler-8620 DEBUG Checking readiness of task: 1652 / 0x46620a0
Jul 07 20:45:58-676288 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-676477 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-676665 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-676855 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-677042 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-677250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-677440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-677630 util-scheduler-8620 DEBUG Running task: 1658 / 0x46620a0
Jul 07 20:45:58-677816 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:58-677994 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-678164 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-678343 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:58-678537 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:58-678727 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:58-679020 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-959352 util-scheduler-8620 DEBUG Checking readiness of task: 1652 / 0x46620a0
Jul 07 20:45:58-959733 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-959938 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-960134 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-960329 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-960519 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-960711 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-960905 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-961129 util-scheduler-8620 DEBUG Running task: 1652 / 0x46620a0
Jul 07 20:45:58-961576 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:58-961833 util-scheduler-8620 DEBUG Adding task: 1659 / 0x4662248
Jul 07 20:45:58-962111 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-962305 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-962496 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-962685 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-962874 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-963062 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-963251 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-963438 util-scheduler-8620 DEBUG Running task: 1659 / 0x4662248
Jul 07 20:45:58-963629 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:58-963827 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:58-964057 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:45:58-964264 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:58-964469 util-scheduler-8620 DEBUG Adding task: 1660 / 0x46620a0
Jul 07 20:45:58-964657 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-964862 util-scheduler-8620 DEBUG Adding task: 1661 / 0x46620a0
Jul 07 20:45:58-965103 util-scheduler-8620 DEBUG Checking readiness of task: 1661 / 0x46620a0
Jul 07 20:45:58-965315 util-scheduler-8620 DEBUG Checking readiness of task: 1660 / 0x46620a0
Jul 07 20:45:58-965507 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-965696 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-965884 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-966074 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-966262 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-966450 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-966638 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-966829 util-scheduler-8620 DEBUG Running task: 1660 / 0x46620a0
Jul 07 20:45:58-967013 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:58-967190 util-8620 DEBUG process_notify is running
Jul 07 20:45:58-967361 util-8620 DEBUG client_notify is running
Jul 07 20:45:58-967551 util-scheduler-8620 DEBUG Canceling task: 1592 / 0x4d5c9e8
Jul 07 20:45:58-967774 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:45:58-967993 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:45:58-968232 cadet-p2p-8620 DEBUG Checking 0x513ff20 towards HS92G30M (->KNAS)
Jul 07 20:45:58-968464 cadet-p2p-8620 DEBUG   on connection HS92G30M (->KNAS) FWD
Jul 07 20:45:58-968642 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:58-968831 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:58-969098 cadet-p2p-8620 INFO snd {               ACK} ( 84) on connection HS92G30M (->KNAS) (0x4d61c30) FWD (size 40)
Jul 07 20:45:58-969312 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:58-969491 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:58-969678 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:58-969851 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:58-970033 cadet-con-8620 DEBUG  C_P- 0x4d61c30 1
Jul 07 20:45:58-970206 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:58-970385 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:58-970583 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:45:58-970761 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:58-970942 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:58-971168 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:45:58-971390 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:45:58-971583 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:58-971785 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:58-971988 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:58-972874 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:58-980318 util-scheduler-8620 DEBUG Checking readiness of task: 1661 / 0x46620a0
Jul 07 20:45:58-980605 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-980800 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-980999 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-981211 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-981405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-981596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-981787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-981981 util-scheduler-8620 DEBUG Running task: 1661 / 0x46620a0
Jul 07 20:45:58-982402 util-8620 DEBUG receive_ready read 152/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:58-982655 util-scheduler-8620 DEBUG Adding task: 1662 / 0x4662248
Jul 07 20:45:58-982923 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-983119 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-983310 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-983502 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-983692 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-983883 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-984071 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-984261 util-scheduler-8620 DEBUG Running task: 1662 / 0x4662248
Jul 07 20:45:58-984450 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:58-984651 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:58-984875 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:45:58-985137 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:45:58-985416 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-985624 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-985807 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:45:58-985980 cadet-con-8620 DEBUG   ACK 64 (was 64)
Jul 07 20:45:58-986208 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:58-986438 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-986642 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-986824 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:45:58-987027 util-scheduler-8620 DEBUG Adding task: 1663 / 0x4662248
Jul 07 20:45:58-987263 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:58-987456 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:58-987645 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:58-987835 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:58-988022 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:58-988210 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:58-988398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:58-988611 util-scheduler-8620 DEBUG Running task: 1663 / 0x4662248
Jul 07 20:45:58-988800 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:45:58-988991 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:45:58-989225 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 20:45:58-989475 cadet-con-8620 INFO <-- {              POLL} on connection CMHCKRVP from V8XX
Jul 07 20:45:58-989726 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:45:58-989940 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:45:58-990131 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:45:58-990310 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:45:58-990548 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:58-990733 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:45:58-990916 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:45:58-991090 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:45:58-991326 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:45:58-991509 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:45:58-991692 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:45:58-991876 cadet-con-8620 DEBUG  same ACK already in queue
Jul 07 20:45:58-992057 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:58-992277 util-scheduler-8620 DEBUG Adding task: 1664 / 0x46620a0
Jul 07 20:45:59-177487 util-scheduler-8620 DEBUG Checking readiness of task: 1664 / 0x46620a0
Jul 07 20:45:59-177879 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-178077 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-178270 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-178467 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-178662 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-178851 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-179042 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-179238 util-scheduler-8620 DEBUG Running task: 1664 / 0x46620a0
Jul 07 20:45:59-179664 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:59-179920 util-scheduler-8620 DEBUG Adding task: 1665 / 0x4662248
Jul 07 20:45:59-180202 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-180394 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-180584 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-180774 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-180968 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-181157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-181373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-181562 util-scheduler-8620 DEBUG Running task: 1665 / 0x4662248
Jul 07 20:45:59-181753 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:59-181951 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:59-182180 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:59-182385 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-182593 util-scheduler-8620 DEBUG Adding task: 1666 / 0x46620a0
Jul 07 20:45:59-182779 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:59-182984 util-scheduler-8620 DEBUG Adding task: 1667 / 0x46620a0
Jul 07 20:45:59-183226 util-scheduler-8620 DEBUG Checking readiness of task: 1667 / 0x46620a0
Jul 07 20:45:59-183421 util-scheduler-8620 DEBUG Checking readiness of task: 1666 / 0x46620a0
Jul 07 20:45:59-183612 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-183831 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-184021 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-184212 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-184400 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-184589 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-184776 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-184967 util-scheduler-8620 DEBUG Running task: 1666 / 0x46620a0
Jul 07 20:45:59-185153 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-185359 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-185536 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-185735 util-scheduler-8620 DEBUG Canceling task: 1641 / 0x4d6ff98
Jul 07 20:45:59-185979 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:45:59-186209 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:59-186475 cadet-p2p-8620 DEBUG Checking 0x51acd38 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-186716 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:59-186897 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:45:59-187096 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:45:59-187375 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:45:59-187576 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:59-187760 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:59-187951 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:45:59-188125 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:59-188308 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:45:59-188482 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:59-188702 cadet-p2p-8620 DEBUG Checking 0x51ac328 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-188935 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-189118 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:59-189321 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-189549 cadet-p2p-8620 DEBUG Checking 0x51ac328 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-189777 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-189957 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:59-190130 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-190295 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:59-190499 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:45:59-190722 util-scheduler-8620 DEBUG Adding task: 1668 / 0x4d6ff98
Jul 07 20:45:59-190901 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:59-191081 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:45:59-191279 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:59-191453 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:45:59-191626 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:59-191863 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:59-192058 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:45:59-192234 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:45:59-192466 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:59-192658 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:45:59-192834 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:45:59-193030 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:59-193255 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:45:59-193439 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:45:59-193645 util-scheduler-8620 DEBUG Adding task: 1669 / 0x4d6ff98
Jul 07 20:45:59-193865 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:59-194089 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-194296 util-scheduler-8620 DEBUG Adding task: 1670 / 0x46620a0
Jul 07 20:45:59-194498 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:45:59-196666 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-197071 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:59-197410 util-scheduler-8620 DEBUG Checking readiness of task: 1670 / 0x46620a0
Jul 07 20:45:59-197613 util-scheduler-8620 DEBUG Checking readiness of task: 1667 / 0x46620a0
Jul 07 20:45:59-197806 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-197996 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-198187 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-198378 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-198568 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-198759 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-198948 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-199143 util-scheduler-8620 DEBUG Running task: 1670 / 0x46620a0
Jul 07 20:45:59-199330 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-199509 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-199683 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-199864 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:59-200065 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:59-200257 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:59-200556 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-200765 util-scheduler-8620 DEBUG Running task: 1668 / 0x4d6ff98
Jul 07 20:45:59-200966 util-scheduler-8620 DEBUG Canceling task: 1669 / 0x4d6ff98
Jul 07 20:45:59-201264 util-scheduler-8620 DEBUG Adding task: 1671 / 0x4d6ff98
Jul 07 20:45:59-201501 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:59-201705 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-201913 util-scheduler-8620 DEBUG Adding task: 1672 / 0x46620a0
Jul 07 20:45:59-202161 util-scheduler-8620 DEBUG Checking readiness of task: 1672 / 0x46620a0
Jul 07 20:45:59-202355 util-scheduler-8620 DEBUG Checking readiness of task: 1667 / 0x46620a0
Jul 07 20:45:59-202589 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-202781 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-202972 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-203163 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-203354 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-203543 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-203731 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-203921 util-scheduler-8620 DEBUG Running task: 1672 / 0x46620a0
Jul 07 20:45:59-204105 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-204280 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-204449 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-204625 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:59-204815 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:59-205003 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:59-205325 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-207865 util-scheduler-8620 DEBUG Checking readiness of task: 1667 / 0x46620a0
Jul 07 20:45:59-208069 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-208262 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-208452 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-208643 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-208908 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-209099 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-209315 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-209507 util-scheduler-8620 DEBUG Running task: 1667 / 0x46620a0
Jul 07 20:45:59-209916 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:59-210560 util-scheduler-8620 DEBUG Adding task: 1673 / 0x4662248
Jul 07 20:45:59-210824 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-211018 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-211209 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-211399 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-211589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-211778 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-211967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-212160 util-scheduler-8620 DEBUG Running task: 1673 / 0x4662248
Jul 07 20:45:59-212350 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:59-212548 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:59-212769 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:59-212982 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-213183 util-scheduler-8620 DEBUG Adding task: 1674 / 0x46620a0
Jul 07 20:45:59-213395 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:59-213600 util-scheduler-8620 DEBUG Adding task: 1675 / 0x46620a0
Jul 07 20:45:59-213842 util-scheduler-8620 DEBUG Checking readiness of task: 1675 / 0x46620a0
Jul 07 20:45:59-214033 util-scheduler-8620 DEBUG Checking readiness of task: 1674 / 0x46620a0
Jul 07 20:45:59-214224 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-214413 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-214604 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-214794 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-214983 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-215173 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-215360 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-215551 util-scheduler-8620 DEBUG Running task: 1674 / 0x46620a0
Jul 07 20:45:59-215796 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-215974 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-216143 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-216330 util-scheduler-8620 DEBUG Canceling task: 1671 / 0x4d6ff98
Jul 07 20:45:59-216551 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:45:59-216769 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:59-217010 cadet-p2p-8620 DEBUG Checking 0x51ac328 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-217267 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-217453 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:45:59-217647 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-217869 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:59-218047 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:45:59-218222 cadet-p2p-8620 DEBUG   payload ID 1
Jul 07 20:45:59-218509 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:45:59-218704 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:59-218883 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:59-219071 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:59-219259 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:45:59-219488 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:59-219664 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:59-219835 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:45:59-220006 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:59-220203 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:45:59-221757 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:45:59-221943 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:45:59-222153 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:59-222334 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:59-222517 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:59-222697 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:59-222874 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:59-223043 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:59-223260 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:59-223431 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:59-223664 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:59-223850 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:59-224030 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:59-224220 util-scheduler-8620 DEBUG Canceling task: 1374 / 0x4d707d0
Jul 07 20:45:59-224435 util-scheduler-8620 DEBUG Adding task: 1676 / 0x4d707d0
Jul 07 20:45:59-224685 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:59-224864 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:45:59-225043 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 1
Jul 07 20:45:59-225237 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:59-225461 cadet-p2p-8620 DEBUG Checking 0x51c1eb0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-225691 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-225873 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:45:59-226046 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-226275 cadet-p2p-8620 DEBUG Checking 0x51c1eb0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-226504 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-226685 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:45:59-226859 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-227024 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:45:59-227228 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `V8XX'
Jul 07 20:45:59-227441 util-scheduler-8620 DEBUG Adding task: 1677 / 0x4d6ff98
Jul 07 20:45:59-227619 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:45:59-227795 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:45:59-227992 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:59-228168 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:45:59-228343 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:45:59-228580 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:45:59-228776 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:45:59-228953 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:45:59-229150 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:59-229379 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:45:59-229563 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:45:59-229786 util-scheduler-8620 DEBUG Adding task: 1678 / 0x4d6ff98
Jul 07 20:45:59-230007 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:59-230203 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-230407 util-scheduler-8620 DEBUG Adding task: 1679 / 0x46620a0
Jul 07 20:45:59-230608 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:45:59-231656 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-231862 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:45:59-232119 util-scheduler-8620 DEBUG Checking readiness of task: 1679 / 0x46620a0
Jul 07 20:45:59-232316 util-scheduler-8620 DEBUG Checking readiness of task: 1675 / 0x46620a0
Jul 07 20:45:59-232508 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-232699 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-232890 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-233083 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-233299 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-233490 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-233679 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-233873 util-scheduler-8620 DEBUG Running task: 1679 / 0x46620a0
Jul 07 20:45:59-234058 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-234236 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-234407 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-234586 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:59-234780 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:59-234970 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:59-235266 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-235475 util-scheduler-8620 DEBUG Running task: 1677 / 0x4d6ff98
Jul 07 20:45:59-235669 util-scheduler-8620 DEBUG Canceling task: 1678 / 0x4d6ff98
Jul 07 20:45:59-235883 util-scheduler-8620 DEBUG Adding task: 1680 / 0x4d6ff98
Jul 07 20:45:59-236100 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:45:59-236307 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-236506 util-scheduler-8620 DEBUG Adding task: 1681 / 0x46620a0
Jul 07 20:45:59-236749 util-scheduler-8620 DEBUG Checking readiness of task: 1681 / 0x46620a0
Jul 07 20:45:59-236942 util-scheduler-8620 DEBUG Checking readiness of task: 1675 / 0x46620a0
Jul 07 20:45:59-237133 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-237352 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-237543 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-237735 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-237925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-238115 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-238303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-238495 util-scheduler-8620 DEBUG Running task: 1681 / 0x46620a0
Jul 07 20:45:59-238678 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-238854 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-239023 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-239200 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:45:59-239389 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:59-239603 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:45:59-239894 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:45:59-244360 util-scheduler-8620 DEBUG Checking readiness of task: 1675 / 0x46620a0
Jul 07 20:45:59-244568 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-244761 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-244953 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-245144 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-245424 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-245615 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-245804 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-245996 util-scheduler-8620 DEBUG Running task: 1675 / 0x46620a0
Jul 07 20:45:59-246400 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:45:59-246633 util-scheduler-8620 DEBUG Adding task: 1682 / 0x4662248
Jul 07 20:45:59-246883 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-247076 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-247266 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-247458 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-247646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-247835 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-248023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-248212 util-scheduler-8620 DEBUG Running task: 1682 / 0x4662248
Jul 07 20:45:59-248402 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:45:59-248596 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:45:59-248812 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:45:59-249010 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:45:59-249234 util-scheduler-8620 DEBUG Adding task: 1683 / 0x46620a0
Jul 07 20:45:59-249420 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:45:59-249622 util-scheduler-8620 DEBUG Adding task: 1684 / 0x46620a0
Jul 07 20:45:59-249862 util-scheduler-8620 DEBUG Checking readiness of task: 1684 / 0x46620a0
Jul 07 20:45:59-250054 util-scheduler-8620 DEBUG Checking readiness of task: 1683 / 0x46620a0
Jul 07 20:45:59-250246 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:45:59-250435 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:45:59-250625 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:45:59-250814 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:45:59-251003 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:45:59-251190 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:45:59-251379 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:45:59-251569 util-scheduler-8620 DEBUG Running task: 1683 / 0x46620a0
Jul 07 20:45:59-251754 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:45:59-251928 util-8620 DEBUG process_notify is running
Jul 07 20:45:59-252099 util-8620 DEBUG client_notify is running
Jul 07 20:45:59-252282 util-scheduler-8620 DEBUG Canceling task: 1680 / 0x4d6ff98
Jul 07 20:45:59-252502 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 172 bytes.
Jul 07 20:45:59-252717 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:45:59-253010 cadet-p2p-8620 DEBUG Checking 0x51c1eb0 towards CMHCKRVP (->V8XX)
Jul 07 20:45:59-253281 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:45:59-253465 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:45:59-253639 cadet-con-8620 DEBUG  sendable
Jul 07 20:45:59-253859 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:45:59-254036 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:45:59-254209 cadet-p2p-8620 DEBUG   payload ID 2
Jul 07 20:45:59-254488 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 172)
Jul 07 20:45:59-254683 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:45:59-254860 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:45:59-255046 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:45:59-255219 cadet-con-8620 DEBUG  calling cont
Jul 07 20:45:59-255387 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:45:59-255574 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:45:59-255751 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:45:59-255974 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 500 ms
Jul 07 20:45:59-256146 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:45:59-256374 cadet-chn-8620 DEBUG !! using delay 2 s
Jul 07 20:45:59-256570 util-scheduler-8620 DEBUG Adding task: 1685 / 0x4d65218
Jul 07 20:45:59-256771 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:45:59-256999 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:45:59-257173 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:45:59-257371 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:45:59-257542 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:45:59-257738 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:45:59-257912 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:45:59-258086 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:45:59-258282 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:45:59-258460 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:45:59-258641 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:45:59-258820 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:45:59-258996 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:45:59-259165 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:45:59-259379 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:45:59-259552 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:45:59-259783 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:45:59-259967 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:45:59-260144 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:45:59-260328 util-scheduler-8620 DEBUG Canceling task: 1676 / 0x4d707d0
Jul 07 20:45:59-260540 util-scheduler-8620 DEBUG Adding task: 1686 / 0x4d707d0
Jul 07 20:45:59-260780 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:45:59-260957 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:45:59-261133 cadet-con-8620 DEBUG !   accounting pid 2
Jul 07 20:45:59-261325 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:45:59-261506 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:45:59-261705 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:45:59-261893 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:45:59-262067 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:45:59-262268 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:45:59-262471 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 172 bytes.
Jul 07 20:45:59-262654 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:45:59-262831 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:45:59-263020 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:45:59-264193 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:00-003853 util-scheduler-8620 DEBUG Checking readiness of task: 1684 / 0x46620a0
Jul 07 20:46:00-004282 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-004484 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-004681 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-004876 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-005070 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-005301 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-005506 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-005705 util-scheduler-8620 DEBUG Running task: 1684 / 0x46620a0
Jul 07 20:46:00-006332 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:00-006600 util-scheduler-8620 DEBUG Adding task: 1687 / 0x4662248
Jul 07 20:46:00-006886 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-007083 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-007278 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-007470 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-007663 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-007854 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-008047 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-008239 util-scheduler-8620 DEBUG Running task: 1687 / 0x4662248
Jul 07 20:46:00-008434 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:00-008637 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:00-008870 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:00-009080 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:00-009323 util-scheduler-8620 DEBUG Adding task: 1688 / 0x46620a0
Jul 07 20:46:00-009515 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:00-009723 util-scheduler-8620 DEBUG Adding task: 1689 / 0x46620a0
Jul 07 20:46:00-009972 util-scheduler-8620 DEBUG Checking readiness of task: 1689 / 0x46620a0
Jul 07 20:46:00-010169 util-scheduler-8620 DEBUG Checking readiness of task: 1688 / 0x46620a0
Jul 07 20:46:00-010364 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-010558 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-010750 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-010943 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-011135 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-011330 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-011523 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-011717 util-scheduler-8620 DEBUG Running task: 1688 / 0x46620a0
Jul 07 20:46:00-011905 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:00-012086 util-8620 DEBUG process_notify is running
Jul 07 20:46:00-012262 util-8620 DEBUG client_notify is running
Jul 07 20:46:00-012458 util-scheduler-8620 DEBUG Canceling task: 1657 / 0x5e2b838
Jul 07 20:46:00-012684 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:46:00-012908 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:00-013151 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-013722 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-013911 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:00-014090 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:00-014318 cadet-p2p-8620 DEBUG Checking 0x4dbd080 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-014572 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:00-014840 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:46:00-015037 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:46:00-015323 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 48)
Jul 07 20:46:00-015815 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:00-016005 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:00-016199 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:46:00-016393 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 4
Jul 07 20:46:00-016575 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:00-016763 util-scheduler-8620 DEBUG Canceling task: 1612 / 0x5e31aa0
Jul 07 20:46:00-016981 util-scheduler-8620 DEBUG Adding task: 1690 / 0x5e31aa0
Jul 07 20:46:00-017260 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:00-017436 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:00-017662 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-017894 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-018078 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:00-018254 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:00-018475 cadet-p2p-8620 DEBUG Checking 0x513d4a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-018717 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-018949 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-019133 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:00-019307 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:00-019528 cadet-p2p-8620 DEBUG Checking 0x513d4a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-019709 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:00-019917 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:46:00-020132 util-scheduler-8620 DEBUG Adding task: 1691 / 0x5e2b838
Jul 07 20:46:00-020314 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:00-020493 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:46:00-020693 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:00-020871 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:00-021048 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:00-021315 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-021514 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:46:00-021695 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:46:00-021930 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-022125 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:46:00-022304 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:46:00-022538 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-022733 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:46:00-022912 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:00-023113 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:00-023320 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 48 bytes.
Jul 07 20:46:00-023505 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:46:00-023711 util-scheduler-8620 DEBUG Adding task: 1692 / 0x5e2b838
Jul 07 20:46:00-023935 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:00-024134 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:00-024338 util-scheduler-8620 DEBUG Adding task: 1693 / 0x46620a0
Jul 07 20:46:00-024542 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:46:00-024920 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:00-025122 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:00-025419 util-scheduler-8620 DEBUG Checking readiness of task: 1693 / 0x46620a0
Jul 07 20:46:00-025617 util-scheduler-8620 DEBUG Checking readiness of task: 1689 / 0x46620a0
Jul 07 20:46:00-025811 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-026004 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-026197 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-026388 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-026580 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-026771 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-026961 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-027155 util-scheduler-8620 DEBUG Running task: 1693 / 0x46620a0
Jul 07 20:46:00-027342 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:00-027523 util-8620 DEBUG process_notify is running
Jul 07 20:46:00-027697 util-8620 DEBUG client_notify is running
Jul 07 20:46:00-027879 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:00-028077 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:00-028269 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:00-028564 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:00-028775 util-scheduler-8620 DEBUG Running task: 1691 / 0x5e2b838
Jul 07 20:46:00-028972 util-scheduler-8620 DEBUG Canceling task: 1692 / 0x5e2b838
Jul 07 20:46:00-029187 util-scheduler-8620 DEBUG Adding task: 1694 / 0x5e2b838
Jul 07 20:46:00-029430 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:00-029628 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:00-029828 util-scheduler-8620 DEBUG Adding task: 1695 / 0x46620a0
Jul 07 20:46:00-030071 util-scheduler-8620 DEBUG Checking readiness of task: 1695 / 0x46620a0
Jul 07 20:46:00-030267 util-scheduler-8620 DEBUG Checking readiness of task: 1689 / 0x46620a0
Jul 07 20:46:00-030460 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-030652 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-030843 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-031036 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-031226 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-031422 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-031614 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-031805 util-scheduler-8620 DEBUG Running task: 1695 / 0x46620a0
Jul 07 20:46:00-031992 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:00-032170 util-8620 DEBUG process_notify is running
Jul 07 20:46:00-032341 util-8620 DEBUG client_notify is running
Jul 07 20:46:00-032519 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:00-032712 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:00-032902 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:00-033184 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:00-117883 util-scheduler-8620 DEBUG Checking readiness of task: 1689 / 0x46620a0
Jul 07 20:46:00-118217 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-118413 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-118606 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-118797 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-119017 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-119207 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-119397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-119592 util-scheduler-8620 DEBUG Running task: 1689 / 0x46620a0
Jul 07 20:46:00-120007 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:00-120259 util-scheduler-8620 DEBUG Adding task: 1696 / 0x4662248
Jul 07 20:46:00-120531 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-120724 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-120915 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-121106 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-121323 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-121513 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-121702 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-121891 util-scheduler-8620 DEBUG Running task: 1696 / 0x4662248
Jul 07 20:46:00-122082 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:00-122280 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:00-122509 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 20:46:00-122770 cadet-con-8620 INFO <-- {              POLL} on connection CMHCKRVP from V8XX
Jul 07 20:46:00-123023 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:00-123232 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:00-123419 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:46:00-123592 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:46:00-123823 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:00-123999 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:00-124173 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:00-124345 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:00-124564 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:00-124744 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:46:00-124925 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:46:00-125273 cadet-con-8620 INFO --> {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:00-125469 cadet-con-8620 DEBUG  ack 64
Jul 07 20:46:00-125650 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:00-125886 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:00-126093 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:00-126387 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:00-126588 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:00-126813 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:00-127118 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:00-128648 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:00-128862 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:46:00-129080 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:46:00-129325 util-scheduler-8620 DEBUG Adding task: 1697 / 0x4d6ff98
Jul 07 20:46:00-129507 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:00-129713 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:00-129891 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:00-130066 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:00-130307 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:00-130491 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:46:00-130665 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:00-130864 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:00-131067 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:00-131282 util-scheduler-8620 DEBUG Adding task: 1698 / 0x46620a0
Jul 07 20:46:00-131533 util-scheduler-8620 DEBUG Checking readiness of task: 1698 / 0x46620a0
Jul 07 20:46:00-131726 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-131917 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-132118 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-132309 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-132498 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-132687 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-132877 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-133066 util-scheduler-8620 DEBUG Running task: 1697 / 0x4d6ff98
Jul 07 20:46:00-133300 util-scheduler-8620 DEBUG Adding task: 1699 / 0x4d6ff98
Jul 07 20:46:00-133522 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:00-133724 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:00-133924 util-scheduler-8620 DEBUG Adding task: 1700 / 0x46620a0
Jul 07 20:46:00-134165 util-scheduler-8620 DEBUG Checking readiness of task: 1700 / 0x46620a0
Jul 07 20:46:00-134359 util-scheduler-8620 DEBUG Checking readiness of task: 1698 / 0x46620a0
Jul 07 20:46:00-134549 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-134739 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-134928 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-135120 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-135308 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-135496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-135684 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-135876 util-scheduler-8620 DEBUG Running task: 1700 / 0x46620a0
Jul 07 20:46:00-136060 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:00-136238 util-8620 DEBUG process_notify is running
Jul 07 20:46:00-136408 util-8620 DEBUG client_notify is running
Jul 07 20:46:00-136588 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:00-136784 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:00-137076 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:00-137344 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:00-193646 util-scheduler-8620 DEBUG Checking readiness of task: 1698 / 0x46620a0
Jul 07 20:46:00-193972 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-194168 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-194362 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-194553 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-194744 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-194934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-195123 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-195318 util-scheduler-8620 DEBUG Running task: 1698 / 0x46620a0
Jul 07 20:46:00-195735 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:00-195986 util-scheduler-8620 DEBUG Adding task: 1701 / 0x4662248
Jul 07 20:46:00-196258 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:00-196452 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:00-196669 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:00-196861 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:00-197050 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:00-197269 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:00-197460 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:00-197652 util-scheduler-8620 DEBUG Running task: 1701 / 0x4662248
Jul 07 20:46:00-197844 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:00-198044 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:00-198271 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:00-198534 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:00-198791 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:00-199000 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:00-199185 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:00-199359 cadet-con-8620 DEBUG   ACK 64 (was 0)
Jul 07 20:46:00-199534 cadet-con-8620 DEBUG   Cancel poll
Jul 07 20:46:00-199715 util-scheduler-8620 DEBUG Canceling task: 1653 / 0x5e31aa4
Jul 07 20:46:00-199959 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:00-200191 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:00-200396 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:00-200578 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:00-200752 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:00-200961 util-scheduler-8620 DEBUG Adding task: 1702 / 0x46620a0
Jul 07 20:46:01-007371 util-scheduler-8620 DEBUG Checking readiness of task: 1702 / 0x46620a0
Jul 07 20:46:01-007762 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:01-007962 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:01-008157 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:01-008352 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:01-008548 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:01-008745 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:01-008939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:01-009138 util-scheduler-8620 DEBUG Running task: 1702 / 0x46620a0
Jul 07 20:46:01-009591 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:01-009858 util-scheduler-8620 DEBUG Adding task: 1703 / 0x4662248
Jul 07 20:46:01-010142 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:01-010340 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:01-010533 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:01-010726 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:01-010917 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:01-011108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:01-011299 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:01-011490 util-scheduler-8620 DEBUG Running task: 1703 / 0x4662248
Jul 07 20:46:01-011683 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:01-011885 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:01-012118 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:01-012384 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:01-012644 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:01-012884 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:01-013072 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:01-013271 cadet-con-8620 DEBUG   ACK 64 (was 64)
Jul 07 20:46:01-013502 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:01-013734 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:01-013942 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:01-014127 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:01-014304 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:01-014516 util-scheduler-8620 DEBUG Adding task: 1704 / 0x46620a0
Jul 07 20:46:01-256977 util-scheduler-8620 DEBUG Checking readiness of task: 1704 / 0x46620a0
Jul 07 20:46:01-257367 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:01-257565 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:01-257758 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:01-257952 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:01-258143 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:01-258333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:01-258522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:01-258717 util-scheduler-8620 DEBUG Running task: 1685 / 0x4d65218
Jul 07 20:46:01-258920 cadet-chn-8620 DEBUG !!! RETRANSMIT 0
Jul 07 20:46:01-259212 cadet-chn-8620 INFO ===> {              DATA} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:01-259415 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:46:01-259617 cadet-chn-8620 DEBUG   using existing copy: 0x51720d0 {r:0x4d65218 q:(nil) t:260}
Jul 07 20:46:01-259808 cadet-chn-8620 DEBUG   new chq: 0x51d6ab0
Jul 07 20:46:01-260014 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:01-260216 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:01-260398 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:01-260581 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:01-260761 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:01-260939 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:01-261109 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:01-261350 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:01-261525 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:01-261763 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:01-261948 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:01-262669 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:01-262849 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:01-263037 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:01-266966 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:01-267868 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:01-268112 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:01-268305 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:01-271576 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:01-271823 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:01-272008 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:01-272231 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:01-272429 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:01-272716 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection CMHCKRVP (->V8XX) (172 bytes)
Jul 07 20:46:01-272920 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:01-273098 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:01-273298 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:46:01-273471 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:01-273649 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:01-273884 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:01-274094 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:01-274442 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 172)
Jul 07 20:46:01-274644 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:01-274870 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:01-275053 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:01-275228 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:01-275430 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:01-275635 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:01-275812 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:01-275988 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:01-276227 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:01-276410 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:46:01-276586 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:01-276819 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:01-277013 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:01-277211 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:01-277413 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:01-277693 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:01-277915 util-scheduler-8620 DEBUG Adding task: 1705 / 0x4d5e5d8
Jul 07 20:46:01-278195 util-scheduler-8620 DEBUG Checking readiness of task: 1705 / 0x4d5e5d8
Jul 07 20:46:01-278393 util-scheduler-8620 DEBUG Checking readiness of task: 1704 / 0x46620a0
Jul 07 20:46:01-278585 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:01-278774 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:01-278964 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:01-279153 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:01-279342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:01-279530 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:01-279719 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:01-279912 util-scheduler-8620 DEBUG Running task: 1705 / 0x4d5e5d8
Jul 07 20:46:01-280099 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:01-280279 util-8620 DEBUG process_notify is running
Jul 07 20:46:01-280451 util-8620 DEBUG client_notify is running
Jul 07 20:46:01-280679 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:46:01-281039 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:02-008382 util-scheduler-8620 DEBUG Checking readiness of task: 1704 / 0x46620a0
Jul 07 20:46:02-008771 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-008975 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-009171 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-009398 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-009593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-009786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-009980 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-010179 util-scheduler-8620 DEBUG Running task: 1704 / 0x46620a0
Jul 07 20:46:02-010606 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-010875 util-scheduler-8620 DEBUG Adding task: 1706 / 0x4662248
Jul 07 20:46:02-011169 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-011377 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-011602 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-011801 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-011995 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-012190 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-012383 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-012577 util-scheduler-8620 DEBUG Running task: 1706 / 0x4662248
Jul 07 20:46:02-012773 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:02-012980 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:02-013254 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:02-013529 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-013791 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-014006 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-014193 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:02-014371 cadet-con-8620 DEBUG   ACK 64 (was 64)
Jul 07 20:46:02-014604 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-014839 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-015050 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-015237 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:02-015418 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:02-015643 util-scheduler-8620 DEBUG Adding task: 1707 / 0x46620a0
Jul 07 20:46:02-659103 util-scheduler-8620 DEBUG Checking readiness of task: 1707 / 0x46620a0
Jul 07 20:46:02-659491 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-659688 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-659881 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-660083 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-660277 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-660466 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-660657 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-660853 util-scheduler-8620 DEBUG Running task: 1707 / 0x46620a0
Jul 07 20:46:02-661304 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-661563 util-scheduler-8620 DEBUG Adding task: 1708 / 0x4662248
Jul 07 20:46:02-661844 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-662038 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-662229 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-662424 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-663172 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-663373 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-663565 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-663758 util-scheduler-8620 DEBUG Running task: 1708 / 0x4662248
Jul 07 20:46:02-663950 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-664153 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-664389 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:02-664598 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-664807 util-scheduler-8620 DEBUG Adding task: 1709 / 0x46620a0
Jul 07 20:46:02-664996 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:02-665228 util-scheduler-8620 DEBUG Adding task: 1710 / 0x46620a0
Jul 07 20:46:02-665478 util-scheduler-8620 DEBUG Checking readiness of task: 1710 / 0x46620a0
Jul 07 20:46:02-665708 util-scheduler-8620 DEBUG Checking readiness of task: 1709 / 0x46620a0
Jul 07 20:46:02-665900 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-666091 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-666280 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-666471 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-666660 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-666850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-667038 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-667231 util-scheduler-8620 DEBUG Running task: 1709 / 0x46620a0
Jul 07 20:46:02-667415 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-667595 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-667770 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-667962 util-scheduler-8620 DEBUG Canceling task: 1699 / 0x4d6ff98
Jul 07 20:46:02-668187 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:46:02-668410 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:02-668650 cadet-p2p-8620 DEBUG Checking 0x51d4690 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-668885 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:02-669063 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:02-669279 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:02-669550 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:02-669748 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-669930 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-670119 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:02-670293 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:02-670477 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:02-670651 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-670870 cadet-p2p-8620 DEBUG Checking 0x51ea6b0 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-671104 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-671286 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:02-671461 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-671688 cadet-p2p-8620 DEBUG Checking 0x51ea6b0 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-671917 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-672099 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:02-672276 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-672442 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:02-672649 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `V8XX'
Jul 07 20:46:02-672863 util-scheduler-8620 DEBUG Adding task: 1711 / 0x4d6ff98
Jul 07 20:46:02-673042 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:02-673243 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:02-673446 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-673622 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:02-673796 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-674035 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-674230 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:02-674408 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:02-674606 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-674811 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:02-674995 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:02-675199 util-scheduler-8620 DEBUG Adding task: 1712 / 0x4d6ff98
Jul 07 20:46:02-675418 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:02-675613 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-675832 util-scheduler-8620 DEBUG Adding task: 1713 / 0x46620a0
Jul 07 20:46:02-676034 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:02-682860 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-683183 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:02-683398 util-scheduler-8620 DEBUG Running task: 1710 / 0x46620a0
Jul 07 20:46:02-683825 util-8620 DEBUG receive_ready read 33824/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-684963 util-scheduler-8620 DEBUG Adding task: 1714 / 0x4662248
Jul 07 20:46:02-685262 util-scheduler-8620 DEBUG Checking readiness of task: 1713 / 0x46620a0
Jul 07 20:46:02-685461 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-685654 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-685846 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-686038 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-686228 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-686418 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-686607 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-686800 util-scheduler-8620 DEBUG Running task: 1713 / 0x46620a0
Jul 07 20:46:02-686985 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-687164 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-687336 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-687517 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-687714 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:02-687906 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-688206 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-688415 util-scheduler-8620 DEBUG Running task: 1714 / 0x4662248
Jul 07 20:46:02-688608 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:02-689360 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:02-689591 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `V8XX'
Jul 07 20:46:02-689850 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-690094 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-690324 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-690532 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:02-690777 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-690987 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-691176 cadet-con-8620 DEBUG  PID 1 (expected 1+)
Jul 07 20:46:02-691356 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:02-691547 util-scheduler-8620 DEBUG Canceling task: 1635 / 0x4d707d0
Jul 07 20:46:02-691769 util-scheduler-8620 DEBUG Adding task: 1715 / 0x4d707d0
Jul 07 20:46:02-691992 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:02-692263 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:02-692482 util-scheduler-8620 DEBUG Adding task: 1716 / 0x4d5e5d8
Jul 07 20:46:02-692670 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:02-692840 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:02-697462 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:02-698839 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:02-699050 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:02-702418 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on V8XX
Jul 07 20:46:02-702675 cadet-chn-8620 DEBUG   channel confirm FWD V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-702939 cadet-chn-8620 DEBUG   sending channel BCK ack for channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-703195 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-703408 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:02-703688 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-703871 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-704057 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-704238 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-704416 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-704586 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-704803 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-704976 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-705312 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-705502 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-705796 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:02-705968 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-706152 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:02-709839 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:02-710530 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:02-710777 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-710966 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:02-714167 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:02-714409 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:02-714594 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:02-714816 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-715010 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:46:02-715285 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:02-715484 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:02-715661 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:02-715836 cadet-con-8620 DEBUG      ack recv 64
Jul 07 20:46:02-716009 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:02-716186 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:02-716420 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-716639 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-716952 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:02-717152 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:02-717403 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-717586 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:02-717761 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-717962 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-718167 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-718343 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:02-718517 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-718757 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-718954 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:02-719132 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:02-719365 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-719559 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-719735 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-719933 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-720165 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:02-720341 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:02-720516 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:02-720687 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:02-720925 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:02-721105 cadet-con-8620 DEBUG  ACK 65
Jul 07 20:46:02-721309 cadet-con-8620 DEBUG  last pid 1, last ack 64, qmax 11, q 0
Jul 07 20:46:02-721574 cadet-con-8620 INFO --> {               ACK} ( 65) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:02-721764 cadet-con-8620 DEBUG  ack 65
Jul 07 20:46:02-721942 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:02-722174 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-722384 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-722673 cadet-p2p-8620 INFO que {               ACK} ( 65) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:02-722871 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:02-723093 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-723276 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 2
Jul 07 20:46:02-723451 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-723651 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-723910 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-724090 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:02-724265 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-724502 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-724686 cadet-p2p-8620 DEBUG QQQ    payload , 65
Jul 07 20:46:02-724861 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:02-725094 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-725314 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:02-725493 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:02-725727 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-725922 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-726100 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-726296 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-732832 util-scheduler-8620 DEBUG Adding task: 1717 / 0x4662248
Jul 07 20:46:02-733080 util-scheduler-8620 DEBUG Running task: 1711 / 0x4d6ff98
Jul 07 20:46:02-733315 util-scheduler-8620 DEBUG Canceling task: 1712 / 0x4d6ff98
Jul 07 20:46:02-733537 util-scheduler-8620 DEBUG Adding task: 1718 / 0x4d6ff98
Jul 07 20:46:02-733764 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:02-733967 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-734173 util-scheduler-8620 DEBUG Adding task: 1719 / 0x46620a0
Jul 07 20:46:02-734440 util-scheduler-8620 DEBUG Checking readiness of task: 1719 / 0x46620a0
Jul 07 20:46:02-734638 util-scheduler-8620 DEBUG Checking readiness of task: 1716 / 0x4d5e5d8
Jul 07 20:46:02-734830 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-735021 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-735210 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-735401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-735807 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-736201 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-736399 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-736645 util-scheduler-8620 DEBUG Running task: 1716 / 0x4d5e5d8
Jul 07 20:46:02-736838 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:02-737021 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-737220 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-737470 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:02-737788 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:02-738007 util-scheduler-8620 DEBUG Running task: 1719 / 0x46620a0
Jul 07 20:46:02-738224 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-738401 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-738571 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-738750 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-738948 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:02-739137 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-739443 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-739844 util-scheduler-8620 DEBUG Running task: 1717 / 0x4662248
Jul 07 20:46:02-740038 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:02-740381 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:02-740616 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:02-740883 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-741139 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-741374 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-741558 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:02-741732 cadet-con-8620 DEBUG   ACK 65 (was 64)
Jul 07 20:46:02-741960 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-742190 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-742394 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-742576 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:02-742790 util-scheduler-8620 DEBUG Adding task: 1720 / 0x4662248
Jul 07 20:46:02-743058 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-743251 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-743440 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-743632 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-743827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-744021 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-744212 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-744405 util-scheduler-8620 DEBUG Running task: 1720 / 0x4662248
Jul 07 20:46:02-744609 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:02-744939 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:02-745165 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:02-745441 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-745691 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-745900 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-746083 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:02-746255 cadet-con-8620 DEBUG   ACK 66 (was 65)
Jul 07 20:46:02-746482 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-746713 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-746920 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-747101 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:02-747306 util-scheduler-8620 DEBUG Adding task: 1721 / 0x4662248
Jul 07 20:46:02-747554 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-747750 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-747943 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-748135 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-748326 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-748518 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-748732 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-748926 util-scheduler-8620 DEBUG Running task: 1721 / 0x4662248
Jul 07 20:46:02-749116 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:02-749469 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:02-749701 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `V8XX'
Jul 07 20:46:02-749958 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-750201 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-750429 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-750638 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:02-750882 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-751090 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-751279 cadet-con-8620 DEBUG  PID 2 (expected 2+)
Jul 07 20:46:02-751460 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:02-751656 util-scheduler-8620 DEBUG Canceling task: 1715 / 0x4d707d0
Jul 07 20:46:02-751889 util-scheduler-8620 DEBUG Adding task: 1722 / 0x4d707d0
Jul 07 20:46:02-752070 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:02-752333 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:02-752553 util-scheduler-8620 DEBUG Adding task: 1723 / 0x4d5e5d8
Jul 07 20:46:02-752739 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:02-752907 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:02-756592 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:02-757526 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:02-757736 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:02-761020 cadet-tun-8620 INFO <=== {          DATA_ACK} on V8XX
Jul 07 20:46:02-761252 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:46:02-761436 cadet-chn-8620 DEBUG   id 0
Jul 07 20:46:02-761611 cadet-chn-8620 DEBUG !!! Freeing 0
Jul 07 20:46:02-761866 cadet-chn-8620 INFO !!!  took 3505865 µs, new delay 3505865 µs
Jul 07 20:46:02-762042 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:02-762228 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:46:02-762417 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-762597 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-762785 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:46:02-762961 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:02-763130 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:02-763318 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:02-763495 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:46:02-763718 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 875 ms
Jul 07 20:46:02-763890 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:02-764093 cadet-chn-8620 DEBUG !! using delay 3502932 µs
Jul 07 20:46:02-764295 util-scheduler-8620 DEBUG Adding task: 1724 / 0x4d65218
Jul 07 20:46:02-764500 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:02-764682 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:02-764862 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 2
Jul 07 20:46:02-765034 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-765281 cadet-p2p-8620 DEBUG Checking 0x522b690 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-765477 cadet-chn-8620 DEBUG  COPYFREE 0x51720d0
Jul 07 20:46:02-765662 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:02-765835 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:46:02-766038 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-766221 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-766405 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-766589 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-766767 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-766939 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-767158 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-767360 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-767596 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-767783 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-767964 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:46:02-768195 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-768377 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:02-768567 util-scheduler-8620 DEBUG Canceling task: 1724 / 0x4d65218
Jul 07 20:46:02-768815 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:02-768992 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:02-769168 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:02-769365 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:02-769591 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:02-769774 cadet-con-8620 DEBUG  ACK 66
Jul 07 20:46:02-769968 cadet-con-8620 DEBUG  last pid 2, last ack 65, qmax 11, q 0
Jul 07 20:46:02-770150 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:02-770319 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:02-770506 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:02-770687 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-770864 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-771052 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:02-771227 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:02-771413 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:02-771592 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-771817 cadet-p2p-8620 DEBUG Checking 0x522ab60 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-772051 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-772236 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-772412 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-772678 cadet-con-8620 INFO --> {               ACK} ( 66) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:02-772871 cadet-con-8620 DEBUG  ack 66
Jul 07 20:46:02-773050 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:02-773309 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-773520 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-773822 cadet-p2p-8620 INFO que {               ACK} ( 66) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:02-774024 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:02-774249 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-774432 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-774607 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-774809 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-775014 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-775191 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:02-775368 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-775607 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-775790 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:46:02-775966 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:02-776201 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-776396 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-776574 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-776773 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-776993 util-scheduler-8620 DEBUG Adding task: 1725 / 0x4662248
Jul 07 20:46:02-777290 util-scheduler-8620 DEBUG Checking readiness of task: 1723 / 0x4d5e5d8
Jul 07 20:46:02-777494 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-777687 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-777878 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-778091 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-778282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-778474 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-778664 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-778859 util-scheduler-8620 DEBUG Running task: 1723 / 0x4d5e5d8
Jul 07 20:46:02-779046 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:02-779228 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-779402 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-779635 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:02-779885 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:02-780098 util-scheduler-8620 DEBUG Running task: 1725 / 0x4662248
Jul 07 20:46:02-780300 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:46:02-780705 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:46:02-780928 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `V8XX'
Jul 07 20:46:02-781180 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:02-781444 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-781673 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-781885 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:02-782131 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-782350 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-782543 cadet-con-8620 DEBUG  PID 3 (expected 3+)
Jul 07 20:46:02-782728 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:02-782933 util-scheduler-8620 DEBUG Canceling task: 1722 / 0x4d707d0
Jul 07 20:46:02-783166 util-scheduler-8620 DEBUG Adding task: 1726 / 0x4d707d0
Jul 07 20:46:02-783349 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:02-783622 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:02-783848 util-scheduler-8620 DEBUG Adding task: 1727 / 0x4d5e5d8
Jul 07 20:46:02-784044 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:02-784213 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:02-787684 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:02-806132 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:02-806399 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:02-855014 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:02-855330 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:46:02-855633 cadet-chn-8620 INFO <=== DATA 0 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-855826 cadet-chn-8620 DEBUG RECV 0 (33296)
Jul 07 20:46:02-856002 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:46:02-856493 util-server-nc-8620 DEBUG Adding message of type 285 and size 33292 to pending queue (which has 1 entries)
Jul 07 20:46:02-856824 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:02-857039 util-scheduler-8620 DEBUG Adding task: 1728 / 0x4d5c418
Jul 07 20:46:02-857259 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:46:02-857441 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:46:02-857687 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-857905 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:02-858105 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-858286 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-858468 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-858648 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-858825 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-858993 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-859209 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-859411 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-859791 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-859981 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-860282 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:02-860453 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-860638 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:02-863893 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:02-864658 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:02-864896 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-865083 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:02-868457 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:02-868762 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:02-868951 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:02-869179 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-869403 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:02-869688 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:02-869889 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:02-870067 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:02-870239 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:46:02-870411 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:02-870588 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:02-870821 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-871030 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-871345 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:02-871546 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:02-871907 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-872092 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-872267 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-872469 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-872670 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-872846 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:02-873019 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-873279 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-873463 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:46:02-873638 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:02-873870 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-874063 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-874240 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-874471 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-874665 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:02-874840 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:02-875037 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-875214 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:02-875446 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:02-875622 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:02-875796 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:02-875967 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:02-876185 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:02-876363 cadet-con-8620 DEBUG  ACK 67
Jul 07 20:46:02-876542 cadet-con-8620 DEBUG  last pid 3, last ack 66, qmax 11, q 0
Jul 07 20:46:02-876722 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:02-876888 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:02-877072 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:02-877275 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-877483 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-877670 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:02-877844 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:02-878026 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:02-878200 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-878423 cadet-p2p-8620 DEBUG Checking 0x522ab60 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-878655 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-878838 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-879010 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-879271 cadet-con-8620 INFO --> {               ACK} ( 67) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:02-879462 cadet-con-8620 DEBUG  ack 67
Jul 07 20:46:02-879641 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:02-879877 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-880088 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-880389 cadet-p2p-8620 INFO que {               ACK} ( 67) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:02-880595 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:02-880823 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-881014 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-881216 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-881423 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-881635 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-881815 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:02-881993 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-882239 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-882425 cadet-p2p-8620 DEBUG QQQ    payload , 67
Jul 07 20:46:02-882602 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:02-882837 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-883029 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-883206 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-883437 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-883629 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:02-883805 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:02-884002 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-884188 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:02-884409 util-scheduler-8620 DEBUG Adding task: 1729 / 0x46620a0
Jul 07 20:46:02-884698 util-scheduler-8620 DEBUG Checking readiness of task: 1729 / 0x46620a0
Jul 07 20:46:02-884898 util-scheduler-8620 DEBUG Checking readiness of task: 1728 / 0x4d5c418
Jul 07 20:46:02-885088 util-scheduler-8620 DEBUG Checking readiness of task: 1727 / 0x4d5e5d8
Jul 07 20:46:02-885304 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-885494 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-885685 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-885873 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-886062 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-886250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-886439 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-886632 util-scheduler-8620 DEBUG Running task: 1727 / 0x4d5e5d8
Jul 07 20:46:02-886818 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:02-886997 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-887168 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-887422 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:02-887630 util-scheduler-8620 DEBUG Adding task: 1730 / 0x4d5e5d8
Jul 07 20:46:02-887857 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:02-888167 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:02-888367 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:02-888566 util-scheduler-8620 DEBUG Running task: 1728 / 0x4d5c418
Jul 07 20:46:02-888750 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:02-888925 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-889116 util-server-nc-8620 DEBUG Copying message of type 285 and size 33292 from pending queue to transmission buffer
Jul 07 20:46:02-890028 util-8620 DEBUG Connection transmitted 33292/33292 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:02-890484 util-scheduler-8620 DEBUG Running task: 1729 / 0x46620a0
Jul 07 20:46:02-890897 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-891140 util-scheduler-8620 DEBUG Adding task: 1731 / 0x4662248
Jul 07 20:46:02-891401 util-scheduler-8620 DEBUG Checking readiness of task: 1730 / 0x4d5e5d8
Jul 07 20:46:02-891596 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-891787 util-scheduler-8620 DEBUG Checking readiness of task: 1645 / 0x4d5c418
Jul 07 20:46:02-891977 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-892167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-892357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-892545 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-892735 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-892925 util-scheduler-8620 DEBUG Running task: 1645 / 0x4d5c418
Jul 07 20:46:02-893332 util-8620 DEBUG receive_ready read 80/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:46:02-893561 util-8620 DEBUG Server receives 80 bytes from `<unbound UNIX client>'.
Jul 07 20:46:02-893758 util-8620 DEBUG Server-mst receives 80 bytes with 0 bytes already in private buffer
Jul 07 20:46:02-893946 util-8620 DEBUG Server-mst has 80 bytes left in inbound buffer
Jul 07 20:46:02-894130 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:46:02-894321 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:46:02-894544 util-scheduler-8620 DEBUG Adding task: 1732 / 0x4d5c578
Jul 07 20:46:02-894731 cadet-loc-8620 DEBUG 
Jul 07 20:46:02-894901 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:46:02-895076 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:02-895255 cadet-loc-8620 DEBUG   on channel 80000002
Jul 07 20:46:02-895438 cadet-loc-8620 DEBUG    -- ch 0x4d650a8
Jul 07 20:46:02-895617 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:46:02-895792 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:46:02-896013 cadet-tun-8620 DEBUG Tunnel send connection ACKs on V8XX
Jul 07 20:46:02-896198 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:46:02-896376 cadet-tun-8620 DEBUG   allowed 64
Jul 07 20:46:02-896573 util-scheduler-8620 DEBUG Canceling task: 1732 / 0x4d5c578
Jul 07 20:46:02-896767 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:02-896948 util-8620 DEBUG Server-mst has 72 bytes left in inbound buffer
Jul 07 20:46:02-897134 util-8620 DEBUG Server-mst leaves 72 bytes in private buffer
Jul 07 20:46:02-897337 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:46:02-897516 util-8620 DEBUG Server-mst receives 0 bytes with 72 bytes already in private buffer
Jul 07 20:46:02-897702 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:46:02-897889 util-8620 DEBUG Server schedules transmission of 72-byte message of type 285 to client.
Jul 07 20:46:02-898101 util-scheduler-8620 DEBUG Adding task: 1733 / 0x4d5c578
Jul 07 20:46:02-898307 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:46:02-898481 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:02-898656 cadet-loc-8620 DEBUG   on channel 80000002
Jul 07 20:46:02-898838 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:46:02-899087 cadet-chn-8620 INFO ===> {              DATA} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-899284 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:46:02-899488 cadet-chn-8620 DEBUG !!! SAVE 1 {              DATA}
Jul 07 20:46:02-899673 cadet-chn-8620 DEBUG   at 0x5266ee0
Jul 07 20:46:02-899851 cadet-chn-8620 DEBUG   new chq: 0x52824e8
Jul 07 20:46:02-900051 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:02-900251 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-900432 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-900614 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-900794 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-900970 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-901138 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-901376 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-901553 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-901793 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-901978 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-902275 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:02-902445 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-902628 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:02-906115 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:02-906935 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:02-907178 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:02-907367 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:02-910667 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:02-910959 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:02-911154 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:02-911382 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:02-911582 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:02-911875 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (156 bytes)
Jul 07 20:46:02-912081 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:02-912264 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:02-912439 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:46:02-912619 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 3
Jul 07 20:46:02-912857 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:02-913067 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:02-913410 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 156)
Jul 07 20:46:02-913612 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:02-913837 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-914019 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-914194 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-914395 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:02-914597 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-914772 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:02-914947 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-915186 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-915368 cadet-p2p-8620 DEBUG QQQ    payload , 67
Jul 07 20:46:02-915544 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:02-915776 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-915970 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-916146 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-916378 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-916602 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:02-916779 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:02-917011 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-917224 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:02-917402 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:02-917600 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-917808 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-917987 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-918168 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-918349 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-918524 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-918692 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-918908 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-919080 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-919324 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:02-919510 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-919681 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:02-919855 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:46:02-920057 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:02-920232 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-920413 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:02-920590 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-920766 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-920934 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-921146 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-921340 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-921568 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:02-921752 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-921925 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:46:02-922150 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:02-922338 cadet-loc-8620 DEBUG send local FWD ack on 80000002 towards 0x4d5c6d8
Jul 07 20:46:02-922546 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:02-922749 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:02-922963 util-scheduler-8620 DEBUG Adding task: 1734 / 0x4d5c418
Jul 07 20:46:02-923147 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:46:02-923337 util-scheduler-8620 DEBUG Canceling task: 1733 / 0x4d5c578
Jul 07 20:46:02-923538 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:02-923721 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:46:02-923928 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:46:02-924138 util-scheduler-8620 DEBUG Adding task: 1735 / 0x4d5c418
Jul 07 20:46:02-924341 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:46:02-924578 util-scheduler-8620 DEBUG Running task: 1730 / 0x4d5e5d8
Jul 07 20:46:02-924774 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:02-924958 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-925135 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-925398 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:02-925764 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:02-926040 util-scheduler-8620 DEBUG Running task: 1731 / 0x4662248
Jul 07 20:46:02-926238 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-926441 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-926685 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:02-926906 util-scheduler-8620 DEBUG Adding task: 1736 / 0x4662248
Jul 07 20:46:02-927172 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-927367 util-scheduler-8620 DEBUG Checking readiness of task: 1734 / 0x4d5c418
Jul 07 20:46:02-927558 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-927747 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-927935 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-928124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-928312 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-928500 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-928690 util-scheduler-8620 DEBUG Running task: 1734 / 0x4d5c418
Jul 07 20:46:02-928873 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:02-929048 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-929265 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:02-929554 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:02-929759 util-scheduler-8620 DEBUG Running task: 1736 / 0x4662248
Jul 07 20:46:02-929948 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-930139 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-930348 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:02-930551 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-930753 util-scheduler-8620 DEBUG Adding task: 1737 / 0x46620a0
Jul 07 20:46:02-930962 util-scheduler-8620 DEBUG Adding task: 1738 / 0x4662248
Jul 07 20:46:02-931198 util-scheduler-8620 DEBUG Checking readiness of task: 1737 / 0x46620a0
Jul 07 20:46:02-931392 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-931582 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-931774 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-931963 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-932151 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-932341 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-932530 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-932719 util-scheduler-8620 DEBUG Running task: 1737 / 0x46620a0
Jul 07 20:46:02-932903 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-933077 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-933268 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-933455 util-scheduler-8620 DEBUG Canceling task: 1694 / 0x5e2b838
Jul 07 20:46:02-933677 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:46:02-933895 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:02-934128 cadet-p2p-8620 DEBUG Checking 0x497c568 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-934361 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-934542 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:46:02-934716 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-934936 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:02-935113 cadet-p2p-8620 DEBUG   size 84 ok
Jul 07 20:46:02-935289 cadet-p2p-8620 DEBUG   payload ID 1
Jul 07 20:46:02-935575 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({         KEEPALIVE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 84)
Jul 07 20:46:02-935771 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-935966 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-936155 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:02-936342 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:02-936572 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-936746 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:02-936918 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:02-937089 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:02-937310 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:02-937488 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:02-937663 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:02-937871 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:02-938051 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:02-938238 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:02-938425 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:02-938605 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:02-938775 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:02-939001 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:02-939175 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:02-939414 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-939670 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:02-939855 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:02-940044 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:02-940211 cadet-chn-8620 DEBUG  channel not ready yet!
Jul 07 20:46:02-940384 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:02-940585 util-scheduler-8620 DEBUG Canceling task: 1690 / 0x5e31aa0
Jul 07 20:46:02-940802 util-scheduler-8620 DEBUG Adding task: 1739 / 0x5e31aa0
Jul 07 20:46:02-941052 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:02-941257 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:46:02-941436 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 1
Jul 07 20:46:02-941609 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-941831 cadet-p2p-8620 DEBUG Checking 0x513d4a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-942075 cadet-p2p-8620 DEBUG Checking 0x513d4a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-942253 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:02-942459 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `D3TJ'
Jul 07 20:46:02-942675 util-scheduler-8620 DEBUG Adding task: 1740 / 0x5e2b838
Jul 07 20:46:02-942852 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:02-943028 cadet-p2p-8620 DEBUG   return 84
Jul 07 20:46:02-943226 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:02-943402 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:02-943575 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:02-943814 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-944008 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:46:02-944184 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:46:02-944417 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-944610 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:46:02-944785 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:02-944981 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:02-945185 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 84 bytes.
Jul 07 20:46:02-945390 core-api-8620 DEBUG Produced SEND message to core with 84 bytes payload
Jul 07 20:46:02-945593 util-scheduler-8620 DEBUG Adding task: 1741 / 0x5e2b838
Jul 07 20:46:02-945815 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:02-946012 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-946215 util-scheduler-8620 DEBUG Adding task: 1742 / 0x46620a0
Jul 07 20:46:02-946416 util-8620 DEBUG Transmitting message of type 76 and size 140 to core service.
Jul 07 20:46:02-950184 util-8620 DEBUG Connection transmitted 140/140 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-950402 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:02-950607 util-scheduler-8620 DEBUG Running task: 1738 / 0x4662248
Jul 07 20:46:02-952117 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-952324 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-952554 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:02-952740 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:02-952923 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:02-953137 util-scheduler-8620 DEBUG Adding task: 1743 / 0x46620a0
Jul 07 20:46:02-953433 util-scheduler-8620 DEBUG Checking readiness of task: 1743 / 0x46620a0
Jul 07 20:46:02-953632 util-scheduler-8620 DEBUG Checking readiness of task: 1742 / 0x46620a0
Jul 07 20:46:02-953826 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-954017 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-954216 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-954408 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-954602 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-954794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-954986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-955182 util-scheduler-8620 DEBUG Running task: 1742 / 0x46620a0
Jul 07 20:46:02-955370 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-955554 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-955730 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-955908 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-956131 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-956331 util-scheduler-8620 DEBUG Adding task: 1744 / 0x46620a0
Jul 07 20:46:02-956531 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-956837 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-957033 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:02-957252 util-scheduler-8620 DEBUG Running task: 1740 / 0x5e2b838
Jul 07 20:46:02-957449 util-scheduler-8620 DEBUG Canceling task: 1741 / 0x5e2b838
Jul 07 20:46:02-957668 util-scheduler-8620 DEBUG Adding task: 1745 / 0x5e2b838
Jul 07 20:46:02-957891 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:02-958070 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:02-958306 util-scheduler-8620 DEBUG Checking readiness of task: 1744 / 0x46620a0
Jul 07 20:46:02-958499 util-scheduler-8620 DEBUG Checking readiness of task: 1743 / 0x46620a0
Jul 07 20:46:02-958688 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-958877 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-959066 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-959255 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-959443 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-959634 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-959821 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-960011 util-scheduler-8620 DEBUG Running task: 1743 / 0x46620a0
Jul 07 20:46:02-960418 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-960671 util-scheduler-8620 DEBUG Adding task: 1746 / 0x4662248
Jul 07 20:46:02-960882 util-scheduler-8620 DEBUG Running task: 1744 / 0x46620a0
Jul 07 20:46:02-961066 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-961262 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-961432 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-961607 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-961815 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-962010 util-scheduler-8620 DEBUG Adding task: 1747 / 0x46620a0
Jul 07 20:46:02-962206 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-962503 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-962698 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:02-962931 util-scheduler-8620 DEBUG Checking readiness of task: 1747 / 0x46620a0
Jul 07 20:46:02-963124 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-963313 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-963503 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-963692 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-963881 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-964069 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-964257 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-964447 util-scheduler-8620 DEBUG Running task: 1747 / 0x46620a0
Jul 07 20:46:02-964630 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-964804 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-964972 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-965152 util-scheduler-8620 DEBUG Canceling task: 1718 / 0x4d6ff98
Jul 07 20:46:02-965396 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 172 bytes.
Jul 07 20:46:02-965612 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:02-965849 cadet-p2p-8620 DEBUG Checking 0x526b930 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-966096 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:02-966278 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:02-966465 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:02-966745 cadet-p2p-8620 INFO snd {               ACK} ( 67) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:02-966940 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-967119 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-967305 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:02-967479 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:02-967662 cadet-con-8620 DEBUG  C_P- 0x4d707d0 4
Jul 07 20:46:02-967834 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-968054 cadet-p2p-8620 DEBUG Checking 0x522ab60 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-968286 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-968466 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-968642 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-968872 cadet-p2p-8620 DEBUG Checking 0x522ab60 towards CMHCKRVP (->V8XX)
Jul 07 20:46:02-969106 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:02-969318 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:02-969500 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-969671 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:02-969887 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:02-970116 util-scheduler-8620 DEBUG Adding task: 1748 / 0x4d6ff98
Jul 07 20:46:02-970298 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:02-970485 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:02-970689 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:02-970903 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:02-971084 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:02-971333 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-971531 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:02-971710 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:02-971943 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-972138 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:02-972314 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:02-972546 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:02-972738 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:02-972914 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:02-973111 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:02-973341 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:02-973525 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:02-973737 util-scheduler-8620 DEBUG Adding task: 1749 / 0x4d6ff98
Jul 07 20:46:02-973954 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:02-974151 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-974355 util-scheduler-8620 DEBUG Adding task: 1750 / 0x46620a0
Jul 07 20:46:02-974554 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:02-979835 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-980062 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:02-980271 util-scheduler-8620 DEBUG Running task: 1746 / 0x4662248
Jul 07 20:46:02-980464 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-980734 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-980958 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:02-981143 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:02-981370 util-scheduler-8620 DEBUG Adding task: 1751 / 0x46620a0
Jul 07 20:46:02-981630 util-scheduler-8620 DEBUG Checking readiness of task: 1751 / 0x46620a0
Jul 07 20:46:02-981826 util-scheduler-8620 DEBUG Checking readiness of task: 1750 / 0x46620a0
Jul 07 20:46:02-982017 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-982208 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-982397 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-982587 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-982775 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-982963 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-983150 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-983342 util-scheduler-8620 DEBUG Running task: 1750 / 0x46620a0
Jul 07 20:46:02-983526 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-983704 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-983877 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-984058 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-984259 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:02-984451 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-984757 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-984976 util-scheduler-8620 DEBUG Running task: 1751 / 0x46620a0
Jul 07 20:46:02-985407 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:02-985667 util-scheduler-8620 DEBUG Adding task: 1752 / 0x4662248
Jul 07 20:46:02-985880 util-scheduler-8620 DEBUG Running task: 1748 / 0x4d6ff98
Jul 07 20:46:02-986084 util-scheduler-8620 DEBUG Canceling task: 1749 / 0x4d6ff98
Jul 07 20:46:02-986304 util-scheduler-8620 DEBUG Adding task: 1753 / 0x4d6ff98
Jul 07 20:46:02-986533 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:02-987304 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-987533 util-scheduler-8620 DEBUG Adding task: 1754 / 0x46620a0
Jul 07 20:46:02-987789 util-scheduler-8620 DEBUG Checking readiness of task: 1754 / 0x46620a0
Jul 07 20:46:02-987983 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-988174 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-988364 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-988554 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-988743 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-988931 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-989120 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-989334 util-scheduler-8620 DEBUG Running task: 1754 / 0x46620a0
Jul 07 20:46:02-989523 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-989700 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-989871 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-990047 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:02-990241 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:02-990430 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:02-990736 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:02-990945 util-scheduler-8620 DEBUG Running task: 1752 / 0x4662248
Jul 07 20:46:02-991134 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:02-991329 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:02-991545 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:02-991741 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:02-991936 util-scheduler-8620 DEBUG Adding task: 1755 / 0x46620a0
Jul 07 20:46:02-992146 util-scheduler-8620 DEBUG Adding task: 1756 / 0x4662248
Jul 07 20:46:02-992383 util-scheduler-8620 DEBUG Checking readiness of task: 1755 / 0x46620a0
Jul 07 20:46:02-992575 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:02-992765 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:02-992954 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:02-993144 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:02-993353 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:02-993543 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:02-993733 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:02-993935 util-scheduler-8620 DEBUG Running task: 1755 / 0x46620a0
Jul 07 20:46:02-994119 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:02-994292 util-8620 DEBUG process_notify is running
Jul 07 20:46:02-994462 util-8620 DEBUG client_notify is running
Jul 07 20:46:02-994644 util-scheduler-8620 DEBUG Canceling task: 1745 / 0x5e2b838
Jul 07 20:46:02-994867 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 48 bytes.
Jul 07 20:46:02-995083 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:02-995318 cadet-p2p-8620 DEBUG Checking 0x513d4a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-995569 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:02-995747 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:46:02-995935 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:46:02-996215 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 48)
Jul 07 20:46:02-996409 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:02-996589 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:02-996775 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:46:02-996963 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:02-997141 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:02-997346 util-scheduler-8620 DEBUG Canceling task: 1739 / 0x5e31aa0
Jul 07 20:46:02-997556 util-scheduler-8620 DEBUG Adding task: 1757 / 0x5e31aa0
Jul 07 20:46:02-997805 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:02-997977 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:02-998202 cadet-p2p-8620 DEBUG Checking 0x51622c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-998435 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-998620 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:46:02-998798 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-999042 cadet-p2p-8620 DEBUG Checking 0x51622c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-999281 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:02-999464 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 1
Jul 07 20:46:02-999641 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:02-999807 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:03-000013 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `D3TJ'
Jul 07 20:46:03-000232 util-scheduler-8620 DEBUG Adding task: 1758 / 0x5e2b838
Jul 07 20:46:03-000416 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:03-000596 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:46:03-000800 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:03-000979 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:03-001158 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:03-001428 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:03-001629 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:46:03-001815 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:03-002022 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:03-002236 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 48 bytes.
Jul 07 20:46:03-002432 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:46:03-002649 util-scheduler-8620 DEBUG Adding task: 1759 / 0x5e2b838
Jul 07 20:46:03-002874 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:03-003083 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:03-003295 util-scheduler-8620 DEBUG Adding task: 1760 / 0x46620a0
Jul 07 20:46:03-003503 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:46:03-003852 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-004055 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:03-004259 util-scheduler-8620 DEBUG Running task: 1756 / 0x4662248
Jul 07 20:46:03-004451 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:03-004648 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:03-004865 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:03-005051 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:03-005280 util-scheduler-8620 DEBUG Adding task: 1761 / 0x46620a0
Jul 07 20:46:03-005546 util-scheduler-8620 DEBUG Checking readiness of task: 1761 / 0x46620a0
Jul 07 20:46:03-005944 util-scheduler-8620 DEBUG Checking readiness of task: 1760 / 0x46620a0
Jul 07 20:46:03-006255 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-006509 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-006705 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-006898 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-007090 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-007379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-007572 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-007770 util-scheduler-8620 DEBUG Running task: 1760 / 0x46620a0
Jul 07 20:46:03-007991 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:03-008176 util-8620 DEBUG process_notify is running
Jul 07 20:46:03-008352 util-8620 DEBUG client_notify is running
Jul 07 20:46:03-008536 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:03-008739 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:03-008935 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:03-009273 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-009489 util-scheduler-8620 DEBUG Running task: 1761 / 0x46620a0
Jul 07 20:46:03-009904 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:03-010143 util-scheduler-8620 DEBUG Adding task: 1762 / 0x4662248
Jul 07 20:46:03-010353 util-scheduler-8620 DEBUG Running task: 1758 / 0x5e2b838
Jul 07 20:46:03-010551 util-scheduler-8620 DEBUG Canceling task: 1759 / 0x5e2b838
Jul 07 20:46:03-010767 util-scheduler-8620 DEBUG Adding task: 1763 / 0x5e2b838
Jul 07 20:46:03-010992 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:03-011191 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:03-011395 util-scheduler-8620 DEBUG Adding task: 1764 / 0x46620a0
Jul 07 20:46:03-011644 util-scheduler-8620 DEBUG Checking readiness of task: 1764 / 0x46620a0
Jul 07 20:46:03-011841 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-012041 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-012233 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-012426 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-012618 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-012809 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-013000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-013215 util-scheduler-8620 DEBUG Running task: 1764 / 0x46620a0
Jul 07 20:46:03-013404 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:03-013582 util-8620 DEBUG process_notify is running
Jul 07 20:46:03-013754 util-8620 DEBUG client_notify is running
Jul 07 20:46:03-013932 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:03-014124 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:03-014315 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:03-014599 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-014808 util-scheduler-8620 DEBUG Running task: 1762 / 0x4662248
Jul 07 20:46:03-015003 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:03-015202 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:03-015422 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:03-015622 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:03-015852 util-scheduler-8620 DEBUG Adding task: 1765 / 0x46620a0
Jul 07 20:46:03-016040 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:03-016249 util-scheduler-8620 DEBUG Adding task: 1766 / 0x46620a0
Jul 07 20:46:03-016496 util-scheduler-8620 DEBUG Checking readiness of task: 1766 / 0x46620a0
Jul 07 20:46:03-016693 util-scheduler-8620 DEBUG Checking readiness of task: 1765 / 0x46620a0
Jul 07 20:46:03-016888 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-017082 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-017298 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-017493 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-017684 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-017876 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-018067 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-018261 util-scheduler-8620 DEBUG Running task: 1765 / 0x46620a0
Jul 07 20:46:03-018447 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:03-018625 util-8620 DEBUG process_notify is running
Jul 07 20:46:03-018795 util-8620 DEBUG client_notify is running
Jul 07 20:46:03-018980 util-scheduler-8620 DEBUG Canceling task: 1753 / 0x4d6ff98
Jul 07 20:46:03-019202 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:03-019421 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:03-019659 cadet-p2p-8620 DEBUG Checking 0x522ab60 towards CMHCKRVP (->V8XX)
Jul 07 20:46:03-019892 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:03-020077 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:03-020253 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:03-020477 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:03-020658 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:03-020836 cadet-p2p-8620 DEBUG   payload ID 3
Jul 07 20:46:03-021122 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:03-021345 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:03-021529 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:03-021720 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:03-021910 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:03-022144 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:03-022321 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:03-022496 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:03-022669 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:03-022868 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:03-023046 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:03-023222 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:03-023424 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:03-023604 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:03-023789 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:03-023971 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:03-024149 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:03-024321 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:03-024539 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:03-024714 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:03-024948 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:03-025134 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:03-025344 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:03-025534 util-scheduler-8620 DEBUG Canceling task: 1686 / 0x4d707d0
Jul 07 20:46:03-025749 util-scheduler-8620 DEBUG Adding task: 1767 / 0x4d707d0
Jul 07 20:46:03-026002 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:03-026198 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:46:03-026380 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 3
Jul 07 20:46:03-026555 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:03-026781 cadet-p2p-8620 DEBUG Checking 0x526a870 towards CMHCKRVP (->V8XX)
Jul 07 20:46:03-027013 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:03-027196 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 3
Jul 07 20:46:03-027372 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:03-027600 cadet-p2p-8620 DEBUG Checking 0x526a870 towards CMHCKRVP (->V8XX)
Jul 07 20:46:03-027832 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:03-028015 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 3
Jul 07 20:46:03-028191 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:03-028359 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:03-028566 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:03-028781 util-scheduler-8620 DEBUG Adding task: 1768 / 0x4d6ff98
Jul 07 20:46:03-028962 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:03-029140 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:03-029364 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:03-029543 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:03-029720 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:03-029958 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:03-030156 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:03-030335 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:03-030570 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:03-030766 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:03-030944 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:03-031143 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:03-031350 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:03-031536 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:03-031738 util-scheduler-8620 DEBUG Adding task: 1769 / 0x4d6ff98
Jul 07 20:46:03-031960 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:03-032158 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:03-032362 util-scheduler-8620 DEBUG Adding task: 1770 / 0x46620a0
Jul 07 20:46:03-032563 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:03-033913 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-034126 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:03-034385 util-scheduler-8620 DEBUG Checking readiness of task: 1770 / 0x46620a0
Jul 07 20:46:03-034584 util-scheduler-8620 DEBUG Checking readiness of task: 1766 / 0x46620a0
Jul 07 20:46:03-034860 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-035057 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-035252 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-035446 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-035639 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-035830 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-036023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-036219 util-scheduler-8620 DEBUG Running task: 1770 / 0x46620a0
Jul 07 20:46:03-036407 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:03-036585 util-8620 DEBUG process_notify is running
Jul 07 20:46:03-036759 util-8620 DEBUG client_notify is running
Jul 07 20:46:03-036939 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:03-037152 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:03-037369 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:03-037604 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-037813 util-scheduler-8620 DEBUG Running task: 1768 / 0x4d6ff98
Jul 07 20:46:03-038009 util-scheduler-8620 DEBUG Canceling task: 1769 / 0x4d6ff98
Jul 07 20:46:03-038239 util-scheduler-8620 DEBUG Adding task: 1771 / 0x4d6ff98
Jul 07 20:46:03-038459 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:03-038657 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:03-038857 util-scheduler-8620 DEBUG Adding task: 1772 / 0x46620a0
Jul 07 20:46:03-039099 util-scheduler-8620 DEBUG Checking readiness of task: 1772 / 0x46620a0
Jul 07 20:46:03-039295 util-scheduler-8620 DEBUG Checking readiness of task: 1766 / 0x46620a0
Jul 07 20:46:03-039489 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-039680 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-039873 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-040064 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-040255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-040448 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-040637 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-040830 util-scheduler-8620 DEBUG Running task: 1766 / 0x46620a0
Jul 07 20:46:03-041259 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:03-041492 util-scheduler-8620 DEBUG Adding task: 1773 / 0x4662248
Jul 07 20:46:03-041704 util-scheduler-8620 DEBUG Running task: 1772 / 0x46620a0
Jul 07 20:46:03-041892 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:03-042075 util-8620 DEBUG process_notify is running
Jul 07 20:46:03-042248 util-8620 DEBUG client_notify is running
Jul 07 20:46:03-042428 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:03-042620 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:03-042811 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:03-043112 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:03-043363 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-043558 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-043750 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-043943 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-044135 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-044326 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-044517 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-044707 util-scheduler-8620 DEBUG Running task: 1773 / 0x4662248
Jul 07 20:46:03-044898 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:03-045093 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:03-045334 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:03-045518 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:03-045721 util-scheduler-8620 DEBUG Adding task: 1774 / 0x46620a0
Jul 07 20:46:03-218198 util-scheduler-8620 DEBUG Checking readiness of task: 1774 / 0x46620a0
Jul 07 20:46:03-218572 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-218802 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-218998 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-219190 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-219385 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-219576 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-219768 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-219964 util-scheduler-8620 DEBUG Running task: 1774 / 0x46620a0
Jul 07 20:46:03-220387 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:03-220641 util-scheduler-8620 DEBUG Adding task: 1775 / 0x4662248
Jul 07 20:46:03-220922 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:03-221116 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:03-221338 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:03-221531 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:03-221722 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:03-221912 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:03-222104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:03-222296 util-scheduler-8620 DEBUG Running task: 1775 / 0x4662248
Jul 07 20:46:03-222486 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:03-222687 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:03-222915 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:03-223181 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:03-223437 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:03-223646 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:03-223832 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:03-224006 cadet-con-8620 DEBUG   ACK 65 (was 64)
Jul 07 20:46:03-224235 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:03-224466 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:03-224673 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:03-224856 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:03-225034 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:03-225268 util-scheduler-8620 DEBUG Adding task: 1776 / 0x46620a0
Jul 07 20:46:05-594266 util-scheduler-8620 DEBUG Checking readiness of task: 1776 / 0x46620a0
Jul 07 20:46:05-594652 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:05-594850 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:05-595044 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:05-595236 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:05-595427 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:05-595616 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:05-595808 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:05-596003 util-scheduler-8620 DEBUG Running task: 1776 / 0x46620a0
Jul 07 20:46:05-596426 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:05-596682 util-scheduler-8620 DEBUG Adding task: 1777 / 0x4662248
Jul 07 20:46:05-596963 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:05-597157 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:05-597381 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:05-597573 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:05-597794 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:05-597984 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:05-598175 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:05-598364 util-scheduler-8620 DEBUG Running task: 1777 / 0x4662248
Jul 07 20:46:05-598556 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:05-598755 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:05-598989 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:05-599198 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:05-599406 util-scheduler-8620 DEBUG Adding task: 1778 / 0x46620a0
Jul 07 20:46:05-599614 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:05-599822 util-scheduler-8620 DEBUG Adding task: 1779 / 0x46620a0
Jul 07 20:46:05-600070 util-scheduler-8620 DEBUG Checking readiness of task: 1779 / 0x46620a0
Jul 07 20:46:05-600266 util-scheduler-8620 DEBUG Checking readiness of task: 1778 / 0x46620a0
Jul 07 20:46:05-600458 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:05-600649 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:05-600839 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:05-601029 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:05-601244 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:05-601449 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:05-601640 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:05-601832 util-scheduler-8620 DEBUG Running task: 1778 / 0x46620a0
Jul 07 20:46:05-602017 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:05-602196 util-8620 DEBUG process_notify is running
Jul 07 20:46:05-602371 util-8620 DEBUG client_notify is running
Jul 07 20:46:05-602561 util-scheduler-8620 DEBUG Canceling task: 1763 / 0x5e2b838
Jul 07 20:46:05-602787 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 96 bytes.
Jul 07 20:46:05-603009 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:05-603249 cadet-p2p-8620 DEBUG Checking 0x51622c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:05-603483 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:05-603666 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 1
Jul 07 20:46:05-603845 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:05-604067 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:05-604245 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:46:05-604419 cadet-p2p-8620 DEBUG   payload ID 2
Jul 07 20:46:05-604706 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 96)
Jul 07 20:46:05-604901 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:05-605081 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:05-605295 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:05-605471 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:05-605640 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:05-605828 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:46:05-606016 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:46:05-606238 cadet-chn-8620 DEBUG !!! STD BACKOFF 500 ms
Jul 07 20:46:05-606451 util-scheduler-8620 DEBUG Adding task: 1780 / 0x5e33a48
Jul 07 20:46:05-606654 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:05-606884 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:05-607062 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:05-607235 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:05-607407 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:05-607604 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:05-607798 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:05-607974 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:05-608175 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:05-608354 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:05-608537 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:05-608717 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:05-608893 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:05-609062 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:05-609306 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:05-609477 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:05-609710 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:05-609955 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:05-610140 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:05-610332 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:05-610499 cadet-chn-8620 DEBUG  channel not ready yet!
Jul 07 20:46:05-610673 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:05-610859 util-scheduler-8620 DEBUG Canceling task: 1757 / 0x5e31aa0
Jul 07 20:46:05-611073 util-scheduler-8620 DEBUG Adding task: 1781 / 0x5e31aa0
Jul 07 20:46:05-611320 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:05-611499 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:46:05-611679 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 2
Jul 07 20:46:05-611852 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:05-612033 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:46:05-612233 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:05-612412 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:05-612587 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:05-612786 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:05-612991 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 96 bytes.
Jul 07 20:46:05-613176 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:46:05-613385 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:05-613577 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:46:05-613835 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:06-236536 util-scheduler-8620 DEBUG Checking readiness of task: 1779 / 0x46620a0
Jul 07 20:46:06-236944 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:06-237157 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:06-237378 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:06-237571 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:06-237763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:06-237955 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:06-238145 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:06-238342 util-scheduler-8620 DEBUG Running task: 1779 / 0x46620a0
Jul 07 20:46:06-238771 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:06-239031 util-scheduler-8620 DEBUG Adding task: 1782 / 0x4662248
Jul 07 20:46:06-239312 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:06-239507 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:06-239700 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:06-239891 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:06-240082 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:06-240273 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:06-240496 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:06-240688 util-scheduler-8620 DEBUG Running task: 1782 / 0x4662248
Jul 07 20:46:06-240881 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:06-241081 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:06-241340 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:06-241607 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:06-241864 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:06-242074 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:06-242259 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:06-242432 cadet-con-8620 DEBUG   ACK 67 (was 66)
Jul 07 20:46:06-242662 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:06-242892 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:06-243097 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:06-243280 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:06-243459 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:06-243670 util-scheduler-8620 DEBUG Adding task: 1783 / 0x46620a0
Jul 07 20:46:06-606970 util-scheduler-8620 DEBUG Checking readiness of task: 1783 / 0x46620a0
Jul 07 20:46:06-607355 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:06-607555 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:06-607763 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:06-607955 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:06-608146 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:06-608337 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:06-608527 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:06-608735 util-scheduler-8620 DEBUG Running task: 1780 / 0x5e33a48
Jul 07 20:46:06-608916 cadet-chn-8620 DEBUG !!! RE-CREATE
Jul 07 20:46:06-609226 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:06-609446 util-scheduler-8620 DEBUG Adding task: 1784 / 0x4d5e5d8
Jul 07 20:46:06-609735 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:06-609955 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:06-610157 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:06-610339 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:06-610523 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:06-610704 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:06-610882 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:06-611050 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:06-611268 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:06-611440 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:06-611678 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:06-611966 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:06-612152 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:06-612464 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:06-612637 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:06-612826 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:06-616508 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:06-617862 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:06-618102 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:06-618295 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:06-621602 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:06-621860 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:06-622044 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:06-622267 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:06-622475 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:06-622696 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:06-622889 cadet-tun-8620 DEBUG type {    CHANNEL_CREATE}
Jul 07 20:46:06-623171 cadet-con-8620 INFO --> {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (96 bytes)
Jul 07 20:46:06-623370 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:06-623553 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:06-623727 cadet-con-8620 DEBUG      ack recv 65
Jul 07 20:46:06-623899 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:06-624077 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:06-624312 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:06-624523 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:06-624843 cadet-p2p-8620 INFO que {         ENCRYPTED} ({    CHANNEL_CREATE} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 96)
Jul 07 20:46:06-625044 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:06-625289 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:06-625474 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 2
Jul 07 20:46:06-625649 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:06-625859 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 96 bytes
Jul 07 20:46:06-626077 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `D3TJ'
Jul 07 20:46:06-626309 util-scheduler-8620 DEBUG Adding task: 1785 / 0x5e2b838
Jul 07 20:46:06-626490 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:06-626695 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:06-626930 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:06-627107 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:06-627347 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:06-627543 cadet-p2p-8620 DEBUG QQQ    payload {    CHANNEL_CREATE}, 0
Jul 07 20:46:06-627721 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:06-627920 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:06-628190 util-scheduler-8620 DEBUG Checking readiness of task: 1784 / 0x4d5e5d8
Jul 07 20:46:06-628387 util-scheduler-8620 DEBUG Checking readiness of task: 1783 / 0x46620a0
Jul 07 20:46:06-628579 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:06-628769 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:06-628959 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:06-629149 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:06-629361 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:06-629550 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:06-629740 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:06-629933 util-scheduler-8620 DEBUG Running task: 1784 / 0x4d5e5d8
Jul 07 20:46:06-630119 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:06-630297 util-8620 DEBUG process_notify is running
Jul 07 20:46:06-630472 util-8620 DEBUG client_notify is running
Jul 07 20:46:06-630702 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:46:06-630962 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:06-631172 util-scheduler-8620 DEBUG Running task: 1785 / 0x5e2b838
Jul 07 20:46:06-631384 util-scheduler-8620 DEBUG Adding task: 1786 / 0x5e2b838
Jul 07 20:46:06-631606 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:06-631807 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:06-632012 util-scheduler-8620 DEBUG Adding task: 1787 / 0x46620a0
Jul 07 20:46:06-632255 util-scheduler-8620 DEBUG Checking readiness of task: 1787 / 0x46620a0
Jul 07 20:46:06-632451 util-scheduler-8620 DEBUG Checking readiness of task: 1783 / 0x46620a0
Jul 07 20:46:06-632676 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:06-632868 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:06-633057 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:06-633269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:06-633462 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:06-633653 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:06-633841 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:06-634032 util-scheduler-8620 DEBUG Running task: 1787 / 0x46620a0
Jul 07 20:46:06-634216 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:06-634392 util-8620 DEBUG process_notify is running
Jul 07 20:46:06-634561 util-8620 DEBUG client_notify is running
Jul 07 20:46:06-634742 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:06-634941 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:06-635137 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:06-635430 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:07-166581 util-scheduler-8620 DEBUG Checking readiness of task: 1783 / 0x46620a0
Jul 07 20:46:07-166926 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-167121 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-167315 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-167507 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-167698 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-167887 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-168078 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-168272 util-scheduler-8620 DEBUG Running task: 1783 / 0x46620a0
Jul 07 20:46:07-168699 util-8620 DEBUG receive_ready read 16192/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:07-168978 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:07-169224 util-scheduler-8620 DEBUG Adding task: 1788 / 0x46620a0
Jul 07 20:46:07-169520 util-scheduler-8620 DEBUG Checking readiness of task: 1788 / 0x46620a0
Jul 07 20:46:07-170377 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-170610 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-170805 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-170998 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-171186 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-171376 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-171570 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-171766 util-scheduler-8620 DEBUG Running task: 1788 / 0x46620a0
Jul 07 20:46:07-172183 util-8620 DEBUG receive_ready read 17220/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:07-172512 util-scheduler-8620 DEBUG Adding task: 1789 / 0x4662248
Jul 07 20:46:07-172783 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-172981 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-173175 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-173392 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-173585 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-173777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-174003 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-174202 util-scheduler-8620 DEBUG Running task: 1789 / 0x4662248
Jul 07 20:46:07-174404 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:46:07-174791 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:46:07-175029 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `V8XX'
Jul 07 20:46:07-175296 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:07-175544 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:07-175773 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:07-175983 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:07-176229 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:07-176441 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:07-176632 cadet-con-8620 DEBUG  PID 4 (expected 4+)
Jul 07 20:46:07-176814 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:07-177006 util-scheduler-8620 DEBUG Canceling task: 1726 / 0x4d707d0
Jul 07 20:46:07-177258 util-scheduler-8620 DEBUG Adding task: 1790 / 0x4d707d0
Jul 07 20:46:07-177441 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:07-177702 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:07-177917 util-scheduler-8620 DEBUG Adding task: 1791 / 0x4d5e5d8
Jul 07 20:46:07-178109 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:07-178278 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:07-181930 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:07-200247 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:07-200670 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:07-250234 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:07-250561 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:46:07-250862 cadet-chn-8620 INFO <=== DATA 0 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:07-251115 cadet-chn-8620 WARNING MID 0 on channel V8XX:19 gid:40000000 (80000002 / 0) not expected (window: 1 - 64). Dropping!
Jul 07 20:46:07-251308 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:46:07-251491 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:46:07-251737 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:07-252390 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:07-252588 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:46:07-252779 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:07-252966 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:07-253156 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:46:07-253364 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:07-253532 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:07-253720 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:07-253910 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:07-254109 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:07-254291 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:46:07-254471 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 3
Jul 07 20:46:07-254645 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:07-254875 cadet-p2p-8620 DEBUG Checking 0x5296118 towards CMHCKRVP (->V8XX)
Jul 07 20:46:07-255112 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:07-255396 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:07-255575 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-256132 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:07-256340 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:07-256523 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-256707 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:07-256890 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-257101 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-257297 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-257516 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:07-257691 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-257923 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:07-258110 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-258407 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:07-258578 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-258764 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:07-262118 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:07-262916 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:07-263165 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-263356 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:07-266586 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:07-266830 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:07-267014 cadet-tun-8620 DEBUG     q_n 1, 
Jul 07 20:46:07-267236 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:07-267432 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:07-267721 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:07-267926 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 1
Jul 07 20:46:07-268105 cadet-con-8620 DEBUG last pid sent 3
Jul 07 20:46:07-268280 cadet-con-8620 DEBUG      ack recv 67
Jul 07 20:46:07-268453 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:07-268633 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:07-268870 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:07-269080 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:07-269421 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:07-269624 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:07-269848 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:07-270031 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:07-270205 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-270408 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:07-270612 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:07-270789 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:07-270965 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:07-271202 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-271400 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:07-271578 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:07-271812 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-272020 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:07-272197 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:07-272395 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:07-272571 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:07-272804 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:07-272982 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:07-273157 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:07-273351 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:07-273573 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:07-273751 cadet-con-8620 DEBUG  ACK 68
Jul 07 20:46:07-273930 cadet-con-8620 DEBUG  last pid 4, last ack 67, qmax 11, q 0
Jul 07 20:46:07-274195 cadet-con-8620 INFO --> {               ACK} ( 68) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:07-274384 cadet-con-8620 DEBUG  ack 68
Jul 07 20:46:07-274561 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:07-274794 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:07-275000 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:07-275313 cadet-p2p-8620 INFO que {               ACK} ( 68) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:07-275511 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:07-275733 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:07-275915 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:07-276089 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-276288 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:07-276487 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:07-276663 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:07-276838 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:07-277073 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-277278 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:46:07-277455 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:07-277689 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-277881 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:07-278058 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:07-278290 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-278483 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:07-278660 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:07-278855 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:07-279041 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:07-279259 util-scheduler-8620 DEBUG Adding task: 1792 / 0x46620a0
Jul 07 20:46:07-279548 util-scheduler-8620 DEBUG Checking readiness of task: 1792 / 0x46620a0
Jul 07 20:46:07-279749 util-scheduler-8620 DEBUG Checking readiness of task: 1791 / 0x4d5e5d8
Jul 07 20:46:07-279941 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-280199 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-280423 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-280616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-280805 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-280996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-281185 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-281411 util-scheduler-8620 DEBUG Running task: 1791 / 0x4d5e5d8
Jul 07 20:46:07-281597 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:07-281776 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-281951 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-282210 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:07-282423 util-scheduler-8620 DEBUG Adding task: 1793 / 0x4d5e5d8
Jul 07 20:46:07-282628 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:07-282884 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:07-283085 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:07-283284 util-scheduler-8620 DEBUG Running task: 1792 / 0x46620a0
Jul 07 20:46:07-283689 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:07-283929 util-scheduler-8620 DEBUG Adding task: 1794 / 0x4662248
Jul 07 20:46:07-284188 util-scheduler-8620 DEBUG Checking readiness of task: 1793 / 0x4d5e5d8
Jul 07 20:46:07-284383 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-284575 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-284765 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-284954 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-285164 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-285378 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-285568 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-285758 util-scheduler-8620 DEBUG Running task: 1793 / 0x4d5e5d8
Jul 07 20:46:07-285942 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:07-286118 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-286288 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-286498 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:07-286742 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:07-286951 util-scheduler-8620 DEBUG Running task: 1794 / 0x4662248
Jul 07 20:46:07-287143 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:07-287340 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:07-287557 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:07-287810 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:07-288060 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-288267 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-288450 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:07-288623 cadet-con-8620 DEBUG   ACK 66 (was 65)
Jul 07 20:46:07-288851 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-289081 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-289309 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-289491 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:07-289665 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:07-289866 util-scheduler-8620 DEBUG Adding task: 1795 / 0x46620a0
Jul 07 20:46:07-363677 util-scheduler-8620 DEBUG Checking readiness of task: 1795 / 0x46620a0
Jul 07 20:46:07-363976 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-364172 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-364366 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-364557 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-364747 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-364937 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-365128 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-365349 util-scheduler-8620 DEBUG Running task: 1795 / 0x46620a0
Jul 07 20:46:07-365765 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:07-366013 util-scheduler-8620 DEBUG Adding task: 1796 / 0x4662248
Jul 07 20:46:07-366281 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-366474 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-366664 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-366854 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-367043 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-367246 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-367435 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-367626 util-scheduler-8620 DEBUG Running task: 1796 / 0x4662248
Jul 07 20:46:07-367815 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:07-368014 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:07-368239 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:07-368521 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:07-368763 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-368993 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-369222 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:07-369467 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-369674 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-369863 cadet-con-8620 DEBUG  PID 0 (expected 0+)
Jul 07 20:46:07-370043 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:07-370231 util-scheduler-8620 DEBUG Canceling task: 1572 / 0x5e31aa0
Jul 07 20:46:07-370455 util-scheduler-8620 DEBUG Adding task: 1797 / 0x5e31aa0
Jul 07 20:46:07-370634 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:07-370889 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:07-371103 util-scheduler-8620 DEBUG Adding task: 1798 / 0x4d5e5d8
Jul 07 20:46:07-371287 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:07-371473 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:07-375008 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:07-376323 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:07-376532 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:07-379772 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on D3TJ
Jul 07 20:46:07-380025 cadet-chn-8620 DEBUG   channel confirm FWD D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-380273 cadet-chn-8620 DEBUG   !! retry timer confirm 1 s
Jul 07 20:46:07-380479 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:07-380660 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-380846 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:07-381027 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-381226 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-381399 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-381614 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-381786 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-382020 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-382266 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-382452 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-382682 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-382868 cadet-loc-8620 DEBUG send local FWD ack on 80000003 towards 0x4d5c6d8
Jul 07 20:46:07-383080 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:07-383279 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:07-383485 util-scheduler-8620 DEBUG Adding task: 1799 / 0x4d5c418
Jul 07 20:46:07-383671 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:07-383858 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:46:07-384041 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:07-384222 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:07-384408 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:46:07-384581 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:07-384749 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:07-384936 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:46:07-385123 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:46:07-385340 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:07-385522 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:46:07-385700 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 2
Jul 07 20:46:07-385874 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:07-386078 core-api-8620 DEBUG Aborting transmission request to core for 96 bytes to `D3TJ'
Jul 07 20:46:07-386321 cadet-chn-8620 DEBUG   sending channel BCK ack for channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-386569 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-386803 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:07-387001 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:07-387178 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-387358 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:07-387537 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-387712 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-387881 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-388092 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-388262 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-388490 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-388733 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-388918 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-389225 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:07-389398 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-389583 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:07-392678 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:07-393352 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:07-393589 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-393782 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:07-397175 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:07-397475 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:07-397659 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:07-397882 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:07-398061 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:07-398280 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-398474 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:46:07-398747 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (88 bytes)
Jul 07 20:46:07-398945 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:07-399122 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:07-399295 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:46:07-399466 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:07-399642 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:07-399875 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-400083 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-400394 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 88)
Jul 07 20:46:07-400593 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:07-400817 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-401000 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:07-401175 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-401489 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 88 bytes
Jul 07 20:46:07-401714 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:07-401941 util-scheduler-8620 DEBUG Adding task: 1800 / 0x5e2b838
Jul 07 20:46:07-402122 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:07-402327 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:07-402504 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:07-402679 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:07-402918 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-403113 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:07-403291 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:07-403489 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:07-403727 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-403903 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:07-404079 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:07-404250 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:07-404491 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-404670 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:46:07-404849 cadet-con-8620 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 20:46:07-405114 cadet-con-8620 INFO --> {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:07-405325 cadet-con-8620 DEBUG  ack 64
Jul 07 20:46:07-405503 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:07-405737 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-405943 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-406231 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:07-406429 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:07-406651 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-406832 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:07-407006 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-407205 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:07-407404 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:07-407579 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:07-407752 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:07-407987 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-408169 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:46:07-408343 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:07-408576 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-408768 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:07-408944 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:07-409140 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:07-409343 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:07-409553 util-scheduler-8620 DEBUG Adding task: 1801 / 0x46620a0
Jul 07 20:46:07-409825 util-scheduler-8620 DEBUG Checking readiness of task: 1801 / 0x46620a0
Jul 07 20:46:07-410024 util-scheduler-8620 DEBUG Checking readiness of task: 1799 / 0x4d5c418
Jul 07 20:46:07-410216 util-scheduler-8620 DEBUG Checking readiness of task: 1798 / 0x4d5e5d8
Jul 07 20:46:07-410407 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-410597 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-410787 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-410977 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-411168 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-411357 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-411546 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-411739 util-scheduler-8620 DEBUG Running task: 1798 / 0x4d5e5d8
Jul 07 20:46:07-411926 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:07-412105 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-412279 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-412506 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:07-412764 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:07-412976 util-scheduler-8620 DEBUG Running task: 1799 / 0x4d5c418
Jul 07 20:46:07-413160 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:07-413355 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-413547 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:07-413783 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:07-413988 util-scheduler-8620 DEBUG Running task: 1800 / 0x5e2b838
Jul 07 20:46:07-414184 util-scheduler-8620 DEBUG Canceling task: 1786 / 0x5e2b838
Jul 07 20:46:07-414419 util-scheduler-8620 DEBUG Adding task: 1802 / 0x5e2b838
Jul 07 20:46:07-414643 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:07-414844 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:07-415044 util-scheduler-8620 DEBUG Adding task: 1803 / 0x46620a0
Jul 07 20:46:07-415287 util-scheduler-8620 DEBUG Checking readiness of task: 1803 / 0x46620a0
Jul 07 20:46:07-415480 util-scheduler-8620 DEBUG Checking readiness of task: 1801 / 0x46620a0
Jul 07 20:46:07-415671 util-scheduler-8620 DEBUG Checking readiness of task: 1735 / 0x4d5c418
Jul 07 20:46:07-415862 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-416052 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-416242 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-416430 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-416620 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-416808 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-416998 util-scheduler-8620 DEBUG Running task: 1735 / 0x4d5c418
Jul 07 20:46:07-417400 util-8620 DEBUG receive_ready read 88/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:46:07-417610 util-8620 DEBUG Server receives 88 bytes from `<unbound UNIX client>'.
Jul 07 20:46:07-417801 util-8620 DEBUG Server-mst receives 88 bytes with 0 bytes already in private buffer
Jul 07 20:46:07-417989 util-8620 DEBUG Server-mst has 88 bytes left in inbound buffer
Jul 07 20:46:07-418171 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:46:07-418372 util-8620 DEBUG Server schedules transmission of 88-byte message of type 285 to client.
Jul 07 20:46:07-418587 util-scheduler-8620 DEBUG Adding task: 1804 / 0x4d5c578
Jul 07 20:46:07-418768 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:46:07-418941 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:07-419117 cadet-loc-8620 DEBUG   on channel 80000003
Jul 07 20:46:07-419298 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:46:07-419541 cadet-chn-8620 INFO ===> {              DATA} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-419740 cadet-chn-8620 INFO ===> {              DATA} 0
Jul 07 20:46:07-419941 cadet-chn-8620 DEBUG !!! SAVE 0 {              DATA}
Jul 07 20:46:07-420126 cadet-chn-8620 DEBUG   at 0x5157240
Jul 07 20:46:07-420305 cadet-chn-8620 DEBUG   new chq: 0x530e938
Jul 07 20:46:07-420507 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:07-420705 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:07-420885 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-421067 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:07-421269 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-421462 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-421631 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-421845 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-422017 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-422247 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-422492 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-422677 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-422949 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:07-423122 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-423305 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:07-426699 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:07-427553 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:07-427806 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:07-427998 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:07-431361 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:07-431615 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:07-431826 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:07-432052 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:07-432232 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:07-432453 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-432649 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:07-432929 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 0) on connection 1KSG9GE2 (->D3TJ) (172 bytes)
Jul 07 20:46:07-433130 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:07-433333 cadet-con-8620 DEBUG last pid sent 2
Jul 07 20:46:07-433507 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:46:07-433690 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:07-433927 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:07-434136 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:07-434452 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 172)
Jul 07 20:46:07-434653 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:07-434879 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-435064 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:07-435239 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-435442 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:07-435645 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:07-435823 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:07-435997 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:07-436237 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-436420 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:46:07-436595 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:07-436828 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-437022 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:07-437218 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:07-437453 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:07-437646 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:07-437823 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:07-438020 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:07-438226 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:07-438405 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-438587 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:07-438767 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-438944 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-439112 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-439326 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-439497 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-439728 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:07-439971 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-440156 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-440328 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:07-440504 cadet-chn-8620 DEBUG  gap ok: 0 - 1
Jul 07 20:46:07-440706 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:07-440882 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:07-441063 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:07-441260 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:07-441436 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:07-441604 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:07-441865 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-442038 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:07-442266 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:07-442526 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:07-442712 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:07-442886 cadet-chn-8620 DEBUG  buffer space 21, allowing
Jul 07 20:46:07-443110 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:07-443296 cadet-loc-8620 DEBUG send local FWD ack on 80000003 towards 0x4d5c6d8
Jul 07 20:46:07-443504 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:07-443723 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:07-443934 util-scheduler-8620 DEBUG Adding task: 1805 / 0x4d5c418
Jul 07 20:46:07-444117 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:46:07-444301 util-scheduler-8620 DEBUG Canceling task: 1804 / 0x4d5c578
Jul 07 20:46:07-444497 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:07-444678 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:46:07-444885 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:46:07-445089 util-scheduler-8620 DEBUG Adding task: 1806 / 0x4d5c418
Jul 07 20:46:07-445311 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:46:07-445540 util-scheduler-8620 DEBUG Running task: 1803 / 0x46620a0
Jul 07 20:46:07-445729 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:07-445907 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-446078 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-446258 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:07-446453 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:07-446645 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:07-446946 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:07-447222 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-447419 util-scheduler-8620 DEBUG Checking readiness of task: 1805 / 0x4d5c418
Jul 07 20:46:07-447612 util-scheduler-8620 DEBUG Checking readiness of task: 1801 / 0x46620a0
Jul 07 20:46:07-447804 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-447995 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-448186 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-448376 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-448566 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-448755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-448946 util-scheduler-8620 DEBUG Running task: 1805 / 0x4d5c418
Jul 07 20:46:07-449129 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:07-449326 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-449517 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:07-449751 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:07-901343 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-901696 util-scheduler-8620 DEBUG Checking readiness of task: 1801 / 0x46620a0
Jul 07 20:46:07-901895 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-902087 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-902278 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-902469 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-902659 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-902851 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-903080 util-scheduler-8620 DEBUG Running task: 1801 / 0x46620a0
Jul 07 20:46:07-903513 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:07-903777 util-scheduler-8620 DEBUG Adding task: 1807 / 0x4662248
Jul 07 20:46:07-904064 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-904263 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-904458 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-904653 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-904847 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-905041 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-905256 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-905447 util-scheduler-8620 DEBUG Running task: 1807 / 0x4662248
Jul 07 20:46:07-905641 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:07-905841 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:07-906074 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:07-906280 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:07-906485 util-scheduler-8620 DEBUG Adding task: 1808 / 0x46620a0
Jul 07 20:46:07-906672 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:07-906876 util-scheduler-8620 DEBUG Adding task: 1809 / 0x46620a0
Jul 07 20:46:07-907123 util-scheduler-8620 DEBUG Checking readiness of task: 1809 / 0x46620a0
Jul 07 20:46:07-907316 util-scheduler-8620 DEBUG Checking readiness of task: 1808 / 0x46620a0
Jul 07 20:46:07-907507 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-907696 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-907885 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-908076 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-908263 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-908451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-908639 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-908830 util-scheduler-8620 DEBUG Running task: 1808 / 0x46620a0
Jul 07 20:46:07-909014 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:07-909210 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-909385 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-909574 util-scheduler-8620 DEBUG Canceling task: 1771 / 0x4d6ff98
Jul 07 20:46:07-909798 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:07-910019 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:07-910257 cadet-p2p-8620 DEBUG Checking 0x52e2e00 towards CMHCKRVP (->V8XX)
Jul 07 20:46:07-910490 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:07-910669 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:07-910859 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:07-911128 cadet-p2p-8620 INFO snd {               ACK} ( 68) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:07-911323 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:07-911503 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:07-911690 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:07-911863 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:07-912046 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:07-912221 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:07-912441 cadet-p2p-8620 DEBUG Checking 0x5296118 towards CMHCKRVP (->V8XX)
Jul 07 20:46:07-912674 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:07-912856 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:07-913052 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-913299 cadet-p2p-8620 DEBUG Checking 0x5296118 towards CMHCKRVP (->V8XX)
Jul 07 20:46:07-913530 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:07-913710 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:07-913883 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:07-914048 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:07-914253 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `V8XX'
Jul 07 20:46:07-914467 util-scheduler-8620 DEBUG Adding task: 1810 / 0x4d6ff98
Jul 07 20:46:07-914646 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:07-914822 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:07-915020 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:07-915196 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:07-915369 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:07-915607 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-915805 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:07-915985 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:07-916226 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:07-916425 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:07-916618 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:07-916824 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:07-917034 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:07-917245 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:07-917461 util-scheduler-8620 DEBUG Adding task: 1811 / 0x4d6ff98
Jul 07 20:46:07-917690 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:07-917891 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:07-918095 util-scheduler-8620 DEBUG Adding task: 1812 / 0x46620a0
Jul 07 20:46:07-918298 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:07-919036 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:07-919237 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:07-919490 util-scheduler-8620 DEBUG Checking readiness of task: 1812 / 0x46620a0
Jul 07 20:46:07-919686 util-scheduler-8620 DEBUG Checking readiness of task: 1809 / 0x46620a0
Jul 07 20:46:07-919876 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-920065 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-920254 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-920444 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-920632 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-920821 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-921009 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-921222 util-scheduler-8620 DEBUG Running task: 1812 / 0x46620a0
Jul 07 20:46:07-921408 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:07-921585 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-921755 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-921934 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:07-922129 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:07-922318 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:07-922599 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:07-922806 util-scheduler-8620 DEBUG Running task: 1810 / 0x4d6ff98
Jul 07 20:46:07-923019 util-scheduler-8620 DEBUG Canceling task: 1811 / 0x4d6ff98
Jul 07 20:46:07-923238 util-scheduler-8620 DEBUG Adding task: 1813 / 0x4d6ff98
Jul 07 20:46:07-923456 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:07-923649 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:07-923846 util-scheduler-8620 DEBUG Adding task: 1814 / 0x46620a0
Jul 07 20:46:07-924084 util-scheduler-8620 DEBUG Checking readiness of task: 1814 / 0x46620a0
Jul 07 20:46:07-924278 util-scheduler-8620 DEBUG Checking readiness of task: 1809 / 0x46620a0
Jul 07 20:46:07-924467 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:07-924656 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:07-924846 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:07-925034 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:07-925242 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:07-925431 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:07-925620 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:07-925810 util-scheduler-8620 DEBUG Running task: 1814 / 0x46620a0
Jul 07 20:46:07-925995 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:07-926168 util-8620 DEBUG process_notify is running
Jul 07 20:46:07-926337 util-8620 DEBUG client_notify is running
Jul 07 20:46:07-926512 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:07-926701 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:07-926888 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:07-927167 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:08-388632 util-scheduler-8620 DEBUG Checking readiness of task: 1809 / 0x46620a0
Jul 07 20:46:08-388966 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-389163 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:08-389381 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-389573 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-389762 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-389953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-390142 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-390336 util-scheduler-8620 DEBUG Running task: 1809 / 0x46620a0
Jul 07 20:46:08-390751 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:08-391001 util-scheduler-8620 DEBUG Adding task: 1815 / 0x4662248
Jul 07 20:46:08-391272 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-391465 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:08-391657 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-391847 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-392037 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-392226 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-392415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-392603 util-scheduler-8620 DEBUG Running task: 1815 / 0x4662248
Jul 07 20:46:08-392794 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:08-392992 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:08-394037 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `D3TJ'
Jul 07 20:46:08-394305 cadet-con-8620 INFO <-- {              POLL} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:08-394586 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:08-394797 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:08-394983 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:46:08-395156 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:46:08-395385 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:08-395560 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:08-395734 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:08-395906 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:08-396127 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:08-396304 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:46:08-396484 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:46:08-396665 cadet-con-8620 DEBUG  same ACK already in queue
Jul 07 20:46:08-396842 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:08-397052 util-scheduler-8620 DEBUG Adding task: 1816 / 0x46620a0
Jul 07 20:46:08-621913 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-622272 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-622472 util-scheduler-8620 DEBUG Checking readiness of task: 1646 / 0x4663d68
Jul 07 20:46:08-622669 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-622861 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-623055 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-623245 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-623438 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-623633 util-scheduler-8620 DEBUG Running task: 1646 / 0x4663d68
Jul 07 20:46:08-624056 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:46:08-624309 util-scheduler-8620 DEBUG Adding task: 1817 / 0x4663f10
Jul 07 20:46:08-624587 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-624782 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-624973 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-625163 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-625382 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-625586 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-625775 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-625965 util-scheduler-8620 DEBUG Running task: 1817 / 0x4663f10
Jul 07 20:46:08-626158 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:46:08-626354 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:08-626569 util-scheduler-8620 DEBUG Adding task: 1818 / 0x4663d68
Jul 07 20:46:08-626757 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:46:08-626986 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 11469
Jul 07 20:46:08-627181 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 11469 Bps
Jul 07 20:46:08-627444 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11601 Bps, last update was 10 s ago
Jul 07 20:46:08-627681 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11469 Bps, last update was 269 µs ago
Jul 07 20:46:08-627897 util-scheduler-8620 DEBUG Adding task: 1819 / 0x4d6fa48
Jul 07 20:46:08-628138 util-scheduler-8620 DEBUG Checking readiness of task: 1818 / 0x4663d68
Jul 07 20:46:08-628331 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-628522 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-628712 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-628902 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-629117 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-629333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-629522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-629713 util-scheduler-8620 DEBUG Running task: 1819 / 0x4d6fa48
Jul 07 20:46:08-748805 util-scheduler-8620 DEBUG Checking readiness of task: 1818 / 0x4663d68
Jul 07 20:46:08-749051 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-749310 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-749504 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-749697 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-749887 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-750077 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-750266 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-750459 util-scheduler-8620 DEBUG Running task: 1818 / 0x4663d68
Jul 07 20:46:08-750868 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:46:08-751103 util-scheduler-8620 DEBUG Adding task: 1820 / 0x4663f10
Jul 07 20:46:08-751359 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-751552 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-751743 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-751934 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-752124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-752313 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-752501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-752690 util-scheduler-8620 DEBUG Running task: 1820 / 0x4663f10
Jul 07 20:46:08-752882 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:46:08-753073 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:08-753299 util-scheduler-8620 DEBUG Adding task: 1821 / 0x4663d68
Jul 07 20:46:08-753486 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:46:08-753703 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 11469
Jul 07 20:46:08-753893 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 bandwidth changed to 11469 Bps
Jul 07 20:46:08-754135 util-bandwidth-8620 DEBUG Tracker 0x4d6fa48 updated, have 11469 Bps, last update was 126 ms ago
Jul 07 20:46:08-754352 util-scheduler-8620 DEBUG Adding task: 1822 / 0x4d6fa48
Jul 07 20:46:08-754607 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:08-754800 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:08-754990 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:08-755180 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:08-755370 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:08-755561 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:08-755751 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:08-755941 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:08-756130 util-scheduler-8620 DEBUG Running task: 1822 / 0x4d6fa48
Jul 07 20:46:09-104730 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-105148 util-scheduler-8620 DEBUG Checking readiness of task: 1816 / 0x46620a0
Jul 07 20:46:09-105395 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-105605 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-105840 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-106040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-106252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-106472 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-106677 util-scheduler-8620 DEBUG Running task: 1816 / 0x46620a0
Jul 07 20:46:09-107105 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:09-107357 util-scheduler-8620 DEBUG Adding task: 1823 / 0x4662248
Jul 07 20:46:09-107637 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-107831 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-108021 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-108213 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-108402 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-108591 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-108780 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-108968 util-scheduler-8620 DEBUG Running task: 1823 / 0x4662248
Jul 07 20:46:09-109158 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:09-109385 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:09-109617 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:09-109827 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-110034 util-scheduler-8620 DEBUG Adding task: 1824 / 0x46620a0
Jul 07 20:46:09-110226 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:09-110437 util-scheduler-8620 DEBUG Adding task: 1825 / 0x46620a0
Jul 07 20:46:09-110684 util-scheduler-8620 DEBUG Checking readiness of task: 1825 / 0x46620a0
Jul 07 20:46:09-110879 util-scheduler-8620 DEBUG Checking readiness of task: 1824 / 0x46620a0
Jul 07 20:46:09-111071 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-111262 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-111451 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-111642 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-111831 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-112019 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-112209 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-112401 util-scheduler-8620 DEBUG Running task: 1824 / 0x46620a0
Jul 07 20:46:09-112587 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-112765 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-112937 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-113130 util-scheduler-8620 DEBUG Canceling task: 1802 / 0x5e2b838
Jul 07 20:46:09-113380 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:09-113602 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:09-113841 cadet-p2p-8620 DEBUG Checking 0x530d5c8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-114077 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:09-114255 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:09-114446 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:09-114715 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:09-114925 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:09-115104 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:09-115292 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:09-115466 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:09-115671 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:09-115847 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:09-116067 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-116299 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-116483 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:09-116658 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-116885 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-117114 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-117316 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:09-117490 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-117656 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:09-117861 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:09-118078 util-scheduler-8620 DEBUG Adding task: 1826 / 0x5e2b838
Jul 07 20:46:09-118259 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:09-118436 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:09-118635 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:09-118810 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:09-118983 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:09-119222 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-119416 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:09-119593 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:09-119827 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-120020 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:09-120197 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:09-120395 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:09-120600 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:09-120783 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:09-120987 util-scheduler-8620 DEBUG Adding task: 1827 / 0x5e2b838
Jul 07 20:46:09-121225 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:09-121422 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-121623 util-scheduler-8620 DEBUG Adding task: 1828 / 0x46620a0
Jul 07 20:46:09-121824 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:09-122073 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-122269 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:09-122513 util-scheduler-8620 DEBUG Checking readiness of task: 1828 / 0x46620a0
Jul 07 20:46:09-122709 util-scheduler-8620 DEBUG Checking readiness of task: 1825 / 0x46620a0
Jul 07 20:46:09-122900 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-123091 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-123281 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-123472 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-123661 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-123850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-124041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-124234 util-scheduler-8620 DEBUG Running task: 1828 / 0x46620a0
Jul 07 20:46:09-124417 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-124594 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-124765 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-124944 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:09-125137 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:09-125363 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:09-125604 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-125810 util-scheduler-8620 DEBUG Running task: 1826 / 0x5e2b838
Jul 07 20:46:09-126003 util-scheduler-8620 DEBUG Canceling task: 1827 / 0x5e2b838
Jul 07 20:46:09-126215 util-scheduler-8620 DEBUG Adding task: 1829 / 0x5e2b838
Jul 07 20:46:09-126431 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:09-126624 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-126822 util-scheduler-8620 DEBUG Adding task: 1830 / 0x46620a0
Jul 07 20:46:09-127060 util-scheduler-8620 DEBUG Checking readiness of task: 1830 / 0x46620a0
Jul 07 20:46:09-127253 util-scheduler-8620 DEBUG Checking readiness of task: 1825 / 0x46620a0
Jul 07 20:46:09-127444 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-127634 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-127825 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-128032 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-128223 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-128412 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-128600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-128790 util-scheduler-8620 DEBUG Running task: 1830 / 0x46620a0
Jul 07 20:46:09-128974 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-129149 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-129340 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-129517 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:09-129708 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:09-129896 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:09-130135 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-237399 util-scheduler-8620 DEBUG Checking readiness of task: 1825 / 0x46620a0
Jul 07 20:46:09-237671 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-237868 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-238060 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-238251 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-238442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-238633 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-238822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-239016 util-scheduler-8620 DEBUG Running task: 1825 / 0x46620a0
Jul 07 20:46:09-239424 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:09-239665 util-scheduler-8620 DEBUG Adding task: 1831 / 0x4662248
Jul 07 20:46:09-239925 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-240119 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-240311 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-240501 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-240693 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-240882 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-241072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-241289 util-scheduler-8620 DEBUG Running task: 1831 / 0x4662248
Jul 07 20:46:09-241504 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:09-241702 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:09-241923 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:09-242124 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-242326 util-scheduler-8620 DEBUG Adding task: 1832 / 0x46620a0
Jul 07 20:46:09-242511 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:09-242713 util-scheduler-8620 DEBUG Adding task: 1833 / 0x46620a0
Jul 07 20:46:09-242955 util-scheduler-8620 DEBUG Checking readiness of task: 1833 / 0x46620a0
Jul 07 20:46:09-243159 util-scheduler-8620 DEBUG Checking readiness of task: 1832 / 0x46620a0
Jul 07 20:46:09-243350 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-243542 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-243732 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-243921 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-244111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-244300 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-244487 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-244679 util-scheduler-8620 DEBUG Running task: 1832 / 0x46620a0
Jul 07 20:46:09-244862 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-245040 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-245231 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-245420 util-scheduler-8620 DEBUG Canceling task: 1813 / 0x4d6ff98
Jul 07 20:46:09-245641 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 156 bytes.
Jul 07 20:46:09-245859 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:09-246093 cadet-p2p-8620 DEBUG Checking 0x5296118 towards CMHCKRVP (->V8XX)
Jul 07 20:46:09-246325 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:09-246507 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 3
Jul 07 20:46:09-246680 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-246902 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:09-247078 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:46:09-247252 cadet-p2p-8620 DEBUG   payload ID 4
Jul 07 20:46:09-247535 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 156)
Jul 07 20:46:09-247729 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:09-247906 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:09-248093 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:09-248265 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:09-248433 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:09-248621 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:09-248799 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:46:09-249027 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 875 ms
Jul 07 20:46:09-249223 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:09-249430 cadet-chn-8620 DEBUG !! using delay 3502932 µs
Jul 07 20:46:09-249626 util-scheduler-8620 DEBUG Adding task: 1834 / 0x4d65218
Jul 07 20:46:09-249828 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:09-250057 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:09-250234 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:09-250406 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:09-250578 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:09-250775 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:09-250950 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:09-251123 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:09-251324 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:09-251503 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:09-251706 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:09-251887 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:09-252064 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:09-252234 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:09-252451 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:09-252624 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:09-252856 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:09-253042 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:09-253243 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:09-253431 util-scheduler-8620 DEBUG Canceling task: 1767 / 0x4d707d0
Jul 07 20:46:09-253647 util-scheduler-8620 DEBUG Adding task: 1835 / 0x4d707d0
Jul 07 20:46:09-253892 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:09-254071 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:46:09-254248 cadet-con-8620 DEBUG !   accounting pid 4
Jul 07 20:46:09-254419 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:09-254639 cadet-p2p-8620 DEBUG Checking 0x52e2238 towards CMHCKRVP (->V8XX)
Jul 07 20:46:09-254869 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:09-255051 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:09-255224 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-255450 cadet-p2p-8620 DEBUG Checking 0x52e2238 towards CMHCKRVP (->V8XX)
Jul 07 20:46:09-255679 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:09-255861 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:09-256033 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-256200 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:09-256403 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:09-256613 util-scheduler-8620 DEBUG Adding task: 1836 / 0x4d6ff98
Jul 07 20:46:09-256791 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:09-256969 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:46:09-257166 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:09-257365 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:09-257540 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:09-257777 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:09-257971 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:09-258148 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:09-258346 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:09-258550 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 156 bytes.
Jul 07 20:46:09-258733 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:46:09-258934 util-scheduler-8620 DEBUG Adding task: 1837 / 0x4d6ff98
Jul 07 20:46:09-259153 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:09-259347 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-259547 util-scheduler-8620 DEBUG Adding task: 1838 / 0x46620a0
Jul 07 20:46:09-259748 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:46:09-259995 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-260193 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:09-260439 util-scheduler-8620 DEBUG Checking readiness of task: 1838 / 0x46620a0
Jul 07 20:46:09-260636 util-scheduler-8620 DEBUG Checking readiness of task: 1833 / 0x46620a0
Jul 07 20:46:09-260826 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-261016 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-261229 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-261421 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-261629 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-261820 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-262008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-262201 util-scheduler-8620 DEBUG Running task: 1838 / 0x46620a0
Jul 07 20:46:09-262386 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-262563 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-262734 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-262912 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:09-263107 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:09-263295 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:09-263530 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-263738 util-scheduler-8620 DEBUG Running task: 1836 / 0x4d6ff98
Jul 07 20:46:09-263943 util-scheduler-8620 DEBUG Canceling task: 1837 / 0x4d6ff98
Jul 07 20:46:09-264158 util-scheduler-8620 DEBUG Adding task: 1839 / 0x4d6ff98
Jul 07 20:46:09-264376 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:09-264589 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-264794 util-scheduler-8620 DEBUG Adding task: 1840 / 0x46620a0
Jul 07 20:46:09-265036 util-scheduler-8620 DEBUG Checking readiness of task: 1840 / 0x46620a0
Jul 07 20:46:09-265251 util-scheduler-8620 DEBUG Checking readiness of task: 1833 / 0x46620a0
Jul 07 20:46:09-265445 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-265636 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-265825 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-266015 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-266206 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-266395 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-266584 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-266774 util-scheduler-8620 DEBUG Running task: 1833 / 0x46620a0
Jul 07 20:46:09-267174 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:09-267406 util-scheduler-8620 DEBUG Adding task: 1841 / 0x4662248
Jul 07 20:46:09-267616 util-scheduler-8620 DEBUG Running task: 1840 / 0x46620a0
Jul 07 20:46:09-267802 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-267977 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-268146 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-268323 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:09-268512 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:09-268700 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:09-268940 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-269185 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-269399 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-269590 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-269781 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-269968 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-270158 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-270346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-270535 util-scheduler-8620 DEBUG Running task: 1841 / 0x4662248
Jul 07 20:46:09-270738 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:09-270934 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:09-271147 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:09-271327 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:09-271528 util-scheduler-8620 DEBUG Adding task: 1842 / 0x46620a0
Jul 07 20:46:09-271767 util-scheduler-8620 DEBUG Checking readiness of task: 1842 / 0x46620a0
Jul 07 20:46:09-271961 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-272150 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-272341 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-272530 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-272718 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-272908 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-273096 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-273312 util-scheduler-8620 DEBUG Running task: 1842 / 0x46620a0
Jul 07 20:46:09-273723 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:09-273956 util-scheduler-8620 DEBUG Adding task: 1843 / 0x4662248
Jul 07 20:46:09-274208 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-274402 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-274593 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-274784 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-274973 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-275164 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-275353 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-275544 util-scheduler-8620 DEBUG Running task: 1843 / 0x4662248
Jul 07 20:46:09-275733 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:09-275927 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:09-276140 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:09-276337 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:09-276537 util-scheduler-8620 DEBUG Adding task: 1844 / 0x46620a0
Jul 07 20:46:09-276721 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:09-276921 util-scheduler-8620 DEBUG Adding task: 1845 / 0x46620a0
Jul 07 20:46:09-277161 util-scheduler-8620 DEBUG Checking readiness of task: 1845 / 0x46620a0
Jul 07 20:46:09-277378 util-scheduler-8620 DEBUG Checking readiness of task: 1844 / 0x46620a0
Jul 07 20:46:09-277570 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-277762 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-277952 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-278143 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-278333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-278523 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-278712 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-278903 util-scheduler-8620 DEBUG Running task: 1844 / 0x46620a0
Jul 07 20:46:09-279089 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:09-279264 util-8620 DEBUG process_notify is running
Jul 07 20:46:09-279435 util-8620 DEBUG client_notify is running
Jul 07 20:46:09-279620 util-scheduler-8620 DEBUG Canceling task: 1839 / 0x4d6ff98
Jul 07 20:46:09-279844 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:09-280078 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:09-280314 cadet-p2p-8620 DEBUG Checking 0x52e2238 towards CMHCKRVP (->V8XX)
Jul 07 20:46:09-280547 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:09-280730 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:09-280906 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-281126 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:09-281330 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:09-281504 cadet-p2p-8620 DEBUG   payload ID 5
Jul 07 20:46:09-281788 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:46:09-281983 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:09-282161 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:09-282348 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:09-282522 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:09-282690 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:09-282877 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:09-283067 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:09-283264 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:09-283492 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:09-283670 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:09-283842 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:09-284014 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:09-284212 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:09-284387 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:09-284561 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:09-284760 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:09-284938 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:09-285121 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:09-285334 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:09-285511 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:09-285681 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:09-285897 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:09-286071 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:09-286304 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:09-286489 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:09-286666 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:09-286852 util-scheduler-8620 DEBUG Canceling task: 1835 / 0x4d707d0
Jul 07 20:46:09-287067 util-scheduler-8620 DEBUG Adding task: 1846 / 0x4d707d0
Jul 07 20:46:09-287314 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:09-287494 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:09-287672 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 5
Jul 07 20:46:09-287846 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:09-288029 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:09-288229 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:09-288407 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:09-288581 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:09-288780 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:09-288984 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:46:09-289168 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:09-289369 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:09-289559 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:09-290741 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:09-801494 util-scheduler-8620 DEBUG Checking readiness of task: 1845 / 0x46620a0
Jul 07 20:46:09-801872 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-802069 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-802262 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-802453 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-802644 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-802834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-803023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-803217 util-scheduler-8620 DEBUG Running task: 1845 / 0x46620a0
Jul 07 20:46:09-803640 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:09-803896 util-scheduler-8620 DEBUG Adding task: 1847 / 0x4662248
Jul 07 20:46:09-804170 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:09-804364 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:09-804555 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:09-804746 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:09-804939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:09-805129 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:09-805343 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:09-805532 util-scheduler-8620 DEBUG Running task: 1847 / 0x4662248
Jul 07 20:46:09-805723 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:09-805921 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:09-806148 core-api-8620 DEBUG Received message of type 269 and size 40 from peer `D3TJ'
Jul 07 20:46:09-806410 cadet-con-8620 INFO <-- {              POLL} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:09-806661 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:09-806868 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:09-807053 cadet-con-8620 DEBUG   FWD FC
Jul 07 20:46:09-807227 cadet-con-8620 DEBUG   PID 0, OLD 0
Jul 07 20:46:09-807456 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-807630 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:09-807804 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:09-807974 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:09-808195 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-808373 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:46:09-808552 cadet-con-8620 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 20:46:09-808820 cadet-con-8620 INFO --> {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:09-809010 cadet-con-8620 DEBUG  ack 64
Jul 07 20:46:09-809187 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:09-809443 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:09-809648 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:09-809941 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:09-810139 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:09-810363 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-810546 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:09-810720 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:09-810922 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:09-811146 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:09-811323 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:09-811497 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:09-811733 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-811917 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:46:09-812111 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:09-812344 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-812537 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:09-812715 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:09-812953 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:09-813150 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:09-813351 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:09-813553 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:09-813743 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:09-813956 util-scheduler-8620 DEBUG Adding task: 1848 / 0x46620a0
Jul 07 20:46:10-113012 util-scheduler-8620 DEBUG Checking readiness of task: 1848 / 0x46620a0
Jul 07 20:46:10-113361 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-113561 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-113759 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-113955 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-114154 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-114345 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-114536 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-114731 util-scheduler-8620 DEBUG Running task: 1848 / 0x46620a0
Jul 07 20:46:10-115157 util-8620 DEBUG receive_ready read 16192/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:10-115438 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:10-115658 util-scheduler-8620 DEBUG Adding task: 1849 / 0x46620a0
Jul 07 20:46:10-115966 util-scheduler-8620 DEBUG Checking readiness of task: 1849 / 0x46620a0
Jul 07 20:46:10-116165 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-116357 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-116548 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-116740 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-116930 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-117137 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-117357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-117552 util-scheduler-8620 DEBUG Running task: 1849 / 0x46620a0
Jul 07 20:46:10-117959 util-8620 DEBUG receive_ready read 16192/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:10-118229 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:10-118433 util-scheduler-8620 DEBUG Adding task: 1850 / 0x46620a0
Jul 07 20:46:10-118718 util-scheduler-8620 DEBUG Checking readiness of task: 1850 / 0x46620a0
Jul 07 20:46:10-118916 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-119106 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-119297 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-119486 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-119677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-119866 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-120055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-120245 util-scheduler-8620 DEBUG Running task: 1850 / 0x46620a0
Jul 07 20:46:10-120644 util-8620 DEBUG receive_ready read 1028/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:10-120878 util-scheduler-8620 DEBUG Adding task: 1851 / 0x4662248
Jul 07 20:46:10-121153 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-121380 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-121575 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-121768 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-121960 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-122149 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-122341 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-122530 util-scheduler-8620 DEBUG Running task: 1851 / 0x4662248
Jul 07 20:46:10-122729 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:46:10-123148 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:46:10-123381 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `V8XX'
Jul 07 20:46:10-123652 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:10-123905 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:10-124134 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:10-124341 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:10-124586 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:10-124796 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:10-124984 cadet-con-8620 DEBUG  PID 5 (expected 5+)
Jul 07 20:46:10-125164 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:10-125381 util-scheduler-8620 DEBUG Canceling task: 1790 / 0x4d707d0
Jul 07 20:46:10-125610 util-scheduler-8620 DEBUG Adding task: 1852 / 0x4d707d0
Jul 07 20:46:10-125790 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:10-126052 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:10-126266 util-scheduler-8620 DEBUG Adding task: 1853 / 0x4d5e5d8
Jul 07 20:46:10-126458 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:10-126625 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:10-130718 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:10-148179 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:10-148398 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:10-196594 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:10-196827 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:46:10-197117 cadet-chn-8620 INFO <=== DATA 0 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:10-197392 cadet-chn-8620 WARNING MID 0 on channel V8XX:19 gid:40000000 (80000002 / 0) not expected (window: 1 - 64). Dropping!
Jul 07 20:46:10-197585 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:46:10-197768 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:46:10-198016 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:10-198231 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:10-198431 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:10-198612 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:10-198797 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:10-198977 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:10-199156 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:10-199324 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:10-199541 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:10-199716 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:10-199951 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:10-200137 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:10-200430 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:10-200601 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:10-200785 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:10-203905 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:10-204618 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:10-204880 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:10-205070 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:10-208275 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:10-208515 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:10-208698 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:10-208920 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:10-209113 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:10-209414 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:10-209614 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:10-209792 cadet-con-8620 DEBUG last pid sent 5
Jul 07 20:46:10-209965 cadet-con-8620 DEBUG      ack recv 67
Jul 07 20:46:10-210136 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:10-210312 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:10-210547 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:10-210754 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:10-211065 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:10-211266 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:10-211490 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:10-211673 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 5
Jul 07 20:46:10-211847 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:10-212052 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:46:10-212267 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:10-212493 util-scheduler-8620 DEBUG Adding task: 1854 / 0x4d6ff98
Jul 07 20:46:10-212672 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:10-212875 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:10-213052 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:10-213249 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:10-213488 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:10-213683 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:10-213864 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:10-214063 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:10-214238 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:10-214469 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:10-214643 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:10-214816 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:10-214987 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:10-215207 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:10-215384 cadet-con-8620 DEBUG  ACK 69
Jul 07 20:46:10-215562 cadet-con-8620 DEBUG  last pid 5, last ack 68, qmax 11, q 0
Jul 07 20:46:10-215826 cadet-con-8620 INFO --> {               ACK} ( 69) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:10-216016 cadet-con-8620 DEBUG  ack 69
Jul 07 20:46:10-216191 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:10-216422 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:10-216628 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:10-216917 cadet-p2p-8620 INFO que {               ACK} ( 69) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:10-217114 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:10-217359 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:10-217540 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 5
Jul 07 20:46:10-217713 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:10-217913 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:10-218115 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:10-218303 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:10-218494 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:10-218730 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:10-218913 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:46:10-219087 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:10-219320 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:10-219512 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:10-219689 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:10-219884 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:10-220067 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:10-220276 util-scheduler-8620 DEBUG Adding task: 1855 / 0x46620a0
Jul 07 20:46:10-220556 util-scheduler-8620 DEBUG Checking readiness of task: 1855 / 0x46620a0
Jul 07 20:46:10-220753 util-scheduler-8620 DEBUG Checking readiness of task: 1853 / 0x4d5e5d8
Jul 07 20:46:10-220946 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-221135 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-221350 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-221540 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-221730 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-221918 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-222107 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-222300 util-scheduler-8620 DEBUG Running task: 1853 / 0x4d5e5d8
Jul 07 20:46:10-222487 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:10-222665 util-8620 DEBUG process_notify is running
Jul 07 20:46:10-222838 util-8620 DEBUG client_notify is running
Jul 07 20:46:10-223088 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:10-223297 util-scheduler-8620 DEBUG Adding task: 1856 / 0x4d5e5d8
Jul 07 20:46:10-223501 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:10-223764 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:10-223962 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:10-224159 util-scheduler-8620 DEBUG Running task: 1854 / 0x4d6ff98
Jul 07 20:46:10-224372 util-scheduler-8620 DEBUG Adding task: 1857 / 0x4d6ff98
Jul 07 20:46:10-224597 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:10-224795 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:10-224993 util-scheduler-8620 DEBUG Adding task: 1858 / 0x46620a0
Jul 07 20:46:10-225261 util-scheduler-8620 DEBUG Checking readiness of task: 1858 / 0x46620a0
Jul 07 20:46:10-225457 util-scheduler-8620 DEBUG Checking readiness of task: 1856 / 0x4d5e5d8
Jul 07 20:46:10-225648 util-scheduler-8620 DEBUG Checking readiness of task: 1855 / 0x46620a0
Jul 07 20:46:10-225838 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:10-226031 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:10-226220 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:10-226411 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:10-226599 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:10-226788 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:10-226977 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:10-227168 util-scheduler-8620 DEBUG Running task: 1856 / 0x4d5e5d8
Jul 07 20:46:10-227350 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:10-227526 util-8620 DEBUG process_notify is running
Jul 07 20:46:10-227694 util-8620 DEBUG client_notify is running
Jul 07 20:46:10-227905 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:10-228167 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:10-228376 util-scheduler-8620 DEBUG Running task: 1858 / 0x46620a0
Jul 07 20:46:10-228560 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:10-228734 util-8620 DEBUG process_notify is running
Jul 07 20:46:10-228902 util-8620 DEBUG client_notify is running
Jul 07 20:46:10-229080 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:10-229297 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:10-229485 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:10-229725 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-008192 util-scheduler-8620 DEBUG Checking readiness of task: 1855 / 0x46620a0
Jul 07 20:46:11-008563 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-008762 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-008955 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-009150 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-009369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-009562 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-009754 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-009951 util-scheduler-8620 DEBUG Running task: 1855 / 0x46620a0
Jul 07 20:46:11-010373 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:11-010631 util-scheduler-8620 DEBUG Adding task: 1859 / 0x4662248
Jul 07 20:46:11-010910 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-011105 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-011298 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-011490 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-011682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-011872 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-012064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-012255 util-scheduler-8620 DEBUG Running task: 1859 / 0x4662248
Jul 07 20:46:11-012448 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:11-012649 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:11-012881 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:11-013091 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-013323 util-scheduler-8620 DEBUG Adding task: 1860 / 0x46620a0
Jul 07 20:46:11-013511 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:11-013717 util-scheduler-8620 DEBUG Adding task: 1861 / 0x46620a0
Jul 07 20:46:11-013965 util-scheduler-8620 DEBUG Checking readiness of task: 1861 / 0x46620a0
Jul 07 20:46:11-014159 util-scheduler-8620 DEBUG Checking readiness of task: 1860 / 0x46620a0
Jul 07 20:46:11-014354 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-014545 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-014736 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-014928 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-015120 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-015310 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-015501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-015725 util-scheduler-8620 DEBUG Running task: 1860 / 0x46620a0
Jul 07 20:46:11-015913 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-016093 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-016267 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-016462 util-scheduler-8620 DEBUG Canceling task: 1829 / 0x5e2b838
Jul 07 20:46:11-016688 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:11-016911 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:11-017151 cadet-p2p-8620 DEBUG Checking 0x5330038 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-017411 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:11-017591 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:11-017784 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:11-018056 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:11-018267 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:11-018450 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:11-018639 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:11-018814 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:11-019450 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:11-019644 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:11-019934 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-020181 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-020368 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:11-020547 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-020785 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-021018 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-021247 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:11-021428 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-021600 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:11-021811 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:11-022048 util-scheduler-8620 DEBUG Adding task: 1862 / 0x5e2b838
Jul 07 20:46:11-022231 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:11-022410 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:11-022614 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:11-022791 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:11-022968 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:11-023213 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-023410 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-023590 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-023826 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-024049 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:11-024229 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:11-024431 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:11-024641 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:11-024828 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:11-025040 util-scheduler-8620 DEBUG Adding task: 1863 / 0x5e2b838
Jul 07 20:46:11-025288 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:11-025495 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-025706 util-scheduler-8620 DEBUG Adding task: 1864 / 0x46620a0
Jul 07 20:46:11-025913 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:11-026186 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-026385 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:11-027410 util-scheduler-8620 DEBUG Checking readiness of task: 1864 / 0x46620a0
Jul 07 20:46:11-028879 util-scheduler-8620 DEBUG Checking readiness of task: 1861 / 0x46620a0
Jul 07 20:46:11-029109 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-029334 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-029530 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-029723 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-029916 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-030107 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-030299 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-030498 util-scheduler-8620 DEBUG Running task: 1864 / 0x46620a0
Jul 07 20:46:11-030688 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-030871 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-031046 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-031230 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-031434 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-031630 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-031881 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-032090 util-scheduler-8620 DEBUG Running task: 1862 / 0x5e2b838
Jul 07 20:46:11-032290 util-scheduler-8620 DEBUG Canceling task: 1863 / 0x5e2b838
Jul 07 20:46:11-032514 util-scheduler-8620 DEBUG Adding task: 1865 / 0x5e2b838
Jul 07 20:46:11-032738 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:11-032936 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-033138 util-scheduler-8620 DEBUG Adding task: 1866 / 0x46620a0
Jul 07 20:46:11-033414 util-scheduler-8620 DEBUG Checking readiness of task: 1866 / 0x46620a0
Jul 07 20:46:11-033611 util-scheduler-8620 DEBUG Checking readiness of task: 1861 / 0x46620a0
Jul 07 20:46:11-033804 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-033995 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-034187 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-034378 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-034568 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-034759 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-034949 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-035141 util-scheduler-8620 DEBUG Running task: 1866 / 0x46620a0
Jul 07 20:46:11-035325 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-035503 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-035674 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-035851 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-036042 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-036231 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-036475 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-490461 util-scheduler-8620 DEBUG Checking readiness of task: 1861 / 0x46620a0
Jul 07 20:46:11-490855 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-491154 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-491452 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-491746 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-492039 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-492357 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-492646 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-492848 util-scheduler-8620 DEBUG Running task: 1861 / 0x46620a0
Jul 07 20:46:11-493483 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:11-493941 util-scheduler-8620 DEBUG Adding task: 1867 / 0x4662248
Jul 07 20:46:11-494215 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-494409 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-494602 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-494852 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-495045 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-495236 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-495427 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-495618 util-scheduler-8620 DEBUG Running task: 1867 / 0x4662248
Jul 07 20:46:11-495810 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:11-496009 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:11-496237 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:11-496497 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:11-496741 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-496970 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:11-497179 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:11-497465 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:11-497675 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:11-497866 cadet-con-8620 DEBUG  PID 1 (expected 1+)
Jul 07 20:46:11-498048 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:11-498238 util-scheduler-8620 DEBUG Canceling task: 1797 / 0x5e31aa0
Jul 07 20:46:11-498463 util-scheduler-8620 DEBUG Adding task: 1868 / 0x5e31aa0
Jul 07 20:46:11-498643 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:11-498901 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:11-499115 util-scheduler-8620 DEBUG Adding task: 1869 / 0x4d5e5d8
Jul 07 20:46:11-499299 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:11-499467 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:11-503070 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:11-504445 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:11-504665 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:11-507361 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on D3TJ
Jul 07 20:46:11-507610 cadet-chn-8620 DEBUG   channel confirm FWD D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:11-507845 cadet-chn-8620 DEBUG   sending channel BCK ack for channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:11-508095 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:11-508305 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:11-508503 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:11-508682 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:11-508865 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:11-509046 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:11-509249 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:11-509420 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:11-509634 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:11-509804 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:11-510039 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:11-510284 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:11-510467 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:11-510782 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:11-510954 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:11-511138 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:11-514665 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:11-515259 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:11-515443 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:11-515629 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:11-518727 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:11-518963 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:11-519145 cadet-tun-8620 DEBUG     q_n 1, 
Jul 07 20:46:11-519367 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:11-519543 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:11-519762 cadet-tun-8620 DEBUG  selected: connection BFARXZN9 (->D3TJ)
Jul 07 20:46:11-519956 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:46:11-520226 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (88 bytes)
Jul 07 20:46:11-520423 cadet-con-8620 DEBUG   Q_N+ 0x5e2cf70 0
Jul 07 20:46:11-520601 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:46:11-520775 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:46:11-520946 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:11-521124 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 0
Jul 07 20:46:11-521381 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:11-521588 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:11-521897 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 88)
Jul 07 20:46:11-522095 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:11-522319 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:11-522503 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:11-522679 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-522880 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:11-523083 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:11-523258 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:11-523432 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:11-523672 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-523866 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-524043 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-524277 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-524470 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:11-524650 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:11-524884 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:11-525077 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-525274 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-525471 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:11-525702 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-525877 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:11-526051 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:11-526222 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:11-526442 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-526619 cadet-con-8620 DEBUG  ACK 65
Jul 07 20:46:11-526809 cadet-con-8620 DEBUG  last pid 1, last ack 64, qmax 11, q 0
Jul 07 20:46:11-527072 cadet-con-8620 INFO --> {               ACK} ( 65) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:11-527261 cadet-con-8620 DEBUG  ack 65
Jul 07 20:46:11-527437 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:11-527670 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:11-527875 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:11-528162 cadet-p2p-8620 INFO que {               ACK} ( 65) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:11-528378 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:11-528600 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-528781 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:11-528954 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-529154 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:11-529374 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:11-529549 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:11-529723 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:11-529957 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-530138 cadet-p2p-8620 DEBUG QQQ    payload , 65
Jul 07 20:46:11-530313 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:11-530546 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-530738 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-530914 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-531146 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-531338 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:11-531514 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:11-531746 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:11-531938 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-532114 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-532310 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:11-532493 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:11-532707 util-scheduler-8620 DEBUG Adding task: 1870 / 0x46620a0
Jul 07 20:46:11-532979 util-scheduler-8620 DEBUG Checking readiness of task: 1870 / 0x46620a0
Jul 07 20:46:11-533174 util-scheduler-8620 DEBUG Checking readiness of task: 1869 / 0x4d5e5d8
Jul 07 20:46:11-533388 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-533578 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-533768 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-533958 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-534147 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-534336 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-534524 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-534719 util-scheduler-8620 DEBUG Running task: 1869 / 0x4d5e5d8
Jul 07 20:46:11-534905 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:11-535083 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-535253 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-535479 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:11-535740 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:11-692946 util-scheduler-8620 DEBUG Checking readiness of task: 1870 / 0x46620a0
Jul 07 20:46:11-693284 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-693488 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-693685 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-693883 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-694092 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-694295 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-694485 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-694684 util-scheduler-8620 DEBUG Running task: 1870 / 0x46620a0
Jul 07 20:46:11-695132 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:11-695380 util-scheduler-8620 DEBUG Adding task: 1871 / 0x4662248
Jul 07 20:46:11-695643 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-695836 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-696091 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-696284 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-696474 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-696664 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-696854 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-697043 util-scheduler-8620 DEBUG Running task: 1871 / 0x4662248
Jul 07 20:46:11-697261 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:11-697462 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:11-698566 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:11-698809 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-699026 util-scheduler-8620 DEBUG Adding task: 1872 / 0x46620a0
Jul 07 20:46:11-699218 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:11-699426 util-scheduler-8620 DEBUG Adding task: 1873 / 0x46620a0
Jul 07 20:46:11-699701 util-scheduler-8620 DEBUG Checking readiness of task: 1873 / 0x46620a0
Jul 07 20:46:11-699901 util-scheduler-8620 DEBUG Checking readiness of task: 1872 / 0x46620a0
Jul 07 20:46:11-700094 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-700286 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-700478 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-700669 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-700860 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-701050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-701527 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-701733 util-scheduler-8620 DEBUG Running task: 1872 / 0x46620a0
Jul 07 20:46:11-701921 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-702101 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-702274 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-702465 util-scheduler-8620 DEBUG Canceling task: 1865 / 0x5e2b838
Jul 07 20:46:11-702779 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:11-703002 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:11-703242 cadet-p2p-8620 DEBUG Checking 0x5361008 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-703478 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:11-703656 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:11-703849 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:11-704127 cadet-p2p-8620 INFO snd {               ACK} ( 65) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:11-704323 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:11-704504 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:11-704693 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:11-704868 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:11-705053 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:11-705253 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:11-705477 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-705707 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-705891 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:11-706066 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-706322 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-706567 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-706749 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:11-706923 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-707091 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:11-707298 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:11-707520 util-scheduler-8620 DEBUG Adding task: 1874 / 0x5e2b838
Jul 07 20:46:11-707701 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:11-707879 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:11-708078 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:11-708254 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:11-708430 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:11-708670 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-708865 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-709044 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-709300 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:11-709495 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:11-709673 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:11-709908 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:11-710102 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:11-710279 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:11-710477 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:11-710682 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:11-710866 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:11-711071 util-scheduler-8620 DEBUG Adding task: 1875 / 0x5e2b838
Jul 07 20:46:11-711292 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:11-711487 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-711690 util-scheduler-8620 DEBUG Adding task: 1876 / 0x46620a0
Jul 07 20:46:11-711895 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:11-712141 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-712337 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:11-712538 util-scheduler-8620 DEBUG Running task: 1873 / 0x46620a0
Jul 07 20:46:11-712951 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:11-713182 util-scheduler-8620 DEBUG Adding task: 1877 / 0x4662248
Jul 07 20:46:11-713466 util-scheduler-8620 DEBUG Checking readiness of task: 1876 / 0x46620a0
Jul 07 20:46:11-713661 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-713853 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-714045 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-714237 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-714428 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-714617 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-714806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-714998 util-scheduler-8620 DEBUG Running task: 1876 / 0x46620a0
Jul 07 20:46:11-715185 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-715362 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-715533 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-715711 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-715907 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-716113 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-716346 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-716553 util-scheduler-8620 DEBUG Running task: 1877 / 0x4662248
Jul 07 20:46:11-716744 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:11-716942 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:11-717154 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:11-717376 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-717574 util-scheduler-8620 DEBUG Adding task: 1878 / 0x46620a0
Jul 07 20:46:11-717758 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:11-717957 util-scheduler-8620 DEBUG Adding task: 1879 / 0x46620a0
Jul 07 20:46:11-718156 util-scheduler-8620 DEBUG Running task: 1874 / 0x5e2b838
Jul 07 20:46:11-718349 util-scheduler-8620 DEBUG Canceling task: 1875 / 0x5e2b838
Jul 07 20:46:11-718562 util-scheduler-8620 DEBUG Adding task: 1880 / 0x5e2b838
Jul 07 20:46:11-718778 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:11-718956 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:11-719189 util-scheduler-8620 DEBUG Checking readiness of task: 1879 / 0x46620a0
Jul 07 20:46:11-719383 util-scheduler-8620 DEBUG Checking readiness of task: 1878 / 0x46620a0
Jul 07 20:46:11-719575 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-719765 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-719956 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-720147 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-720337 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-720525 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-720714 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-720904 util-scheduler-8620 DEBUG Running task: 1878 / 0x46620a0
Jul 07 20:46:11-721089 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-721289 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-721460 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-721636 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-721846 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-722043 util-scheduler-8620 DEBUG Adding task: 1881 / 0x46620a0
Jul 07 20:46:11-722240 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-722473 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-722666 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:11-722905 util-scheduler-8620 DEBUG Checking readiness of task: 1881 / 0x46620a0
Jul 07 20:46:11-723099 util-scheduler-8620 DEBUG Checking readiness of task: 1879 / 0x46620a0
Jul 07 20:46:11-723291 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-723481 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-723671 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-723862 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-724052 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-724241 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-724430 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-724621 util-scheduler-8620 DEBUG Running task: 1881 / 0x46620a0
Jul 07 20:46:11-724805 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-724980 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-725170 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-725376 util-scheduler-8620 DEBUG Canceling task: 1857 / 0x4d6ff98
Jul 07 20:46:11-725597 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:11-725813 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:11-726043 cadet-p2p-8620 DEBUG Checking 0x5359108 towards CMHCKRVP (->V8XX)
Jul 07 20:46:11-726274 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:11-726451 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:11-726637 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:11-726897 cadet-p2p-8620 INFO snd {               ACK} ( 69) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:11-727090 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:11-727267 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:11-727452 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:11-727637 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:11-727818 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:11-727992 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:11-728215 cadet-p2p-8620 DEBUG Checking 0x5358640 towards CMHCKRVP (->V8XX)
Jul 07 20:46:11-728444 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:11-728626 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 5
Jul 07 20:46:11-728800 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-729025 cadet-p2p-8620 DEBUG Checking 0x5358640 towards CMHCKRVP (->V8XX)
Jul 07 20:46:11-729279 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:11-729463 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 5
Jul 07 20:46:11-729637 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-729803 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:11-730005 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:11-730215 util-scheduler-8620 DEBUG Adding task: 1882 / 0x4d6ff98
Jul 07 20:46:11-730395 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:11-730571 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:11-730768 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:11-730943 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:11-731117 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:11-731352 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:11-731546 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:11-731724 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:11-731924 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:11-732127 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:11-732310 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:11-732508 util-scheduler-8620 DEBUG Adding task: 1883 / 0x4d6ff98
Jul 07 20:46:11-732721 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:11-732915 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-733113 util-scheduler-8620 DEBUG Adding task: 1884 / 0x46620a0
Jul 07 20:46:11-733334 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:11-734222 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-734424 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:11-734668 util-scheduler-8620 DEBUG Checking readiness of task: 1884 / 0x46620a0
Jul 07 20:46:11-734863 util-scheduler-8620 DEBUG Checking readiness of task: 1879 / 0x46620a0
Jul 07 20:46:11-735055 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-735246 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-735436 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-735626 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-735834 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-736025 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-736215 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-736406 util-scheduler-8620 DEBUG Running task: 1884 / 0x46620a0
Jul 07 20:46:11-736591 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-736767 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-736938 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-737115 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-737331 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-737521 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-737864 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-738074 util-scheduler-8620 DEBUG Running task: 1882 / 0x4d6ff98
Jul 07 20:46:11-738268 util-scheduler-8620 DEBUG Canceling task: 1883 / 0x4d6ff98
Jul 07 20:46:11-738482 util-scheduler-8620 DEBUG Adding task: 1885 / 0x4d6ff98
Jul 07 20:46:11-738697 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:11-738893 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-739622 util-scheduler-8620 DEBUG Adding task: 1886 / 0x46620a0
Jul 07 20:46:11-739876 util-scheduler-8620 DEBUG Checking readiness of task: 1886 / 0x46620a0
Jul 07 20:46:11-740232 util-scheduler-8620 DEBUG Checking readiness of task: 1879 / 0x46620a0
Jul 07 20:46:11-740430 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-740622 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-740813 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-741004 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-741220 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-741411 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-741600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-741796 util-scheduler-8620 DEBUG Running task: 1886 / 0x46620a0
Jul 07 20:46:11-741981 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-742157 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-742327 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-742505 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:11-742695 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-742884 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:11-743118 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:11-831216 util-scheduler-8620 DEBUG Checking readiness of task: 1879 / 0x46620a0
Jul 07 20:46:11-831497 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-831693 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-831889 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-832091 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-832282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-832475 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-832665 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-832857 util-scheduler-8620 DEBUG Running task: 1879 / 0x46620a0
Jul 07 20:46:11-833293 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:11-833538 util-scheduler-8620 DEBUG Adding task: 1887 / 0x4662248
Jul 07 20:46:11-833822 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-834015 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-834206 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-834395 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-834584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-834773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-834963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-835152 util-scheduler-8620 DEBUG Running task: 1887 / 0x4662248
Jul 07 20:46:11-835341 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:11-835538 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:11-835760 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:11-835962 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:11-836165 util-scheduler-8620 DEBUG Adding task: 1888 / 0x46620a0
Jul 07 20:46:11-836352 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:11-836556 util-scheduler-8620 DEBUG Adding task: 1889 / 0x46620a0
Jul 07 20:46:11-836797 util-scheduler-8620 DEBUG Checking readiness of task: 1889 / 0x46620a0
Jul 07 20:46:11-836992 util-scheduler-8620 DEBUG Checking readiness of task: 1888 / 0x46620a0
Jul 07 20:46:11-837186 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:11-837765 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:11-837959 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:11-838151 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:11-838342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:11-838543 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:11-838733 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:11-838923 util-scheduler-8620 DEBUG Running task: 1888 / 0x46620a0
Jul 07 20:46:11-839108 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:11-839286 util-8620 DEBUG process_notify is running
Jul 07 20:46:11-839456 util-8620 DEBUG client_notify is running
Jul 07 20:46:11-839642 util-scheduler-8620 DEBUG Canceling task: 1885 / 0x4d6ff98
Jul 07 20:46:11-839864 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:11-840082 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:11-840317 cadet-p2p-8620 DEBUG Checking 0x5358640 towards CMHCKRVP (->V8XX)
Jul 07 20:46:11-840549 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:11-840732 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 5
Jul 07 20:46:11-840906 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:11-841128 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:11-841334 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:11-841510 cadet-p2p-8620 DEBUG   payload ID 6
Jul 07 20:46:11-841798 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:46:11-841994 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:11-842173 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:11-842360 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:11-842534 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:11-842703 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:11-842891 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:11-843080 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:11-843274 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:11-843502 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:11-843695 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:11-843867 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:11-844039 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:11-844236 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:11-844411 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:11-844585 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:11-844787 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:11-844967 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:11-845149 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:11-845355 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:11-845533 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:11-845703 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:11-845920 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:11-846094 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:11-846327 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:11-846512 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:11-846694 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:11-846880 util-scheduler-8620 DEBUG Canceling task: 1846 / 0x4d707d0
Jul 07 20:46:11-847095 util-scheduler-8620 DEBUG Adding task: 1890 / 0x4d707d0
Jul 07 20:46:11-847347 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:11-847525 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:11-847704 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 6
Jul 07 20:46:11-847878 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:11-848059 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:11-848258 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:11-848433 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:11-848605 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:11-848804 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:11-849008 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:46:11-849214 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:11-849396 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:11-849587 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:11-849828 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:12-753639 util-scheduler-8620 DEBUG Checking readiness of task: 1889 / 0x46620a0
Jul 07 20:46:12-754022 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-754219 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-754412 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-754605 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-754812 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-755004 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-755194 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-755388 util-scheduler-8620 DEBUG Running task: 1834 / 0x4d65218
Jul 07 20:46:12-755575 cadet-chn-8620 DEBUG !!! RETRANSMIT 1
Jul 07 20:46:12-755865 cadet-chn-8620 INFO ===> {              DATA} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:12-756066 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:46:12-756267 cadet-chn-8620 DEBUG   using existing copy: 0x5266ee0 {r:0x4d65218 q:(nil) t:260}
Jul 07 20:46:12-756456 cadet-chn-8620 DEBUG   new chq: 0x537d678
Jul 07 20:46:12-756660 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:12-756861 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:12-757042 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:12-757249 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:12-757460 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:12-757638 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:12-757806 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:12-758021 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:12-758196 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:12-758433 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:12-758618 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:12-758929 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:12-759100 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:12-759285 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:12-763416 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:12-764232 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:12-764415 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:12-764605 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:12-768240 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:12-768492 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:12-768674 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:12-768909 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:12-769104 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:12-769411 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (156 bytes)
Jul 07 20:46:12-769612 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:12-769789 cadet-con-8620 DEBUG last pid sent 6
Jul 07 20:46:12-769962 cadet-con-8620 DEBUG      ack recv 67
Jul 07 20:46:12-770134 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:12-770311 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:12-770545 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:12-770753 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:12-771068 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 156)
Jul 07 20:46:12-771268 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:12-771493 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:12-771674 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 6
Jul 07 20:46:12-771848 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:12-772054 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 156 bytes
Jul 07 20:46:12-772268 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `V8XX'
Jul 07 20:46:12-772499 util-scheduler-8620 DEBUG Adding task: 1891 / 0x4d6ff98
Jul 07 20:46:12-772680 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:12-772885 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:12-773060 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:12-773262 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:12-773502 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:12-773697 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:12-773874 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:12-774072 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:12-774345 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:12-774562 util-scheduler-8620 DEBUG Adding task: 1892 / 0x4d5e5d8
Jul 07 20:46:12-774837 util-scheduler-8620 DEBUG Checking readiness of task: 1892 / 0x4d5e5d8
Jul 07 20:46:12-775037 util-scheduler-8620 DEBUG Checking readiness of task: 1889 / 0x46620a0
Jul 07 20:46:12-775228 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-775418 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-775608 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-775797 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-775987 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-776198 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-776388 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-776581 util-scheduler-8620 DEBUG Running task: 1892 / 0x4d5e5d8
Jul 07 20:46:12-776766 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:12-776945 util-8620 DEBUG process_notify is running
Jul 07 20:46:12-777294 util-8620 DEBUG client_notify is running
Jul 07 20:46:12-777526 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:46:12-777854 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:12-778066 util-scheduler-8620 DEBUG Running task: 1891 / 0x4d6ff98
Jul 07 20:46:12-778280 util-scheduler-8620 DEBUG Adding task: 1893 / 0x4d6ff98
Jul 07 20:46:12-778502 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:12-778699 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:12-778899 util-scheduler-8620 DEBUG Adding task: 1894 / 0x46620a0
Jul 07 20:46:12-779141 util-scheduler-8620 DEBUG Checking readiness of task: 1894 / 0x46620a0
Jul 07 20:46:12-779335 util-scheduler-8620 DEBUG Checking readiness of task: 1889 / 0x46620a0
Jul 07 20:46:12-779525 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-779714 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-779904 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-780093 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-780282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-780556 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-780748 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-780939 util-scheduler-8620 DEBUG Running task: 1894 / 0x46620a0
Jul 07 20:46:12-781123 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:12-781325 util-8620 DEBUG process_notify is running
Jul 07 20:46:12-781495 util-8620 DEBUG client_notify is running
Jul 07 20:46:12-781673 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:12-781869 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:12-782057 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:12-782360 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:12-815900 util-scheduler-8620 DEBUG Checking readiness of task: 1889 / 0x46620a0
Jul 07 20:46:12-816177 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-816373 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-816565 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-816757 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-816947 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-817137 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-817356 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-817550 util-scheduler-8620 DEBUG Running task: 1889 / 0x46620a0
Jul 07 20:46:12-817967 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:12-818213 util-scheduler-8620 DEBUG Adding task: 1895 / 0x4662248
Jul 07 20:46:12-818476 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-818669 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-818861 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-819052 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-819265 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-819455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-819644 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-819833 util-scheduler-8620 DEBUG Running task: 1895 / 0x4662248
Jul 07 20:46:12-820024 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:12-820222 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:12-820447 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:12-820707 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:12-820959 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:12-821167 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:12-821375 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:12-821548 cadet-con-8620 DEBUG   ACK 68 (was 67)
Jul 07 20:46:12-821777 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:12-822008 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:12-822212 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:12-822393 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:12-822569 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:12-822780 util-scheduler-8620 DEBUG Adding task: 1896 / 0x46620a0
Jul 07 20:46:12-872974 util-scheduler-8620 DEBUG Checking readiness of task: 1896 / 0x46620a0
Jul 07 20:46:12-873380 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-873578 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-873771 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-873964 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-874169 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-874360 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-874550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-874745 util-scheduler-8620 DEBUG Running task: 1896 / 0x46620a0
Jul 07 20:46:12-875169 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:12-875427 util-scheduler-8620 DEBUG Adding task: 1897 / 0x4662248
Jul 07 20:46:12-875706 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-875902 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-876095 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-876287 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-876478 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-876669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-876860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-877051 util-scheduler-8620 DEBUG Running task: 1897 / 0x4662248
Jul 07 20:46:12-878366 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:12-878575 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:12-878811 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:12-879076 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:12-879321 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-879553 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:12-879762 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:12-880008 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:12-880216 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:12-880405 cadet-con-8620 DEBUG  PID 2 (expected 2+)
Jul 07 20:46:12-880622 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:12-880817 util-scheduler-8620 DEBUG Canceling task: 1868 / 0x5e31aa0
Jul 07 20:46:12-881043 util-scheduler-8620 DEBUG Adding task: 1898 / 0x5e31aa0
Jul 07 20:46:12-881247 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:12-881506 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:12-881725 util-scheduler-8620 DEBUG Adding task: 1899 / 0x4d5e5d8
Jul 07 20:46:12-881911 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:12-882083 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:12-885638 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:12-886903 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:12-887099 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:12-889830 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on D3TJ
Jul 07 20:46:12-890084 cadet-chn-8620 DEBUG   channel confirm FWD D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:12-890321 cadet-chn-8620 DEBUG   sending channel BCK ack for channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:12-890571 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:12-890783 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:12-890982 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:12-891162 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:12-891346 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:12-891528 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:12-891703 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:12-891873 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:12-892091 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:12-892262 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:12-892495 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:12-892740 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:12-892927 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:12-893244 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:12-893418 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:12-893601 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:12-897154 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:12-897836 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:12-898120 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:12-898307 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:12-901541 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:12-901782 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:12-901968 cadet-tun-8620 DEBUG     q_n 1, 
Jul 07 20:46:12-902194 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:12-902373 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:12-902592 cadet-tun-8620 DEBUG  selected: connection BFARXZN9 (->D3TJ)
Jul 07 20:46:12-902786 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:46:12-903059 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (88 bytes)
Jul 07 20:46:12-903257 cadet-con-8620 DEBUG   Q_N+ 0x5e2cf70 0
Jul 07 20:46:12-903436 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:46:12-903611 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:46:12-903782 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:12-903959 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 1
Jul 07 20:46:12-904196 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:12-904403 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:12-904716 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 88)
Jul 07 20:46:12-904916 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:12-905139 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:12-905363 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:12-905539 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:12-905768 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:12-905974 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:12-906150 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:46:12-906326 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:12-906566 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-906765 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-906942 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-907175 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-907371 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:12-907548 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:12-907783 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:12-907977 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-908154 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-908389 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:12-908583 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-908758 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-908957 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:12-909210 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-909390 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:12-909565 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:12-909737 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:12-909956 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-910136 cadet-con-8620 DEBUG  ACK 66
Jul 07 20:46:12-910314 cadet-con-8620 DEBUG  last pid 2, last ack 65, qmax 11, q 0
Jul 07 20:46:12-910578 cadet-con-8620 INFO --> {               ACK} ( 66) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:12-910770 cadet-con-8620 DEBUG  ack 66
Jul 07 20:46:12-910947 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:12-911182 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:12-911389 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:12-911678 cadet-p2p-8620 INFO que {               ACK} ( 66) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:12-911876 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:12-912101 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-912283 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:12-912458 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:12-912656 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:12-912856 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:12-913032 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:46:12-913706 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:12-913952 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-914138 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:46:12-914313 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:12-914547 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-914742 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-914920 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-915153 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:12-915348 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:12-915525 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:12-915758 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:12-915952 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-916129 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-916364 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:12-916558 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:12-916753 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:12-916951 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:12-917137 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:12-917379 util-scheduler-8620 DEBUG Adding task: 1900 / 0x46620a0
Jul 07 20:46:12-917656 util-scheduler-8620 DEBUG Checking readiness of task: 1900 / 0x46620a0
Jul 07 20:46:12-917853 util-scheduler-8620 DEBUG Checking readiness of task: 1899 / 0x4d5e5d8
Jul 07 20:46:12-918046 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:12-918237 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:12-918427 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:12-918617 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:12-918807 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:12-918996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:12-919185 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:12-919378 util-scheduler-8620 DEBUG Running task: 1899 / 0x4d5e5d8
Jul 07 20:46:12-919563 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:12-919741 util-8620 DEBUG process_notify is running
Jul 07 20:46:12-919914 util-8620 DEBUG client_notify is running
Jul 07 20:46:12-920144 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:12-920475 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:13-018248 util-scheduler-8620 DEBUG Checking readiness of task: 1900 / 0x46620a0
Jul 07 20:46:13-018584 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-018783 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-018978 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-019172 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-019364 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-019557 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-019749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-019945 util-scheduler-8620 DEBUG Running task: 1900 / 0x46620a0
Jul 07 20:46:13-020366 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:13-020620 util-scheduler-8620 DEBUG Adding task: 1901 / 0x4662248
Jul 07 20:46:13-020893 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-021100 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-021324 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-021519 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-021711 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-021904 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-022106 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-022302 util-scheduler-8620 DEBUG Running task: 1901 / 0x4662248
Jul 07 20:46:13-022496 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:13-022700 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:13-022933 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:13-023144 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-023352 util-scheduler-8620 DEBUG Adding task: 1902 / 0x46620a0
Jul 07 20:46:13-023541 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:13-023746 util-scheduler-8620 DEBUG Adding task: 1903 / 0x46620a0
Jul 07 20:46:13-024022 util-scheduler-8620 DEBUG Checking readiness of task: 1903 / 0x46620a0
Jul 07 20:46:13-024220 util-scheduler-8620 DEBUG Checking readiness of task: 1902 / 0x46620a0
Jul 07 20:46:13-024414 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-024606 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-024811 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-025003 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-025222 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-025414 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-025605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-025798 util-scheduler-8620 DEBUG Running task: 1902 / 0x46620a0
Jul 07 20:46:13-025984 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-026164 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-026337 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-026530 util-scheduler-8620 DEBUG Canceling task: 1880 / 0x5e2b838
Jul 07 20:46:13-026757 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:13-026979 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:13-027220 cadet-p2p-8620 DEBUG Checking 0x53971e0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-027457 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:13-027637 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:13-027829 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:13-028101 cadet-p2p-8620 INFO snd {               ACK} ( 66) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:13-028298 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:13-028481 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:13-028670 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:13-028846 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:13-029030 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:13-029230 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:13-029459 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-029695 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-029879 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:13-030056 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-030287 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-030520 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-030703 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:13-030878 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-031047 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:13-031255 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:13-031474 util-scheduler-8620 DEBUG Adding task: 1904 / 0x5e2b838
Jul 07 20:46:13-031657 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:13-031835 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:13-032039 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:13-032217 cadet-p2p-8620 DEBUG QQQ  queue length: 4
Jul 07 20:46:13-032394 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:13-032633 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-032831 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-033010 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-033269 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-033467 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:13-033645 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:13-033882 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-034078 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-034274 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-034511 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-034707 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-034887 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-035088 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:13-035295 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:13-035482 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:13-035688 util-scheduler-8620 DEBUG Adding task: 1905 / 0x5e2b838
Jul 07 20:46:13-035911 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-036109 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-036313 util-scheduler-8620 DEBUG Adding task: 1906 / 0x46620a0
Jul 07 20:46:13-036517 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:13-038101 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-038315 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:13-038570 util-scheduler-8620 DEBUG Checking readiness of task: 1906 / 0x46620a0
Jul 07 20:46:13-038768 util-scheduler-8620 DEBUG Checking readiness of task: 1903 / 0x46620a0
Jul 07 20:46:13-038961 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-039155 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-039347 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-039540 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-039733 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-039924 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-040115 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-040308 util-scheduler-8620 DEBUG Running task: 1906 / 0x46620a0
Jul 07 20:46:13-040495 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-040673 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-040846 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-041026 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-041251 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-041445 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-041745 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-041956 util-scheduler-8620 DEBUG Running task: 1904 / 0x5e2b838
Jul 07 20:46:13-042157 util-scheduler-8620 DEBUG Canceling task: 1905 / 0x5e2b838
Jul 07 20:46:13-042379 util-scheduler-8620 DEBUG Adding task: 1907 / 0x5e2b838
Jul 07 20:46:13-042601 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-042798 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-042999 util-scheduler-8620 DEBUG Adding task: 1908 / 0x46620a0
Jul 07 20:46:13-043241 util-scheduler-8620 DEBUG Checking readiness of task: 1908 / 0x46620a0
Jul 07 20:46:13-043438 util-scheduler-8620 DEBUG Checking readiness of task: 1903 / 0x46620a0
Jul 07 20:46:13-043632 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-043825 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-044018 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-044211 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-044403 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-044594 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-044786 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-044998 util-scheduler-8620 DEBUG Running task: 1903 / 0x46620a0
Jul 07 20:46:13-045424 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:13-045655 util-scheduler-8620 DEBUG Adding task: 1909 / 0x4662248
Jul 07 20:46:13-045868 util-scheduler-8620 DEBUG Running task: 1908 / 0x46620a0
Jul 07 20:46:13-046055 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-046232 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-046404 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-046582 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-046775 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-046966 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-047267 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-047534 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-047730 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-047923 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-048115 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-048307 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-048499 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-048690 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-048881 util-scheduler-8620 DEBUG Running task: 1909 / 0x4662248
Jul 07 20:46:13-049071 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:13-049289 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:13-049507 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:13-049691 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:13-049895 util-scheduler-8620 DEBUG Adding task: 1910 / 0x46620a0
Jul 07 20:46:13-050137 util-scheduler-8620 DEBUG Checking readiness of task: 1910 / 0x46620a0
Jul 07 20:46:13-050332 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-050524 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-050715 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-050907 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-051097 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-051288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-051479 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-051670 util-scheduler-8620 DEBUG Running task: 1910 / 0x46620a0
Jul 07 20:46:13-052072 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:13-052296 util-scheduler-8620 DEBUG Adding task: 1911 / 0x4662248
Jul 07 20:46:13-052543 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-052736 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-052929 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-053122 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-053337 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-053529 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-053719 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-053910 util-scheduler-8620 DEBUG Running task: 1911 / 0x4662248
Jul 07 20:46:13-054098 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:13-054307 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:13-054520 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:13-054717 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-054915 util-scheduler-8620 DEBUG Adding task: 1912 / 0x46620a0
Jul 07 20:46:13-055100 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:13-055298 util-scheduler-8620 DEBUG Adding task: 1913 / 0x46620a0
Jul 07 20:46:13-055539 util-scheduler-8620 DEBUG Checking readiness of task: 1913 / 0x46620a0
Jul 07 20:46:13-055734 util-scheduler-8620 DEBUG Checking readiness of task: 1912 / 0x46620a0
Jul 07 20:46:13-055927 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-056119 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-056311 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-056502 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-056694 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-056884 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-057075 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-057291 util-scheduler-8620 DEBUG Running task: 1912 / 0x46620a0
Jul 07 20:46:13-057478 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-057654 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-057826 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-058009 util-scheduler-8620 DEBUG Canceling task: 1907 / 0x5e2b838
Jul 07 20:46:13-058228 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:13-058443 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:13-058677 cadet-p2p-8620 DEBUG Checking 0x530cb10 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-058909 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-059093 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 2
Jul 07 20:46:13-059269 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-059491 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:13-059671 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:13-059848 cadet-p2p-8620 DEBUG   payload ID 3
Jul 07 20:46:13-060130 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 88)
Jul 07 20:46:13-060328 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:13-060507 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:13-061237 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:13-061436 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:13-061672 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-061851 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:13-062029 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:13-062204 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:13-062403 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:13-062581 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:13-062758 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:13-062961 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:13-063144 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:13-063328 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:13-063511 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:13-063690 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:13-063861 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:13-064078 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:13-064252 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:13-064487 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:13-064735 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:13-064937 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:13-065121 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:13-065337 util-scheduler-8620 DEBUG Canceling task: 1781 / 0x5e31aa0
Jul 07 20:46:13-065552 util-scheduler-8620 DEBUG Adding task: 1914 / 0x5e31aa0
Jul 07 20:46:13-065976 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:13-066158 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:13-066339 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 3
Jul 07 20:46:13-066514 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:13-066740 cadet-p2p-8620 DEBUG Checking 0x531da68 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-066973 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-067158 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 3
Jul 07 20:46:13-067333 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-067563 cadet-p2p-8620 DEBUG Checking 0x531da68 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-067796 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-067978 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 3
Jul 07 20:46:13-068153 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-068322 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:13-068527 core-api-8620 DEBUG Asking core for transmission of 172 bytes to `D3TJ'
Jul 07 20:46:13-068741 util-scheduler-8620 DEBUG Adding task: 1915 / 0x5e2b838
Jul 07 20:46:13-068921 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:13-069109 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:13-069349 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:13-069527 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:13-069704 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:13-069942 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-070140 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 0
Jul 07 20:46:13-070319 cadet-p2p-8620 DEBUG QQQ    size: 172 bytes
Jul 07 20:46:13-070556 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-070751 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-070929 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-071164 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-071358 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-071535 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-071734 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:13-071940 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 88 bytes.
Jul 07 20:46:13-072128 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:13-072330 util-scheduler-8620 DEBUG Adding task: 1916 / 0x5e2b838
Jul 07 20:46:13-072550 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-072747 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-072949 util-scheduler-8620 DEBUG Adding task: 1917 / 0x46620a0
Jul 07 20:46:13-073151 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:13-075645 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-075851 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:13-076104 util-scheduler-8620 DEBUG Checking readiness of task: 1917 / 0x46620a0
Jul 07 20:46:13-076300 util-scheduler-8620 DEBUG Checking readiness of task: 1913 / 0x46620a0
Jul 07 20:46:13-076493 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-076686 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-076878 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-077071 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-077304 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-077517 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-077709 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-077903 util-scheduler-8620 DEBUG Running task: 1917 / 0x46620a0
Jul 07 20:46:13-078090 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-078269 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-078443 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-078622 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-078818 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-079009 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-079292 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-079502 util-scheduler-8620 DEBUG Running task: 1915 / 0x5e2b838
Jul 07 20:46:13-079698 util-scheduler-8620 DEBUG Canceling task: 1916 / 0x5e2b838
Jul 07 20:46:13-079914 util-scheduler-8620 DEBUG Adding task: 1918 / 0x5e2b838
Jul 07 20:46:13-080132 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-080329 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-080528 util-scheduler-8620 DEBUG Adding task: 1919 / 0x46620a0
Jul 07 20:46:13-080770 util-scheduler-8620 DEBUG Checking readiness of task: 1919 / 0x46620a0
Jul 07 20:46:13-080967 util-scheduler-8620 DEBUG Checking readiness of task: 1913 / 0x46620a0
Jul 07 20:46:13-081160 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-081375 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-081568 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-081760 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-081952 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-082146 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-082337 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-082531 util-scheduler-8620 DEBUG Running task: 1919 / 0x46620a0
Jul 07 20:46:13-082716 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-082892 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-083063 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-083242 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-083433 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-083622 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-083903 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-887372 util-scheduler-8620 DEBUG Checking readiness of task: 1913 / 0x46620a0
Jul 07 20:46:13-887760 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-887957 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-888149 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-888340 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-888529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-888720 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-888909 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-889104 util-scheduler-8620 DEBUG Running task: 1913 / 0x46620a0
Jul 07 20:46:13-889548 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:13-889811 util-scheduler-8620 DEBUG Adding task: 1920 / 0x4662248
Jul 07 20:46:13-890095 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-890318 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-890509 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-890699 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-890889 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-891078 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-891266 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-891455 util-scheduler-8620 DEBUG Running task: 1920 / 0x4662248
Jul 07 20:46:13-891644 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:13-891843 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:13-892074 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:13-892281 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-892487 util-scheduler-8620 DEBUG Adding task: 1921 / 0x46620a0
Jul 07 20:46:13-892674 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:13-892877 util-scheduler-8620 DEBUG Adding task: 1922 / 0x46620a0
Jul 07 20:46:13-893119 util-scheduler-8620 DEBUG Checking readiness of task: 1922 / 0x46620a0
Jul 07 20:46:13-896759 util-scheduler-8620 DEBUG Checking readiness of task: 1921 / 0x46620a0
Jul 07 20:46:13-896995 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-897216 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-897410 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-897605 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-897796 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-897988 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-898180 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-898375 util-scheduler-8620 DEBUG Running task: 1921 / 0x46620a0
Jul 07 20:46:13-898565 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-898748 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-898922 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-899117 util-scheduler-8620 DEBUG Canceling task: 1918 / 0x5e2b838
Jul 07 20:46:13-899362 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 172 bytes.
Jul 07 20:46:13-899587 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:13-899843 cadet-p2p-8620 DEBUG Checking 0x531da68 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-900080 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-900265 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 3
Jul 07 20:46:13-900443 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-900667 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:13-900847 cadet-p2p-8620 DEBUG   size 172 ok
Jul 07 20:46:13-901024 cadet-p2p-8620 DEBUG   payload ID 4
Jul 07 20:46:13-901345 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 172)
Jul 07 20:46:13-901547 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:13-901730 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:13-901920 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:13-902097 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:13-902269 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:13-902459 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:13-902638 cadet-chn-8620 DEBUG !!! SENT DATA MID 0
Jul 07 20:46:13-902883 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 1 s
Jul 07 20:46:13-903056 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:13-903284 cadet-chn-8620 DEBUG !! using delay 4 s
Jul 07 20:46:13-903485 util-scheduler-8620 DEBUG Adding task: 1923 / 0x5e33a48
Jul 07 20:46:13-903719 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:13-903954 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:13-904131 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:13-904305 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:13-904479 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:13-904683 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:13-904861 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:13-905037 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:13-905263 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:13-905448 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:13-905632 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:13-905814 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:13-905991 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:13-906165 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:13-906393 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:13-906573 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:13-906814 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:13-907066 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:13-907251 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:13-907433 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:13-907625 util-scheduler-8620 DEBUG Canceling task: 1914 / 0x5e31aa0
Jul 07 20:46:13-907843 util-scheduler-8620 DEBUG Adding task: 1924 / 0x5e31aa0
Jul 07 20:46:13-908096 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:13-908275 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:13-908455 cadet-con-8620 DEBUG !   accounting pid 4
Jul 07 20:46:13-908627 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:13-908854 cadet-p2p-8620 DEBUG Checking 0x5374038 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:13-909089 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-909299 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:13-909475 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-909710 cadet-p2p-8620 DEBUG Checking 0x5374038 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:13-909944 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-910128 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:13-910307 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:13-910479 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:13-910693 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:13-910919 util-scheduler-8620 DEBUG Adding task: 1925 / 0x5e2b838
Jul 07 20:46:13-911099 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:13-911275 cadet-p2p-8620 DEBUG   return 172
Jul 07 20:46:13-911475 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:13-911651 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:13-911826 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:13-912072 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-912269 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-912448 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-912684 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:13-912879 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:13-913056 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:13-913280 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:13-913488 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 172 bytes.
Jul 07 20:46:13-913673 core-api-8620 DEBUG Produced SEND message to core with 172 bytes payload
Jul 07 20:46:13-913884 util-scheduler-8620 DEBUG Adding task: 1926 / 0x5e2b838
Jul 07 20:46:13-914107 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-914333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-914542 util-scheduler-8620 DEBUG Adding task: 1927 / 0x46620a0
Jul 07 20:46:13-914748 util-8620 DEBUG Transmitting message of type 76 and size 228 to core service.
Jul 07 20:46:13-916500 util-8620 DEBUG Connection transmitted 228/228 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-916712 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:13-916982 util-scheduler-8620 DEBUG Checking readiness of task: 1927 / 0x46620a0
Jul 07 20:46:13-917184 util-scheduler-8620 DEBUG Checking readiness of task: 1922 / 0x46620a0
Jul 07 20:46:13-917401 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-917592 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-917784 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-917975 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-918166 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-918356 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-918545 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-918738 util-scheduler-8620 DEBUG Running task: 1927 / 0x46620a0
Jul 07 20:46:13-918924 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-919104 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-919277 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-919458 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-919656 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-919849 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-920139 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:13-920350 util-scheduler-8620 DEBUG Running task: 1925 / 0x5e2b838
Jul 07 20:46:13-920548 util-scheduler-8620 DEBUG Canceling task: 1926 / 0x5e2b838
Jul 07 20:46:13-920773 util-scheduler-8620 DEBUG Adding task: 1928 / 0x5e2b838
Jul 07 20:46:13-921002 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:13-921225 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:13-921442 util-scheduler-8620 DEBUG Adding task: 1929 / 0x46620a0
Jul 07 20:46:13-921697 util-scheduler-8620 DEBUG Checking readiness of task: 1929 / 0x46620a0
Jul 07 20:46:13-921893 util-scheduler-8620 DEBUG Checking readiness of task: 1922 / 0x46620a0
Jul 07 20:46:13-922085 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:13-922277 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:13-922468 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:13-922659 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:13-922862 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:13-923051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:13-923242 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:13-923434 util-scheduler-8620 DEBUG Running task: 1929 / 0x46620a0
Jul 07 20:46:13-923620 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:13-923797 util-8620 DEBUG process_notify is running
Jul 07 20:46:13-923968 util-8620 DEBUG client_notify is running
Jul 07 20:46:13-924146 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:13-924340 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:13-924530 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:13-924823 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-467239 util-scheduler-8620 DEBUG Checking readiness of task: 1922 / 0x46620a0
Jul 07 20:46:14-467637 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-467857 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-468055 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-468257 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-468451 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-468647 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-468843 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-469044 util-scheduler-8620 DEBUG Running task: 1922 / 0x46620a0
Jul 07 20:46:14-469500 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-469772 util-scheduler-8620 DEBUG Adding task: 1930 / 0x4662248
Jul 07 20:46:14-470064 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-470264 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-470459 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-470648 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-470838 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-471027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-471214 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-471404 util-scheduler-8620 DEBUG Running task: 1930 / 0x4662248
Jul 07 20:46:14-471595 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:14-471794 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:14-472026 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:14-472233 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:14-472438 util-scheduler-8620 DEBUG Adding task: 1931 / 0x46620a0
Jul 07 20:46:14-472625 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-472831 util-scheduler-8620 DEBUG Adding task: 1932 / 0x46620a0
Jul 07 20:46:14-473073 util-scheduler-8620 DEBUG Checking readiness of task: 1932 / 0x46620a0
Jul 07 20:46:14-483861 util-scheduler-8620 DEBUG Checking readiness of task: 1931 / 0x46620a0
Jul 07 20:46:14-484152 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-484348 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-484539 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-484730 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-484926 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-485116 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-485331 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-485527 util-scheduler-8620 DEBUG Running task: 1931 / 0x46620a0
Jul 07 20:46:14-485713 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:14-485893 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-486065 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-486257 util-scheduler-8620 DEBUG Canceling task: 1893 / 0x4d6ff98
Jul 07 20:46:14-486502 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 156 bytes.
Jul 07 20:46:14-486724 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:14-486965 cadet-p2p-8620 DEBUG Checking 0x5377be8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-487199 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-487381 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 6
Jul 07 20:46:14-487556 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-487810 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:14-487989 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:46:14-488163 cadet-p2p-8620 DEBUG   payload ID 7
Jul 07 20:46:14-488456 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 156)
Jul 07 20:46:14-488652 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:14-488834 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:14-489020 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:14-489212 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:14-489383 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:14-489570 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:14-489748 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:46:14-489976 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 875 ms
Jul 07 20:46:14-490147 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:14-490351 cadet-chn-8620 DEBUG !! using delay 3502932 µs
Jul 07 20:46:14-490552 util-scheduler-8620 DEBUG Adding task: 1933 / 0x4d65218
Jul 07 20:46:14-490754 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:14-490984 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:14-491160 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:14-491333 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:14-491504 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:14-491700 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:14-491874 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:14-492047 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:14-492246 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-492426 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-492608 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-492789 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-492964 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-493133 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-493370 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-493543 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-493775 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-493959 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-494139 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:14-494325 util-scheduler-8620 DEBUG Canceling task: 1890 / 0x4d707d0
Jul 07 20:46:14-494536 util-scheduler-8620 DEBUG Adding task: 1934 / 0x4d707d0
Jul 07 20:46:14-494784 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:14-494966 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:14-495148 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 7
Jul 07 20:46:14-495323 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:14-495509 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:46:14-495715 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-495894 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:14-496069 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:14-496269 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-496479 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 156 bytes.
Jul 07 20:46:14-496667 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:46:14-496854 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:14-497053 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:46:14-498325 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-498643 util-scheduler-8620 DEBUG Checking readiness of task: 1932 / 0x46620a0
Jul 07 20:46:14-499227 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-499426 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-499643 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-499837 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-500028 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-500219 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-500408 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-500600 util-scheduler-8620 DEBUG Running task: 1932 / 0x46620a0
Jul 07 20:46:14-501008 util-8620 DEBUG receive_ready read 420/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-501273 util-scheduler-8620 DEBUG Adding task: 1935 / 0x4662248
Jul 07 20:46:14-501526 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-501719 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-501909 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-502099 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-502289 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-502477 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-502666 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-502855 util-scheduler-8620 DEBUG Running task: 1935 / 0x4662248
Jul 07 20:46:14-503045 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:14-503245 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:14-503465 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `V8XX'
Jul 07 20:46:14-503723 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-503963 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-504192 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-504399 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:14-504645 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-504857 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-505047 cadet-con-8620 DEBUG  PID 6 (expected 6+)
Jul 07 20:46:14-505243 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:14-505431 util-scheduler-8620 DEBUG Canceling task: 1852 / 0x4d707d0
Jul 07 20:46:14-505652 util-scheduler-8620 DEBUG Adding task: 1936 / 0x4d707d0
Jul 07 20:46:14-505831 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:14-506089 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-506304 util-scheduler-8620 DEBUG Adding task: 1937 / 0x4d5e5d8
Jul 07 20:46:14-506489 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:14-506656 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:14-510388 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:14-511420 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:14-511669 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:14-515405 cadet-tun-8620 INFO <=== {          DATA_ACK} on V8XX
Jul 07 20:46:14-515689 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:46:14-515871 cadet-chn-8620 DEBUG   id 1
Jul 07 20:46:14-516047 cadet-chn-8620 DEBUG !!! Freeing 1
Jul 07 20:46:14-516303 cadet-chn-8620 INFO !!!  took 26303 µs, new delay 26303 µs
Jul 07 20:46:14-516483 cadet-chn-8620 DEBUG  COPYFREE 0x5266ee0
Jul 07 20:46:14-516666 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:14-516837 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:46:14-517037 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-517243 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-517428 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-517610 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-517786 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-517956 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-518173 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-518374 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-518611 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-518795 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-518971 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:46:14-519199 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-519377 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:14-519560 util-scheduler-8620 DEBUG Canceling task: 1933 / 0x4d65218
Jul 07 20:46:14-519805 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:14-519981 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:14-520154 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:14-520325 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:14-520543 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:14-520720 cadet-con-8620 DEBUG  ACK 70
Jul 07 20:46:14-520900 cadet-con-8620 DEBUG  last pid 6, last ack 69, qmax 11, q 0
Jul 07 20:46:14-521166 cadet-con-8620 INFO --> {               ACK} ( 70) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:14-521449 cadet-con-8620 DEBUG  ack 70
Jul 07 20:46:14-521630 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:14-521864 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-522071 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-522367 cadet-p2p-8620 INFO que {               ACK} ( 70) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:14-522566 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:14-522789 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-522972 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 7
Jul 07 20:46:14-523146 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-523350 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:46:14-523564 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:46:14-523787 util-scheduler-8620 DEBUG Adding task: 1938 / 0x4d6ff98
Jul 07 20:46:14-523968 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:14-524170 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-524345 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:14-524519 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-524755 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-524940 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:46:14-525114 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-525331 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-525540 util-scheduler-8620 DEBUG Adding task: 1939 / 0x4662248
Jul 07 20:46:14-525823 util-scheduler-8620 DEBUG Checking readiness of task: 1937 / 0x4d5e5d8
Jul 07 20:46:14-526022 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-526218 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-526410 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-526602 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-526793 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-526987 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-527189 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-527386 util-scheduler-8620 DEBUG Running task: 1937 / 0x4d5e5d8
Jul 07 20:46:14-527574 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-527756 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-527932 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-528176 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:14-528497 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-528753 util-scheduler-8620 DEBUG Running task: 1939 / 0x4662248
Jul 07 20:46:14-528952 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:14-529155 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:14-529425 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:14-529762 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-530025 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-530236 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-530420 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:14-530594 cadet-con-8620 DEBUG   ACK 69 (was 68)
Jul 07 20:46:14-530823 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-531052 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-531257 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-531439 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:14-531649 util-scheduler-8620 DEBUG Adding task: 1940 / 0x4662248
Jul 07 20:46:14-531848 util-scheduler-8620 DEBUG Running task: 1938 / 0x4d6ff98
Jul 07 20:46:14-532061 util-scheduler-8620 DEBUG Adding task: 1941 / 0x4d6ff98
Jul 07 20:46:14-532283 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:14-532485 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:14-532692 util-scheduler-8620 DEBUG Adding task: 1942 / 0x46620a0
Jul 07 20:46:14-532951 util-scheduler-8620 DEBUG Checking readiness of task: 1942 / 0x46620a0
Jul 07 20:46:14-533145 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-533358 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-533548 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-533736 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-533925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-534112 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-534301 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-534491 util-scheduler-8620 DEBUG Running task: 1942 / 0x46620a0
Jul 07 20:46:14-534674 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:14-534854 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-535024 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-535203 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:14-535397 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:14-535586 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:14-535905 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-536113 util-scheduler-8620 DEBUG Running task: 1940 / 0x4662248
Jul 07 20:46:14-536304 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:14-536499 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:14-536715 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:14-536957 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-537209 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-537439 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-537648 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:14-537887 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-538093 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-538280 cadet-con-8620 DEBUG  PID 7 (expected 7+)
Jul 07 20:46:14-538459 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:14-538644 util-scheduler-8620 DEBUG Canceling task: 1936 / 0x4d707d0
Jul 07 20:46:14-538884 util-scheduler-8620 DEBUG Adding task: 1943 / 0x4d707d0
Jul 07 20:46:14-539065 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:14-539311 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-539519 util-scheduler-8620 DEBUG Adding task: 1944 / 0x4d5e5d8
Jul 07 20:46:14-539701 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:14-539868 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:14-543362 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:14-544827 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:14-545064 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:14-548666 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:14-548912 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:14-549231 cadet-chn-8620 INFO <=== DATA 1 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-549424 cadet-chn-8620 DEBUG RECV 1 (16)
Jul 07 20:46:14-549599 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:46:14-549808 util-server-nc-8620 DEBUG Adding message of type 285 and size 12 to pending queue (which has 1 entries)
Jul 07 20:46:14-550012 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:14-550223 util-scheduler-8620 DEBUG Adding task: 1945 / 0x4d5c418
Jul 07 20:46:14-550410 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:46:14-550588 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:46:14-550837 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-551054 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:14-551255 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-551437 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-551619 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-551800 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-551976 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-552147 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-552361 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-552536 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-552784 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-552970 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-553284 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:14-553455 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-553641 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:14-557302 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:14-558071 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:14-558383 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-558577 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:14-562175 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:14-562471 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:14-562654 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:14-562874 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-563070 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:14-563346 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:14-563545 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:14-563722 cadet-con-8620 DEBUG last pid sent 7
Jul 07 20:46:14-563894 cadet-con-8620 DEBUG      ack recv 69
Jul 07 20:46:14-564065 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:14-564241 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:14-564474 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-564682 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-564999 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:14-565223 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:14-565449 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-565660 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 7
Jul 07 20:46:14-565836 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-566037 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:14-566239 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-566415 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:14-566589 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-566826 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-567010 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:46:14-567184 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-567417 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-567610 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-567785 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-567982 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-568157 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:14-568382 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:14-568556 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:14-568731 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:14-568902 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:14-569120 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:14-569318 cadet-con-8620 DEBUG  ACK 71
Jul 07 20:46:14-569497 cadet-con-8620 DEBUG  last pid 7, last ack 70, qmax 11, q 0
Jul 07 20:46:14-569676 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:14-569845 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:14-570028 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:14-570211 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:14-570390 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:14-570575 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:14-570748 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:14-570929 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:14-571102 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:14-571461 cadet-p2p-8620 DEBUG Checking 0x5408900 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-571698 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-571881 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 7
Jul 07 20:46:14-572054 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-572315 cadet-con-8620 INFO --> {               ACK} ( 71) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:14-572505 cadet-con-8620 DEBUG  ack 71
Jul 07 20:46:14-572680 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:14-572913 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-573122 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-573448 cadet-p2p-8620 INFO que {               ACK} ( 71) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:14-573653 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:14-573891 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-574079 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 7
Jul 07 20:46:14-574258 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-574465 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:14-574680 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-574863 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:14-575042 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-575288 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-575476 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:46:14-575654 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-575894 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-576093 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-576280 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-576482 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-576743 util-scheduler-8620 DEBUG Adding task: 1946 / 0x4662248
Jul 07 20:46:14-577036 util-scheduler-8620 DEBUG Checking readiness of task: 1945 / 0x4d5c418
Jul 07 20:46:14-577274 util-scheduler-8620 DEBUG Checking readiness of task: 1944 / 0x4d5e5d8
Jul 07 20:46:14-577470 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-577666 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-577856 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-578047 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-578242 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-578436 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-578784 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-579117 util-scheduler-8620 DEBUG Running task: 1944 / 0x4d5e5d8
Jul 07 20:46:14-579358 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-579540 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-579714 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-579982 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-580202 util-scheduler-8620 DEBUG Adding task: 1947 / 0x4d5e5d8
Jul 07 20:46:14-580419 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:14-580730 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-580938 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:14-581140 util-scheduler-8620 DEBUG Running task: 1945 / 0x4d5c418
Jul 07 20:46:14-581351 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:14-581526 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-581719 util-server-nc-8620 DEBUG Copying message of type 285 and size 12 from pending queue to transmission buffer
Jul 07 20:46:14-582040 util-8620 DEBUG Connection transmitted 12/12 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:14-582246 util-scheduler-8620 DEBUG Running task: 1946 / 0x4662248
Jul 07 20:46:14-582437 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:14-582634 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:14-582857 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:14-583117 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-583368 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-583576 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-583759 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:14-583931 cadet-con-8620 DEBUG   ACK 70 (was 69)
Jul 07 20:46:14-584158 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-584389 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-584593 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-584775 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:14-584955 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-585163 util-scheduler-8620 DEBUG Adding task: 1948 / 0x46620a0
Jul 07 20:46:14-585445 util-scheduler-8620 DEBUG Checking readiness of task: 1948 / 0x46620a0
Jul 07 20:46:14-585640 util-scheduler-8620 DEBUG Checking readiness of task: 1947 / 0x4d5e5d8
Jul 07 20:46:14-585831 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-586020 util-scheduler-8620 DEBUG Checking readiness of task: 1806 / 0x4d5c418
Jul 07 20:46:14-586210 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-586398 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-586587 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-586774 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-586986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-587177 util-scheduler-8620 DEBUG Running task: 1806 / 0x4d5c418
Jul 07 20:46:14-587563 util-8620 DEBUG receive_ready read 20/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:46:14-587773 util-8620 DEBUG Server receives 20 bytes from `<unbound UNIX client>'.
Jul 07 20:46:14-587964 util-8620 DEBUG Server-mst receives 20 bytes with 0 bytes already in private buffer
Jul 07 20:46:14-588147 util-8620 DEBUG Server-mst has 20 bytes left in inbound buffer
Jul 07 20:46:14-588329 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:46:14-588516 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:46:14-588737 util-scheduler-8620 DEBUG Adding task: 1949 / 0x4d5c578
Jul 07 20:46:14-588915 cadet-loc-8620 DEBUG 
Jul 07 20:46:14-589079 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:46:14-589270 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:14-589443 cadet-loc-8620 DEBUG   on channel 80000002
Jul 07 20:46:14-589622 cadet-loc-8620 DEBUG    -- ch 0x4d650a8
Jul 07 20:46:14-589794 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:46:14-589961 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:46:14-590162 cadet-tun-8620 DEBUG Tunnel send connection ACKs on V8XX
Jul 07 20:46:14-590342 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:46:14-590519 cadet-tun-8620 DEBUG   allowed 64
Jul 07 20:46:14-590710 util-scheduler-8620 DEBUG Canceling task: 1949 / 0x4d5c578
Jul 07 20:46:14-590902 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:14-591082 util-8620 DEBUG Server-mst has 12 bytes left in inbound buffer
Jul 07 20:46:14-591266 util-8620 DEBUG Server-mst leaves 12 bytes in private buffer
Jul 07 20:46:14-591441 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:46:14-591618 util-8620 DEBUG Server-mst receives 0 bytes with 12 bytes already in private buffer
Jul 07 20:46:14-591805 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:46:14-591992 util-8620 DEBUG Server schedules transmission of 12-byte message of type 285 to client.
Jul 07 20:46:14-592265 util-scheduler-8620 DEBUG Adding task: 1950 / 0x4d5c578
Jul 07 20:46:14-592447 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:46:14-592618 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:14-592794 cadet-loc-8620 DEBUG   on channel 80000002
Jul 07 20:46:14-592973 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:46:14-593236 cadet-chn-8620 INFO ===> {              DATA} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-593436 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:46:14-593639 cadet-chn-8620 DEBUG !!! SAVE 2 {              DATA}
Jul 07 20:46:14-593822 cadet-chn-8620 DEBUG   at 0x540c558
Jul 07 20:46:14-594005 cadet-chn-8620 DEBUG   new chq: 0x540c638
Jul 07 20:46:14-594210 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:14-594411 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-594593 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-594775 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-594962 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-595139 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-595308 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-595526 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-595699 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-595934 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-596120 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-596422 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:14-596597 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-596783 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:14-600580 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:14-601546 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:14-601760 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-601951 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:14-605324 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:14-605569 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:14-605763 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:14-605984 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-606179 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:14-606454 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection CMHCKRVP (->V8XX) (96 bytes)
Jul 07 20:46:14-606650 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:14-606826 cadet-con-8620 DEBUG last pid sent 7
Jul 07 20:46:14-606998 cadet-con-8620 DEBUG      ack recv 70
Jul 07 20:46:14-607174 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:14-607406 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-607611 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-607922 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 96)
Jul 07 20:46:14-608119 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:14-608343 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-608525 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-608699 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-608900 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:14-609100 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-609294 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:14-609470 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-609707 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-609889 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:46:14-610063 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-610295 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-610487 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-610662 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-610893 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-611084 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:14-611259 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:14-611455 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-611661 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-611839 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-612021 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-612207 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-614379 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-614572 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-614802 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-614981 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-615304 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:14-615495 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-615669 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:14-615847 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:46:14-616054 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-616232 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-616415 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-616596 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-616771 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-616941 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-617153 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-617348 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-617604 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:14-617790 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-617964 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:46:14-618193 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-618384 cadet-loc-8620 DEBUG send local FWD ack on 80000002 towards 0x4d5c6d8
Jul 07 20:46:14-618596 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:14-618803 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:14-619017 util-scheduler-8620 DEBUG Adding task: 1951 / 0x4d5c418
Jul 07 20:46:14-619202 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:46:14-619393 util-scheduler-8620 DEBUG Canceling task: 1950 / 0x4d5c578
Jul 07 20:46:14-619595 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:14-619781 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:46:14-619989 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:46:14-620201 util-scheduler-8620 DEBUG Adding task: 1952 / 0x4d5c418
Jul 07 20:46:14-620403 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:46:14-620642 util-scheduler-8620 DEBUG Running task: 1947 / 0x4d5e5d8
Jul 07 20:46:14-620833 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-621024 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-621227 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-621468 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:14-621809 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-622035 util-scheduler-8620 DEBUG Running task: 1948 / 0x46620a0
Jul 07 20:46:14-622441 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-622682 util-scheduler-8620 DEBUG Adding task: 1953 / 0x4662248
Jul 07 20:46:14-622958 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-623152 util-scheduler-8620 DEBUG Checking readiness of task: 1951 / 0x4d5c418
Jul 07 20:46:14-623343 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-623533 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-623722 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-623911 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-624099 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-624288 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-624478 util-scheduler-8620 DEBUG Running task: 1951 / 0x4d5c418
Jul 07 20:46:14-624661 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:14-624840 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-625032 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:14-625339 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:14-625544 util-scheduler-8620 DEBUG Running task: 1953 / 0x4662248
Jul 07 20:46:14-625736 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:14-625932 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:14-626155 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:14-626359 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:14-626560 util-scheduler-8620 DEBUG Adding task: 1954 / 0x46620a0
Jul 07 20:46:14-626750 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-627912 util-scheduler-8620 DEBUG Adding task: 1955 / 0x46620a0
Jul 07 20:46:14-628201 util-scheduler-8620 DEBUG Checking readiness of task: 1955 / 0x46620a0
Jul 07 20:46:14-628396 util-scheduler-8620 DEBUG Checking readiness of task: 1954 / 0x46620a0
Jul 07 20:46:14-628587 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-628777 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-628966 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-629155 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-629366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-629555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-629743 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-629934 util-scheduler-8620 DEBUG Running task: 1954 / 0x46620a0
Jul 07 20:46:14-630132 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:14-630306 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-630475 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-630663 util-scheduler-8620 DEBUG Canceling task: 1941 / 0x4d6ff98
Jul 07 20:46:14-630885 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:46:14-631103 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:14-631340 cadet-p2p-8620 DEBUG Checking 0x536beb8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-631572 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:14-631750 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:14-631941 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:14-632209 cadet-p2p-8620 INFO snd {               ACK} ( 71) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:14-632402 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:14-632580 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:14-632767 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:14-632939 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:14-633122 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:14-633319 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:14-633545 cadet-p2p-8620 DEBUG Checking 0x5408900 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-633780 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-633964 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-634140 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-634369 cadet-p2p-8620 DEBUG Checking 0x5408900 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-634602 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-634790 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-634968 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-635136 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:14-635349 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:14-635579 util-scheduler-8620 DEBUG Adding task: 1956 / 0x4d6ff98
Jul 07 20:46:14-635769 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:14-635949 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:14-636156 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-636333 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:14-636509 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-636758 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-636954 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-637133 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-637740 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-637937 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:14-638114 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:14-638315 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-638525 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:14-638731 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:14-638952 util-scheduler-8620 DEBUG Adding task: 1957 / 0x4d6ff98
Jul 07 20:46:14-639180 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:14-639382 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:14-639590 util-scheduler-8620 DEBUG Adding task: 1958 / 0x46620a0
Jul 07 20:46:14-639793 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:14-640581 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-640781 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:14-640987 util-scheduler-8620 DEBUG Running task: 1955 / 0x46620a0
Jul 07 20:46:14-641416 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-641650 util-scheduler-8620 DEBUG Adding task: 1959 / 0x4662248
Jul 07 20:46:14-641919 util-scheduler-8620 DEBUG Checking readiness of task: 1958 / 0x46620a0
Jul 07 20:46:14-642115 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-642309 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-642501 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-642692 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-642882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-643072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-643261 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-643455 util-scheduler-8620 DEBUG Running task: 1958 / 0x46620a0
Jul 07 20:46:14-643641 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:14-643818 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-643991 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-644176 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:14-644379 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:14-644571 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:14-644867 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-645080 util-scheduler-8620 DEBUG Running task: 1959 / 0x4662248
Jul 07 20:46:14-645297 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:14-645498 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:14-645726 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:14-645986 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-646228 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-646458 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-646668 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:14-646923 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-647137 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-647328 cadet-con-8620 DEBUG  PID 8 (expected 8+)
Jul 07 20:46:14-647509 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:14-647704 util-scheduler-8620 DEBUG Canceling task: 1943 / 0x4d707d0
Jul 07 20:46:14-647936 util-scheduler-8620 DEBUG Adding task: 1960 / 0x4d707d0
Jul 07 20:46:14-648120 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:14-648380 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-648594 util-scheduler-8620 DEBUG Adding task: 1961 / 0x4d5e5d8
Jul 07 20:46:14-648778 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:14-648946 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:14-652414 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:14-653697 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:14-653897 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:14-657142 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:14-657367 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:14-657646 cadet-chn-8620 INFO <=== DATA 1 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-657895 cadet-chn-8620 WARNING MID 1 on channel V8XX:19 gid:40000000 (80000002 / 0) not expected (window: 2 - 65). Dropping!
Jul 07 20:46:14-658086 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:46:14-658264 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:46:14-658510 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-658706 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:14-658895 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:46:14-659082 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:14-659264 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:14-659454 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:46:14-659630 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:14-659799 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:14-659994 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:14-660184 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:14-660382 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:14-660568 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:46:14-660749 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 7
Jul 07 20:46:14-660924 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:14-661169 cadet-p2p-8620 DEBUG Checking 0x5419038 towards CMHCKRVP (->V8XX)
Jul 07 20:46:14-661447 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-661636 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-661818 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-662036 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:14-662239 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:14-662427 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-662616 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:14-662802 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-662984 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-663158 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-663388 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:14-663566 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-663803 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:14-663996 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-664310 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:14-664491 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-664681 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:14-668332 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:14-669220 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:14-669470 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-669663 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:14-672810 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:14-673050 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:14-673253 cadet-tun-8620 DEBUG     q_n 1, 
Jul 07 20:46:14-673474 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:14-673669 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:14-673946 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:14-674143 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 1
Jul 07 20:46:14-674320 cadet-con-8620 DEBUG last pid sent 7
Jul 07 20:46:14-674493 cadet-con-8620 DEBUG      ack recv 70
Jul 07 20:46:14-674662 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:14-674839 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:14-675103 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-675311 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-675623 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:14-675823 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:14-676046 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-676227 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-676401 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-676602 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:14-676802 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-676977 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:14-677151 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-677408 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-677602 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:14-677778 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:14-678010 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-678202 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-678378 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-678575 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-678750 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:14-678975 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:14-679148 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:14-679323 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:14-679493 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:14-679719 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:14-679902 cadet-con-8620 DEBUG  ACK 72
Jul 07 20:46:14-680082 cadet-con-8620 DEBUG  last pid 8, last ack 71, qmax 11, q 0
Jul 07 20:46:14-680353 cadet-con-8620 INFO --> {               ACK} ( 72) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:14-680544 cadet-con-8620 DEBUG  ack 72
Jul 07 20:46:14-680723 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:14-680958 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-681164 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-681481 cadet-p2p-8620 INFO que {               ACK} ( 72) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:14-681680 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:14-681906 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:14-682088 cadet-con-8620 DEBUG  last ack recv: 70, last pid sent: 7
Jul 07 20:46:14-682263 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-682464 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:14-682664 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:14-682852 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:14-683027 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:14-683264 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-683448 cadet-p2p-8620 DEBUG QQQ    payload , 72
Jul 07 20:46:14-683626 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-683869 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-684071 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:14-684251 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:14-684489 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-684686 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:14-684867 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:14-685068 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:14-685276 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-685498 util-scheduler-8620 DEBUG Adding task: 1962 / 0x46620a0
Jul 07 20:46:14-685735 util-scheduler-8620 DEBUG Running task: 1956 / 0x4d6ff98
Jul 07 20:46:14-685938 util-scheduler-8620 DEBUG Canceling task: 1957 / 0x4d6ff98
Jul 07 20:46:14-686163 util-scheduler-8620 DEBUG Adding task: 1963 / 0x4d6ff98
Jul 07 20:46:14-686390 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:14-686595 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:14-686796 util-scheduler-8620 DEBUG Adding task: 1964 / 0x46620a0
Jul 07 20:46:14-687072 util-scheduler-8620 DEBUG Checking readiness of task: 1964 / 0x46620a0
Jul 07 20:46:14-687273 util-scheduler-8620 DEBUG Checking readiness of task: 1962 / 0x46620a0
Jul 07 20:46:14-687465 util-scheduler-8620 DEBUG Checking readiness of task: 1961 / 0x4d5e5d8
Jul 07 20:46:14-687656 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-687848 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-688039 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-688230 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-688421 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-688611 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-688800 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-688994 util-scheduler-8620 DEBUG Running task: 1961 / 0x4d5e5d8
Jul 07 20:46:14-689180 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-689388 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-689561 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-689808 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-690020 util-scheduler-8620 DEBUG Adding task: 1965 / 0x4d5e5d8
Jul 07 20:46:14-690226 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:14-690538 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-690742 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:14-690944 util-scheduler-8620 DEBUG Running task: 1964 / 0x46620a0
Jul 07 20:46:14-691128 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:14-691313 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-691484 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-691664 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:14-691865 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:14-692333 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:14-692830 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:14-693139 util-scheduler-8620 DEBUG Checking readiness of task: 1965 / 0x4d5e5d8
Jul 07 20:46:14-693375 util-scheduler-8620 DEBUG Checking readiness of task: 1962 / 0x46620a0
Jul 07 20:46:14-693570 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-693763 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-693955 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-694147 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-694339 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-694530 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-694720 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-694916 util-scheduler-8620 DEBUG Running task: 1965 / 0x4d5e5d8
Jul 07 20:46:14-695103 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-695285 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-695458 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-695692 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:14-696087 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-745386 util-scheduler-8620 DEBUG Checking readiness of task: 1962 / 0x46620a0
Jul 07 20:46:14-745732 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-745930 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-746124 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-746317 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-746509 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-746700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-746890 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-747085 util-scheduler-8620 DEBUG Running task: 1962 / 0x46620a0
Jul 07 20:46:14-747504 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-747759 util-scheduler-8620 DEBUG Adding task: 1966 / 0x4662248
Jul 07 20:46:14-748034 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-748227 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-748417 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-748608 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-748798 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-748987 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-749176 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-749393 util-scheduler-8620 DEBUG Running task: 1966 / 0x4662248
Jul 07 20:46:14-749585 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:14-749785 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:14-750013 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:14-750276 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:14-750519 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-750746 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:14-750954 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:14-751200 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:14-751408 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:14-751597 cadet-con-8620 DEBUG  PID 3 (expected 3+)
Jul 07 20:46:14-751777 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:14-751966 util-scheduler-8620 DEBUG Canceling task: 1898 / 0x5e31aa0
Jul 07 20:46:14-752189 util-scheduler-8620 DEBUG Adding task: 1967 / 0x5e31aa0
Jul 07 20:46:14-752368 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:14-752625 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:14-752841 util-scheduler-8620 DEBUG Adding task: 1968 / 0x4d5e5d8
Jul 07 20:46:14-753025 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:14-754018 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:14-757813 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:14-758579 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:14-758776 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:14-761978 cadet-tun-8620 INFO <=== {       CHANNEL_ACK} on D3TJ
Jul 07 20:46:14-762229 cadet-chn-8620 DEBUG   channel confirm FWD D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:14-762465 cadet-chn-8620 DEBUG   sending channel BCK ack for channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:14-762715 cadet-chn-8620 INFO ===> {       CHANNEL_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:14-762926 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:14-763126 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:14-763339 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:14-763525 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:14-763708 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:14-763887 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:14-764058 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:14-764274 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:14-764445 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:14-764680 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-764929 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:14-765114 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:14-765432 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:14-765604 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-765789 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:14-768788 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:14-769914 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:14-770135 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:14-770323 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:14-773444 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:14-773681 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:14-773863 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:14-774083 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:14-774261 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:14-774480 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-774670 cadet-tun-8620 DEBUG type {       CHANNEL_ACK}
Jul 07 20:46:14-774944 cadet-con-8620 INFO --> {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (88 bytes)
Jul 07 20:46:14-775141 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:14-775318 cadet-con-8620 DEBUG last pid sent 4
Jul 07 20:46:14-775491 cadet-con-8620 DEBUG      ack recv 66
Jul 07 20:46:14-775662 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:14-775838 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:14-776071 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:14-776276 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:14-776583 cadet-p2p-8620 INFO que {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 88)
Jul 07 20:46:14-776781 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:14-777005 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-777186 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 4
Jul 07 20:46:14-777385 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-777587 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:14-777788 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:14-777963 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:14-778138 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:14-778376 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:14-778570 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-778747 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-778980 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:14-779173 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-779350 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-779583 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-779775 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-779952 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-780149 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:14-780379 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-780553 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:14-780747 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:14-780919 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:14-781139 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-781345 cadet-con-8620 DEBUG  ACK 67
Jul 07 20:46:14-781524 cadet-con-8620 DEBUG  last pid 3, last ack 66, qmax 11, q 0
Jul 07 20:46:14-782386 cadet-con-8620 INFO --> {               ACK} ( 67) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:14-782579 cadet-con-8620 DEBUG  ack 67
Jul 07 20:46:14-782757 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:14-782989 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:14-783195 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:14-783483 cadet-p2p-8620 INFO que {               ACK} ( 67) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:14-783681 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:14-783903 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-784083 cadet-con-8620 DEBUG  last ack recv: 66, last pid sent: 4
Jul 07 20:46:14-784257 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:14-784455 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:14-784655 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:14-784829 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:14-785007 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:14-785279 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-785463 cadet-p2p-8620 DEBUG QQQ    payload , 67
Jul 07 20:46:14-785640 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:14-785874 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:14-786067 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-786245 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-786479 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:14-786673 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-786850 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-787083 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:14-787276 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:14-787452 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:14-787647 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:14-787833 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-788051 util-scheduler-8620 DEBUG Adding task: 1969 / 0x46620a0
Jul 07 20:46:14-788322 util-scheduler-8620 DEBUG Checking readiness of task: 1969 / 0x46620a0
Jul 07 20:46:14-788520 util-scheduler-8620 DEBUG Checking readiness of task: 1968 / 0x4d5e5d8
Jul 07 20:46:14-788712 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-788902 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-789092 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-789305 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-789495 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-789684 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-789873 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-790065 util-scheduler-8620 DEBUG Running task: 1968 / 0x4d5e5d8
Jul 07 20:46:14-790251 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:14-790429 util-8620 DEBUG process_notify is running
Jul 07 20:46:14-790601 util-8620 DEBUG client_notify is running
Jul 07 20:46:14-790830 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:14-791150 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:14-791364 util-scheduler-8620 DEBUG Running task: 1969 / 0x46620a0
Jul 07 20:46:14-791787 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:14-792087 util-scheduler-8620 DEBUG Adding task: 1970 / 0x4662248
Jul 07 20:46:14-792343 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:14-792537 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:14-792729 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:14-792920 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:14-793110 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:14-793325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:14-793515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:14-793705 util-scheduler-8620 DEBUG Running task: 1970 / 0x4662248
Jul 07 20:46:14-793895 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:14-794091 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:14-794307 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:14-794556 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:14-794803 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-795012 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-795194 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:14-795367 cadet-con-8620 DEBUG   ACK 71 (was 70)
Jul 07 20:46:14-795595 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:14-795825 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:14-796030 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:14-796211 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:14-796386 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:14-796585 util-scheduler-8620 DEBUG Adding task: 1971 / 0x46620a0
Jul 07 20:46:15-203710 util-scheduler-8620 DEBUG Checking readiness of task: 1971 / 0x46620a0
Jul 07 20:46:15-204091 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-204288 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-204483 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-204675 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-204866 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-205060 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-205278 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-205476 util-scheduler-8620 DEBUG Running task: 1971 / 0x46620a0
Jul 07 20:46:15-205899 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:15-206158 util-scheduler-8620 DEBUG Adding task: 1972 / 0x4662248
Jul 07 20:46:15-206440 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-206633 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-206824 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-207015 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-207205 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-207622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-207815 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-208006 util-scheduler-8620 DEBUG Running task: 1972 / 0x4662248
Jul 07 20:46:15-208198 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:15-208399 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:15-208634 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `V8XX'
Jul 07 20:46:15-208925 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:15-209170 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:15-209421 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:15-209628 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:15-209873 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:15-210081 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:15-210270 cadet-con-8620 DEBUG  PID 9 (expected 9+)
Jul 07 20:46:15-210450 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:15-210640 util-scheduler-8620 DEBUG Canceling task: 1960 / 0x4d707d0
Jul 07 20:46:15-210865 util-scheduler-8620 DEBUG Adding task: 1973 / 0x4d707d0
Jul 07 20:46:15-211112 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:15-211378 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:15-211597 util-scheduler-8620 DEBUG Adding task: 1974 / 0x4d5e5d8
Jul 07 20:46:15-211782 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:15-211949 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:15-215493 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:15-216310 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:15-216522 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:15-219826 cadet-tun-8620 INFO <=== {          DATA_ACK} on V8XX
Jul 07 20:46:15-220031 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:46:15-220213 cadet-chn-8620 DEBUG   head 2, out!
Jul 07 20:46:15-220396 cadet-chn-8620 DEBUG free_sent_reliable 1 0
Jul 07 20:46:15-220581 cadet-chn-8620 DEBUG  rel 0x4d65218, head 0x540c558
Jul 07 20:46:15-220758 cadet-chn-8620 DEBUG free_sent_reliable END
Jul 07 20:46:15-220927 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:15-221103 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:46:15-221366 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:15-221548 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:15-221731 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:15-221912 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:15-222090 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:15-222260 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:15-222478 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:15-222652 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:15-222886 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:15-223070 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:15-223248 cadet-chn-8620 DEBUG  buffer space 10, allowing
Jul 07 20:46:15-223475 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:15-223653 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:15-223876 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:15-224051 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:15-224228 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:15-224400 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:15-224619 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:15-224797 cadet-con-8620 DEBUG  ACK 73
Jul 07 20:46:15-224975 cadet-con-8620 DEBUG  last pid 9, last ack 72, qmax 11, q 0
Jul 07 20:46:15-225159 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:15-225348 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:15-225534 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:15-225717 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:15-225898 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:15-226084 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:15-226258 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:15-226440 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:15-226614 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:15-226837 cadet-p2p-8620 DEBUG Checking 0x5419038 towards CMHCKRVP (->V8XX)
Jul 07 20:46:15-227093 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:15-227276 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:15-227450 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:15-227712 cadet-con-8620 INFO --> {               ACK} ( 73) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:15-227904 cadet-con-8620 DEBUG  ack 73
Jul 07 20:46:15-228083 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:15-228316 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:15-228523 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:15-228818 cadet-p2p-8620 INFO que {               ACK} ( 73) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:15-229017 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:15-229263 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:15-229446 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:15-229620 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:15-229820 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:15-230022 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:15-230198 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:15-230372 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:15-230608 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:15-230792 cadet-p2p-8620 DEBUG QQQ    payload , 73
Jul 07 20:46:15-230967 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:15-231199 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:15-231393 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:15-231569 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:15-231802 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:15-231994 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:15-232169 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:15-232366 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:15-232551 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:15-232766 util-scheduler-8620 DEBUG Adding task: 1975 / 0x46620a0
Jul 07 20:46:15-233037 util-scheduler-8620 DEBUG Checking readiness of task: 1975 / 0x46620a0
Jul 07 20:46:15-233257 util-scheduler-8620 DEBUG Checking readiness of task: 1974 / 0x4d5e5d8
Jul 07 20:46:15-233451 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-233640 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-233830 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-234020 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-234208 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-234397 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-234585 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-234777 util-scheduler-8620 DEBUG Running task: 1974 / 0x4d5e5d8
Jul 07 20:46:15-234963 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:15-235145 util-8620 DEBUG process_notify is running
Jul 07 20:46:15-235318 util-8620 DEBUG client_notify is running
Jul 07 20:46:15-235544 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:15-235888 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:15-281896 util-scheduler-8620 DEBUG Checking readiness of task: 1975 / 0x46620a0
Jul 07 20:46:15-282211 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-282407 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-282600 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-282792 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-283009 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-283199 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-283389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-283583 util-scheduler-8620 DEBUG Running task: 1975 / 0x46620a0
Jul 07 20:46:15-284003 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:15-284254 util-scheduler-8620 DEBUG Adding task: 1976 / 0x4662248
Jul 07 20:46:15-284522 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-284719 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-284910 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-285105 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-285319 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-285509 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-285699 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-285899 util-scheduler-8620 DEBUG Running task: 1976 / 0x4662248
Jul 07 20:46:15-286090 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:15-286288 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:15-286512 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:15-286772 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:15-287025 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:15-287234 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:15-287417 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:15-287590 cadet-con-8620 DEBUG   ACK 67 (was 66)
Jul 07 20:46:15-287818 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:15-288048 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:15-288256 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:15-288438 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:15-288613 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:15-288819 util-scheduler-8620 DEBUG Adding task: 1977 / 0x46620a0
Jul 07 20:46:15-372085 util-scheduler-8620 DEBUG Checking readiness of task: 1977 / 0x46620a0
Jul 07 20:46:15-372443 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-372640 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-372832 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-373023 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-373245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-373438 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-373629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-373861 util-scheduler-8620 DEBUG Running task: 1977 / 0x46620a0
Jul 07 20:46:15-374282 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:15-374531 util-scheduler-8620 DEBUG Adding task: 1978 / 0x4662248
Jul 07 20:46:15-374806 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-374999 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-375193 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-375384 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-375574 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-375763 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-375951 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-376169 util-scheduler-8620 DEBUG Running task: 1978 / 0x4662248
Jul 07 20:46:15-376361 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:15-376559 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:15-376790 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:15-376998 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:15-377230 util-scheduler-8620 DEBUG Adding task: 1979 / 0x46620a0
Jul 07 20:46:15-377419 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:15-377622 util-scheduler-8620 DEBUG Adding task: 1980 / 0x46620a0
Jul 07 20:46:15-377866 util-scheduler-8620 DEBUG Checking readiness of task: 1980 / 0x46620a0
Jul 07 20:46:15-378060 util-scheduler-8620 DEBUG Checking readiness of task: 1979 / 0x46620a0
Jul 07 20:46:15-378251 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-378441 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-378630 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-378819 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-379008 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-379198 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-379387 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-379579 util-scheduler-8620 DEBUG Running task: 1979 / 0x46620a0
Jul 07 20:46:15-379763 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:15-379941 util-8620 DEBUG process_notify is running
Jul 07 20:46:15-380113 util-8620 DEBUG client_notify is running
Jul 07 20:46:15-380304 util-scheduler-8620 DEBUG Canceling task: 1928 / 0x5e2b838
Jul 07 20:46:15-380528 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:15-380749 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:15-380987 cadet-p2p-8620 DEBUG Checking 0x544ad30 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:15-381434 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:15-381620 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:15-381812 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:15-382082 cadet-p2p-8620 INFO snd {               ACK} ( 67) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:15-382277 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:15-382458 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:15-382645 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:15-382819 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:15-383003 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:15-383178 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:15-383397 cadet-p2p-8620 DEBUG Checking 0x5374038 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:15-383630 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:15-383814 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:15-383989 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:15-384216 cadet-p2p-8620 DEBUG Checking 0x5374038 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:15-384445 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:15-384627 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:15-384800 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:15-384966 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:15-385176 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:15-385416 util-scheduler-8620 DEBUG Adding task: 1981 / 0x5e2b838
Jul 07 20:46:15-385595 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:15-385772 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:15-385970 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:15-386144 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:15-386338 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:15-386577 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:15-386772 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:15-386950 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:15-387182 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:15-387375 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:15-387551 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:15-387783 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:15-387975 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:15-388152 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:15-388349 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:15-388553 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:15-388738 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:15-388942 util-scheduler-8620 DEBUG Adding task: 1982 / 0x5e2b838
Jul 07 20:46:15-389161 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:15-389380 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:15-389581 util-scheduler-8620 DEBUG Adding task: 1983 / 0x46620a0
Jul 07 20:46:15-389782 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:15-390557 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:15-390759 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:15-391019 util-scheduler-8620 DEBUG Checking readiness of task: 1983 / 0x46620a0
Jul 07 20:46:15-391214 util-scheduler-8620 DEBUG Checking readiness of task: 1980 / 0x46620a0
Jul 07 20:46:15-391406 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-391596 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-391787 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-391978 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-392169 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-392358 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-392547 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-392738 util-scheduler-8620 DEBUG Running task: 1983 / 0x46620a0
Jul 07 20:46:15-392922 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:15-393098 util-8620 DEBUG process_notify is running
Jul 07 20:46:15-393289 util-8620 DEBUG client_notify is running
Jul 07 20:46:15-393467 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:15-393661 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:15-393849 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:15-394130 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:15-394338 util-scheduler-8620 DEBUG Running task: 1981 / 0x5e2b838
Jul 07 20:46:15-394534 util-scheduler-8620 DEBUG Canceling task: 1982 / 0x5e2b838
Jul 07 20:46:15-394749 util-scheduler-8620 DEBUG Adding task: 1984 / 0x5e2b838
Jul 07 20:46:15-394966 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:15-395163 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:15-395361 util-scheduler-8620 DEBUG Adding task: 1985 / 0x46620a0
Jul 07 20:46:15-395600 util-scheduler-8620 DEBUG Checking readiness of task: 1985 / 0x46620a0
Jul 07 20:46:15-395794 util-scheduler-8620 DEBUG Checking readiness of task: 1980 / 0x46620a0
Jul 07 20:46:15-395984 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:15-396191 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:15-396381 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:15-396571 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:15-396760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:15-396949 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:15-397137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:15-397352 util-scheduler-8620 DEBUG Running task: 1985 / 0x46620a0
Jul 07 20:46:15-397535 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:15-397710 util-8620 DEBUG process_notify is running
Jul 07 20:46:15-397878 util-8620 DEBUG client_notify is running
Jul 07 20:46:15-398054 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:15-398242 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:15-398430 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:15-398711 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-032307 util-scheduler-8620 DEBUG Checking readiness of task: 1980 / 0x46620a0
Jul 07 20:46:16-032716 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-032920 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-036108 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-036364 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-036564 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-036756 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-036947 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-037145 util-scheduler-8620 DEBUG Running task: 1980 / 0x46620a0
Jul 07 20:46:16-037590 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:16-037849 util-scheduler-8620 DEBUG Adding task: 1986 / 0x4662248
Jul 07 20:46:16-038133 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-038327 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-038520 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-038711 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-038901 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-039092 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-039282 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-039472 util-scheduler-8620 DEBUG Running task: 1986 / 0x4662248
Jul 07 20:46:16-039664 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:16-039864 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:16-040102 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:16-040313 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:16-040521 util-scheduler-8620 DEBUG Adding task: 1987 / 0x46620a0
Jul 07 20:46:16-040711 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-040918 util-scheduler-8620 DEBUG Adding task: 1988 / 0x46620a0
Jul 07 20:46:16-041165 util-scheduler-8620 DEBUG Checking readiness of task: 1988 / 0x46620a0
Jul 07 20:46:16-041382 util-scheduler-8620 DEBUG Checking readiness of task: 1987 / 0x46620a0
Jul 07 20:46:16-041576 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-041768 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-041959 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-042188 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-042380 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-042571 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-042761 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-042954 util-scheduler-8620 DEBUG Running task: 1987 / 0x46620a0
Jul 07 20:46:16-043140 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:16-043319 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-043493 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-043684 util-scheduler-8620 DEBUG Canceling task: 1984 / 0x5e2b838
Jul 07 20:46:16-043912 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:16-044134 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:16-044377 cadet-p2p-8620 DEBUG Checking 0x5374038 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-044614 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-044803 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:16-044986 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:16-045373 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:46:16-045569 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:16-045955 cadet-p2p-8620 DEBUG   payload ID 0
Jul 07 20:46:16-046347 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 88)
Jul 07 20:46:16-046559 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:16-046745 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:16-046938 cadet-con-8620 DEBUG  sent BCK {         ENCRYPTED}
Jul 07 20:46:16-047133 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 2
Jul 07 20:46:16-047369 cadet-con-8620 DEBUG GMC send BCK ACK on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-047563 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:16-047925 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:16-048117 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:16-048327 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:16-048509 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:16-048690 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:16-048898 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:16-049083 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:16-049301 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:16-049486 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:16-049666 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:16-049839 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:16-050074 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:16-050248 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:16-050486 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-050736 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-050923 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:16-051107 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:16-051306 util-scheduler-8620 DEBUG Canceling task: 1305 / 0x5e2cf38
Jul 07 20:46:16-051530 util-scheduler-8620 DEBUG Adding task: 1989 / 0x5e2cf38
Jul 07 20:46:16-051786 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:16-051969 cadet-con-8620 DEBUG !  Q_N- 0x5e2cf70 0
Jul 07 20:46:16-052150 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 0
Jul 07 20:46:16-052327 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:16-052554 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-052790 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-052976 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:16-053153 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:16-053400 cadet-p2p-8620 DEBUG Checking 0x5442430 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-053657 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-053842 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:16-054017 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:16-054249 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-054478 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-054661 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:16-054834 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:16-055052 cadet-p2p-8620 DEBUG Checking 0x5442430 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-055280 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-055461 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:16-055634 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:16-055801 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:16-056009 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:16-056230 util-scheduler-8620 DEBUG Adding task: 1990 / 0x5e2b838
Jul 07 20:46:16-056411 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:16-056591 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:16-056791 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:16-056967 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:16-057143 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:16-057404 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-057600 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:16-057778 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:16-058012 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-058205 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:16-058381 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:16-058580 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:16-058785 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 88 bytes.
Jul 07 20:46:16-058970 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:16-059177 util-scheduler-8620 DEBUG Adding task: 1991 / 0x5e2b838
Jul 07 20:46:16-059399 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:16-059599 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:16-059806 util-scheduler-8620 DEBUG Adding task: 1992 / 0x46620a0
Jul 07 20:46:16-060009 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:16-061502 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-061711 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:16-061978 util-scheduler-8620 DEBUG Checking readiness of task: 1992 / 0x46620a0
Jul 07 20:46:16-062175 util-scheduler-8620 DEBUG Checking readiness of task: 1988 / 0x46620a0
Jul 07 20:46:16-062367 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-062559 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-062749 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-062940 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-063130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-063320 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-063510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-063703 util-scheduler-8620 DEBUG Running task: 1992 / 0x46620a0
Jul 07 20:46:16-063889 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:16-064069 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-064241 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-064441 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:16-064647 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:16-064843 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:16-065163 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-065421 util-scheduler-8620 DEBUG Running task: 1990 / 0x5e2b838
Jul 07 20:46:16-065625 util-scheduler-8620 DEBUG Canceling task: 1991 / 0x5e2b838
Jul 07 20:46:16-065861 util-scheduler-8620 DEBUG Adding task: 1993 / 0x5e2b838
Jul 07 20:46:16-066104 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:16-066529 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:16-066750 util-scheduler-8620 DEBUG Adding task: 1994 / 0x46620a0
Jul 07 20:46:16-067026 util-scheduler-8620 DEBUG Checking readiness of task: 1994 / 0x46620a0
Jul 07 20:46:16-067233 util-scheduler-8620 DEBUG Checking readiness of task: 1988 / 0x46620a0
Jul 07 20:46:16-067430 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-067629 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-067830 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-068024 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-068219 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-068416 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-068614 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-068816 util-scheduler-8620 DEBUG Running task: 1988 / 0x46620a0
Jul 07 20:46:16-069283 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:16-069538 util-scheduler-8620 DEBUG Adding task: 1995 / 0x4662248
Jul 07 20:46:16-069764 util-scheduler-8620 DEBUG Running task: 1994 / 0x46620a0
Jul 07 20:46:16-069956 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:16-070140 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-070314 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-070498 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:16-070703 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:16-070897 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:16-071217 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-071486 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-071681 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-071874 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-072065 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-072256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-072446 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-072636 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-072828 util-scheduler-8620 DEBUG Running task: 1995 / 0x4662248
Jul 07 20:46:16-073033 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:16-073253 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:16-073480 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:16-073665 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-073875 util-scheduler-8620 DEBUG Adding task: 1996 / 0x46620a0
Jul 07 20:46:16-074118 util-scheduler-8620 DEBUG Checking readiness of task: 1996 / 0x46620a0
Jul 07 20:46:16-074312 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-074531 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-074723 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-074915 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-075105 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-075295 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-075485 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-075676 util-scheduler-8620 DEBUG Running task: 1996 / 0x46620a0
Jul 07 20:46:16-076077 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:16-076306 util-scheduler-8620 DEBUG Adding task: 1997 / 0x4662248
Jul 07 20:46:16-076556 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-076749 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-076941 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-077132 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-077357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-077547 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-077738 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-077928 util-scheduler-8620 DEBUG Running task: 1997 / 0x4662248
Jul 07 20:46:16-078117 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:16-078308 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:16-078519 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:16-078720 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:16-078919 util-scheduler-8620 DEBUG Adding task: 1998 / 0x46620a0
Jul 07 20:46:16-079515 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-079716 util-scheduler-8620 DEBUG Adding task: 1999 / 0x46620a0
Jul 07 20:46:16-079959 util-scheduler-8620 DEBUG Checking readiness of task: 1999 / 0x46620a0
Jul 07 20:46:16-080153 util-scheduler-8620 DEBUG Checking readiness of task: 1998 / 0x46620a0
Jul 07 20:46:16-080346 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-080538 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-080729 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-080920 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-081110 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-081323 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-081516 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-081714 util-scheduler-8620 DEBUG Running task: 1998 / 0x46620a0
Jul 07 20:46:16-081904 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:16-082086 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-082260 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-082453 util-scheduler-8620 DEBUG Canceling task: 1993 / 0x5e2b838
Jul 07 20:46:16-082686 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:16-082909 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:16-083151 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-083392 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-083579 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:16-083760 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:16-083987 cadet-p2p-8620 DEBUG Checking 0x5442430 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-084222 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-084432 cadet-con-8620 DEBUG  last ack recv: 67, last pid sent: 4
Jul 07 20:46:16-084612 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:16-084842 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:16-085023 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:16-085223 cadet-p2p-8620 DEBUG   payload ID 5
Jul 07 20:46:16-085513 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 88)
Jul 07 20:46:16-086113 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:16-086304 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:16-086498 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:16-086694 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:16-086925 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-087102 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:16-087275 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:16-087449 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:16-087647 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:16-087823 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:16-087998 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:16-088198 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:16-088378 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:16-088561 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:16-088743 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:16-088920 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:16-089091 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:16-089328 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:16-089501 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:16-089732 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-089976 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-090160 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:16-090342 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:16-090533 util-scheduler-8620 DEBUG Canceling task: 1924 / 0x5e31aa0
Jul 07 20:46:16-090750 util-scheduler-8620 DEBUG Adding task: 2000 / 0x5e31aa0
Jul 07 20:46:16-091001 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:16-091181 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:46:16-091359 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 5
Jul 07 20:46:16-091532 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:16-091755 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-091985 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-092167 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:16-092340 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:16-092571 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:16-092800 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-092982 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 0
Jul 07 20:46:16-093155 cadet-con-8620 DEBUG  not sendable
Jul 07 20:46:16-093346 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:16-093547 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:16-093723 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:16-093897 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:16-094135 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-094330 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:16-094507 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:16-094706 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:16-094923 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 88 bytes.
Jul 07 20:46:16-095107 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:16-095307 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:16-095499 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:16-097132 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-232541 util-scheduler-8620 DEBUG Checking readiness of task: 1999 / 0x46620a0
Jul 07 20:46:16-232917 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-233113 util-scheduler-8620 DEBUG Checking readiness of task: 1821 / 0x4663d68
Jul 07 20:46:16-233330 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-233522 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-233713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-233902 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-234091 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-234286 util-scheduler-8620 DEBUG Running task: 1821 / 0x4663d68
Jul 07 20:46:16-234708 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:46:16-234965 util-scheduler-8620 DEBUG Adding task: 2001 / 0x4663f10
Jul 07 20:46:16-235242 util-scheduler-8620 DEBUG Checking readiness of task: 1999 / 0x46620a0
Jul 07 20:46:16-235433 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-235623 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-235811 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-236000 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-236189 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-236377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-236569 util-scheduler-8620 DEBUG Running task: 2001 / 0x4663f10
Jul 07 20:46:16-236761 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:46:16-236958 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-237169 util-scheduler-8620 DEBUG Adding task: 2002 / 0x4663d68
Jul 07 20:46:16-237377 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:46:16-237608 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `KNAS' with quota 35486
Jul 07 20:46:16-237800 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 bandwidth changed to 35486 Bps
Jul 07 20:46:16-238060 util-bandwidth-8620 DEBUG Tracker 0x4d6c380 updated, have 24114 Bps, last update was 23 s ago
Jul 07 20:46:16-238293 util-scheduler-8620 DEBUG Adding task: 2003 / 0x4d6c380
Jul 07 20:46:16-293383 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-293740 util-scheduler-8620 DEBUG Checking readiness of task: 1999 / 0x46620a0
Jul 07 20:46:16-293942 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-294137 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-294330 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-294522 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-294713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-294901 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-295095 util-scheduler-8620 DEBUG Running task: 1999 / 0x46620a0
Jul 07 20:46:16-295512 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:16-295764 util-scheduler-8620 DEBUG Adding task: 2004 / 0x4662248
Jul 07 20:46:16-296037 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-296228 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-296449 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-296645 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-296833 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-297022 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-297232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-297423 util-scheduler-8620 DEBUG Running task: 2004 / 0x4662248
Jul 07 20:46:16-297613 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:16-297811 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:16-298037 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:16-298303 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:16-298557 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-298765 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-298951 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:16-299123 cadet-con-8620 DEBUG   ACK 68 (was 67)
Jul 07 20:46:16-299352 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-299580 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-299785 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-300238 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:16-300423 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-300636 util-scheduler-8620 DEBUG Adding task: 2005 / 0x46620a0
Jul 07 20:46:16-490773 util-scheduler-8620 DEBUG Checking readiness of task: 2005 / 0x46620a0
Jul 07 20:46:16-491147 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-491347 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-491540 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-491732 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-491923 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-492114 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-492303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-492499 util-scheduler-8620 DEBUG Running task: 2005 / 0x46620a0
Jul 07 20:46:16-492962 util-8620 DEBUG receive_ready read 288/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:16-493241 util-scheduler-8620 DEBUG Adding task: 2006 / 0x4662248
Jul 07 20:46:16-493519 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-493712 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-493902 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-494092 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-494281 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-494470 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-494659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-494848 util-scheduler-8620 DEBUG Running task: 2006 / 0x4662248
Jul 07 20:46:16-495038 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:16-495239 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:16-495469 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `D3TJ'
Jul 07 20:46:16-495730 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:16-495973 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-496228 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-496437 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:16-496687 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-496934 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-497127 cadet-con-8620 DEBUG  PID 4 (expected 4+)
Jul 07 20:46:16-497338 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:16-497544 util-scheduler-8620 DEBUG Canceling task: 1967 / 0x5e31aa0
Jul 07 20:46:16-497780 util-scheduler-8620 DEBUG Adding task: 2007 / 0x5e31aa0
Jul 07 20:46:16-497967 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:16-498242 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:16-498471 util-scheduler-8620 DEBUG Adding task: 2008 / 0x4d5e5d8
Jul 07 20:46:16-498662 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:16-498833 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:16-502723 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:16-503613 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:16-503831 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:16-507258 cadet-tun-8620 INFO <=== {          DATA_ACK} on D3TJ
Jul 07 20:46:16-507461 cadet-chn-8620 INFO <=== FWD ACK 0
Jul 07 20:46:16-507642 cadet-chn-8620 DEBUG   id 0
Jul 07 20:46:16-507817 cadet-chn-8620 DEBUG !!! Freeing 0
Jul 07 20:46:16-508069 cadet-chn-8620 INFO !!!  took 2605178 µs, new delay 2605178 µs
Jul 07 20:46:16-508250 cadet-chn-8620 DEBUG  COPYFREE 0x5157240
Jul 07 20:46:16-508430 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:16-508597 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:46:16-508796 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:16-508974 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:16-509156 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:16-509358 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:16-509533 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:16-509702 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:16-509919 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:16-510089 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:16-510324 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-510567 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:16-510750 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:16-510927 cadet-chn-8620 DEBUG  buffer space 22, allowing
Jul 07 20:46:16-511151 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:16-511325 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:16-511506 util-scheduler-8620 DEBUG Canceling task: 1923 / 0x5e33a48
Jul 07 20:46:16-511749 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-511922 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:16-512096 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:16-512266 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:16-512484 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-512661 cadet-con-8620 DEBUG  ACK 68
Jul 07 20:46:16-512839 cadet-con-8620 DEBUG  last pid 4, last ack 67, qmax 11, q 0
Jul 07 20:46:16-513107 cadet-con-8620 INFO --> {               ACK} ( 68) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:16-513316 cadet-con-8620 DEBUG  ack 68
Jul 07 20:46:16-513493 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:16-513727 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-513938 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-514242 cadet-p2p-8620 INFO que {               ACK} ( 68) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:16-514444 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:16-514671 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-514854 cadet-con-8620 DEBUG  last ack recv: 68, last pid sent: 5
Jul 07 20:46:16-515030 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:16-515236 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 40 bytes
Jul 07 20:46:16-515453 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `D3TJ'
Jul 07 20:46:16-515719 util-scheduler-8620 DEBUG Adding task: 2009 / 0x5e2b838
Jul 07 20:46:16-515906 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:16-516155 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:16-516333 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:16-516510 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:16-516758 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-516942 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:46:16-517117 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:16-517376 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-517568 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:16-517744 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:16-517940 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:16-518151 util-scheduler-8620 DEBUG Adding task: 2010 / 0x4662248
Jul 07 20:46:16-518425 util-scheduler-8620 DEBUG Checking readiness of task: 2008 / 0x4d5e5d8
Jul 07 20:46:16-518622 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-518813 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-519002 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-519191 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-519378 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-519566 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-519753 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-519946 util-scheduler-8620 DEBUG Running task: 2008 / 0x4d5e5d8
Jul 07 20:46:16-520131 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:16-520309 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-520482 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-520716 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:16-521023 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:16-521253 util-scheduler-8620 DEBUG Running task: 2010 / 0x4662248
Jul 07 20:46:16-521446 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:16-521644 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:16-521859 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:16-522107 cadet-con-8620 INFO <-- {               ACK} on connection BFARXZN9 from D3TJ
Jul 07 20:46:16-522352 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:16-522558 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:16-523127 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:16-523341 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-524540 cadet-con-8620 DEBUG   BCK ACK
Jul 07 20:46:16-525090 cadet-con-8620 DEBUG   ACK 64 (was 0)
Jul 07 20:46:16-525353 cadet-con-8620 DEBUG connection_unlock_queue BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:16-525692 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:16-525903 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-526086 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:16-526287 util-scheduler-8620 DEBUG Adding task: 2011 / 0x4662248
Jul 07 20:46:16-526483 util-scheduler-8620 DEBUG Running task: 2009 / 0x5e2b838
Jul 07 20:46:16-526693 util-scheduler-8620 DEBUG Adding task: 2012 / 0x5e2b838
Jul 07 20:46:16-526925 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:16-527130 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:16-527345 util-scheduler-8620 DEBUG Adding task: 2013 / 0x46620a0
Jul 07 20:46:16-527605 util-scheduler-8620 DEBUG Checking readiness of task: 2013 / 0x46620a0
Jul 07 20:46:16-527803 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:16-528033 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:16-528230 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:16-528424 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:16-528619 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:16-528817 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:16-529011 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:16-529238 util-scheduler-8620 DEBUG Running task: 2013 / 0x46620a0
Jul 07 20:46:16-529430 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:16-529614 util-8620 DEBUG process_notify is running
Jul 07 20:46:16-529791 util-8620 DEBUG client_notify is running
Jul 07 20:46:16-529977 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:16-530185 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:16-530385 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:16-530720 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:16-530940 util-scheduler-8620 DEBUG Running task: 2011 / 0x4662248
Jul 07 20:46:16-531136 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:16-531338 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:16-531573 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:16-531835 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:16-532092 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-532304 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-532493 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:16-532670 cadet-con-8620 DEBUG   ACK 69 (was 68)
Jul 07 20:46:16-532901 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:16-533256 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:16-533475 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:16-533657 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:16-533834 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:16-534050 util-scheduler-8620 DEBUG Adding task: 2014 / 0x46620a0
Jul 07 20:46:17-841822 util-scheduler-8620 DEBUG Checking readiness of task: 2014 / 0x46620a0
Jul 07 20:46:17-842217 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:17-842426 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:17-842625 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:17-842822 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:17-843020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:17-843216 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:17-843412 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:17-843612 util-scheduler-8620 DEBUG Running task: 2003 / 0x4d6c380
Jul 07 20:46:18-617540 util-scheduler-8620 DEBUG Checking readiness of task: 2014 / 0x46620a0
Jul 07 20:46:18-617963 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-618186 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-618393 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-618587 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-618782 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-618979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-619185 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-619425 util-scheduler-8620 DEBUG Running task: 2014 / 0x46620a0
Jul 07 20:46:18-619857 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:18-620132 util-scheduler-8620 DEBUG Adding task: 2015 / 0x4662248
Jul 07 20:46:18-620416 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-620609 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-620800 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-620990 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-621179 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-621397 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-621589 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-621791 util-scheduler-8620 DEBUG Running task: 2015 / 0x4662248
Jul 07 20:46:18-621981 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:18-622182 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:18-622425 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:18-622641 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-622852 util-scheduler-8620 DEBUG Adding task: 2016 / 0x46620a0
Jul 07 20:46:18-623043 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:18-623250 util-scheduler-8620 DEBUG Adding task: 2017 / 0x46620a0
Jul 07 20:46:18-623509 util-scheduler-8620 DEBUG Checking readiness of task: 2017 / 0x46620a0
Jul 07 20:46:18-623704 util-scheduler-8620 DEBUG Checking readiness of task: 2016 / 0x46620a0
Jul 07 20:46:18-623897 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-624094 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-624285 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-624482 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-624673 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-624865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-625072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-625291 util-scheduler-8620 DEBUG Running task: 2016 / 0x46620a0
Jul 07 20:46:18-625482 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-625664 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-625839 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-626031 util-scheduler-8620 DEBUG Canceling task: 1963 / 0x4d6ff98
Jul 07 20:46:18-626264 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:18-626485 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:18-626748 cadet-p2p-8620 DEBUG Checking 0x545ff58 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-626982 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:18-627159 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:18-627351 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:18-627621 cadet-p2p-8620 INFO snd {               ACK} ( 73) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:18-627815 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:18-627994 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:18-628181 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:18-628356 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:18-628555 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:18-628728 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:18-628949 cadet-p2p-8620 DEBUG Checking 0x5419038 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-629180 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-629385 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:18-629585 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-629813 cadet-p2p-8620 DEBUG Checking 0x5419038 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-630043 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-630237 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:18-630410 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-630588 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:18-630793 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `V8XX'
Jul 07 20:46:18-631013 util-scheduler-8620 DEBUG Adding task: 2018 / 0x4d6ff98
Jul 07 20:46:18-631191 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:18-631366 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:18-631563 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:18-631738 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:18-631926 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:18-632163 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:18-632358 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:18-632535 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:18-632766 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:18-632958 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:18-633134 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:18-633354 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:18-633572 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:18-633755 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:18-633961 util-scheduler-8620 DEBUG Adding task: 2019 / 0x4d6ff98
Jul 07 20:46:18-634180 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:18-634377 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-634579 util-scheduler-8620 DEBUG Adding task: 2020 / 0x46620a0
Jul 07 20:46:18-634781 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:18-635535 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-635738 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:18-635995 util-scheduler-8620 DEBUG Checking readiness of task: 2020 / 0x46620a0
Jul 07 20:46:18-636189 util-scheduler-8620 DEBUG Checking readiness of task: 2017 / 0x46620a0
Jul 07 20:46:18-636379 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-636597 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-636791 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-636994 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-637184 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-637395 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-637584 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-637774 util-scheduler-8620 DEBUG Running task: 2020 / 0x46620a0
Jul 07 20:46:18-637958 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-638133 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-638303 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-638482 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:18-638717 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:18-638908 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:18-639200 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-639419 util-scheduler-8620 DEBUG Running task: 2018 / 0x4d6ff98
Jul 07 20:46:18-639618 util-scheduler-8620 DEBUG Canceling task: 2019 / 0x4d6ff98
Jul 07 20:46:18-639884 util-scheduler-8620 DEBUG Adding task: 2021 / 0x4d6ff98
Jul 07 20:46:18-640114 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:18-640321 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-640538 util-scheduler-8620 DEBUG Adding task: 2022 / 0x46620a0
Jul 07 20:46:18-640803 util-scheduler-8620 DEBUG Checking readiness of task: 2022 / 0x46620a0
Jul 07 20:46:18-641005 util-scheduler-8620 DEBUG Checking readiness of task: 2017 / 0x46620a0
Jul 07 20:46:18-641227 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-641427 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-641625 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-641824 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-642019 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-642218 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-642411 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-642607 util-scheduler-8620 DEBUG Running task: 2022 / 0x46620a0
Jul 07 20:46:18-642798 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-642983 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-643158 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-643344 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:18-643550 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:18-643746 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:18-644089 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-748210 util-scheduler-8620 DEBUG Checking readiness of task: 2017 / 0x46620a0
Jul 07 20:46:18-748601 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-748799 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-748993 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-749186 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-749405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-749596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-749786 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-749982 util-scheduler-8620 DEBUG Running task: 2017 / 0x46620a0
Jul 07 20:46:18-750410 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:18-750665 util-scheduler-8620 DEBUG Adding task: 2023 / 0x4662248
Jul 07 20:46:18-750943 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-751135 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-751326 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-751518 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-751709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-751899 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-752100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-752290 util-scheduler-8620 DEBUG Running task: 2023 / 0x4662248
Jul 07 20:46:18-752481 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:18-752681 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:18-752914 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:18-753120 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-753354 util-scheduler-8620 DEBUG Adding task: 2024 / 0x46620a0
Jul 07 20:46:18-753572 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:18-753778 util-scheduler-8620 DEBUG Adding task: 2025 / 0x46620a0
Jul 07 20:46:18-754025 util-scheduler-8620 DEBUG Checking readiness of task: 2025 / 0x46620a0
Jul 07 20:46:18-754217 util-scheduler-8620 DEBUG Checking readiness of task: 2024 / 0x46620a0
Jul 07 20:46:18-754412 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-754603 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-754794 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-754984 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-755174 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-755374 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-755563 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-755754 util-scheduler-8620 DEBUG Running task: 2024 / 0x46620a0
Jul 07 20:46:18-755940 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-756118 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-756289 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-756481 util-scheduler-8620 DEBUG Canceling task: 2021 / 0x4d6ff98
Jul 07 20:46:18-756705 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 96 bytes.
Jul 07 20:46:18-756925 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:18-757180 cadet-p2p-8620 DEBUG Checking 0x5419038 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-757438 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-757620 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:18-757795 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-758016 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:18-758194 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:46:18-758368 cadet-p2p-8620 DEBUG   payload ID 8
Jul 07 20:46:18-758665 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 96)
Jul 07 20:46:18-758861 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:18-759041 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:18-759229 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:18-759403 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:18-759571 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:18-759759 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:18-759935 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:46:18-760163 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 769 ms
Jul 07 20:46:18-760335 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:18-760539 cadet-chn-8620 DEBUG !! using delay 3078216 µs
Jul 07 20:46:18-760735 util-scheduler-8620 DEBUG Adding task: 2026 / 0x4d65218
Jul 07 20:46:18-760937 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:18-761165 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:18-761365 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:18-761538 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:18-761709 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:18-761917 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:18-762093 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:18-762266 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:18-762466 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:18-762643 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:18-762824 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:18-763004 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:18-763180 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:18-763372 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:18-763589 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:18-763780 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:18-764014 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:18-764199 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:18-764379 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:18-764565 util-scheduler-8620 DEBUG Canceling task: 1934 / 0x4d707d0
Jul 07 20:46:18-764777 util-scheduler-8620 DEBUG Adding task: 2027 / 0x4d707d0
Jul 07 20:46:18-765022 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:18-765210 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 1
Jul 07 20:46:18-765415 cadet-con-8620 DEBUG !   accounting pid 8
Jul 07 20:46:18-765587 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:18-765819 cadet-p2p-8620 DEBUG Checking 0x5422758 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-766051 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-766232 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:18-766405 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-766632 cadet-p2p-8620 DEBUG Checking 0x5422758 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-766861 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-767041 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:18-767214 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-767383 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:18-767589 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:18-767801 util-scheduler-8620 DEBUG Adding task: 2028 / 0x4d6ff98
Jul 07 20:46:18-767980 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:18-768157 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:46:18-768355 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:18-768530 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:18-768704 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:18-768943 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:18-769138 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:18-769354 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:18-769554 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:18-769760 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 96 bytes.
Jul 07 20:46:18-769943 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:46:18-770147 util-scheduler-8620 DEBUG Adding task: 2029 / 0x4d6ff98
Jul 07 20:46:18-770368 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:18-770563 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-770765 util-scheduler-8620 DEBUG Adding task: 2030 / 0x46620a0
Jul 07 20:46:18-770965 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:46:18-774168 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-774385 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:18-774644 util-scheduler-8620 DEBUG Checking readiness of task: 2030 / 0x46620a0
Jul 07 20:46:18-774840 util-scheduler-8620 DEBUG Checking readiness of task: 2025 / 0x46620a0
Jul 07 20:46:18-775107 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-775300 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-775491 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-775682 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-775872 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-776061 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-776251 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-776443 util-scheduler-8620 DEBUG Running task: 2030 / 0x46620a0
Jul 07 20:46:18-776628 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-776828 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-777000 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-777180 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:18-777405 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:18-777593 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:18-777891 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-778099 util-scheduler-8620 DEBUG Running task: 2028 / 0x4d6ff98
Jul 07 20:46:18-778294 util-scheduler-8620 DEBUG Canceling task: 2029 / 0x4d6ff98
Jul 07 20:46:18-778511 util-scheduler-8620 DEBUG Adding task: 2031 / 0x4d6ff98
Jul 07 20:46:18-778731 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:18-778927 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-779126 util-scheduler-8620 DEBUG Adding task: 2032 / 0x46620a0
Jul 07 20:46:18-779367 util-scheduler-8620 DEBUG Checking readiness of task: 2032 / 0x46620a0
Jul 07 20:46:18-779559 util-scheduler-8620 DEBUG Checking readiness of task: 2025 / 0x46620a0
Jul 07 20:46:18-779750 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-779940 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-780130 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-780320 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-780509 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-780698 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-780886 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-781076 util-scheduler-8620 DEBUG Running task: 2025 / 0x46620a0
Jul 07 20:46:18-781514 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:18-781742 util-scheduler-8620 DEBUG Adding task: 2033 / 0x4662248
Jul 07 20:46:18-781951 util-scheduler-8620 DEBUG Running task: 2032 / 0x46620a0
Jul 07 20:46:18-782137 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-782312 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-782480 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-782656 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:18-782845 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:18-783031 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:18-783339 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:18-783587 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-783779 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-783970 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-784160 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-784349 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-784539 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-784727 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-784917 util-scheduler-8620 DEBUG Running task: 2033 / 0x4662248
Jul 07 20:46:18-785105 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:18-785323 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:18-785537 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:18-785718 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:18-785920 util-scheduler-8620 DEBUG Adding task: 2034 / 0x46620a0
Jul 07 20:46:18-786177 util-scheduler-8620 DEBUG Checking readiness of task: 2034 / 0x46620a0
Jul 07 20:46:18-786370 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-786561 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-786751 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-786941 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-787130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-787322 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-787510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-787700 util-scheduler-8620 DEBUG Running task: 2034 / 0x46620a0
Jul 07 20:46:18-788097 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:18-788319 util-scheduler-8620 DEBUG Adding task: 2035 / 0x4662248
Jul 07 20:46:18-788564 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-788757 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-789155 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-789443 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-789638 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-789829 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-790020 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-790783 util-scheduler-8620 DEBUG Running task: 2035 / 0x4662248
Jul 07 20:46:18-790978 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:18-791172 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:18-791386 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:18-791583 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:18-791781 util-scheduler-8620 DEBUG Adding task: 2036 / 0x46620a0
Jul 07 20:46:18-791965 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:18-792162 util-scheduler-8620 DEBUG Adding task: 2037 / 0x46620a0
Jul 07 20:46:18-792404 util-scheduler-8620 DEBUG Checking readiness of task: 2037 / 0x46620a0
Jul 07 20:46:18-792596 util-scheduler-8620 DEBUG Checking readiness of task: 2036 / 0x46620a0
Jul 07 20:46:18-792787 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:18-792978 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:18-793168 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:18-793383 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:18-793573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:18-793763 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:18-793951 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:18-794142 util-scheduler-8620 DEBUG Running task: 2036 / 0x46620a0
Jul 07 20:46:18-794326 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:18-794502 util-8620 DEBUG process_notify is running
Jul 07 20:46:18-794671 util-8620 DEBUG client_notify is running
Jul 07 20:46:18-794855 util-scheduler-8620 DEBUG Canceling task: 2031 / 0x4d6ff98
Jul 07 20:46:18-795073 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:46:18-795290 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:18-795523 cadet-p2p-8620 DEBUG Checking 0x5422758 towards CMHCKRVP (->V8XX)
Jul 07 20:46:18-795752 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:18-795933 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:18-796127 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:18-796349 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:18-796525 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:18-796698 cadet-p2p-8620 DEBUG   payload ID 9
Jul 07 20:46:18-796979 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 100)
Jul 07 20:46:18-797172 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:18-797378 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:18-797565 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:18-797738 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:18-797905 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:18-798091 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:18-798278 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:18-798470 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:18-798696 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:18-798870 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:18-799041 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:18-799211 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:18-799406 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:18-799580 cadet-tun-8620 DEBUG  head: 0x4d65198
Jul 07 20:46:18-799753 cadet-tun-8620 DEBUG  head ch: 0x4d650a8
Jul 07 20:46:18-799951 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:18-800127 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:18-800309 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:18-800488 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:18-800663 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:18-800832 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:18-801045 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:18-801238 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:18-801471 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:18-801655 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:18-801831 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:18-802015 util-scheduler-8620 DEBUG Canceling task: 2027 / 0x4d707d0
Jul 07 20:46:18-802227 util-scheduler-8620 DEBUG Adding task: 2038 / 0x4d707d0
Jul 07 20:46:18-802471 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:18-802648 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:18-802826 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 9
Jul 07 20:46:18-802998 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:18-803178 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:18-803388 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:18-803565 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:18-803739 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:18-803937 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:18-804140 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:46:18-804322 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:18-804499 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:18-804687 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:18-806226 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-018048 util-scheduler-8620 DEBUG Checking readiness of task: 2037 / 0x46620a0
Jul 07 20:46:19-018432 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-018631 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-018826 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-019020 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-019213 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-019435 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-019628 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-019826 util-scheduler-8620 DEBUG Running task: 2037 / 0x46620a0
Jul 07 20:46:19-020251 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:19-020511 util-scheduler-8620 DEBUG Adding task: 2039 / 0x4662248
Jul 07 20:46:19-020792 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-020987 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-021179 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-021400 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-021592 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-021784 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-021974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-022166 util-scheduler-8620 DEBUG Running task: 2039 / 0x4662248
Jul 07 20:46:19-022359 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:19-022561 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:19-022791 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:19-023055 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:19-023299 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:19-023529 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-023739 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:19-023987 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-024198 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-024392 cadet-con-8620 DEBUG  PID 10 (expected 10+)
Jul 07 20:46:19-024575 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:19-024768 util-scheduler-8620 DEBUG Canceling task: 1973 / 0x4d707d0
Jul 07 20:46:19-024994 util-scheduler-8620 DEBUG Adding task: 2040 / 0x4d707d0
Jul 07 20:46:19-025176 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:19-025554 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-025777 util-scheduler-8620 DEBUG Adding task: 2041 / 0x4d5e5d8
Jul 07 20:46:19-025965 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:19-026134 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:19-029880 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:19-031226 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:19-031439 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:19-035122 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:19-035351 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:19-035639 cadet-chn-8620 INFO <=== DATA 1 BCK on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-035891 cadet-chn-8620 WARNING MID 1 on channel V8XX:19 gid:40000000 (80000002 / 0) not expected (window: 2 - 65). Dropping!
Jul 07 20:46:19-036085 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:46:19-036268 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:46:19-036516 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-036733 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:19-036933 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:19-037114 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-037328 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:19-037512 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-037690 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-037861 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-038079 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-038282 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-038521 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-038708 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-039005 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:19-039177 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-039364 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:19-042411 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:19-043064 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:19-043243 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-043433 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:19-046623 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:19-046870 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:19-047054 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:19-047276 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:19-047488 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:19-047765 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (100 bytes)
Jul 07 20:46:19-047966 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:19-048145 cadet-con-8620 DEBUG last pid sent 9
Jul 07 20:46:19-048320 cadet-con-8620 DEBUG      ack recv 71
Jul 07 20:46:19-048495 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:19-048673 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:19-048907 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-049115 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-049453 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 100)
Jul 07 20:46:19-049657 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:19-049883 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:19-050068 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 9
Jul 07 20:46:19-050243 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-050450 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:46:19-050667 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:46:19-050894 util-scheduler-8620 DEBUG Adding task: 2042 / 0x4d6ff98
Jul 07 20:46:19-051076 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:19-051282 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:19-051459 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:19-051636 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:19-051875 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-052072 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:19-052251 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-052452 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:19-052630 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:19-052855 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:19-053032 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:19-053226 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:19-053401 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:19-053623 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:19-053804 cadet-con-8620 DEBUG  ACK 74
Jul 07 20:46:19-053984 cadet-con-8620 DEBUG  last pid 10, last ack 73, qmax 11, q 0
Jul 07 20:46:19-054249 cadet-con-8620 INFO --> {               ACK} ( 74) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:19-054440 cadet-con-8620 DEBUG  ack 74
Jul 07 20:46:19-054619 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:19-054853 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-055060 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-055352 cadet-p2p-8620 INFO que {               ACK} ( 74) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:19-055575 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:19-055800 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:19-055984 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 9
Jul 07 20:46:19-056160 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-056361 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:19-056564 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:19-056741 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:19-056917 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:19-057154 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-057367 cadet-p2p-8620 DEBUG QQQ    payload , 74
Jul 07 20:46:19-057545 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-057781 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-057977 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:19-058156 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-058355 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:19-059104 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:19-059333 util-scheduler-8620 DEBUG Adding task: 2043 / 0x46620a0
Jul 07 20:46:19-059612 util-scheduler-8620 DEBUG Checking readiness of task: 2043 / 0x46620a0
Jul 07 20:46:19-059813 util-scheduler-8620 DEBUG Checking readiness of task: 2041 / 0x4d5e5d8
Jul 07 20:46:19-060008 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-060200 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-060392 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-060584 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-060837 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-061031 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-061247 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-061445 util-scheduler-8620 DEBUG Running task: 2041 / 0x4d5e5d8
Jul 07 20:46:19-061633 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-061815 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-061989 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-062240 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-062450 util-scheduler-8620 DEBUG Adding task: 2044 / 0x4d5e5d8
Jul 07 20:46:19-062656 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:19-062956 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-063160 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:19-063359 util-scheduler-8620 DEBUG Running task: 2042 / 0x4d6ff98
Jul 07 20:46:19-063570 util-scheduler-8620 DEBUG Adding task: 2045 / 0x4d6ff98
Jul 07 20:46:19-063795 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:19-063994 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-064193 util-scheduler-8620 DEBUG Adding task: 2046 / 0x46620a0
Jul 07 20:46:19-064439 util-scheduler-8620 DEBUG Checking readiness of task: 2046 / 0x46620a0
Jul 07 20:46:19-064636 util-scheduler-8620 DEBUG Checking readiness of task: 2044 / 0x4d5e5d8
Jul 07 20:46:19-064830 util-scheduler-8620 DEBUG Checking readiness of task: 2043 / 0x46620a0
Jul 07 20:46:19-065023 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-065237 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-065432 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-065624 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-065815 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-066005 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-066217 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-066411 util-scheduler-8620 DEBUG Running task: 2044 / 0x4d5e5d8
Jul 07 20:46:19-066598 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-066775 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-066947 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-067336 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:19-067628 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-067843 util-scheduler-8620 DEBUG Running task: 2046 / 0x46620a0
Jul 07 20:46:19-068030 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-068208 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-068379 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-068559 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:19-068757 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:19-068948 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:19-069306 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-389142 util-scheduler-8620 DEBUG Checking readiness of task: 2043 / 0x46620a0
Jul 07 20:46:19-389556 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-389754 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-389948 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-390139 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-390329 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-390520 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-390710 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-390905 util-scheduler-8620 DEBUG Running task: 2043 / 0x46620a0
Jul 07 20:46:19-391347 util-8620 DEBUG receive_ready read 33412/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:19-391735 util-scheduler-8620 DEBUG Adding task: 2047 / 0x4662248
Jul 07 20:46:19-392014 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-392208 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-392398 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-392589 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-392778 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-392966 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-393155 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-393369 util-scheduler-8620 DEBUG Running task: 2047 / 0x4662248
Jul 07 20:46:19-393567 util-8620 DEBUG Received message of type 70 and size 33412 from core service.
Jul 07 20:46:19-393968 core-api-8620 DEBUG Processing message of type 70 and size 33412 from core service
Jul 07 20:46:19-394201 core-api-8620 DEBUG Received message of type 280 and size 33376 from peer `D3TJ'
Jul 07 20:46:19-394465 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:19-394708 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-394936 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:19-395145 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:19-395390 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:19-395602 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:19-395790 cadet-con-8620 DEBUG  PID 5 (expected 5+)
Jul 07 20:46:19-395971 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:19-396192 util-scheduler-8620 DEBUG Canceling task: 2007 / 0x5e31aa0
Jul 07 20:46:19-396416 util-scheduler-8620 DEBUG Adding task: 2048 / 0x5e31aa0
Jul 07 20:46:19-396596 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:19-396854 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-397070 util-scheduler-8620 DEBUG Adding task: 2049 / 0x4d5e5d8
Jul 07 20:46:19-397403 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:19-397577 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:19-401727 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:19-419273 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:19-419477 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:19-468489 cadet-tun-8620 INFO <=== {              DATA} on D3TJ
Jul 07 20:46:19-468719 cadet-tun-8620 DEBUG  payload of type 582 (UNKNOWN TYPE)
Jul 07 20:46:19-469009 cadet-chn-8620 INFO <=== DATA 0 BCK on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-469222 cadet-chn-8620 DEBUG RECV 0 (33296)
Jul 07 20:46:19-469399 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:46:19-469891 util-server-nc-8620 DEBUG Adding message of type 285 and size 33292 to pending queue (which has 1 entries)
Jul 07 20:46:19-470220 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:19-470430 util-scheduler-8620 DEBUG Adding task: 2050 / 0x4d5c418
Jul 07 20:46:19-470622 cadet-chn-8620 INFO ===> DATA_ACK for 0
Jul 07 20:46:19-470800 cadet-chn-8620 DEBUG  final futures: 0
Jul 07 20:46:19-471047 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-471263 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:19-471462 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:19-471642 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-471824 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:19-472006 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-472184 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-472354 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-472568 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-472740 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-472975 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-473245 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-473431 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-473725 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:19-473897 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-474080 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:19-477168 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:19-478399 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:19-478579 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-478766 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:19-481898 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:19-482134 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:19-482315 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:19-482537 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:19-482714 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:19-485028 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-485258 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:19-485541 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (100 bytes)
Jul 07 20:46:19-485744 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:19-485921 cadet-con-8620 DEBUG last pid sent 5
Jul 07 20:46:19-486095 cadet-con-8620 DEBUG      ack recv 69
Jul 07 20:46:19-486266 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:19-486446 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:19-486679 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:19-486886 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:19-487228 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 100)
Jul 07 20:46:19-487433 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:19-487658 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-487841 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:19-488015 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-488217 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:19-488418 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:19-488593 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:19-488767 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:19-489007 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-489211 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:46:19-489389 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-489623 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-489817 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:19-489992 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:19-490225 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-490418 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:19-490594 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-490791 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:19-490966 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:19-491198 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-491373 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:19-491548 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:19-491720 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:19-491941 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-492118 cadet-con-8620 DEBUG  ACK 69
Jul 07 20:46:19-492297 cadet-con-8620 DEBUG  last pid 5, last ack 68, qmax 11, q 0
Jul 07 20:46:19-492477 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:19-492644 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:19-492841 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:19-493025 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-493231 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-493419 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:19-493594 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-493776 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:19-493950 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-494171 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:19-494402 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-494584 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:46:19-494757 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-495016 cadet-con-8620 INFO --> {               ACK} ( 69) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:19-495206 cadet-con-8620 DEBUG  ack 69
Jul 07 20:46:19-495382 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:19-495612 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:19-495818 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:19-496106 cadet-p2p-8620 INFO que {               ACK} ( 69) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:19-496303 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:19-496524 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-496706 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:19-496878 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-497076 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:19-497300 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:19-497479 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:19-497653 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:19-497903 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-498086 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:46:19-498675 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-498913 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-499108 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:19-499284 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:19-499518 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-499711 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:19-499887 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-500084 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:19-500271 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:19-500487 util-scheduler-8620 DEBUG Adding task: 2051 / 0x46620a0
Jul 07 20:46:19-500769 util-scheduler-8620 DEBUG Checking readiness of task: 2051 / 0x46620a0
Jul 07 20:46:19-500969 util-scheduler-8620 DEBUG Checking readiness of task: 2050 / 0x4d5c418
Jul 07 20:46:19-501160 util-scheduler-8620 DEBUG Checking readiness of task: 2049 / 0x4d5e5d8
Jul 07 20:46:19-501396 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-501588 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-501778 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-501967 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-502157 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-502346 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-502535 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-502729 util-scheduler-8620 DEBUG Running task: 2049 / 0x4d5e5d8
Jul 07 20:46:19-502914 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-503093 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-503265 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-503515 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-503723 util-scheduler-8620 DEBUG Adding task: 2052 / 0x4d5e5d8
Jul 07 20:46:19-503927 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:19-504250 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-504452 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:19-504651 util-scheduler-8620 DEBUG Running task: 2050 / 0x4d5c418
Jul 07 20:46:19-504836 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:19-505010 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-505225 util-server-nc-8620 DEBUG Copying message of type 285 and size 33292 from pending queue to transmission buffer
Jul 07 20:46:19-506129 util-8620 DEBUG Connection transmitted 33292/33292 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:19-506461 util-scheduler-8620 DEBUG Running task: 2051 / 0x46620a0
Jul 07 20:46:19-506869 util-8620 DEBUG receive_ready read 336/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:19-507110 util-scheduler-8620 DEBUG Adding task: 2053 / 0x4662248
Jul 07 20:46:19-507369 util-scheduler-8620 DEBUG Checking readiness of task: 2052 / 0x4d5e5d8
Jul 07 20:46:19-507566 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-507756 util-scheduler-8620 DEBUG Checking readiness of task: 1952 / 0x4d5c418
Jul 07 20:46:19-507948 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-508137 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-508327 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-508516 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-508727 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-508918 util-scheduler-8620 DEBUG Running task: 1952 / 0x4d5c418
Jul 07 20:46:19-509327 util-8620 DEBUG receive_ready read 80/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:46:19-509535 util-8620 DEBUG Server receives 80 bytes from `<unbound UNIX client>'.
Jul 07 20:46:19-509726 util-8620 DEBUG Server-mst receives 80 bytes with 0 bytes already in private buffer
Jul 07 20:46:19-509910 util-8620 DEBUG Server-mst has 80 bytes left in inbound buffer
Jul 07 20:46:19-510092 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:46:19-510279 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:46:19-510495 util-scheduler-8620 DEBUG Adding task: 2054 / 0x4d5c578
Jul 07 20:46:19-510674 cadet-loc-8620 DEBUG 
Jul 07 20:46:19-510840 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:46:19-511010 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:19-511184 cadet-loc-8620 DEBUG   on channel 80000003
Jul 07 20:46:19-511363 cadet-loc-8620 DEBUG    -- ch 0x5e336a0
Jul 07 20:46:19-511535 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:46:19-511702 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:46:19-511906 cadet-tun-8620 DEBUG Tunnel send connection ACKs on D3TJ
Jul 07 20:46:19-512084 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:46:19-512875 cadet-tun-8620 DEBUG   allowed 65
Jul 07 20:46:19-513077 util-scheduler-8620 DEBUG Canceling task: 2054 / 0x4d5c578
Jul 07 20:46:19-513298 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:19-513481 util-8620 DEBUG Server-mst has 72 bytes left in inbound buffer
Jul 07 20:46:19-513667 util-8620 DEBUG Server-mst leaves 72 bytes in private buffer
Jul 07 20:46:19-513844 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:46:19-514023 util-8620 DEBUG Server-mst receives 0 bytes with 72 bytes already in private buffer
Jul 07 20:46:19-514208 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:46:19-514394 util-8620 DEBUG Server schedules transmission of 72-byte message of type 285 to client.
Jul 07 20:46:19-514602 util-scheduler-8620 DEBUG Adding task: 2055 / 0x4d5c578
Jul 07 20:46:19-514782 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:46:19-514954 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:19-515129 cadet-loc-8620 DEBUG   on channel 80000003
Jul 07 20:46:19-515311 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:46:19-515565 cadet-chn-8620 INFO ===> {              DATA} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-515765 cadet-chn-8620 INFO ===> {              DATA} 1
Jul 07 20:46:19-515966 cadet-chn-8620 DEBUG !!! SAVE 1 {              DATA}
Jul 07 20:46:19-516152 cadet-chn-8620 DEBUG   at 0x54adab0
Jul 07 20:46:19-516355 cadet-chn-8620 DEBUG   new chq: 0x54b6d40
Jul 07 20:46:19-516557 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:19-516754 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:19-516933 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-517116 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:19-517319 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-517499 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-517668 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-517881 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-518052 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-518285 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-518528 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-518711 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-518996 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:19-519167 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-519350 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:19-522761 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:19-523508 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:19-523689 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:19-523878 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:19-527022 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:19-527260 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:19-527444 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:19-527667 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:19-527844 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:19-528062 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-528254 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:19-528527 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 1) on connection 1KSG9GE2 (->D3TJ) (156 bytes)
Jul 07 20:46:19-528724 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:19-528901 cadet-con-8620 DEBUG last pid sent 5
Jul 07 20:46:19-529074 cadet-con-8620 DEBUG      ack recv 69
Jul 07 20:46:19-529277 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:19-529512 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:19-529718 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:19-530029 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 1) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 156)
Jul 07 20:46:19-530229 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:19-530453 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-530635 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:19-530810 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-531011 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:19-531212 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:19-531386 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:19-531560 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:19-531797 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-531979 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:46:19-532154 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-532387 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-532581 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:19-532759 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:19-532992 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-533185 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:19-533389 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-533623 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-533816 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:19-533993 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:19-534190 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:19-534396 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:19-534574 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-534756 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:19-534935 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-535110 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-535279 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-535491 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-535661 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-535889 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:19-536131 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-536314 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-536485 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:19-536661 cadet-chn-8620 DEBUG  gap ok: 1 - 2
Jul 07 20:46:19-536863 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:19-537061 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-537266 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:19-537449 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-537623 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-537791 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-538002 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-538171 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-538398 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:19-538640 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-538823 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-538998 cadet-chn-8620 DEBUG  buffer space 21, allowing
Jul 07 20:46:19-539222 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:19-539408 cadet-loc-8620 DEBUG send local FWD ack on 80000003 towards 0x4d5c6d8
Jul 07 20:46:19-539617 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:19-539817 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:19-540026 util-scheduler-8620 DEBUG Adding task: 2056 / 0x4d5c418
Jul 07 20:46:19-540219 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:46:19-540400 util-scheduler-8620 DEBUG Canceling task: 2055 / 0x4d5c578
Jul 07 20:46:19-540593 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:19-540772 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:46:19-540976 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:46:19-541180 util-scheduler-8620 DEBUG Adding task: 2057 / 0x4d5c418
Jul 07 20:46:19-541407 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:46:19-541635 util-scheduler-8620 DEBUG Running task: 2052 / 0x4d5e5d8
Jul 07 20:46:19-541823 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-542000 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-542171 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-542395 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:19-542734 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-542947 util-scheduler-8620 DEBUG Running task: 2053 / 0x4662248
Jul 07 20:46:19-543160 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:19-543362 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:19-543579 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:19-543830 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:19-544077 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-544283 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-544465 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:19-544637 cadet-con-8620 DEBUG   ACK 72 (was 71)
Jul 07 20:46:19-544865 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-545095 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-545327 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-545510 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:19-545720 util-scheduler-8620 DEBUG Adding task: 2058 / 0x4662248
Jul 07 20:46:19-545977 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-546203 util-scheduler-8620 DEBUG Checking readiness of task: 2056 / 0x4d5c418
Jul 07 20:46:19-546396 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-546602 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-546793 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-547485 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-547684 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-547874 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-548081 util-scheduler-8620 DEBUG Running task: 2056 / 0x4d5c418
Jul 07 20:46:19-548267 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:19-548443 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-548637 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:19-548930 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:19-549152 util-scheduler-8620 DEBUG Running task: 2058 / 0x4662248
Jul 07 20:46:19-549380 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:19-549589 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:19-549807 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `V8XX'
Jul 07 20:46:19-550052 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:19-550302 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:19-550530 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-550738 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:19-550978 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-551199 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-551386 cadet-con-8620 DEBUG  PID 11 (expected 11+)
Jul 07 20:46:19-551566 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:19-551814 util-scheduler-8620 DEBUG Canceling task: 2040 / 0x4d707d0
Jul 07 20:46:19-552091 util-scheduler-8620 DEBUG Adding task: 2059 / 0x4d707d0
Jul 07 20:46:19-552274 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:19-552522 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-552734 util-scheduler-8620 DEBUG Adding task: 2060 / 0x4d5e5d8
Jul 07 20:46:19-552918 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:19-553101 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:19-556301 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:19-556955 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:19-557146 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:19-560295 cadet-tun-8620 INFO <=== {          DATA_ACK} on V8XX
Jul 07 20:46:19-560489 cadet-chn-8620 INFO <=== FWD ACK 2
Jul 07 20:46:19-560670 cadet-chn-8620 DEBUG   id 2
Jul 07 20:46:19-560844 cadet-chn-8620 DEBUG !!! Freeing 2
Jul 07 20:46:19-561094 cadet-chn-8620 INFO !!!  took 800911 µs, new delay 800911 µs
Jul 07 20:46:19-561298 cadet-chn-8620 DEBUG  COPYFREE 0x540c558
Jul 07 20:46:19-561480 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:19-561647 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:46:19-561846 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:19-562023 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:19-562204 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:19-562383 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:19-562559 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:19-562728 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:19-562943 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-563116 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:19-563348 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:19-563533 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:19-563708 cadet-chn-8620 DEBUG  buffer space 11, allowing
Jul 07 20:46:19-563935 cadet-chn-8620 DEBUG   sending FWD ack to client on channel V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-564113 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:19-564295 util-scheduler-8620 DEBUG Canceling task: 2026 / 0x4d65218
Jul 07 20:46:19-564537 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:19-564734 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:19-564909 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:19-565080 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:19-565322 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:19-565500 cadet-con-8620 DEBUG  ACK 75
Jul 07 20:46:19-565679 cadet-con-8620 DEBUG  last pid 11, last ack 74, qmax 11, q 0
Jul 07 20:46:19-565858 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:19-566038 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:19-566224 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:19-566408 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-566586 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-566773 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:19-566948 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-567129 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:19-567303 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-567528 cadet-p2p-8620 DEBUG Checking 0x5491e90 towards CMHCKRVP (->V8XX)
Jul 07 20:46:19-567759 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:19-567940 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 9
Jul 07 20:46:19-568114 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-568374 cadet-con-8620 INFO --> {               ACK} ( 75) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:19-568564 cadet-con-8620 DEBUG  ack 75
Jul 07 20:46:19-568740 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:19-568976 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-569181 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-569520 cadet-p2p-8620 INFO que {               ACK} ( 75) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:19-569719 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:19-569941 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:19-570122 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 9
Jul 07 20:46:19-570294 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-570494 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:19-570694 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:19-570884 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:19-571058 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:19-571294 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-571476 cadet-p2p-8620 DEBUG QQQ    payload , 75
Jul 07 20:46:19-571650 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-571883 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-572074 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:19-572250 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-572446 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:19-572657 util-scheduler-8620 DEBUG Adding task: 2061 / 0x4662248
Jul 07 20:46:19-572912 util-scheduler-8620 DEBUG Checking readiness of task: 2060 / 0x4d5e5d8
Jul 07 20:46:19-573106 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-573324 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-573515 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-573704 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-573893 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-574096 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-574286 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-574504 util-scheduler-8620 DEBUG Running task: 2060 / 0x4d5e5d8
Jul 07 20:46:19-574689 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-574866 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-575053 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-575273 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:19-575593 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-575805 util-scheduler-8620 DEBUG Running task: 2061 / 0x4662248
Jul 07 20:46:19-575995 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:19-576189 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:19-576419 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `V8XX'
Jul 07 20:46:19-576665 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:19-576912 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:19-577155 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-577403 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:19-577646 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-577852 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-578039 cadet-con-8620 DEBUG  PID 12 (expected 12+)
Jul 07 20:46:19-578218 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:19-578403 util-scheduler-8620 DEBUG Canceling task: 2059 / 0x4d707d0
Jul 07 20:46:19-578621 util-scheduler-8620 DEBUG Adding task: 2062 / 0x4d707d0
Jul 07 20:46:19-578799 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:19-579039 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-579252 util-scheduler-8620 DEBUG Adding task: 2063 / 0x4d5e5d8
Jul 07 20:46:19-579433 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:19-579599 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:19-583234 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:19-583876 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:19-584068 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:19-587759 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on V8XX
Jul 07 20:46:19-587996 cadet-chn-8620 DEBUG Channel V8XX:40000000 (0x4d650a8)
Jul 07 20:46:19-588184 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x4d65218
Jul 07 20:46:19-588372 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:46:19-588543 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:46:19-588716 cadet-chn-8620 DEBUG   id 80000002
Jul 07 20:46:19-588891 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:46:19-589097 util-server-nc-8620 DEBUG Adding message of type 274 and size 48 to pending queue (which has 1 entries)
Jul 07 20:46:19-589336 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:19-589542 util-scheduler-8620 DEBUG Adding task: 2064 / 0x4d5c418
Jul 07 20:46:19-590004 cadet-chn-8620 DEBUG destroying channel V8XX:1073741824
Jul 07 20:46:19-590220 cadet-chn-8620 DEBUG Channel V8XX:40000000 (0x4d650a8)
Jul 07 20:46:19-590405 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x4d65218
Jul 07 20:46:19-590590 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:46:19-590760 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:46:19-590931 cadet-chn-8620 DEBUG   id 80000002
Jul 07 20:46:19-591106 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:46:19-591639 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:19-591835 cadet-p2p-8620 DEBUG queue destroy type {         ENCRYPTED}
Jul 07 20:46:19-592022 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-592201 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-592388 cadet-con-8620 DEBUG  not sent FWD {         ENCRYPTED}
Jul 07 20:46:19-592630 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-592828 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:19-593047 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:19-593303 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:19-593525 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:19-593739 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:19-593933 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 9
Jul 07 20:46:19-594107 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-594354 cadet-p2p-8620 DEBUG Checking 0x54c8450 towards CMHCKRVP (->V8XX)
Jul 07 20:46:19-595067 cadet-tun-8620 DEBUG Removing channel 0x4d650a8 from tunnel 0x4d64a70
Jul 07 20:46:19-595458 cadet-tun-8620 DEBUG  found! V8XX:19 gid:40000000 (80000002 / 0)
Jul 07 20:46:19-596330 cadet-tun-8620 DEBUG Tunnel V8XX destroy if empty
Jul 07 20:46:19-596705 cadet-tun-8620 DEBUG Tunnel V8XX empty: destroying scheduled
Jul 07 20:46:19-596921 util-scheduler-8620 DEBUG Adding task: 2065 / 0x4d64a70
Jul 07 20:46:19-597295 cadet-tun-8620 DEBUG Scheduled destroy of 0x4d64a70 as 811
Jul 07 20:46:19-597542 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:19-597719 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:19-597891 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:19-598063 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:19-598284 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:19-598462 cadet-con-8620 DEBUG  ACK 76
Jul 07 20:46:19-598641 cadet-con-8620 DEBUG  last pid 12, last ack 75, qmax 11, q 0
Jul 07 20:46:19-598820 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:19-598990 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:19-599176 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:19-599355 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-599531 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-599717 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:19-599890 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-600071 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:19-600244 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-600450 core-api-8620 DEBUG Aborting transmission request to core for 100 bytes to `V8XX'
Jul 07 20:46:19-600722 cadet-con-8620 INFO --> {               ACK} ( 76) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:19-600913 cadet-con-8620 DEBUG  ack 76
Jul 07 20:46:19-601090 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:19-601351 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:19-601559 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:19-601853 cadet-p2p-8620 INFO que {               ACK} ( 76) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:19-602051 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:19-602276 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:19-602457 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 9
Jul 07 20:46:19-602631 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-602834 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:46:19-603049 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:46:19-603265 util-scheduler-8620 DEBUG Adding task: 2066 / 0x4d6ff98
Jul 07 20:46:19-603445 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:19-603647 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:19-603823 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:19-603997 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:19-604233 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:19-604415 cadet-p2p-8620 DEBUG QQQ    payload , 76
Jul 07 20:46:19-604590 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:19-604788 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:19-604971 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:19-605182 util-scheduler-8620 DEBUG Adding task: 2067 / 0x46620a0
Jul 07 20:46:19-605477 util-scheduler-8620 DEBUG Checking readiness of task: 2067 / 0x46620a0
Jul 07 20:46:19-605673 util-scheduler-8620 DEBUG Checking readiness of task: 2064 / 0x4d5c418
Jul 07 20:46:19-605865 util-scheduler-8620 DEBUG Checking readiness of task: 2063 / 0x4d5e5d8
Jul 07 20:46:19-606057 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-606247 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-606459 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-608159 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-608366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-608636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-608830 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-609025 util-scheduler-8620 DEBUG Running task: 2063 / 0x4d5e5d8
Jul 07 20:46:19-609235 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-609416 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-609587 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-609833 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:19-610043 util-scheduler-8620 DEBUG Adding task: 2068 / 0x4d5e5d8
Jul 07 20:46:19-610246 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:19-610563 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-610763 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:19-610962 util-scheduler-8620 DEBUG Running task: 2064 / 0x4d5c418
Jul 07 20:46:19-611146 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:19-611321 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-611512 util-server-nc-8620 DEBUG Copying message of type 274 and size 48 from pending queue to transmission buffer
Jul 07 20:46:19-611837 util-8620 DEBUG Connection transmitted 48/48 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:19-612107 util-scheduler-8620 DEBUG Running task: 2066 / 0x4d6ff98
Jul 07 20:46:19-612305 util-scheduler-8620 DEBUG Canceling task: 2045 / 0x4d6ff98
Jul 07 20:46:19-612525 util-scheduler-8620 DEBUG Adding task: 2069 / 0x4d6ff98
Jul 07 20:46:19-612750 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:19-612948 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-613145 util-scheduler-8620 DEBUG Adding task: 2070 / 0x46620a0
Jul 07 20:46:19-613418 util-scheduler-8620 DEBUG Checking readiness of task: 2070 / 0x46620a0
Jul 07 20:46:19-613612 util-scheduler-8620 DEBUG Checking readiness of task: 2068 / 0x4d5e5d8
Jul 07 20:46:19-613803 util-scheduler-8620 DEBUG Checking readiness of task: 2067 / 0x46620a0
Jul 07 20:46:19-613993 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-614181 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-614371 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-614561 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-614750 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-614939 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-615127 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-615318 util-scheduler-8620 DEBUG Running task: 2067 / 0x46620a0
Jul 07 20:46:19-615723 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:19-615953 util-scheduler-8620 DEBUG Adding task: 2071 / 0x4662248
Jul 07 20:46:19-616163 util-scheduler-8620 DEBUG Running task: 2068 / 0x4d5e5d8
Jul 07 20:46:19-616346 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:19-616521 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-616690 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-616901 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:46:19-617210 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:19-617424 util-scheduler-8620 DEBUG Running task: 2070 / 0x46620a0
Jul 07 20:46:19-617622 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-617816 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-617986 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-618165 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:19-618360 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:19-618549 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:19-618938 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-619188 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-619382 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-619574 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-619842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-620035 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-620225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-620414 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-620603 util-scheduler-8620 DEBUG Running task: 2071 / 0x4662248
Jul 07 20:46:19-620794 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:19-620990 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:19-621231 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:19-621440 util-scheduler-8620 DEBUG Adding task: 2072 / 0x4662248
Jul 07 20:46:19-621675 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-621867 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-622056 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-622246 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-622435 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-622624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-622812 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-623001 util-scheduler-8620 DEBUG Running task: 2072 / 0x4662248
Jul 07 20:46:19-623188 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:19-623378 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:19-623588 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:19-623783 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-623980 util-scheduler-8620 DEBUG Adding task: 2073 / 0x46620a0
Jul 07 20:46:19-624162 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:19-624362 util-scheduler-8620 DEBUG Adding task: 2074 / 0x46620a0
Jul 07 20:46:19-624601 util-scheduler-8620 DEBUG Checking readiness of task: 2074 / 0x46620a0
Jul 07 20:46:19-624794 util-scheduler-8620 DEBUG Checking readiness of task: 2073 / 0x46620a0
Jul 07 20:46:19-624986 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-625176 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-625391 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-625581 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-625772 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-625961 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-626150 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-626340 util-scheduler-8620 DEBUG Running task: 2073 / 0x46620a0
Jul 07 20:46:19-626525 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-626699 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-627349 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-627544 util-scheduler-8620 DEBUG Canceling task: 2012 / 0x5e2b838
Jul 07 20:46:19-627768 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 40 bytes.
Jul 07 20:46:19-627986 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:19-628220 cadet-p2p-8620 DEBUG Checking 0x54a6eb8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-628454 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:19-628632 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:19-628820 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:19-629091 cadet-p2p-8620 INFO snd {               ACK} ( 69) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:19-629310 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-629489 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-629675 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:19-629847 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-630029 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:19-630202 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-630423 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:19-630655 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-630836 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:46:19-631010 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-631236 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:19-631465 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-631647 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:46:19-631820 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:19-631986 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:19-632190 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `D3TJ'
Jul 07 20:46:19-632403 util-scheduler-8620 DEBUG Adding task: 2075 / 0x5e2b838
Jul 07 20:46:19-632582 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:19-632758 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:19-632955 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:19-633129 cadet-p2p-8620 DEBUG QQQ  queue length: 3
Jul 07 20:46:19-633327 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:19-633564 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:19-633757 cadet-p2p-8620 DEBUG QQQ    payload {       CHANNEL_ACK}, 0
Jul 07 20:46:19-633935 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:19-634168 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-634360 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:19-634536 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:19-634769 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:19-634963 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:19-635139 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:19-635335 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:19-635540 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:19-635723 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:19-635924 util-scheduler-8620 DEBUG Adding task: 2076 / 0x5e2b838
Jul 07 20:46:19-636139 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:19-636333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-636534 util-scheduler-8620 DEBUG Adding task: 2077 / 0x46620a0
Jul 07 20:46:19-636731 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:19-637554 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-637754 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:19-637954 util-scheduler-8620 DEBUG Running task: 2074 / 0x46620a0
Jul 07 20:46:19-638372 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:19-638600 util-scheduler-8620 DEBUG Adding task: 2078 / 0x4662248
Jul 07 20:46:19-638854 util-scheduler-8620 DEBUG Checking readiness of task: 2077 / 0x46620a0
Jul 07 20:46:19-639048 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-639239 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-639428 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-639618 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-639819 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-640009 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-640198 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-640388 util-scheduler-8620 DEBUG Running task: 2077 / 0x46620a0
Jul 07 20:46:19-640573 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-640749 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-640919 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-641095 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:19-641312 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:19-641501 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:19-641782 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-641990 util-scheduler-8620 DEBUG Running task: 2078 / 0x4662248
Jul 07 20:46:19-642179 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:19-642372 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:19-642585 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:19-642779 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-642977 util-scheduler-8620 DEBUG Adding task: 2079 / 0x46620a0
Jul 07 20:46:19-643161 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:19-643359 util-scheduler-8620 DEBUG Adding task: 2080 / 0x46620a0
Jul 07 20:46:19-643556 util-scheduler-8620 DEBUG Running task: 2075 / 0x5e2b838
Jul 07 20:46:19-643746 util-scheduler-8620 DEBUG Canceling task: 2076 / 0x5e2b838
Jul 07 20:46:19-643958 util-scheduler-8620 DEBUG Adding task: 2081 / 0x5e2b838
Jul 07 20:46:19-644173 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:19-644349 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:19-644580 util-scheduler-8620 DEBUG Checking readiness of task: 2080 / 0x46620a0
Jul 07 20:46:19-645164 util-scheduler-8620 DEBUG Checking readiness of task: 2079 / 0x46620a0
Jul 07 20:46:19-645384 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-645576 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-645767 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-645958 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-646147 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-646337 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-646526 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-646717 util-scheduler-8620 DEBUG Running task: 2079 / 0x46620a0
Jul 07 20:46:19-646901 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-647077 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-647246 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-647421 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:19-647631 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:19-647848 util-scheduler-8620 DEBUG Adding task: 2082 / 0x46620a0
Jul 07 20:46:19-648046 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:19-648329 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:19-648526 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:19-648766 util-scheduler-8620 DEBUG Checking readiness of task: 2082 / 0x46620a0
Jul 07 20:46:19-648960 util-scheduler-8620 DEBUG Checking readiness of task: 2080 / 0x46620a0
Jul 07 20:46:19-649151 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:19-649395 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:19-649610 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:19-649800 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:19-649990 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:19-650179 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:19-650368 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:19-650558 util-scheduler-8620 DEBUG Running task: 2082 / 0x46620a0
Jul 07 20:46:19-650742 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:19-650917 util-8620 DEBUG process_notify is running
Jul 07 20:46:19-651086 util-8620 DEBUG client_notify is running
Jul 07 20:46:19-651268 util-scheduler-8620 DEBUG Canceling task: 2069 / 0x4d6ff98
Jul 07 20:46:19-651489 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:46:19-651702 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:19-651932 cadet-p2p-8620 DEBUG Checking 0x54cc148 towards CMHCKRVP (->V8XX)
Jul 07 20:46:19-652162 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:19-652337 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:19-652522 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:19-652783 cadet-p2p-8620 INFO snd {               ACK} ( 76) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:19-652975 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:19-653151 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:19-653362 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:19-653534 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:19-654085 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:19-654261 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:19-654442 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:19-654642 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:19-654816 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:19-654990 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:19-655188 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:19-655392 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:19-655574 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:19-655751 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:19-655939 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:19-658303 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:20-003269 util-scheduler-8620 DEBUG Checking readiness of task: 2080 / 0x46620a0
Jul 07 20:46:20-003647 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:20-003846 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:20-004042 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:20-004236 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:20-004432 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:20-004625 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:20-004850 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:20-005052 util-scheduler-8620 DEBUG Running task: 2080 / 0x46620a0
Jul 07 20:46:20-005508 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:20-005765 util-scheduler-8620 DEBUG Adding task: 2083 / 0x4662248
Jul 07 20:46:20-006044 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:20-006238 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:20-006431 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:20-006625 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:20-006817 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:20-007008 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:20-007199 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:20-007391 util-scheduler-8620 DEBUG Running task: 2083 / 0x4662248
Jul 07 20:46:20-007586 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:20-007788 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:20-008020 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:20-008286 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:20-008544 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:20-008754 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:20-008953 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:20-009128 cadet-con-8620 DEBUG   ACK 73 (was 72)
Jul 07 20:46:20-009853 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:20-010093 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:20-010302 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:20-010487 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:20-010667 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:20-010881 util-scheduler-8620 DEBUG Adding task: 2084 / 0x46620a0
Jul 07 20:46:21-402407 util-scheduler-8620 DEBUG Checking readiness of task: 2084 / 0x46620a0
Jul 07 20:46:21-402814 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-403014 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-403209 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-403401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-403593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-403783 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-403973 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-404169 util-scheduler-8620 DEBUG Running task: 2084 / 0x46620a0
Jul 07 20:46:21-404592 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:21-404848 util-scheduler-8620 DEBUG Adding task: 2085 / 0x4662248
Jul 07 20:46:21-405127 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-405349 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-405540 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-405730 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-405920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-406109 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-406298 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-406488 util-scheduler-8620 DEBUG Running task: 2085 / 0x4662248
Jul 07 20:46:21-406715 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:21-406916 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:21-407149 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:21-407356 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-407564 util-scheduler-8620 DEBUG Adding task: 2086 / 0x46620a0
Jul 07 20:46:21-407752 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:21-407961 util-scheduler-8620 DEBUG Adding task: 2087 / 0x46620a0
Jul 07 20:46:21-408205 util-scheduler-8620 DEBUG Checking readiness of task: 2087 / 0x46620a0
Jul 07 20:46:21-408397 util-scheduler-8620 DEBUG Checking readiness of task: 2086 / 0x46620a0
Jul 07 20:46:21-408589 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-408779 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-408970 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-409160 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-409376 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-409565 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-409754 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-409945 util-scheduler-8620 DEBUG Running task: 2086 / 0x46620a0
Jul 07 20:46:21-410130 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-410307 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-410480 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-410671 util-scheduler-8620 DEBUG Canceling task: 2081 / 0x5e2b838
Jul 07 20:46:21-410895 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 88 bytes.
Jul 07 20:46:21-411116 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:21-411355 cadet-p2p-8620 DEBUG Checking 0x539dbb8 towards BFARXZN9 (->D3TJ)
Jul 07 20:46:21-411590 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:46:21-411773 cadet-con-8620 DEBUG  last ack recv: 64, last pid sent: 0
Jul 07 20:46:21-411948 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-412169 cadet-p2p-8620 DEBUG   on connection BFARXZN9 (->D3TJ) BCK
Jul 07 20:46:21-412347 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:21-412522 cadet-p2p-8620 DEBUG   payload ID 1
Jul 07 20:46:21-412809 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({       CHANNEL_ACK} 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK (size 88)
Jul 07 20:46:21-413005 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:21-413186 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:21-413400 cadet-con-8620 DEBUG  sent BCK {         ENCRYPTED}
Jul 07 20:46:21-413589 cadet-con-8620 DEBUG  C_P- 0x5e2cf38 1
Jul 07 20:46:21-413820 cadet-con-8620 DEBUG GMC send BCK ACK on BFARXZN9 (->D3TJ)
Jul 07 20:46:21-413995 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:21-414166 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:21-414337 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:21-414534 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:21-414708 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:21-414882 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:21-415082 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:21-415262 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:21-415443 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:21-415624 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:21-415800 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:21-415969 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:21-416184 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:21-416354 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:21-416586 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:21-416848 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:21-417032 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:21-417235 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:21-417423 util-scheduler-8620 DEBUG Canceling task: 1989 / 0x5e2cf38
Jul 07 20:46:21-417635 util-scheduler-8620 DEBUG Adding task: 2088 / 0x5e2cf38
Jul 07 20:46:21-417890 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:21-418068 cadet-con-8620 DEBUG !  Q_N- 0x5e2cf70 0
Jul 07 20:46:21-418246 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 1
Jul 07 20:46:21-418418 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:21-418640 cadet-p2p-8620 DEBUG Checking 0x54a5c30 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-418870 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-419051 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:21-419225 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-419451 cadet-p2p-8620 DEBUG Checking 0x54a5c30 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-419680 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-419861 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:21-420033 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-420199 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:21-420403 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `D3TJ'
Jul 07 20:46:21-420614 util-scheduler-8620 DEBUG Adding task: 2089 / 0x5e2b838
Jul 07 20:46:21-420792 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:21-420968 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:21-421166 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:21-421365 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:21-421539 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:21-421777 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-421972 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 0
Jul 07 20:46:21-422151 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:21-422412 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-422605 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:21-422781 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:21-422979 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:21-423183 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 88 bytes.
Jul 07 20:46:21-423365 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:21-423569 util-scheduler-8620 DEBUG Adding task: 2090 / 0x5e2b838
Jul 07 20:46:21-423788 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:21-423983 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-424184 util-scheduler-8620 DEBUG Adding task: 2091 / 0x46620a0
Jul 07 20:46:21-424384 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:21-425983 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-426194 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:21-426447 util-scheduler-8620 DEBUG Checking readiness of task: 2091 / 0x46620a0
Jul 07 20:46:21-426641 util-scheduler-8620 DEBUG Checking readiness of task: 2087 / 0x46620a0
Jul 07 20:46:21-426832 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-427022 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-427211 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-427401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-427590 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-427779 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-427971 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-428179 util-scheduler-8620 DEBUG Running task: 2091 / 0x46620a0
Jul 07 20:46:21-428365 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-428731 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-428908 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-429089 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:21-429313 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:21-429504 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:21-429805 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-430014 util-scheduler-8620 DEBUG Running task: 2089 / 0x5e2b838
Jul 07 20:46:21-430208 util-scheduler-8620 DEBUG Canceling task: 2090 / 0x5e2b838
Jul 07 20:46:21-430426 util-scheduler-8620 DEBUG Adding task: 2092 / 0x5e2b838
Jul 07 20:46:21-430647 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:21-430842 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-431042 util-scheduler-8620 DEBUG Adding task: 2093 / 0x46620a0
Jul 07 20:46:21-431284 util-scheduler-8620 DEBUG Checking readiness of task: 2093 / 0x46620a0
Jul 07 20:46:21-431478 util-scheduler-8620 DEBUG Checking readiness of task: 2087 / 0x46620a0
Jul 07 20:46:21-431669 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-431859 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-432049 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-432239 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-432429 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-432618 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-432806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-432998 util-scheduler-8620 DEBUG Running task: 2087 / 0x46620a0
Jul 07 20:46:21-433421 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:21-433650 util-scheduler-8620 DEBUG Adding task: 2094 / 0x4662248
Jul 07 20:46:21-433860 util-scheduler-8620 DEBUG Running task: 2093 / 0x46620a0
Jul 07 20:46:21-434043 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-434218 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-434386 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-434561 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:21-434749 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:21-434936 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:21-435233 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-435480 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-435673 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-435864 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-436055 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-436243 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-436431 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-436620 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-436809 util-scheduler-8620 DEBUG Running task: 2094 / 0x4662248
Jul 07 20:46:21-436997 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:21-437215 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:21-437433 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:21-437629 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:21-437832 util-scheduler-8620 DEBUG Adding task: 2095 / 0x46620a0
Jul 07 20:46:21-438074 util-scheduler-8620 DEBUG Checking readiness of task: 2095 / 0x46620a0
Jul 07 20:46:21-438267 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-438457 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-438647 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-438836 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-439026 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-439214 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-439402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-439592 util-scheduler-8620 DEBUG Running task: 2095 / 0x46620a0
Jul 07 20:46:21-439989 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:21-440211 util-scheduler-8620 DEBUG Adding task: 2096 / 0x4662248
Jul 07 20:46:21-440456 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-440648 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-440838 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-441028 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-441239 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-441431 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-441620 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-441810 util-scheduler-8620 DEBUG Running task: 2096 / 0x4662248
Jul 07 20:46:21-441997 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:21-442188 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:21-442399 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:21-442593 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-442790 util-scheduler-8620 DEBUG Adding task: 2097 / 0x46620a0
Jul 07 20:46:21-442972 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:21-443168 util-scheduler-8620 DEBUG Adding task: 2098 / 0x46620a0
Jul 07 20:46:21-443406 util-scheduler-8620 DEBUG Checking readiness of task: 2098 / 0x46620a0
Jul 07 20:46:21-443598 util-scheduler-8620 DEBUG Checking readiness of task: 2097 / 0x46620a0
Jul 07 20:46:21-443788 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-443979 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-444169 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-444359 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-444548 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-444737 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-444925 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-445126 util-scheduler-8620 DEBUG Running task: 2097 / 0x46620a0
Jul 07 20:46:21-445334 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-445509 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-445678 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-445860 util-scheduler-8620 DEBUG Canceling task: 2092 / 0x5e2b838
Jul 07 20:46:21-446079 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 100 bytes.
Jul 07 20:46:21-446293 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:21-446545 cadet-p2p-8620 DEBUG Checking 0x54a5c30 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-446793 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-446976 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 5
Jul 07 20:46:21-447150 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-447371 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:21-447547 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:21-447720 cadet-p2p-8620 DEBUG   payload ID 6
Jul 07 20:46:21-448002 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 100)
Jul 07 20:46:21-448195 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:21-448372 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:21-448558 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:21-448732 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:21-448899 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:21-449087 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:21-449298 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:21-449492 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:21-449719 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-449894 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:21-450065 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:21-450235 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:21-450432 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:21-450605 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:21-450778 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:21-450976 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:21-451152 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:21-451332 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:21-451512 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:21-451689 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:21-451859 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:21-452072 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:21-452242 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:21-452471 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:21-452714 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:21-452896 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:21-453073 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:21-453279 util-scheduler-8620 DEBUG Canceling task: 2000 / 0x5e31aa0
Jul 07 20:46:21-453489 util-scheduler-8620 DEBUG Adding task: 2099 / 0x5e31aa0
Jul 07 20:46:21-453735 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:21-453912 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:21-454089 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 6
Jul 07 20:46:21-454261 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:21-454482 cadet-p2p-8620 DEBUG Checking 0x54be6a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-454710 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-454890 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 6
Jul 07 20:46:21-455062 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-455288 cadet-p2p-8620 DEBUG Checking 0x54be6a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-455517 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-455698 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 6
Jul 07 20:46:21-455870 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-456036 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:21-456238 core-api-8620 DEBUG Asking core for transmission of 156 bytes to `D3TJ'
Jul 07 20:46:21-456448 util-scheduler-8620 DEBUG Adding task: 2100 / 0x5e2b838
Jul 07 20:46:21-456626 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:21-456802 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:21-457000 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:21-457216 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:21-457394 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:21-457632 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-457826 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 1
Jul 07 20:46:21-458006 cadet-p2p-8620 DEBUG QQQ    size: 156 bytes
Jul 07 20:46:21-458203 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:21-458406 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 100 bytes.
Jul 07 20:46:21-458588 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:21-458789 util-scheduler-8620 DEBUG Adding task: 2101 / 0x5e2b838
Jul 07 20:46:21-459002 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:21-459195 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-459396 util-scheduler-8620 DEBUG Adding task: 2102 / 0x46620a0
Jul 07 20:46:21-459594 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:21-461040 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-461273 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:21-461521 util-scheduler-8620 DEBUG Checking readiness of task: 2102 / 0x46620a0
Jul 07 20:46:21-461716 util-scheduler-8620 DEBUG Checking readiness of task: 2098 / 0x46620a0
Jul 07 20:46:21-461907 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-462097 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-462288 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-462478 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-462668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-462857 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-463047 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-463238 util-scheduler-8620 DEBUG Running task: 2102 / 0x46620a0
Jul 07 20:46:21-463422 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-463598 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-463768 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-463944 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:21-464135 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:21-464323 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:21-464631 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-464839 util-scheduler-8620 DEBUG Running task: 2100 / 0x5e2b838
Jul 07 20:46:21-465030 util-scheduler-8620 DEBUG Canceling task: 2101 / 0x5e2b838
Jul 07 20:46:21-465267 util-scheduler-8620 DEBUG Adding task: 2103 / 0x5e2b838
Jul 07 20:46:21-465487 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:21-465682 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-465880 util-scheduler-8620 DEBUG Adding task: 2104 / 0x46620a0
Jul 07 20:46:21-466119 util-scheduler-8620 DEBUG Checking readiness of task: 2104 / 0x46620a0
Jul 07 20:46:21-466312 util-scheduler-8620 DEBUG Checking readiness of task: 2098 / 0x46620a0
Jul 07 20:46:21-466502 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-466691 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-466880 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-467070 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-467270 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-467459 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-467664 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-467855 util-scheduler-8620 DEBUG Running task: 2098 / 0x46620a0
Jul 07 20:46:21-468259 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:21-468486 util-scheduler-8620 DEBUG Adding task: 2105 / 0x4662248
Jul 07 20:46:21-468696 util-scheduler-8620 DEBUG Running task: 2104 / 0x46620a0
Jul 07 20:46:21-468879 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-469054 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-469247 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-469424 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:21-469613 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:21-469801 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:21-470109 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:21-470355 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-470547 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-471109 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-471305 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-471495 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-471684 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-471874 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-472063 util-scheduler-8620 DEBUG Running task: 2105 / 0x4662248
Jul 07 20:46:21-472252 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:21-472446 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:21-472660 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:21-472840 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:21-473040 util-scheduler-8620 DEBUG Adding task: 2106 / 0x46620a0
Jul 07 20:46:21-473302 util-scheduler-8620 DEBUG Checking readiness of task: 2106 / 0x46620a0
Jul 07 20:46:21-473496 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-473686 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-473876 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-474066 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-474256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-474444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-474632 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-474822 util-scheduler-8620 DEBUG Running task: 2106 / 0x46620a0
Jul 07 20:46:21-475219 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:21-475563 util-scheduler-8620 DEBUG Adding task: 2107 / 0x4662248
Jul 07 20:46:21-475810 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-476002 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-476192 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-476381 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-476573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-476765 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-476954 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-477144 util-scheduler-8620 DEBUG Running task: 2107 / 0x4662248
Jul 07 20:46:21-477376 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:21-477569 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:21-477781 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:21-477980 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:21-478178 util-scheduler-8620 DEBUG Adding task: 2108 / 0x46620a0
Jul 07 20:46:21-478361 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:21-478557 util-scheduler-8620 DEBUG Adding task: 2109 / 0x46620a0
Jul 07 20:46:21-478798 util-scheduler-8620 DEBUG Checking readiness of task: 2109 / 0x46620a0
Jul 07 20:46:21-478989 util-scheduler-8620 DEBUG Checking readiness of task: 2108 / 0x46620a0
Jul 07 20:46:21-479180 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:21-479369 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:21-479560 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:21-479749 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:21-479938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:21-480127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:21-480315 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:21-480505 util-scheduler-8620 DEBUG Running task: 2108 / 0x46620a0
Jul 07 20:46:21-480688 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:21-480863 util-8620 DEBUG process_notify is running
Jul 07 20:46:21-481032 util-8620 DEBUG client_notify is running
Jul 07 20:46:21-481237 util-scheduler-8620 DEBUG Canceling task: 2103 / 0x5e2b838
Jul 07 20:46:21-481457 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 156 bytes.
Jul 07 20:46:21-482301 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:21-482542 cadet-p2p-8620 DEBUG Checking 0x54be6a8 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-482773 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-482955 cadet-con-8620 DEBUG  last ack recv: 69, last pid sent: 6
Jul 07 20:46:21-483129 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:21-483349 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:21-483525 cadet-p2p-8620 DEBUG   size 156 ok
Jul 07 20:46:21-483700 cadet-p2p-8620 DEBUG   payload ID 7
Jul 07 20:46:21-483978 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 1) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 156)
Jul 07 20:46:21-484170 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:21-484348 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:21-484599 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:21-484774 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:21-484940 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:21-485127 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:21-485330 cadet-chn-8620 DEBUG !!! SENT DATA MID 1
Jul 07 20:46:21-485557 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 1200 ms
Jul 07 20:46:21-485729 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:21-485934 cadet-chn-8620 DEBUG !! using delay 4802588 µs
Jul 07 20:46:21-486130 util-scheduler-8620 DEBUG Adding task: 2110 / 0x5e33a48
Jul 07 20:46:21-486331 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:21-486557 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:21-486731 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:21-488103 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:21-488280 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:21-488480 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:21-488654 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:21-488827 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:21-489027 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:21-489255 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:21-489460 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:21-489641 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:21-489817 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:21-489986 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:21-490200 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:21-490371 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:21-490602 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:21-490846 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:21-491042 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:21-491218 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:21-491408 util-scheduler-8620 DEBUG Canceling task: 2099 / 0x5e31aa0
Jul 07 20:46:21-491620 util-scheduler-8620 DEBUG Adding task: 2111 / 0x5e31aa0
Jul 07 20:46:21-491862 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:21-492040 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:21-492217 cadet-con-8620 DEBUG !   accounting pid 7
Jul 07 20:46:21-492387 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:21-492567 cadet-p2p-8620 DEBUG   return 156
Jul 07 20:46:21-492767 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:21-492942 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:21-493115 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:21-493339 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:21-493542 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 156 bytes.
Jul 07 20:46:21-493724 core-api-8620 DEBUG Produced SEND message to core with 156 bytes payload
Jul 07 20:46:21-493903 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:21-494092 util-8620 DEBUG Transmitting message of type 76 and size 212 to core service.
Jul 07 20:46:21-495537 util-8620 DEBUG Connection transmitted 212/212 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:22-757582 util-scheduler-8620 DEBUG Checking readiness of task: 2109 / 0x46620a0
Jul 07 20:46:22-757966 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:22-758164 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:22-758362 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:22-758555 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:22-758746 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:22-758937 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:22-759127 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:22-759323 util-scheduler-8620 DEBUG Running task: 2109 / 0x46620a0
Jul 07 20:46:22-759749 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:22-760007 util-scheduler-8620 DEBUG Adding task: 2112 / 0x4662248
Jul 07 20:46:22-760287 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:22-760481 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:22-760672 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:22-760862 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:22-761053 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:22-761268 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:22-761459 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:22-761649 util-scheduler-8620 DEBUG Running task: 2112 / 0x4662248
Jul 07 20:46:22-761840 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:22-762899 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:22-763138 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:22-763436 cadet-con-8620 INFO <-- {               ACK} on connection BFARXZN9 from D3TJ
Jul 07 20:46:22-763692 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:22-763901 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:22-764143 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:22-764351 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:22-764708 cadet-con-8620 DEBUG   BCK ACK
Jul 07 20:46:22-764888 cadet-con-8620 DEBUG   ACK 65 (was 64)
Jul 07 20:46:22-765119 cadet-con-8620 DEBUG connection_unlock_queue BCK on BFARXZN9 (->D3TJ)
Jul 07 20:46:22-765377 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:46:22-765583 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:22-765766 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:22-765943 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:22-766156 util-scheduler-8620 DEBUG Adding task: 2113 / 0x46620a0
Jul 07 20:46:23-001146 util-scheduler-8620 DEBUG Checking readiness of task: 2113 / 0x46620a0
Jul 07 20:46:23-001557 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-001757 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-001954 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-002148 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-002341 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-002534 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-002726 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-002924 util-scheduler-8620 DEBUG Running task: 2113 / 0x46620a0
Jul 07 20:46:23-003348 util-8620 DEBUG receive_ready read 344/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:23-003607 util-scheduler-8620 DEBUG Adding task: 2114 / 0x4662248
Jul 07 20:46:23-003886 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-004081 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-004274 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-004466 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-005177 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-005406 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-005601 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-005793 util-scheduler-8620 DEBUG Running task: 2114 / 0x4662248
Jul 07 20:46:23-005986 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:23-006192 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:23-006424 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:23-006689 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:23-006946 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-007156 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-007342 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:23-007517 cadet-con-8620 DEBUG   ACK 71 (was 69)
Jul 07 20:46:23-007752 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-007984 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-008191 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-008378 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:23-008582 util-scheduler-8620 DEBUG Adding task: 2115 / 0x4662248
Jul 07 20:46:23-008824 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-009018 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-009234 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-009455 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-009647 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-009838 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-010029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-010220 util-scheduler-8620 DEBUG Running task: 2115 / 0x4662248
Jul 07 20:46:23-010410 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:46:23-010605 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:46:23-010821 core-api-8620 DEBUG Received message of type 280 and size 100 from peer `D3TJ'
Jul 07 20:46:23-011065 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:23-011302 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-011533 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-011742 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:23-011982 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-012202 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-012391 cadet-con-8620 DEBUG  PID 6 (expected 6+)
Jul 07 20:46:23-012575 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:23-012767 util-scheduler-8620 DEBUG Canceling task: 2048 / 0x5e31aa0
Jul 07 20:46:23-012992 util-scheduler-8620 DEBUG Adding task: 2116 / 0x5e31aa0
Jul 07 20:46:23-013174 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:23-013459 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:23-013681 util-scheduler-8620 DEBUG Adding task: 2117 / 0x4d5e5d8
Jul 07 20:46:23-013868 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:23-014037 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:23-017616 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:23-018574 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:23-018794 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:23-022105 cadet-tun-8620 INFO <=== {          DATA_ACK} on D3TJ
Jul 07 20:46:23-022312 cadet-chn-8620 INFO <=== FWD ACK 1
Jul 07 20:46:23-022498 cadet-chn-8620 DEBUG   id 1
Jul 07 20:46:23-022675 cadet-chn-8620 DEBUG !!! Freeing 1
Jul 07 20:46:23-022930 cadet-chn-8620 INFO !!!  took 1537350 µs, new delay 1537350 µs
Jul 07 20:46:23-023114 cadet-chn-8620 DEBUG  COPYFREE 0x54adab0
Jul 07 20:46:23-023297 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:23-023468 cadet-chn-8620 DEBUG  head sent is NULL
Jul 07 20:46:23-023669 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:23-023851 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-024035 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:23-024218 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-024396 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:23-024567 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-024786 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-024959 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-025219 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-025468 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-025654 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-025834 cadet-chn-8620 DEBUG  buffer space 22, allowing
Jul 07 20:46:23-026061 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-026239 cadet-chn-8620 DEBUG   already allowed
Jul 07 20:46:23-026423 util-scheduler-8620 DEBUG Canceling task: 2110 / 0x5e33a48
Jul 07 20:46:23-026668 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-026846 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:23-027023 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:23-027197 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:23-027418 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-027625 cadet-con-8620 DEBUG  ACK 70
Jul 07 20:46:23-027808 cadet-con-8620 DEBUG  last pid 6, last ack 69, qmax 11, q 0
Jul 07 20:46:23-028078 cadet-con-8620 INFO --> {               ACK} ( 70) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:23-028275 cadet-con-8620 DEBUG  ack 70
Jul 07 20:46:23-028455 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:23-028691 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-028901 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-029223 cadet-p2p-8620 INFO que {               ACK} ( 70) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:23-029430 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:23-029656 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-029841 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:23-030017 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-030325 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 40 bytes
Jul 07 20:46:23-030545 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `D3TJ'
Jul 07 20:46:23-030768 util-scheduler-8620 DEBUG Adding task: 2118 / 0x5e2b838
Jul 07 20:46:23-030951 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:23-031157 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:23-031337 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:23-031513 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:23-031753 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-031939 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:46:23-032115 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:23-032314 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:23-032523 util-scheduler-8620 DEBUG Adding task: 2119 / 0x4662248
Jul 07 20:46:23-032785 util-scheduler-8620 DEBUG Checking readiness of task: 2117 / 0x4d5e5d8
Jul 07 20:46:23-032986 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-033178 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-033396 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-033589 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-033779 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-033970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-034160 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-034354 util-scheduler-8620 DEBUG Running task: 2117 / 0x4d5e5d8
Jul 07 20:46:23-034542 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:23-034721 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-034896 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-035126 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:23-035438 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:23-035652 util-scheduler-8620 DEBUG Running task: 2119 / 0x4662248
Jul 07 20:46:23-035845 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:23-036042 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:23-036261 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `D3TJ'
Jul 07 20:46:23-036508 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:23-036744 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-036972 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-037180 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:23-037447 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-037656 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-037845 cadet-con-8620 DEBUG  PID 7 (expected 7+)
Jul 07 20:46:23-038057 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:23-038244 util-scheduler-8620 DEBUG Canceling task: 2116 / 0x5e31aa0
Jul 07 20:46:23-038469 util-scheduler-8620 DEBUG Adding task: 2120 / 0x5e31aa0
Jul 07 20:46:23-038651 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:23-038897 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:23-039173 util-scheduler-8620 DEBUG Adding task: 2121 / 0x4d5e5d8
Jul 07 20:46:23-039827 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:23-040020 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:23-043300 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:23-043965 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:23-044160 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:23-047429 cadet-tun-8620 INFO <=== {              DATA} on D3TJ
Jul 07 20:46:23-047636 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:23-047917 cadet-chn-8620 INFO <=== DATA 1 BCK on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-048107 cadet-chn-8620 DEBUG RECV 1 (16)
Jul 07 20:46:23-048283 cadet-chn-8620 DEBUG as expected, sending to client
Jul 07 20:46:23-048489 util-server-nc-8620 DEBUG Adding message of type 285 and size 12 to pending queue (which has 1 entries)
Jul 07 20:46:23-048693 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:23-048902 util-scheduler-8620 DEBUG Adding task: 2122 / 0x4d5c418
Jul 07 20:46:23-049090 cadet-chn-8620 INFO ===> DATA_ACK for 1
Jul 07 20:46:23-049295 cadet-chn-8620 DEBUG  final futures: 1
Jul 07 20:46:23-049543 cadet-chn-8620 INFO ===> {          DATA_ACK} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-049760 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:23-049959 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:23-050138 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-050322 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:23-050504 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-050682 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:23-050853 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-051067 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-051240 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-051475 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-051721 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-051906 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-052200 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:23-052372 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-052559 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:23-057661 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:23-058626 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:23-058837 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-059041 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:23-063265 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:23-063577 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:23-063761 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:23-063985 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:23-064163 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:23-064383 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-064581 cadet-tun-8620 DEBUG type {          DATA_ACK}
Jul 07 20:46:23-064861 cadet-con-8620 INFO --> {         ENCRYPTED} ({          DATA_ACK} 1) on connection 1KSG9GE2 (->D3TJ) (100 bytes)
Jul 07 20:46:23-065063 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:23-065264 cadet-con-8620 DEBUG last pid sent 7
Jul 07 20:46:23-065466 cadet-con-8620 DEBUG      ack recv 71
Jul 07 20:46:23-065641 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:23-065819 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:23-066055 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-066294 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-066613 cadet-p2p-8620 INFO que {         ENCRYPTED} ({          DATA_ACK} 1) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 100)
Jul 07 20:46:23-066817 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:23-067046 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-067230 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:23-067406 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-067609 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:23-067999 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:23-068180 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:23-068358 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:23-068600 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-068784 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:46:23-068961 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:23-069225 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-069460 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:23-069640 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:23-069841 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:23-070018 cadet-chn-8620 DEBUG send_data_ack END
Jul 07 20:46:23-070245 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-070421 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:23-070596 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:23-070771 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:23-070992 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-071171 cadet-con-8620 DEBUG  ACK 71
Jul 07 20:46:23-071365 cadet-con-8620 DEBUG  last pid 7, last ack 70, qmax 11, q 0
Jul 07 20:46:23-071546 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:23-071715 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:23-071900 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:23-072085 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:23-072267 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:23-072455 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:23-072631 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:23-072814 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:23-072989 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:23-073234 cadet-p2p-8620 DEBUG Checking 0x5509688 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-073475 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-073663 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:23-073842 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-074116 cadet-con-8620 INFO --> {               ACK} ( 71) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:23-074326 cadet-con-8620 DEBUG  ack 71
Jul 07 20:46:23-074511 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 1
Jul 07 20:46:23-074756 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-074971 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-075282 cadet-p2p-8620 INFO que {               ACK} ( 71) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:23-075490 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:23-075721 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-075911 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:23-076093 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-076305 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:23-076517 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:23-076707 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:23-076888 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:23-077141 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-077388 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:46:23-077601 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:23-077853 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-078054 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:23-078239 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:23-078445 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:23-078639 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:23-078921 util-scheduler-8620 DEBUG Adding task: 2123 / 0x46620a0
Jul 07 20:46:23-079149 util-scheduler-8620 DEBUG Running task: 2118 / 0x5e2b838
Jul 07 20:46:23-079372 util-scheduler-8620 DEBUG Adding task: 2124 / 0x5e2b838
Jul 07 20:46:23-079606 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:23-079818 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:23-080022 util-scheduler-8620 DEBUG Adding task: 2125 / 0x46620a0
Jul 07 20:46:23-080463 util-scheduler-8620 DEBUG Checking readiness of task: 2125 / 0x46620a0
Jul 07 20:46:23-080677 util-scheduler-8620 DEBUG Checking readiness of task: 2123 / 0x46620a0
Jul 07 20:46:23-080872 util-scheduler-8620 DEBUG Checking readiness of task: 2122 / 0x4d5c418
Jul 07 20:46:23-081065 util-scheduler-8620 DEBUG Checking readiness of task: 2121 / 0x4d5e5d8
Jul 07 20:46:23-081288 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-081482 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-081674 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-081866 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-082057 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-082252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-082442 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-082637 util-scheduler-8620 DEBUG Running task: 2121 / 0x4d5e5d8
Jul 07 20:46:23-082825 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:23-083005 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-083179 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-083431 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:23-083638 util-scheduler-8620 DEBUG Adding task: 2126 / 0x4d5e5d8
Jul 07 20:46:23-083844 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:23-084142 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:23-084344 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:23-084544 util-scheduler-8620 DEBUG Running task: 2122 / 0x4d5c418
Jul 07 20:46:23-084728 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:23-084905 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-085097 util-server-nc-8620 DEBUG Copying message of type 285 and size 12 from pending queue to transmission buffer
Jul 07 20:46:23-085436 util-8620 DEBUG Connection transmitted 12/12 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:23-085646 util-scheduler-8620 DEBUG Running task: 2125 / 0x46620a0
Jul 07 20:46:23-085832 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:23-086008 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-086179 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-086359 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:23-086557 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:23-086746 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:23-087053 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:23-087312 util-scheduler-8620 DEBUG Checking readiness of task: 2126 / 0x4d5e5d8
Jul 07 20:46:23-087507 util-scheduler-8620 DEBUG Checking readiness of task: 2123 / 0x46620a0
Jul 07 20:46:23-087724 util-scheduler-8620 DEBUG Checking readiness of task: 2057 / 0x4d5c418
Jul 07 20:46:23-087917 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-088109 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-088301 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-088492 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-088682 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-088873 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-089065 util-scheduler-8620 DEBUG Running task: 2057 / 0x4d5c418
Jul 07 20:46:23-089474 util-8620 DEBUG receive_ready read 20/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:46:23-089684 util-8620 DEBUG Server receives 20 bytes from `<unbound UNIX client>'.
Jul 07 20:46:23-089879 util-8620 DEBUG Server-mst receives 20 bytes with 0 bytes already in private buffer
Jul 07 20:46:23-090066 util-8620 DEBUG Server-mst has 20 bytes left in inbound buffer
Jul 07 20:46:23-090251 util-8620 DEBUG Tokenizer gives server message of type 286 from client
Jul 07 20:46:23-090441 util-8620 DEBUG Server schedules transmission of 8-byte message of type 286 to client.
Jul 07 20:46:23-090664 util-scheduler-8620 DEBUG Adding task: 2127 / 0x4d5c578
Jul 07 20:46:23-090846 cadet-loc-8620 DEBUG 
Jul 07 20:46:23-091014 cadet-loc-8620 DEBUG Got a local ACK
Jul 07 20:46:23-091190 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:23-091371 cadet-loc-8620 DEBUG   on channel 80000003
Jul 07 20:46:23-091555 cadet-loc-8620 DEBUG    -- ch 0x5e336a0
Jul 07 20:46:23-091735 cadet-chn-8620 DEBUG send_buffered_data
Jul 07 20:46:23-091947 cadet-chn-8620 DEBUG send_buffered_data END
Jul 07 20:46:23-092174 cadet-tun-8620 DEBUG Tunnel send connection ACKs on D3TJ
Jul 07 20:46:23-092362 cadet-tun-8620 DEBUG   buffer 64
Jul 07 20:46:23-092554 cadet-tun-8620 DEBUG   allowed 65
Jul 07 20:46:23-092754 util-scheduler-8620 DEBUG Canceling task: 2127 / 0x4d5c578
Jul 07 20:46:23-092955 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:23-093148 util-8620 DEBUG Server-mst has 12 bytes left in inbound buffer
Jul 07 20:46:23-093479 util-8620 DEBUG Server-mst leaves 12 bytes in private buffer
Jul 07 20:46:23-093678 util-8620 DEBUG Server processes additional messages instantly.
Jul 07 20:46:23-093862 util-8620 DEBUG Server-mst receives 0 bytes with 12 bytes already in private buffer
Jul 07 20:46:23-094051 util-8620 DEBUG Tokenizer gives server message of type 285 from client
Jul 07 20:46:23-094239 util-8620 DEBUG Server schedules transmission of 12-byte message of type 285 to client.
Jul 07 20:46:23-094461 util-scheduler-8620 DEBUG Adding task: 2128 / 0x4d5c578
Jul 07 20:46:23-094644 cadet-loc-8620 DEBUG Got data from a client!
Jul 07 20:46:23-094819 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:46:23-094996 cadet-loc-8620 DEBUG   on channel 80000003
Jul 07 20:46:23-095178 cadet-chn-8620 DEBUG   sending on channel...
Jul 07 20:46:23-095431 cadet-chn-8620 INFO ===> {              DATA} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-095632 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:46:23-095836 cadet-chn-8620 DEBUG !!! SAVE 2 {              DATA}
Jul 07 20:46:23-096023 cadet-chn-8620 DEBUG   at 0x54ea370
Jul 07 20:46:23-096203 cadet-chn-8620 DEBUG   new chq: 0x54ea2f0
Jul 07 20:46:23-096407 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:23-096607 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:23-096788 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-096971 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:23-097156 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-097357 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:23-097528 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-097767 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-097939 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-098176 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-098420 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-098604 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-098911 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:23-099084 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-099269 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:23-103239 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:23-103983 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:23-104173 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-104362 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:23-107669 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:23-107991 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:23-108184 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:23-108416 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:23-108597 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:23-108825 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-109027 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:23-109347 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (96 bytes)
Jul 07 20:46:23-109556 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:23-109744 cadet-con-8620 DEBUG last pid sent 7
Jul 07 20:46:23-109924 cadet-con-8620 DEBUG      ack recv 71
Jul 07 20:46:23-110106 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 2
Jul 07 20:46:23-110347 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:23-110565 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:23-111568 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 96)
Jul 07 20:46:23-111819 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:23-112063 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-112255 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:23-112435 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-112643 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:46:23-112850 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:23-113027 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:23-113231 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:23-113599 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-114027 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:46:23-114353 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:23-114651 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-114849 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:23-115026 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:23-115259 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:23-115454 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:23-115629 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:23-115827 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:23-116036 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:23-116215 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-116397 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:23-116578 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-116754 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:23-116922 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-117142 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-117338 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-117570 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:23-117841 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-118025 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-118198 cadet-chn-8620 DEBUG GMCH allow
Jul 07 20:46:23-118373 cadet-chn-8620 DEBUG  gap ok: 2 - 3
Jul 07 20:46:23-118574 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:23-118749 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-118928 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:23-119106 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-119280 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:23-119447 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-119657 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-119825 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-120051 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:23-120293 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-120475 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-120647 cadet-chn-8620 DEBUG  buffer space 21, allowing
Jul 07 20:46:23-120885 cadet-chn-8620 DEBUG   sending FWD ack to client on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:23-121070 cadet-loc-8620 DEBUG send local FWD ack on 80000003 towards 0x4d5c6d8
Jul 07 20:46:23-121302 util-server-nc-8620 DEBUG Adding message of type 286 and size 8 to pending queue (which has 1 entries)
Jul 07 20:46:23-121508 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:23-121724 util-scheduler-8620 DEBUG Adding task: 2129 / 0x4d5c418
Jul 07 20:46:23-121905 cadet-loc-8620 DEBUG receive done OK
Jul 07 20:46:23-122091 util-scheduler-8620 DEBUG Canceling task: 2128 / 0x4d5c578
Jul 07 20:46:23-122286 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:46:23-122467 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:46:23-122671 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:46:23-122878 util-scheduler-8620 DEBUG Adding task: 2130 / 0x4d5c418
Jul 07 20:46:23-123078 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:46:23-123314 util-scheduler-8620 DEBUG Running task: 2126 / 0x4d5e5d8
Jul 07 20:46:23-123502 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:23-123680 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-123850 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-124081 util-8620 DEBUG Transmitting message of type 168 and size 38 to statistics service.
Jul 07 20:46:23-125090 util-8620 DEBUG Connection transmitted 38/38 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:23-125405 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:23-125608 util-scheduler-8620 DEBUG Checking readiness of task: 2129 / 0x4d5c418
Jul 07 20:46:23-125807 util-scheduler-8620 DEBUG Checking readiness of task: 2123 / 0x46620a0
Jul 07 20:46:23-126004 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-126200 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-126396 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-126592 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-126788 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-126979 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-127185 util-scheduler-8620 DEBUG Running task: 2129 / 0x4d5c418
Jul 07 20:46:23-127461 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:23-128055 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-128256 util-server-nc-8620 DEBUG Copying message of type 286 and size 8 from pending queue to transmission buffer
Jul 07 20:46:23-128548 util-8620 DEBUG Connection transmitted 8/8 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:23-524491 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:23-524873 util-scheduler-8620 DEBUG Checking readiness of task: 2123 / 0x46620a0
Jul 07 20:46:23-525072 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-525296 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-525489 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-525682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-525872 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-526062 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-526258 util-scheduler-8620 DEBUG Running task: 2123 / 0x46620a0
Jul 07 20:46:23-526685 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:23-526946 util-scheduler-8620 DEBUG Adding task: 2131 / 0x4662248
Jul 07 20:46:23-527230 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:23-527423 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-527614 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-527804 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-527994 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-528183 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-528372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-528565 util-scheduler-8620 DEBUG Running task: 2131 / 0x4662248
Jul 07 20:46:23-528757 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:23-528957 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:23-529211 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:23-529479 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:23-529723 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:23-529951 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:23-530160 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:23-530406 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:23-530617 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:23-530806 cadet-con-8620 DEBUG  PID 13 (expected 13+)
Jul 07 20:46:23-530987 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:23-531176 util-scheduler-8620 DEBUG Canceling task: 2062 / 0x4d707d0
Jul 07 20:46:23-531400 util-scheduler-8620 DEBUG Adding task: 2132 / 0x4d707d0
Jul 07 20:46:23-531580 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:23-531839 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:23-532057 util-scheduler-8620 DEBUG Adding task: 2133 / 0x4d5e5d8
Jul 07 20:46:23-532243 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:23-532410 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:23-536222 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:23-537800 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:23-538101 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:23-540966 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:23-541167 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:23-542737 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:23-544441 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:23-545414 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:23-545643 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:23-545827 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:23-546013 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:23-546239 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:23-546418 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:23-546603 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:23-546864 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:23-547108 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:23-547309 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:23-547607 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:23-547793 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-547992 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:23-551886 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:23-552536 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:23-552714 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:23-552902 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:23-556635 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:23-556886 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:23-557069 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:23-557316 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:23-557509 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:23-557785 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:23-557982 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:23-558159 cadet-con-8620 DEBUG last pid sent 9
Jul 07 20:46:23-558332 cadet-con-8620 DEBUG      ack recv 73
Jul 07 20:46:23-558523 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:23-558701 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:23-558937 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:23-559145 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:23-559457 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:23-559657 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:23-559881 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:23-560063 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 9
Jul 07 20:46:23-560238 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-560442 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:23-560659 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:23-560888 util-scheduler-8620 DEBUG Adding task: 2134 / 0x4d6ff98
Jul 07 20:46:23-561069 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:23-561308 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:23-561501 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:23-562859 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:23-563211 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:23-563409 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:23-563588 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:23-563790 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:23-564288 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:23-564471 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:23-564646 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:23-564820 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:23-565042 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:23-565246 cadet-con-8620 DEBUG  ACK 77
Jul 07 20:46:23-565429 cadet-con-8620 DEBUG  last pid 13, last ack 76, qmax 11, q 0
Jul 07 20:46:23-565696 cadet-con-8620 INFO --> {               ACK} ( 77) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:23-565886 cadet-con-8620 DEBUG  ack 77
Jul 07 20:46:23-566064 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:23-566298 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:23-566504 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:23-566795 cadet-p2p-8620 INFO que {               ACK} ( 77) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:23-567020 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:23-567245 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:23-567428 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 9
Jul 07 20:46:23-567602 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:23-567803 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:23-568005 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:23-568180 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:23-568355 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:23-568593 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:23-568777 cadet-p2p-8620 DEBUG QQQ    payload , 77
Jul 07 20:46:23-568952 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:23-569186 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:23-569405 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:23-569583 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:23-569781 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:23-569982 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:23-570198 util-scheduler-8620 DEBUG Adding task: 2135 / 0x46620a0
Jul 07 20:46:23-570474 util-scheduler-8620 DEBUG Checking readiness of task: 2135 / 0x46620a0
Jul 07 20:46:23-570688 util-scheduler-8620 DEBUG Checking readiness of task: 2133 / 0x4d5e5d8
Jul 07 20:46:23-570882 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:23-571073 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-571263 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-571454 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-571644 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-571833 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-572023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-572216 util-scheduler-8620 DEBUG Running task: 2133 / 0x4d5e5d8
Jul 07 20:46:23-572403 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:23-572582 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-572754 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-573002 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:23-573240 util-scheduler-8620 DEBUG Adding task: 2136 / 0x4d5e5d8
Jul 07 20:46:23-573447 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:23-573842 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:23-574047 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:23-574246 util-scheduler-8620 DEBUG Running task: 2134 / 0x4d6ff98
Jul 07 20:46:23-574459 util-scheduler-8620 DEBUG Adding task: 2137 / 0x4d6ff98
Jul 07 20:46:23-574683 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:23-574879 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:23-575076 util-scheduler-8620 DEBUG Adding task: 2138 / 0x46620a0
Jul 07 20:46:23-575319 util-scheduler-8620 DEBUG Checking readiness of task: 2138 / 0x46620a0
Jul 07 20:46:23-575513 util-scheduler-8620 DEBUG Checking readiness of task: 2136 / 0x4d5e5d8
Jul 07 20:46:23-575705 util-scheduler-8620 DEBUG Checking readiness of task: 2135 / 0x46620a0
Jul 07 20:46:23-575895 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:23-576085 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:23-576452 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:23-576646 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:23-576868 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:23-577059 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:23-577270 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:23-577462 util-scheduler-8620 DEBUG Running task: 2136 / 0x4d5e5d8
Jul 07 20:46:23-577646 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:23-577822 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-577991 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-578205 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:23-578533 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:23-578748 util-scheduler-8620 DEBUG Running task: 2138 / 0x46620a0
Jul 07 20:46:23-578932 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:23-579107 util-8620 DEBUG process_notify is running
Jul 07 20:46:23-579275 util-8620 DEBUG client_notify is running
Jul 07 20:46:23-579454 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:23-579649 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:23-579839 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:23-580141 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:24-113635 util-scheduler-8620 DEBUG Checking readiness of task: 2135 / 0x46620a0
Jul 07 20:46:24-114023 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-114221 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-114418 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-114610 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-114802 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-114992 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-115182 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-115378 util-scheduler-8620 DEBUG Running task: 2135 / 0x46620a0
Jul 07 20:46:24-115805 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:24-116062 util-scheduler-8620 DEBUG Adding task: 2139 / 0x4662248
Jul 07 20:46:24-116341 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-116534 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-116725 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-116915 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-117106 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-117324 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-117514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-117703 util-scheduler-8620 DEBUG Running task: 2139 / 0x4662248
Jul 07 20:46:24-117895 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:24-118094 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:24-118327 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:24-118537 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:24-118744 util-scheduler-8620 DEBUG Adding task: 2140 / 0x46620a0
Jul 07 20:46:24-118931 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:24-119136 util-scheduler-8620 DEBUG Adding task: 2141 / 0x46620a0
Jul 07 20:46:24-119381 util-scheduler-8620 DEBUG Checking readiness of task: 2141 / 0x46620a0
Jul 07 20:46:24-119576 util-scheduler-8620 DEBUG Checking readiness of task: 2140 / 0x46620a0
Jul 07 20:46:24-119799 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-119989 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-120179 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-120368 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-120557 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-120746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-120935 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-121127 util-scheduler-8620 DEBUG Running task: 2140 / 0x46620a0
Jul 07 20:46:24-121700 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:24-121885 util-8620 DEBUG process_notify is running
Jul 07 20:46:24-122058 util-8620 DEBUG client_notify is running
Jul 07 20:46:24-122251 util-scheduler-8620 DEBUG Canceling task: 2137 / 0x4d6ff98
Jul 07 20:46:24-122478 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:24-122985 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:24-123231 cadet-p2p-8620 DEBUG Checking 0x552e380 towards CMHCKRVP (->V8XX)
Jul 07 20:46:24-123465 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:24-123644 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:24-123913 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:24-124190 cadet-p2p-8620 INFO snd {               ACK} ( 77) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:24-124384 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:24-124565 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:24-124754 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:24-124928 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:24-125111 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:24-125312 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:24-125533 cadet-p2p-8620 DEBUG Checking 0x552e080 towards CMHCKRVP (->V8XX)
Jul 07 20:46:24-125765 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:24-125948 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 9
Jul 07 20:46:24-126123 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:24-126352 cadet-p2p-8620 DEBUG Checking 0x552e080 towards CMHCKRVP (->V8XX)
Jul 07 20:46:24-126582 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:24-126763 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 9
Jul 07 20:46:24-126935 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:24-127101 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:24-127306 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:24-127521 util-scheduler-8620 DEBUG Adding task: 2142 / 0x4d6ff98
Jul 07 20:46:24-127700 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:24-127876 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:24-128075 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:24-128250 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:24-128424 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:24-128666 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:24-128861 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:24-129038 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:24-129256 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:24-129462 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:24-129645 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:24-129850 util-scheduler-8620 DEBUG Adding task: 2143 / 0x4d6ff98
Jul 07 20:46:24-130069 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:24-130266 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:24-130469 util-scheduler-8620 DEBUG Adding task: 2144 / 0x46620a0
Jul 07 20:46:24-130694 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:24-131508 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:24-131711 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:24-131966 util-scheduler-8620 DEBUG Checking readiness of task: 2144 / 0x46620a0
Jul 07 20:46:24-132160 util-scheduler-8620 DEBUG Checking readiness of task: 2141 / 0x46620a0
Jul 07 20:46:24-132352 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-132543 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-132735 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-133004 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-133220 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-133412 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-133601 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-133793 util-scheduler-8620 DEBUG Running task: 2144 / 0x46620a0
Jul 07 20:46:24-133978 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:24-134154 util-8620 DEBUG process_notify is running
Jul 07 20:46:24-134324 util-8620 DEBUG client_notify is running
Jul 07 20:46:24-134503 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:24-134731 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:24-134919 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:24-135201 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:24-135409 util-scheduler-8620 DEBUG Running task: 2142 / 0x4d6ff98
Jul 07 20:46:24-135603 util-scheduler-8620 DEBUG Canceling task: 2143 / 0x4d6ff98
Jul 07 20:46:24-135819 util-scheduler-8620 DEBUG Adding task: 2145 / 0x4d6ff98
Jul 07 20:46:24-136036 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:24-136231 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:24-136430 util-scheduler-8620 DEBUG Adding task: 2146 / 0x46620a0
Jul 07 20:46:24-136670 util-scheduler-8620 DEBUG Checking readiness of task: 2146 / 0x46620a0
Jul 07 20:46:24-136863 util-scheduler-8620 DEBUG Checking readiness of task: 2141 / 0x46620a0
Jul 07 20:46:24-137055 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-137268 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-137459 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-137649 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-137838 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-138027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-138215 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-138406 util-scheduler-8620 DEBUG Running task: 2146 / 0x46620a0
Jul 07 20:46:24-138593 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:24-138768 util-8620 DEBUG process_notify is running
Jul 07 20:46:24-138937 util-8620 DEBUG client_notify is running
Jul 07 20:46:24-139113 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:24-139302 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:24-139488 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:24-139767 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:24-252200 util-scheduler-8620 DEBUG Checking readiness of task: 2141 / 0x46620a0
Jul 07 20:46:24-252577 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-252802 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-252997 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-253219 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-253414 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-253606 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-253797 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-253995 util-scheduler-8620 DEBUG Running task: 2141 / 0x46620a0
Jul 07 20:46:24-254425 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:24-254680 util-scheduler-8620 DEBUG Adding task: 2147 / 0x4662248
Jul 07 20:46:24-254962 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-255156 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-255347 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-255537 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-255739 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-255930 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-256119 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-256308 util-scheduler-8620 DEBUG Running task: 2147 / 0x4662248
Jul 07 20:46:24-256499 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:24-256698 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:24-256929 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:24-257136 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:24-257371 util-scheduler-8620 DEBUG Adding task: 2148 / 0x46620a0
Jul 07 20:46:24-257559 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:24-257764 util-scheduler-8620 DEBUG Adding task: 2149 / 0x46620a0
Jul 07 20:46:24-258008 util-scheduler-8620 DEBUG Checking readiness of task: 2149 / 0x46620a0
Jul 07 20:46:24-258200 util-scheduler-8620 DEBUG Checking readiness of task: 2148 / 0x46620a0
Jul 07 20:46:24-258662 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-258858 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-259050 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-259241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-259431 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-259621 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-259810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-260002 util-scheduler-8620 DEBUG Running task: 2148 / 0x46620a0
Jul 07 20:46:24-260188 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:24-260366 util-8620 DEBUG process_notify is running
Jul 07 20:46:24-260539 util-8620 DEBUG client_notify is running
Jul 07 20:46:24-260730 util-scheduler-8620 DEBUG Canceling task: 2145 / 0x4d6ff98
Jul 07 20:46:24-260957 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:24-261178 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:24-261445 cadet-p2p-8620 DEBUG Checking 0x552e080 towards CMHCKRVP (->V8XX)
Jul 07 20:46:24-261678 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:24-261860 cadet-con-8620 DEBUG  last ack recv: 73, last pid sent: 9
Jul 07 20:46:24-262036 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:24-262258 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:24-262435 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:24-262627 cadet-p2p-8620 DEBUG   payload ID 10
Jul 07 20:46:24-262914 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:24-263109 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:24-263290 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:24-263478 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:24-263666 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:24-263895 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:24-264070 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:24-264242 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:24-264413 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:24-264858 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:24-265039 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:24-265643 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:24-265833 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:24-266018 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:24-266200 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:24-266378 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:24-266548 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:24-266715 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:24-266949 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:24-267132 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:24-267313 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:24-267502 util-scheduler-8620 DEBUG Canceling task: 2038 / 0x4d707d0
Jul 07 20:46:24-267717 util-scheduler-8620 DEBUG Adding task: 2150 / 0x4d707d0
Jul 07 20:46:24-267984 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:24-268163 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:24-268342 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 10
Jul 07 20:46:24-268515 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:24-268701 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:24-268900 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:24-269074 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:24-269273 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:24-269475 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:24-269680 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:24-269863 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:24-270043 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:24-270234 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:24-271622 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:24-724750 util-scheduler-8620 DEBUG Checking readiness of task: 2149 / 0x46620a0
Jul 07 20:46:24-725133 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-725359 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-725554 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-725747 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-725940 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-726131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-726321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-726517 util-scheduler-8620 DEBUG Running task: 2149 / 0x46620a0
Jul 07 20:46:24-726942 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:24-727198 util-scheduler-8620 DEBUG Adding task: 2151 / 0x4662248
Jul 07 20:46:24-727477 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:24-727670 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:24-727890 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:24-728082 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:24-728272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:24-728462 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:24-728651 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:24-728844 util-scheduler-8620 DEBUG Running task: 2151 / 0x4662248
Jul 07 20:46:24-729035 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:24-729259 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:24-729491 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:24-729758 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:24-730013 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:24-730221 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:24-730405 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:24-730579 cadet-con-8620 DEBUG   ACK 74 (was 73)
Jul 07 20:46:24-730809 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:24-731085 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:24-731291 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:24-731472 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:24-731651 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:24-731862 util-scheduler-8620 DEBUG Adding task: 2152 / 0x46620a0
Jul 07 20:46:26-619803 util-scheduler-8620 DEBUG Checking readiness of task: 2152 / 0x46620a0
Jul 07 20:46:26-620176 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:26-620372 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:26-620566 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:26-620757 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:26-620948 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:26-621139 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:26-621350 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:26-621544 util-scheduler-8620 DEBUG Running task: 895 / 0x4d68be8
Jul 07 20:46:26-621820 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:46:26-621998 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:46:26-622252 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:46:26-622441 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:46:26-622677 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:46:26-622885 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:46:26-623190 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:46:26-623389 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:26-623616 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:46:26-623799 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:46:26-623975 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:26-624183 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:46:26-624398 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:46:26-624621 util-scheduler-8620 DEBUG Adding task: 2153 / 0x4d683b0
Jul 07 20:46:26-624801 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:26-625006 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:46:26-625181 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:26-625378 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:46:26-625617 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:46:26-625830 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:46:26-626007 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:26-626210 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:46:26-626467 util-scheduler-8620 DEBUG Checking readiness of task: 2152 / 0x46620a0
Jul 07 20:46:26-626659 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:26-626849 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:26-627039 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:26-627228 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:26-627417 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:26-627606 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:26-627794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:26-627984 util-scheduler-8620 DEBUG Running task: 2153 / 0x4d683b0
Jul 07 20:46:26-628196 util-scheduler-8620 DEBUG Adding task: 2154 / 0x4d683b0
Jul 07 20:46:26-628419 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:46:26-628622 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:26-628831 util-scheduler-8620 DEBUG Adding task: 2155 / 0x46620a0
Jul 07 20:46:26-629073 util-scheduler-8620 DEBUG Checking readiness of task: 2155 / 0x46620a0
Jul 07 20:46:26-629309 util-scheduler-8620 DEBUG Checking readiness of task: 2152 / 0x46620a0
Jul 07 20:46:26-629500 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:26-629690 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:26-629880 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:26-630070 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:26-630259 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:26-630448 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:26-630636 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:26-630827 util-scheduler-8620 DEBUG Running task: 2155 / 0x46620a0
Jul 07 20:46:26-631012 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:26-631190 util-8620 DEBUG process_notify is running
Jul 07 20:46:26-631375 util-8620 DEBUG client_notify is running
Jul 07 20:46:26-631554 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:26-631752 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:26-631942 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:26-632198 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:27-370070 util-scheduler-8620 DEBUG Checking readiness of task: 2152 / 0x46620a0
Jul 07 20:46:27-370460 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-370658 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-370853 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-371046 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-371239 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-371431 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-371622 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-371819 util-scheduler-8620 DEBUG Running task: 2152 / 0x46620a0
Jul 07 20:46:27-372246 util-8620 DEBUG receive_ready read 80/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:27-372506 util-scheduler-8620 DEBUG Adding task: 2156 / 0x4662248
Jul 07 20:46:27-372789 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-373016 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-373238 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-373430 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-373620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-373811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-374000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-374190 util-scheduler-8620 DEBUG Running task: 2156 / 0x4662248
Jul 07 20:46:27-374381 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:27-374583 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:27-374853 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:27-375060 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:27-375268 util-scheduler-8620 DEBUG Adding task: 2157 / 0x46620a0
Jul 07 20:46:27-375481 util-scheduler-8620 DEBUG Adding task: 2158 / 0x4662248
Jul 07 20:46:27-375722 util-scheduler-8620 DEBUG Checking readiness of task: 2157 / 0x46620a0
Jul 07 20:46:27-375916 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-376106 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-376296 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-376486 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-376675 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-376864 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-377052 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-377269 util-scheduler-8620 DEBUG Running task: 2157 / 0x46620a0
Jul 07 20:46:27-377457 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:27-377635 util-8620 DEBUG process_notify is running
Jul 07 20:46:27-377806 util-8620 DEBUG client_notify is running
Jul 07 20:46:27-377997 util-scheduler-8620 DEBUG Canceling task: 2124 / 0x5e2b838
Jul 07 20:46:27-378224 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 40 bytes.
Jul 07 20:46:27-378445 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:27-378685 cadet-p2p-8620 DEBUG Checking 0x54abf48 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-378919 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:27-379096 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:27-379287 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:27-379554 cadet-p2p-8620 INFO snd {               ACK} ( 71) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:27-379749 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:27-379928 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:27-380116 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:27-380290 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:27-380474 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 3
Jul 07 20:46:27-380648 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:27-380869 cadet-p2p-8620 DEBUG Checking 0x5509688 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-381101 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-381310 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:27-381486 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:27-381713 cadet-p2p-8620 DEBUG Checking 0x5509688 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-381942 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-382123 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:27-382295 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:27-382461 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:27-382667 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `D3TJ'
Jul 07 20:46:27-382878 util-scheduler-8620 DEBUG Adding task: 2159 / 0x5e2b838
Jul 07 20:46:27-383075 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:27-383252 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:27-383451 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:27-383626 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:27-383800 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:27-384039 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-384233 cadet-p2p-8620 DEBUG QQQ    payload {          DATA_ACK}, 1
Jul 07 20:46:27-384410 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:46:27-384645 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:27-384838 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:27-385015 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:27-385236 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:27-385442 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:27-385625 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:27-385828 util-scheduler-8620 DEBUG Adding task: 2160 / 0x5e2b838
Jul 07 20:46:27-386046 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:27-386240 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:27-386441 util-scheduler-8620 DEBUG Adding task: 2161 / 0x46620a0
Jul 07 20:46:27-386641 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:27-386892 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:27-387088 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:27-387285 util-scheduler-8620 DEBUG Running task: 2158 / 0x4662248
Jul 07 20:46:27-387474 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:27-387666 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:27-387876 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:46:27-388054 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:27-388232 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:27-388436 util-scheduler-8620 DEBUG Adding task: 2162 / 0x46620a0
Jul 07 20:46:27-388679 util-scheduler-8620 DEBUG Checking readiness of task: 2162 / 0x46620a0
Jul 07 20:46:27-388873 util-scheduler-8620 DEBUG Checking readiness of task: 2161 / 0x46620a0
Jul 07 20:46:27-389064 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-389280 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-389471 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-389661 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-389850 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-390040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-390228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-390432 util-scheduler-8620 DEBUG Running task: 2161 / 0x46620a0
Jul 07 20:46:27-390616 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:27-390791 util-8620 DEBUG process_notify is running
Jul 07 20:46:27-390961 util-8620 DEBUG client_notify is running
Jul 07 20:46:27-391138 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:27-391347 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:27-391544 util-scheduler-8620 DEBUG Adding task: 2163 / 0x46620a0
Jul 07 20:46:27-391740 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:27-391982 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:27-392175 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:27-392386 util-scheduler-8620 DEBUG Running task: 2159 / 0x5e2b838
Jul 07 20:46:27-392578 util-scheduler-8620 DEBUG Canceling task: 2160 / 0x5e2b838
Jul 07 20:46:27-392790 util-scheduler-8620 DEBUG Adding task: 2164 / 0x5e2b838
Jul 07 20:46:27-393004 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:27-393181 core-api-8620 DEBUG Request pending, not processing queue
Jul 07 20:46:27-393439 util-scheduler-8620 DEBUG Checking readiness of task: 2163 / 0x46620a0
Jul 07 20:46:27-393632 util-scheduler-8620 DEBUG Checking readiness of task: 2162 / 0x46620a0
Jul 07 20:46:27-393823 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-394013 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-394203 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-394393 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-394582 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-394771 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-394961 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-395151 util-scheduler-8620 DEBUG Running task: 2163 / 0x46620a0
Jul 07 20:46:27-395335 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:27-395509 util-8620 DEBUG process_notify is running
Jul 07 20:46:27-395679 util-8620 DEBUG client_notify is running
Jul 07 20:46:27-395855 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:27-396059 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:27-396256 util-scheduler-8620 DEBUG Adding task: 2165 / 0x46620a0
Jul 07 20:46:27-396452 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:27-396693 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:27-396887 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:27-397123 util-scheduler-8620 DEBUG Checking readiness of task: 2165 / 0x46620a0
Jul 07 20:46:27-397342 util-scheduler-8620 DEBUG Checking readiness of task: 2162 / 0x46620a0
Jul 07 20:46:27-397533 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:27-397723 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:27-397913 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:27-398102 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:27-398295 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:27-398483 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:27-398672 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:27-398862 util-scheduler-8620 DEBUG Running task: 2165 / 0x46620a0
Jul 07 20:46:27-399045 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:27-399219 util-8620 DEBUG process_notify is running
Jul 07 20:46:27-399388 util-8620 DEBUG client_notify is running
Jul 07 20:46:27-399569 util-scheduler-8620 DEBUG Canceling task: 2154 / 0x4d683b0
Jul 07 20:46:27-399793 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:46:27-400005 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:46:27-400233 cadet-p2p-8620 DEBUG Checking 0x545b260 towards KT5Q8VM8 (->P00P)
Jul 07 20:46:27-400462 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:46:27-400640 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:27-400809 cadet-p2p-8620 DEBUG   path create
Jul 07 20:46:27-400980 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:46:27-401159 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:46:27-401444 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:46:27-401652 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:27-401829 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:27-402015 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:46:27-402194 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:46:27-402402 util-scheduler-8620 DEBUG Adding task: 2166 / 0x4d68be8
Jul 07 20:46:27-402640 cadet-con-8620 DEBUG next keepalive in 64 s
Jul 07 20:46:27-402809 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:27-402986 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:27-403185 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:46:27-403358 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:27-403532 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:27-403728 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:46:27-403931 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:46:27-404113 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:27-404290 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:27-404478 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:27-404725 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:28-216062 util-scheduler-8620 DEBUG Checking readiness of task: 2162 / 0x46620a0
Jul 07 20:46:28-216472 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-216670 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-216864 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-217057 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-217290 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-217483 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-217674 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-217870 util-scheduler-8620 DEBUG Running task: 2162 / 0x46620a0
Jul 07 20:46:28-218313 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:28-218570 util-scheduler-8620 DEBUG Adding task: 2167 / 0x4662248
Jul 07 20:46:28-218850 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-219043 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-219235 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-219447 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-219638 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-219828 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-220020 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-220211 util-scheduler-8620 DEBUG Running task: 2167 / 0x4662248
Jul 07 20:46:28-220402 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:28-220619 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:28-220852 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:28-221119 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:28-221387 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:28-221639 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:28-221848 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:28-222094 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:28-222304 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:28-222494 cadet-con-8620 DEBUG  PID 14 (expected 14+)
Jul 07 20:46:28-222694 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:28-222918 util-scheduler-8620 DEBUG Canceling task: 2132 / 0x4d707d0
Jul 07 20:46:28-223159 util-scheduler-8620 DEBUG Adding task: 2168 / 0x4d707d0
Jul 07 20:46:28-223340 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:28-223602 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:28-223841 util-scheduler-8620 DEBUG Adding task: 2169 / 0x4d5e5d8
Jul 07 20:46:28-224027 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:28-224195 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:28-227884 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:28-228813 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:28-229032 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:28-232444 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:28-232655 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:28-233058 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:28-233409 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:28-233624 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:28-233826 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:28-234006 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:28-234207 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:28-234405 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:28-234583 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:28-234754 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:28-234921 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:28-235157 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:28-235341 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:28-235652 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:28-235825 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:28-236025 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:28-239157 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:28-240307 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:28-240487 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:28-240675 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:28-243416 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:28-243679 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:28-243865 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:28-244088 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:28-244284 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:28-244557 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:28-244756 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:28-244934 cadet-con-8620 DEBUG last pid sent 10
Jul 07 20:46:28-245108 cadet-con-8620 DEBUG      ack recv 74
Jul 07 20:46:28-245306 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:28-245484 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:28-245719 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:28-245927 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:28-246239 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:28-246439 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:28-246664 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:28-246849 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:28-247026 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:28-247231 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:28-247448 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:28-247676 util-scheduler-8620 DEBUG Adding task: 2170 / 0x4d6ff98
Jul 07 20:46:28-247858 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:28-248062 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:28-248239 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:28-248439 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:28-248679 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:28-248874 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:28-249052 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:28-249273 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:28-249508 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:28-249685 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:28-249858 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:28-250028 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:28-250246 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:28-250425 cadet-con-8620 DEBUG  ACK 78
Jul 07 20:46:28-250604 cadet-con-8620 DEBUG  last pid 14, last ack 77, qmax 11, q 0
Jul 07 20:46:28-250868 cadet-con-8620 INFO --> {               ACK} ( 78) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:28-251056 cadet-con-8620 DEBUG  ack 78
Jul 07 20:46:28-251234 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:28-251467 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:28-251673 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:28-251962 cadet-p2p-8620 INFO que {               ACK} ( 78) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:28-252159 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:28-252380 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:28-252562 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:28-252734 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:28-252933 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:28-253135 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:28-253347 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:28-253522 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:28-253757 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:28-253938 cadet-p2p-8620 DEBUG QQQ    payload , 78
Jul 07 20:46:28-254112 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:28-254344 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:28-254536 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:28-254711 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:28-254907 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:28-255089 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:28-255299 util-scheduler-8620 DEBUG Adding task: 2171 / 0x46620a0
Jul 07 20:46:28-255575 util-scheduler-8620 DEBUG Checking readiness of task: 2171 / 0x46620a0
Jul 07 20:46:28-255773 util-scheduler-8620 DEBUG Checking readiness of task: 2169 / 0x4d5e5d8
Jul 07 20:46:28-255966 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-256155 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-256346 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-256536 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-256725 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-256914 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-257102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-257319 util-scheduler-8620 DEBUG Running task: 2169 / 0x4d5e5d8
Jul 07 20:46:28-257505 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:28-257684 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-257857 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-258102 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:28-258311 util-scheduler-8620 DEBUG Adding task: 2172 / 0x4d5e5d8
Jul 07 20:46:28-258515 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:28-258893 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:28-259094 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:28-259292 util-scheduler-8620 DEBUG Running task: 2170 / 0x4d6ff98
Jul 07 20:46:28-259506 util-scheduler-8620 DEBUG Adding task: 2173 / 0x4d6ff98
Jul 07 20:46:28-259730 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:28-259926 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:28-260122 util-scheduler-8620 DEBUG Adding task: 2174 / 0x46620a0
Jul 07 20:46:28-260366 util-scheduler-8620 DEBUG Checking readiness of task: 2174 / 0x46620a0
Jul 07 20:46:28-260560 util-scheduler-8620 DEBUG Checking readiness of task: 2172 / 0x4d5e5d8
Jul 07 20:46:28-260752 util-scheduler-8620 DEBUG Checking readiness of task: 2171 / 0x46620a0
Jul 07 20:46:28-260943 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-261132 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-261347 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-261538 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-261727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-261917 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-262105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-262295 util-scheduler-8620 DEBUG Running task: 2172 / 0x4d5e5d8
Jul 07 20:46:28-262478 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:28-262654 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-262825 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-263036 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:28-263274 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:28-263483 util-scheduler-8620 DEBUG Running task: 2174 / 0x46620a0
Jul 07 20:46:28-263667 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:28-263843 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-264013 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-264193 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:28-264388 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:28-264576 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:28-264889 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:28-308197 util-scheduler-8620 DEBUG Checking readiness of task: 2171 / 0x46620a0
Jul 07 20:46:28-308584 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-308784 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-308977 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-309169 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-309394 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-309585 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-309776 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-309972 util-scheduler-8620 DEBUG Running task: 2171 / 0x46620a0
Jul 07 20:46:28-310394 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:28-310650 util-scheduler-8620 DEBUG Adding task: 2175 / 0x4662248
Jul 07 20:46:28-310928 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-311123 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-311343 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-311534 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-311724 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-311913 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-312102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-312291 util-scheduler-8620 DEBUG Running task: 2175 / 0x4662248
Jul 07 20:46:28-312482 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:28-312681 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:28-312913 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:28-313119 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:28-313708 util-scheduler-8620 DEBUG Adding task: 2176 / 0x46620a0
Jul 07 20:46:28-313901 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:28-314107 util-scheduler-8620 DEBUG Adding task: 2177 / 0x46620a0
Jul 07 20:46:28-314355 util-scheduler-8620 DEBUG Checking readiness of task: 2177 / 0x46620a0
Jul 07 20:46:28-314813 util-scheduler-8620 DEBUG Checking readiness of task: 2176 / 0x46620a0
Jul 07 20:46:28-315012 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-315204 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-315396 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-315587 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-315854 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-316047 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-316237 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-316430 util-scheduler-8620 DEBUG Running task: 2176 / 0x46620a0
Jul 07 20:46:28-316616 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:28-316795 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-316968 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-317160 util-scheduler-8620 DEBUG Canceling task: 2173 / 0x4d6ff98
Jul 07 20:46:28-317413 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:28-317634 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:28-317874 cadet-p2p-8620 DEBUG Checking 0x5550cd8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:28-318109 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:28-318288 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:28-318483 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:28-318752 cadet-p2p-8620 INFO snd {               ACK} ( 78) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:28-318959 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:28-319141 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:28-319328 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:28-319502 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:28-319686 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:28-319861 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:28-320081 cadet-p2p-8620 DEBUG Checking 0x5550130 towards CMHCKRVP (->V8XX)
Jul 07 20:46:28-320313 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:28-320496 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:28-320760 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:28-320991 cadet-p2p-8620 DEBUG Checking 0x5550130 towards CMHCKRVP (->V8XX)
Jul 07 20:46:28-321246 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:28-321430 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:28-321602 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:28-321769 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:28-321996 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:28-322213 util-scheduler-8620 DEBUG Adding task: 2178 / 0x4d6ff98
Jul 07 20:46:28-322393 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:28-322571 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:28-322769 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:28-322947 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:28-323122 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:28-323361 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:28-323556 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:28-323733 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:28-323932 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:28-324136 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:28-324319 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:28-324521 util-scheduler-8620 DEBUG Adding task: 2179 / 0x4d6ff98
Jul 07 20:46:28-324738 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:28-324933 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:28-325135 util-scheduler-8620 DEBUG Adding task: 2180 / 0x46620a0
Jul 07 20:46:28-325362 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:28-326194 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:28-326396 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:28-326647 util-scheduler-8620 DEBUG Checking readiness of task: 2180 / 0x46620a0
Jul 07 20:46:28-326841 util-scheduler-8620 DEBUG Checking readiness of task: 2177 / 0x46620a0
Jul 07 20:46:28-327032 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-327222 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-327412 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-327602 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-327791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-327979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-328167 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-328358 util-scheduler-8620 DEBUG Running task: 2180 / 0x46620a0
Jul 07 20:46:28-328546 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:28-328722 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-328891 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-329070 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:28-329289 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:28-329478 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:28-329758 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:28-329965 util-scheduler-8620 DEBUG Running task: 2178 / 0x4d6ff98
Jul 07 20:46:28-330159 util-scheduler-8620 DEBUG Canceling task: 2179 / 0x4d6ff98
Jul 07 20:46:28-330373 util-scheduler-8620 DEBUG Adding task: 2181 / 0x4d6ff98
Jul 07 20:46:28-330590 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:28-330785 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:28-330981 util-scheduler-8620 DEBUG Adding task: 2182 / 0x46620a0
Jul 07 20:46:28-331220 util-scheduler-8620 DEBUG Checking readiness of task: 2182 / 0x46620a0
Jul 07 20:46:28-331413 util-scheduler-8620 DEBUG Checking readiness of task: 2177 / 0x46620a0
Jul 07 20:46:28-331650 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-331896 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-332105 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-332297 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-332486 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-332675 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-332865 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-333055 util-scheduler-8620 DEBUG Running task: 2182 / 0x46620a0
Jul 07 20:46:28-333261 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:28-333438 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-333606 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-333782 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:28-334038 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:28-334229 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:28-334521 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:28-444500 util-scheduler-8620 DEBUG Checking readiness of task: 2177 / 0x46620a0
Jul 07 20:46:28-444747 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-444943 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-445135 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-445356 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-445546 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-445736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-445926 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-446118 util-scheduler-8620 DEBUG Running task: 2177 / 0x46620a0
Jul 07 20:46:28-446525 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:28-446761 util-scheduler-8620 DEBUG Adding task: 2183 / 0x4662248
Jul 07 20:46:28-447015 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-447209 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-447400 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-447591 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-447780 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-447970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-448160 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-448349 util-scheduler-8620 DEBUG Running task: 2183 / 0x4662248
Jul 07 20:46:28-448541 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:28-448738 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:28-448955 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:28-449153 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:28-449379 util-scheduler-8620 DEBUG Adding task: 2184 / 0x46620a0
Jul 07 20:46:28-449564 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:28-449765 util-scheduler-8620 DEBUG Adding task: 2185 / 0x46620a0
Jul 07 20:46:28-450007 util-scheduler-8620 DEBUG Checking readiness of task: 2185 / 0x46620a0
Jul 07 20:46:28-450201 util-scheduler-8620 DEBUG Checking readiness of task: 2184 / 0x46620a0
Jul 07 20:46:28-450393 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:28-450583 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:28-450775 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:28-450977 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:28-451187 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:28-451379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:28-451568 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:28-451758 util-scheduler-8620 DEBUG Running task: 2184 / 0x46620a0
Jul 07 20:46:28-451942 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:28-452117 util-8620 DEBUG process_notify is running
Jul 07 20:46:28-452287 util-8620 DEBUG client_notify is running
Jul 07 20:46:28-452472 util-scheduler-8620 DEBUG Canceling task: 2181 / 0x4d6ff98
Jul 07 20:46:28-452692 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:28-452908 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:28-453141 cadet-p2p-8620 DEBUG Checking 0x5550130 towards CMHCKRVP (->V8XX)
Jul 07 20:46:28-453399 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:28-453581 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:28-453755 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:28-453975 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:28-454152 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:28-454326 cadet-p2p-8620 DEBUG   payload ID 11
Jul 07 20:46:28-454606 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:28-454800 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:28-454976 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:28-455162 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:28-455350 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:28-455578 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:28-455753 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:28-455925 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:28-456096 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:28-456293 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:28-456467 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:28-456667 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:28-456847 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:28-457029 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:28-457232 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:28-457410 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:28-457579 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:28-457745 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:28-457977 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:28-458162 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:28-458340 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:28-458528 util-scheduler-8620 DEBUG Canceling task: 2150 / 0x4d707d0
Jul 07 20:46:28-458739 util-scheduler-8620 DEBUG Adding task: 2186 / 0x4d707d0
Jul 07 20:46:28-458989 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:28-459166 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:28-459344 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 11
Jul 07 20:46:28-459516 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:28-459696 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:28-459895 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:28-460068 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:28-460241 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:28-460437 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:28-460640 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:28-460824 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:28-461002 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:28-461212 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:28-462726 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:29-307830 util-scheduler-8620 DEBUG Checking readiness of task: 2185 / 0x46620a0
Jul 07 20:46:29-308213 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:29-308410 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:29-308602 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:29-308793 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:29-308985 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:29-309175 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:29-309396 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:29-309591 util-scheduler-8620 DEBUG Running task: 2185 / 0x46620a0
Jul 07 20:46:29-310015 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:29-310271 util-scheduler-8620 DEBUG Adding task: 2187 / 0x4662248
Jul 07 20:46:29-310551 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:29-310744 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:29-310935 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:29-311124 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:29-311314 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:29-311504 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:29-311694 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:29-311883 util-scheduler-8620 DEBUG Running task: 2187 / 0x4662248
Jul 07 20:46:29-312074 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:29-312274 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:29-312503 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:29-312770 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:29-313026 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:29-313448 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:29-313639 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:29-313813 cadet-con-8620 DEBUG   ACK 75 (was 74)
Jul 07 20:46:29-314199 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:29-314436 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:29-314643 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:29-314827 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:29-315004 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:29-315294 util-scheduler-8620 DEBUG Adding task: 2188 / 0x46620a0
Jul 07 20:46:31-520681 util-scheduler-8620 DEBUG Checking readiness of task: 2188 / 0x46620a0
Jul 07 20:46:31-521081 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-524536 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-524745 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-524945 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-525141 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-525362 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-525553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-525749 util-scheduler-8620 DEBUG Running task: 2188 / 0x46620a0
Jul 07 20:46:31-526171 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:31-526425 util-scheduler-8620 DEBUG Adding task: 2189 / 0x4662248
Jul 07 20:46:31-526742 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-526936 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-527127 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-527317 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-527507 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-527709 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-527899 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-528088 util-scheduler-8620 DEBUG Running task: 2189 / 0x4662248
Jul 07 20:46:31-528279 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:31-528479 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:31-528711 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:31-528919 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:31-529127 util-scheduler-8620 DEBUG Adding task: 2190 / 0x46620a0
Jul 07 20:46:31-529346 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:31-529552 util-scheduler-8620 DEBUG Adding task: 2191 / 0x46620a0
Jul 07 20:46:31-529795 util-scheduler-8620 DEBUG Checking readiness of task: 2191 / 0x46620a0
Jul 07 20:46:31-529988 util-scheduler-8620 DEBUG Checking readiness of task: 2190 / 0x46620a0
Jul 07 20:46:31-530181 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-530371 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-530566 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-530755 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-530944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-531133 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-531322 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-531513 util-scheduler-8620 DEBUG Running task: 2190 / 0x46620a0
Jul 07 20:46:31-531697 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:31-531875 util-8620 DEBUG process_notify is running
Jul 07 20:46:31-532048 util-8620 DEBUG client_notify is running
Jul 07 20:46:31-532240 util-scheduler-8620 DEBUG Canceling task: 2164 / 0x5e2b838
Jul 07 20:46:31-532464 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 100 bytes.
Jul 07 20:46:31-532684 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:31-532924 cadet-p2p-8620 DEBUG Checking 0x5509688 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-533157 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-533368 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 7
Jul 07 20:46:31-533543 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:31-533765 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:31-533944 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:46:31-534117 cadet-p2p-8620 DEBUG   payload ID 8
Jul 07 20:46:31-534403 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({          DATA_ACK} 1) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 100)
Jul 07 20:46:31-534599 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:31-534778 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:31-534965 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:31-535139 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:31-535308 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:31-535495 cadet-chn-8620 DEBUG channel message sent callback {          DATA_ACK}
Jul 07 20:46:31-535683 cadet-chn-8620 DEBUG !!! SENT {          DATA_ACK}
Jul 07 20:46:31-535878 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 2
Jul 07 20:46:31-536105 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-536280 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:31-536469 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:31-536642 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:31-536838 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:31-537014 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:31-537213 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:31-537416 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:31-537595 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:31-537778 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:31-537958 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:31-538134 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:31-538303 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:31-538518 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:31-538689 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:31-538921 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:31-539167 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:31-539351 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:31-539533 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:31-539718 util-scheduler-8620 DEBUG Canceling task: 2111 / 0x5e31aa0
Jul 07 20:46:31-539931 util-scheduler-8620 DEBUG Adding task: 2192 / 0x5e31aa0
Jul 07 20:46:31-540181 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:31-540359 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:31-540537 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 8
Jul 07 20:46:31-540713 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:31-540934 cadet-p2p-8620 DEBUG Checking 0x551c438 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-541164 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-541370 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:31-541542 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:31-541771 cadet-p2p-8620 DEBUG Checking 0x551c438 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-542000 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-542181 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:31-542354 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:31-542521 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:31-542724 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `D3TJ'
Jul 07 20:46:31-542937 util-scheduler-8620 DEBUG Adding task: 2193 / 0x5e2b838
Jul 07 20:46:31-543116 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:31-543293 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:46:31-543491 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:31-543666 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:31-543840 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:31-544077 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-544272 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:31-544449 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:31-544646 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:31-544850 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 100 bytes.
Jul 07 20:46:31-545032 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:46:31-545259 util-scheduler-8620 DEBUG Adding task: 2194 / 0x5e2b838
Jul 07 20:46:31-545489 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:31-545685 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:31-545887 util-scheduler-8620 DEBUG Adding task: 2195 / 0x46620a0
Jul 07 20:46:31-546087 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:46:31-546343 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:31-546544 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:31-546808 util-scheduler-8620 DEBUG Checking readiness of task: 2195 / 0x46620a0
Jul 07 20:46:31-547003 util-scheduler-8620 DEBUG Checking readiness of task: 2191 / 0x46620a0
Jul 07 20:46:31-547193 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-547385 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-547576 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-547767 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-547957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-548148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-548336 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-548528 util-scheduler-8620 DEBUG Running task: 2195 / 0x46620a0
Jul 07 20:46:31-548723 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:31-548899 util-8620 DEBUG process_notify is running
Jul 07 20:46:31-549069 util-8620 DEBUG client_notify is running
Jul 07 20:46:31-549271 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:31-549467 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:31-549654 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:31-549885 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:31-550093 util-scheduler-8620 DEBUG Running task: 2193 / 0x5e2b838
Jul 07 20:46:31-550289 util-scheduler-8620 DEBUG Canceling task: 2194 / 0x5e2b838
Jul 07 20:46:31-550503 util-scheduler-8620 DEBUG Adding task: 2196 / 0x5e2b838
Jul 07 20:46:31-550725 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:31-550919 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:31-551120 util-scheduler-8620 DEBUG Adding task: 2197 / 0x46620a0
Jul 07 20:46:31-551361 util-scheduler-8620 DEBUG Checking readiness of task: 2197 / 0x46620a0
Jul 07 20:46:31-551558 util-scheduler-8620 DEBUG Checking readiness of task: 2191 / 0x46620a0
Jul 07 20:46:31-551755 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-551945 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-552139 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-552330 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-552521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-552711 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-552900 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-553091 util-scheduler-8620 DEBUG Running task: 2197 / 0x46620a0
Jul 07 20:46:31-553299 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:31-553475 util-8620 DEBUG process_notify is running
Jul 07 20:46:31-553644 util-8620 DEBUG client_notify is running
Jul 07 20:46:31-553824 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:31-554014 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:31-554204 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:31-554445 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:31-554693 util-scheduler-8620 DEBUG Checking readiness of task: 2191 / 0x46620a0
Jul 07 20:46:31-554887 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-555078 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-555268 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-555458 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-555668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-555857 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-556050 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-556243 util-scheduler-8620 DEBUG Running task: 2191 / 0x46620a0
Jul 07 20:46:31-556644 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:31-556875 util-scheduler-8620 DEBUG Adding task: 2198 / 0x4662248
Jul 07 20:46:31-557121 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-557493 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-557688 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-557879 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-558071 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-558261 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-558452 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-558641 util-scheduler-8620 DEBUG Running task: 2198 / 0x4662248
Jul 07 20:46:31-558830 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:31-559024 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:31-559239 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:31-559418 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:31-559620 util-scheduler-8620 DEBUG Adding task: 2199 / 0x46620a0
Jul 07 20:46:31-559859 util-scheduler-8620 DEBUG Checking readiness of task: 2199 / 0x46620a0
Jul 07 20:46:31-560052 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-560243 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-560433 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-560627 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-560816 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-561006 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-561219 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-561410 util-scheduler-8620 DEBUG Running task: 2199 / 0x46620a0
Jul 07 20:46:31-561827 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:31-562052 util-scheduler-8620 DEBUG Adding task: 2200 / 0x4662248
Jul 07 20:46:31-562298 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-562494 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-562684 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-562874 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-563064 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-563254 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-563443 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-563634 util-scheduler-8620 DEBUG Running task: 2200 / 0x4662248
Jul 07 20:46:31-563824 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:31-564016 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:31-564226 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:31-564423 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:31-564622 util-scheduler-8620 DEBUG Adding task: 2201 / 0x46620a0
Jul 07 20:46:31-564806 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:31-565023 util-scheduler-8620 DEBUG Adding task: 2202 / 0x46620a0
Jul 07 20:46:31-565292 util-scheduler-8620 DEBUG Checking readiness of task: 2202 / 0x46620a0
Jul 07 20:46:31-565488 util-scheduler-8620 DEBUG Checking readiness of task: 2201 / 0x46620a0
Jul 07 20:46:31-565683 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:31-565874 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:31-566063 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:31-566253 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:31-566444 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:31-566633 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:31-566822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:31-567012 util-scheduler-8620 DEBUG Running task: 2201 / 0x46620a0
Jul 07 20:46:31-567196 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:31-567371 util-8620 DEBUG process_notify is running
Jul 07 20:46:31-567540 util-8620 DEBUG client_notify is running
Jul 07 20:46:31-567724 util-scheduler-8620 DEBUG Canceling task: 2196 / 0x5e2b838
Jul 07 20:46:31-567944 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 96 bytes.
Jul 07 20:46:31-568158 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:31-568389 cadet-p2p-8620 DEBUG Checking 0x551c438 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-568620 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-568802 cadet-con-8620 DEBUG  last ack recv: 71, last pid sent: 8
Jul 07 20:46:31-568976 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:31-569220 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:31-569399 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:46:31-569572 cadet-p2p-8620 DEBUG   payload ID 9
Jul 07 20:46:31-569850 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 96)
Jul 07 20:46:31-570044 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:31-570234 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:31-570420 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:31-570596 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:31-570763 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:31-570950 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:31-571127 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:46:31-571351 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 1242 ms
Jul 07 20:46:31-571524 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:31-571729 cadet-chn-8620 DEBUG !! using delay 4970936 µs
Jul 07 20:46:31-571924 util-scheduler-8620 DEBUG Adding task: 2203 / 0x5e33a48
Jul 07 20:46:31-572124 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:31-572351 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:31-572524 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:31-572694 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:46:31-572865 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:31-573060 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:31-573260 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:31-573436 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:31-573637 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:31-573814 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:31-573995 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:31-574173 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:31-574347 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:31-574515 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:31-574728 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:31-574897 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:31-575126 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 10/11 (qn 1/0)
Jul 07 20:46:31-575388 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:31-575573 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:31-575749 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:31-575933 util-scheduler-8620 DEBUG Canceling task: 2192 / 0x5e31aa0
Jul 07 20:46:31-576144 util-scheduler-8620 DEBUG Adding task: 2204 / 0x5e31aa0
Jul 07 20:46:31-576384 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:31-576561 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 1
Jul 07 20:46:31-576737 cadet-con-8620 DEBUG !   accounting pid 9
Jul 07 20:46:31-576906 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:31-577085 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:46:31-577306 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:31-577481 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:31-577654 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:31-577851 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:31-578053 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 96 bytes.
Jul 07 20:46:31-578235 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:46:31-578411 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:31-578598 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:46:31-578949 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:32-555435 util-scheduler-8620 DEBUG Checking readiness of task: 2202 / 0x46620a0
Jul 07 20:46:32-555825 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-556022 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-556217 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-556409 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-556604 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-556795 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-556986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-557186 util-scheduler-8620 DEBUG Running task: 2202 / 0x46620a0
Jul 07 20:46:32-557636 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:32-557896 util-scheduler-8620 DEBUG Adding task: 2205 / 0x4662248
Jul 07 20:46:32-558179 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-558376 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-558576 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-558774 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-558972 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-559170 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-559363 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-559554 util-scheduler-8620 DEBUG Running task: 2205 / 0x4662248
Jul 07 20:46:32-559751 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:32-559951 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:32-560192 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:32-560460 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:32-560718 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:32-560929 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:32-561115 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:32-561576 cadet-con-8620 DEBUG   ACK 72 (was 71)
Jul 07 20:46:32-561815 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:32-562077 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:32-562284 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:32-562480 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:32-562658 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:32-562872 util-scheduler-8620 DEBUG Adding task: 2206 / 0x46620a0
Jul 07 20:46:32-748065 util-scheduler-8620 DEBUG Checking readiness of task: 2206 / 0x46620a0
Jul 07 20:46:32-748447 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-748643 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-748836 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-749028 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-749252 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-749445 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-749635 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-749832 util-scheduler-8620 DEBUG Running task: 2206 / 0x46620a0
Jul 07 20:46:32-750256 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:32-750512 util-scheduler-8620 DEBUG Adding task: 2207 / 0x4662248
Jul 07 20:46:32-750792 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-750985 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-751176 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-751366 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-751556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-751746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-751936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-752125 util-scheduler-8620 DEBUG Running task: 2207 / 0x4662248
Jul 07 20:46:32-752316 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:32-752517 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:32-752749 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:32-753013 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:32-753409 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:32-753642 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:32-753864 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:32-754110 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:32-754318 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:32-754509 cadet-con-8620 DEBUG  PID 15 (expected 15+)
Jul 07 20:46:32-754690 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:32-754881 util-scheduler-8620 DEBUG Canceling task: 2168 / 0x4d707d0
Jul 07 20:46:32-755105 util-scheduler-8620 DEBUG Adding task: 2208 / 0x4d707d0
Jul 07 20:46:32-755284 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:32-755545 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:32-755764 util-scheduler-8620 DEBUG Adding task: 2209 / 0x4d5e5d8
Jul 07 20:46:32-755949 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:32-756116 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:32-760173 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:32-760923 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:32-761119 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:32-770942 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:32-771207 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:32-771440 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:32-771650 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:32-771858 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:32-772089 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:32-772269 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:32-772453 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:32-772635 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:32-772812 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:32-772980 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:32-773579 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:32-773820 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:32-774006 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:32-774301 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:32-774472 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:32-774657 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:32-777781 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:32-778445 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:32-778623 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:32-778812 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:32-781955 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:32-782193 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:32-782375 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:32-782596 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:32-782789 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:32-783062 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:32-783261 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:32-783438 cadet-con-8620 DEBUG last pid sent 11
Jul 07 20:46:32-783611 cadet-con-8620 DEBUG      ack recv 75
Jul 07 20:46:32-783783 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:32-783959 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:32-784191 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:32-784397 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:32-784710 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:32-784909 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:32-785134 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:32-785341 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 11
Jul 07 20:46:32-785517 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:32-785721 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:32-785937 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:32-786163 util-scheduler-8620 DEBUG Adding task: 2210 / 0x4d6ff98
Jul 07 20:46:32-786344 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:32-786547 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:32-786723 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:32-786897 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:32-787137 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:32-787332 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:32-787510 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:32-787707 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:32-787937 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:32-788112 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:32-788286 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:32-788456 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:32-788675 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:32-788852 cadet-con-8620 DEBUG  ACK 79
Jul 07 20:46:32-789031 cadet-con-8620 DEBUG  last pid 15, last ack 78, qmax 11, q 0
Jul 07 20:46:32-789316 cadet-con-8620 INFO --> {               ACK} ( 79) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:32-789530 cadet-con-8620 DEBUG  ack 79
Jul 07 20:46:32-789708 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:32-789941 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:32-790146 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:32-790434 cadet-p2p-8620 INFO que {               ACK} ( 79) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:32-790645 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:32-790867 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:32-791049 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 11
Jul 07 20:46:32-791222 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:32-791420 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:32-791620 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:32-791795 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:32-791968 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:32-792204 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:32-792386 cadet-p2p-8620 DEBUG QQQ    payload , 79
Jul 07 20:46:32-792560 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:32-792792 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:32-792984 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:32-793159 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:32-793379 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:32-793562 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:32-793774 util-scheduler-8620 DEBUG Adding task: 2211 / 0x46620a0
Jul 07 20:46:32-794047 util-scheduler-8620 DEBUG Checking readiness of task: 2211 / 0x46620a0
Jul 07 20:46:32-794244 util-scheduler-8620 DEBUG Checking readiness of task: 2209 / 0x4d5e5d8
Jul 07 20:46:32-794436 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-794626 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-794816 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-795005 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-795193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-795382 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-795571 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-795764 util-scheduler-8620 DEBUG Running task: 2209 / 0x4d5e5d8
Jul 07 20:46:32-795949 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:32-796127 util-8620 DEBUG process_notify is running
Jul 07 20:46:32-796300 util-8620 DEBUG client_notify is running
Jul 07 20:46:32-796547 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:32-796756 util-scheduler-8620 DEBUG Adding task: 2212 / 0x4d5e5d8
Jul 07 20:46:32-796959 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:32-797341 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:32-797542 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:32-797740 util-scheduler-8620 DEBUG Running task: 2210 / 0x4d6ff98
Jul 07 20:46:32-797952 util-scheduler-8620 DEBUG Adding task: 2213 / 0x4d6ff98
Jul 07 20:46:32-798174 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:32-798371 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:32-798568 util-scheduler-8620 DEBUG Adding task: 2214 / 0x46620a0
Jul 07 20:46:32-798811 util-scheduler-8620 DEBUG Checking readiness of task: 2214 / 0x46620a0
Jul 07 20:46:32-799006 util-scheduler-8620 DEBUG Checking readiness of task: 2212 / 0x4d5e5d8
Jul 07 20:46:32-799197 util-scheduler-8620 DEBUG Checking readiness of task: 2211 / 0x46620a0
Jul 07 20:46:32-799388 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:32-799596 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:32-799787 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:32-799977 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:32-800166 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:32-800354 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:32-800543 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:32-800734 util-scheduler-8620 DEBUG Running task: 2212 / 0x4d5e5d8
Jul 07 20:46:32-800917 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:32-801092 util-8620 DEBUG process_notify is running
Jul 07 20:46:32-801284 util-8620 DEBUG client_notify is running
Jul 07 20:46:32-801497 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:32-801785 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:32-801997 util-scheduler-8620 DEBUG Running task: 2214 / 0x46620a0
Jul 07 20:46:32-802182 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:32-802356 util-8620 DEBUG process_notify is running
Jul 07 20:46:32-802525 util-8620 DEBUG client_notify is running
Jul 07 20:46:32-802704 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:32-802900 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:32-803089 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:32-803394 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:33-485483 util-scheduler-8620 DEBUG Checking readiness of task: 2211 / 0x46620a0
Jul 07 20:46:33-485866 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-486064 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-486258 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-486450 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-486642 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-486850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-487041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-487247 util-scheduler-8620 DEBUG Running task: 2211 / 0x46620a0
Jul 07 20:46:33-487682 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:33-487939 util-scheduler-8620 DEBUG Adding task: 2215 / 0x4662248
Jul 07 20:46:33-488217 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-488411 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-488603 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-488793 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-488983 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-489173 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-489384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-489573 util-scheduler-8620 DEBUG Running task: 2215 / 0x4662248
Jul 07 20:46:33-489765 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:33-489965 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:33-490199 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:33-490406 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:33-490613 util-scheduler-8620 DEBUG Adding task: 2216 / 0x46620a0
Jul 07 20:46:33-490831 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:33-491039 util-scheduler-8620 DEBUG Adding task: 2217 / 0x46620a0
Jul 07 20:46:33-491286 util-scheduler-8620 DEBUG Checking readiness of task: 2217 / 0x46620a0
Jul 07 20:46:33-491480 util-scheduler-8620 DEBUG Checking readiness of task: 2216 / 0x46620a0
Jul 07 20:46:33-491672 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-491863 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-492053 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-492243 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-492432 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-492622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-492810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-493002 util-scheduler-8620 DEBUG Running task: 2216 / 0x46620a0
Jul 07 20:46:33-493187 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:33-493385 util-8620 DEBUG process_notify is running
Jul 07 20:46:33-493557 util-8620 DEBUG client_notify is running
Jul 07 20:46:33-493748 util-scheduler-8620 DEBUG Canceling task: 2213 / 0x4d6ff98
Jul 07 20:46:33-493973 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:33-494207 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:33-494447 cadet-p2p-8620 DEBUG Checking 0x5570210 towards CMHCKRVP (->V8XX)
Jul 07 20:46:33-494681 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:33-494858 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:33-495050 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:33-495320 cadet-p2p-8620 INFO snd {               ACK} ( 79) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:33-495514 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:33-495694 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:33-495882 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:33-496055 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:33-496237 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:33-496412 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:33-496634 cadet-p2p-8620 DEBUG Checking 0x556f240 towards CMHCKRVP (->V8XX)
Jul 07 20:46:33-496867 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:33-497050 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 11
Jul 07 20:46:33-497246 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:33-497476 cadet-p2p-8620 DEBUG Checking 0x556f240 towards CMHCKRVP (->V8XX)
Jul 07 20:46:33-497706 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:33-497888 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 11
Jul 07 20:46:33-498060 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:33-498226 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:33-498430 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:33-498642 util-scheduler-8620 DEBUG Adding task: 2218 / 0x4d6ff98
Jul 07 20:46:33-498820 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:33-498996 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:33-499194 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:33-499369 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:33-499544 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:33-499781 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:33-499976 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:33-500153 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:33-500349 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:33-500554 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:33-500736 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:33-500938 util-scheduler-8620 DEBUG Adding task: 2219 / 0x4d6ff98
Jul 07 20:46:33-501175 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:33-501412 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:33-501613 util-scheduler-8620 DEBUG Adding task: 2220 / 0x46620a0
Jul 07 20:46:33-501813 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:33-502063 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:33-502259 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:33-502503 util-scheduler-8620 DEBUG Checking readiness of task: 2220 / 0x46620a0
Jul 07 20:46:33-502697 util-scheduler-8620 DEBUG Checking readiness of task: 2217 / 0x46620a0
Jul 07 20:46:33-502887 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-503077 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-503267 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-503457 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-503646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-503835 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-504024 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-504214 util-scheduler-8620 DEBUG Running task: 2220 / 0x46620a0
Jul 07 20:46:33-504398 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:33-504572 util-8620 DEBUG process_notify is running
Jul 07 20:46:33-504741 util-8620 DEBUG client_notify is running
Jul 07 20:46:33-504919 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:33-505113 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:33-505323 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:33-505565 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:33-505771 util-scheduler-8620 DEBUG Running task: 2218 / 0x4d6ff98
Jul 07 20:46:33-505964 util-scheduler-8620 DEBUG Canceling task: 2219 / 0x4d6ff98
Jul 07 20:46:33-506176 util-scheduler-8620 DEBUG Adding task: 2221 / 0x4d6ff98
Jul 07 20:46:33-506390 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:33-506584 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:33-506781 util-scheduler-8620 DEBUG Adding task: 2222 / 0x46620a0
Jul 07 20:46:33-507021 util-scheduler-8620 DEBUG Checking readiness of task: 2222 / 0x46620a0
Jul 07 20:46:33-507214 util-scheduler-8620 DEBUG Checking readiness of task: 2217 / 0x46620a0
Jul 07 20:46:33-507405 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-507595 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-507784 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-507973 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-508162 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-508351 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-508539 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-508729 util-scheduler-8620 DEBUG Running task: 2222 / 0x46620a0
Jul 07 20:46:33-508912 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:33-509086 util-8620 DEBUG process_notify is running
Jul 07 20:46:33-509276 util-8620 DEBUG client_notify is running
Jul 07 20:46:33-509451 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:33-509639 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:33-509826 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:33-510084 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:33-617373 util-scheduler-8620 DEBUG Checking readiness of task: 2217 / 0x46620a0
Jul 07 20:46:33-617753 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-617950 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-618143 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-618334 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-618525 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-618717 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-618906 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-619102 util-scheduler-8620 DEBUG Running task: 2217 / 0x46620a0
Jul 07 20:46:33-619530 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:33-619788 util-scheduler-8620 DEBUG Adding task: 2223 / 0x4662248
Jul 07 20:46:33-620068 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-620262 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-620453 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-620644 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-620837 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-621026 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-621240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-621433 util-scheduler-8620 DEBUG Running task: 2223 / 0x4662248
Jul 07 20:46:33-621623 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:33-621822 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:33-622054 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:33-622262 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:33-622468 util-scheduler-8620 DEBUG Adding task: 2224 / 0x46620a0
Jul 07 20:46:33-622671 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:33-622878 util-scheduler-8620 DEBUG Adding task: 2225 / 0x46620a0
Jul 07 20:46:33-623122 util-scheduler-8620 DEBUG Checking readiness of task: 2225 / 0x46620a0
Jul 07 20:46:33-623315 util-scheduler-8620 DEBUG Checking readiness of task: 2224 / 0x46620a0
Jul 07 20:46:33-623507 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:33-623696 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:33-623886 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:33-624076 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:33-624266 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:33-624454 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:33-624643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:33-624835 util-scheduler-8620 DEBUG Running task: 2224 / 0x46620a0
Jul 07 20:46:33-625020 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:33-625217 util-8620 DEBUG process_notify is running
Jul 07 20:46:33-625390 util-8620 DEBUG client_notify is running
Jul 07 20:46:33-625580 util-scheduler-8620 DEBUG Canceling task: 2221 / 0x4d6ff98
Jul 07 20:46:33-625805 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:33-626025 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:33-626265 cadet-p2p-8620 DEBUG Checking 0x556f240 towards CMHCKRVP (->V8XX)
Jul 07 20:46:33-626498 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:33-626712 cadet-con-8620 DEBUG  last ack recv: 75, last pid sent: 11
Jul 07 20:46:33-626888 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:33-627111 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:33-627289 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:33-627463 cadet-p2p-8620 DEBUG   payload ID 12
Jul 07 20:46:33-627749 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:33-627943 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:33-628123 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:33-628310 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:33-628500 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:33-628729 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:33-628903 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:33-629074 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:33-629268 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:33-629466 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:33-629640 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:33-629840 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:33-630019 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:33-630200 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:33-630379 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:33-630554 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:33-630725 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:33-630903 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:33-631137 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:33-631320 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:33-631498 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:33-631686 util-scheduler-8620 DEBUG Canceling task: 2186 / 0x4d707d0
Jul 07 20:46:33-631900 util-scheduler-8620 DEBUG Adding task: 2226 / 0x4d707d0
Jul 07 20:46:33-632151 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:33-632329 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:33-632507 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 12
Jul 07 20:46:33-632679 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:33-632861 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:33-633060 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:33-633255 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:33-633429 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:33-633629 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:33-633833 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:33-634015 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:33-634194 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:33-634383 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:33-634631 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:34-347813 util-scheduler-8620 DEBUG Checking readiness of task: 2225 / 0x46620a0
Jul 07 20:46:34-348188 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:34-348386 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:34-348579 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:34-348770 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:34-348962 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:34-349153 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:34-349373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:34-349576 util-scheduler-8620 DEBUG Running task: 2225 / 0x46620a0
Jul 07 20:46:34-350003 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:34-350290 util-scheduler-8620 DEBUG Adding task: 2227 / 0x4662248
Jul 07 20:46:34-350575 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:34-350773 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:34-350972 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:34-351170 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:34-351376 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:34-351574 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:34-351774 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:34-351969 util-scheduler-8620 DEBUG Running task: 2227 / 0x4662248
Jul 07 20:46:34-352162 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:34-352363 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:34-352598 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:34-352864 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:34-353118 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:34-353357 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:34-353542 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:34-353715 cadet-con-8620 DEBUG   ACK 76 (was 75)
Jul 07 20:46:34-353944 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:34-354173 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:34-354376 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:34-354558 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:34-354734 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:34-354946 util-scheduler-8620 DEBUG Adding task: 2228 / 0x46620a0
Jul 07 20:46:36-545236 util-scheduler-8620 DEBUG Checking readiness of task: 2228 / 0x46620a0
Jul 07 20:46:36-545642 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:36-548952 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:36-549174 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:36-549397 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:36-549591 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:36-549781 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:36-549972 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:36-550166 util-scheduler-8620 DEBUG Running task: 2203 / 0x5e33a48
Jul 07 20:46:36-550353 cadet-chn-8620 DEBUG !!! RETRANSMIT 2
Jul 07 20:46:36-550659 cadet-chn-8620 INFO ===> {              DATA} FWD on channel D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:36-550860 cadet-chn-8620 INFO ===> {              DATA} 2
Jul 07 20:46:36-551061 cadet-chn-8620 DEBUG   using existing copy: 0x54ea370 {r:0x5e33a48 q:(nil) t:260}
Jul 07 20:46:36-551251 cadet-chn-8620 DEBUG   new chq: 0x556e3a0
Jul 07 20:46:36-551460 cadet-tun-8620 DEBUG GMT Send on Tunnel D3TJ
Jul 07 20:46:36-551663 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:36-551844 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:36-552026 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:36-552206 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:36-552383 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:36-552553 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:36-552768 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:36-552940 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:36-553177 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:36-553448 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:36-553656 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:36-553970 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:36-554142 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:36-554326 cadet-tun-8620 INFO   ENC with key QFKEV1JF
Jul 07 20:46:36-557878 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:36-559138 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:36-559322 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:36-559511 cadet-tun-8620 INFO   HMAC with key QFKEV1JF
Jul 07 20:46:36-562209 cadet-tun-8620 DEBUG tunnel_get_connection D3TJ
Jul 07 20:46:36-562449 cadet-tun-8620 DEBUG   connection 1KSG9GE2 (->D3TJ): 3
Jul 07 20:46:36-562632 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:36-562855 cadet-tun-8620 DEBUG   connection BFARXZN9 (->D3TJ): 3
Jul 07 20:46:36-563034 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:36-563255 cadet-tun-8620 DEBUG  selected: connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:36-563448 cadet-tun-8620 DEBUG type {              DATA}
Jul 07 20:46:36-563730 cadet-con-8620 INFO --> {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (96 bytes)
Jul 07 20:46:36-563933 cadet-con-8620 DEBUG   Q_N+ 0x5e31aa4 0
Jul 07 20:46:36-564113 cadet-con-8620 DEBUG last pid sent 9
Jul 07 20:46:36-564287 cadet-con-8620 DEBUG      ack recv 72
Jul 07 20:46:36-564459 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:36-564637 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:36-564872 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:36-565080 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:36-565420 cadet-p2p-8620 INFO que {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 96)
Jul 07 20:46:36-565619 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:36-565844 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:36-566026 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 9
Jul 07 20:46:36-566200 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:36-566406 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 96 bytes
Jul 07 20:46:36-566622 core-api-8620 DEBUG Asking core for transmission of 96 bytes to `D3TJ'
Jul 07 20:46:36-566852 util-scheduler-8620 DEBUG Adding task: 2229 / 0x5e2b838
Jul 07 20:46:36-567032 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:36-567236 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:36-567412 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:36-567588 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:36-567825 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:36-568020 cadet-p2p-8620 DEBUG QQQ    payload {              DATA}, 2
Jul 07 20:46:36-568196 cadet-p2p-8620 DEBUG QQQ    size: 96 bytes
Jul 07 20:46:36-568395 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:36-568666 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:36-568884 util-scheduler-8620 DEBUG Adding task: 2230 / 0x4d5e5d8
Jul 07 20:46:36-569159 util-scheduler-8620 DEBUG Checking readiness of task: 2230 / 0x4d5e5d8
Jul 07 20:46:36-569381 util-scheduler-8620 DEBUG Checking readiness of task: 2228 / 0x46620a0
Jul 07 20:46:36-569573 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:36-569763 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:36-569952 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:36-570142 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:36-570331 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:36-570520 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:36-570708 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:36-570902 util-scheduler-8620 DEBUG Running task: 2230 / 0x4d5e5d8
Jul 07 20:46:36-571087 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:36-571290 util-8620 DEBUG process_notify is running
Jul 07 20:46:36-571464 util-8620 DEBUG client_notify is running
Jul 07 20:46:36-571696 util-8620 DEBUG Transmitting message of type 168 and size 43 to statistics service.
Jul 07 20:46:36-571955 util-8620 DEBUG Connection transmitted 43/43 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:36-572166 util-scheduler-8620 DEBUG Running task: 2229 / 0x5e2b838
Jul 07 20:46:36-572378 util-scheduler-8620 DEBUG Adding task: 2231 / 0x5e2b838
Jul 07 20:46:36-572602 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:36-572798 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:36-572996 util-scheduler-8620 DEBUG Adding task: 2232 / 0x46620a0
Jul 07 20:46:36-573264 util-scheduler-8620 DEBUG Checking readiness of task: 2232 / 0x46620a0
Jul 07 20:46:36-573459 util-scheduler-8620 DEBUG Checking readiness of task: 2228 / 0x46620a0
Jul 07 20:46:36-573649 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:36-573839 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:36-574029 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:36-574219 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:36-574408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:36-574597 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:36-574785 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:36-574975 util-scheduler-8620 DEBUG Running task: 2232 / 0x46620a0
Jul 07 20:46:36-575158 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:36-575332 util-8620 DEBUG process_notify is running
Jul 07 20:46:36-575500 util-8620 DEBUG client_notify is running
Jul 07 20:46:36-575679 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:36-575874 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:36-576063 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:36-576317 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:37-284228 util-scheduler-8620 DEBUG Checking readiness of task: 2228 / 0x46620a0
Jul 07 20:46:37-284605 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:37-284806 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:37-285001 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:37-285215 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:37-285411 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:37-285603 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:37-285795 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:37-285991 util-scheduler-8620 DEBUG Running task: 2228 / 0x46620a0
Jul 07 20:46:37-286418 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:37-286680 util-scheduler-8620 DEBUG Adding task: 2233 / 0x4662248
Jul 07 20:46:37-286963 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:37-287157 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:37-287350 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:37-287540 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:37-287731 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:37-287922 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:37-288111 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:37-288340 util-scheduler-8620 DEBUG Running task: 2233 / 0x4662248
Jul 07 20:46:37-288538 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:37-288741 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:37-288985 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:37-289286 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:37-289549 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:37-289781 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:37-289987 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:37-290232 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:37-290440 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:37-290627 cadet-con-8620 DEBUG  PID 16 (expected 16+)
Jul 07 20:46:37-290809 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:37-291001 util-scheduler-8620 DEBUG Canceling task: 2208 / 0x4d707d0
Jul 07 20:46:37-291232 util-scheduler-8620 DEBUG Adding task: 2234 / 0x4d707d0
Jul 07 20:46:37-291411 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:37-291669 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:37-291888 util-scheduler-8620 DEBUG Adding task: 2235 / 0x4d5e5d8
Jul 07 20:46:37-292072 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:37-292239 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:37-296595 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:37-297483 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:37-297683 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:37-300872 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:37-301074 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:37-301324 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:37-301534 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:37-301747 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:37-301946 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:37-302126 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:37-302308 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:37-302488 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:37-302668 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:37-302924 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:37-303100 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:37-303348 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:37-303614 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:37-303914 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:37-304086 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:37-304271 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:37-307679 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:37-308452 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:37-308737 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:37-308927 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:37-312277 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:37-312523 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:37-312706 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:37-312926 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:37-313121 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:37-313417 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:37-313615 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:37-313791 cadet-con-8620 DEBUG last pid sent 12
Jul 07 20:46:37-313963 cadet-con-8620 DEBUG      ack recv 76
Jul 07 20:46:37-314136 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:37-314312 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:37-314543 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:37-314778 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:37-315091 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:37-315290 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:37-315528 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:37-315710 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 12
Jul 07 20:46:37-315884 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:37-316088 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:37-316304 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:37-316531 util-scheduler-8620 DEBUG Adding task: 2236 / 0x4d6ff98
Jul 07 20:46:37-316712 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:37-316915 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:37-317090 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:37-317285 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:37-317522 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:37-317716 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:37-317892 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:37-318088 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:37-318318 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:37-318492 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:37-318665 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:37-318835 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:37-319054 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:37-319231 cadet-con-8620 DEBUG  ACK 80
Jul 07 20:46:37-319412 cadet-con-8620 DEBUG  last pid 16, last ack 79, qmax 11, q 0
Jul 07 20:46:37-319683 cadet-con-8620 INFO --> {               ACK} ( 80) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:37-319878 cadet-con-8620 DEBUG  ack 80
Jul 07 20:46:37-320064 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:37-320305 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:37-320512 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:37-320804 cadet-p2p-8620 INFO que {               ACK} ( 80) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:37-321003 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:37-321253 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:37-321437 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 12
Jul 07 20:46:37-321611 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:37-321813 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:37-322014 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:37-322190 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:37-322363 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:37-322598 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:37-322781 cadet-p2p-8620 DEBUG QQQ    payload , 80
Jul 07 20:46:37-322955 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:37-323186 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:37-323378 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:37-323554 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:37-323750 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:37-323933 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:37-324148 util-scheduler-8620 DEBUG Adding task: 2237 / 0x46620a0
Jul 07 20:46:37-324428 util-scheduler-8620 DEBUG Checking readiness of task: 2237 / 0x46620a0
Jul 07 20:46:37-324625 util-scheduler-8620 DEBUG Checking readiness of task: 2235 / 0x4d5e5d8
Jul 07 20:46:37-324817 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:37-325007 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:37-325241 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:37-325433 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:37-325622 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:37-325811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:37-326000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:37-326193 util-scheduler-8620 DEBUG Running task: 2235 / 0x4d5e5d8
Jul 07 20:46:37-326379 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:37-326557 util-8620 DEBUG process_notify is running
Jul 07 20:46:37-326729 util-8620 DEBUG client_notify is running
Jul 07 20:46:37-326977 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:37-327186 util-scheduler-8620 DEBUG Adding task: 2238 / 0x4d5e5d8
Jul 07 20:46:37-327390 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:37-327646 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:37-327846 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:37-328043 util-scheduler-8620 DEBUG Running task: 2236 / 0x4d6ff98
Jul 07 20:46:37-328254 util-scheduler-8620 DEBUG Adding task: 2239 / 0x4d6ff98
Jul 07 20:46:37-328476 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:37-328671 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:37-328868 util-scheduler-8620 DEBUG Adding task: 2240 / 0x46620a0
Jul 07 20:46:37-329110 util-scheduler-8620 DEBUG Checking readiness of task: 2240 / 0x46620a0
Jul 07 20:46:37-329328 util-scheduler-8620 DEBUG Checking readiness of task: 2238 / 0x4d5e5d8
Jul 07 20:46:37-329519 util-scheduler-8620 DEBUG Checking readiness of task: 2237 / 0x46620a0
Jul 07 20:46:37-329710 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:37-329900 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:37-330090 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:37-330279 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:37-330469 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:37-330657 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:37-330845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:37-331034 util-scheduler-8620 DEBUG Running task: 2238 / 0x4d5e5d8
Jul 07 20:46:37-331219 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:37-331393 util-8620 DEBUG process_notify is running
Jul 07 20:46:37-331562 util-8620 DEBUG client_notify is running
Jul 07 20:46:37-331776 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:37-332021 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:37-332231 util-scheduler-8620 DEBUG Running task: 2240 / 0x46620a0
Jul 07 20:46:37-332416 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:37-332591 util-8620 DEBUG process_notify is running
Jul 07 20:46:37-332759 util-8620 DEBUG client_notify is running
Jul 07 20:46:37-332939 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:37-333132 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:37-333344 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:37-333584 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:38-508504 util-scheduler-8620 DEBUG Checking readiness of task: 2237 / 0x46620a0
Jul 07 20:46:38-508885 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-509096 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-509341 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-509534 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-509725 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-509914 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-510102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-510297 util-scheduler-8620 DEBUG Running task: 2237 / 0x46620a0
Jul 07 20:46:38-510717 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:38-510971 util-scheduler-8620 DEBUG Adding task: 2241 / 0x4662248
Jul 07 20:46:38-511247 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-511440 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-511642 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-511831 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-512023 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-512211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-512399 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-512587 util-scheduler-8620 DEBUG Running task: 2241 / 0x4662248
Jul 07 20:46:38-512777 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:38-512975 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:38-513227 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:38-513433 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:38-513639 util-scheduler-8620 DEBUG Adding task: 2242 / 0x46620a0
Jul 07 20:46:38-513824 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:38-514028 util-scheduler-8620 DEBUG Adding task: 2243 / 0x46620a0
Jul 07 20:46:38-514270 util-scheduler-8620 DEBUG Checking readiness of task: 2243 / 0x46620a0
Jul 07 20:46:38-514462 util-scheduler-8620 DEBUG Checking readiness of task: 2242 / 0x46620a0
Jul 07 20:46:38-514653 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-514842 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-515031 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-515219 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-515407 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-515595 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-515782 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-515973 util-scheduler-8620 DEBUG Running task: 2242 / 0x46620a0
Jul 07 20:46:38-516155 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:38-516334 util-8620 DEBUG process_notify is running
Jul 07 20:46:38-516505 util-8620 DEBUG client_notify is running
Jul 07 20:46:38-516697 util-scheduler-8620 DEBUG Canceling task: 2239 / 0x4d6ff98
Jul 07 20:46:38-516921 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:38-517147 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:38-517803 cadet-p2p-8620 DEBUG Checking 0x55a3270 towards CMHCKRVP (->V8XX)
Jul 07 20:46:38-518045 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:38-518227 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:38-518420 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:38-518694 cadet-p2p-8620 INFO snd {               ACK} ( 80) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:38-518891 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:38-519072 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:38-519282 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:38-519459 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:38-519645 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:38-519820 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:38-520044 cadet-p2p-8620 DEBUG Checking 0x55a22a8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:38-520281 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:38-520465 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 12
Jul 07 20:46:38-520641 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:38-520873 cadet-p2p-8620 DEBUG Checking 0x55a22a8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:38-521106 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:38-521313 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 12
Jul 07 20:46:38-521489 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:38-521657 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:38-521864 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:38-522092 util-scheduler-8620 DEBUG Adding task: 2244 / 0x4d6ff98
Jul 07 20:46:38-522282 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:38-522469 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:38-522677 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:38-522852 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:38-523026 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:38-523266 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:38-523462 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:38-523641 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:38-523843 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:38-524051 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:38-524236 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:38-524449 util-scheduler-8620 DEBUG Adding task: 2245 / 0x4d6ff98
Jul 07 20:46:38-524670 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:38-524870 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:38-525076 util-scheduler-8620 DEBUG Adding task: 2246 / 0x46620a0
Jul 07 20:46:38-525305 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:38-526037 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:38-526242 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:38-526507 util-scheduler-8620 DEBUG Checking readiness of task: 2246 / 0x46620a0
Jul 07 20:46:38-526710 util-scheduler-8620 DEBUG Checking readiness of task: 2243 / 0x46620a0
Jul 07 20:46:38-526904 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-527095 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-527286 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-527478 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-527668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-527859 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-528053 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-528249 util-scheduler-8620 DEBUG Running task: 2246 / 0x46620a0
Jul 07 20:46:38-528437 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:38-528616 util-8620 DEBUG process_notify is running
Jul 07 20:46:38-528790 util-8620 DEBUG client_notify is running
Jul 07 20:46:38-528979 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:38-529182 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:38-529399 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:38-529718 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:38-529929 util-scheduler-8620 DEBUG Running task: 2244 / 0x4d6ff98
Jul 07 20:46:38-530127 util-scheduler-8620 DEBUG Canceling task: 2245 / 0x4d6ff98
Jul 07 20:46:38-530350 util-scheduler-8620 DEBUG Adding task: 2247 / 0x4d6ff98
Jul 07 20:46:38-530572 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:38-530771 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:38-530973 util-scheduler-8620 DEBUG Adding task: 2248 / 0x46620a0
Jul 07 20:46:38-531221 util-scheduler-8620 DEBUG Checking readiness of task: 2248 / 0x46620a0
Jul 07 20:46:38-531415 util-scheduler-8620 DEBUG Checking readiness of task: 2243 / 0x46620a0
Jul 07 20:46:38-531605 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-531795 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-531984 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-532176 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-532365 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-532553 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-532741 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-532931 util-scheduler-8620 DEBUG Running task: 2248 / 0x46620a0
Jul 07 20:46:38-533113 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:38-533307 util-8620 DEBUG process_notify is running
Jul 07 20:46:38-533477 util-8620 DEBUG client_notify is running
Jul 07 20:46:38-533652 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:38-533853 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:38-534041 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:38-534320 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:38-904485 util-scheduler-8620 DEBUG Checking readiness of task: 2243 / 0x46620a0
Jul 07 20:46:38-904868 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-905064 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-905288 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-905486 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-905679 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-905870 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-906062 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-906258 util-scheduler-8620 DEBUG Running task: 2243 / 0x46620a0
Jul 07 20:46:38-906684 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:38-906937 util-scheduler-8620 DEBUG Adding task: 2249 / 0x4662248
Jul 07 20:46:38-907214 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-907408 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-907599 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-907790 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-907981 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-908170 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-908360 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-908549 util-scheduler-8620 DEBUG Running task: 2249 / 0x4662248
Jul 07 20:46:38-908740 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:38-908938 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:38-909221 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:38-909430 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:38-909636 util-scheduler-8620 DEBUG Adding task: 2250 / 0x46620a0
Jul 07 20:46:38-909824 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:38-910030 util-scheduler-8620 DEBUG Adding task: 2251 / 0x46620a0
Jul 07 20:46:38-910275 util-scheduler-8620 DEBUG Checking readiness of task: 2251 / 0x46620a0
Jul 07 20:46:38-910468 util-scheduler-8620 DEBUG Checking readiness of task: 2250 / 0x46620a0
Jul 07 20:46:38-910660 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:38-910850 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:38-911040 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:38-911230 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:38-911420 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:38-911607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:38-911795 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:38-911987 util-scheduler-8620 DEBUG Running task: 2250 / 0x46620a0
Jul 07 20:46:38-912175 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:38-912354 util-8620 DEBUG process_notify is running
Jul 07 20:46:38-912526 util-8620 DEBUG client_notify is running
Jul 07 20:46:38-912717 util-scheduler-8620 DEBUG Canceling task: 2247 / 0x4d6ff98
Jul 07 20:46:38-912941 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:38-913162 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:38-913428 cadet-p2p-8620 DEBUG Checking 0x55a22a8 towards CMHCKRVP (->V8XX)
Jul 07 20:46:38-913662 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:38-913845 cadet-con-8620 DEBUG  last ack recv: 76, last pid sent: 12
Jul 07 20:46:38-914021 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:38-914243 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:38-914422 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:38-914598 cadet-p2p-8620 DEBUG   payload ID 13
Jul 07 20:46:38-914884 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:38-915079 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:38-915259 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:38-915448 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:38-915636 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:38-915866 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:38-916041 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:38-916214 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:38-916386 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:38-916582 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:38-916757 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:38-916958 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:38-917138 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:38-917345 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:38-917525 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:38-917701 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:38-917871 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:38-918036 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:38-918268 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:38-918453 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:38-918631 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:38-918817 util-scheduler-8620 DEBUG Canceling task: 2226 / 0x4d707d0
Jul 07 20:46:38-919030 util-scheduler-8620 DEBUG Adding task: 2252 / 0x4d707d0
Jul 07 20:46:38-919298 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:38-919478 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:38-919657 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 13
Jul 07 20:46:38-919832 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:38-920015 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:38-920215 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:38-920391 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:38-920565 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:38-920764 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:38-920968 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:38-921152 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:38-921356 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:38-921548 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:38-926523 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:39-763972 util-scheduler-8620 DEBUG Checking readiness of task: 2251 / 0x46620a0
Jul 07 20:46:39-764353 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:39-764562 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:39-764756 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:39-764948 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:39-765139 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:39-765360 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:39-765549 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:39-765745 util-scheduler-8620 DEBUG Running task: 2251 / 0x46620a0
Jul 07 20:46:39-766165 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:39-766418 util-scheduler-8620 DEBUG Adding task: 2253 / 0x4662248
Jul 07 20:46:39-766694 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:39-766888 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:39-767079 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:39-767270 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:39-767459 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:39-767661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:39-767851 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:39-768040 util-scheduler-8620 DEBUG Running task: 2253 / 0x4662248
Jul 07 20:46:39-768230 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:39-768429 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:39-768657 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:39-768923 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:39-769178 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:39-769414 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:39-769599 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:39-769772 cadet-con-8620 DEBUG   ACK 77 (was 76)
Jul 07 20:46:39-770002 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:39-770234 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:39-770441 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:39-770624 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:39-770800 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:39-771009 util-scheduler-8620 DEBUG Adding task: 2254 / 0x46620a0
Jul 07 20:46:41-808055 util-scheduler-8620 DEBUG Checking readiness of task: 2254 / 0x46620a0
Jul 07 20:46:41-808477 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:41-808677 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:41-808873 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:41-809065 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:41-809297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:41-809491 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:41-809681 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:41-809878 util-scheduler-8620 DEBUG Running task: 2254 / 0x46620a0
Jul 07 20:46:41-810303 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:41-810560 util-scheduler-8620 DEBUG Adding task: 2255 / 0x4662248
Jul 07 20:46:41-810840 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:41-811035 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:41-811227 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:41-811420 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:41-811612 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:41-811802 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:41-811992 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:41-812184 util-scheduler-8620 DEBUG Running task: 2255 / 0x4662248
Jul 07 20:46:41-812376 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:41-812576 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:41-812812 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:41-813078 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:41-813426 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:41-813659 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:41-813868 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:41-814115 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:41-814322 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:41-814511 cadet-con-8620 DEBUG  PID 17 (expected 17+)
Jul 07 20:46:41-814692 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:41-814882 util-scheduler-8620 DEBUG Canceling task: 2234 / 0x4d707d0
Jul 07 20:46:41-815105 util-scheduler-8620 DEBUG Adding task: 2256 / 0x4d707d0
Jul 07 20:46:41-815284 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:41-815542 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:41-815761 util-scheduler-8620 DEBUG Adding task: 2257 / 0x4d5e5d8
Jul 07 20:46:41-815945 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:41-816113 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:41-819713 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:41-821082 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:41-821325 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:41-824590 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:41-824794 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:41-825022 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:41-825259 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:41-825471 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:41-825672 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:41-825852 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:41-826037 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:41-826217 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:41-826395 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:41-826587 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:41-826757 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:41-826991 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:41-827178 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:41-827470 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:41-827642 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:41-827826 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:41-830896 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:41-831542 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:41-831784 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:41-831973 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:41-835189 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:41-835432 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:41-835617 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:41-835839 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:41-836032 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:41-836304 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:41-836503 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:41-836680 cadet-con-8620 DEBUG last pid sent 13
Jul 07 20:46:41-836853 cadet-con-8620 DEBUG      ack recv 77
Jul 07 20:46:41-837024 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:41-837227 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:41-837463 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:41-837669 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:41-837982 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:41-838181 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:41-838405 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:41-838588 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 13
Jul 07 20:46:41-838763 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:41-838966 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:41-839181 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:41-839406 util-scheduler-8620 DEBUG Adding task: 2258 / 0x4d6ff98
Jul 07 20:46:41-839585 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:41-839788 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:41-839965 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:41-840139 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:41-840376 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:41-840571 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:41-840748 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:41-840946 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:41-841175 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:41-841377 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:41-841552 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:41-841722 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:41-841941 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:41-842119 cadet-con-8620 DEBUG  ACK 81
Jul 07 20:46:41-842298 cadet-con-8620 DEBUG  last pid 17, last ack 80, qmax 11, q 0
Jul 07 20:46:41-842560 cadet-con-8620 INFO --> {               ACK} ( 81) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:41-842752 cadet-con-8620 DEBUG  ack 81
Jul 07 20:46:41-842929 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:41-843161 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:41-843366 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:41-843655 cadet-p2p-8620 INFO que {               ACK} ( 81) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:41-843873 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:41-844095 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:41-844276 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 13
Jul 07 20:46:41-844449 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:41-844648 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:41-844849 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:41-845025 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:41-845224 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:41-845461 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:41-845644 cadet-p2p-8620 DEBUG QQQ    payload , 81
Jul 07 20:46:41-845818 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:41-846050 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:41-846243 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:41-846419 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:41-846614 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:41-846796 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:41-847008 util-scheduler-8620 DEBUG Adding task: 2259 / 0x46620a0
Jul 07 20:46:41-847281 util-scheduler-8620 DEBUG Checking readiness of task: 2259 / 0x46620a0
Jul 07 20:46:41-847478 util-scheduler-8620 DEBUG Checking readiness of task: 2257 / 0x4d5e5d8
Jul 07 20:46:41-847670 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:41-847860 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:41-848050 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:41-848241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:41-848430 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:41-848619 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:41-848807 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:41-848999 util-scheduler-8620 DEBUG Running task: 2257 / 0x4d5e5d8
Jul 07 20:46:41-849186 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:41-849391 util-8620 DEBUG process_notify is running
Jul 07 20:46:41-849567 util-8620 DEBUG client_notify is running
Jul 07 20:46:41-849814 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:41-850027 util-scheduler-8620 DEBUG Adding task: 2260 / 0x4d5e5d8
Jul 07 20:46:41-850233 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:41-850496 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:41-850695 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:41-850891 util-scheduler-8620 DEBUG Running task: 2258 / 0x4d6ff98
Jul 07 20:46:41-851100 util-scheduler-8620 DEBUG Adding task: 2261 / 0x4d6ff98
Jul 07 20:46:41-851322 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:41-851517 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:41-851714 util-scheduler-8620 DEBUG Adding task: 2262 / 0x46620a0
Jul 07 20:46:41-851958 util-scheduler-8620 DEBUG Checking readiness of task: 2262 / 0x46620a0
Jul 07 20:46:41-852151 util-scheduler-8620 DEBUG Checking readiness of task: 2260 / 0x4d5e5d8
Jul 07 20:46:41-852342 util-scheduler-8620 DEBUG Checking readiness of task: 2259 / 0x46620a0
Jul 07 20:46:41-852532 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:41-852724 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:41-852915 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:41-853104 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:41-853318 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:41-853526 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:41-853716 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:41-853907 util-scheduler-8620 DEBUG Running task: 2260 / 0x4d5e5d8
Jul 07 20:46:41-854092 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:41-854267 util-8620 DEBUG process_notify is running
Jul 07 20:46:41-854436 util-8620 DEBUG client_notify is running
Jul 07 20:46:41-854648 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:41-854896 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:41-855105 util-scheduler-8620 DEBUG Running task: 2262 / 0x46620a0
Jul 07 20:46:41-855289 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:41-855463 util-8620 DEBUG process_notify is running
Jul 07 20:46:41-855631 util-8620 DEBUG client_notify is running
Jul 07 20:46:41-855810 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:41-856013 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:41-856201 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:41-856442 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:42-066576 util-scheduler-8620 DEBUG Checking readiness of task: 2259 / 0x46620a0
Jul 07 20:46:42-066895 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:42-067094 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:42-067290 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:42-067483 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:42-067676 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:42-067868 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:42-068059 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:42-068256 util-scheduler-8620 DEBUG Running task: 2259 / 0x46620a0
Jul 07 20:46:42-068673 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:42-068919 util-scheduler-8620 DEBUG Adding task: 2263 / 0x4662248
Jul 07 20:46:42-069214 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:42-069413 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:42-069607 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:42-069800 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:42-069994 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:42-070185 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:42-070376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:42-070567 util-scheduler-8620 DEBUG Running task: 2263 / 0x4662248
Jul 07 20:46:42-070761 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:42-070961 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:42-071190 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:42-071396 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:42-071604 util-scheduler-8620 DEBUG Adding task: 2264 / 0x46620a0
Jul 07 20:46:42-071792 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:42-071999 util-scheduler-8620 DEBUG Adding task: 2265 / 0x46620a0
Jul 07 20:46:42-072243 util-scheduler-8620 DEBUG Checking readiness of task: 2265 / 0x46620a0
Jul 07 20:46:42-072438 util-scheduler-8620 DEBUG Checking readiness of task: 2264 / 0x46620a0
Jul 07 20:46:42-072633 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:42-072854 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:42-073046 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:42-073267 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:42-073460 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:42-073651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:42-073842 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:42-074035 util-scheduler-8620 DEBUG Running task: 2264 / 0x46620a0
Jul 07 20:46:42-074221 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:42-074401 util-8620 DEBUG process_notify is running
Jul 07 20:46:42-074573 util-8620 DEBUG client_notify is running
Jul 07 20:46:42-074765 util-scheduler-8620 DEBUG Canceling task: 2231 / 0x5e2b838
Jul 07 20:46:42-074991 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 96 bytes.
Jul 07 20:46:42-075212 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:42-075451 cadet-p2p-8620 DEBUG Checking 0x55800c0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:42-075686 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:42-075870 cadet-con-8620 DEBUG  last ack recv: 72, last pid sent: 9
Jul 07 20:46:42-076047 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:42-076270 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:42-076450 cadet-p2p-8620 DEBUG   size 96 ok
Jul 07 20:46:42-076628 cadet-p2p-8620 DEBUG   payload ID 10
Jul 07 20:46:42-076915 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({              DATA} 2) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 96)
Jul 07 20:46:42-077112 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:42-077330 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:42-077520 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:42-077697 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:42-077867 cadet-tun-8620 DEBUG tun_message_sent
Jul 07 20:46:42-078056 cadet-chn-8620 DEBUG channel message sent callback {              DATA}
Jul 07 20:46:42-078236 cadet-chn-8620 DEBUG !!! SENT DATA MID 2
Jul 07 20:46:42-078465 cadet-chn-8620 DEBUG !! scheduling retry in 4 * 1242 ms
Jul 07 20:46:42-078640 cadet-chn-8620 DEBUG !! delay != 0
Jul 07 20:46:42-078846 cadet-chn-8620 DEBUG !! using delay 4970936 µs
Jul 07 20:46:42-079045 util-scheduler-8620 DEBUG Adding task: 2266 / 0x5e33a48
Jul 07 20:46:42-079251 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:42-079484 cadet-con-8620 DEBUG GMC send FWD ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:42-079661 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:42-079834 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:42-080006 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:42-080204 cadet-tun-8620 DEBUG GCT_unchoke_channels on D3TJ
Jul 07 20:46:42-080382 cadet-tun-8620 DEBUG  head: 0x5e339c8
Jul 07 20:46:42-080559 cadet-tun-8620 DEBUG  head ch: 0x5e336a0
Jul 07 20:46:42-080760 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS D3TJ
Jul 07 20:46:42-080941 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:42-081125 cadet-tun-8620 DEBUG TTT  kx_ctx 0x60aeb30, rekey_task 0
Jul 07 20:46:42-081335 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:42-081513 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:46:42-081685 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:42-081901 cadet-tun-8620 DEBUG TTT  - D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:42-082075 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:42-082307 cadet-tun-8620 DEBUG TTT  - 1KSG9GE2 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:42-082554 cadet-tun-8620 DEBUG TTT  - BFARXZN9 (->D3TJ) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:42-082739 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:42-082924 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:42-083110 util-scheduler-8620 DEBUG Canceling task: 2204 / 0x5e31aa0
Jul 07 20:46:42-083339 util-scheduler-8620 DEBUG Adding task: 2267 / 0x5e31aa0
Jul 07 20:46:42-083588 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:42-083769 cadet-con-8620 DEBUG !  Q_N- 0x5e31aa4 0
Jul 07 20:46:42-083949 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 10
Jul 07 20:46:42-084123 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:42-084307 cadet-p2p-8620 DEBUG   return 96
Jul 07 20:46:42-084510 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:42-084689 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:42-084864 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:42-085063 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:42-085296 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 96 bytes.
Jul 07 20:46:42-085483 core-api-8620 DEBUG Produced SEND message to core with 96 bytes payload
Jul 07 20:46:42-085665 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:42-085858 util-8620 DEBUG Transmitting message of type 76 and size 152 to core service.
Jul 07 20:46:42-086112 util-8620 DEBUG Connection transmitted 152/152 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:43-244068 util-scheduler-8620 DEBUG Checking readiness of task: 2265 / 0x46620a0
Jul 07 20:46:43-244484 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-244701 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-244897 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-245118 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-245340 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-245547 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-245738 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-245944 util-scheduler-8620 DEBUG Running task: 2265 / 0x46620a0
Jul 07 20:46:43-246376 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:43-246638 util-scheduler-8620 DEBUG Adding task: 2268 / 0x4662248
Jul 07 20:46:43-246920 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-247116 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-247308 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-248467 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-248680 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-248873 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-249065 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-249281 util-scheduler-8620 DEBUG Running task: 2268 / 0x4662248
Jul 07 20:46:43-249474 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:43-249678 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:43-249915 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:43-250124 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:43-250335 util-scheduler-8620 DEBUG Adding task: 2269 / 0x46620a0
Jul 07 20:46:43-250525 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:43-250733 util-scheduler-8620 DEBUG Adding task: 2270 / 0x46620a0
Jul 07 20:46:43-250989 util-scheduler-8620 DEBUG Checking readiness of task: 2270 / 0x46620a0
Jul 07 20:46:43-251186 util-scheduler-8620 DEBUG Checking readiness of task: 2269 / 0x46620a0
Jul 07 20:46:43-251396 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-251588 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-251779 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-252002 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-252193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-252383 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-252573 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-252765 util-scheduler-8620 DEBUG Running task: 2269 / 0x46620a0
Jul 07 20:46:43-252952 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:43-253130 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-253329 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-253522 util-scheduler-8620 DEBUG Canceling task: 2261 / 0x4d6ff98
Jul 07 20:46:43-253752 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:43-253976 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:43-254217 cadet-p2p-8620 DEBUG Checking 0x55d35a0 towards CMHCKRVP (->V8XX)
Jul 07 20:46:43-254452 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:43-254631 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:43-254823 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:43-255094 cadet-p2p-8620 INFO snd {               ACK} ( 81) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:43-255289 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:43-255469 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:43-255657 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:43-255832 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:43-256014 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:43-256189 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:43-256410 cadet-p2p-8620 DEBUG Checking 0x55d2a20 towards CMHCKRVP (->V8XX)
Jul 07 20:46:43-256643 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:43-256828 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 13
Jul 07 20:46:43-257004 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:43-257253 cadet-p2p-8620 DEBUG Checking 0x55d2a20 towards CMHCKRVP (->V8XX)
Jul 07 20:46:43-257487 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:43-257669 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 13
Jul 07 20:46:43-257844 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:43-258010 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:43-258216 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:43-258433 util-scheduler-8620 DEBUG Adding task: 2271 / 0x4d6ff98
Jul 07 20:46:43-258614 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:43-258792 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:43-258993 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:43-259169 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:43-259344 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:43-259583 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:43-259785 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:43-259963 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:43-260162 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:43-260369 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:43-260552 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:43-260758 util-scheduler-8620 DEBUG Adding task: 2272 / 0x4d6ff98
Jul 07 20:46:43-260979 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:43-261175 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:43-261656 util-scheduler-8620 DEBUG Adding task: 2273 / 0x46620a0
Jul 07 20:46:43-261864 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:43-262112 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:43-262307 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:43-262534 util-scheduler-8620 DEBUG Running task: 2270 / 0x46620a0
Jul 07 20:46:43-262941 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:43-263174 util-scheduler-8620 DEBUG Adding task: 2274 / 0x4662248
Jul 07 20:46:43-263435 util-scheduler-8620 DEBUG Checking readiness of task: 2273 / 0x46620a0
Jul 07 20:46:43-263631 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-263822 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-264013 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-264205 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-264395 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-264585 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-264773 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-264965 util-scheduler-8620 DEBUG Running task: 2273 / 0x46620a0
Jul 07 20:46:43-265150 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:43-265351 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-265522 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-265703 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:43-265899 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:43-266088 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:43-266371 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:43-266579 util-scheduler-8620 DEBUG Running task: 2274 / 0x4662248
Jul 07 20:46:43-266770 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:46:43-266966 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:46:43-267186 core-api-8620 DEBUG Received message of type 266 and size 36 from peer `KNAS'
Jul 07 20:46:43-268182 cadet-con-8620 INFO <-- {CONNECTION_DESTROY} on connection HS92G30M from KNAS
Jul 07 20:46:43-269501 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-269731 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:43-270451 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-270683 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:46:43-272333 cadet-con-8620 DEBUG   directly destroying connection!
Jul 07 20:46:43-273934 cadet-con-8620 DEBUG destroying connection HS92G30M (->KNAS)
Jul 07 20:46:43-274971 cadet-con-8620 DEBUG  fc's f: 0x4d61c34, b: 0x4d61c68
Jul 07 20:46:43-276106 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:46:43-277784 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection HS92G30M (->KNAS)
Jul 07 20:46:43-278477 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-278695 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:46:43-280154 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection HS92G30M (->KNAS)
Jul 07 20:46:43-280564 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-280783 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:43-281289 cadet-con-8620 DEBUG  get next hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-281505 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:46:43-283413 cadet-p2p-8620 DEBUG removing connection HS92G30M (->KNAS)
Jul 07 20:46:43-284590 cadet-p2p-8620 DEBUG from peer KNAS
Jul 07 20:46:43-286075 cadet-p2p-8620 DEBUG peer KNAS ok, has 1 connections.
Jul 07 20:46:43-289236 cadet-con-8620 DEBUG  get prev hop HS92G30M (->KNAS) [0/2]
Jul 07 20:46:43-289461 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:43-290180 cadet-p2p-8620 DEBUG removing connection HS92G30M (->KNAS)
Jul 07 20:46:43-290544 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:46:43-290904 cadet-p2p-8620 DEBUG peer GN10 ok, has 5 connections.
Jul 07 20:46:43-292102 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:46:43-294216 cadet-tun-8620 DEBUG Removing connection HS92G30M (->KNAS) from tunnel KNAS
Jul 07 20:46:43-296497 cadet-tun-8620 DEBUG Tunnel KNAS cstate CADET_TUNNEL_READY => CADET_TUNNEL_WAITING
Jul 07 20:46:43-297243 util-scheduler-8620 DEBUG Canceling task: 1322 / 0x4d61c30
Jul 07 20:46:43-297793 util-scheduler-8620 DEBUG Canceling task: 1588 / 0x4d61c30
Jul 07 20:46:43-300176 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:43-300403 util-scheduler-8620 DEBUG Adding task: 2275 / 0x4d5e5d8
Jul 07 20:46:43-301110 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:43-301346 util-scheduler-8620 DEBUG Adding task: 2276 / 0x46620a0
Jul 07 20:46:43-301552 util-scheduler-8620 DEBUG Running task: 2271 / 0x4d6ff98
Jul 07 20:46:43-301750 util-scheduler-8620 DEBUG Canceling task: 2272 / 0x4d6ff98
Jul 07 20:46:43-301971 util-scheduler-8620 DEBUG Adding task: 2277 / 0x4d6ff98
Jul 07 20:46:43-302194 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:43-302392 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:43-302590 util-scheduler-8620 DEBUG Adding task: 2278 / 0x46620a0
Jul 07 20:46:43-302849 util-scheduler-8620 DEBUG Checking readiness of task: 2278 / 0x46620a0
Jul 07 20:46:43-303048 util-scheduler-8620 DEBUG Checking readiness of task: 2276 / 0x46620a0
Jul 07 20:46:43-303239 util-scheduler-8620 DEBUG Checking readiness of task: 2275 / 0x4d5e5d8
Jul 07 20:46:43-303431 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-303625 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-303816 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-304007 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-304196 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-304385 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-304575 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-304767 util-scheduler-8620 DEBUG Running task: 2275 / 0x4d5e5d8
Jul 07 20:46:43-304954 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:43-305132 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-305326 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-305551 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:46:43-305879 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:43-306158 util-scheduler-8620 DEBUG Running task: 2278 / 0x46620a0
Jul 07 20:46:43-306346 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:43-306522 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-306693 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-306871 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:43-307065 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:43-307255 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:43-307538 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:43-307747 util-scheduler-8620 DEBUG Running task: 1328 / 0x4d61838
Jul 07 20:46:43-308832 cadet-tun-8620 DEBUG delayed destroying tunnel 0x4d61838
Jul 07 20:46:43-310573 cadet-tun-8620 DEBUG destroying tunnel KNAS
Jul 07 20:46:43-313906 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:43-314132 util-scheduler-8620 DEBUG Adding task: 2279 / 0x4d5e5d8
Jul 07 20:46:43-315508 util-scheduler-8620 DEBUG Checking readiness of task: 2279 / 0x4d5e5d8
Jul 07 20:46:43-315713 util-scheduler-8620 DEBUG Checking readiness of task: 2276 / 0x46620a0
Jul 07 20:46:43-315908 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-316100 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-316313 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-316506 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-316696 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-316887 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-317078 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-317291 util-scheduler-8620 DEBUG Running task: 2279 / 0x4d5e5d8
Jul 07 20:46:43-317477 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:43-317654 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-317825 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-318041 util-8620 DEBUG Transmitting message of type 168 and size 32 to statistics service.
Jul 07 20:46:43-318402 util-8620 DEBUG Connection transmitted 32/32 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:43-376548 util-scheduler-8620 DEBUG Checking readiness of task: 2276 / 0x46620a0
Jul 07 20:46:43-376863 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-377059 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-377280 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-377472 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-377662 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-377853 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-378043 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-378236 util-scheduler-8620 DEBUG Running task: 2276 / 0x46620a0
Jul 07 20:46:43-378647 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:43-378889 util-scheduler-8620 DEBUG Adding task: 2280 / 0x4662248
Jul 07 20:46:43-379151 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-379344 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-379535 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-379724 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-379913 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-380101 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-380291 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-380480 util-scheduler-8620 DEBUG Running task: 2280 / 0x4662248
Jul 07 20:46:43-380669 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:43-380866 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:43-381087 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:43-381325 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:43-381528 util-scheduler-8620 DEBUG Adding task: 2281 / 0x46620a0
Jul 07 20:46:43-381714 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:43-381916 util-scheduler-8620 DEBUG Adding task: 2282 / 0x46620a0
Jul 07 20:46:43-382156 util-scheduler-8620 DEBUG Checking readiness of task: 2282 / 0x46620a0
Jul 07 20:46:43-382348 util-scheduler-8620 DEBUG Checking readiness of task: 2281 / 0x46620a0
Jul 07 20:46:43-382539 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-382728 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-382917 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-383108 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-383297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-383508 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-383699 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-383889 util-scheduler-8620 DEBUG Running task: 2281 / 0x46620a0
Jul 07 20:46:43-384074 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:43-384249 util-8620 DEBUG process_notify is running
Jul 07 20:46:43-384420 util-8620 DEBUG client_notify is running
Jul 07 20:46:43-384604 util-scheduler-8620 DEBUG Canceling task: 2277 / 0x4d6ff98
Jul 07 20:46:43-384829 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:43-385047 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:43-385307 cadet-p2p-8620 DEBUG Checking 0x55d2a20 towards CMHCKRVP (->V8XX)
Jul 07 20:46:43-385540 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:43-385722 cadet-con-8620 DEBUG  last ack recv: 77, last pid sent: 13
Jul 07 20:46:43-385897 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:43-386118 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:43-386294 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:43-386468 cadet-p2p-8620 DEBUG   payload ID 14
Jul 07 20:46:43-386752 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:43-386947 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:43-387126 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:43-387313 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:43-387500 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:43-387731 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:43-387907 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:43-388079 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:43-388250 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:43-388449 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:43-388623 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:43-388822 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:43-389001 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:43-389182 cadet-tun-8620 DEBUG TTT  kx_ctx 0x539be20, rekey_task 0
Jul 07 20:46:43-389385 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:43-389561 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:43-389731 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:43-389895 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:43-390128 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:43-390312 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:43-390489 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:43-390675 util-scheduler-8620 DEBUG Canceling task: 2252 / 0x4d707d0
Jul 07 20:46:43-390887 util-scheduler-8620 DEBUG Adding task: 2283 / 0x4d707d0
Jul 07 20:46:43-391137 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:43-391315 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:43-391492 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 14
Jul 07 20:46:43-391664 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:43-391847 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:43-392045 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:43-392220 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:43-392395 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:43-392592 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:43-392795 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:43-392979 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:43-393160 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:43-393373 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:43-393618 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:43-915883 util-scheduler-8620 DEBUG Checking readiness of task: 2282 / 0x46620a0
Jul 07 20:46:43-916195 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:43-916391 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:43-916584 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:43-916776 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:43-916967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:43-917156 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:43-917421 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:43-917614 util-scheduler-8620 DEBUG Running task: 1337 / 0x4d64a70
Jul 07 20:46:43-918073 cadet-tun-8620 INFO finish KX for V8XX
Jul 07 20:46:44-044256 util-scheduler-8620 DEBUG Checking readiness of task: 2282 / 0x46620a0
Jul 07 20:46:44-044477 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:44-044677 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:44-044873 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:44-045068 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:44-045285 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:44-045480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:44-045673 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:44-045869 util-scheduler-8620 DEBUG Running task: 2282 / 0x46620a0
Jul 07 20:46:44-046290 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:44-046543 util-scheduler-8620 DEBUG Adding task: 2284 / 0x4662248
Jul 07 20:46:44-046808 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:44-047005 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:44-047199 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:44-047393 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:44-047585 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:44-047778 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:44-047970 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:44-048162 util-scheduler-8620 DEBUG Running task: 2284 / 0x4662248
Jul 07 20:46:44-048355 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:44-048556 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:44-048779 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:44-049038 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:44-049319 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:44-049531 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:44-049717 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:44-049893 cadet-con-8620 DEBUG   ACK 78 (was 77)
Jul 07 20:46:44-050123 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:44-050355 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:44-050563 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:44-050749 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:44-050938 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:44-051149 util-scheduler-8620 DEBUG Adding task: 2285 / 0x46620a0
Jul 07 20:46:46-022649 util-scheduler-8620 DEBUG Checking readiness of task: 2285 / 0x46620a0
Jul 07 20:46:46-023036 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-023236 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-023458 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-023656 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-023853 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-024050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-024241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-024439 util-scheduler-8620 DEBUG Running task: 2285 / 0x46620a0
Jul 07 20:46:46-024864 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:46-025125 util-scheduler-8620 DEBUG Adding task: 2286 / 0x4662248
Jul 07 20:46:46-025528 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-025731 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-025925 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-026118 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-026311 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-026503 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-026696 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-026891 util-scheduler-8620 DEBUG Running task: 2286 / 0x4662248
Jul 07 20:46:46-027085 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:46-027289 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:46-027527 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:46-027794 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:46-028055 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-028268 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-028456 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:46-028632 cadet-con-8620 DEBUG   ACK 73 (was 72)
Jul 07 20:46:46-028865 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-029100 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-029335 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-029523 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:46-029704 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:46-029920 util-scheduler-8620 DEBUG Adding task: 2287 / 0x46620a0
Jul 07 20:46:46-201599 util-scheduler-8620 DEBUG Checking readiness of task: 2287 / 0x46620a0
Jul 07 20:46:46-201980 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-202179 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-202371 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-202564 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-202755 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-202945 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-203136 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-203331 util-scheduler-8620 DEBUG Running task: 2287 / 0x46620a0
Jul 07 20:46:46-203750 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:46-204004 util-scheduler-8620 DEBUG Adding task: 2288 / 0x4662248
Jul 07 20:46:46-204278 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-204473 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-204664 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-204854 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-205043 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-205287 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-205479 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-205669 util-scheduler-8620 DEBUG Running task: 2288 / 0x4662248
Jul 07 20:46:46-205860 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:46-206061 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:46-206290 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `D3TJ'
Jul 07 20:46:46-206551 cadet-con-8620 INFO <-- {               ACK} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:46-206804 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-207012 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-207196 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:46-207367 cadet-con-8620 DEBUG   ACK 74 (was 73)
Jul 07 20:46:46-207594 cadet-con-8620 DEBUG connection_unlock_queue FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-207824 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-208030 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-208212 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:46-208412 util-scheduler-8620 DEBUG Adding task: 2289 / 0x4662248
Jul 07 20:46:46-208649 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-208843 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-209036 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-209246 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-209438 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-209627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-209816 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-210005 util-scheduler-8620 DEBUG Running task: 2289 / 0x4662248
Jul 07 20:46:46-210194 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:46-210385 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:46-210601 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:46-210844 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:46-211080 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-211309 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-211517 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:46-211756 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-211963 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-212151 cadet-con-8620 DEBUG  PID 8 (expected 8+)
Jul 07 20:46:46-212330 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:46-212519 util-scheduler-8620 DEBUG Canceling task: 2120 / 0x5e31aa0
Jul 07 20:46:46-212742 util-scheduler-8620 DEBUG Adding task: 2290 / 0x5e31aa0
Jul 07 20:46:46-212920 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:46-213177 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:46-213419 util-scheduler-8620 DEBUG Adding task: 2291 / 0x4d5e5d8
Jul 07 20:46:46-213605 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:46-213775 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:46-217372 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:46-218219 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:46-218425 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:46-221695 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on D3TJ
Jul 07 20:46:46-221932 cadet-chn-8620 DEBUG Channel D3TJ:0 (0x5e336a0)
Jul 07 20:46:46-222120 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x5e33a48
Jul 07 20:46:46-222308 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:46:46-222480 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:46:46-222652 cadet-chn-8620 DEBUG   id 80000003
Jul 07 20:46:46-222830 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:46:46-223062 util-server-nc-8620 DEBUG Adding message of type 274 and size 48 to pending queue (which has 1 entries)
Jul 07 20:46:46-223266 util-8620 DEBUG Scheduling transmission (0x4d5c418).
Jul 07 20:46:46-223471 util-scheduler-8620 DEBUG Adding task: 2292 / 0x4d5c418
Jul 07 20:46:46-223685 cadet-chn-8620 DEBUG destroying channel D3TJ:0
Jul 07 20:46:46-223897 cadet-chn-8620 DEBUG Channel D3TJ:0 (0x5e336a0)
Jul 07 20:46:46-224081 cadet-chn-8620 DEBUG   root 0x4d5c6d8/0x5e33a48
Jul 07 20:46:46-224266 cadet-chn-8620 DEBUG   cli 0
Jul 07 20:46:46-224435 cadet-chn-8620 DEBUG   ready YES
Jul 07 20:46:46-224605 cadet-chn-8620 DEBUG   id 80000003
Jul 07 20:46:46-224778 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:46:46-225247 cadet-chn-8620 DEBUG  COPYFREE BATCH 0x54ea370
Jul 07 20:46:46-225452 util-scheduler-8620 DEBUG Canceling task: 2266 / 0x5e33a48
Jul 07 20:46:46-225657 cadet-tun-8620 DEBUG Removing channel 0x5e336a0 from tunnel 0x5e2de48
Jul 07 20:46:46-225889 cadet-tun-8620 DEBUG  found! D3TJ:19 gid:0 (80000003 / 0)
Jul 07 20:46:46-226149 cadet-tun-8620 DEBUG Tunnel D3TJ destroy if empty
Jul 07 20:46:46-226351 cadet-tun-8620 DEBUG Tunnel D3TJ empty: destroying scheduled
Jul 07 20:46:46-226556 util-scheduler-8620 DEBUG Adding task: 2293 / 0x5e2de48
Jul 07 20:46:46-226746 cadet-tun-8620 DEBUG Scheduled destroy of 0x5e2de48 as 8F5
Jul 07 20:46:46-226980 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-227155 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:46-227328 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:46-227499 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:46-227719 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-227897 cadet-con-8620 DEBUG  ACK 72
Jul 07 20:46:46-228076 cadet-con-8620 DEBUG  last pid 8, last ack 71, qmax 11, q 0
Jul 07 20:46:46-228343 cadet-con-8620 INFO --> {               ACK} ( 72) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:46-228534 cadet-con-8620 DEBUG  ack 72
Jul 07 20:46:46-228710 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:46-228944 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-229150 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-229472 cadet-p2p-8620 INFO que {               ACK} ( 72) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:46-229671 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:46-229895 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-230077 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:46-230251 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:46-230457 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 40 bytes
Jul 07 20:46:46-230672 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `D3TJ'
Jul 07 20:46:46-230886 util-scheduler-8620 DEBUG Adding task: 2294 / 0x5e2b838
Jul 07 20:46:46-231066 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:46-231270 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:46-231450 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:46-231624 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:46-231862 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-232045 cadet-p2p-8620 DEBUG QQQ    payload , 72
Jul 07 20:46:46-232219 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:46-232416 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:46-232599 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:46-232804 util-scheduler-8620 DEBUG Adding task: 2295 / 0x46620a0
Jul 07 20:46:46-233069 util-scheduler-8620 DEBUG Checking readiness of task: 2295 / 0x46620a0
Jul 07 20:46:46-233287 util-scheduler-8620 DEBUG Checking readiness of task: 2292 / 0x4d5c418
Jul 07 20:46:46-233480 util-scheduler-8620 DEBUG Checking readiness of task: 2291 / 0x4d5e5d8
Jul 07 20:46:46-233671 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-233864 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-234072 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-234264 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-234453 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-234643 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-234831 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-235024 util-scheduler-8620 DEBUG Running task: 2291 / 0x4d5e5d8
Jul 07 20:46:46-235209 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:46-235386 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-235560 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-235801 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:46-236009 util-scheduler-8620 DEBUG Adding task: 2296 / 0x4d5e5d8
Jul 07 20:46:46-236211 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:46-236472 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:46-236669 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:46-236868 util-scheduler-8620 DEBUG Running task: 2292 / 0x4d5c418
Jul 07 20:46:46-237051 util-8620 DEBUG transmit_ready running (0x4d5c418).
Jul 07 20:46:46-237248 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-237441 util-server-nc-8620 DEBUG Copying message of type 274 and size 48 from pending queue to transmission buffer
Jul 07 20:46:46-237677 util-8620 DEBUG Connection transmitted 48/48 bytes to `<unbound UNIX client>' (0x4d5c418)
Jul 07 20:46:46-237886 util-scheduler-8620 DEBUG Running task: 2294 / 0x5e2b838
Jul 07 20:46:46-238096 util-scheduler-8620 DEBUG Adding task: 2297 / 0x5e2b838
Jul 07 20:46:46-238319 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:46-238516 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:46-238714 util-scheduler-8620 DEBUG Adding task: 2298 / 0x46620a0
Jul 07 20:46:46-238960 util-scheduler-8620 DEBUG Checking readiness of task: 2298 / 0x46620a0
Jul 07 20:46:46-239153 util-scheduler-8620 DEBUG Checking readiness of task: 2296 / 0x4d5e5d8
Jul 07 20:46:46-239344 util-scheduler-8620 DEBUG Checking readiness of task: 2295 / 0x46620a0
Jul 07 20:46:46-239535 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-239725 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-239914 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-240105 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-240294 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-240483 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-240671 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-240863 util-scheduler-8620 DEBUG Running task: 2296 / 0x4d5e5d8
Jul 07 20:46:46-241046 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:46-241242 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-241412 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-241625 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:46:46-241878 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:46-242087 util-scheduler-8620 DEBUG Running task: 2298 / 0x46620a0
Jul 07 20:46:46-242271 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:46-242445 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-242614 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-242793 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:46-242987 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:46-243192 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:46-243433 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:46-306965 util-scheduler-8620 DEBUG Checking readiness of task: 2295 / 0x46620a0
Jul 07 20:46:46-307185 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-307381 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-307573 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-307765 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-307955 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-308145 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-308334 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-308525 util-scheduler-8620 DEBUG Running task: 2295 / 0x46620a0
Jul 07 20:46:46-308929 util-8620 DEBUG receive_ready read 124/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:46-309163 util-scheduler-8620 DEBUG Adding task: 2299 / 0x4662248
Jul 07 20:46:46-309440 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-309633 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-309824 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-310014 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-310203 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-310394 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-310583 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-310772 util-scheduler-8620 DEBUG Running task: 2299 / 0x4662248
Jul 07 20:46:46-310962 util-8620 DEBUG Received message of type 70 and size 124 from core service.
Jul 07 20:46:46-311157 core-api-8620 DEBUG Processing message of type 70 and size 124 from core service
Jul 07 20:46:46-311375 core-api-8620 DEBUG Received message of type 280 and size 88 from peer `D3TJ'
Jul 07 20:46:46-311628 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection 1KSG9GE2 from D3TJ
Jul 07 20:46:46-311867 cadet-con-8620 DEBUG   connection 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-312093 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-312301 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:46-312545 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-312752 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-312940 cadet-con-8620 DEBUG  PID 9 (expected 9+)
Jul 07 20:46:46-313118 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:46-313324 util-scheduler-8620 DEBUG Canceling task: 2290 / 0x5e31aa0
Jul 07 20:46:46-313542 util-scheduler-8620 DEBUG Adding task: 2300 / 0x5e31aa0
Jul 07 20:46:46-313721 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:46-313958 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:46-314170 util-scheduler-8620 DEBUG Adding task: 2301 / 0x4d5e5d8
Jul 07 20:46:46-314351 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:46-314518 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:46-317835 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:46-319100 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:46-319307 cadet-tun-8620 INFO   HMAC with key V7H63X9N
Jul 07 20:46:46-322537 cadet-tun-8620 INFO <=== {   CHANNEL_DESTROY} on D3TJ
Jul 07 20:46:46-322782 cadet-con-8620 DEBUG GMC send BCK ACK on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-322961 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:46-323135 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:46-323306 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:46-323527 cadet-con-8620 DEBUG connection send BCK ack on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-323729 cadet-con-8620 DEBUG  ACK 73
Jul 07 20:46:46-323909 cadet-con-8620 DEBUG  last pid 9, last ack 72, qmax 11, q 0
Jul 07 20:46:46-324090 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:46-324258 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:46-324443 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:46-324628 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:46-324808 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:46-324996 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:46-325169 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:46-325374 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:46-325547 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:46-325752 core-api-8620 DEBUG Aborting transmission request to core for 40 bytes to `D3TJ'
Jul 07 20:46:46-326022 cadet-con-8620 INFO --> {               ACK} ( 73) on connection 1KSG9GE2 (->D3TJ) (40 bytes)
Jul 07 20:46:46-326213 cadet-con-8620 DEBUG  ack 73
Jul 07 20:46:46-326389 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:46:46-326622 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:46:46-326827 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:46:46-327118 cadet-p2p-8620 INFO que {               ACK} ( 73) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 40)
Jul 07 20:46:46-327316 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:46-327539 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-327720 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:46:46-327894 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:46-328097 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 40 bytes
Jul 07 20:46:46-328309 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `D3TJ'
Jul 07 20:46:46-328526 util-scheduler-8620 DEBUG Adding task: 2302 / 0x5e2b838
Jul 07 20:46:46-328705 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:46-328908 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:46-329083 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:46-329278 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:46:46-329514 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:46:46-329699 cadet-p2p-8620 DEBUG QQQ    payload , 73
Jul 07 20:46:46-329874 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:46-330070 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:46-330252 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:46-330461 util-scheduler-8620 DEBUG Adding task: 2303 / 0x46620a0
Jul 07 20:46:46-330715 util-scheduler-8620 DEBUG Checking readiness of task: 2303 / 0x46620a0
Jul 07 20:46:46-330923 util-scheduler-8620 DEBUG Checking readiness of task: 2301 / 0x4d5e5d8
Jul 07 20:46:46-331114 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-331304 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-331494 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-331683 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-331872 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-332060 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-332249 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-332440 util-scheduler-8620 DEBUG Running task: 2301 / 0x4d5e5d8
Jul 07 20:46:46-332626 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:46-332802 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-332972 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-333206 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:46-333464 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:46-333673 util-scheduler-8620 DEBUG Running task: 2302 / 0x5e2b838
Jul 07 20:46:46-333882 util-scheduler-8620 DEBUG Canceling task: 2297 / 0x5e2b838
Jul 07 20:46:46-334098 util-scheduler-8620 DEBUG Adding task: 2304 / 0x5e2b838
Jul 07 20:46:46-334317 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:46:46-334515 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:46-334714 util-scheduler-8620 DEBUG Adding task: 2305 / 0x46620a0
Jul 07 20:46:46-334954 util-scheduler-8620 DEBUG Checking readiness of task: 2305 / 0x46620a0
Jul 07 20:46:46-335148 util-scheduler-8620 DEBUG Checking readiness of task: 2303 / 0x46620a0
Jul 07 20:46:46-335338 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-335527 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-335716 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-335905 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-336094 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-336284 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-336474 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-336664 util-scheduler-8620 DEBUG Running task: 2305 / 0x46620a0
Jul 07 20:46:46-336847 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:46-337022 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-337207 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-337388 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:46-337580 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:46-337769 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:46-338011 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:46-344128 util-scheduler-8620 DEBUG Checking readiness of task: 2303 / 0x46620a0
Jul 07 20:46:46-344358 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-344554 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-344747 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-344940 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-345131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-345353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-345549 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-345750 util-scheduler-8620 DEBUG Running task: 2303 / 0x46620a0
Jul 07 20:46:46-346169 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:46-346413 util-scheduler-8620 DEBUG Adding task: 2306 / 0x4662248
Jul 07 20:46:46-346678 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-346874 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-347067 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-347265 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-347457 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-347651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-347841 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-348033 util-scheduler-8620 DEBUG Running task: 2306 / 0x4662248
Jul 07 20:46:46-348225 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:46-348424 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:46-348651 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:46-348940 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:46-349185 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:46-349836 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:46-350045 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:46-350289 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:46-350499 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:46-350688 cadet-con-8620 DEBUG  PID 18 (expected 18+)
Jul 07 20:46:46-350868 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:46-351057 util-scheduler-8620 DEBUG Canceling task: 2256 / 0x4d707d0
Jul 07 20:46:46-351281 util-scheduler-8620 DEBUG Adding task: 2307 / 0x4d707d0
Jul 07 20:46:46-351461 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:46-351715 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:46-351928 util-scheduler-8620 DEBUG Adding task: 2308 / 0x4d5e5d8
Jul 07 20:46:46-352110 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:46-352276 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:46-355681 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:46-356460 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:46-356664 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:46-359894 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:46-360097 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:46-360323 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:46-360533 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:46-360743 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:46-360944 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:46-361127 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:46-361334 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:46-361514 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:46-361692 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:46-361862 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:46-362030 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:46-362264 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:46-362450 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:46-362742 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:46-362926 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:46-363112 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:46-366173 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:46-366806 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:46-367039 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:46-367228 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:46-370842 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:46-371126 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:46-371311 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:46-371540 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:46-371742 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:46-372033 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:46-372241 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:46-372422 cadet-con-8620 DEBUG last pid sent 14
Jul 07 20:46:46-372597 cadet-con-8620 DEBUG      ack recv 78
Jul 07 20:46:46-372768 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:46-372944 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:46-373179 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:46-373412 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:46-373732 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:46-373946 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:46-374175 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:46-374385 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:46-374560 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:46-374763 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:46-374984 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:46-375215 util-scheduler-8620 DEBUG Adding task: 2309 / 0x4d6ff98
Jul 07 20:46:46-375398 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:46-375602 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:46-375781 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:46-375956 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:46-376198 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:46-376433 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:46-376611 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:46-376810 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:46-377043 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:46-377245 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:46-377421 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:46-377594 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:46-377818 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:46-377998 cadet-con-8620 DEBUG  ACK 82
Jul 07 20:46:46-378177 cadet-con-8620 DEBUG  last pid 18, last ack 81, qmax 11, q 0
Jul 07 20:46:46-378446 cadet-con-8620 INFO --> {               ACK} ( 82) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:46-378637 cadet-con-8620 DEBUG  ack 82
Jul 07 20:46:46-378814 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:46-379046 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:46-379253 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:46-379544 cadet-p2p-8620 INFO que {               ACK} ( 82) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:46-379741 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:46-379963 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:46-380145 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:46-380317 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:46-380516 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:46-380719 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:46-380895 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:46-381069 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:46-381333 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:46-381515 cadet-p2p-8620 DEBUG QQQ    payload , 82
Jul 07 20:46:46-381690 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:46-381922 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:46-382114 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:46-382290 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:46-382487 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:46-382671 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:46-382884 util-scheduler-8620 DEBUG Adding task: 2310 / 0x46620a0
Jul 07 20:46:46-383161 util-scheduler-8620 DEBUG Checking readiness of task: 2310 / 0x46620a0
Jul 07 20:46:46-383357 util-scheduler-8620 DEBUG Checking readiness of task: 2308 / 0x4d5e5d8
Jul 07 20:46:46-383549 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-383739 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-383932 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-384121 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-384310 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-384500 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-384708 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-384902 util-scheduler-8620 DEBUG Running task: 2308 / 0x4d5e5d8
Jul 07 20:46:46-385088 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:46-385291 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-385462 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-385712 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:46-385922 util-scheduler-8620 DEBUG Adding task: 2311 / 0x4d5e5d8
Jul 07 20:46:46-386124 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:46-386380 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:46-386579 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:46-386776 util-scheduler-8620 DEBUG Running task: 2309 / 0x4d6ff98
Jul 07 20:46:46-386986 util-scheduler-8620 DEBUG Adding task: 2312 / 0x4d6ff98
Jul 07 20:46:46-387208 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:46-387403 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:46-387600 util-scheduler-8620 DEBUG Adding task: 2313 / 0x46620a0
Jul 07 20:46:46-387843 util-scheduler-8620 DEBUG Checking readiness of task: 2313 / 0x46620a0
Jul 07 20:46:46-388037 util-scheduler-8620 DEBUG Checking readiness of task: 2311 / 0x4d5e5d8
Jul 07 20:46:46-388453 util-scheduler-8620 DEBUG Checking readiness of task: 2310 / 0x46620a0
Jul 07 20:46:46-388646 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:46-388837 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:46-389027 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:46-389241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:46-389432 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:46-389623 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:46-389811 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:46-390004 util-scheduler-8620 DEBUG Running task: 2311 / 0x4d5e5d8
Jul 07 20:46:46-390187 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:46-390362 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-390532 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-390745 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:46-390992 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:46-391202 util-scheduler-8620 DEBUG Running task: 2313 / 0x46620a0
Jul 07 20:46:46-391386 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:46-391561 util-8620 DEBUG process_notify is running
Jul 07 20:46:46-391729 util-8620 DEBUG client_notify is running
Jul 07 20:46:46-391909 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:46-392103 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:46-392292 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:46-392531 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:47-919266 util-scheduler-8620 DEBUG Checking readiness of task: 2310 / 0x46620a0
Jul 07 20:46:47-919636 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:47-919834 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:47-920027 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:47-920218 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:47-920408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:47-920599 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:47-920818 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:47-921016 util-scheduler-8620 DEBUG Running task: 2310 / 0x46620a0
Jul 07 20:46:47-921462 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:47-921717 util-scheduler-8620 DEBUG Adding task: 2314 / 0x4662248
Jul 07 20:46:47-921995 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:47-922188 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:47-922378 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:47-922569 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:47-922757 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:47-922946 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:47-923134 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:47-923323 util-scheduler-8620 DEBUG Running task: 2314 / 0x4662248
Jul 07 20:46:47-923516 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:47-923715 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:47-923944 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:46:47-924149 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:47-924358 util-scheduler-8620 DEBUG Adding task: 2315 / 0x46620a0
Jul 07 20:46:47-924547 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:47-924753 util-scheduler-8620 DEBUG Adding task: 2316 / 0x46620a0
Jul 07 20:46:47-924995 util-scheduler-8620 DEBUG Checking readiness of task: 2316 / 0x46620a0
Jul 07 20:46:47-925209 util-scheduler-8620 DEBUG Checking readiness of task: 2315 / 0x46620a0
Jul 07 20:46:47-925404 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:47-925594 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:47-925786 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:47-925975 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:47-926165 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:47-926353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:47-926543 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:47-926734 util-scheduler-8620 DEBUG Running task: 2315 / 0x46620a0
Jul 07 20:46:47-926919 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:47-927096 util-8620 DEBUG process_notify is running
Jul 07 20:46:47-927268 util-8620 DEBUG client_notify is running
Jul 07 20:46:47-927458 util-scheduler-8620 DEBUG Canceling task: 2304 / 0x5e2b838
Jul 07 20:46:47-927684 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 40 bytes.
Jul 07 20:46:47-927905 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:46:47-928145 cadet-p2p-8620 DEBUG Checking 0x56091b0 towards 1KSG9GE2 (->D3TJ)
Jul 07 20:46:47-928379 cadet-p2p-8620 DEBUG   on connection 1KSG9GE2 (->D3TJ) FWD
Jul 07 20:46:47-928557 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:47-928748 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:47-929016 cadet-p2p-8620 INFO snd {               ACK} ( 73) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD (size 40)
Jul 07 20:46:47-929231 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:47-929414 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:47-929601 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:47-929775 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:47-929956 cadet-con-8620 DEBUG  C_P- 0x5e31aa0 1
Jul 07 20:46:47-930131 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:47-930312 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:47-930511 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:46:47-930703 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:47-930878 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:47-931077 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:46:47-931281 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 40 bytes.
Jul 07 20:46:47-931464 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:47-931643 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:47-931833 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:47-932079 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:50-632794 util-scheduler-8620 DEBUG Checking readiness of task: 2316 / 0x46620a0
Jul 07 20:46:50-633182 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-633412 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-633607 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-633801 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-633993 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-634184 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-634375 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-634574 util-scheduler-8620 DEBUG Running task: 2316 / 0x46620a0
Jul 07 20:46:50-634997 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:50-635270 util-scheduler-8620 DEBUG Adding task: 2317 / 0x4662248
Jul 07 20:46:50-635559 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-635759 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-635950 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-636141 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-636332 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-636526 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-636724 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-636919 util-scheduler-8620 DEBUG Running task: 2317 / 0x4662248
Jul 07 20:46:50-637113 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:50-637352 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:50-637587 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:50-637854 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:50-638102 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:50-638333 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:50-638541 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:50-638791 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:50-639002 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:50-639192 cadet-con-8620 DEBUG  PID 19 (expected 19+)
Jul 07 20:46:50-639376 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:50-639569 util-scheduler-8620 DEBUG Canceling task: 2307 / 0x4d707d0
Jul 07 20:46:50-639800 util-scheduler-8620 DEBUG Adding task: 2318 / 0x4d707d0
Jul 07 20:46:50-639981 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:50-640242 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:50-640460 util-scheduler-8620 DEBUG Adding task: 2319 / 0x4d5e5d8
Jul 07 20:46:50-640646 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:50-640813 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:50-644420 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:50-645805 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:50-646023 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:50-649367 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:50-649572 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:50-649806 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:50-650017 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:50-650225 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:50-650426 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:50-650606 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:50-650790 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:50-650968 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:50-651144 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:50-651314 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:50-651485 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:50-651720 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:50-651905 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:50-652198 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:50-652369 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:50-652553 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:50-655657 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:50-656319 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:50-656554 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:50-656743 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:50-659921 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:50-660160 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:50-660343 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:50-660565 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:50-660758 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:50-661031 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:50-661252 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:50-661431 cadet-con-8620 DEBUG last pid sent 14
Jul 07 20:46:50-661608 cadet-con-8620 DEBUG      ack recv 78
Jul 07 20:46:50-661780 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:50-661957 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:50-662191 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:50-662397 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:50-662709 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:50-662908 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:50-663132 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:50-663315 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:50-663489 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:50-663692 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:50-663894 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:50-664071 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:50-664246 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:50-664484 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-664667 cadet-p2p-8620 DEBUG QQQ    payload , 82
Jul 07 20:46:50-664842 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:50-665074 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-665287 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-665463 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-665697 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-665889 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-666065 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-666261 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:50-666492 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:50-666690 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:50-666862 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:50-667034 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:50-667253 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:50-667444 cadet-con-8620 DEBUG  ACK 83
Jul 07 20:46:50-667623 cadet-con-8620 DEBUG  last pid 19, last ack 82, qmax 11, q 0
Jul 07 20:46:50-667801 cadet-con-8620 DEBUG  canceling old ACK
Jul 07 20:46:50-667970 cadet-con-8620 DEBUG !  GMC cancel message
Jul 07 20:46:50-668153 cadet-p2p-8620 DEBUG queue destroy type {               ACK}
Jul 07 20:46:50-668336 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:50-668515 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:50-668702 cadet-con-8620 DEBUG  not sent FWD {               ACK}
Jul 07 20:46:50-668875 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:50-669057 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:50-669249 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:50-669472 cadet-p2p-8620 DEBUG Checking 0x5631a90 towards CMHCKRVP (->V8XX)
Jul 07 20:46:50-669704 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:50-669886 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:50-670059 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:50-670317 cadet-con-8620 INFO --> {               ACK} ( 83) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:50-670508 cadet-con-8620 DEBUG  ack 83
Jul 07 20:46:50-670684 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 2
Jul 07 20:46:50-670915 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:50-671120 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:50-671408 cadet-p2p-8620 INFO que {               ACK} ( 83) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:50-671608 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:50-671829 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:50-672010 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:50-672182 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:50-672381 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:50-672580 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:50-672754 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:50-672928 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:50-673162 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-673364 cadet-p2p-8620 DEBUG QQQ    payload , 83
Jul 07 20:46:50-673539 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:50-673771 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-673963 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-674139 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-674371 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-674563 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-674739 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-674935 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:50-675119 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:50-675334 util-scheduler-8620 DEBUG Adding task: 2320 / 0x46620a0
Jul 07 20:46:50-675609 util-scheduler-8620 DEBUG Checking readiness of task: 2320 / 0x46620a0
Jul 07 20:46:50-675805 util-scheduler-8620 DEBUG Checking readiness of task: 2319 / 0x4d5e5d8
Jul 07 20:46:50-675999 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-676211 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-676409 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-676611 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-676801 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-677006 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-677216 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-677413 util-scheduler-8620 DEBUG Running task: 2319 / 0x4d5e5d8
Jul 07 20:46:50-677598 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:50-677778 util-8620 DEBUG process_notify is running
Jul 07 20:46:50-677950 util-8620 DEBUG client_notify is running
Jul 07 20:46:50-678200 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:50-678409 util-scheduler-8620 DEBUG Adding task: 2321 / 0x4d5e5d8
Jul 07 20:46:50-678613 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:50-678868 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:50-679065 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:50-679309 util-scheduler-8620 DEBUG Checking readiness of task: 2321 / 0x4d5e5d8
Jul 07 20:46:50-679503 util-scheduler-8620 DEBUG Checking readiness of task: 2320 / 0x46620a0
Jul 07 20:46:50-679693 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-679883 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-680073 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-680262 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-680451 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-680639 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-680827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-681017 util-scheduler-8620 DEBUG Running task: 2321 / 0x4d5e5d8
Jul 07 20:46:50-681219 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:50-681395 util-8620 DEBUG process_notify is running
Jul 07 20:46:50-681567 util-8620 DEBUG client_notify is running
Jul 07 20:46:50-681778 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:50-682024 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:50-970039 util-scheduler-8620 DEBUG Checking readiness of task: 2320 / 0x46620a0
Jul 07 20:46:50-970427 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-970625 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-970819 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-971010 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-971202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-971392 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-971581 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-971776 util-scheduler-8620 DEBUG Running task: 2320 / 0x46620a0
Jul 07 20:46:50-972201 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:50-972459 util-scheduler-8620 DEBUG Adding task: 2322 / 0x4662248
Jul 07 20:46:50-972739 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-972932 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-973123 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-973350 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-973540 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-973732 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-973921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-974141 util-scheduler-8620 DEBUG Running task: 2322 / 0x4662248
Jul 07 20:46:50-974352 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:50-974555 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:50-974792 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:50-974999 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:50-975207 util-scheduler-8620 DEBUG Adding task: 2323 / 0x46620a0
Jul 07 20:46:50-975394 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:50-975601 util-scheduler-8620 DEBUG Adding task: 2324 / 0x46620a0
Jul 07 20:46:50-975848 util-scheduler-8620 DEBUG Checking readiness of task: 2324 / 0x46620a0
Jul 07 20:46:50-976046 util-scheduler-8620 DEBUG Checking readiness of task: 2323 / 0x46620a0
Jul 07 20:46:50-976238 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-976428 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-976633 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-976823 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-977013 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-977225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-977418 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-977610 util-scheduler-8620 DEBUG Running task: 2323 / 0x46620a0
Jul 07 20:46:50-977795 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:50-977971 util-8620 DEBUG process_notify is running
Jul 07 20:46:50-978144 util-8620 DEBUG client_notify is running
Jul 07 20:46:50-978333 util-scheduler-8620 DEBUG Canceling task: 2312 / 0x4d6ff98
Jul 07 20:46:50-978559 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:50-978781 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:50-979021 cadet-p2p-8620 DEBUG Checking 0x565d790 towards CMHCKRVP (->V8XX)
Jul 07 20:46:50-979254 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:50-979433 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:50-979630 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:50-979900 cadet-p2p-8620 INFO snd {               ACK} ( 83) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:50-980095 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:50-980275 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:50-980461 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:50-980635 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:50-980819 cadet-con-8620 DEBUG  C_P- 0x4d707d0 3
Jul 07 20:46:50-980994 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:50-981241 cadet-p2p-8620 DEBUG Checking 0x5631a90 towards CMHCKRVP (->V8XX)
Jul 07 20:46:50-981475 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:50-981658 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:50-981832 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:50-982059 cadet-p2p-8620 DEBUG Checking 0x5631a90 towards CMHCKRVP (->V8XX)
Jul 07 20:46:50-982288 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:50-982470 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:50-982642 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:50-982808 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:50-983015 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:50-983229 util-scheduler-8620 DEBUG Adding task: 2325 / 0x4d6ff98
Jul 07 20:46:50-983408 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:50-983584 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:50-983782 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:50-983958 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:46:50-984132 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:50-984388 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-984583 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-984760 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-984994 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:50-985187 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:50-985390 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:50-985588 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:50-985797 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:50-985982 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:50-986185 util-scheduler-8620 DEBUG Adding task: 2326 / 0x4d6ff98
Jul 07 20:46:50-986406 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:50-986600 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:50-986803 util-scheduler-8620 DEBUG Adding task: 2327 / 0x46620a0
Jul 07 20:46:50-987003 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:50-987255 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:50-987451 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:50-987697 util-scheduler-8620 DEBUG Checking readiness of task: 2327 / 0x46620a0
Jul 07 20:46:50-987891 util-scheduler-8620 DEBUG Checking readiness of task: 2324 / 0x46620a0
Jul 07 20:46:50-988082 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-988271 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-988461 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-988650 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-988839 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-989027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-989241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-989434 util-scheduler-8620 DEBUG Running task: 2327 / 0x46620a0
Jul 07 20:46:50-989619 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:50-989793 util-8620 DEBUG process_notify is running
Jul 07 20:46:50-989964 util-8620 DEBUG client_notify is running
Jul 07 20:46:50-990140 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:50-990334 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:50-990522 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:50-990764 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:50-990970 util-scheduler-8620 DEBUG Running task: 2325 / 0x4d6ff98
Jul 07 20:46:50-991160 util-scheduler-8620 DEBUG Canceling task: 2326 / 0x4d6ff98
Jul 07 20:46:50-991373 util-scheduler-8620 DEBUG Adding task: 2328 / 0x4d6ff98
Jul 07 20:46:50-991586 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:50-991779 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:50-991976 util-scheduler-8620 DEBUG Adding task: 2329 / 0x46620a0
Jul 07 20:46:50-992216 util-scheduler-8620 DEBUG Checking readiness of task: 2329 / 0x46620a0
Jul 07 20:46:50-992409 util-scheduler-8620 DEBUG Checking readiness of task: 2324 / 0x46620a0
Jul 07 20:46:50-992599 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:50-992788 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:50-992978 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:50-993167 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:50-993382 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:50-993589 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:50-993779 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:50-993968 util-scheduler-8620 DEBUG Running task: 2329 / 0x46620a0
Jul 07 20:46:50-994152 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:50-994326 util-8620 DEBUG process_notify is running
Jul 07 20:46:50-994495 util-8620 DEBUG client_notify is running
Jul 07 20:46:50-994670 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:50-994859 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:50-995047 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:50-995289 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:51-405416 util-scheduler-8620 DEBUG Checking readiness of task: 2324 / 0x46620a0
Jul 07 20:46:51-405785 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-405985 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-406178 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-406368 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-406559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-406749 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-406939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-407133 util-scheduler-8620 DEBUG Running task: 2324 / 0x46620a0
Jul 07 20:46:51-407553 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:51-407816 util-scheduler-8620 DEBUG Adding task: 2330 / 0x4662248
Jul 07 20:46:51-408090 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-408285 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-408476 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-408666 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-408857 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-409047 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-409264 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-409456 util-scheduler-8620 DEBUG Running task: 2330 / 0x4662248
Jul 07 20:46:51-409648 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:51-409846 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:51-410075 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:51-410281 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:51-410487 util-scheduler-8620 DEBUG Adding task: 2331 / 0x46620a0
Jul 07 20:46:51-410674 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:51-410879 util-scheduler-8620 DEBUG Adding task: 2332 / 0x46620a0
Jul 07 20:46:51-411122 util-scheduler-8620 DEBUG Checking readiness of task: 2332 / 0x46620a0
Jul 07 20:46:51-411315 util-scheduler-8620 DEBUG Checking readiness of task: 2331 / 0x46620a0
Jul 07 20:46:51-411508 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-411698 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-411888 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-412079 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-412268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-412457 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-412673 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-412866 util-scheduler-8620 DEBUG Running task: 2331 / 0x46620a0
Jul 07 20:46:51-413050 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:51-413257 util-8620 DEBUG process_notify is running
Jul 07 20:46:51-413430 util-8620 DEBUG client_notify is running
Jul 07 20:46:51-413619 util-scheduler-8620 DEBUG Canceling task: 2328 / 0x4d6ff98
Jul 07 20:46:51-413845 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:51-414065 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:51-414303 cadet-p2p-8620 DEBUG Checking 0x5631a90 towards CMHCKRVP (->V8XX)
Jul 07 20:46:51-414536 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:51-414719 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 14
Jul 07 20:46:51-414894 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:51-415114 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:51-415292 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:51-415466 cadet-p2p-8620 DEBUG   payload ID 15
Jul 07 20:46:51-415752 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:51-415950 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:51-416129 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:51-416316 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:51-416504 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:51-416732 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:51-416907 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:51-417079 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:51-417276 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:51-417475 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:51-417649 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:51-417849 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:51-418030 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:51-418210 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:51-418388 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:51-418564 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:51-418732 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:51-418898 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:51-419129 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:51-419314 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:51-419493 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:51-419678 util-scheduler-8620 DEBUG Canceling task: 2283 / 0x4d707d0
Jul 07 20:46:51-419890 util-scheduler-8620 DEBUG Adding task: 2333 / 0x4d707d0
Jul 07 20:46:51-420141 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:51-420318 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:51-420496 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 15
Jul 07 20:46:51-420669 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:51-420890 cadet-p2p-8620 DEBUG Checking 0x565c820 towards CMHCKRVP (->V8XX)
Jul 07 20:46:51-421119 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:51-421330 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 15
Jul 07 20:46:51-421503 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:51-421732 cadet-p2p-8620 DEBUG Checking 0x565c820 towards CMHCKRVP (->V8XX)
Jul 07 20:46:51-421962 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:51-422142 cadet-con-8620 DEBUG  last ack recv: 78, last pid sent: 15
Jul 07 20:46:51-422314 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:51-422479 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:51-422683 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:51-422894 util-scheduler-8620 DEBUG Adding task: 2334 / 0x4d6ff98
Jul 07 20:46:51-423072 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:51-423264 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:51-423462 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:51-423638 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:51-423813 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:51-424057 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:51-424252 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:51-424429 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:51-424627 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:51-424835 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:51-425019 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:51-425244 util-scheduler-8620 DEBUG Adding task: 2335 / 0x4d6ff98
Jul 07 20:46:51-425466 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:51-425662 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:51-425863 util-scheduler-8620 DEBUG Adding task: 2336 / 0x46620a0
Jul 07 20:46:51-426067 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:51-426321 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:51-426518 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:51-426763 util-scheduler-8620 DEBUG Checking readiness of task: 2336 / 0x46620a0
Jul 07 20:46:51-426958 util-scheduler-8620 DEBUG Checking readiness of task: 2332 / 0x46620a0
Jul 07 20:46:51-427149 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-427339 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-427530 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-427720 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-427911 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-428100 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-428290 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-428481 util-scheduler-8620 DEBUG Running task: 2336 / 0x46620a0
Jul 07 20:46:51-428666 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:51-428852 util-8620 DEBUG process_notify is running
Jul 07 20:46:51-429024 util-8620 DEBUG client_notify is running
Jul 07 20:46:51-429226 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:51-429422 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:51-429612 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:51-429849 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:51-430055 util-scheduler-8620 DEBUG Running task: 2334 / 0x4d6ff98
Jul 07 20:46:51-430246 util-scheduler-8620 DEBUG Canceling task: 2335 / 0x4d6ff98
Jul 07 20:46:51-430458 util-scheduler-8620 DEBUG Adding task: 2337 / 0x4d6ff98
Jul 07 20:46:51-430672 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:51-430864 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:51-431060 util-scheduler-8620 DEBUG Adding task: 2338 / 0x46620a0
Jul 07 20:46:51-431298 util-scheduler-8620 DEBUG Checking readiness of task: 2338 / 0x46620a0
Jul 07 20:46:51-431491 util-scheduler-8620 DEBUG Checking readiness of task: 2332 / 0x46620a0
Jul 07 20:46:51-431681 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-431869 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-432058 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-432248 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-432452 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-432642 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-432830 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-433019 util-scheduler-8620 DEBUG Running task: 2338 / 0x46620a0
Jul 07 20:46:51-433434 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:51-433618 util-8620 DEBUG process_notify is running
Jul 07 20:46:51-433789 util-8620 DEBUG client_notify is running
Jul 07 20:46:51-433968 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:51-434158 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:51-434347 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:51-434578 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:51-434827 util-scheduler-8620 DEBUG Checking readiness of task: 2332 / 0x46620a0
Jul 07 20:46:51-435019 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-435213 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-435404 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-435593 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-435782 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-435973 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-436161 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-436352 util-scheduler-8620 DEBUG Running task: 2332 / 0x46620a0
Jul 07 20:46:51-436751 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:51-436976 util-scheduler-8620 DEBUG Adding task: 2339 / 0x4662248
Jul 07 20:46:51-437245 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-437438 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-437628 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-437818 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-438006 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-438196 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-438384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-438572 util-scheduler-8620 DEBUG Running task: 2339 / 0x4662248
Jul 07 20:46:51-438759 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:51-438952 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:51-439165 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:51-439346 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:51-439547 util-scheduler-8620 DEBUG Adding task: 2340 / 0x46620a0
Jul 07 20:46:51-932859 util-scheduler-8620 DEBUG Checking readiness of task: 2340 / 0x46620a0
Jul 07 20:46:51-933150 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-933429 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-933624 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-933816 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-934007 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-934197 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-934387 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-934583 util-scheduler-8620 DEBUG Running task: 2340 / 0x46620a0
Jul 07 20:46:51-934995 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:51-935260 util-scheduler-8620 DEBUG Adding task: 2341 / 0x4662248
Jul 07 20:46:51-935527 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:51-935721 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:51-935912 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:51-936106 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:51-936296 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:51-936487 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:51-936676 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:51-936867 util-scheduler-8620 DEBUG Running task: 2341 / 0x4662248
Jul 07 20:46:51-937057 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:51-937280 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:51-937504 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:51-937766 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:51-938022 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:51-938231 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:51-938418 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:51-938592 cadet-con-8620 DEBUG   ACK 79 (was 78)
Jul 07 20:46:51-938822 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:51-939054 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:51-939260 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:51-939443 cadet-p2p-8620 DEBUG   already unlocked!
Jul 07 20:46:51-939620 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:51-939823 util-scheduler-8620 DEBUG Adding task: 2342 / 0x46620a0
Jul 07 20:46:55-238821 util-scheduler-8620 DEBUG Checking readiness of task: 2342 / 0x46620a0
Jul 07 20:46:55-239220 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-239421 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-239639 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-239834 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-240036 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-240235 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-240427 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-240642 util-scheduler-8620 DEBUG Running task: 2342 / 0x46620a0
Jul 07 20:46:55-241069 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:55-241355 util-scheduler-8620 DEBUG Adding task: 2343 / 0x4662248
Jul 07 20:46:55-241662 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-241868 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-242066 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-242265 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-242454 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-242643 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-242850 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-243053 util-scheduler-8620 DEBUG Running task: 2343 / 0x4662248
Jul 07 20:46:55-243247 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:55-243449 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:55-243686 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:55-244330 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:55-244550 util-scheduler-8620 DEBUG Adding task: 2344 / 0x46620a0
Jul 07 20:46:55-244740 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:55-244973 util-scheduler-8620 DEBUG Adding task: 2345 / 0x46620a0
Jul 07 20:46:55-245255 util-scheduler-8620 DEBUG Checking readiness of task: 2345 / 0x46620a0
Jul 07 20:46:55-245455 util-scheduler-8620 DEBUG Checking readiness of task: 2344 / 0x46620a0
Jul 07 20:46:55-245649 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-245841 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-246055 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-246246 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-246436 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-246626 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-246817 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-247010 util-scheduler-8620 DEBUG Running task: 2344 / 0x46620a0
Jul 07 20:46:55-247197 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:55-247377 util-8620 DEBUG process_notify is running
Jul 07 20:46:55-247552 util-8620 DEBUG client_notify is running
Jul 07 20:46:55-247744 util-scheduler-8620 DEBUG Canceling task: 2337 / 0x4d6ff98
Jul 07 20:46:55-247977 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:55-248202 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:55-248446 cadet-p2p-8620 DEBUG Checking 0x565c820 towards CMHCKRVP (->V8XX)
Jul 07 20:46:55-248683 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:55-248868 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 15
Jul 07 20:46:55-249045 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:55-249290 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:55-249471 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:55-249646 cadet-p2p-8620 DEBUG   payload ID 16
Jul 07 20:46:55-249939 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:55-250138 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:55-250319 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:55-250508 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:55-250698 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:55-250930 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:55-251107 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:55-251280 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:55-251453 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:55-251653 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:55-251831 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:55-252037 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:55-252221 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:55-252407 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:55-252594 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:55-252772 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:55-252945 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:55-253118 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:55-254098 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:55-254289 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:55-254469 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:55-254663 util-scheduler-8620 DEBUG Canceling task: 2333 / 0x4d707d0
Jul 07 20:46:55-254883 util-scheduler-8620 DEBUG Adding task: 2346 / 0x4d707d0
Jul 07 20:46:55-255134 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:55-255310 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:55-255511 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 16
Jul 07 20:46:55-255684 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:55-255870 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:55-256073 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:55-256250 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:55-256423 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:55-256621 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:55-256825 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:55-257008 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:55-257187 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:55-257398 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:55-258213 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:55-404165 util-scheduler-8620 DEBUG Checking readiness of task: 2345 / 0x46620a0
Jul 07 20:46:55-404491 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-404690 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-404884 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-405077 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-405289 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-405478 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-405667 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-405864 util-scheduler-8620 DEBUG Running task: 2345 / 0x46620a0
Jul 07 20:46:55-406282 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:55-406532 util-scheduler-8620 DEBUG Adding task: 2347 / 0x4662248
Jul 07 20:46:55-406803 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-406995 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-407186 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-407374 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-407564 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-407752 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-407939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-408128 util-scheduler-8620 DEBUG Running task: 2347 / 0x4662248
Jul 07 20:46:55-408318 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:55-408516 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:55-408739 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:55-408999 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:55-409262 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:55-409492 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:55-409699 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:55-409943 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:55-410152 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:55-410341 cadet-con-8620 DEBUG  PID 20 (expected 20+)
Jul 07 20:46:55-410521 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:55-410707 util-scheduler-8620 DEBUG Canceling task: 2318 / 0x4d707d0
Jul 07 20:46:55-410930 util-scheduler-8620 DEBUG Adding task: 2348 / 0x4d707d0
Jul 07 20:46:55-411109 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:55-411367 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:55-411584 util-scheduler-8620 DEBUG Adding task: 2349 / 0x4d5e5d8
Jul 07 20:46:55-411768 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:55-411963 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:55-415864 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:55-416795 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:55-417034 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:55-420629 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:55-420847 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:55-421081 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:55-421316 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:55-421526 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:55-421726 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:55-421907 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:55-422089 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:55-422267 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:55-422443 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:55-422612 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:55-422784 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:55-423018 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:55-423203 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:55-423558 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:55-423730 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:55-423915 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:55-426973 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:55-428155 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:55-428401 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:55-428593 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:55-432046 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:55-432348 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:55-432532 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:55-432757 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:55-432952 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:55-433250 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:55-433451 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:55-433627 cadet-con-8620 DEBUG last pid sent 16
Jul 07 20:46:55-433800 cadet-con-8620 DEBUG      ack recv 79
Jul 07 20:46:55-433972 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:55-434148 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:55-434381 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:55-434588 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:55-434900 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:55-435099 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:55-435322 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:55-435504 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 16
Jul 07 20:46:55-435678 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:55-435882 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:55-436097 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:55-436326 util-scheduler-8620 DEBUG Adding task: 2350 / 0x4d6ff98
Jul 07 20:46:55-436506 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:55-436709 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:55-436885 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:55-437059 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:55-437317 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:55-437514 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:55-437690 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:55-437887 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:55-438147 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:55-438323 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:55-438496 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:55-438666 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:55-438885 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:55-439062 cadet-con-8620 DEBUG  ACK 84
Jul 07 20:46:55-439241 cadet-con-8620 DEBUG  last pid 20, last ack 83, qmax 11, q 0
Jul 07 20:46:55-439502 cadet-con-8620 INFO --> {               ACK} ( 84) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:55-439691 cadet-con-8620 DEBUG  ack 84
Jul 07 20:46:55-439867 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:55-440098 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:55-440302 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:55-440590 cadet-p2p-8620 INFO que {               ACK} ( 84) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:55-440786 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:55-441007 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:55-441187 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 16
Jul 07 20:46:55-441381 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:55-441580 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:55-441780 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:55-441955 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:55-442129 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:55-442368 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:55-442553 cadet-p2p-8620 DEBUG QQQ    payload , 84
Jul 07 20:46:55-442733 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:55-442981 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:55-443176 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:55-443353 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:55-443551 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:55-443736 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:55-443952 util-scheduler-8620 DEBUG Adding task: 2351 / 0x46620a0
Jul 07 20:46:55-444243 util-scheduler-8620 DEBUG Checking readiness of task: 2351 / 0x46620a0
Jul 07 20:46:55-444445 util-scheduler-8620 DEBUG Checking readiness of task: 2349 / 0x4d5e5d8
Jul 07 20:46:55-444640 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-444831 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-445022 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-445236 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-445432 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-445624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-445818 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-446017 util-scheduler-8620 DEBUG Running task: 2349 / 0x4d5e5d8
Jul 07 20:46:55-446208 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:55-446394 util-8620 DEBUG process_notify is running
Jul 07 20:46:55-446570 util-8620 DEBUG client_notify is running
Jul 07 20:46:55-446835 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:55-447054 util-scheduler-8620 DEBUG Adding task: 2352 / 0x4d5e5d8
Jul 07 20:46:55-447264 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:55-447569 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:55-447769 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:55-447969 util-scheduler-8620 DEBUG Running task: 2350 / 0x4d6ff98
Jul 07 20:46:55-448181 util-scheduler-8620 DEBUG Adding task: 2353 / 0x4d6ff98
Jul 07 20:46:55-448436 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:55-448635 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:55-448832 util-scheduler-8620 DEBUG Adding task: 2354 / 0x46620a0
Jul 07 20:46:55-449083 util-scheduler-8620 DEBUG Checking readiness of task: 2354 / 0x46620a0
Jul 07 20:46:55-449304 util-scheduler-8620 DEBUG Checking readiness of task: 2352 / 0x4d5e5d8
Jul 07 20:46:55-449496 util-scheduler-8620 DEBUG Checking readiness of task: 2351 / 0x46620a0
Jul 07 20:46:55-449685 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:55-449874 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:55-450064 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:55-450252 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:55-450440 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:55-450628 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:55-450816 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:55-451006 util-scheduler-8620 DEBUG Running task: 2352 / 0x4d5e5d8
Jul 07 20:46:55-451190 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:55-451364 util-8620 DEBUG process_notify is running
Jul 07 20:46:55-451533 util-8620 DEBUG client_notify is running
Jul 07 20:46:55-451743 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:55-452030 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:55-452241 util-scheduler-8620 DEBUG Running task: 2354 / 0x46620a0
Jul 07 20:46:55-452424 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:55-452597 util-8620 DEBUG process_notify is running
Jul 07 20:46:55-452769 util-8620 DEBUG client_notify is running
Jul 07 20:46:55-452948 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:55-453141 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:55-453351 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:55-453642 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:56-260891 util-scheduler-8620 DEBUG Checking readiness of task: 2351 / 0x46620a0
Jul 07 20:46:56-261288 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:56-261485 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:56-261679 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:56-261870 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:56-262061 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:56-262250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:56-262440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:56-262632 util-scheduler-8620 DEBUG Running task: 1566 / 0x5e2de48
Jul 07 20:46:56-262872 cadet-tun-8620 INFO finish KX for D3TJ
Jul 07 20:46:57-483607 util-scheduler-8620 DEBUG Checking readiness of task: 2351 / 0x46620a0
Jul 07 20:46:57-483995 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-484192 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-484386 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-484579 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-484771 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-484961 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-485151 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-485399 util-scheduler-8620 DEBUG Running task: 2351 / 0x46620a0
Jul 07 20:46:57-485827 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:57-486082 util-scheduler-8620 DEBUG Adding task: 2355 / 0x4662248
Jul 07 20:46:57-486361 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-486556 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-486747 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-486937 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-487126 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-487315 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-487504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-487692 util-scheduler-8620 DEBUG Running task: 2355 / 0x4662248
Jul 07 20:46:57-487884 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:57-488083 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:57-488315 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:57-488521 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:57-488728 util-scheduler-8620 DEBUG Adding task: 2356 / 0x46620a0
Jul 07 20:46:57-488915 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:57-489121 util-scheduler-8620 DEBUG Adding task: 2357 / 0x46620a0
Jul 07 20:46:57-489386 util-scheduler-8620 DEBUG Checking readiness of task: 2357 / 0x46620a0
Jul 07 20:46:57-489580 util-scheduler-8620 DEBUG Checking readiness of task: 2356 / 0x46620a0
Jul 07 20:46:57-489772 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-489962 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-490154 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-490344 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-490533 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-490722 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-490912 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-491103 util-scheduler-8620 DEBUG Running task: 2356 / 0x46620a0
Jul 07 20:46:57-491289 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:57-491467 util-8620 DEBUG process_notify is running
Jul 07 20:46:57-491639 util-8620 DEBUG client_notify is running
Jul 07 20:46:57-491829 util-scheduler-8620 DEBUG Canceling task: 2353 / 0x4d6ff98
Jul 07 20:46:57-492053 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:57-492274 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:57-492514 cadet-p2p-8620 DEBUG Checking 0x568e648 towards CMHCKRVP (->V8XX)
Jul 07 20:46:57-492760 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:57-492937 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:57-493129 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:57-493420 cadet-p2p-8620 INFO snd {               ACK} ( 84) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:57-493614 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:57-493794 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:57-493981 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:57-494155 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:57-494339 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:57-494512 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:57-494733 cadet-p2p-8620 DEBUG Checking 0x568da18 towards CMHCKRVP (->V8XX)
Jul 07 20:46:57-494967 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:57-495149 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 16
Jul 07 20:46:57-495341 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:57-495570 cadet-p2p-8620 DEBUG Checking 0x568da18 towards CMHCKRVP (->V8XX)
Jul 07 20:46:57-495799 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:57-495980 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 16
Jul 07 20:46:57-496153 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:57-496319 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:57-496523 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:57-496739 util-scheduler-8620 DEBUG Adding task: 2358 / 0x4d6ff98
Jul 07 20:46:57-496918 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:57-497095 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:57-497313 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:57-497488 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:57-497662 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:57-497900 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:57-498095 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:57-498273 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:57-498470 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:57-498676 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:57-498859 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:57-499061 util-scheduler-8620 DEBUG Adding task: 2359 / 0x4d6ff98
Jul 07 20:46:57-499278 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:57-499472 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:57-499674 util-scheduler-8620 DEBUG Adding task: 2360 / 0x46620a0
Jul 07 20:46:57-499875 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:57-500127 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:57-500322 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:57-500566 util-scheduler-8620 DEBUG Checking readiness of task: 2360 / 0x46620a0
Jul 07 20:46:57-500760 util-scheduler-8620 DEBUG Checking readiness of task: 2357 / 0x46620a0
Jul 07 20:46:57-500950 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-501140 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-501369 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-501561 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-501749 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-501939 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-502127 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-502317 util-scheduler-8620 DEBUG Running task: 2360 / 0x46620a0
Jul 07 20:46:57-502500 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:57-502676 util-8620 DEBUG process_notify is running
Jul 07 20:46:57-502845 util-8620 DEBUG client_notify is running
Jul 07 20:46:57-503024 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:57-503216 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:57-503405 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:57-503646 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:57-503851 util-scheduler-8620 DEBUG Running task: 2358 / 0x4d6ff98
Jul 07 20:46:57-504042 util-scheduler-8620 DEBUG Canceling task: 2359 / 0x4d6ff98
Jul 07 20:46:57-504254 util-scheduler-8620 DEBUG Adding task: 2361 / 0x4d6ff98
Jul 07 20:46:57-504468 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:57-504660 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:57-504873 util-scheduler-8620 DEBUG Adding task: 2362 / 0x46620a0
Jul 07 20:46:57-505114 util-scheduler-8620 DEBUG Checking readiness of task: 2362 / 0x46620a0
Jul 07 20:46:57-505328 util-scheduler-8620 DEBUG Checking readiness of task: 2357 / 0x46620a0
Jul 07 20:46:57-505519 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-505710 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-505899 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-506089 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-506278 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-506467 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-506660 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-506850 util-scheduler-8620 DEBUG Running task: 2362 / 0x46620a0
Jul 07 20:46:57-507033 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:57-507208 util-8620 DEBUG process_notify is running
Jul 07 20:46:57-507376 util-8620 DEBUG client_notify is running
Jul 07 20:46:57-507552 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:57-507741 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:57-507927 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:57-508169 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:57-608816 util-scheduler-8620 DEBUG Checking readiness of task: 2357 / 0x46620a0
Jul 07 20:46:57-609075 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-609294 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-609487 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-609679 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-609870 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-610060 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-610250 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-610443 util-scheduler-8620 DEBUG Running task: 2357 / 0x46620a0
Jul 07 20:46:57-610847 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:57-611083 util-scheduler-8620 DEBUG Adding task: 2363 / 0x4662248
Jul 07 20:46:57-611337 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-611530 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-611721 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-611910 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-612100 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-612289 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-612478 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-612668 util-scheduler-8620 DEBUG Running task: 2363 / 0x4662248
Jul 07 20:46:57-612857 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:57-613052 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:57-613314 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:57-613514 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:57-613715 util-scheduler-8620 DEBUG Adding task: 2364 / 0x46620a0
Jul 07 20:46:57-613899 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:57-614100 util-scheduler-8620 DEBUG Adding task: 2365 / 0x46620a0
Jul 07 20:46:57-614384 util-scheduler-8620 DEBUG Checking readiness of task: 2365 / 0x46620a0
Jul 07 20:46:57-614578 util-scheduler-8620 DEBUG Checking readiness of task: 2364 / 0x46620a0
Jul 07 20:46:57-614769 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:57-614959 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:57-615149 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:57-615338 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:57-615528 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:57-615715 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:57-615905 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:57-616095 util-scheduler-8620 DEBUG Running task: 2364 / 0x46620a0
Jul 07 20:46:57-616281 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:57-616454 util-8620 DEBUG process_notify is running
Jul 07 20:46:57-616627 util-8620 DEBUG client_notify is running
Jul 07 20:46:57-616810 util-scheduler-8620 DEBUG Canceling task: 2361 / 0x4d6ff98
Jul 07 20:46:57-617031 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:57-617265 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:57-617499 cadet-p2p-8620 DEBUG Checking 0x568da18 towards CMHCKRVP (->V8XX)
Jul 07 20:46:57-617729 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:57-617911 cadet-con-8620 DEBUG  last ack recv: 79, last pid sent: 16
Jul 07 20:46:57-618085 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:57-618303 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:57-618480 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:46:57-618654 cadet-p2p-8620 DEBUG   payload ID 17
Jul 07 20:46:57-618934 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:46:57-619127 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:57-619304 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:57-619490 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:46:57-619676 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:46:57-619904 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:57-620079 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:46:57-620251 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:46:57-620422 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:46:57-620618 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:46:57-620792 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:46:57-620992 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:57-621173 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:57-621374 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:57-621553 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:57-621729 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:57-621898 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:57-622064 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:57-622297 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:57-622482 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:57-622659 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:46:57-622844 util-scheduler-8620 DEBUG Canceling task: 2346 / 0x4d707d0
Jul 07 20:46:57-623055 util-scheduler-8620 DEBUG Adding task: 2366 / 0x4d707d0
Jul 07 20:46:57-623305 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:46:57-623482 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:46:57-623660 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 17
Jul 07 20:46:57-623832 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:57-624013 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:46:57-624212 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:57-624388 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:46:57-624578 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:46:57-624776 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:57-624980 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:46:57-625163 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:46:57-625361 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:57-625550 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:46:57-625799 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:58-396293 util-scheduler-8620 DEBUG Checking readiness of task: 2365 / 0x46620a0
Jul 07 20:46:58-396660 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:58-396860 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:58-397055 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:58-397275 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:58-397469 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:58-397660 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:58-397851 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:58-398047 util-scheduler-8620 DEBUG Running task: 2365 / 0x46620a0
Jul 07 20:46:58-398471 util-8620 DEBUG receive_ready read 152/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:58-398728 util-scheduler-8620 DEBUG Adding task: 2367 / 0x4662248
Jul 07 20:46:58-399004 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:58-399198 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:58-399389 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:58-399579 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:58-399770 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:58-399958 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:58-400150 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:58-400340 util-scheduler-8620 DEBUG Running task: 2367 / 0x4662248
Jul 07 20:46:58-400534 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:58-400737 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:58-400966 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:58-401254 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:58-401512 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:58-401721 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:58-401905 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:58-402077 cadet-con-8620 DEBUG   ACK 80 (was 79)
Jul 07 20:46:58-402307 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:58-402537 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:58-402742 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:58-402925 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:58-403126 util-scheduler-8620 DEBUG Adding task: 2368 / 0x4662248
Jul 07 20:46:58-403362 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:58-403554 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:58-403745 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:58-403935 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:58-404124 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:58-404313 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:58-404501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:58-404716 util-scheduler-8620 DEBUG Running task: 2368 / 0x4662248
Jul 07 20:46:58-404906 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:46:58-405097 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:46:58-405332 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:46:58-405574 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:46:58-405826 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:58-406032 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:58-406213 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:46:58-406383 cadet-con-8620 DEBUG   ACK 81 (was 80)
Jul 07 20:46:58-406606 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:58-406838 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:58-407044 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:58-407224 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:46:58-407396 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:58-407604 util-scheduler-8620 DEBUG Adding task: 2369 / 0x46620a0
Jul 07 20:46:59-872387 util-scheduler-8620 DEBUG Checking readiness of task: 2369 / 0x46620a0
Jul 07 20:46:59-872766 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-872963 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-873154 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-873383 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-873576 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-873770 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-873961 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-874157 util-scheduler-8620 DEBUG Running task: 2369 / 0x46620a0
Jul 07 20:46:59-874583 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:59-874840 util-scheduler-8620 DEBUG Adding task: 2370 / 0x4662248
Jul 07 20:46:59-875120 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-875315 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-875507 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-875698 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-875888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-876080 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-876268 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-876457 util-scheduler-8620 DEBUG Running task: 2370 / 0x4662248
Jul 07 20:46:59-876649 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:46:59-876848 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:46:59-877080 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:46:59-877371 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:46:59-877618 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:46:59-877848 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:59-878055 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:46:59-878301 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:59-878509 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:59-878699 cadet-con-8620 DEBUG  PID 21 (expected 21+)
Jul 07 20:46:59-878880 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:46:59-879068 util-scheduler-8620 DEBUG Canceling task: 2348 / 0x4d707d0
Jul 07 20:46:59-879291 util-scheduler-8620 DEBUG Adding task: 2371 / 0x4d707d0
Jul 07 20:46:59-879470 cadet-con-8620 DEBUG   message for us!
Jul 07 20:46:59-879756 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:59-879977 util-scheduler-8620 DEBUG Adding task: 2372 / 0x4d5e5d8
Jul 07 20:46:59-880163 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:46:59-880332 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:46:59-883935 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:46:59-884770 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:46:59-884978 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:46:59-888274 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:46:59-888481 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:46:59-888711 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:46:59-888921 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:46:59-889131 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:46:59-889359 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:46:59-889541 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:46:59-889724 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:46:59-889904 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:46:59-890079 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:46:59-890250 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:46:59-890417 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:46:59-890652 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:46:59-890837 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:46:59-891129 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:46:59-891301 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:59-891485 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:46:59-894551 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:46:59-895179 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:46:59-895415 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:46:59-895602 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:46:59-898797 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:46:59-899037 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:46:59-899220 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:46:59-899444 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:46:59-899639 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:46:59-899912 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:46:59-900112 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:46:59-900289 cadet-con-8620 DEBUG last pid sent 17
Jul 07 20:46:59-900477 cadet-con-8620 DEBUG      ack recv 81
Jul 07 20:46:59-900649 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:46:59-900829 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:46:59-901063 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:59-901298 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:59-901611 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:46:59-901814 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:46:59-902042 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:59-902226 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 17
Jul 07 20:46:59-902402 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:59-902607 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:46:59-902824 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:59-903050 util-scheduler-8620 DEBUG Adding task: 2373 / 0x4d6ff98
Jul 07 20:46:59-903232 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:59-903436 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:59-903613 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:59-903789 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:59-904027 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:59-904247 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:59-904428 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:59-904627 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:59-904858 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:46:59-905035 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:46:59-905234 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:46:59-905408 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:46:59-905629 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:46:59-905807 cadet-con-8620 DEBUG  ACK 85
Jul 07 20:46:59-905986 cadet-con-8620 DEBUG  last pid 21, last ack 84, qmax 11, q 0
Jul 07 20:46:59-906252 cadet-con-8620 INFO --> {               ACK} ( 85) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:46:59-906442 cadet-con-8620 DEBUG  ack 85
Jul 07 20:46:59-906619 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:46:59-906849 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:46:59-907056 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:46:59-907344 cadet-p2p-8620 INFO que {               ACK} ( 85) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:46:59-907541 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:46:59-907763 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:59-907946 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 17
Jul 07 20:46:59-908118 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:59-908317 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:46:59-908517 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:59-908692 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:59-908866 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:59-909099 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:59-909308 cadet-p2p-8620 DEBUG QQQ    payload , 85
Jul 07 20:46:59-909484 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:46:59-909717 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:59-909910 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:59-910086 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:59-910283 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:59-910465 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:59-910677 util-scheduler-8620 DEBUG Adding task: 2374 / 0x46620a0
Jul 07 20:46:59-910948 util-scheduler-8620 DEBUG Checking readiness of task: 2374 / 0x46620a0
Jul 07 20:46:59-911145 util-scheduler-8620 DEBUG Checking readiness of task: 2372 / 0x4d5e5d8
Jul 07 20:46:59-911338 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-911528 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-911719 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-911908 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-912098 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-912286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-912476 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-912669 util-scheduler-8620 DEBUG Running task: 2372 / 0x4d5e5d8
Jul 07 20:46:59-912855 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:59-913034 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-913231 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-913479 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:46:59-913687 util-scheduler-8620 DEBUG Adding task: 2375 / 0x4d5e5d8
Jul 07 20:46:59-913890 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:46:59-914154 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:59-914368 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:46:59-914566 util-scheduler-8620 DEBUG Running task: 2373 / 0x4d6ff98
Jul 07 20:46:59-914775 util-scheduler-8620 DEBUG Adding task: 2376 / 0x4d6ff98
Jul 07 20:46:59-914997 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:59-915194 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:59-915391 util-scheduler-8620 DEBUG Adding task: 2377 / 0x46620a0
Jul 07 20:46:59-915634 util-scheduler-8620 DEBUG Checking readiness of task: 2377 / 0x46620a0
Jul 07 20:46:59-915828 util-scheduler-8620 DEBUG Checking readiness of task: 2375 / 0x4d5e5d8
Jul 07 20:46:59-916019 util-scheduler-8620 DEBUG Checking readiness of task: 2374 / 0x46620a0
Jul 07 20:46:59-916213 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-916403 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-916592 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-916782 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-916972 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-917160 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-917375 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-917566 util-scheduler-8620 DEBUG Running task: 2375 / 0x4d5e5d8
Jul 07 20:46:59-917750 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:46:59-917924 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-918095 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-918305 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:46:59-918554 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:46:59-918764 util-scheduler-8620 DEBUG Running task: 2377 / 0x46620a0
Jul 07 20:46:59-918948 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:59-919123 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-919291 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-919469 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:59-919663 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:59-919851 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:59-920092 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:59-920339 util-scheduler-8620 DEBUG Checking readiness of task: 2374 / 0x46620a0
Jul 07 20:46:59-920533 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-920722 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-920913 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-921102 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-921326 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-921516 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-921705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-921896 util-scheduler-8620 DEBUG Running task: 2374 / 0x46620a0
Jul 07 20:46:59-922300 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:46:59-922527 util-scheduler-8620 DEBUG Adding task: 2378 / 0x4662248
Jul 07 20:46:59-922774 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-922967 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-923157 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-923347 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-923552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-923742 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-923930 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-924119 util-scheduler-8620 DEBUG Running task: 2378 / 0x4662248
Jul 07 20:46:59-924309 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:46:59-924502 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:46:59-924718 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:46:59-924915 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:59-925113 util-scheduler-8620 DEBUG Adding task: 2379 / 0x46620a0
Jul 07 20:46:59-925322 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:46:59-925522 util-scheduler-8620 DEBUG Adding task: 2380 / 0x46620a0
Jul 07 20:46:59-925761 util-scheduler-8620 DEBUG Checking readiness of task: 2380 / 0x46620a0
Jul 07 20:46:59-925954 util-scheduler-8620 DEBUG Checking readiness of task: 2379 / 0x46620a0
Jul 07 20:46:59-926149 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-926340 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-926530 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-926719 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-926909 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-927098 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-927287 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-927477 util-scheduler-8620 DEBUG Running task: 2379 / 0x46620a0
Jul 07 20:46:59-927661 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:59-927836 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-928005 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-928189 util-scheduler-8620 DEBUG Canceling task: 2376 / 0x4d6ff98
Jul 07 20:46:59-928410 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:46:59-928626 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:46:59-928857 cadet-p2p-8620 DEBUG Checking 0x56bd188 towards CMHCKRVP (->V8XX)
Jul 07 20:46:59-929090 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:46:59-929294 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:46:59-929481 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:46:59-929748 cadet-p2p-8620 INFO snd {               ACK} ( 85) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:46:59-929941 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:46:59-930121 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:46:59-930307 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:46:59-930481 cadet-con-8620 DEBUG  calling cont
Jul 07 20:46:59-930664 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:46:59-930838 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:46:59-931057 cadet-p2p-8620 DEBUG Checking 0x562b310 towards CMHCKRVP (->V8XX)
Jul 07 20:46:59-931288 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:59-931470 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 17
Jul 07 20:46:59-931644 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:59-931873 cadet-p2p-8620 DEBUG Checking 0x562b310 towards CMHCKRVP (->V8XX)
Jul 07 20:46:59-932102 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:46:59-932284 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 17
Jul 07 20:46:59-932457 cadet-con-8620 DEBUG  sendable
Jul 07 20:46:59-932622 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:46:59-932825 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:46:59-933035 util-scheduler-8620 DEBUG Adding task: 2381 / 0x4d6ff98
Jul 07 20:46:59-933236 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:46:59-933431 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:46:59-933629 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:46:59-933805 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:46:59-933978 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:46:59-934214 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:46:59-934407 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:46:59-934584 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:46:59-934781 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:46:59-934984 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:46:59-935168 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:46:59-935367 util-scheduler-8620 DEBUG Adding task: 2382 / 0x4d6ff98
Jul 07 20:46:59-935582 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:59-935776 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:59-935976 util-scheduler-8620 DEBUG Adding task: 2383 / 0x46620a0
Jul 07 20:46:59-936178 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:46:59-936426 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:59-936620 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:46:59-936860 util-scheduler-8620 DEBUG Checking readiness of task: 2383 / 0x46620a0
Jul 07 20:46:59-937055 util-scheduler-8620 DEBUG Checking readiness of task: 2380 / 0x46620a0
Jul 07 20:46:59-937272 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-937464 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-937655 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-937846 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-938035 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-938225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-938413 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-938605 util-scheduler-8620 DEBUG Running task: 2383 / 0x46620a0
Jul 07 20:46:59-938790 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:59-938967 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-939136 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-939313 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:59-939504 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:59-939693 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:59-940032 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:46:59-940241 util-scheduler-8620 DEBUG Running task: 2381 / 0x4d6ff98
Jul 07 20:46:59-940434 util-scheduler-8620 DEBUG Canceling task: 2382 / 0x4d6ff98
Jul 07 20:46:59-940648 util-scheduler-8620 DEBUG Adding task: 2384 / 0x4d6ff98
Jul 07 20:46:59-940865 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:46:59-941060 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:46:59-941283 util-scheduler-8620 DEBUG Adding task: 2385 / 0x46620a0
Jul 07 20:46:59-941528 util-scheduler-8620 DEBUG Checking readiness of task: 2385 / 0x46620a0
Jul 07 20:46:59-941723 util-scheduler-8620 DEBUG Checking readiness of task: 2380 / 0x46620a0
Jul 07 20:46:59-941914 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:46:59-942106 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:46:59-942297 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:46:59-942498 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:46:59-942705 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:46:59-942895 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:46:59-943085 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:46:59-943275 util-scheduler-8620 DEBUG Running task: 2385 / 0x46620a0
Jul 07 20:46:59-943460 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:46:59-943634 util-8620 DEBUG process_notify is running
Jul 07 20:46:59-943803 util-8620 DEBUG client_notify is running
Jul 07 20:46:59-943980 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:46:59-944169 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:46:59-944358 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:46:59-944644 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:00-031093 util-scheduler-8620 DEBUG Checking readiness of task: 2380 / 0x46620a0
Jul 07 20:47:00-031378 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:00-031575 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:00-031770 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:00-031963 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:00-032157 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:00-032349 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:00-032542 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:00-032736 util-scheduler-8620 DEBUG Running task: 2380 / 0x46620a0
Jul 07 20:47:00-033143 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:00-033408 util-scheduler-8620 DEBUG Adding task: 2386 / 0x4662248
Jul 07 20:47:00-033661 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:00-033856 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:00-034050 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:00-034242 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:00-034434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:00-034625 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:00-034817 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:00-035007 util-scheduler-8620 DEBUG Running task: 2386 / 0x4662248
Jul 07 20:47:00-035199 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:00-035396 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:00-035616 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:00-035818 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:00-036021 util-scheduler-8620 DEBUG Adding task: 2387 / 0x46620a0
Jul 07 20:47:00-036210 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:00-036412 util-scheduler-8620 DEBUG Adding task: 2388 / 0x46620a0
Jul 07 20:47:00-036653 util-scheduler-8620 DEBUG Checking readiness of task: 2388 / 0x46620a0
Jul 07 20:47:00-036848 util-scheduler-8620 DEBUG Checking readiness of task: 2387 / 0x46620a0
Jul 07 20:47:00-037042 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:00-037260 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:00-037454 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:00-037646 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:00-037838 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:00-038029 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:00-038239 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:00-038432 util-scheduler-8620 DEBUG Running task: 2387 / 0x46620a0
Jul 07 20:47:00-038619 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:00-038797 util-8620 DEBUG process_notify is running
Jul 07 20:47:00-038970 util-8620 DEBUG client_notify is running
Jul 07 20:47:00-039156 util-scheduler-8620 DEBUG Canceling task: 2384 / 0x4d6ff98
Jul 07 20:47:00-039379 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:00-039596 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:00-039830 cadet-p2p-8620 DEBUG Checking 0x562b310 towards CMHCKRVP (->V8XX)
Jul 07 20:47:00-040062 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:00-040247 cadet-con-8620 DEBUG  last ack recv: 81, last pid sent: 17
Jul 07 20:47:00-040424 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:00-040645 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:00-040824 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:47:00-041001 cadet-p2p-8620 DEBUG   payload ID 18
Jul 07 20:47:00-041305 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:47:00-041503 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:00-041684 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:00-041872 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:47:00-042062 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:47:00-042293 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:00-042470 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:47:00-042644 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:47:00-042819 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:47:00-043018 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:47:00-043194 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:47:00-043396 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:00-043577 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:00-043759 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:00-043939 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:00-044119 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:00-044290 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:00-044459 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:00-044693 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:00-044879 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:00-045059 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:00-045270 util-scheduler-8620 DEBUG Canceling task: 2366 / 0x4d707d0
Jul 07 20:47:00-045486 util-scheduler-8620 DEBUG Adding task: 2389 / 0x4d707d0
Jul 07 20:47:00-045738 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:00-045918 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:47:00-046102 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 18
Jul 07 20:47:00-046276 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:00-046461 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:47:00-046662 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:00-046837 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:00-047013 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:00-047212 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:00-047418 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:47:00-047605 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:47:00-047785 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:00-047977 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:47:00-048227 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:00-712214 util-scheduler-8620 DEBUG Checking readiness of task: 2388 / 0x46620a0
Jul 07 20:47:00-712607 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:00-715456 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:00-715689 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:00-715886 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:00-716078 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:00-716271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:00-716462 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:00-716672 util-scheduler-8620 DEBUG Running task: 2388 / 0x46620a0
Jul 07 20:47:00-717097 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:00-717415 util-scheduler-8620 DEBUG Adding task: 2390 / 0x4662248
Jul 07 20:47:00-717700 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:00-717895 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:00-718087 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:00-718279 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:00-718471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:00-718662 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:00-718853 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:00-719042 util-scheduler-8620 DEBUG Running task: 2390 / 0x4662248
Jul 07 20:47:00-719234 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:47:00-719435 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:47:00-719667 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:47:00-719935 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:47:00-720191 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:00-720400 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:00-720586 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:47:00-720761 cadet-con-8620 DEBUG   ACK 82 (was 81)
Jul 07 20:47:00-720994 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:00-721299 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:00-721510 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:00-721693 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:47:00-721870 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:00-722079 util-scheduler-8620 DEBUG Adding task: 2391 / 0x46620a0
Jul 07 20:47:04-215836 util-scheduler-8620 DEBUG Checking readiness of task: 2391 / 0x46620a0
Jul 07 20:47:04-216221 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-216419 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-216632 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-216825 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-217015 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-217236 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-217429 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-217647 util-scheduler-8620 DEBUG Running task: 2391 / 0x46620a0
Jul 07 20:47:04-218072 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:04-218331 util-scheduler-8620 DEBUG Adding task: 2392 / 0x4662248
Jul 07 20:47:04-218611 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-218826 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-219054 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-219247 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-219440 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-219631 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-219843 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-220034 util-scheduler-8620 DEBUG Running task: 2392 / 0x4662248
Jul 07 20:47:04-220227 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:04-220427 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:04-220661 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:04-220942 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:47:04-221209 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:47:04-221442 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:04-221649 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:04-221913 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:04-222122 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:04-222313 cadet-con-8620 DEBUG  PID 22 (expected 22+)
Jul 07 20:47:04-222494 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:04-222682 util-scheduler-8620 DEBUG Canceling task: 2371 / 0x4d707d0
Jul 07 20:47:04-222907 util-scheduler-8620 DEBUG Adding task: 2393 / 0x4d707d0
Jul 07 20:47:04-223104 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:04-223364 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:04-223583 util-scheduler-8620 DEBUG Adding task: 2394 / 0x4d5e5d8
Jul 07 20:47:04-223769 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:04-223937 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:04-228110 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:04-228968 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:04-229182 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:47:04-232550 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:47:04-232758 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:47:04-232987 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:47:04-233220 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:47:04-233432 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:47:04-233633 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:04-233833 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:04-234017 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:04-234197 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:04-234374 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:04-234546 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:04-234729 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:04-234971 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:04-235157 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:04-235450 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:47:04-235622 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:04-235827 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:47:04-238935 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:47:04-239614 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:47:04-239850 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:04-240038 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:47:04-243331 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:04-243583 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:47:04-243768 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:04-243990 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:47:04-244183 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:47:04-244477 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:47:04-244700 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:47:04-244883 cadet-con-8620 DEBUG last pid sent 18
Jul 07 20:47:04-245057 cadet-con-8620 DEBUG      ack recv 82
Jul 07 20:47:04-245250 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:47:04-245446 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:47:04-245681 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:04-245887 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:04-246199 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:47:04-246398 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:04-246640 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:04-246824 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 18
Jul 07 20:47:04-246998 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:04-247203 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:47:04-247419 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:04-247666 util-scheduler-8620 DEBUG Adding task: 2395 / 0x4d6ff98
Jul 07 20:47:04-247848 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:04-248053 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:04-248231 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:04-248406 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:04-248661 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:04-248858 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:04-249036 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:04-249253 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:04-249485 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:04-249661 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:04-249835 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:04-250005 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:04-250226 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:47:04-250404 cadet-con-8620 DEBUG  ACK 86
Jul 07 20:47:04-250583 cadet-con-8620 DEBUG  last pid 22, last ack 85, qmax 11, q 0
Jul 07 20:47:04-250846 cadet-con-8620 INFO --> {               ACK} ( 86) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:47:04-251036 cadet-con-8620 DEBUG  ack 86
Jul 07 20:47:04-251212 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:47:04-251444 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:04-251649 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:04-251938 cadet-p2p-8620 INFO que {               ACK} ( 86) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:47:04-252135 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:04-252358 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:04-252539 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 18
Jul 07 20:47:04-252712 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:04-252913 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:04-253114 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:04-253309 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:04-253484 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:04-253719 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:04-253901 cadet-p2p-8620 DEBUG QQQ    payload , 86
Jul 07 20:47:04-254076 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:04-254309 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:04-254502 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:04-254678 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:04-254877 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:04-255060 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:04-255288 util-scheduler-8620 DEBUG Adding task: 2396 / 0x46620a0
Jul 07 20:47:04-255562 util-scheduler-8620 DEBUG Checking readiness of task: 2396 / 0x46620a0
Jul 07 20:47:04-255759 util-scheduler-8620 DEBUG Checking readiness of task: 2394 / 0x4d5e5d8
Jul 07 20:47:04-255952 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-256143 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-256333 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-256524 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-256713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-256903 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-257091 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-257304 util-scheduler-8620 DEBUG Running task: 2394 / 0x4d5e5d8
Jul 07 20:47:04-257490 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:04-257671 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-257843 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-258090 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:04-258298 util-scheduler-8620 DEBUG Adding task: 2397 / 0x4d5e5d8
Jul 07 20:47:04-258500 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:04-258765 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:04-258963 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:04-259160 util-scheduler-8620 DEBUG Running task: 2395 / 0x4d6ff98
Jul 07 20:47:04-259367 util-scheduler-8620 DEBUG Adding task: 2398 / 0x4d6ff98
Jul 07 20:47:04-259590 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:04-259787 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:04-259984 util-scheduler-8620 DEBUG Adding task: 2399 / 0x46620a0
Jul 07 20:47:04-260228 util-scheduler-8620 DEBUG Checking readiness of task: 2399 / 0x46620a0
Jul 07 20:47:04-260422 util-scheduler-8620 DEBUG Checking readiness of task: 2397 / 0x4d5e5d8
Jul 07 20:47:04-260613 util-scheduler-8620 DEBUG Checking readiness of task: 2396 / 0x46620a0
Jul 07 20:47:04-260802 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-260992 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-261182 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-261394 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-261583 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-261773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-261961 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-262152 util-scheduler-8620 DEBUG Running task: 2397 / 0x4d5e5d8
Jul 07 20:47:04-262334 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:04-262511 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-262691 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-262901 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:47:04-263150 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:04-263359 util-scheduler-8620 DEBUG Running task: 2399 / 0x46620a0
Jul 07 20:47:04-263544 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:04-263719 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-263888 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-264066 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:04-264260 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:04-264464 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:04-264707 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:04-924159 util-scheduler-8620 DEBUG Checking readiness of task: 2396 / 0x46620a0
Jul 07 20:47:04-924537 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-924735 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-924929 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-925120 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-925398 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-925589 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-925782 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-925978 util-scheduler-8620 DEBUG Running task: 2396 / 0x46620a0
Jul 07 20:47:04-926402 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:04-926659 util-scheduler-8620 DEBUG Adding task: 2400 / 0x4662248
Jul 07 20:47:04-926939 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-927132 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-927324 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-927514 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-927706 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-927896 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-928086 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-928275 util-scheduler-8620 DEBUG Running task: 2400 / 0x4662248
Jul 07 20:47:04-928467 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:04-928667 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:04-928900 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:04-929109 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:04-929344 util-scheduler-8620 DEBUG Adding task: 2401 / 0x46620a0
Jul 07 20:47:04-929531 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:04-929738 util-scheduler-8620 DEBUG Adding task: 2402 / 0x46620a0
Jul 07 20:47:04-929983 util-scheduler-8620 DEBUG Checking readiness of task: 2402 / 0x46620a0
Jul 07 20:47:04-930179 util-scheduler-8620 DEBUG Checking readiness of task: 2401 / 0x46620a0
Jul 07 20:47:04-930371 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-930561 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-930751 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-930941 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-931130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-931319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-931506 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-931699 util-scheduler-8620 DEBUG Running task: 2401 / 0x46620a0
Jul 07 20:47:04-931882 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:04-932062 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-932234 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-932424 util-scheduler-8620 DEBUG Canceling task: 2398 / 0x4d6ff98
Jul 07 20:47:04-932648 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:04-932869 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:04-933108 cadet-p2p-8620 DEBUG Checking 0x56eb100 towards CMHCKRVP (->V8XX)
Jul 07 20:47:04-933396 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:04-933576 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:04-933769 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:04-934037 cadet-p2p-8620 INFO snd {               ACK} ( 86) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:47:04-934232 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:04-934414 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:04-934602 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:47:04-934777 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:04-934960 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:47:04-935134 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:04-935356 cadet-p2p-8620 DEBUG Checking 0x56ea578 towards CMHCKRVP (->V8XX)
Jul 07 20:47:04-935589 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:04-935772 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 18
Jul 07 20:47:04-935948 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:04-936174 cadet-p2p-8620 DEBUG Checking 0x56ea578 towards CMHCKRVP (->V8XX)
Jul 07 20:47:04-936404 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:04-936585 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 18
Jul 07 20:47:04-936758 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:04-936924 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:04-937128 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:04-937371 util-scheduler-8620 DEBUG Adding task: 2403 / 0x4d6ff98
Jul 07 20:47:04-937551 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:04-937728 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:04-937926 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:04-938103 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:04-938277 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:04-938516 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:04-938712 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:04-938890 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:04-939088 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:04-939297 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:04-939481 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:04-939685 util-scheduler-8620 DEBUG Adding task: 2404 / 0x4d6ff98
Jul 07 20:47:04-939903 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:04-940099 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:04-940300 util-scheduler-8620 DEBUG Adding task: 2405 / 0x46620a0
Jul 07 20:47:04-940501 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:04-940752 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:04-940949 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:04-941218 util-scheduler-8620 DEBUG Checking readiness of task: 2405 / 0x46620a0
Jul 07 20:47:04-941415 util-scheduler-8620 DEBUG Checking readiness of task: 2402 / 0x46620a0
Jul 07 20:47:04-941606 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-941795 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-941985 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-942175 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-942364 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-942552 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-942742 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-942931 util-scheduler-8620 DEBUG Running task: 2405 / 0x46620a0
Jul 07 20:47:04-943135 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:04-943324 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-943496 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-943674 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:04-943868 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:04-944057 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:04-944298 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:04-944504 util-scheduler-8620 DEBUG Running task: 2403 / 0x4d6ff98
Jul 07 20:47:04-944696 util-scheduler-8620 DEBUG Canceling task: 2404 / 0x4d6ff98
Jul 07 20:47:04-944909 util-scheduler-8620 DEBUG Adding task: 2406 / 0x4d6ff98
Jul 07 20:47:04-945124 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:04-945344 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:04-945543 util-scheduler-8620 DEBUG Adding task: 2407 / 0x46620a0
Jul 07 20:47:04-945781 util-scheduler-8620 DEBUG Checking readiness of task: 2407 / 0x46620a0
Jul 07 20:47:04-945975 util-scheduler-8620 DEBUG Checking readiness of task: 2402 / 0x46620a0
Jul 07 20:47:04-946166 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:04-946355 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:04-946545 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:04-946735 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:04-946926 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:04-947115 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:04-947303 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:04-947494 util-scheduler-8620 DEBUG Running task: 2407 / 0x46620a0
Jul 07 20:47:04-947677 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:04-947853 util-8620 DEBUG process_notify is running
Jul 07 20:47:04-948021 util-8620 DEBUG client_notify is running
Jul 07 20:47:04-948196 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:04-948385 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:04-948573 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:04-948815 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:06-523888 util-scheduler-8620 DEBUG Checking readiness of task: 2402 / 0x46620a0
Jul 07 20:47:06-524266 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:06-524465 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:06-524657 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:06-524849 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:06-525040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:06-525263 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:06-525456 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:06-525652 util-scheduler-8620 DEBUG Running task: 2402 / 0x46620a0
Jul 07 20:47:06-526070 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:06-526323 util-scheduler-8620 DEBUG Adding task: 2408 / 0x4662248
Jul 07 20:47:06-526598 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:06-526793 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:06-526985 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:06-527176 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:06-527399 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:06-527590 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:06-527779 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:06-527969 util-scheduler-8620 DEBUG Running task: 2408 / 0x4662248
Jul 07 20:47:06-528160 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:06-528359 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:06-528589 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:06-528795 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:06-529001 util-scheduler-8620 DEBUG Adding task: 2409 / 0x46620a0
Jul 07 20:47:06-529215 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:06-529423 util-scheduler-8620 DEBUG Adding task: 2410 / 0x46620a0
Jul 07 20:47:06-529670 util-scheduler-8620 DEBUG Checking readiness of task: 2410 / 0x46620a0
Jul 07 20:47:06-529863 util-scheduler-8620 DEBUG Checking readiness of task: 2409 / 0x46620a0
Jul 07 20:47:06-530056 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:06-530246 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:06-530436 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:06-530625 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:06-530815 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:06-531003 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:06-531193 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:06-531385 util-scheduler-8620 DEBUG Running task: 2409 / 0x46620a0
Jul 07 20:47:06-531570 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:06-531749 util-8620 DEBUG process_notify is running
Jul 07 20:47:06-531920 util-8620 DEBUG client_notify is running
Jul 07 20:47:06-532110 util-scheduler-8620 DEBUG Canceling task: 2406 / 0x4d6ff98
Jul 07 20:47:06-532334 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:06-532554 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:06-532792 cadet-p2p-8620 DEBUG Checking 0x56ea578 towards CMHCKRVP (->V8XX)
Jul 07 20:47:06-533025 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:06-533233 cadet-con-8620 DEBUG  last ack recv: 82, last pid sent: 18
Jul 07 20:47:06-533410 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:06-533631 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:06-533810 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:47:06-533984 cadet-p2p-8620 DEBUG   payload ID 19
Jul 07 20:47:06-534269 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:47:06-534464 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:06-534643 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:06-534830 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:47:06-535019 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:47:06-535247 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:06-535422 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:47:06-535595 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:47:06-535766 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:47:06-535964 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:47:06-536139 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:47:06-536340 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:06-536520 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:06-536701 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:06-536879 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:06-537056 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:06-537266 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:06-537436 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:06-537669 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:06-537855 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:06-538033 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:06-538219 util-scheduler-8620 DEBUG Canceling task: 2389 / 0x4d707d0
Jul 07 20:47:06-538431 util-scheduler-8620 DEBUG Adding task: 2411 / 0x4d707d0
Jul 07 20:47:06-538682 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:06-538859 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:47:06-539037 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 19
Jul 07 20:47:06-539211 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:06-539392 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:47:06-539608 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:06-539786 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:06-539960 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:06-540170 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:06-540549 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:47:06-540736 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:47:06-540917 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:06-541258 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:47:06-541610 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:07-383115 util-scheduler-8620 DEBUG Checking readiness of task: 2410 / 0x46620a0
Jul 07 20:47:07-383505 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:07-383702 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:07-383894 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:07-384085 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:07-384275 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:07-384464 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:07-384653 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:07-384849 util-scheduler-8620 DEBUG Running task: 2410 / 0x46620a0
Jul 07 20:47:07-385292 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:07-385550 util-scheduler-8620 DEBUG Adding task: 2412 / 0x4662248
Jul 07 20:47:07-385830 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:07-386028 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:07-386219 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:07-386409 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:07-386598 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:07-386788 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:07-386977 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:07-387167 util-scheduler-8620 DEBUG Running task: 2412 / 0x4662248
Jul 07 20:47:07-387357 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:47:07-387558 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:47:07-387788 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:47:07-388054 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:47:07-388309 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:07-388520 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:07-388704 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:47:07-388877 cadet-con-8620 DEBUG   ACK 83 (was 82)
Jul 07 20:47:07-389139 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:07-390266 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:07-390480 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:07-390666 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:47:07-390844 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:07-391060 util-scheduler-8620 DEBUG Adding task: 2413 / 0x46620a0
Jul 07 20:47:08-545081 util-scheduler-8620 DEBUG Checking readiness of task: 2413 / 0x46620a0
Jul 07 20:47:08-545490 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-545691 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-545883 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-546076 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-546267 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-546457 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-546647 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-546842 util-scheduler-8620 DEBUG Running task: 2413 / 0x46620a0
Jul 07 20:47:08-547264 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:08-547520 util-scheduler-8620 DEBUG Adding task: 2414 / 0x4662248
Jul 07 20:47:08-547800 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-547994 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-548185 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-548375 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-548565 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-548754 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-548945 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-549135 util-scheduler-8620 DEBUG Running task: 2414 / 0x4662248
Jul 07 20:47:08-549356 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:08-549563 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:08-549799 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:08-550067 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:47:08-550316 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:47:08-550551 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:08-550760 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:08-551007 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:08-551217 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:08-551408 cadet-con-8620 DEBUG  PID 23 (expected 23+)
Jul 07 20:47:08-551591 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:08-551782 util-scheduler-8620 DEBUG Canceling task: 2393 / 0x4d707d0
Jul 07 20:47:08-552011 util-scheduler-8620 DEBUG Adding task: 2415 / 0x4d707d0
Jul 07 20:47:08-552193 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:08-552456 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:08-552677 util-scheduler-8620 DEBUG Adding task: 2416 / 0x4d5e5d8
Jul 07 20:47:08-552865 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:08-553033 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:08-556740 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:08-558220 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:08-558457 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:47:08-561369 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:47:08-561577 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:47:08-561813 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:47:08-562024 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:47:08-562264 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:47:08-562465 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:08-562648 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:08-562832 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:08-563024 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:08-563201 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:08-563371 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:08-563539 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:08-563775 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:08-563961 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:08-564253 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:47:08-564425 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:08-564610 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:47:08-568196 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:47:08-568848 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:47:08-569081 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:08-569293 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:47:08-572447 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:08-572687 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:47:08-572870 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:08-573093 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:47:08-573311 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:47:08-573586 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:47:08-573785 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:47:08-573962 cadet-con-8620 DEBUG last pid sent 19
Jul 07 20:47:08-574135 cadet-con-8620 DEBUG      ack recv 83
Jul 07 20:47:08-574308 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:47:08-574486 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:47:08-574720 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:08-574927 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:08-575240 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:47:08-575440 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:08-575664 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:08-575847 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 19
Jul 07 20:47:08-576023 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:08-576232 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:47:08-576451 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:08-576683 util-scheduler-8620 DEBUG Adding task: 2417 / 0x4d6ff98
Jul 07 20:47:08-576864 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:08-577068 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:08-577271 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:08-577447 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:08-577687 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:08-577883 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:08-578060 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:08-578257 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:08-578488 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:08-578665 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:08-578838 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:08-579010 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:08-579229 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:47:08-579411 cadet-con-8620 DEBUG  ACK 87
Jul 07 20:47:08-579590 cadet-con-8620 DEBUG  last pid 23, last ack 86, qmax 11, q 0
Jul 07 20:47:08-579855 cadet-con-8620 INFO --> {               ACK} ( 87) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:47:08-580066 cadet-con-8620 DEBUG  ack 87
Jul 07 20:47:08-580244 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:47:08-580477 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:08-580683 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:08-580973 cadet-p2p-8620 INFO que {               ACK} ( 87) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:47:08-581171 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:08-581416 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:08-581599 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 19
Jul 07 20:47:08-581772 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:08-581972 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:08-582174 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:08-582350 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:08-582524 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:08-582758 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:08-582940 cadet-p2p-8620 DEBUG QQQ    payload , 87
Jul 07 20:47:08-583115 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:08-583348 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:08-583541 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:08-583718 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:08-583913 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:08-584097 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:08-584309 util-scheduler-8620 DEBUG Adding task: 2418 / 0x46620a0
Jul 07 20:47:08-584583 util-scheduler-8620 DEBUG Checking readiness of task: 2418 / 0x46620a0
Jul 07 20:47:08-584781 util-scheduler-8620 DEBUG Checking readiness of task: 2416 / 0x4d5e5d8
Jul 07 20:47:08-584974 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-585164 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-585379 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-585569 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-585759 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-585947 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-586138 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-586331 util-scheduler-8620 DEBUG Running task: 2416 / 0x4d5e5d8
Jul 07 20:47:08-586519 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:08-586697 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-586872 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-587119 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:08-587327 util-scheduler-8620 DEBUG Adding task: 2419 / 0x4d5e5d8
Jul 07 20:47:08-587531 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:08-587786 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:08-587985 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:08-588194 util-scheduler-8620 DEBUG Running task: 2417 / 0x4d6ff98
Jul 07 20:47:08-588403 util-scheduler-8620 DEBUG Adding task: 2420 / 0x4d6ff98
Jul 07 20:47:08-588626 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:08-588823 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:08-589021 util-scheduler-8620 DEBUG Adding task: 2421 / 0x46620a0
Jul 07 20:47:08-589287 util-scheduler-8620 DEBUG Checking readiness of task: 2421 / 0x46620a0
Jul 07 20:47:08-589486 util-scheduler-8620 DEBUG Checking readiness of task: 2419 / 0x4d5e5d8
Jul 07 20:47:08-589677 util-scheduler-8620 DEBUG Checking readiness of task: 2418 / 0x46620a0
Jul 07 20:47:08-589885 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-590076 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-590266 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-590457 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-590646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-590836 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-591025 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-591216 util-scheduler-8620 DEBUG Running task: 2419 / 0x4d5e5d8
Jul 07 20:47:08-591401 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:08-591575 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-591745 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-591958 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:47:08-592202 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:08-592412 util-scheduler-8620 DEBUG Running task: 2421 / 0x46620a0
Jul 07 20:47:08-592597 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:08-592772 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-592941 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-593120 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:08-593339 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:08-593529 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:08-593769 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:08-594018 util-scheduler-8620 DEBUG Checking readiness of task: 2418 / 0x46620a0
Jul 07 20:47:08-594210 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-594401 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-594591 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-594782 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-594970 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-595160 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-595348 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-595539 util-scheduler-8620 DEBUG Running task: 2418 / 0x46620a0
Jul 07 20:47:08-595942 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:08-596170 util-scheduler-8620 DEBUG Adding task: 2422 / 0x4662248
Jul 07 20:47:08-596417 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-596610 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-596802 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-596992 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-597182 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-597394 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-597583 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-597772 util-scheduler-8620 DEBUG Running task: 2422 / 0x4662248
Jul 07 20:47:08-597963 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:08-598158 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:08-598375 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:08-598572 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:08-598786 util-scheduler-8620 DEBUG Adding task: 2423 / 0x46620a0
Jul 07 20:47:08-598970 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:08-599169 util-scheduler-8620 DEBUG Adding task: 2424 / 0x46620a0
Jul 07 20:47:08-599411 util-scheduler-8620 DEBUG Checking readiness of task: 2424 / 0x46620a0
Jul 07 20:47:08-599606 util-scheduler-8620 DEBUG Checking readiness of task: 2423 / 0x46620a0
Jul 07 20:47:08-599797 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-599988 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-600178 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-600369 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-600558 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-600749 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-600938 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-601128 util-scheduler-8620 DEBUG Running task: 2423 / 0x46620a0
Jul 07 20:47:08-601337 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:08-601513 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-601682 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-601868 util-scheduler-8620 DEBUG Canceling task: 2420 / 0x4d6ff98
Jul 07 20:47:08-602089 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:08-602306 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:08-602538 cadet-p2p-8620 DEBUG Checking 0x5719068 towards CMHCKRVP (->V8XX)
Jul 07 20:47:08-602771 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:08-602950 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:08-603137 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:08-603403 cadet-p2p-8620 INFO snd {               ACK} ( 87) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:47:08-603597 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:08-603777 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:08-603964 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:47:08-604138 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:08-604322 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:47:08-604496 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:08-604716 cadet-p2p-8620 DEBUG Checking 0x5718590 towards CMHCKRVP (->V8XX)
Jul 07 20:47:08-604948 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:08-605130 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 19
Jul 07 20:47:08-605329 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:08-605556 cadet-p2p-8620 DEBUG Checking 0x5718590 towards CMHCKRVP (->V8XX)
Jul 07 20:47:08-605785 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:08-605966 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 19
Jul 07 20:47:08-606139 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:08-606305 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:08-606507 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:08-606718 util-scheduler-8620 DEBUG Adding task: 2425 / 0x4d6ff98
Jul 07 20:47:08-606896 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:08-607072 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:08-607270 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:08-607444 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:08-607635 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:08-607879 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:08-608075 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:08-608252 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:08-608449 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:08-608655 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:08-608838 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:08-609062 util-scheduler-8620 DEBUG Adding task: 2426 / 0x4d6ff98
Jul 07 20:47:08-609318 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:08-609516 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:08-609718 util-scheduler-8620 DEBUG Adding task: 2427 / 0x46620a0
Jul 07 20:47:08-609919 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:08-610168 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:08-610365 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:08-610617 util-scheduler-8620 DEBUG Checking readiness of task: 2427 / 0x46620a0
Jul 07 20:47:08-610815 util-scheduler-8620 DEBUG Checking readiness of task: 2424 / 0x46620a0
Jul 07 20:47:08-611009 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-611201 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-611392 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-611582 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-611772 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-611962 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-612152 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-612345 util-scheduler-8620 DEBUG Running task: 2427 / 0x46620a0
Jul 07 20:47:08-612529 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:08-612707 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-612879 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-613057 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:08-613275 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:08-613465 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:08-613705 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:08-613911 util-scheduler-8620 DEBUG Running task: 2425 / 0x4d6ff98
Jul 07 20:47:08-614105 util-scheduler-8620 DEBUG Canceling task: 2426 / 0x4d6ff98
Jul 07 20:47:08-614322 util-scheduler-8620 DEBUG Adding task: 2428 / 0x4d6ff98
Jul 07 20:47:08-614538 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:08-614733 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:08-614932 util-scheduler-8620 DEBUG Adding task: 2429 / 0x46620a0
Jul 07 20:47:08-615174 util-scheduler-8620 DEBUG Checking readiness of task: 2429 / 0x46620a0
Jul 07 20:47:08-615369 util-scheduler-8620 DEBUG Checking readiness of task: 2424 / 0x46620a0
Jul 07 20:47:08-615560 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-615750 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-615940 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-616131 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-616320 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-616509 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-616698 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-616887 util-scheduler-8620 DEBUG Running task: 2424 / 0x46620a0
Jul 07 20:47:08-617311 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:08-617538 util-scheduler-8620 DEBUG Adding task: 2430 / 0x4662248
Jul 07 20:47:08-617747 util-scheduler-8620 DEBUG Running task: 2429 / 0x46620a0
Jul 07 20:47:08-617932 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:08-618108 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-618293 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-618471 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:08-618660 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:08-618849 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:08-619090 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:08-619335 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-619531 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-619721 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-619912 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-620101 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-620291 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-620480 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-620669 util-scheduler-8620 DEBUG Running task: 2430 / 0x4662248
Jul 07 20:47:08-620858 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:08-621052 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:08-621286 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:08-621469 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:08-621670 util-scheduler-8620 DEBUG Adding task: 2431 / 0x46620a0
Jul 07 20:47:08-621909 util-scheduler-8620 DEBUG Checking readiness of task: 2431 / 0x46620a0
Jul 07 20:47:08-622103 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-622293 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-622483 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-622673 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-622862 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-623050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-623238 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-623429 util-scheduler-8620 DEBUG Running task: 2431 / 0x46620a0
Jul 07 20:47:08-623827 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:08-624048 util-scheduler-8620 DEBUG Adding task: 2432 / 0x4662248
Jul 07 20:47:08-624292 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-624486 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-624678 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-624869 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-625058 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-625268 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-625458 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-625647 util-scheduler-8620 DEBUG Running task: 2432 / 0x4662248
Jul 07 20:47:08-625837 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:08-626027 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:08-626238 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:08-626434 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:08-626631 util-scheduler-8620 DEBUG Adding task: 2433 / 0x46620a0
Jul 07 20:47:08-626815 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:08-627012 util-scheduler-8620 DEBUG Adding task: 2434 / 0x46620a0
Jul 07 20:47:08-627266 util-scheduler-8620 DEBUG Checking readiness of task: 2434 / 0x46620a0
Jul 07 20:47:08-627459 util-scheduler-8620 DEBUG Checking readiness of task: 2433 / 0x46620a0
Jul 07 20:47:08-627652 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:08-627841 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:08-628030 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:08-628222 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:08-628411 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:08-628600 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:08-628788 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:08-628979 util-scheduler-8620 DEBUG Running task: 2433 / 0x46620a0
Jul 07 20:47:08-629162 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:08-629360 util-8620 DEBUG process_notify is running
Jul 07 20:47:08-629532 util-8620 DEBUG client_notify is running
Jul 07 20:47:08-629714 util-scheduler-8620 DEBUG Canceling task: 2428 / 0x4d6ff98
Jul 07 20:47:08-629934 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:08-630147 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:08-630379 cadet-p2p-8620 DEBUG Checking 0x5718590 towards CMHCKRVP (->V8XX)
Jul 07 20:47:08-630619 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:08-630802 cadet-con-8620 DEBUG  last ack recv: 83, last pid sent: 19
Jul 07 20:47:08-630975 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:08-631195 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:08-631372 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:47:08-631547 cadet-p2p-8620 DEBUG   payload ID 20
Jul 07 20:47:08-631826 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:47:08-632020 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:08-632197 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:08-632383 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:47:08-632570 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:47:08-632797 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:08-632972 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:47:08-633144 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:47:08-633337 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:47:08-633535 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:47:08-633709 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:47:08-633910 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:08-634089 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:08-634273 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:08-634452 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:08-634628 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:08-634798 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:08-634964 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:08-635196 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:08-635380 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:08-635557 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:08-635742 util-scheduler-8620 DEBUG Canceling task: 2411 / 0x4d707d0
Jul 07 20:47:08-635952 util-scheduler-8620 DEBUG Adding task: 2435 / 0x4d707d0
Jul 07 20:47:08-636204 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:08-636382 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:47:08-636560 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 20
Jul 07 20:47:08-636732 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:08-636911 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:47:08-637114 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:08-637329 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:08-637504 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:08-637702 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:08-637906 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:47:08-638089 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:47:08-638267 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:08-638455 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:47:08-638699 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:09-112117 util-scheduler-8620 DEBUG Checking readiness of task: 2434 / 0x46620a0
Jul 07 20:47:09-112462 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:09-112661 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:09-112855 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:09-113046 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:09-113265 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:09-113457 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:09-113647 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:09-113841 util-scheduler-8620 DEBUG Running task: 2434 / 0x46620a0
Jul 07 20:47:09-114259 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:09-114511 util-scheduler-8620 DEBUG Adding task: 2436 / 0x4662248
Jul 07 20:47:09-114783 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:09-114975 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:09-115166 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:09-115357 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:09-115546 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:09-115736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:09-115926 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:09-116117 util-scheduler-8620 DEBUG Running task: 2436 / 0x4662248
Jul 07 20:47:09-116308 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:47:09-116508 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:47:09-116735 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:47:09-117001 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:47:09-117282 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:09-117493 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:09-117677 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:47:09-117852 cadet-con-8620 DEBUG   ACK 84 (was 83)
Jul 07 20:47:09-118081 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:09-118312 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:09-118520 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:09-118703 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:47:09-118878 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:09-119087 util-scheduler-8620 DEBUG Adding task: 2437 / 0x46620a0
Jul 07 20:47:13-201724 util-scheduler-8620 DEBUG Checking readiness of task: 2437 / 0x46620a0
Jul 07 20:47:13-202119 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-202324 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-202518 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-202711 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-202904 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-203131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-203324 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-203520 util-scheduler-8620 DEBUG Running task: 2437 / 0x46620a0
Jul 07 20:47:13-203944 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:13-204203 util-scheduler-8620 DEBUG Adding task: 2438 / 0x4662248
Jul 07 20:47:13-204487 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-204680 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-204870 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-205061 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-205276 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-205469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-205659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-205850 util-scheduler-8620 DEBUG Running task: 2438 / 0x4662248
Jul 07 20:47:13-206043 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:13-206245 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:13-206481 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:13-206749 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:47:13-207000 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:47:13-207231 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:13-207440 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:13-207686 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:13-207908 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:13-208097 cadet-con-8620 DEBUG  PID 24 (expected 24+)
Jul 07 20:47:13-208279 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:13-208469 util-scheduler-8620 DEBUG Canceling task: 2415 / 0x4d707d0
Jul 07 20:47:13-208695 util-scheduler-8620 DEBUG Adding task: 2439 / 0x4d707d0
Jul 07 20:47:13-208874 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:13-209133 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:13-209377 util-scheduler-8620 DEBUG Adding task: 2440 / 0x4d5e5d8
Jul 07 20:47:13-209563 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:13-209732 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:13-213321 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:13-214156 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:13-214367 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:47:13-217660 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:47:13-217869 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:47:13-218097 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:47:13-218308 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:47:13-218516 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:47:13-218716 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:13-218896 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:13-219078 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:13-219257 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:13-219433 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:13-219602 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:13-219770 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:13-220004 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:13-220189 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:13-220479 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:47:13-220650 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:13-220863 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:47:13-223933 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:47:13-225079 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:47:13-225337 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:13-225526 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:47:13-228170 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:13-228408 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:47:13-228590 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:13-228812 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:47:13-229005 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:47:13-229301 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:47:13-229502 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:47:13-229680 cadet-con-8620 DEBUG last pid sent 20
Jul 07 20:47:13-229854 cadet-con-8620 DEBUG      ack recv 84
Jul 07 20:47:13-230030 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:47:13-230208 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:47:13-230442 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:13-230650 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:13-230961 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:47:13-231162 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:13-231387 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:13-231570 cadet-con-8620 DEBUG  last ack recv: 84, last pid sent: 20
Jul 07 20:47:13-231746 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:13-231950 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:47:13-232167 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:13-232391 util-scheduler-8620 DEBUG Adding task: 2441 / 0x4d6ff98
Jul 07 20:47:13-232571 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:13-232774 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:13-232951 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:13-233125 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:13-233387 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:13-233582 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:13-233759 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:13-233957 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:13-234186 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:13-234362 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:13-234536 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:13-234706 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:13-234926 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:47:13-235105 cadet-con-8620 DEBUG  ACK 88
Jul 07 20:47:13-235283 cadet-con-8620 DEBUG  last pid 24, last ack 87, qmax 11, q 0
Jul 07 20:47:13-235546 cadet-con-8620 INFO --> {               ACK} ( 88) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:47:13-235735 cadet-con-8620 DEBUG  ack 88
Jul 07 20:47:13-235911 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:47:13-236142 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:13-236347 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:13-236637 cadet-p2p-8620 INFO que {               ACK} ( 88) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:47:13-236834 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:13-237059 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:13-237262 cadet-con-8620 DEBUG  last ack recv: 84, last pid sent: 20
Jul 07 20:47:13-237450 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:13-237648 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:13-237849 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:13-238044 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:13-238220 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:13-238454 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:13-238638 cadet-p2p-8620 DEBUG QQQ    payload , 88
Jul 07 20:47:13-238813 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:13-239045 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:13-239237 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:13-239414 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:13-239609 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:13-239792 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:13-240002 util-scheduler-8620 DEBUG Adding task: 2442 / 0x46620a0
Jul 07 20:47:13-240274 util-scheduler-8620 DEBUG Checking readiness of task: 2442 / 0x46620a0
Jul 07 20:47:13-240470 util-scheduler-8620 DEBUG Checking readiness of task: 2440 / 0x4d5e5d8
Jul 07 20:47:13-240662 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-240852 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-241041 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-241253 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-241443 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-241633 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-241821 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-242015 util-scheduler-8620 DEBUG Running task: 2440 / 0x4d5e5d8
Jul 07 20:47:13-242200 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:13-242379 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-242552 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-242797 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:13-243005 util-scheduler-8620 DEBUG Adding task: 2443 / 0x4d5e5d8
Jul 07 20:47:13-243208 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:13-243468 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:13-243666 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:13-243863 util-scheduler-8620 DEBUG Running task: 2441 / 0x4d6ff98
Jul 07 20:47:13-244072 util-scheduler-8620 DEBUG Adding task: 2444 / 0x4d6ff98
Jul 07 20:47:13-244294 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:13-244490 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:13-244687 util-scheduler-8620 DEBUG Adding task: 2445 / 0x46620a0
Jul 07 20:47:13-244931 util-scheduler-8620 DEBUG Checking readiness of task: 2445 / 0x46620a0
Jul 07 20:47:13-245127 util-scheduler-8620 DEBUG Checking readiness of task: 2443 / 0x4d5e5d8
Jul 07 20:47:13-245341 util-scheduler-8620 DEBUG Checking readiness of task: 2442 / 0x46620a0
Jul 07 20:47:13-245533 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-245723 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-245912 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-246101 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-246290 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-246479 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-246667 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-246857 util-scheduler-8620 DEBUG Running task: 2443 / 0x4d5e5d8
Jul 07 20:47:13-247043 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:13-247218 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-247387 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-247620 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:47:13-247866 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:13-248077 util-scheduler-8620 DEBUG Running task: 2445 / 0x46620a0
Jul 07 20:47:13-248261 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:13-248436 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-248604 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-248781 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:13-248975 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:13-249163 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:13-249425 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:13-358902 util-scheduler-8620 DEBUG Checking readiness of task: 2442 / 0x46620a0
Jul 07 20:47:13-359194 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-359390 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-359583 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-359775 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-359966 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-360160 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-360350 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-360545 util-scheduler-8620 DEBUG Running task: 2442 / 0x46620a0
Jul 07 20:47:13-360958 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:13-361227 util-scheduler-8620 DEBUG Adding task: 2446 / 0x4662248
Jul 07 20:47:13-361495 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-361689 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-361880 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-362071 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-362261 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-362450 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-362639 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-362828 util-scheduler-8620 DEBUG Running task: 2446 / 0x4662248
Jul 07 20:47:13-363019 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:13-363216 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:13-363442 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:13-363645 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:13-363846 util-scheduler-8620 DEBUG Adding task: 2447 / 0x46620a0
Jul 07 20:47:13-364033 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:13-364235 util-scheduler-8620 DEBUG Adding task: 2448 / 0x46620a0
Jul 07 20:47:13-364476 util-scheduler-8620 DEBUG Checking readiness of task: 2448 / 0x46620a0
Jul 07 20:47:13-364668 util-scheduler-8620 DEBUG Checking readiness of task: 2447 / 0x46620a0
Jul 07 20:47:13-364860 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-365050 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-365262 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-365454 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-365643 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-365833 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-366044 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-366237 util-scheduler-8620 DEBUG Running task: 2447 / 0x46620a0
Jul 07 20:47:13-366422 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:13-366599 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-366769 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-366957 util-scheduler-8620 DEBUG Canceling task: 2444 / 0x4d6ff98
Jul 07 20:47:13-367183 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:13-367403 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:13-367642 cadet-p2p-8620 DEBUG Checking 0x57474a8 towards CMHCKRVP (->V8XX)
Jul 07 20:47:13-367877 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:13-368069 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:13-368260 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:13-368598 cadet-p2p-8620 INFO snd {               ACK} ( 88) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:47:13-368794 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:13-368974 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:13-369160 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:47:13-369357 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:13-369540 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:47:13-369714 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:13-369935 cadet-p2p-8620 DEBUG Checking 0x57469b0 towards CMHCKRVP (->V8XX)
Jul 07 20:47:13-370166 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:13-370349 cadet-con-8620 DEBUG  last ack recv: 84, last pid sent: 20
Jul 07 20:47:13-370523 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:13-370749 cadet-p2p-8620 DEBUG Checking 0x57469b0 towards CMHCKRVP (->V8XX)
Jul 07 20:47:13-370978 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:13-371159 cadet-con-8620 DEBUG  last ack recv: 84, last pid sent: 20
Jul 07 20:47:13-371331 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:13-371497 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:13-371700 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:13-371916 util-scheduler-8620 DEBUG Adding task: 2449 / 0x4d6ff98
Jul 07 20:47:13-372095 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:13-372273 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:13-372471 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:13-372646 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:13-372819 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:13-373056 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:13-373273 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:13-373451 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:13-373648 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:13-373853 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:13-374037 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:13-374239 util-scheduler-8620 DEBUG Adding task: 2450 / 0x4d6ff98
Jul 07 20:47:13-374455 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:13-374649 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:13-374850 util-scheduler-8620 DEBUG Adding task: 2451 / 0x46620a0
Jul 07 20:47:13-375048 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:13-375295 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:13-375491 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:13-375739 util-scheduler-8620 DEBUG Checking readiness of task: 2451 / 0x46620a0
Jul 07 20:47:13-375933 util-scheduler-8620 DEBUG Checking readiness of task: 2448 / 0x46620a0
Jul 07 20:47:13-376122 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-376332 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-376522 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-376712 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-376901 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-377093 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-377304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-377496 util-scheduler-8620 DEBUG Running task: 2451 / 0x46620a0
Jul 07 20:47:13-377680 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:13-377855 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-378025 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-378202 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:13-378395 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:13-378583 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:13-378859 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:13-379063 util-scheduler-8620 DEBUG Running task: 2449 / 0x4d6ff98
Jul 07 20:47:13-379255 util-scheduler-8620 DEBUG Canceling task: 2450 / 0x4d6ff98
Jul 07 20:47:13-379468 util-scheduler-8620 DEBUG Adding task: 2452 / 0x4d6ff98
Jul 07 20:47:13-379682 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:13-379875 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:13-380072 util-scheduler-8620 DEBUG Adding task: 2453 / 0x46620a0
Jul 07 20:47:13-380311 util-scheduler-8620 DEBUG Checking readiness of task: 2453 / 0x46620a0
Jul 07 20:47:13-380504 util-scheduler-8620 DEBUG Checking readiness of task: 2448 / 0x46620a0
Jul 07 20:47:13-380694 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-380884 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-381074 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-381285 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-381476 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-381664 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-381852 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-382043 util-scheduler-8620 DEBUG Running task: 2453 / 0x46620a0
Jul 07 20:47:13-382225 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:13-382400 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-382568 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-382743 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:13-382932 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:13-383118 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:13-383357 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:13-489085 util-scheduler-8620 DEBUG Checking readiness of task: 2448 / 0x46620a0
Jul 07 20:47:13-489328 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-489522 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-489713 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-489904 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-490094 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-490283 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-490472 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-490682 util-scheduler-8620 DEBUG Running task: 2448 / 0x46620a0
Jul 07 20:47:13-491087 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:13-491319 util-scheduler-8620 DEBUG Adding task: 2454 / 0x4662248
Jul 07 20:47:13-491570 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-491764 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-491955 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-492145 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-492334 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-492523 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-492711 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-492899 util-scheduler-8620 DEBUG Running task: 2454 / 0x4662248
Jul 07 20:47:13-493089 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:13-493305 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:13-493521 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:13-493718 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:13-493916 util-scheduler-8620 DEBUG Adding task: 2455 / 0x46620a0
Jul 07 20:47:13-494099 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:13-494297 util-scheduler-8620 DEBUG Adding task: 2456 / 0x46620a0
Jul 07 20:47:13-494537 util-scheduler-8620 DEBUG Checking readiness of task: 2456 / 0x46620a0
Jul 07 20:47:13-494741 util-scheduler-8620 DEBUG Checking readiness of task: 2455 / 0x46620a0
Jul 07 20:47:13-494931 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:13-495121 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:13-495310 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:13-495500 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:13-495689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:13-495878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:13-496066 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:13-496257 util-scheduler-8620 DEBUG Running task: 2455 / 0x46620a0
Jul 07 20:47:13-496440 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:13-496616 util-8620 DEBUG process_notify is running
Jul 07 20:47:13-496785 util-8620 DEBUG client_notify is running
Jul 07 20:47:13-496968 util-scheduler-8620 DEBUG Canceling task: 2452 / 0x4d6ff98
Jul 07 20:47:13-497208 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:13-497426 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:13-497656 cadet-p2p-8620 DEBUG Checking 0x57469b0 towards CMHCKRVP (->V8XX)
Jul 07 20:47:13-497886 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:13-498067 cadet-con-8620 DEBUG  last ack recv: 84, last pid sent: 20
Jul 07 20:47:13-498239 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:13-498458 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:13-498635 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:47:13-498808 cadet-p2p-8620 DEBUG   payload ID 21
Jul 07 20:47:13-499088 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:47:13-499281 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:13-499457 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:13-499643 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:47:13-499829 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:47:13-500057 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:13-500250 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:47:13-500422 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:47:13-500593 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:47:13-500789 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:47:13-500963 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:47:13-501162 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:13-501364 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:13-501544 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:13-501721 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:13-501897 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:13-502066 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:13-502232 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:13-502468 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:13-502653 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:13-502830 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:13-503015 util-scheduler-8620 DEBUG Canceling task: 2435 / 0x4d707d0
Jul 07 20:47:13-503226 util-scheduler-8620 DEBUG Adding task: 2457 / 0x4d707d0
Jul 07 20:47:13-503477 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:13-503654 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:47:13-503833 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 21
Jul 07 20:47:13-504005 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:13-504184 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:47:13-504382 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:13-504558 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:13-504731 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:13-504928 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:13-505131 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:47:13-505338 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:47:13-505516 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:13-505705 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:47:13-505951 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:14-128471 util-scheduler-8620 DEBUG Checking readiness of task: 2456 / 0x46620a0
Jul 07 20:47:14-128797 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:14-128995 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:14-129210 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:14-129406 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:14-129600 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:14-129793 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:14-129987 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:14-130185 util-scheduler-8620 DEBUG Running task: 2456 / 0x46620a0
Jul 07 20:47:14-130604 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:14-130859 util-scheduler-8620 DEBUG Adding task: 2458 / 0x4662248
Jul 07 20:47:14-131141 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:14-131341 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:14-131534 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:14-131726 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:14-131916 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:14-132106 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:14-132295 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:14-132508 util-scheduler-8620 DEBUG Running task: 2458 / 0x4662248
Jul 07 20:47:14-132700 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:47:14-132898 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:47:14-133126 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:47:14-133417 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:47:14-133672 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:14-133882 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:14-134066 cadet-con-8620 DEBUG   FWD ACK
Jul 07 20:47:14-134239 cadet-con-8620 DEBUG   ACK 85 (was 84)
Jul 07 20:47:14-134467 cadet-con-8620 DEBUG connection_unlock_queue FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:14-134699 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:14-134904 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:14-135086 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:47:14-135261 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:14-135468 util-scheduler-8620 DEBUG Adding task: 2459 / 0x46620a0
Jul 07 20:47:17-928642 util-scheduler-8620 DEBUG Checking readiness of task: 2459 / 0x46620a0
Jul 07 20:47:17-929029 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:17-929250 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:17-929447 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:17-929643 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:17-929837 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:17-930029 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:17-930221 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:17-930418 util-scheduler-8620 DEBUG Running task: 2459 / 0x46620a0
Jul 07 20:47:17-930845 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:17-931107 util-scheduler-8620 DEBUG Adding task: 2460 / 0x4662248
Jul 07 20:47:17-931398 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:17-931595 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:17-931803 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:17-931998 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:17-932191 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:17-932384 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:17-932575 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:17-932767 util-scheduler-8620 DEBUG Running task: 2460 / 0x4662248
Jul 07 20:47:17-932958 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:17-933159 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:17-933418 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:17-933682 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection CMHCKRVP from V8XX
Jul 07 20:47:17-933927 cadet-con-8620 DEBUG   connection CMHCKRVP (->V8XX)
Jul 07 20:47:17-934155 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:17-934364 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:17-934608 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:17-934820 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:17-935010 cadet-con-8620 DEBUG  PID 25 (expected 25+)
Jul 07 20:47:17-935192 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:17-935381 util-scheduler-8620 DEBUG Canceling task: 2439 / 0x4d707d0
Jul 07 20:47:17-935606 util-scheduler-8620 DEBUG Adding task: 2461 / 0x4d707d0
Jul 07 20:47:17-935785 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:17-936046 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:17-936298 util-scheduler-8620 DEBUG Adding task: 2462 / 0x4d5e5d8
Jul 07 20:47:17-936485 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:17-936653 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:17-940738 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:17-941590 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:17-941803 cadet-tun-8620 INFO   HMAC with key VJ50N9K4
Jul 07 20:47:17-945054 cadet-tun-8620 INFO <=== {              DATA} on V8XX
Jul 07 20:47:17-945280 cadet-tun-8620 DEBUG  payload of type 586 (UNKNOWN TYPE)
Jul 07 20:47:17-945511 cadet-tun-8620 DEBUG WARNING channel 0x40000000 unknown
Jul 07 20:47:17-945721 cadet-tun-8620 DEBUG WARNING destroying unknown channel 1073741824 on tunnel V8XX
Jul 07 20:47:17-945931 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:47:17-946132 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:17-946313 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:17-946496 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:17-946675 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:17-946852 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:17-947021 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:17-947190 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:17-947424 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:17-947609 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:17-947900 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:47:17-948072 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:17-948257 cadet-tun-8620 INFO   ENC with key WNEQZBYQ
Jul 07 20:47:17-951323 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:47:17-951967 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:47:17-952204 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:47:17-952393 cadet-tun-8620 INFO   HMAC with key WNEQZBYQ
Jul 07 20:47:17-955583 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:17-955823 cadet-tun-8620 DEBUG   connection CMHCKRVP (->V8XX): 3
Jul 07 20:47:17-956007 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:17-956229 cadet-tun-8620 DEBUG  selected: connection CMHCKRVP (->V8XX)
Jul 07 20:47:17-956422 cadet-tun-8620 DEBUG type {   CHANNEL_DESTROY}
Jul 07 20:47:17-956696 cadet-con-8620 INFO --> {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (88 bytes)
Jul 07 20:47:17-956897 cadet-con-8620 DEBUG   Q_N+ 0x4d707d4 0
Jul 07 20:47:17-957075 cadet-con-8620 DEBUG last pid sent 21
Jul 07 20:47:17-957271 cadet-con-8620 DEBUG      ack recv 85
Jul 07 20:47:17-957444 cadet-con-8620 DEBUG   not droppable, Q_N stays the same
Jul 07 20:47:17-957621 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:47:17-957859 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:17-958066 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:17-958377 cadet-p2p-8620 INFO que {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 88)
Jul 07 20:47:17-958578 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:17-958801 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:17-958985 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:47:17-959160 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:17-959365 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 88 bytes
Jul 07 20:47:17-959581 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:17-959807 util-scheduler-8620 DEBUG Adding task: 2463 / 0x4d6ff98
Jul 07 20:47:17-959987 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:17-960190 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:17-960367 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:17-960541 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:17-960778 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:17-960972 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:17-961173 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:17-961393 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:17-961638 cadet-con-8620 DEBUG GMC send BCK ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:17-961815 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:17-961989 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:17-962159 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:17-962378 cadet-con-8620 DEBUG connection send BCK ack on CMHCKRVP (->V8XX)
Jul 07 20:47:17-962555 cadet-con-8620 DEBUG  ACK 89
Jul 07 20:47:17-962733 cadet-con-8620 DEBUG  last pid 25, last ack 88, qmax 11, q 0
Jul 07 20:47:17-962996 cadet-con-8620 INFO --> {               ACK} ( 89) on connection CMHCKRVP (->V8XX) (40 bytes)
Jul 07 20:47:17-963185 cadet-con-8620 DEBUG  ack 89
Jul 07 20:47:17-963362 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 1
Jul 07 20:47:17-963593 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:17-963800 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:17-964087 cadet-p2p-8620 INFO que {               ACK} ( 89) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 40)
Jul 07 20:47:17-964284 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:17-964506 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:17-964688 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:47:17-964861 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:17-965059 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:17-965280 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:17-965456 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:17-965630 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:17-965863 cadet-p2p-8620 DEBUG QQQ  - {               ACK} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:17-966045 cadet-p2p-8620 DEBUG QQQ    payload , 89
Jul 07 20:47:17-966220 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:17-966452 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:17-966645 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:17-966820 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:17-967015 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:17-967197 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:17-967408 util-scheduler-8620 DEBUG Adding task: 2464 / 0x46620a0
Jul 07 20:47:17-967680 util-scheduler-8620 DEBUG Checking readiness of task: 2464 / 0x46620a0
Jul 07 20:47:17-967878 util-scheduler-8620 DEBUG Checking readiness of task: 2462 / 0x4d5e5d8
Jul 07 20:47:17-968069 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:17-968260 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:17-968450 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:17-968640 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:17-968829 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:17-969018 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:17-969226 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:17-969421 util-scheduler-8620 DEBUG Running task: 2462 / 0x4d5e5d8
Jul 07 20:47:17-969608 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:17-969787 util-8620 DEBUG process_notify is running
Jul 07 20:47:17-969959 util-8620 DEBUG client_notify is running
Jul 07 20:47:17-970205 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:17-970412 util-scheduler-8620 DEBUG Adding task: 2465 / 0x4d5e5d8
Jul 07 20:47:17-970615 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:17-970879 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:17-971078 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:17-971291 util-scheduler-8620 DEBUG Running task: 2463 / 0x4d6ff98
Jul 07 20:47:17-971501 util-scheduler-8620 DEBUG Adding task: 2466 / 0x4d6ff98
Jul 07 20:47:17-971727 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:17-971923 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:17-972120 util-scheduler-8620 DEBUG Adding task: 2467 / 0x46620a0
Jul 07 20:47:17-972364 util-scheduler-8620 DEBUG Checking readiness of task: 2467 / 0x46620a0
Jul 07 20:47:17-972558 util-scheduler-8620 DEBUG Checking readiness of task: 2465 / 0x4d5e5d8
Jul 07 20:47:17-972749 util-scheduler-8620 DEBUG Checking readiness of task: 2464 / 0x46620a0
Jul 07 20:47:17-972939 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:17-973129 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:17-973343 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:17-973534 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:17-973724 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:17-973912 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:17-974102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:17-974291 util-scheduler-8620 DEBUG Running task: 2465 / 0x4d5e5d8
Jul 07 20:47:17-974474 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:17-974650 util-8620 DEBUG process_notify is running
Jul 07 20:47:17-974818 util-8620 DEBUG client_notify is running
Jul 07 20:47:17-975030 util-8620 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 20:47:17-975275 util-8620 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:17-975484 util-scheduler-8620 DEBUG Running task: 2467 / 0x46620a0
Jul 07 20:47:17-975668 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:17-975842 util-8620 DEBUG process_notify is running
Jul 07 20:47:17-976011 util-8620 DEBUG client_notify is running
Jul 07 20:47:17-976189 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:17-976383 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:17-976571 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:17-976811 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:18-437926 util-scheduler-8620 DEBUG Checking readiness of task: 2464 / 0x46620a0
Jul 07 20:47:18-438241 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:18-438438 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:18-438630 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:18-438822 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:18-439012 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:18-439202 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:18-439391 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:18-439585 util-scheduler-8620 DEBUG Running task: 2464 / 0x46620a0
Jul 07 20:47:18-440000 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:18-440246 util-scheduler-8620 DEBUG Adding task: 2468 / 0x4662248
Jul 07 20:47:18-440514 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:18-440706 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:18-440897 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:18-441087 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:18-441301 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:18-441515 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:18-441706 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:18-441895 util-scheduler-8620 DEBUG Running task: 2468 / 0x4662248
Jul 07 20:47:18-442087 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:18-442284 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:18-442512 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:18-442715 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:18-442920 util-scheduler-8620 DEBUG Adding task: 2469 / 0x46620a0
Jul 07 20:47:18-443105 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:18-443309 util-scheduler-8620 DEBUG Adding task: 2470 / 0x46620a0
Jul 07 20:47:18-443552 util-scheduler-8620 DEBUG Checking readiness of task: 2470 / 0x46620a0
Jul 07 20:47:18-443744 util-scheduler-8620 DEBUG Checking readiness of task: 2469 / 0x46620a0
Jul 07 20:47:18-443947 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:18-444137 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:18-444327 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:18-444516 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:18-444706 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:18-444894 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:18-445084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:18-445298 util-scheduler-8620 DEBUG Running task: 2469 / 0x46620a0
Jul 07 20:47:18-445484 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:18-445662 util-8620 DEBUG process_notify is running
Jul 07 20:47:18-445832 util-8620 DEBUG client_notify is running
Jul 07 20:47:18-446021 util-scheduler-8620 DEBUG Canceling task: 2466 / 0x4d6ff98
Jul 07 20:47:18-446245 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:18-446464 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:18-446701 cadet-p2p-8620 DEBUG Checking 0x5775528 towards CMHCKRVP (->V8XX)
Jul 07 20:47:18-446934 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:18-447112 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:18-447301 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:18-447569 cadet-p2p-8620 INFO snd {               ACK} ( 89) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 40)
Jul 07 20:47:18-447763 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:18-447944 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:18-448130 cadet-con-8620 DEBUG  sent FWD {               ACK}
Jul 07 20:47:18-448311 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:18-448496 cadet-con-8620 DEBUG  C_P- 0x4d707d0 2
Jul 07 20:47:18-448670 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:18-448891 cadet-p2p-8620 DEBUG Checking 0x52c9070 towards CMHCKRVP (->V8XX)
Jul 07 20:47:18-449123 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:18-449330 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:47:18-449505 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:18-449731 cadet-p2p-8620 DEBUG Checking 0x52c9070 towards CMHCKRVP (->V8XX)
Jul 07 20:47:18-449961 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:18-450142 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:47:18-450313 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:18-450479 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:18-450682 core-api-8620 DEBUG Asking core for transmission of 88 bytes to `V8XX'
Jul 07 20:47:18-450895 util-scheduler-8620 DEBUG Adding task: 2471 / 0x4d6ff98
Jul 07 20:47:18-451074 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:18-451266 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:18-451467 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:18-451643 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:18-451817 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:18-452054 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:18-452249 cadet-p2p-8620 DEBUG QQQ    payload {   CHANNEL_DESTROY}, 0
Jul 07 20:47:18-452427 cadet-p2p-8620 DEBUG QQQ    size: 88 bytes
Jul 07 20:47:18-452624 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:18-452829 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:18-453013 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:18-453238 util-scheduler-8620 DEBUG Adding task: 2472 / 0x4d6ff98
Jul 07 20:47:18-453458 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:18-453652 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:18-453852 util-scheduler-8620 DEBUG Adding task: 2473 / 0x46620a0
Jul 07 20:47:18-454053 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:18-454298 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:18-454495 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:18-454741 util-scheduler-8620 DEBUG Checking readiness of task: 2473 / 0x46620a0
Jul 07 20:47:18-454936 util-scheduler-8620 DEBUG Checking readiness of task: 2470 / 0x46620a0
Jul 07 20:47:18-455126 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:18-455316 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:18-455504 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:18-455694 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:18-455883 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:18-456072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:18-456260 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:18-456450 util-scheduler-8620 DEBUG Running task: 2473 / 0x46620a0
Jul 07 20:47:18-456633 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:18-456808 util-8620 DEBUG process_notify is running
Jul 07 20:47:18-456977 util-8620 DEBUG client_notify is running
Jul 07 20:47:18-457155 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:18-457371 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:18-457561 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:18-457799 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:18-458005 util-scheduler-8620 DEBUG Running task: 2471 / 0x4d6ff98
Jul 07 20:47:18-458200 util-scheduler-8620 DEBUG Canceling task: 2472 / 0x4d6ff98
Jul 07 20:47:18-458415 util-scheduler-8620 DEBUG Adding task: 2474 / 0x4d6ff98
Jul 07 20:47:18-458630 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:18-458823 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:18-459021 util-scheduler-8620 DEBUG Adding task: 2475 / 0x46620a0
Jul 07 20:47:18-459257 util-scheduler-8620 DEBUG Checking readiness of task: 2475 / 0x46620a0
Jul 07 20:47:18-459450 util-scheduler-8620 DEBUG Checking readiness of task: 2470 / 0x46620a0
Jul 07 20:47:18-459639 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:18-459829 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:18-460018 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:18-460209 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:18-460397 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:18-460602 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:18-460792 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:18-460983 util-scheduler-8620 DEBUG Running task: 2475 / 0x46620a0
Jul 07 20:47:18-461167 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:18-461364 util-8620 DEBUG process_notify is running
Jul 07 20:47:18-461533 util-8620 DEBUG client_notify is running
Jul 07 20:47:18-461709 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:18-461897 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:18-462085 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:18-462324 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:19-030352 util-scheduler-8620 DEBUG Checking readiness of task: 2470 / 0x46620a0
Jul 07 20:47:19-030755 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-030963 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-031163 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-031362 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-031558 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-031753 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-031945 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-032146 util-scheduler-8620 DEBUG Running task: 2470 / 0x46620a0
Jul 07 20:47:19-032571 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:19-032833 util-scheduler-8620 DEBUG Adding task: 2476 / 0x4662248
Jul 07 20:47:19-033132 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-033358 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-033553 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-033746 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-033940 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-034132 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-034325 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-034518 util-scheduler-8620 DEBUG Running task: 2476 / 0x4662248
Jul 07 20:47:19-034713 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:19-034916 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:19-035153 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:19-035363 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:19-035573 util-scheduler-8620 DEBUG Adding task: 2477 / 0x46620a0
Jul 07 20:47:19-035764 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:19-035975 util-scheduler-8620 DEBUG Adding task: 2478 / 0x46620a0
Jul 07 20:47:19-036223 util-scheduler-8620 DEBUG Checking readiness of task: 2478 / 0x46620a0
Jul 07 20:47:19-036420 util-scheduler-8620 DEBUG Checking readiness of task: 2477 / 0x46620a0
Jul 07 20:47:19-036616 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-036810 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-037006 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-038127 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-038342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-038537 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-038762 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-038960 util-scheduler-8620 DEBUG Running task: 2477 / 0x46620a0
Jul 07 20:47:19-039165 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:19-039347 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-039523 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-039717 util-scheduler-8620 DEBUG Canceling task: 2474 / 0x4d6ff98
Jul 07 20:47:19-039951 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 88 bytes.
Jul 07 20:47:19-040176 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:19-040420 cadet-p2p-8620 DEBUG Checking 0x52c9070 towards CMHCKRVP (->V8XX)
Jul 07 20:47:19-040658 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:19-040844 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 21
Jul 07 20:47:19-041024 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:19-041270 cadet-p2p-8620 DEBUG   on connection CMHCKRVP (->V8XX) FWD
Jul 07 20:47:19-041455 cadet-p2p-8620 DEBUG   size 88 ok
Jul 07 20:47:19-041634 cadet-p2p-8620 DEBUG   payload ID 22
Jul 07 20:47:19-041925 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({   CHANNEL_DESTROY} 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD (size 88)
Jul 07 20:47:19-042125 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:19-042309 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:19-042500 cadet-con-8620 DEBUG  sent FWD {         ENCRYPTED}
Jul 07 20:47:19-042692 cadet-con-8620 DEBUG  C_P- 0x4d707d0 1
Jul 07 20:47:19-042926 cadet-con-8620 DEBUG GMC send FWD ACK on CMHCKRVP (->V8XX)
Jul 07 20:47:19-043103 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:47:19-043278 cadet-con-8620 DEBUG   buffer available: 11
Jul 07 20:47:19-043454 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:47:19-043654 cadet-tun-8620 DEBUG GCT_unchoke_channels on V8XX
Jul 07 20:47:19-043830 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:47:19-044034 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:47:19-044218 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:47:19-044402 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:47:19-044583 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:47:19-044764 cadet-tun-8620 DEBUG TTT  destroy 2065
Jul 07 20:47:19-044935 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:47:19-045104 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:47:19-045855 cadet-tun-8620 DEBUG TTT  - CMHCKRVP (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:47:19-046050 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:47:19-046233 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:19-046425 util-scheduler-8620 DEBUG Canceling task: 2457 / 0x4d707d0
Jul 07 20:47:19-046646 util-scheduler-8620 DEBUG Adding task: 2479 / 0x4d707d0
Jul 07 20:47:19-046901 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:19-047083 cadet-con-8620 DEBUG !  Q_N- 0x4d707d4 0
Jul 07 20:47:19-047266 cadet-con-8620 DEBUG !   forced, Q_N not accounting pid 22
Jul 07 20:47:19-047443 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:19-047628 cadet-p2p-8620 DEBUG   return 88
Jul 07 20:47:19-047833 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:19-048013 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:19-048190 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:19-048394 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:19-048603 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 88 bytes.
Jul 07 20:47:19-048790 core-api-8620 DEBUG Produced SEND message to core with 88 bytes payload
Jul 07 20:47:19-048974 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:19-049168 util-8620 DEBUG Transmitting message of type 76 and size 144 to core service.
Jul 07 20:47:19-050459 util-8620 DEBUG Connection transmitted 144/144 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:19-597611 util-scheduler-8620 DEBUG Checking readiness of task: 2478 / 0x46620a0
Jul 07 20:47:19-597977 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-598172 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-598364 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-598557 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-598748 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-598938 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-599127 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-599318 util-scheduler-8620 DEBUG Running task: 2065 / 0x4d64a70
Jul 07 20:47:19-599754 cadet-tun-8620 DEBUG delayed destroying tunnel 0x4d64a70
Jul 07 20:47:19-601786 cadet-con-8620 DEBUG   sending connection destroy for connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-603064 cadet-con-8620 INFO --> {CONNECTION_DESTROY} ( 0) on connection CMHCKRVP (->V8XX) (36 bytes)
Jul 07 20:47:19-603270 cadet-con-8620 DEBUG   C_P+ 0x4d707d0 0
Jul 07 20:47:19-603511 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:19-603724 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:19-604030 cadet-p2p-8620 INFO que {CONNECTION_DESTROY} ( 0) on connection CMHCKRVP (->V8XX) (0x4d707d0) FWD towards V8XX (size 36)
Jul 07 20:47:19-604228 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:19-604454 cadet-con-8620 DEBUG  checking sendability of FWD traffic on CMHCKRVP (->V8XX)
Jul 07 20:47:19-604658 cadet-con-8620 DEBUG  last ack recv: 85, last pid sent: 22
Jul 07 20:47:19-604839 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:19-605049 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:47:19-605302 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:47:19-605531 util-scheduler-8620 DEBUG Adding task: 2480 / 0x4d6ff98
Jul 07 20:47:19-605714 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:19-605918 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:19-606095 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:19-606272 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:19-606512 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} FWD on CMHCKRVP (->V8XX)
Jul 07 20:47:19-606697 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:19-606886 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:19-607086 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:19-607910 cadet-tun-8620 DEBUG destroying tunnel V8XX
Jul 07 20:47:19-608584 cadet-con-8620 DEBUG destroying connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-608925 cadet-con-8620 DEBUG  fc's f: 0x4d707d4, b: 0x4d70808
Jul 07 20:47:19-609292 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:19-609536 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-609962 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:19-610180 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:19-611639 cadet-p2p-8620 DEBUG GMP queue cancel {CONNECTION_DESTROY}
Jul 07 20:47:19-612361 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-612627 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:19-612841 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:19-613082 cadet-con-8620 DEBUG  get next hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:19-613315 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:19-613563 cadet-p2p-8620 DEBUG removing connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-613765 cadet-p2p-8620 DEBUG from peer V8XX
Jul 07 20:47:19-613970 cadet-p2p-8620 DEBUG peer V8XX ok, has 1 connections.
Jul 07 20:47:19-614216 cadet-con-8620 DEBUG  get prev hop CMHCKRVP (->V8XX) [0/2]
Jul 07 20:47:19-614424 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:19-614654 cadet-p2p-8620 DEBUG removing connection CMHCKRVP (->V8XX)
Jul 07 20:47:19-614854 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:47:19-615055 cadet-p2p-8620 DEBUG peer GN10 ok, has 4 connections.
Jul 07 20:47:19-615432 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:19-615841 cadet-tun-8620 DEBUG Removing connection CMHCKRVP (->V8XX) from tunnel V8XX
Jul 07 20:47:19-616302 util-scheduler-8620 DEBUG Canceling task: 2479 / 0x4d707d0
Jul 07 20:47:19-616515 util-scheduler-8620 DEBUG Canceling task: 2461 / 0x4d707d0
Jul 07 20:47:19-616818 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:19-617037 util-scheduler-8620 DEBUG Adding task: 2481 / 0x4d5e5d8
Jul 07 20:47:19-619678 dht-api-8620 DEBUG Sending STOP for V8XXK9GA to DHT via 0x46642c0
Jul 07 20:47:19-623569 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:47:19-623789 util-scheduler-8620 DEBUG Adding task: 2482 / 0x4665be0
Jul 07 20:47:19-624563 util-scheduler-8620 DEBUG Checking readiness of task: 2482 / 0x4665be0
Jul 07 20:47:19-624769 util-scheduler-8620 DEBUG Checking readiness of task: 2481 / 0x4d5e5d8
Jul 07 20:47:19-624963 util-scheduler-8620 DEBUG Checking readiness of task: 2478 / 0x46620a0
Jul 07 20:47:19-625155 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-625369 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-625561 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-625752 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-625942 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-626131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-626320 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-626513 util-scheduler-8620 DEBUG Running task: 2481 / 0x4d5e5d8
Jul 07 20:47:19-626700 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:19-626878 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-627051 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-627290 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:19-627497 util-scheduler-8620 DEBUG Adding task: 2483 / 0x4d5e5d8
Jul 07 20:47:19-627700 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:47:19-627959 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:19-628156 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:19-628353 util-scheduler-8620 DEBUG Running task: 2482 / 0x4665be0
Jul 07 20:47:19-628541 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:47:19-628715 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-628884 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-629078 dht-api-8620 DEBUG Forwarded request of 80 bytes to DHT service
Jul 07 20:47:19-629293 util-8620 DEBUG Transmitting message of type 144 and size 80 to dht service.
Jul 07 20:47:19-629535 util-8620 DEBUG Connection transmitted 80/80 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:47:19-629743 util-scheduler-8620 DEBUG Running task: 2480 / 0x4d6ff98
Jul 07 20:47:19-629956 util-scheduler-8620 DEBUG Adding task: 2484 / 0x4d6ff98
Jul 07 20:47:19-630187 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:19-630388 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:19-630587 util-scheduler-8620 DEBUG Adding task: 2485 / 0x46620a0
Jul 07 20:47:19-630834 util-scheduler-8620 DEBUG Checking readiness of task: 2485 / 0x46620a0
Jul 07 20:47:19-631027 util-scheduler-8620 DEBUG Checking readiness of task: 2483 / 0x4d5e5d8
Jul 07 20:47:19-631219 util-scheduler-8620 DEBUG Checking readiness of task: 2478 / 0x46620a0
Jul 07 20:47:19-631409 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-631598 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-631788 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-631999 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-632188 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-632377 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-632566 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-632756 util-scheduler-8620 DEBUG Running task: 2483 / 0x4d5e5d8
Jul 07 20:47:19-632940 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:19-633114 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-633307 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-633519 util-8620 DEBUG Transmitting message of type 168 and size 32 to statistics service.
Jul 07 20:47:19-633765 util-8620 DEBUG Connection transmitted 32/32 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:19-633975 util-scheduler-8620 DEBUG Running task: 2485 / 0x46620a0
Jul 07 20:47:19-634158 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:19-634332 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-634501 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-634679 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:19-634873 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:19-635062 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:19-635299 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:19-905109 util-scheduler-8620 DEBUG Checking readiness of task: 2478 / 0x46620a0
Jul 07 20:47:19-905448 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-905645 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-905838 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-906029 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-906220 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-906410 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-906600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-906796 util-scheduler-8620 DEBUG Running task: 2478 / 0x46620a0
Jul 07 20:47:19-907214 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:19-907461 util-scheduler-8620 DEBUG Adding task: 2486 / 0x4662248
Jul 07 20:47:19-907727 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-907920 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-908111 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-908301 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-908504 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-908693 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-908882 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-909071 util-scheduler-8620 DEBUG Running task: 2486 / 0x4662248
Jul 07 20:47:19-909285 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:47:19-909487 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:47:19-909825 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `V8XX'
Jul 07 20:47:19-910284 cadet-con-8620 INFO <-- {               ACK} on connection CMHCKRVP from V8XX
Jul 07 20:47:19-910866 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:19-911091 util-scheduler-8620 DEBUG Adding task: 2487 / 0x4d5e5d8
Jul 07 20:47:19-912801 cadet-con-8620 INFO ===> BROKEN on unknown connection CMHCKRVP
Jul 07 20:47:19-915884 cadet-p2p-8620 INFO que { CONNECTION_BROKEN} ( 2) on connection NULL ((nil))  towards V8XX (size 100)
Jul 07 20:47:19-916121 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:19-916547 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:19-916759 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:19-916939 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:47:19-917117 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:19-917332 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} FWD on NULL
Jul 07 20:47:19-917515 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:19-917692 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:19-917881 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_BROKEN}  on NULL
Jul 07 20:47:19-918060 cadet-p2p-8620 DEBUG QQQ    payload , 2
Jul 07 20:47:19-918234 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:47:19-918434 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:19-919038 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:19-919253 util-scheduler-8620 DEBUG Adding task: 2488 / 0x46620a0
Jul 07 20:47:19-919514 util-scheduler-8620 DEBUG Checking readiness of task: 2488 / 0x46620a0
Jul 07 20:47:19-919710 util-scheduler-8620 DEBUG Checking readiness of task: 2487 / 0x4d5e5d8
Jul 07 20:47:19-919903 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:19-920094 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:19-920284 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:19-920474 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:19-920663 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:19-920853 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:19-921041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:19-921252 util-scheduler-8620 DEBUG Running task: 2487 / 0x4d5e5d8
Jul 07 20:47:19-921439 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:19-921632 util-8620 DEBUG process_notify is running
Jul 07 20:47:19-921803 util-8620 DEBUG client_notify is running
Jul 07 20:47:19-922025 util-8620 DEBUG Transmitting message of type 168 and size 50 to statistics service.
Jul 07 20:47:19-922281 util-8620 DEBUG Connection transmitted 50/50 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:20-942949 util-scheduler-8620 DEBUG Checking readiness of task: 2488 / 0x46620a0
Jul 07 20:47:20-943316 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:20-943514 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:20-943707 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:20-943899 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:20-944091 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:20-944293 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:20-944483 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:20-944679 util-scheduler-8620 DEBUG Running task: 2488 / 0x46620a0
Jul 07 20:47:20-945098 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:20-945375 util-scheduler-8620 DEBUG Adding task: 2489 / 0x4662248
Jul 07 20:47:20-945652 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:20-945845 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:20-946036 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:20-946226 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:20-946416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:20-946606 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:20-946794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:20-947014 util-scheduler-8620 DEBUG Running task: 2489 / 0x4662248
Jul 07 20:47:20-947208 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:20-947407 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:20-947637 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:20-947843 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:20-948050 util-scheduler-8620 DEBUG Adding task: 2490 / 0x46620a0
Jul 07 20:47:20-948237 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:20-948441 util-scheduler-8620 DEBUG Adding task: 2491 / 0x46620a0
Jul 07 20:47:20-948685 util-scheduler-8620 DEBUG Checking readiness of task: 2491 / 0x46620a0
Jul 07 20:47:20-948877 util-scheduler-8620 DEBUG Checking readiness of task: 2490 / 0x46620a0
Jul 07 20:47:20-949069 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:20-949279 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:20-949469 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:20-949660 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:20-949848 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:20-950038 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:20-950225 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:20-950417 util-scheduler-8620 DEBUG Running task: 2490 / 0x46620a0
Jul 07 20:47:20-950602 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:20-950780 util-8620 DEBUG process_notify is running
Jul 07 20:47:20-950952 util-8620 DEBUG client_notify is running
Jul 07 20:47:20-951140 util-scheduler-8620 DEBUG Canceling task: 2484 / 0x4d6ff98
Jul 07 20:47:20-951367 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:47:20-951586 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:20-951779 cadet-p2p-8620 DEBUG Checking 0x577ae58 towards NULL
Jul 07 20:47:20-951971 cadet-p2p-8620 DEBUG   on connection NULL FWD
Jul 07 20:47:20-952147 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:47:20-952337 cadet-p2p-8620 DEBUG   raw {CONNECTION_DESTROY}
Jul 07 20:47:20-952557 cadet-p2p-8620 INFO snd {CONNECTION_DESTROY} ( 0) on connection NULL ((nil)) FWD (size 36)
Jul 07 20:47:20-952750 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:20-952928 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:20-953115 cadet-con-8620 DEBUG  sent FWD {CONNECTION_DESTROY}
Jul 07 20:47:20-953536 cadet-p2p-8620 DEBUG Checking 0x577d0f0 towards NULL
Jul 07 20:47:20-953736 cadet-p2p-8620 DEBUG Checking 0x577d0f0 towards NULL
Jul 07 20:47:20-953917 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:20-954253 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:47:20-954475 util-scheduler-8620 DEBUG Adding task: 2492 / 0x4d6ff98
Jul 07 20:47:20-954655 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:20-954832 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:47:20-955031 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:20-955207 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:20-955383 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:20-955579 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_BROKEN}  on NULL
Jul 07 20:47:20-955759 cadet-p2p-8620 DEBUG QQQ    payload , 2
Jul 07 20:47:20-955934 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:47:20-956132 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:20-956338 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:47:20-956521 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:47:20-956737 util-scheduler-8620 DEBUG Adding task: 2493 / 0x4d6ff98
Jul 07 20:47:20-956955 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:20-957167 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:20-957392 util-scheduler-8620 DEBUG Adding task: 2494 / 0x46620a0
Jul 07 20:47:20-957592 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:47:20-957843 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:20-958040 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:20-958292 util-scheduler-8620 DEBUG Checking readiness of task: 2494 / 0x46620a0
Jul 07 20:47:20-958486 util-scheduler-8620 DEBUG Checking readiness of task: 2491 / 0x46620a0
Jul 07 20:47:20-958677 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:20-958867 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:20-959057 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:20-959247 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:20-959435 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:20-959624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:20-959814 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:20-960005 util-scheduler-8620 DEBUG Running task: 2494 / 0x46620a0
Jul 07 20:47:20-960189 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:20-960365 util-8620 DEBUG process_notify is running
Jul 07 20:47:20-960535 util-8620 DEBUG client_notify is running
Jul 07 20:47:20-960713 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:20-960907 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:20-961095 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:20-961355 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:20-961561 util-scheduler-8620 DEBUG Running task: 2492 / 0x4d6ff98
Jul 07 20:47:20-961754 util-scheduler-8620 DEBUG Canceling task: 2493 / 0x4d6ff98
Jul 07 20:47:20-961968 util-scheduler-8620 DEBUG Adding task: 2495 / 0x4d6ff98
Jul 07 20:47:20-962184 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:20-962380 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:20-962579 util-scheduler-8620 DEBUG Adding task: 2496 / 0x46620a0
Jul 07 20:47:20-962818 util-scheduler-8620 DEBUG Checking readiness of task: 2496 / 0x46620a0
Jul 07 20:47:20-963012 util-scheduler-8620 DEBUG Checking readiness of task: 2491 / 0x46620a0
Jul 07 20:47:20-963203 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:20-963391 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:20-963581 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:20-963769 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:20-963959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:20-964147 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:20-964336 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:20-964525 util-scheduler-8620 DEBUG Running task: 2496 / 0x46620a0
Jul 07 20:47:20-964710 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:20-964883 util-8620 DEBUG process_notify is running
Jul 07 20:47:20-965053 util-8620 DEBUG client_notify is running
Jul 07 20:47:20-965250 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:20-965441 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:20-965628 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:20-965867 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:21-073068 util-scheduler-8620 DEBUG Checking readiness of task: 2491 / 0x46620a0
Jul 07 20:47:21-073399 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-073598 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-073793 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-073986 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-074180 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-074372 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-074565 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-074759 util-scheduler-8620 DEBUG Running task: 2491 / 0x46620a0
Jul 07 20:47:21-075166 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:21-075403 util-scheduler-8620 DEBUG Adding task: 2497 / 0x4662248
Jul 07 20:47:21-075660 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-075855 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-076048 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-076241 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-076434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-076626 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-076817 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-077008 util-scheduler-8620 DEBUG Running task: 2497 / 0x4662248
Jul 07 20:47:21-077224 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:21-077423 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:21-077644 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:21-077844 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:21-078047 util-scheduler-8620 DEBUG Adding task: 2498 / 0x46620a0
Jul 07 20:47:21-078234 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:21-078437 util-scheduler-8620 DEBUG Adding task: 2499 / 0x46620a0
Jul 07 20:47:21-078680 util-scheduler-8620 DEBUG Checking readiness of task: 2499 / 0x46620a0
Jul 07 20:47:21-078877 util-scheduler-8620 DEBUG Checking readiness of task: 2498 / 0x46620a0
Jul 07 20:47:21-079070 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-079265 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-079457 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-079651 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-079859 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-080052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-080242 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-080435 util-scheduler-8620 DEBUG Running task: 2498 / 0x46620a0
Jul 07 20:47:21-080621 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:21-080800 util-8620 DEBUG process_notify is running
Jul 07 20:47:21-080972 util-8620 DEBUG client_notify is running
Jul 07 20:47:21-081157 util-scheduler-8620 DEBUG Canceling task: 2495 / 0x4d6ff98
Jul 07 20:47:21-081412 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:47:21-081631 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:21-081816 cadet-p2p-8620 DEBUG Checking 0x577d0f0 towards NULL
Jul 07 20:47:21-082002 cadet-p2p-8620 DEBUG   on connection NULL 
Jul 07 20:47:21-082178 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:47:21-082367 cadet-p2p-8620 DEBUG   raw { CONNECTION_BROKEN}
Jul 07 20:47:21-082584 cadet-p2p-8620 INFO snd { CONNECTION_BROKEN} ( 2) on connection NULL ((nil))  (size 100)
Jul 07 20:47:21-083053 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:47:21-083263 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:21-083443 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:21-083620 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:21-083821 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:21-084027 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:47:21-084212 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:47:21-084392 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:21-084585 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:47:21-084833 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:21-796704 util-scheduler-8620 DEBUG Checking readiness of task: 2499 / 0x46620a0
Jul 07 20:47:21-797362 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-797663 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-798047 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-798245 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-798437 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-798629 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-798820 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-799020 util-scheduler-8620 DEBUG Running task: 2499 / 0x46620a0
Jul 07 20:47:21-799441 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:21-799693 util-scheduler-8620 DEBUG Adding task: 2500 / 0x4662248
Jul 07 20:47:21-799967 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-800160 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-800351 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-800540 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-800730 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-800920 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-801109 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-801323 util-scheduler-8620 DEBUG Running task: 2500 / 0x4662248
Jul 07 20:47:21-801514 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:47:21-801714 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:47:21-801942 core-api-8620 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 20:47:21-802141 cadet-con-8620 DEBUG     path has 2 hops.
Jul 07 20:47:21-802384 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection NCSKBW46 from V8XX
Jul 07 20:47:21-802590 cadet-con-8620 DEBUG     origin: V8XX
Jul 07 20:47:21-802931 cadet-con-8620 DEBUG   Creating path...
Jul 07 20:47:21-803153 cadet-con-8620 DEBUG   - 0: taking V8XX
Jul 07 20:47:21-803343 cadet-con-8620 DEBUG     storing at 0
Jul 07 20:47:21-803544 cadet-con-8620 DEBUG   - 1: taking GN10
Jul 07 20:47:21-803725 cadet-con-8620 DEBUG     storing at 1
Jul 07 20:47:21-803994 cadet-con-8620 DEBUG   Own position: 1
Jul 07 20:47:21-804261 cadet-con-8620 DEBUG   Creating connection
Jul 07 20:47:21-804511 cadet-con-8620 DEBUG  get next hop NCSKBW46 [1/2]
Jul 07 20:47:21-804722 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:21-804929 cadet-con-8620 DEBUG  get prev hop NCSKBW46 [1/2]
Jul 07 20:47:21-805136 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:21-805362 cadet-con-8620 DEBUG register neighbors for connection NCSKBW46
Jul 07 20:47:21-805524 cadet-8620 DEBUG PATH:
Jul 07 20:47:21-805707 cadet-8620 DEBUG   V8XX
Jul 07 20:47:21-805916 cadet-8620 DEBUG   GN10
Jul 07 20:47:21-806072 cadet-8620 DEBUG END
Jul 07 20:47:21-806240 cadet-con-8620 DEBUG own pos 1
Jul 07 20:47:21-806430 cadet-con-8620 DEBUG putting connection NCSKBW46 to next peer 0x4d5be88
Jul 07 20:47:21-806641 cadet-con-8620 DEBUG next peer 0x4d5be88 GN10
Jul 07 20:47:21-806837 cadet-con-8620 DEBUG putting connection NCSKBW46 to prev peer 0x4d64970
Jul 07 20:47:21-807046 cadet-con-8620 DEBUG prev peer 0x4d64970 V8XX
Jul 07 20:47:21-807239 cadet-p2p-8620 DEBUG adding connection NCSKBW46
Jul 07 20:47:21-807440 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:47:21-807641 cadet-p2p-8620 DEBUG peer GN10 ok, has 3 connections.
Jul 07 20:47:21-807832 cadet-p2p-8620 DEBUG  now has 4 connections.
Jul 07 20:47:21-808005 cadet-p2p-8620 DEBUG result 1
Jul 07 20:47:21-808190 cadet-p2p-8620 DEBUG adding connection NCSKBW46
Jul 07 20:47:21-808388 cadet-p2p-8620 DEBUG to peer V8XX
Jul 07 20:47:21-808589 cadet-p2p-8620 DEBUG peer V8XX ok, has 0 connections.
Jul 07 20:47:21-808775 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:47:21-808948 cadet-p2p-8620 DEBUG result 1
Jul 07 20:47:21-809128 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:21-809362 util-scheduler-8620 DEBUG Adding task: 2501 / 0x52cba38
Jul 07 20:47:21-809567 cadet-con-8620 DEBUG Connection NCSKBW46 state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:47:21-809762 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:47:21-809979 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:47:21-810159 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:47:21-810333 cadet-p2p-8620 DEBUG   already known
Jul 07 20:47:21-810590 cadet-tun-8620 DEBUG add connection NCSKBW46 (->V8XX)
Jul 07 20:47:21-810791 cadet-tun-8620 DEBUG  to tunnel V8XX
Jul 07 20:47:21-810999 util-scheduler-8620 DEBUG Adding task: 2502 / 0x52cbfb8
Jul 07 20:47:21-811214 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_NEW => CADET_TUNNEL_WAITING
Jul 07 20:47:21-811450 cadet-con-8620 INFO ===> {           FWD ACK} on connection NCSKBW46 (->V8XX)
Jul 07 20:47:21-811685 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:21-811889 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:21-812187 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 36)
Jul 07 20:47:21-812384 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:21-812609 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:21-812792 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:21-812967 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:21-813173 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:47:21-813411 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:47:21-813625 util-scheduler-8620 DEBUG Adding task: 2503 / 0x4d6ff98
Jul 07 20:47:21-813804 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:21-814007 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:21-814183 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:21-814357 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:21-814594 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:21-814779 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:21-814955 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:21-815152 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:21-815385 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_SENT
Jul 07 20:47:21-815624 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:47:21-815830 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:21-816042 util-scheduler-8620 DEBUG Adding task: 2504 / 0x46620a0
Jul 07 20:47:21-816290 util-scheduler-8620 DEBUG Checking readiness of task: 2504 / 0x46620a0
Jul 07 20:47:21-816483 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-816691 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-816881 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-817071 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-817283 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-817473 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-817662 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-817851 util-scheduler-8620 DEBUG Running task: 2503 / 0x4d6ff98
Jul 07 20:47:21-818057 util-scheduler-8620 DEBUG Adding task: 2505 / 0x4d6ff98
Jul 07 20:47:21-818279 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:21-818482 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:21-818682 util-scheduler-8620 DEBUG Adding task: 2506 / 0x46620a0
Jul 07 20:47:21-818880 util-scheduler-8620 DEBUG Running task: 2502 / 0x52cbfb8
Jul 07 20:47:21-819126 util-scheduler-8620 DEBUG Checking readiness of task: 2506 / 0x46620a0
Jul 07 20:47:21-819319 util-scheduler-8620 DEBUG Checking readiness of task: 2504 / 0x46620a0
Jul 07 20:47:21-819522 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:21-819712 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:21-819902 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:21-820092 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:21-820282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:21-820470 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:21-820658 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:21-820849 util-scheduler-8620 DEBUG Running task: 2506 / 0x46620a0
Jul 07 20:47:21-821034 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:21-821232 util-8620 DEBUG process_notify is running
Jul 07 20:47:21-821406 util-8620 DEBUG client_notify is running
Jul 07 20:47:21-821585 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:21-821780 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:21-821971 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:21-822221 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:22-928754 util-scheduler-8620 DEBUG Checking readiness of task: 2504 / 0x46620a0
Jul 07 20:47:22-929122 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:22-929350 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:22-929546 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:22-929743 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:22-929935 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:22-930127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:22-930318 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:22-930519 util-scheduler-8620 DEBUG Running task: 2504 / 0x46620a0
Jul 07 20:47:22-930945 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:22-931205 util-scheduler-8620 DEBUG Adding task: 2507 / 0x4662248
Jul 07 20:47:22-931488 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:22-931684 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:22-931876 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:22-932067 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:22-932258 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:22-932488 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:22-932683 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:22-932874 util-scheduler-8620 DEBUG Running task: 2507 / 0x4662248
Jul 07 20:47:22-933067 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 20:47:22-933291 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 20:47:22-933524 core-api-8620 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 20:47:22-933726 cadet-con-8620 DEBUG     path has 2 hops.
Jul 07 20:47:22-933969 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection NCSKBW46 from V8XX
Jul 07 20:47:22-934176 cadet-con-8620 DEBUG     origin: V8XX
Jul 07 20:47:22-934399 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:47:22-934622 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:47:22-934803 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:47:22-934977 cadet-p2p-8620 DEBUG   already known
Jul 07 20:47:22-935221 cadet-tun-8620 DEBUG add connection NCSKBW46 (->V8XX)
Jul 07 20:47:22-935421 cadet-tun-8620 DEBUG  to tunnel V8XX
Jul 07 20:47:22-935651 cadet-con-8620 INFO ===> {           FWD ACK} on connection NCSKBW46 (->V8XX)
Jul 07 20:47:22-935886 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:22-936093 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:22-936387 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 36)
Jul 07 20:47:22-936583 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:22-936808 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:22-936991 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:22-937166 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:22-937397 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:22-937600 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:22-937774 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:47:22-937948 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:22-938187 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:22-938370 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:22-938545 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:22-938776 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:22-938957 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:22-939132 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:22-939330 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:22-939564 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 20:47:22-939804 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:47:22-940011 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:22-940223 util-scheduler-8620 DEBUG Adding task: 2508 / 0x46620a0
Jul 07 20:47:23-768683 util-scheduler-8620 DEBUG Checking readiness of task: 2508 / 0x46620a0
Jul 07 20:47:23-769026 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-769253 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-769479 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-769673 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-769867 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-770077 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-770282 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-770477 util-scheduler-8620 DEBUG Running task: 2508 / 0x46620a0
Jul 07 20:47:23-770922 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:23-771198 util-scheduler-8620 DEBUG Adding task: 2509 / 0x4662248
Jul 07 20:47:23-771470 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-771664 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-771856 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-772046 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-772237 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-772426 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-772615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-772803 util-scheduler-8620 DEBUG Running task: 2509 / 0x4662248
Jul 07 20:47:23-772997 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:23-773221 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:23-773449 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:23-773657 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:23-773863 util-scheduler-8620 DEBUG Adding task: 2510 / 0x46620a0
Jul 07 20:47:23-774050 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:23-774253 util-scheduler-8620 DEBUG Adding task: 2511 / 0x46620a0
Jul 07 20:47:23-774496 util-scheduler-8620 DEBUG Checking readiness of task: 2511 / 0x46620a0
Jul 07 20:47:23-774689 util-scheduler-8620 DEBUG Checking readiness of task: 2510 / 0x46620a0
Jul 07 20:47:23-774881 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-775070 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-775260 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-775448 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-775637 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-775839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-776027 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-776219 util-scheduler-8620 DEBUG Running task: 2510 / 0x46620a0
Jul 07 20:47:23-776403 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:23-776581 util-8620 DEBUG process_notify is running
Jul 07 20:47:23-776753 util-8620 DEBUG client_notify is running
Jul 07 20:47:23-776942 util-scheduler-8620 DEBUG Canceling task: 2505 / 0x4d6ff98
Jul 07 20:47:23-777167 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:47:23-777425 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:23-777663 cadet-p2p-8620 DEBUG Checking 0x57836b8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:23-777897 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:23-778074 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:47:23-778243 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:47:23-778413 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:47:23-778602 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:47:23-778860 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 36)
Jul 07 20:47:23-779054 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:23-779233 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:23-779420 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:47:23-779600 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:47:23-779810 util-scheduler-8620 DEBUG Adding task: 2512 / 0x52cba38
Jul 07 20:47:23-780048 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:47:23-780220 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:23-780440 cadet-p2p-8620 DEBUG Checking 0x52cc968 towards NCSKBW46 (->V8XX)
Jul 07 20:47:23-780679 cadet-p2p-8620 DEBUG Checking 0x52cc968 towards NCSKBW46 (->V8XX)
Jul 07 20:47:23-780858 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:23-781079 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:47:23-781318 util-scheduler-8620 DEBUG Adding task: 2513 / 0x4d6ff98
Jul 07 20:47:23-781497 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:23-781674 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:47:23-781872 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:23-782048 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:23-782223 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:23-782460 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:23-782643 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:23-782818 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:23-783019 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:23-783225 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:47:23-783408 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:47:23-783611 util-scheduler-8620 DEBUG Adding task: 2514 / 0x4d6ff98
Jul 07 20:47:23-783828 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:23-784023 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:23-784223 util-scheduler-8620 DEBUG Adding task: 2515 / 0x46620a0
Jul 07 20:47:23-784425 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:47:23-784673 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:23-784868 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:23-785113 util-scheduler-8620 DEBUG Checking readiness of task: 2515 / 0x46620a0
Jul 07 20:47:23-785332 util-scheduler-8620 DEBUG Checking readiness of task: 2511 / 0x46620a0
Jul 07 20:47:23-785523 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-785713 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-785943 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-786135 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-786324 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-786627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-786817 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-787010 util-scheduler-8620 DEBUG Running task: 2515 / 0x46620a0
Jul 07 20:47:23-787194 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:23-787370 util-8620 DEBUG process_notify is running
Jul 07 20:47:23-787541 util-8620 DEBUG client_notify is running
Jul 07 20:47:23-787720 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:23-787914 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:23-788104 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:23-788344 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:23-788549 util-scheduler-8620 DEBUG Running task: 2513 / 0x4d6ff98
Jul 07 20:47:23-788741 util-scheduler-8620 DEBUG Canceling task: 2514 / 0x4d6ff98
Jul 07 20:47:23-788956 util-scheduler-8620 DEBUG Adding task: 2516 / 0x4d6ff98
Jul 07 20:47:23-789172 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:23-789386 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:23-789583 util-scheduler-8620 DEBUG Adding task: 2517 / 0x46620a0
Jul 07 20:47:23-789823 util-scheduler-8620 DEBUG Checking readiness of task: 2517 / 0x46620a0
Jul 07 20:47:23-790015 util-scheduler-8620 DEBUG Checking readiness of task: 2511 / 0x46620a0
Jul 07 20:47:23-790205 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-790395 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-790602 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-790792 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-790983 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-791171 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-791360 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-791549 util-scheduler-8620 DEBUG Running task: 2517 / 0x46620a0
Jul 07 20:47:23-791733 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:23-791906 util-8620 DEBUG process_notify is running
Jul 07 20:47:23-792075 util-8620 DEBUG client_notify is running
Jul 07 20:47:23-792252 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:23-792440 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:23-792627 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:23-792865 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:23-898643 util-scheduler-8620 DEBUG Checking readiness of task: 2511 / 0x46620a0
Jul 07 20:47:23-898920 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-899115 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-899307 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-899498 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-899691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-899881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-900071 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-900264 util-scheduler-8620 DEBUG Running task: 2511 / 0x46620a0
Jul 07 20:47:23-900675 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:23-900914 util-scheduler-8620 DEBUG Adding task: 2518 / 0x4662248
Jul 07 20:47:23-901174 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-901396 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-901588 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-901778 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-901968 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-902157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-902346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-902534 util-scheduler-8620 DEBUG Running task: 2518 / 0x4662248
Jul 07 20:47:23-902725 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:23-902934 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:23-903154 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:23-903356 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:23-903558 util-scheduler-8620 DEBUG Adding task: 2519 / 0x46620a0
Jul 07 20:47:23-903743 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:23-903946 util-scheduler-8620 DEBUG Adding task: 2520 / 0x46620a0
Jul 07 20:47:23-904188 util-scheduler-8620 DEBUG Checking readiness of task: 2520 / 0x46620a0
Jul 07 20:47:23-904381 util-scheduler-8620 DEBUG Checking readiness of task: 2519 / 0x46620a0
Jul 07 20:47:23-904573 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:23-904762 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:23-904953 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:23-905143 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:23-905377 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:23-905566 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:23-905755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:23-905945 util-scheduler-8620 DEBUG Running task: 2519 / 0x46620a0
Jul 07 20:47:23-906130 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:23-906307 util-8620 DEBUG process_notify is running
Jul 07 20:47:23-906477 util-8620 DEBUG client_notify is running
Jul 07 20:47:23-906663 util-scheduler-8620 DEBUG Canceling task: 2516 / 0x4d6ff98
Jul 07 20:47:23-906885 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:47:23-907101 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:23-907336 cadet-p2p-8620 DEBUG Checking 0x52cc968 towards NCSKBW46 (->V8XX)
Jul 07 20:47:23-907568 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:23-907745 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:47:23-907914 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:47:23-908081 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:47:23-908251 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:47:23-908506 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 36)
Jul 07 20:47:23-908698 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:23-908877 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:23-909063 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:47:23-909265 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:23-909458 util-scheduler-8620 DEBUG Canceling task: 2512 / 0x52cba38
Jul 07 20:47:23-909671 util-scheduler-8620 DEBUG Adding task: 2521 / 0x52cba38
Jul 07 20:47:23-909907 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:47:23-910078 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:23-910257 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:47:23-910456 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:23-910630 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:23-910803 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:23-911002 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:23-911206 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:47:23-911389 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:47:23-911567 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:23-911755 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:47:23-911999 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:24-294651 util-scheduler-8620 DEBUG Checking readiness of task: 2520 / 0x46620a0
Jul 07 20:47:24-294975 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-295172 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-295365 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-295557 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-295748 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-295938 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-296128 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-296323 util-scheduler-8620 DEBUG Running task: 2520 / 0x46620a0
Jul 07 20:47:24-296736 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:24-296983 util-scheduler-8620 DEBUG Adding task: 2522 / 0x4662248
Jul 07 20:47:24-297281 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-297476 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-297668 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-297886 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-298081 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-298271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-298462 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-298652 util-scheduler-8620 DEBUG Running task: 2522 / 0x4662248
Jul 07 20:47:24-298844 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:47:24-299043 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:47:24-299276 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:47:24-299539 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection NCSKBW46 from V8XX
Jul 07 20:47:24-299758 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:47:24-300021 cadet-con-8620 DEBUG  get next hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-300233 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:24-300474 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-300683 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:24-300865 cadet-con-8620 DEBUG   ACK
Jul 07 20:47:24-301094 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:47:24-301303 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:24-301494 util-scheduler-8620 DEBUG Canceling task: 2501 / 0x52cba38
Jul 07 20:47:24-301720 util-scheduler-8620 DEBUG Adding task: 2523 / 0x52cba38
Jul 07 20:47:24-301904 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:47:24-302077 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:24-302261 util-scheduler-8620 DEBUG Canceling task: 2521 / 0x52cba38
Jul 07 20:47:24-302475 util-scheduler-8620 DEBUG Adding task: 2524 / 0x52cba38
Jul 07 20:47:24-302724 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:24-302933 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:47:24-303115 cadet-tun-8620 DEBUG   cstate triggered rekey
Jul 07 20:47:24-303312 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:24-303514 cadet-tun-8620 INFO   new kx ctx for V8XX
Jul 07 20:47:24-426687 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:47:24-427022 cadet-tun-8620 INFO PE: 00000000
Jul 07 20:47:24-427213 cadet-tun-8620 INFO KM: SY1Y2DBY
Jul 07 20:47:24-427399 cadet-tun-8620 INFO EK: 65Y43XST
Jul 07 20:47:24-427585 cadet-tun-8620 INFO DK: 9J1RHJ8Z
Jul 07 20:47:24-427805 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:24-428010 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:24-428215 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:24-428446 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:24-428628 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:24-428850 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:24-429137 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:24-429364 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:24-429602 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-429812 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:24-430130 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:24-430332 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:24-430558 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:24-430741 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:24-430917 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:24-431124 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:24-431340 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:24-431571 util-scheduler-8620 DEBUG Adding task: 2525 / 0x4d6ff98
Jul 07 20:47:24-431777 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:24-431983 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:24-432159 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:24-432333 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:24-432573 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:24-432767 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:24-432945 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:24-433143 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:24-433416 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:24-433611 util-scheduler-8620 DEBUG Adding task: 2526 / 0x52cbfb8
Jul 07 20:47:24-433803 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:24-434016 util-scheduler-8620 DEBUG Adding task: 2527 / 0x46620a0
Jul 07 20:47:24-434290 util-scheduler-8620 DEBUG Checking readiness of task: 2527 / 0x46620a0
Jul 07 20:47:24-434487 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-434678 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-434868 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-435057 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-435245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-435434 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-435624 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-435816 util-scheduler-8620 DEBUG Running task: 2527 / 0x46620a0
Jul 07 20:47:24-436228 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:24-436458 util-scheduler-8620 DEBUG Adding task: 2528 / 0x4662248
Jul 07 20:47:24-436666 util-scheduler-8620 DEBUG Running task: 2525 / 0x4d6ff98
Jul 07 20:47:24-436874 util-scheduler-8620 DEBUG Adding task: 2529 / 0x4d6ff98
Jul 07 20:47:24-437096 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:24-437318 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:24-437520 util-scheduler-8620 DEBUG Adding task: 2530 / 0x46620a0
Jul 07 20:47:24-437759 util-scheduler-8620 DEBUG Checking readiness of task: 2530 / 0x46620a0
Jul 07 20:47:24-437952 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-438142 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-438331 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-438520 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-438708 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-438896 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-439085 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-439275 util-scheduler-8620 DEBUG Running task: 2530 / 0x46620a0
Jul 07 20:47:24-439461 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:24-439640 util-8620 DEBUG process_notify is running
Jul 07 20:47:24-439812 util-8620 DEBUG client_notify is running
Jul 07 20:47:24-439991 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:24-440185 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:24-440377 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:24-440696 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:24-440907 util-scheduler-8620 DEBUG Running task: 2528 / 0x4662248
Jul 07 20:47:24-441099 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:24-441315 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:24-441549 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:24-441799 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:24-442038 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:24-442264 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-442470 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:24-443090 cadet-con-8620 DEBUG  PID 0 (expected 0+)
Jul 07 20:47:24-443282 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:24-443474 util-scheduler-8620 DEBUG Canceling task: 2523 / 0x52cba38
Jul 07 20:47:24-443700 util-scheduler-8620 DEBUG Adding task: 2531 / 0x52cba38
Jul 07 20:47:24-444046 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:24-444304 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:24-444516 util-scheduler-8620 DEBUG Adding task: 2532 / 0x4d5e5d8
Jul 07 20:47:24-444701 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:24-444880 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:24-448147 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:24-448981 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:24-449211 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:24-453015 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:24-453238 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:24-456293 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:24-463382 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:24-464175 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:24-468333 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:24-469988 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:24-472903 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:24-473093 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:24-473292 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:24-473468 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:24-473936 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:24-474124 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:47:24-474307 cadet-con-8620 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 20:47:24-474580 cadet-con-8620 INFO --> {               ACK} ( 64) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:24-474772 cadet-con-8620 DEBUG  ack 64
Jul 07 20:47:24-474950 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:47:24-475187 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-475395 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:24-475691 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:24-475890 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:24-476115 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:24-476298 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:24-476474 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:24-476675 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:24-476878 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:24-477055 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:24-477248 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:24-477486 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:24-477670 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:47:24-477844 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:24-478079 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:24-478271 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:24-478447 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:24-478645 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:24-478829 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:24-479040 util-scheduler-8620 DEBUG Adding task: 2533 / 0x46620a0
Jul 07 20:47:24-479337 util-scheduler-8620 DEBUG Checking readiness of task: 2533 / 0x46620a0
Jul 07 20:47:24-479576 util-scheduler-8620 DEBUG Checking readiness of task: 2532 / 0x4d5e5d8
Jul 07 20:47:24-479769 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-479960 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-480149 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-480338 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-480527 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-480716 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-480904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-481098 util-scheduler-8620 DEBUG Running task: 2532 / 0x4d5e5d8
Jul 07 20:47:24-481304 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:24-481481 util-8620 DEBUG process_notify is running
Jul 07 20:47:24-481652 util-8620 DEBUG client_notify is running
Jul 07 20:47:24-481898 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:24-482106 util-scheduler-8620 DEBUG Adding task: 2534 / 0x4d5e5d8
Jul 07 20:47:24-482309 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:24-482566 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:24-482764 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:24-483006 util-scheduler-8620 DEBUG Checking readiness of task: 2534 / 0x4d5e5d8
Jul 07 20:47:24-483199 util-scheduler-8620 DEBUG Checking readiness of task: 2533 / 0x46620a0
Jul 07 20:47:24-483392 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-483582 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-483772 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-483962 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-484152 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-484340 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-484529 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-484719 util-scheduler-8620 DEBUG Running task: 2534 / 0x4d5e5d8
Jul 07 20:47:24-484902 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:24-485077 util-8620 DEBUG process_notify is running
Jul 07 20:47:24-485266 util-8620 DEBUG client_notify is running
Jul 07 20:47:24-485477 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:24-485722 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:24-760456 util-scheduler-8620 DEBUG Checking readiness of task: 2533 / 0x46620a0
Jul 07 20:47:24-760709 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-760904 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-761097 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-761346 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-761552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-761742 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-761932 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-762124 util-scheduler-8620 DEBUG Running task: 2533 / 0x46620a0
Jul 07 20:47:24-762535 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:24-762776 util-scheduler-8620 DEBUG Adding task: 2535 / 0x4662248
Jul 07 20:47:24-763038 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:24-763253 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:24-763447 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:24-763637 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:24-763827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:24-764016 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:24-764205 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:24-764395 util-scheduler-8620 DEBUG Running task: 2535 / 0x4662248
Jul 07 20:47:24-764585 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:47:24-764785 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:47:24-765005 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:47:24-765281 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection NCSKBW46 from V8XX
Jul 07 20:47:24-765495 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:47:24-765735 cadet-con-8620 DEBUG  get next hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-765942 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:24-766181 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:24-766387 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:24-766568 cadet-con-8620 DEBUG   ACK
Jul 07 20:47:24-766798 cadet-con-8620 DEBUG Connection NCSKBW46 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:47:24-766981 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:24-767168 util-scheduler-8620 DEBUG Canceling task: 2531 / 0x52cba38
Jul 07 20:47:24-767389 util-scheduler-8620 DEBUG Adding task: 2536 / 0x52cba38
Jul 07 20:47:24-767572 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:47:24-767751 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:24-767954 util-scheduler-8620 DEBUG Adding task: 2537 / 0x46620a0
Jul 07 20:47:26-265133 util-scheduler-8620 DEBUG Checking readiness of task: 2537 / 0x46620a0
Jul 07 20:47:26-265545 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-265744 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-265937 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-266131 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-266322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-266513 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-266704 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-266900 util-scheduler-8620 DEBUG Running task: 2537 / 0x46620a0
Jul 07 20:47:26-267325 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:26-267579 util-scheduler-8620 DEBUG Adding task: 2538 / 0x4662248
Jul 07 20:47:26-267858 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-268053 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-268245 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-268436 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-268626 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-268816 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-269007 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-269223 util-scheduler-8620 DEBUG Running task: 2538 / 0x4662248
Jul 07 20:47:26-269417 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:26-269616 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:26-269849 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:26-270089 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:26-270297 util-scheduler-8620 DEBUG Adding task: 2539 / 0x46620a0
Jul 07 20:47:26-270484 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:26-270691 util-scheduler-8620 DEBUG Adding task: 2540 / 0x46620a0
Jul 07 20:47:26-270938 util-scheduler-8620 DEBUG Checking readiness of task: 2540 / 0x46620a0
Jul 07 20:47:26-271133 util-scheduler-8620 DEBUG Checking readiness of task: 2539 / 0x46620a0
Jul 07 20:47:26-271326 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-271517 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-271707 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-271899 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-272088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-272277 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-272467 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-272659 util-scheduler-8620 DEBUG Running task: 2539 / 0x46620a0
Jul 07 20:47:26-272846 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:26-273025 util-8620 DEBUG process_notify is running
Jul 07 20:47:26-273219 util-8620 DEBUG client_notify is running
Jul 07 20:47:26-273412 util-scheduler-8620 DEBUG Canceling task: 2529 / 0x4d6ff98
Jul 07 20:47:26-273639 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:26-273861 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:26-274102 cadet-p2p-8620 DEBUG Checking 0x581ddd0 towards NCSKBW46 (->V8XX)
Jul 07 20:47:26-274337 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:26-274515 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:26-274708 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:26-274980 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:26-275176 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:26-275359 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:26-275547 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:26-275723 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:26-275908 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:47:26-276082 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:26-276304 cadet-p2p-8620 DEBUG Checking 0x57f60e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:26-276542 cadet-p2p-8620 DEBUG Checking 0x57f60e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:26-276722 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:26-276930 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:26-277143 util-scheduler-8620 DEBUG Adding task: 2541 / 0x4d6ff98
Jul 07 20:47:26-277348 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:26-277526 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:26-277725 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:26-277901 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:26-278075 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:26-278316 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:26-278512 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:26-278689 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:26-278889 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:26-279095 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:26-279280 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:26-279483 util-scheduler-8620 DEBUG Adding task: 2542 / 0x4d6ff98
Jul 07 20:47:26-279704 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:26-279899 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:26-280105 util-scheduler-8620 DEBUG Adding task: 2543 / 0x46620a0
Jul 07 20:47:26-280335 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:26-281263 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:26-281467 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:26-281717 util-scheduler-8620 DEBUG Checking readiness of task: 2543 / 0x46620a0
Jul 07 20:47:26-281912 util-scheduler-8620 DEBUG Checking readiness of task: 2540 / 0x46620a0
Jul 07 20:47:26-282104 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-282295 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-282488 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-282679 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-282869 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-283059 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-283250 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-283442 util-scheduler-8620 DEBUG Running task: 2543 / 0x46620a0
Jul 07 20:47:26-283628 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:26-283805 util-8620 DEBUG process_notify is running
Jul 07 20:47:26-283976 util-8620 DEBUG client_notify is running
Jul 07 20:47:26-284155 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:26-284350 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:26-284540 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:26-284835 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:26-285044 util-scheduler-8620 DEBUG Running task: 2541 / 0x4d6ff98
Jul 07 20:47:26-285262 util-scheduler-8620 DEBUG Canceling task: 2542 / 0x4d6ff98
Jul 07 20:47:26-285479 util-scheduler-8620 DEBUG Adding task: 2544 / 0x4d6ff98
Jul 07 20:47:26-285695 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:26-285890 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:26-286089 util-scheduler-8620 DEBUG Adding task: 2545 / 0x46620a0
Jul 07 20:47:26-286331 util-scheduler-8620 DEBUG Checking readiness of task: 2545 / 0x46620a0
Jul 07 20:47:26-286525 util-scheduler-8620 DEBUG Checking readiness of task: 2540 / 0x46620a0
Jul 07 20:47:26-286717 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-286908 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-287099 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-287289 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-287479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-287668 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-287858 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-288050 util-scheduler-8620 DEBUG Running task: 2545 / 0x46620a0
Jul 07 20:47:26-288234 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:26-288411 util-8620 DEBUG process_notify is running
Jul 07 20:47:26-288580 util-8620 DEBUG client_notify is running
Jul 07 20:47:26-288758 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:26-288947 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:26-289137 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:26-289551 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:26-396933 util-scheduler-8620 DEBUG Checking readiness of task: 2540 / 0x46620a0
Jul 07 20:47:26-397218 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-397415 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-397607 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-397798 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-397989 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-398178 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-398369 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-398561 util-scheduler-8620 DEBUG Running task: 2540 / 0x46620a0
Jul 07 20:47:26-398964 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:26-399201 util-scheduler-8620 DEBUG Adding task: 2546 / 0x4662248
Jul 07 20:47:26-399454 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-399649 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-399840 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-400031 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-400222 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-400411 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-400600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-400789 util-scheduler-8620 DEBUG Running task: 2546 / 0x4662248
Jul 07 20:47:26-400977 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:26-401174 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:26-401420 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:26-401619 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:26-401820 util-scheduler-8620 DEBUG Adding task: 2547 / 0x46620a0
Jul 07 20:47:26-402003 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:26-402206 util-scheduler-8620 DEBUG Adding task: 2548 / 0x46620a0
Jul 07 20:47:26-402446 util-scheduler-8620 DEBUG Checking readiness of task: 2548 / 0x46620a0
Jul 07 20:47:26-402640 util-scheduler-8620 DEBUG Checking readiness of task: 2547 / 0x46620a0
Jul 07 20:47:26-402831 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:26-403020 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:26-403211 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:26-403401 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:26-403589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:26-403777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:26-403967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:26-404157 util-scheduler-8620 DEBUG Running task: 2547 / 0x46620a0
Jul 07 20:47:26-404342 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:26-404517 util-8620 DEBUG process_notify is running
Jul 07 20:47:26-404687 util-8620 DEBUG client_notify is running
Jul 07 20:47:26-404870 util-scheduler-8620 DEBUG Canceling task: 2544 / 0x4d6ff98
Jul 07 20:47:26-405092 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:26-405333 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:26-405567 cadet-p2p-8620 DEBUG Checking 0x57f60e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:26-405798 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:26-405975 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:26-406162 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:26-406440 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:26-406653 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:26-406833 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:26-407020 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:26-407207 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:26-407385 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:26-407572 util-scheduler-8620 DEBUG Canceling task: 2524 / 0x52cba38
Jul 07 20:47:26-407783 util-scheduler-8620 DEBUG Adding task: 2549 / 0x52cba38
Jul 07 20:47:26-408034 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:26-408204 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:26-408382 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:26-408581 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:26-408757 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:26-408931 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:26-409128 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:26-409358 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:26-409553 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:26-409731 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:26-409920 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:26-410172 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:29-122107 util-scheduler-8620 DEBUG Checking readiness of task: 2548 / 0x46620a0
Jul 07 20:47:29-122502 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-122699 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-122892 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-123085 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-123276 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-123467 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-123657 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-123854 util-scheduler-8620 DEBUG Running task: 2548 / 0x46620a0
Jul 07 20:47:29-124275 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:29-124535 util-scheduler-8620 DEBUG Adding task: 2550 / 0x4662248
Jul 07 20:47:29-124813 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-125006 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-125224 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-125417 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-125606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-125795 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-125983 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-126173 util-scheduler-8620 DEBUG Running task: 2550 / 0x4662248
Jul 07 20:47:29-126363 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:29-126563 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:29-126791 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:29-127054 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:29-127298 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:29-127527 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:29-127737 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:29-127935 cadet-con-8620 DEBUG  PID 1 (expected 1+)
Jul 07 20:47:29-128117 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:29-128307 util-scheduler-8620 DEBUG Canceling task: 2536 / 0x52cba38
Jul 07 20:47:29-128573 util-scheduler-8620 DEBUG Adding task: 2551 / 0x52cba38
Jul 07 20:47:29-128754 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:29-129015 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:29-129259 util-scheduler-8620 DEBUG Adding task: 2552 / 0x4d5e5d8
Jul 07 20:47:29-129444 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:29-129614 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:29-133720 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:29-134563 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:29-134770 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:29-137980 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:29-138172 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:29-141211 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:29-141855 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:29-142059 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:29-145999 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:29-146407 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:29-146663 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:29-146843 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:29-147018 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:29-147190 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:29-147413 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:29-147593 cadet-con-8620 DEBUG  ACK 65
Jul 07 20:47:29-147772 cadet-con-8620 DEBUG  last pid 1, last ack 64, qmax 11, q 0
Jul 07 20:47:29-148046 cadet-con-8620 INFO --> {               ACK} ( 65) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:29-148239 cadet-con-8620 DEBUG  ack 65
Jul 07 20:47:29-148420 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:29-148656 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:29-148862 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:29-149161 cadet-p2p-8620 INFO que {               ACK} ( 65) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:29-149390 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:29-149616 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:29-149800 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:29-149976 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:29-150180 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:47:29-150398 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:47:29-150625 util-scheduler-8620 DEBUG Adding task: 2553 / 0x4d6ff98
Jul 07 20:47:29-150809 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:29-151013 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:29-151189 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:29-151364 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:29-151602 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:29-151788 cadet-p2p-8620 DEBUG QQQ    payload , 65
Jul 07 20:47:29-151964 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:29-152164 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:29-152360 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:29-152573 util-scheduler-8620 DEBUG Adding task: 2554 / 0x46620a0
Jul 07 20:47:29-152845 util-scheduler-8620 DEBUG Checking readiness of task: 2554 / 0x46620a0
Jul 07 20:47:29-153042 util-scheduler-8620 DEBUG Checking readiness of task: 2552 / 0x4d5e5d8
Jul 07 20:47:29-153258 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-153449 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-153639 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-153830 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-154018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-154234 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-154423 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-154617 util-scheduler-8620 DEBUG Running task: 2552 / 0x4d5e5d8
Jul 07 20:47:29-154803 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:29-154983 util-8620 DEBUG process_notify is running
Jul 07 20:47:29-155156 util-8620 DEBUG client_notify is running
Jul 07 20:47:29-155402 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:29-155611 util-scheduler-8620 DEBUG Adding task: 2555 / 0x4d5e5d8
Jul 07 20:47:29-155814 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:29-156175 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:29-156376 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:29-156575 util-scheduler-8620 DEBUG Running task: 2553 / 0x4d6ff98
Jul 07 20:47:29-156783 util-scheduler-8620 DEBUG Adding task: 2556 / 0x4d6ff98
Jul 07 20:47:29-157004 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:29-157229 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:29-157429 util-scheduler-8620 DEBUG Adding task: 2557 / 0x46620a0
Jul 07 20:47:29-157672 util-scheduler-8620 DEBUG Checking readiness of task: 2557 / 0x46620a0
Jul 07 20:47:29-157867 util-scheduler-8620 DEBUG Checking readiness of task: 2555 / 0x4d5e5d8
Jul 07 20:47:29-158058 util-scheduler-8620 DEBUG Checking readiness of task: 2554 / 0x46620a0
Jul 07 20:47:29-158248 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-158438 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-158628 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-158818 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-159006 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-159196 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-159384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-159576 util-scheduler-8620 DEBUG Running task: 2555 / 0x4d5e5d8
Jul 07 20:47:29-159760 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:29-159935 util-8620 DEBUG process_notify is running
Jul 07 20:47:29-160104 util-8620 DEBUG client_notify is running
Jul 07 20:47:29-160314 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:29-160603 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:29-160817 util-scheduler-8620 DEBUG Running task: 2557 / 0x46620a0
Jul 07 20:47:29-161003 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:29-161178 util-8620 DEBUG process_notify is running
Jul 07 20:47:29-161371 util-8620 DEBUG client_notify is running
Jul 07 20:47:29-161551 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:29-161746 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:29-161935 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:29-162263 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:29-162513 util-scheduler-8620 DEBUG Checking readiness of task: 2554 / 0x46620a0
Jul 07 20:47:29-162708 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-162899 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-163090 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-163280 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-163486 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-163676 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-163866 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-164056 util-scheduler-8620 DEBUG Running task: 2554 / 0x46620a0
Jul 07 20:47:29-164461 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:29-164691 util-scheduler-8620 DEBUG Adding task: 2558 / 0x4662248
Jul 07 20:47:29-164940 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-165133 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-165352 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-165543 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-165734 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-165922 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-166111 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-166301 util-scheduler-8620 DEBUG Running task: 2558 / 0x4662248
Jul 07 20:47:29-166491 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:29-166688 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:29-166904 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:29-167101 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:29-167299 util-scheduler-8620 DEBUG Adding task: 2559 / 0x46620a0
Jul 07 20:47:29-167481 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:29-167680 util-scheduler-8620 DEBUG Adding task: 2560 / 0x46620a0
Jul 07 20:47:29-167918 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:29-168111 util-scheduler-8620 DEBUG Checking readiness of task: 2559 / 0x46620a0
Jul 07 20:47:29-168302 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-168493 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-168683 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-168872 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-169061 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-169271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-169461 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-169653 util-scheduler-8620 DEBUG Running task: 2559 / 0x46620a0
Jul 07 20:47:29-169837 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:29-170011 util-8620 DEBUG process_notify is running
Jul 07 20:47:29-170180 util-8620 DEBUG client_notify is running
Jul 07 20:47:29-170365 util-scheduler-8620 DEBUG Canceling task: 2556 / 0x4d6ff98
Jul 07 20:47:29-170586 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:47:29-170802 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:29-171038 cadet-p2p-8620 DEBUG Checking 0x584a148 towards NCSKBW46 (->V8XX)
Jul 07 20:47:29-171271 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:29-171448 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:29-171636 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:29-171904 cadet-p2p-8620 INFO snd {               ACK} ( 65) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:29-172098 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:29-172281 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:29-172470 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:29-172643 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:29-172826 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:29-173016 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:29-173220 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:29-173421 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:29-173596 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:29-173770 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:29-173979 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:29-174183 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:29-174366 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:29-174543 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:29-174731 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:29-175506 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:29-434037 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:29-434414 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-434611 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-434804 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-434996 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-435188 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-435379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-435569 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-435762 util-scheduler-8620 DEBUG Running task: 2526 / 0x52cbfb8
Jul 07 20:47:29-436003 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:29-436252 cadet-tun-8620 DEBUG  kx started 5 s ago
Jul 07 20:47:29-436457 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:29-436658 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:29-436861 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:29-437099 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:29-437305 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:29-437528 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:29-437821 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:29-438019 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:29-438257 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:29-438466 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:29-438785 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:29-438985 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:29-439209 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:29-439393 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:29-439569 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:29-439776 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:29-439993 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:29-440217 util-scheduler-8620 DEBUG Adding task: 2561 / 0x4d6ff98
Jul 07 20:47:29-440396 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:29-440601 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:29-440778 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:29-440956 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:29-441217 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:29-441418 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:29-442790 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:29-443109 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:29-443376 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:29-443596 util-scheduler-8620 DEBUG Adding task: 2562 / 0x52cbfb8
Jul 07 20:47:29-443908 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:29-444108 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-444299 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-444490 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-444680 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-444869 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-445058 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-445280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-445474 util-scheduler-8620 DEBUG Running task: 2561 / 0x4d6ff98
Jul 07 20:47:29-445685 util-scheduler-8620 DEBUG Adding task: 2563 / 0x4d6ff98
Jul 07 20:47:29-445911 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:29-446114 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:29-446323 util-scheduler-8620 DEBUG Adding task: 2564 / 0x46620a0
Jul 07 20:47:29-446569 util-scheduler-8620 DEBUG Checking readiness of task: 2564 / 0x46620a0
Jul 07 20:47:29-446763 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:29-446954 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:29-447143 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:29-447333 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:29-447523 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:29-447712 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:29-447900 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:29-448089 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:29-448280 util-scheduler-8620 DEBUG Running task: 2564 / 0x46620a0
Jul 07 20:47:29-448465 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:29-448644 util-8620 DEBUG process_notify is running
Jul 07 20:47:29-448818 util-8620 DEBUG client_notify is running
Jul 07 20:47:29-448997 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:29-449219 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:29-449472 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:29-449795 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:31-404528 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:31-404914 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:31-405111 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:31-405329 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:31-405523 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:31-405713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:31-405904 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:31-406094 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:31-406287 util-scheduler-8620 DEBUG Running task: 2166 / 0x4d68be8
Jul 07 20:47:31-406560 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:47:31-406739 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:47:31-406992 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:47:31-407185 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:47:31-407418 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:47:31-407627 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:47:31-407935 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:47:31-408166 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:31-408393 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:47:31-408577 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:31-408754 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:31-408961 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:47:31-409177 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:47:31-409430 util-scheduler-8620 DEBUG Adding task: 2565 / 0x4d683b0
Jul 07 20:47:31-409612 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:31-409817 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:47:31-409993 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:31-410169 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:47:31-410421 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:47:31-410604 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:31-410780 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:47:31-410980 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:47:31-411237 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:31-411430 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:31-411624 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:31-411813 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:31-412003 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:31-412192 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:31-412381 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:31-412569 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:31-412758 util-scheduler-8620 DEBUG Running task: 2565 / 0x4d683b0
Jul 07 20:47:31-412968 util-scheduler-8620 DEBUG Adding task: 2566 / 0x4d683b0
Jul 07 20:47:31-413275 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:47:31-413488 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:31-413698 util-scheduler-8620 DEBUG Adding task: 2567 / 0x46620a0
Jul 07 20:47:31-413942 util-scheduler-8620 DEBUG Checking readiness of task: 2567 / 0x46620a0
Jul 07 20:47:31-414136 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:31-414327 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:31-414518 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:31-414707 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:31-414897 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:31-415085 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:31-415275 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:31-415463 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:31-415655 util-scheduler-8620 DEBUG Running task: 2567 / 0x46620a0
Jul 07 20:47:31-415839 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:31-416018 util-8620 DEBUG process_notify is running
Jul 07 20:47:31-416190 util-8620 DEBUG client_notify is running
Jul 07 20:47:31-416369 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:31-416567 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:31-416758 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:31-417062 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:33-721979 util-scheduler-8620 DEBUG Checking readiness of task: 2560 / 0x46620a0
Jul 07 20:47:33-722362 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-722591 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-722788 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-722981 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-723174 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-723379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-723571 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-723767 util-scheduler-8620 DEBUG Running task: 2560 / 0x46620a0
Jul 07 20:47:33-724189 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:33-724447 util-scheduler-8620 DEBUG Adding task: 2568 / 0x4662248
Jul 07 20:47:33-724728 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-724924 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-725114 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-725333 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-725523 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-725713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-725902 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-726092 util-scheduler-8620 DEBUG Running task: 2568 / 0x4662248
Jul 07 20:47:33-726282 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:33-726483 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:33-726714 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:33-726984 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:33-727227 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:33-727456 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:33-727665 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:33-727861 cadet-con-8620 DEBUG  PID 2 (expected 2+)
Jul 07 20:47:33-728042 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:33-728231 util-scheduler-8620 DEBUG Canceling task: 2551 / 0x52cba38
Jul 07 20:47:33-728455 util-scheduler-8620 DEBUG Adding task: 2569 / 0x52cba38
Jul 07 20:47:33-728634 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:33-728891 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:33-729108 util-scheduler-8620 DEBUG Adding task: 2570 / 0x4d5e5d8
Jul 07 20:47:33-729329 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:33-729499 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:33-733066 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:33-734442 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:33-734657 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:33-737380 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:33-737578 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:33-741113 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:33-741808 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:33-742011 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:33-745156 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:33-745434 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:33-745904 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:33-746085 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:33-746259 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:33-746429 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:33-746650 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:33-746827 cadet-con-8620 DEBUG  ACK 66
Jul 07 20:47:33-747010 cadet-con-8620 DEBUG  last pid 2, last ack 65, qmax 11, q 0
Jul 07 20:47:33-747307 cadet-con-8620 INFO --> {               ACK} ( 66) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:33-747500 cadet-con-8620 DEBUG  ack 66
Jul 07 20:47:33-747681 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:47:33-747916 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:33-748124 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:33-748421 cadet-p2p-8620 INFO que {               ACK} ( 66) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:33-748621 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:33-748845 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:33-749028 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:33-749224 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:33-749429 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:33-749632 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:33-749808 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:33-749983 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:33-750222 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:33-750406 cadet-p2p-8620 DEBUG QQQ    payload , 66
Jul 07 20:47:33-750582 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:33-750816 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:33-751009 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:33-751185 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:33-751382 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:33-751565 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:33-751780 util-scheduler-8620 DEBUG Adding task: 2571 / 0x46620a0
Jul 07 20:47:33-752052 util-scheduler-8620 DEBUG Checking readiness of task: 2571 / 0x46620a0
Jul 07 20:47:33-752249 util-scheduler-8620 DEBUG Checking readiness of task: 2570 / 0x4d5e5d8
Jul 07 20:47:33-752443 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-752632 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-752822 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-753012 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-753220 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-753412 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-753600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-753794 util-scheduler-8620 DEBUG Running task: 2570 / 0x4d5e5d8
Jul 07 20:47:33-753980 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:33-754159 util-8620 DEBUG process_notify is running
Jul 07 20:47:33-754330 util-8620 DEBUG client_notify is running
Jul 07 20:47:33-754574 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:33-754782 util-scheduler-8620 DEBUG Adding task: 2572 / 0x4d5e5d8
Jul 07 20:47:33-754985 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:33-755246 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:33-755444 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:33-755685 util-scheduler-8620 DEBUG Checking readiness of task: 2572 / 0x4d5e5d8
Jul 07 20:47:33-755879 util-scheduler-8620 DEBUG Checking readiness of task: 2571 / 0x46620a0
Jul 07 20:47:33-756070 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-756259 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-756449 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-756639 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-756827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-757036 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-757244 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-757436 util-scheduler-8620 DEBUG Running task: 2572 / 0x4d5e5d8
Jul 07 20:47:33-757618 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:33-757793 util-8620 DEBUG process_notify is running
Jul 07 20:47:33-757961 util-8620 DEBUG client_notify is running
Jul 07 20:47:33-758170 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:33-758414 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:33-970355 util-scheduler-8620 DEBUG Checking readiness of task: 2571 / 0x46620a0
Jul 07 20:47:33-970732 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-970956 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-971167 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-971368 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-971567 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-971781 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-971984 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-972198 util-scheduler-8620 DEBUG Running task: 2571 / 0x46620a0
Jul 07 20:47:33-972639 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:33-972897 util-scheduler-8620 DEBUG Adding task: 2573 / 0x4662248
Jul 07 20:47:33-973178 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-973407 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-973599 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-973790 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-973981 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-974170 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-974362 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-974552 util-scheduler-8620 DEBUG Running task: 2573 / 0x4662248
Jul 07 20:47:33-974744 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:33-974944 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:33-975175 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:33-975382 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:33-975588 util-scheduler-8620 DEBUG Adding task: 2574 / 0x46620a0
Jul 07 20:47:33-975776 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:33-975981 util-scheduler-8620 DEBUG Adding task: 2575 / 0x46620a0
Jul 07 20:47:33-976228 util-scheduler-8620 DEBUG Checking readiness of task: 2575 / 0x46620a0
Jul 07 20:47:33-976422 util-scheduler-8620 DEBUG Checking readiness of task: 2574 / 0x46620a0
Jul 07 20:47:33-976615 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-976805 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-976999 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-977210 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-977402 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-977592 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-977782 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-977974 util-scheduler-8620 DEBUG Running task: 2574 / 0x46620a0
Jul 07 20:47:33-978161 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:33-978367 util-8620 DEBUG process_notify is running
Jul 07 20:47:33-978541 util-8620 DEBUG client_notify is running
Jul 07 20:47:33-978733 util-scheduler-8620 DEBUG Canceling task: 2563 / 0x4d6ff98
Jul 07 20:47:33-978961 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:33-979196 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:33-979437 cadet-p2p-8620 DEBUG Checking 0x5876430 towards NCSKBW46 (->V8XX)
Jul 07 20:47:33-979673 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:33-979852 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:33-980044 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:33-980315 cadet-p2p-8620 INFO snd {               ACK} ( 66) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:33-980511 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:33-980693 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:33-980882 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:33-981057 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:33-981263 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:47:33-981440 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:33-981664 cadet-p2p-8620 DEBUG Checking 0x584d1c8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:33-981903 cadet-p2p-8620 DEBUG Checking 0x584d1c8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:33-982082 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:33-982289 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:33-982506 util-scheduler-8620 DEBUG Adding task: 2576 / 0x4d6ff98
Jul 07 20:47:33-982686 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:33-982865 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:33-983063 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:33-983240 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:33-983415 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:33-983655 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:33-983851 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:33-984029 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:33-984228 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:33-984434 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:33-984618 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:33-984823 util-scheduler-8620 DEBUG Adding task: 2577 / 0x4d6ff98
Jul 07 20:47:33-985044 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:33-985260 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:33-985465 util-scheduler-8620 DEBUG Adding task: 2578 / 0x46620a0
Jul 07 20:47:33-985667 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:33-986414 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:33-986618 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:33-986868 util-scheduler-8620 DEBUG Checking readiness of task: 2578 / 0x46620a0
Jul 07 20:47:33-987067 util-scheduler-8620 DEBUG Checking readiness of task: 2575 / 0x46620a0
Jul 07 20:47:33-987259 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-987450 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-987640 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-987831 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-988021 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-988212 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-988403 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-988594 util-scheduler-8620 DEBUG Running task: 2578 / 0x46620a0
Jul 07 20:47:33-988780 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:33-988977 util-8620 DEBUG process_notify is running
Jul 07 20:47:33-989149 util-8620 DEBUG client_notify is running
Jul 07 20:47:33-989352 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:33-989547 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:33-989738 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:33-989972 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:33-990179 util-scheduler-8620 DEBUG Running task: 2576 / 0x4d6ff98
Jul 07 20:47:33-990373 util-scheduler-8620 DEBUG Canceling task: 2577 / 0x4d6ff98
Jul 07 20:47:33-990588 util-scheduler-8620 DEBUG Adding task: 2579 / 0x4d6ff98
Jul 07 20:47:33-990807 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:33-991001 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:33-991199 util-scheduler-8620 DEBUG Adding task: 2580 / 0x46620a0
Jul 07 20:47:33-991442 util-scheduler-8620 DEBUG Checking readiness of task: 2580 / 0x46620a0
Jul 07 20:47:33-991635 util-scheduler-8620 DEBUG Checking readiness of task: 2575 / 0x46620a0
Jul 07 20:47:33-991826 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:33-992016 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:33-992206 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:33-992396 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:33-992586 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:33-992776 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:33-992966 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:33-993157 util-scheduler-8620 DEBUG Running task: 2580 / 0x46620a0
Jul 07 20:47:33-993362 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:33-993539 util-8620 DEBUG process_notify is running
Jul 07 20:47:33-993709 util-8620 DEBUG client_notify is running
Jul 07 20:47:33-993886 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:33-994075 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:33-994265 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:33-994595 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:34-103505 util-scheduler-8620 DEBUG Checking readiness of task: 2575 / 0x46620a0
Jul 07 20:47:34-103803 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-104000 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-104193 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-104383 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-104574 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-104764 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-104956 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-105148 util-scheduler-8620 DEBUG Running task: 2575 / 0x46620a0
Jul 07 20:47:34-105580 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:34-105816 util-scheduler-8620 DEBUG Adding task: 2581 / 0x4662248
Jul 07 20:47:34-106073 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-106266 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-106457 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-106647 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-106858 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-107047 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-107237 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-107426 util-scheduler-8620 DEBUG Running task: 2581 / 0x4662248
Jul 07 20:47:34-107615 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:34-107811 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:34-108031 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:34-108229 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:34-108430 util-scheduler-8620 DEBUG Adding task: 2582 / 0x46620a0
Jul 07 20:47:34-108614 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:34-108817 util-scheduler-8620 DEBUG Adding task: 2583 / 0x46620a0
Jul 07 20:47:34-109057 util-scheduler-8620 DEBUG Checking readiness of task: 2583 / 0x46620a0
Jul 07 20:47:34-109270 util-scheduler-8620 DEBUG Checking readiness of task: 2582 / 0x46620a0
Jul 07 20:47:34-109462 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-109670 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-109870 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-110061 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-110251 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-110442 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-110631 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-110823 util-scheduler-8620 DEBUG Running task: 2582 / 0x46620a0
Jul 07 20:47:34-111006 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:34-111183 util-8620 DEBUG process_notify is running
Jul 07 20:47:34-111353 util-8620 DEBUG client_notify is running
Jul 07 20:47:34-111538 util-scheduler-8620 DEBUG Canceling task: 2579 / 0x4d6ff98
Jul 07 20:47:34-111759 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:34-111976 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:34-112211 cadet-p2p-8620 DEBUG Checking 0x584d1c8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:34-112442 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:34-112619 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:34-112806 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:34-113087 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:34-113303 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:34-113481 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:34-113668 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:34-113856 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:34-114034 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:34-114219 util-scheduler-8620 DEBUG Canceling task: 2549 / 0x52cba38
Jul 07 20:47:34-114430 util-scheduler-8620 DEBUG Adding task: 2584 / 0x52cba38
Jul 07 20:47:34-114680 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:34-114853 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:34-115032 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:34-115230 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:34-115404 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:34-115577 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:34-115775 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:34-115978 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:34-116161 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:34-116338 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:34-116526 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:34-116789 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:34-444010 util-scheduler-8620 DEBUG Checking readiness of task: 2583 / 0x46620a0
Jul 07 20:47:34-444272 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-447608 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-447814 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-448007 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-448198 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-448388 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-448578 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-448769 util-scheduler-8620 DEBUG Running task: 2562 / 0x52cbfb8
Jul 07 20:47:34-448994 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:34-449261 cadet-tun-8620 DEBUG  kx started 10 s ago
Jul 07 20:47:34-449466 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:34-449668 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:34-449870 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:34-450102 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:34-450282 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:34-450503 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:34-450789 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:34-450985 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:34-451221 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:34-451430 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:34-451742 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:34-451943 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:34-452168 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:34-452352 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:34-452527 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:34-452736 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:34-452952 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:34-453174 util-scheduler-8620 DEBUG Adding task: 2585 / 0x4d6ff98
Jul 07 20:47:34-453377 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:34-453580 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:34-453756 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:34-453929 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:34-454167 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:34-454363 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:34-454539 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:34-454737 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:34-454981 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:34-455179 util-scheduler-8620 DEBUG Adding task: 2586 / 0x52cbfb8
Jul 07 20:47:34-455430 util-scheduler-8620 DEBUG Checking readiness of task: 2583 / 0x46620a0
Jul 07 20:47:34-455622 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-455812 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-456002 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-456192 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-456380 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-456570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-456759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-456971 util-scheduler-8620 DEBUG Running task: 2585 / 0x4d6ff98
Jul 07 20:47:34-457180 util-scheduler-8620 DEBUG Adding task: 2587 / 0x4d6ff98
Jul 07 20:47:34-457424 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:34-457624 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:34-457830 util-scheduler-8620 DEBUG Adding task: 2588 / 0x46620a0
Jul 07 20:47:34-458072 util-scheduler-8620 DEBUG Checking readiness of task: 2588 / 0x46620a0
Jul 07 20:47:34-458266 util-scheduler-8620 DEBUG Checking readiness of task: 2583 / 0x46620a0
Jul 07 20:47:34-458456 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-458646 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-458835 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-459026 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-459214 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-459402 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-459590 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-459781 util-scheduler-8620 DEBUG Running task: 2588 / 0x46620a0
Jul 07 20:47:34-459966 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:34-460143 util-8620 DEBUG process_notify is running
Jul 07 20:47:34-460315 util-8620 DEBUG client_notify is running
Jul 07 20:47:34-460494 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:34-460687 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:34-460877 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:34-461138 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:34-461410 util-scheduler-8620 DEBUG Checking readiness of task: 2583 / 0x46620a0
Jul 07 20:47:34-461603 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-461793 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-461982 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-462172 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-462360 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-462548 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-462737 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-462926 util-scheduler-8620 DEBUG Running task: 2583 / 0x46620a0
Jul 07 20:47:34-463331 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:34-463558 util-scheduler-8620 DEBUG Adding task: 2589 / 0x4662248
Jul 07 20:47:34-463804 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-463996 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-464187 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-464377 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-464566 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-464754 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-464946 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-465134 util-scheduler-8620 DEBUG Running task: 2589 / 0x4662248
Jul 07 20:47:34-465348 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:34-465543 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:34-465758 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:34-465970 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:34-466168 util-scheduler-8620 DEBUG Adding task: 2590 / 0x46620a0
Jul 07 20:47:34-466352 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:34-466555 util-scheduler-8620 DEBUG Adding task: 2591 / 0x46620a0
Jul 07 20:47:34-466795 util-scheduler-8620 DEBUG Checking readiness of task: 2591 / 0x46620a0
Jul 07 20:47:34-466988 util-scheduler-8620 DEBUG Checking readiness of task: 2590 / 0x46620a0
Jul 07 20:47:34-467180 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:34-467369 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:34-467559 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:34-467748 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:34-467937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:34-468125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:34-468314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:34-468503 util-scheduler-8620 DEBUG Running task: 2590 / 0x46620a0
Jul 07 20:47:34-468687 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:34-468863 util-8620 DEBUG process_notify is running
Jul 07 20:47:34-469032 util-8620 DEBUG client_notify is running
Jul 07 20:47:34-469236 util-scheduler-8620 DEBUG Canceling task: 2587 / 0x4d6ff98
Jul 07 20:47:34-469461 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:34-469676 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:34-469906 cadet-p2p-8620 DEBUG Checking 0x587b388 towards NCSKBW46 (->V8XX)
Jul 07 20:47:34-470138 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:34-470315 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:34-470502 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:34-470782 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:34-470975 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:34-471153 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:34-471340 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:34-471528 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:34-471704 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:34-471887 util-scheduler-8620 DEBUG Canceling task: 2584 / 0x52cba38
Jul 07 20:47:34-472097 util-scheduler-8620 DEBUG Adding task: 2592 / 0x52cba38
Jul 07 20:47:34-472341 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:34-472510 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:34-472689 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:34-472887 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:34-473062 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:34-473258 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:34-473456 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:34-473660 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:34-473843 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:34-474019 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:34-474207 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:34-474450 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:37-719675 util-scheduler-8620 DEBUG Checking readiness of task: 2591 / 0x46620a0
Jul 07 20:47:37-720064 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:37-720262 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:37-720455 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:37-720648 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:37-720867 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:37-721059 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:37-721284 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:37-721481 util-scheduler-8620 DEBUG Running task: 2591 / 0x46620a0
Jul 07 20:47:37-721903 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:37-722160 util-scheduler-8620 DEBUG Adding task: 2593 / 0x4662248
Jul 07 20:47:37-722436 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:37-722629 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:37-722820 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:37-723011 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:37-723200 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:37-723389 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:37-723578 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:37-723767 util-scheduler-8620 DEBUG Running task: 2593 / 0x4662248
Jul 07 20:47:37-723957 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:37-724157 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:37-724386 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:47:37-724595 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:37-724803 util-scheduler-8620 DEBUG Adding task: 2594 / 0x46620a0
Jul 07 20:47:37-724991 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:37-725223 util-scheduler-8620 DEBUG Adding task: 2595 / 0x46620a0
Jul 07 20:47:37-725471 util-scheduler-8620 DEBUG Checking readiness of task: 2595 / 0x46620a0
Jul 07 20:47:37-725662 util-scheduler-8620 DEBUG Checking readiness of task: 2594 / 0x46620a0
Jul 07 20:47:37-725856 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:37-726046 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:37-726235 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:37-726426 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:37-726615 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:37-726804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:37-726992 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:37-727184 util-scheduler-8620 DEBUG Running task: 2594 / 0x46620a0
Jul 07 20:47:37-727368 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:37-727546 util-8620 DEBUG process_notify is running
Jul 07 20:47:37-727732 util-8620 DEBUG client_notify is running
Jul 07 20:47:37-727921 util-scheduler-8620 DEBUG Canceling task: 2566 / 0x4d683b0
Jul 07 20:47:37-728145 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:47:37-728365 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:47:37-728605 cadet-p2p-8620 DEBUG Checking 0x584e4b8 towards KT5Q8VM8 (->P00P)
Jul 07 20:47:37-728839 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:47:37-729016 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:47:37-729185 cadet-p2p-8620 DEBUG   path create
Jul 07 20:47:37-729673 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:47:37-729862 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:47:37-730181 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:47:37-730377 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:37-730560 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:37-730749 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:47:37-730930 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:47:37-731191 util-scheduler-8620 DEBUG Adding task: 2596 / 0x4d68be8
Jul 07 20:47:37-731433 cadet-con-8620 DEBUG next keepalive in 64 s
Jul 07 20:47:37-731604 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:37-731788 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:47:37-731990 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:47:37-732165 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:37-732342 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:37-732541 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:47:37-732747 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:47:37-732931 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:47:37-733113 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:37-733352 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:47:37-733611 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:38-198254 util-scheduler-8620 DEBUG Checking readiness of task: 2595 / 0x46620a0
Jul 07 20:47:38-198603 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-198802 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-198995 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-199187 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-199378 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-199568 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-199759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-199954 util-scheduler-8620 DEBUG Running task: 2595 / 0x46620a0
Jul 07 20:47:38-200381 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:38-200637 util-scheduler-8620 DEBUG Adding task: 2597 / 0x4662248
Jul 07 20:47:38-200910 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-201104 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-201326 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-201635 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-201829 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-202019 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-202208 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-202398 util-scheduler-8620 DEBUG Running task: 2597 / 0x4662248
Jul 07 20:47:38-202590 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:38-202789 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:38-203019 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:38-203283 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:38-203530 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:38-203759 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:38-203968 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:38-204165 cadet-con-8620 DEBUG  PID 3 (expected 3+)
Jul 07 20:47:38-204346 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:38-204534 util-scheduler-8620 DEBUG Canceling task: 2569 / 0x52cba38
Jul 07 20:47:38-204758 util-scheduler-8620 DEBUG Adding task: 2598 / 0x52cba38
Jul 07 20:47:38-204938 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:38-205225 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:38-205447 util-scheduler-8620 DEBUG Adding task: 2599 / 0x4d5e5d8
Jul 07 20:47:38-205634 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:38-206166 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:38-209777 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:38-210636 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:38-210847 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:38-214190 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:38-214384 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:38-217468 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:38-218541 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:38-218734 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:38-221823 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:38-222072 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:38-222313 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:38-222489 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:38-222662 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:38-222832 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:38-223052 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:38-223230 cadet-con-8620 DEBUG  ACK 67
Jul 07 20:47:38-223422 cadet-con-8620 DEBUG  last pid 3, last ack 66, qmax 11, q 0
Jul 07 20:47:38-223691 cadet-con-8620 INFO --> {               ACK} ( 67) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:38-223882 cadet-con-8620 DEBUG  ack 67
Jul 07 20:47:38-224061 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:38-224295 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:38-224500 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:38-224795 cadet-p2p-8620 INFO que {               ACK} ( 67) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:38-224993 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:38-225239 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:38-225422 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:38-225597 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:38-225802 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:47:38-226016 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:47:38-226238 util-scheduler-8620 DEBUG Adding task: 2600 / 0x4d6ff98
Jul 07 20:47:38-226418 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:38-226626 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:38-226801 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:38-226976 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:38-227214 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:38-227397 cadet-p2p-8620 DEBUG QQQ    payload , 67
Jul 07 20:47:38-227573 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:38-227771 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:38-227952 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:38-228164 util-scheduler-8620 DEBUG Adding task: 2601 / 0x46620a0
Jul 07 20:47:38-228432 util-scheduler-8620 DEBUG Checking readiness of task: 2601 / 0x46620a0
Jul 07 20:47:38-228628 util-scheduler-8620 DEBUG Checking readiness of task: 2599 / 0x4d5e5d8
Jul 07 20:47:38-228820 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-229010 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-229220 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-229411 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-229601 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-229790 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-229978 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-230170 util-scheduler-8620 DEBUG Running task: 2599 / 0x4d5e5d8
Jul 07 20:47:38-230356 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:38-230557 util-8620 DEBUG process_notify is running
Jul 07 20:47:38-230731 util-8620 DEBUG client_notify is running
Jul 07 20:47:38-230972 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:38-231181 util-scheduler-8620 DEBUG Adding task: 2602 / 0x4d5e5d8
Jul 07 20:47:38-231384 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:38-231645 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:38-231843 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:38-232039 util-scheduler-8620 DEBUG Running task: 2600 / 0x4d6ff98
Jul 07 20:47:38-232246 util-scheduler-8620 DEBUG Adding task: 2603 / 0x4d6ff98
Jul 07 20:47:38-232468 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:38-232663 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:38-232860 util-scheduler-8620 DEBUG Adding task: 2604 / 0x46620a0
Jul 07 20:47:38-233102 util-scheduler-8620 DEBUG Checking readiness of task: 2604 / 0x46620a0
Jul 07 20:47:38-233317 util-scheduler-8620 DEBUG Checking readiness of task: 2602 / 0x4d5e5d8
Jul 07 20:47:38-233509 util-scheduler-8620 DEBUG Checking readiness of task: 2601 / 0x46620a0
Jul 07 20:47:38-233699 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-233889 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-234079 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-234269 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-234458 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-234646 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-234835 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-235025 util-scheduler-8620 DEBUG Running task: 2602 / 0x4d5e5d8
Jul 07 20:47:38-235208 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:38-235383 util-8620 DEBUG process_notify is running
Jul 07 20:47:38-235552 util-8620 DEBUG client_notify is running
Jul 07 20:47:38-235807 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:38-236046 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:38-236256 util-scheduler-8620 DEBUG Running task: 2604 / 0x46620a0
Jul 07 20:47:38-236439 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:38-236618 util-8620 DEBUG process_notify is running
Jul 07 20:47:38-236787 util-8620 DEBUG client_notify is running
Jul 07 20:47:38-236965 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:38-237160 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:38-237369 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:38-237610 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:38-319752 util-scheduler-8620 DEBUG Checking readiness of task: 2601 / 0x46620a0
Jul 07 20:47:38-320109 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-320306 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-320499 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-320691 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-320883 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-321074 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-321297 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-321493 util-scheduler-8620 DEBUG Running task: 2601 / 0x46620a0
Jul 07 20:47:38-321918 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:38-322197 util-scheduler-8620 DEBUG Adding task: 2605 / 0x4662248
Jul 07 20:47:38-322471 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-322663 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-322854 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-323044 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-323234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-323423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-323613 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-323802 util-scheduler-8620 DEBUG Running task: 2605 / 0x4662248
Jul 07 20:47:38-323993 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:38-324191 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:38-324418 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:38-324624 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:38-324829 util-scheduler-8620 DEBUG Adding task: 2606 / 0x46620a0
Jul 07 20:47:38-325015 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:38-325243 util-scheduler-8620 DEBUG Adding task: 2607 / 0x46620a0
Jul 07 20:47:38-325488 util-scheduler-8620 DEBUG Checking readiness of task: 2607 / 0x46620a0
Jul 07 20:47:38-325681 util-scheduler-8620 DEBUG Checking readiness of task: 2606 / 0x46620a0
Jul 07 20:47:38-325873 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:38-326065 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:38-326255 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:38-326445 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:38-326634 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:38-326837 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:38-327026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:38-327217 util-scheduler-8620 DEBUG Running task: 2606 / 0x46620a0
Jul 07 20:47:38-327402 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:38-327580 util-8620 DEBUG process_notify is running
Jul 07 20:47:38-327752 util-8620 DEBUG client_notify is running
Jul 07 20:47:38-327940 util-scheduler-8620 DEBUG Canceling task: 2603 / 0x4d6ff98
Jul 07 20:47:38-328162 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:47:38-328381 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:38-328619 cadet-p2p-8620 DEBUG Checking 0x5893820 towards NCSKBW46 (->V8XX)
Jul 07 20:47:38-328852 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:38-329029 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:38-329246 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:38-329517 cadet-p2p-8620 INFO snd {               ACK} ( 67) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:38-329711 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:38-329892 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:38-330080 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:38-330255 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:38-330438 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:38-330612 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:38-330794 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:38-330993 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:38-331167 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:38-331342 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:38-331540 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:38-331744 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:38-331943 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:38-332123 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:38-332314 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:38-332562 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:39-456453 util-scheduler-8620 DEBUG Checking readiness of task: 2607 / 0x46620a0
Jul 07 20:47:39-456804 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:39-460097 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:39-460535 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:39-460735 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:39-460927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:39-461118 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:39-461333 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:39-461528 util-scheduler-8620 DEBUG Running task: 2586 / 0x52cbfb8
Jul 07 20:47:39-461766 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:39-462012 cadet-tun-8620 DEBUG  kx started 15 s ago
Jul 07 20:47:39-462219 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:39-462419 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:39-462622 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:39-462857 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:39-463038 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:39-463260 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:39-463552 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:39-463749 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:39-463987 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:39-464194 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:39-464510 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:39-464710 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:39-464937 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:39-465119 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:39-465317 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:39-465524 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:39-465739 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:39-465964 util-scheduler-8620 DEBUG Adding task: 2608 / 0x4d6ff98
Jul 07 20:47:39-466144 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:39-466347 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:39-466523 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:39-466698 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:39-466938 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:39-467173 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:39-467352 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:39-467551 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:39-467793 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:39-467992 util-scheduler-8620 DEBUG Adding task: 2609 / 0x52cbfb8
Jul 07 20:47:39-468257 util-scheduler-8620 DEBUG Checking readiness of task: 2607 / 0x46620a0
Jul 07 20:47:39-468449 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:39-468656 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:39-468847 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:39-469038 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:39-469282 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:39-469474 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:39-469663 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:39-469852 util-scheduler-8620 DEBUG Running task: 2608 / 0x4d6ff98
Jul 07 20:47:39-470062 util-scheduler-8620 DEBUG Adding task: 2610 / 0x4d6ff98
Jul 07 20:47:39-470284 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:39-470487 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:39-470695 util-scheduler-8620 DEBUG Adding task: 2611 / 0x46620a0
Jul 07 20:47:39-470942 util-scheduler-8620 DEBUG Checking readiness of task: 2611 / 0x46620a0
Jul 07 20:47:39-471135 util-scheduler-8620 DEBUG Checking readiness of task: 2607 / 0x46620a0
Jul 07 20:47:39-471326 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:39-471516 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:39-471706 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:39-471896 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:39-472086 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:39-472275 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:39-472464 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:39-472655 util-scheduler-8620 DEBUG Running task: 2611 / 0x46620a0
Jul 07 20:47:39-472840 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:39-473018 util-8620 DEBUG process_notify is running
Jul 07 20:47:39-473209 util-8620 DEBUG client_notify is running
Jul 07 20:47:39-473390 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:39-473585 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:39-473776 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:39-474033 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:42-280629 util-scheduler-8620 DEBUG Checking readiness of task: 2607 / 0x46620a0
Jul 07 20:47:42-281045 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-281273 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-281469 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-281689 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-281898 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-282089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-282280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-282478 util-scheduler-8620 DEBUG Running task: 2607 / 0x46620a0
Jul 07 20:47:42-282901 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:42-283157 util-scheduler-8620 DEBUG Adding task: 2612 / 0x4662248
Jul 07 20:47:42-283438 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-283633 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-283826 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-284018 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-284209 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-284399 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-284588 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-284779 util-scheduler-8620 DEBUG Running task: 2612 / 0x4662248
Jul 07 20:47:42-284971 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:42-285226 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:42-285463 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:42-285671 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:42-285879 util-scheduler-8620 DEBUG Adding task: 2613 / 0x46620a0
Jul 07 20:47:42-286067 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:42-286274 util-scheduler-8620 DEBUG Adding task: 2614 / 0x46620a0
Jul 07 20:47:42-286522 util-scheduler-8620 DEBUG Checking readiness of task: 2614 / 0x46620a0
Jul 07 20:47:42-286716 util-scheduler-8620 DEBUG Checking readiness of task: 2613 / 0x46620a0
Jul 07 20:47:42-286908 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-287098 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-287291 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-287482 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-287674 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-287864 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-288054 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-288247 util-scheduler-8620 DEBUG Running task: 2613 / 0x46620a0
Jul 07 20:47:42-288433 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:42-288612 util-8620 DEBUG process_notify is running
Jul 07 20:47:42-288785 util-8620 DEBUG client_notify is running
Jul 07 20:47:42-288976 util-scheduler-8620 DEBUG Canceling task: 2610 / 0x4d6ff98
Jul 07 20:47:42-289227 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:42-289451 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:42-289701 cadet-p2p-8620 DEBUG Checking 0x5896640 towards NCSKBW46 (->V8XX)
Jul 07 20:47:42-289937 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:42-290117 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:42-290308 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:42-290595 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:42-290791 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:42-290974 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:42-291163 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:42-291352 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:42-291531 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:42-291716 util-scheduler-8620 DEBUG Canceling task: 2592 / 0x52cba38
Jul 07 20:47:42-291931 util-scheduler-8620 DEBUG Adding task: 2615 / 0x52cba38
Jul 07 20:47:42-292182 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:42-292356 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:42-292540 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:42-292741 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:42-292916 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:42-293092 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:42-293316 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:42-293523 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:42-293708 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:42-293888 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:42-294080 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:42-294886 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:42-873135 util-scheduler-8620 DEBUG Checking readiness of task: 2614 / 0x46620a0
Jul 07 20:47:42-873507 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-873729 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-873924 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-874116 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-874307 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-874497 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-874687 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-874881 util-scheduler-8620 DEBUG Running task: 2614 / 0x46620a0
Jul 07 20:47:42-875298 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:42-875548 util-scheduler-8620 DEBUG Adding task: 2616 / 0x4662248
Jul 07 20:47:42-875819 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-876012 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-876203 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-876393 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-876582 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-876772 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-876962 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-877151 util-scheduler-8620 DEBUG Running task: 2616 / 0x4662248
Jul 07 20:47:42-877369 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:42-877569 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:42-877798 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:42-878062 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:42-878306 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:42-879011 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:42-879224 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:42-879423 cadet-con-8620 DEBUG  PID 4 (expected 4+)
Jul 07 20:47:42-879603 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:42-879791 util-scheduler-8620 DEBUG Canceling task: 2598 / 0x52cba38
Jul 07 20:47:42-880016 util-scheduler-8620 DEBUG Adding task: 2617 / 0x52cba38
Jul 07 20:47:42-880196 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:42-880453 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:42-880669 util-scheduler-8620 DEBUG Adding task: 2618 / 0x4d5e5d8
Jul 07 20:47:42-880854 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:42-881021 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:42-884614 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:42-885411 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:42-885606 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:42-888734 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:42-888927 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:42-891964 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:42-892519 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:42-892709 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:42-895792 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:42-896036 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:42-896277 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:42-896454 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:42-896626 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:42-896797 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:42-897016 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:42-897213 cadet-con-8620 DEBUG  ACK 68
Jul 07 20:47:42-897394 cadet-con-8620 DEBUG  last pid 4, last ack 67, qmax 11, q 0
Jul 07 20:47:42-897664 cadet-con-8620 INFO --> {               ACK} ( 68) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:42-897882 cadet-con-8620 DEBUG  ack 68
Jul 07 20:47:42-898062 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:42-898297 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:42-898502 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:42-898796 cadet-p2p-8620 INFO que {               ACK} ( 68) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:42-898994 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:42-899217 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:42-899400 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:42-899575 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:42-899779 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:47:42-899993 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:47:42-900216 util-scheduler-8620 DEBUG Adding task: 2619 / 0x4d6ff98
Jul 07 20:47:42-900396 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:42-900599 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:42-900775 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:42-900949 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:42-901187 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:42-901391 cadet-p2p-8620 DEBUG QQQ    payload , 68
Jul 07 20:47:42-901567 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:42-901764 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:42-901946 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:42-902157 util-scheduler-8620 DEBUG Adding task: 2620 / 0x46620a0
Jul 07 20:47:42-902419 util-scheduler-8620 DEBUG Checking readiness of task: 2620 / 0x46620a0
Jul 07 20:47:42-902614 util-scheduler-8620 DEBUG Checking readiness of task: 2618 / 0x4d5e5d8
Jul 07 20:47:42-902806 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-902996 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-903186 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-903376 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-903564 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-903753 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-903941 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-904134 util-scheduler-8620 DEBUG Running task: 2618 / 0x4d5e5d8
Jul 07 20:47:42-904319 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:42-904496 util-8620 DEBUG process_notify is running
Jul 07 20:47:42-904668 util-8620 DEBUG client_notify is running
Jul 07 20:47:42-904908 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:42-905115 util-scheduler-8620 DEBUG Adding task: 2621 / 0x4d5e5d8
Jul 07 20:47:42-905336 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:42-905596 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:42-905794 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:42-905991 util-scheduler-8620 DEBUG Running task: 2619 / 0x4d6ff98
Jul 07 20:47:42-906197 util-scheduler-8620 DEBUG Adding task: 2622 / 0x4d6ff98
Jul 07 20:47:42-906419 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:42-906614 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:42-906811 util-scheduler-8620 DEBUG Adding task: 2623 / 0x46620a0
Jul 07 20:47:42-907054 util-scheduler-8620 DEBUG Checking readiness of task: 2623 / 0x46620a0
Jul 07 20:47:42-907247 util-scheduler-8620 DEBUG Checking readiness of task: 2621 / 0x4d5e5d8
Jul 07 20:47:42-907439 util-scheduler-8620 DEBUG Checking readiness of task: 2620 / 0x46620a0
Jul 07 20:47:42-907646 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:42-907840 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:42-908030 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:42-908220 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:42-908409 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:42-908598 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:42-908787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:42-908978 util-scheduler-8620 DEBUG Running task: 2621 / 0x4d5e5d8
Jul 07 20:47:42-909162 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:42-909358 util-8620 DEBUG process_notify is running
Jul 07 20:47:42-909528 util-8620 DEBUG client_notify is running
Jul 07 20:47:42-909738 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:42-909983 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:42-910193 util-scheduler-8620 DEBUG Running task: 2623 / 0x46620a0
Jul 07 20:47:42-910377 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:42-910552 util-8620 DEBUG process_notify is running
Jul 07 20:47:42-910720 util-8620 DEBUG client_notify is running
Jul 07 20:47:42-910898 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:42-911092 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:42-911280 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:42-911521 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:44-191270 util-scheduler-8620 DEBUG Checking readiness of task: 2620 / 0x46620a0
Jul 07 20:47:44-191643 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-191840 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-192034 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-192227 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-192418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-192610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-192810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-193006 util-scheduler-8620 DEBUG Running task: 2620 / 0x46620a0
Jul 07 20:47:44-193447 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:44-193703 util-scheduler-8620 DEBUG Adding task: 2624 / 0x4662248
Jul 07 20:47:44-193980 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-194174 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-194365 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-194555 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-194745 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-194934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-195124 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-195314 util-scheduler-8620 DEBUG Running task: 2624 / 0x4662248
Jul 07 20:47:44-195505 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:44-195704 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:44-195935 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:44-196144 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:44-196388 util-scheduler-8620 DEBUG Adding task: 2625 / 0x46620a0
Jul 07 20:47:44-196576 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:44-196781 util-scheduler-8620 DEBUG Adding task: 2626 / 0x46620a0
Jul 07 20:47:44-197024 util-scheduler-8620 DEBUG Checking readiness of task: 2626 / 0x46620a0
Jul 07 20:47:44-197238 util-scheduler-8620 DEBUG Checking readiness of task: 2625 / 0x46620a0
Jul 07 20:47:44-197432 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-197622 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-197811 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-198001 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-198192 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-198381 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-198570 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-198762 util-scheduler-8620 DEBUG Running task: 2625 / 0x46620a0
Jul 07 20:47:44-198947 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:44-199124 util-8620 DEBUG process_notify is running
Jul 07 20:47:44-199295 util-8620 DEBUG client_notify is running
Jul 07 20:47:44-199484 util-scheduler-8620 DEBUG Canceling task: 2622 / 0x4d6ff98
Jul 07 20:47:44-199708 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:47:44-199928 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:44-200166 cadet-p2p-8620 DEBUG Checking 0x58af308 towards NCSKBW46 (->V8XX)
Jul 07 20:47:44-200399 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:44-200577 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:44-200768 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:44-201035 cadet-p2p-8620 INFO snd {               ACK} ( 68) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:44-201249 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:44-201431 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:44-201619 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:44-201793 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:44-201976 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:44-202149 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:44-202331 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:44-202530 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:44-202704 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:44-202878 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:44-203077 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:44-203281 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:44-203464 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:44-203642 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:44-203833 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:44-204080 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:44-468374 util-scheduler-8620 DEBUG Checking readiness of task: 2626 / 0x46620a0
Jul 07 20:47:44-468668 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-472133 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-472493 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-472690 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-472882 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-473073 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-473296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-473491 util-scheduler-8620 DEBUG Running task: 2609 / 0x52cbfb8
Jul 07 20:47:44-473763 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:44-474011 cadet-tun-8620 DEBUG  kx started 20 s ago
Jul 07 20:47:44-474218 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:44-474419 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:44-474621 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:44-474856 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:44-475036 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:44-475258 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:44-475550 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:44-475747 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:44-475984 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:44-476191 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:44-476507 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:44-476707 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:44-476933 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:44-477116 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:44-477320 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:44-477531 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:44-477747 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:44-477972 util-scheduler-8620 DEBUG Adding task: 2627 / 0x4d6ff98
Jul 07 20:47:44-478152 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:44-478355 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:44-478532 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:44-478706 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:44-478944 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:44-479139 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:44-479316 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:44-479514 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:44-479757 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:44-479957 util-scheduler-8620 DEBUG Adding task: 2628 / 0x52cbfb8
Jul 07 20:47:44-480224 util-scheduler-8620 DEBUG Checking readiness of task: 2626 / 0x46620a0
Jul 07 20:47:44-480429 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-480620 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-480810 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-481000 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-481216 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-481409 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-481598 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-481789 util-scheduler-8620 DEBUG Running task: 2627 / 0x4d6ff98
Jul 07 20:47:44-482000 util-scheduler-8620 DEBUG Adding task: 2629 / 0x4d6ff98
Jul 07 20:47:44-482222 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:44-482426 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:44-482634 util-scheduler-8620 DEBUG Adding task: 2630 / 0x46620a0
Jul 07 20:47:44-482879 util-scheduler-8620 DEBUG Checking readiness of task: 2630 / 0x46620a0
Jul 07 20:47:44-483073 util-scheduler-8620 DEBUG Checking readiness of task: 2626 / 0x46620a0
Jul 07 20:47:44-483263 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:44-483453 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:44-483642 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:44-483832 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:44-484039 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:44-484228 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:44-484417 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:44-484608 util-scheduler-8620 DEBUG Running task: 2630 / 0x46620a0
Jul 07 20:47:44-484793 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:44-484971 util-8620 DEBUG process_notify is running
Jul 07 20:47:44-485144 util-8620 DEBUG client_notify is running
Jul 07 20:47:44-485350 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:44-485546 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:44-485737 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:44-486094 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:45-436589 util-scheduler-8620 DEBUG Checking readiness of task: 2626 / 0x46620a0
Jul 07 20:47:45-436978 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:45-437232 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:45-437429 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:45-437623 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:45-437827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:45-438020 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:45-438228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:45-438428 util-scheduler-8620 DEBUG Running task: 2626 / 0x46620a0
Jul 07 20:47:45-438851 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:45-439105 util-scheduler-8620 DEBUG Adding task: 2631 / 0x4662248
Jul 07 20:47:45-439384 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:45-439577 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:45-439768 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:45-439960 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:45-440150 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:45-440340 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:45-440529 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:45-440718 util-scheduler-8620 DEBUG Running task: 2631 / 0x4662248
Jul 07 20:47:45-440909 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:45-441109 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:45-441367 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:45-441575 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:45-441818 util-scheduler-8620 DEBUG Adding task: 2632 / 0x46620a0
Jul 07 20:47:45-442007 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:45-442214 util-scheduler-8620 DEBUG Adding task: 2633 / 0x46620a0
Jul 07 20:47:45-442460 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:45-442654 util-scheduler-8620 DEBUG Checking readiness of task: 2632 / 0x46620a0
Jul 07 20:47:45-442848 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:45-443039 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:45-443230 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:45-443422 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:45-443612 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:45-443802 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:45-444019 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:45-444212 util-scheduler-8620 DEBUG Running task: 2632 / 0x46620a0
Jul 07 20:47:45-444399 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:45-444578 util-8620 DEBUG process_notify is running
Jul 07 20:47:45-444751 util-8620 DEBUG client_notify is running
Jul 07 20:47:45-444942 util-scheduler-8620 DEBUG Canceling task: 2629 / 0x4d6ff98
Jul 07 20:47:45-445167 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:45-445586 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:45-445828 cadet-p2p-8620 DEBUG Checking 0x58a6760 towards NCSKBW46 (->V8XX)
Jul 07 20:47:45-446063 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:45-446242 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:45-446433 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:45-446718 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:45-446914 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:45-447095 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:45-447284 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:45-447472 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:45-447651 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:45-447836 util-scheduler-8620 DEBUG Canceling task: 2615 / 0x52cba38
Jul 07 20:47:45-448051 util-scheduler-8620 DEBUG Adding task: 2634 / 0x52cba38
Jul 07 20:47:45-448304 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:45-448480 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:45-448662 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:45-448863 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:45-449039 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:45-449236 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:45-449438 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:45-449644 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:45-449828 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:45-450008 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:45-450199 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:45-451088 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:46-227463 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:46-227789 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:46-227985 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:46-228178 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:46-228389 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:46-228584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:46-228775 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:46-228966 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:46-229159 util-scheduler-8620 DEBUG Running task: 2293 / 0x5e2de48
Jul 07 20:47:46-229384 cadet-tun-8620 DEBUG delayed destroying tunnel 0x5e2de48
Jul 07 20:47:46-229908 cadet-con-8620 DEBUG   sending connection destroy for connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-230183 cadet-con-8620 INFO --> {CONNECTION_DESTROY} ( 0) on connection 1KSG9GE2 (->D3TJ) (36 bytes)
Jul 07 20:47:46-230399 cadet-con-8620 DEBUG   C_P+ 0x5e31aa0 0
Jul 07 20:47:46-230640 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:47:46-230849 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-231150 cadet-p2p-8620 INFO que {CONNECTION_DESTROY} ( 0) on connection 1KSG9GE2 (->D3TJ) (0x5e31aa0) FWD towards D3TJ (size 36)
Jul 07 20:47:46-231375 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:46-231621 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-231805 cadet-con-8620 DEBUG  last ack recv: 74, last pid sent: 10
Jul 07 20:47:46-231981 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:46-232187 cadet-p2p-8620 DEBUG calling core tmt rdy towards D3TJ for 36 bytes
Jul 07 20:47:46-232403 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:47:46-232643 util-scheduler-8620 DEBUG Adding task: 2635 / 0x5e2b838
Jul 07 20:47:46-232824 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:46-233027 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:47:46-233225 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:46-233402 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:47:46-233656 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-233840 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:46-234016 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:46-234215 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:47:46-234758 cadet-con-8620 DEBUG   sending connection destroy for connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-235940 cadet-con-8620 INFO --> {CONNECTION_DESTROY} ( 0) on connection BFARXZN9 (->D3TJ) (36 bytes)
Jul 07 20:47:46-236144 cadet-con-8620 DEBUG   C_P+ 0x5e2cf38 0
Jul 07 20:47:46-236385 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:47:46-236597 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-236918 cadet-p2p-8620 INFO que {CONNECTION_DESTROY} ( 0) on connection BFARXZN9 (->D3TJ) (0x5e2cf38) BCK towards D3TJ (size 36)
Jul 07 20:47:46-237116 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:46-237362 cadet-con-8620 DEBUG  checking sendability of BCK traffic on BFARXZN9 (->D3TJ)
Jul 07 20:47:46-237545 cadet-con-8620 DEBUG  last ack recv: 65, last pid sent: 1
Jul 07 20:47:46-237721 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:46-237942 cadet-p2p-8620 DEBUG core tmt rdy towards D3TJ already called
Jul 07 20:47:46-238146 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:47:46-238320 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:47:46-238495 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:47:46-238734 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} FWD on 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-238916 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:46-239125 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:46-239359 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} BCK on BFARXZN9 (->D3TJ)
Jul 07 20:47:46-239539 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:46-239713 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:46-239911 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:47:46-240235 cadet-tun-8620 DEBUG destroying tunnel D3TJ
Jul 07 20:47:46-240482 cadet-con-8620 DEBUG destroying connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-240664 cadet-con-8620 DEBUG  fc's f: 0x5e31aa4, b: 0x5e31ad8
Jul 07 20:47:46-240846 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:46-241077 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-241347 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:47:46-241554 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-241912 cadet-p2p-8620 DEBUG GMP queue cancel {CONNECTION_DESTROY}
Jul 07 20:47:46-242150 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-242404 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:47:46-242612 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:46-242850 cadet-con-8620 DEBUG  get next hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:47:46-243057 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-243290 cadet-p2p-8620 DEBUG removing connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-243515 cadet-p2p-8620 DEBUG from peer D3TJ
Jul 07 20:47:46-243719 cadet-p2p-8620 DEBUG peer D3TJ ok, has 2 connections.
Jul 07 20:47:46-243964 cadet-con-8620 DEBUG  get prev hop 1KSG9GE2 (->D3TJ) [0/2]
Jul 07 20:47:46-244189 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:46-244439 cadet-p2p-8620 DEBUG removing connection 1KSG9GE2 (->D3TJ)
Jul 07 20:47:46-244639 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:47:46-244985 cadet-p2p-8620 DEBUG peer GN10 ok, has 4 connections.
Jul 07 20:47:46-245180 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:46-245466 cadet-tun-8620 DEBUG Removing connection 1KSG9GE2 (->D3TJ) from tunnel D3TJ
Jul 07 20:47:46-246283 util-scheduler-8620 DEBUG Canceling task: 2267 / 0x5e31aa0
Jul 07 20:47:46-246496 util-scheduler-8620 DEBUG Canceling task: 2300 / 0x5e31aa0
Jul 07 20:47:46-246828 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:46-247046 util-scheduler-8620 DEBUG Adding task: 2636 / 0x4d5e5d8
Jul 07 20:47:46-247582 cadet-con-8620 DEBUG destroying connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-247789 cadet-con-8620 DEBUG  fc's f: 0x5e2cf3c, b: 0x5e2cf70
Jul 07 20:47:46-247975 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:46-248215 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-248461 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:47:46-248672 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:46-248908 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-249138 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:47:46-249367 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-249581 cadet-p2p-8620 DEBUG GMP queue cancel {CONNECTION_DESTROY}
Jul 07 20:47:46-249931 cadet-con-8620 DEBUG  get next hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:47:46-250143 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:47:46-250376 cadet-p2p-8620 DEBUG removing connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-250576 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:47:46-250795 cadet-p2p-8620 DEBUG peer GN10 ok, has 3 connections.
Jul 07 20:47:46-251035 cadet-con-8620 DEBUG  get prev hop BFARXZN9 (->D3TJ) [1/2]
Jul 07 20:47:46-251240 cadet-con-8620 DEBUG   ID: D3TJ (6)
Jul 07 20:47:46-251469 cadet-p2p-8620 DEBUG removing connection BFARXZN9 (->D3TJ)
Jul 07 20:47:46-251684 cadet-p2p-8620 DEBUG from peer D3TJ
Jul 07 20:47:46-251884 cadet-p2p-8620 DEBUG peer D3TJ ok, has 1 connections.
Jul 07 20:47:46-252075 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:47:46-252318 cadet-tun-8620 DEBUG Removing connection BFARXZN9 (->D3TJ) from tunnel D3TJ
Jul 07 20:47:46-253020 util-scheduler-8620 DEBUG Canceling task: 1243 / 0x5e2cf38
Jul 07 20:47:46-253355 util-scheduler-8620 DEBUG Canceling task: 2088 / 0x5e2cf38
Jul 07 20:47:46-253757 util-scheduler-8620 DEBUG Checking readiness of task: 2636 / 0x4d5e5d8
Jul 07 20:47:46-253958 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:46-254151 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:46-254353 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:46-254544 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:46-254733 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:46-254923 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:46-255113 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:46-255301 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:46-255494 util-scheduler-8620 DEBUG Running task: 2636 / 0x4d5e5d8
Jul 07 20:47:46-255680 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:46-255858 util-8620 DEBUG process_notify is running
Jul 07 20:47:46-256032 util-8620 DEBUG client_notify is running
Jul 07 20:47:46-256269 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:46-256477 util-scheduler-8620 DEBUG Adding task: 2637 / 0x4d5e5d8
Jul 07 20:47:46-256678 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:47:46-256937 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:46-257153 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:46-257387 util-scheduler-8620 DEBUG Running task: 2635 / 0x5e2b838
Jul 07 20:47:46-258434 util-scheduler-8620 DEBUG Adding task: 2638 / 0x5e2b838
Jul 07 20:47:46-259518 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:47:46-259728 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:46-259933 util-scheduler-8620 DEBUG Adding task: 2639 / 0x46620a0
Jul 07 20:47:46-260191 util-scheduler-8620 DEBUG Checking readiness of task: 2639 / 0x46620a0
Jul 07 20:47:46-260386 util-scheduler-8620 DEBUG Checking readiness of task: 2637 / 0x4d5e5d8
Jul 07 20:47:46-261062 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:46-261719 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:46-262247 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:46-262443 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:46-262636 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:46-262826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:46-263017 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:46-263207 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:46-263399 util-scheduler-8620 DEBUG Running task: 2637 / 0x4d5e5d8
Jul 07 20:47:46-263585 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:46-263762 util-8620 DEBUG process_notify is running
Jul 07 20:47:46-263932 util-8620 DEBUG client_notify is running
Jul 07 20:47:46-264166 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:46-264373 util-scheduler-8620 DEBUG Adding task: 2640 / 0x4d5e5d8
Jul 07 20:47:46-264574 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:47:46-264825 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:46-265022 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:46-265241 util-scheduler-8620 DEBUG Running task: 2639 / 0x46620a0
Jul 07 20:47:46-265427 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:46-265602 util-8620 DEBUG process_notify is running
Jul 07 20:47:46-265771 util-8620 DEBUG client_notify is running
Jul 07 20:47:46-265948 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:46-266143 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:46-266331 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:46-266572 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:46-266825 util-scheduler-8620 DEBUG Checking readiness of task: 2640 / 0x4d5e5d8
Jul 07 20:47:46-267018 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:46-267208 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:46-267399 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:46-267588 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:46-267778 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:46-267967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:46-268156 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:46-268344 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:46-268535 util-scheduler-8620 DEBUG Running task: 2640 / 0x4d5e5d8
Jul 07 20:47:46-268721 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:46-268895 util-8620 DEBUG process_notify is running
Jul 07 20:47:46-269063 util-8620 DEBUG client_notify is running
Jul 07 20:47:46-269313 util-8620 DEBUG Transmitting message of type 168 and size 32 to statistics service.
Jul 07 20:47:46-269560 util-8620 DEBUG Connection transmitted 32/32 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:47-173801 util-scheduler-8620 DEBUG Checking readiness of task: 2633 / 0x46620a0
Jul 07 20:47:47-174164 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-174365 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-174562 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-174762 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-174959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-175149 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-175339 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-175538 util-scheduler-8620 DEBUG Running task: 2633 / 0x46620a0
Jul 07 20:47:47-175970 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:47-176230 util-scheduler-8620 DEBUG Adding task: 2641 / 0x4662248
Jul 07 20:47:47-176511 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-176705 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-176908 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-177104 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-177333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-177528 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-177719 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-177913 util-scheduler-8620 DEBUG Running task: 2641 / 0x4662248
Jul 07 20:47:47-178107 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:47-178308 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:47-178544 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:47-178806 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:47-179049 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:47-179278 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:47-179485 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:47-179680 cadet-con-8620 DEBUG  PID 5 (expected 5+)
Jul 07 20:47:47-179860 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:47-180047 util-scheduler-8620 DEBUG Canceling task: 2617 / 0x52cba38
Jul 07 20:47:47-180272 util-scheduler-8620 DEBUG Adding task: 2642 / 0x52cba38
Jul 07 20:47:47-180451 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:47-180711 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:47-180927 util-scheduler-8620 DEBUG Adding task: 2643 / 0x4d5e5d8
Jul 07 20:47:47-181111 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:47-181513 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:47-185026 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:47-186315 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:47-186515 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:47-189718 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:47-189922 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:47-193036 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:47-193769 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:47-193975 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:47-197227 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:47-197483 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:47-197729 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:47-197937 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:47-198113 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:47-198284 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:47-198504 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:47-198681 cadet-con-8620 DEBUG  ACK 69
Jul 07 20:47:47-198861 cadet-con-8620 DEBUG  last pid 5, last ack 68, qmax 11, q 0
Jul 07 20:47:47-199130 cadet-con-8620 INFO --> {               ACK} ( 69) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:47-199321 cadet-con-8620 DEBUG  ack 69
Jul 07 20:47:47-199502 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:47-199737 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:47-199943 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:47-200242 cadet-p2p-8620 INFO que {               ACK} ( 69) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:47-200440 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:47-200664 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:47-200846 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:47-201020 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:47-201245 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:47:47-201460 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:47:47-201684 util-scheduler-8620 DEBUG Adding task: 2644 / 0x4d6ff98
Jul 07 20:47:47-201863 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:47-202069 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:47-202245 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:47-202420 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:47-202655 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:47-202838 cadet-p2p-8620 DEBUG QQQ    payload , 69
Jul 07 20:47:47-203013 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:47-203210 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:47-203392 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:47-203604 util-scheduler-8620 DEBUG Adding task: 2645 / 0x46620a0
Jul 07 20:47:47-203876 util-scheduler-8620 DEBUG Checking readiness of task: 2645 / 0x46620a0
Jul 07 20:47:47-204072 util-scheduler-8620 DEBUG Checking readiness of task: 2643 / 0x4d5e5d8
Jul 07 20:47:47-204264 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-204457 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-204650 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-204842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-205033 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-205246 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-205437 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-205631 util-scheduler-8620 DEBUG Running task: 2643 / 0x4d5e5d8
Jul 07 20:47:47-205818 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:47-206000 util-8620 DEBUG process_notify is running
Jul 07 20:47:47-206175 util-8620 DEBUG client_notify is running
Jul 07 20:47:47-206431 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:47-206645 util-scheduler-8620 DEBUG Adding task: 2646 / 0x4d5e5d8
Jul 07 20:47:47-206853 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:47-207173 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:47-207376 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:47-207576 util-scheduler-8620 DEBUG Running task: 2644 / 0x4d6ff98
Jul 07 20:47:47-207786 util-scheduler-8620 DEBUG Adding task: 2647 / 0x4d6ff98
Jul 07 20:47:47-208009 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:47-208231 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:47-208429 util-scheduler-8620 DEBUG Adding task: 2648 / 0x46620a0
Jul 07 20:47:47-208680 util-scheduler-8620 DEBUG Checking readiness of task: 2648 / 0x46620a0
Jul 07 20:47:47-208873 util-scheduler-8620 DEBUG Checking readiness of task: 2646 / 0x4d5e5d8
Jul 07 20:47:47-209063 util-scheduler-8620 DEBUG Checking readiness of task: 2645 / 0x46620a0
Jul 07 20:47:47-209277 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-209467 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-209656 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-209844 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-210032 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-210220 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-210407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-210596 util-scheduler-8620 DEBUG Running task: 2646 / 0x4d5e5d8
Jul 07 20:47:47-210778 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:47-210953 util-8620 DEBUG process_notify is running
Jul 07 20:47:47-211122 util-8620 DEBUG client_notify is running
Jul 07 20:47:47-211332 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:47-211620 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:47-211830 util-scheduler-8620 DEBUG Running task: 2648 / 0x46620a0
Jul 07 20:47:47-212014 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:47-212188 util-8620 DEBUG process_notify is running
Jul 07 20:47:47-212355 util-8620 DEBUG client_notify is running
Jul 07 20:47:47-212532 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:47-212726 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:47-212912 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:47-213251 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:47-213513 util-scheduler-8620 DEBUG Checking readiness of task: 2645 / 0x46620a0
Jul 07 20:47:47-213705 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-213895 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-214085 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-214274 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-214463 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-214651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-214839 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-215028 util-scheduler-8620 DEBUG Running task: 2645 / 0x46620a0
Jul 07 20:47:47-215431 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:47-215660 util-scheduler-8620 DEBUG Adding task: 2649 / 0x4662248
Jul 07 20:47:47-215906 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-216098 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-216287 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-216476 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-216664 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-216852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-217040 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-217265 util-scheduler-8620 DEBUG Running task: 2649 / 0x4662248
Jul 07 20:47:47-217456 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:47-217652 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:47-217867 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:47-218063 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:47-218264 util-scheduler-8620 DEBUG Adding task: 2650 / 0x46620a0
Jul 07 20:47:47-218446 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:47-218646 util-scheduler-8620 DEBUG Adding task: 2651 / 0x46620a0
Jul 07 20:47:47-218885 util-scheduler-8620 DEBUG Checking readiness of task: 2651 / 0x46620a0
Jul 07 20:47:47-219076 util-scheduler-8620 DEBUG Checking readiness of task: 2650 / 0x46620a0
Jul 07 20:47:47-219266 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:47-219455 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:47-219646 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:47-219838 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:47-220028 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:47-220218 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:47-220406 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:47-220598 util-scheduler-8620 DEBUG Running task: 2650 / 0x46620a0
Jul 07 20:47:47-220782 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:47-220957 util-8620 DEBUG process_notify is running
Jul 07 20:47:47-221130 util-8620 DEBUG client_notify is running
Jul 07 20:47:47-221341 util-scheduler-8620 DEBUG Canceling task: 2647 / 0x4d6ff98
Jul 07 20:47:47-221573 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:47:47-221795 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:47-222033 cadet-p2p-8620 DEBUG Checking 0x58b9370 towards NCSKBW46 (->V8XX)
Jul 07 20:47:47-222267 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:47-222444 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:47-222633 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:47-222901 cadet-p2p-8620 INFO snd {               ACK} ( 69) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:47-223094 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:47-223275 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:47-223462 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:47-223634 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:47-223816 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:47-223989 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:47-224170 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:47-224367 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:47-224540 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:47-224712 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:47-224909 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:47-225111 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:47-225315 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:47-225492 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:47-225682 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:47-226679 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:49-141623 util-scheduler-8620 DEBUG Checking readiness of task: 2651 / 0x46620a0
Jul 07 20:47:49-142003 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-142201 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-142395 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-142616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-142808 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-142998 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-143187 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-143400 util-scheduler-8620 DEBUG Running task: 2651 / 0x46620a0
Jul 07 20:47:49-143822 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:49-144075 util-scheduler-8620 DEBUG Adding task: 2652 / 0x4662248
Jul 07 20:47:49-144352 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-144545 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-144735 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-144925 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-145114 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-145353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-145544 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-145734 util-scheduler-8620 DEBUG Running task: 2652 / 0x4662248
Jul 07 20:47:49-145924 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:49-146123 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:49-146352 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:47:49-146556 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:49-146765 util-scheduler-8620 DEBUG Adding task: 2653 / 0x46620a0
Jul 07 20:47:49-146952 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:49-147156 util-scheduler-8620 DEBUG Adding task: 2654 / 0x46620a0
Jul 07 20:47:49-147399 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-147592 util-scheduler-8620 DEBUG Checking readiness of task: 2653 / 0x46620a0
Jul 07 20:47:49-147784 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-147974 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-148164 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-148353 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-148543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-148731 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-148920 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-149111 util-scheduler-8620 DEBUG Running task: 2653 / 0x46620a0
Jul 07 20:47:49-149319 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:49-149497 util-8620 DEBUG process_notify is running
Jul 07 20:47:49-149670 util-8620 DEBUG client_notify is running
Jul 07 20:47:49-149858 util-scheduler-8620 DEBUG Canceling task: 2638 / 0x5e2b838
Jul 07 20:47:49-150081 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:47:49-150300 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:47:49-150487 cadet-p2p-8620 DEBUG Checking 0x58872e0 towards NULL
Jul 07 20:47:49-150684 cadet-p2p-8620 DEBUG   on connection NULL FWD
Jul 07 20:47:49-150859 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:47:49-151047 cadet-p2p-8620 DEBUG   raw {CONNECTION_DESTROY}
Jul 07 20:47:49-151262 cadet-p2p-8620 INFO snd {CONNECTION_DESTROY} ( 0) on connection NULL ((nil)) FWD (size 36)
Jul 07 20:47:49-151457 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:49-151636 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:49-151821 cadet-con-8620 DEBUG  sent FWD {CONNECTION_DESTROY}
Jul 07 20:47:49-152009 cadet-p2p-8620 DEBUG Checking 0x5887e68 towards NULL
Jul 07 20:47:49-152222 cadet-p2p-8620 DEBUG Checking 0x5887e68 towards NULL
Jul 07 20:47:49-152398 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:49-152605 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `D3TJ'
Jul 07 20:47:49-152819 util-scheduler-8620 DEBUG Adding task: 2655 / 0x5e2b838
Jul 07 20:47:49-152998 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:49-153175 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:47:49-153397 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:47:49-153571 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:49-153745 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x5e2b864
Jul 07 20:47:49-153942 cadet-p2p-8620 DEBUG QQQ  - {CONNECTION_DESTROY} BCK on NULL
Jul 07 20:47:49-154120 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:47:49-154296 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:47:49-154494 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:47:49-154697 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:47:49-154880 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:47:49-155081 util-scheduler-8620 DEBUG Adding task: 2656 / 0x5e2b838
Jul 07 20:47:49-155299 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:47:49-155493 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:49-155693 util-scheduler-8620 DEBUG Adding task: 2657 / 0x46620a0
Jul 07 20:47:49-155892 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:47:49-156138 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:49-156335 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:49-156580 util-scheduler-8620 DEBUG Checking readiness of task: 2657 / 0x46620a0
Jul 07 20:47:49-156773 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-156964 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-157153 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-157368 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-157558 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-157748 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-157936 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-158125 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-158315 util-scheduler-8620 DEBUG Running task: 2657 / 0x46620a0
Jul 07 20:47:49-158499 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:49-158675 util-8620 DEBUG process_notify is running
Jul 07 20:47:49-158845 util-8620 DEBUG client_notify is running
Jul 07 20:47:49-159022 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:49-159216 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:49-159404 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:49-159642 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:49-159847 util-scheduler-8620 DEBUG Running task: 2655 / 0x5e2b838
Jul 07 20:47:49-160040 util-scheduler-8620 DEBUG Canceling task: 2656 / 0x5e2b838
Jul 07 20:47:49-160252 util-scheduler-8620 DEBUG Adding task: 2658 / 0x5e2b838
Jul 07 20:47:49-160468 core-api-8620 DEBUG Adding SEND REQUEST for peer `D3TJ' to message queue
Jul 07 20:47:49-160661 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:49-160859 util-scheduler-8620 DEBUG Adding task: 2659 / 0x46620a0
Jul 07 20:47:49-161098 util-scheduler-8620 DEBUG Checking readiness of task: 2659 / 0x46620a0
Jul 07 20:47:49-161313 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-161507 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-161715 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-161905 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-162095 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-162284 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-162472 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-162661 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-162851 util-scheduler-8620 DEBUG Running task: 2659 / 0x46620a0
Jul 07 20:47:49-163034 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:49-163209 util-8620 DEBUG process_notify is running
Jul 07 20:47:49-163377 util-8620 DEBUG client_notify is running
Jul 07 20:47:49-163553 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:49-163740 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:49-163927 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:49-164164 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:49-480391 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-480700 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-483345 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-483558 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-483807 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-484016 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-484206 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-484397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-484590 util-scheduler-8620 DEBUG Running task: 2628 / 0x52cbfb8
Jul 07 20:47:49-484822 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:49-485067 cadet-tun-8620 DEBUG  kx started 25 s ago
Jul 07 20:47:49-485298 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:49-485498 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:49-485700 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:49-485934 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:49-486114 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:49-486335 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:49-486623 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:49-486822 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:49-487058 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:49-487264 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:49-487578 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:49-487778 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:49-488003 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:49-488186 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:49-488361 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:49-488569 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:49-488782 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:49-489004 util-scheduler-8620 DEBUG Adding task: 2660 / 0x4d6ff98
Jul 07 20:47:49-489183 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:49-489408 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:49-489583 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:49-489759 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:49-489997 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:49-490230 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:49-490409 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:49-490608 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:49-490851 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:49-491048 util-scheduler-8620 DEBUG Adding task: 2661 / 0x52cbfb8
Jul 07 20:47:49-491305 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-491497 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-491687 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-491877 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-492067 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-492256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-492445 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-492634 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-492823 util-scheduler-8620 DEBUG Running task: 2660 / 0x4d6ff98
Jul 07 20:47:49-493029 util-scheduler-8620 DEBUG Adding task: 2662 / 0x4d6ff98
Jul 07 20:47:49-493270 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:49-493472 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:49-493677 util-scheduler-8620 DEBUG Adding task: 2663 / 0x46620a0
Jul 07 20:47:49-493920 util-scheduler-8620 DEBUG Checking readiness of task: 2663 / 0x46620a0
Jul 07 20:47:49-494113 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-494303 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-494495 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-494684 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-494873 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-495062 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-495250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-495439 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-495629 util-scheduler-8620 DEBUG Running task: 2663 / 0x46620a0
Jul 07 20:47:49-495813 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:49-495991 util-8620 DEBUG process_notify is running
Jul 07 20:47:49-496162 util-8620 DEBUG client_notify is running
Jul 07 20:47:49-496340 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:49-496532 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:49-496721 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:49-496974 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:49-497239 util-scheduler-8620 DEBUG Checking readiness of task: 2654 / 0x46620a0
Jul 07 20:47:49-497433 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-497623 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-497813 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-498002 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-498191 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-498379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-498572 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-498763 util-scheduler-8620 DEBUG Running task: 2654 / 0x46620a0
Jul 07 20:47:49-499166 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:49-499411 util-scheduler-8620 DEBUG Adding task: 2664 / 0x4662248
Jul 07 20:47:49-499658 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-499849 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-500040 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-500230 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-500419 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-500608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-500796 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-500985 util-scheduler-8620 DEBUG Running task: 2664 / 0x4662248
Jul 07 20:47:49-501174 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:49-501404 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:49-501620 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:49-501837 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:49-502046 util-scheduler-8620 DEBUG Adding task: 2665 / 0x46620a0
Jul 07 20:47:49-502233 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:49-502436 util-scheduler-8620 DEBUG Adding task: 2666 / 0x46620a0
Jul 07 20:47:49-502677 util-scheduler-8620 DEBUG Checking readiness of task: 2666 / 0x46620a0
Jul 07 20:47:49-502869 util-scheduler-8620 DEBUG Checking readiness of task: 2665 / 0x46620a0
Jul 07 20:47:49-503059 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:49-503250 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:49-503440 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:49-503631 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:49-503820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:49-504008 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:49-504197 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:49-504388 util-scheduler-8620 DEBUG Running task: 2665 / 0x46620a0
Jul 07 20:47:49-504571 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:49-504746 util-8620 DEBUG process_notify is running
Jul 07 20:47:49-504914 util-8620 DEBUG client_notify is running
Jul 07 20:47:49-505099 util-scheduler-8620 DEBUG Canceling task: 2662 / 0x4d6ff98
Jul 07 20:47:49-505340 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:49-505555 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:49-505785 cadet-p2p-8620 DEBUG Checking 0x58d0930 towards NCSKBW46 (->V8XX)
Jul 07 20:47:49-506017 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:49-506194 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:49-506380 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:49-506662 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:49-506856 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:49-507034 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:49-507220 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:49-507407 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:49-507584 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:49-507770 util-scheduler-8620 DEBUG Canceling task: 2634 / 0x52cba38
Jul 07 20:47:49-507981 util-scheduler-8620 DEBUG Adding task: 2667 / 0x52cba38
Jul 07 20:47:49-508225 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:49-508395 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:49-508578 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:49-508776 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:49-508950 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:49-509124 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:49-509360 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:49-509564 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:49-509746 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:49-509923 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:49-510111 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:49-510354 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:51-435740 util-scheduler-8620 DEBUG Checking readiness of task: 2666 / 0x46620a0
Jul 07 20:47:51-436108 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-436307 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-436501 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-436705 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-436896 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-437086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-437304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-437501 util-scheduler-8620 DEBUG Running task: 2666 / 0x46620a0
Jul 07 20:47:51-437920 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:51-438173 util-scheduler-8620 DEBUG Adding task: 2668 / 0x4662248
Jul 07 20:47:51-438449 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-438642 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-438833 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-439024 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-439214 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-439402 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-439591 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-439781 util-scheduler-8620 DEBUG Running task: 2668 / 0x4662248
Jul 07 20:47:51-439971 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:51-440170 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:51-440401 core-api-8620 DEBUG Received notification about transmission readiness to `D3TJ'.
Jul 07 20:47:51-440605 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:51-440813 util-scheduler-8620 DEBUG Adding task: 2669 / 0x46620a0
Jul 07 20:47:51-441000 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:51-441227 util-scheduler-8620 DEBUG Adding task: 2670 / 0x46620a0
Jul 07 20:47:51-441472 util-scheduler-8620 DEBUG Checking readiness of task: 2670 / 0x46620a0
Jul 07 20:47:51-441668 util-scheduler-8620 DEBUG Checking readiness of task: 2669 / 0x46620a0
Jul 07 20:47:51-441860 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-442052 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-442242 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-442432 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-442620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-442809 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-442997 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-443188 util-scheduler-8620 DEBUG Running task: 2669 / 0x46620a0
Jul 07 20:47:51-443372 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:51-443549 util-8620 DEBUG process_notify is running
Jul 07 20:47:51-443751 util-8620 DEBUG client_notify is running
Jul 07 20:47:51-443940 util-scheduler-8620 DEBUG Canceling task: 2658 / 0x5e2b838
Jul 07 20:47:51-444163 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' with 36 bytes.
Jul 07 20:47:51-444381 cadet-p2p-8620 DEBUG Queue send towards D3TJ (max 196)
Jul 07 20:47:51-444567 cadet-p2p-8620 DEBUG Checking 0x5887e68 towards NULL
Jul 07 20:47:51-444751 cadet-p2p-8620 DEBUG   on connection NULL BCK
Jul 07 20:47:51-444927 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:47:51-445115 cadet-p2p-8620 DEBUG   raw {CONNECTION_DESTROY}
Jul 07 20:47:51-445354 cadet-p2p-8620 INFO snd {CONNECTION_DESTROY} ( 0) on connection NULL ((nil)) BCK (size 36)
Jul 07 20:47:51-445545 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:51-445724 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:51-445912 cadet-con-8620 DEBUG  sent BCK {CONNECTION_DESTROY}
Jul 07 20:47:51-446103 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:47:51-446303 cadet-p2p-8620 DEBUG QQQ Message queue towards D3TJ
Jul 07 20:47:51-446477 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:51-446651 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:51-446850 cadet-p2p-8620 DEBUG QQQ End queue towards D3TJ
Jul 07 20:47:51-447054 core-api-8620 DEBUG Transmitting SEND request to `D3TJ' yielded 36 bytes.
Jul 07 20:47:51-447236 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:47:51-447415 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:51-447604 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:47:51-447849 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:51-805118 util-scheduler-8620 DEBUG Checking readiness of task: 2670 / 0x46620a0
Jul 07 20:47:51-805460 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-805658 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-805851 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-806043 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-806235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-806425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-806615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-806810 util-scheduler-8620 DEBUG Running task: 2670 / 0x46620a0
Jul 07 20:47:51-807225 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:51-807471 util-scheduler-8620 DEBUG Adding task: 2671 / 0x4662248
Jul 07 20:47:51-807738 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-807930 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-808121 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-808311 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-808501 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-808691 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-808880 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-809069 util-scheduler-8620 DEBUG Running task: 2671 / 0x4662248
Jul 07 20:47:51-809286 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:51-809488 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:51-809925 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:51-810375 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:51-810626 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:51-810858 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:51-811094 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:51-811291 cadet-con-8620 DEBUG  PID 6 (expected 6+)
Jul 07 20:47:51-811474 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:51-811663 util-scheduler-8620 DEBUG Canceling task: 2642 / 0x52cba38
Jul 07 20:47:51-811887 util-scheduler-8620 DEBUG Adding task: 2672 / 0x52cba38
Jul 07 20:47:51-812067 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:51-812325 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:51-812539 util-scheduler-8620 DEBUG Adding task: 2673 / 0x4d5e5d8
Jul 07 20:47:51-812723 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:51-812891 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:51-816426 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:51-817237 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:51-817435 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:51-820573 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:51-820750 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:51-823709 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:51-824762 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:51-824969 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:51-828149 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:51-828396 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:51-828639 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:51-828817 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:51-828990 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:51-829165 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:51-829408 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:51-829587 cadet-con-8620 DEBUG  ACK 70
Jul 07 20:47:51-829767 cadet-con-8620 DEBUG  last pid 6, last ack 69, qmax 11, q 0
Jul 07 20:47:51-830036 cadet-con-8620 INFO --> {               ACK} ( 70) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:51-830228 cadet-con-8620 DEBUG  ack 70
Jul 07 20:47:51-830408 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:51-830642 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:51-830848 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:51-831144 cadet-p2p-8620 INFO que {               ACK} ( 70) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:51-831343 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:51-831567 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:51-831750 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:51-831927 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:51-832132 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:47:51-832348 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:47:51-832570 util-scheduler-8620 DEBUG Adding task: 2674 / 0x4d6ff98
Jul 07 20:47:51-832751 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:51-832954 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:51-833131 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:51-833327 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:51-833565 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:51-833747 cadet-p2p-8620 DEBUG QQQ    payload , 70
Jul 07 20:47:51-833922 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:51-834119 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:51-834304 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:51-834511 util-scheduler-8620 DEBUG Adding task: 2675 / 0x46620a0
Jul 07 20:47:51-834776 util-scheduler-8620 DEBUG Checking readiness of task: 2675 / 0x46620a0
Jul 07 20:47:51-834972 util-scheduler-8620 DEBUG Checking readiness of task: 2673 / 0x4d5e5d8
Jul 07 20:47:51-835164 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-835356 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-835570 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-835763 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-835953 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-836142 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-836332 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-836525 util-scheduler-8620 DEBUG Running task: 2673 / 0x4d5e5d8
Jul 07 20:47:51-836711 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:51-836889 util-8620 DEBUG process_notify is running
Jul 07 20:47:51-837061 util-8620 DEBUG client_notify is running
Jul 07 20:47:51-837320 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:51-837529 util-scheduler-8620 DEBUG Adding task: 2676 / 0x4d5e5d8
Jul 07 20:47:51-837731 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:51-837991 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:51-838190 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:51-838387 util-scheduler-8620 DEBUG Running task: 2674 / 0x4d6ff98
Jul 07 20:47:51-838592 util-scheduler-8620 DEBUG Adding task: 2677 / 0x4d6ff98
Jul 07 20:47:51-838813 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:51-839009 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:51-839207 util-scheduler-8620 DEBUG Adding task: 2678 / 0x46620a0
Jul 07 20:47:51-839449 util-scheduler-8620 DEBUG Checking readiness of task: 2678 / 0x46620a0
Jul 07 20:47:51-839643 util-scheduler-8620 DEBUG Checking readiness of task: 2676 / 0x4d5e5d8
Jul 07 20:47:51-839834 util-scheduler-8620 DEBUG Checking readiness of task: 2675 / 0x46620a0
Jul 07 20:47:51-840024 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:51-840214 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:51-840404 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:51-840595 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:51-840784 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:51-840973 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:51-841162 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:51-841372 util-scheduler-8620 DEBUG Running task: 2676 / 0x4d5e5d8
Jul 07 20:47:51-841556 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:51-841730 util-8620 DEBUG process_notify is running
Jul 07 20:47:51-841899 util-8620 DEBUG client_notify is running
Jul 07 20:47:51-842109 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:51-842353 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:51-842562 util-scheduler-8620 DEBUG Running task: 2678 / 0x46620a0
Jul 07 20:47:51-842747 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:51-842921 util-8620 DEBUG process_notify is running
Jul 07 20:47:51-843090 util-8620 DEBUG client_notify is running
Jul 07 20:47:51-843267 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:51-843461 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:51-843701 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:51-843942 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:52-637319 util-scheduler-8620 DEBUG Checking readiness of task: 2675 / 0x46620a0
Jul 07 20:47:52-637650 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:52-637847 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:52-638064 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:52-638256 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:52-638447 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:52-638654 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:52-638852 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:52-639046 util-scheduler-8620 DEBUG Running task: 2675 / 0x46620a0
Jul 07 20:47:52-639465 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:52-639713 util-scheduler-8620 DEBUG Adding task: 2679 / 0x4662248
Jul 07 20:47:52-639983 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:52-640175 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:52-640366 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:52-640555 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:52-640746 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:52-640934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:52-641123 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:52-641334 util-scheduler-8620 DEBUG Running task: 2679 / 0x4662248
Jul 07 20:47:52-641526 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:52-641724 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:52-641950 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:52-642173 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:52-642397 util-scheduler-8620 DEBUG Adding task: 2680 / 0x46620a0
Jul 07 20:47:52-642584 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:52-642801 util-scheduler-8620 DEBUG Adding task: 2681 / 0x46620a0
Jul 07 20:47:52-643058 util-scheduler-8620 DEBUG Checking readiness of task: 2681 / 0x46620a0
Jul 07 20:47:52-643253 util-scheduler-8620 DEBUG Checking readiness of task: 2680 / 0x46620a0
Jul 07 20:47:52-643445 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:52-643634 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:52-643824 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:52-644013 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:52-644202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:52-644390 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:52-644578 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:52-644769 util-scheduler-8620 DEBUG Running task: 2680 / 0x46620a0
Jul 07 20:47:52-644952 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:52-645130 util-8620 DEBUG process_notify is running
Jul 07 20:47:52-645322 util-8620 DEBUG client_notify is running
Jul 07 20:47:52-645510 util-scheduler-8620 DEBUG Canceling task: 2677 / 0x4d6ff98
Jul 07 20:47:52-645734 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:47:52-645952 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:52-646189 cadet-p2p-8620 DEBUG Checking 0x58e7a48 towards NCSKBW46 (->V8XX)
Jul 07 20:47:52-646423 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:52-646600 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:52-646791 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:52-647060 cadet-p2p-8620 INFO snd {               ACK} ( 70) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:52-647254 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:52-647435 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:52-647641 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:52-647816 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:52-647998 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:52-648172 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:52-648354 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:52-648553 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:52-648728 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:52-648902 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:52-649099 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:52-649322 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:52-649509 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:52-649687 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:52-649877 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:52-650123 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:54-493047 util-scheduler-8620 DEBUG Checking readiness of task: 2681 / 0x46620a0
Jul 07 20:47:54-493442 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:54-496804 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:54-497027 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:54-497249 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:54-497442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:54-497633 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:54-497824 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:54-498018 util-scheduler-8620 DEBUG Running task: 2661 / 0x52cbfb8
Jul 07 20:47:54-498253 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:54-498499 cadet-tun-8620 DEBUG  kx started 30 s ago
Jul 07 20:47:54-498705 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:54-498904 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:54-499105 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:54-499339 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:54-499520 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:54-499741 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:54-500031 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:54-500228 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:54-500464 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:54-500671 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:54-500984 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:54-501185 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:54-501434 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:54-501618 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:54-501793 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:54-501998 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:54-502214 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:54-502437 util-scheduler-8620 DEBUG Adding task: 2682 / 0x4d6ff98
Jul 07 20:47:54-502617 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:54-502820 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:54-502999 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:54-503174 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:54-503411 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:54-503607 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:54-503783 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:54-504008 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:54-504252 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:54-504450 util-scheduler-8620 DEBUG Adding task: 2683 / 0x52cbfb8
Jul 07 20:47:54-504713 util-scheduler-8620 DEBUG Checking readiness of task: 2681 / 0x46620a0
Jul 07 20:47:54-504907 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:54-505098 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:54-505311 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:54-505502 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:54-505691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:54-505879 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:54-506067 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:54-506269 util-scheduler-8620 DEBUG Running task: 2682 / 0x4d6ff98
Jul 07 20:47:54-506477 util-scheduler-8620 DEBUG Adding task: 2684 / 0x4d6ff98
Jul 07 20:47:54-506699 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:54-506901 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:54-507109 util-scheduler-8620 DEBUG Adding task: 2685 / 0x46620a0
Jul 07 20:47:54-507352 util-scheduler-8620 DEBUG Checking readiness of task: 2685 / 0x46620a0
Jul 07 20:47:54-507546 util-scheduler-8620 DEBUG Checking readiness of task: 2681 / 0x46620a0
Jul 07 20:47:54-507736 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:54-507925 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:54-508114 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:54-508303 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:54-508491 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:54-508679 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:54-508868 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:54-509058 util-scheduler-8620 DEBUG Running task: 2685 / 0x46620a0
Jul 07 20:47:54-509265 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:54-509443 util-8620 DEBUG process_notify is running
Jul 07 20:47:54-509616 util-8620 DEBUG client_notify is running
Jul 07 20:47:54-509794 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:54-509992 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:54-510189 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:54-510443 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:56-337257 util-scheduler-8620 DEBUG Checking readiness of task: 2681 / 0x46620a0
Jul 07 20:47:56-337639 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-337837 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-338030 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:56-338221 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-338442 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-338653 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-338845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-339050 util-scheduler-8620 DEBUG Running task: 2681 / 0x46620a0
Jul 07 20:47:56-339473 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:56-339730 util-scheduler-8620 DEBUG Adding task: 2686 / 0x4662248
Jul 07 20:47:56-340009 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-340233 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-340425 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:56-340616 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-340805 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-340995 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-341186 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-341416 util-scheduler-8620 DEBUG Running task: 2686 / 0x4662248
Jul 07 20:47:56-341736 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:47:56-342046 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:47:56-342819 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:47:56-343088 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:47:56-343334 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:47:56-343564 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:56-343776 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:56-343972 cadet-con-8620 DEBUG  PID 7 (expected 7+)
Jul 07 20:47:56-344152 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:47:56-344344 util-scheduler-8620 DEBUG Canceling task: 2672 / 0x52cba38
Jul 07 20:47:56-344570 util-scheduler-8620 DEBUG Adding task: 2687 / 0x52cba38
Jul 07 20:47:56-344750 cadet-con-8620 DEBUG   message for us!
Jul 07 20:47:56-345011 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:56-345249 util-scheduler-8620 DEBUG Adding task: 2688 / 0x4d5e5d8
Jul 07 20:47:56-345435 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:56-345604 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:56-349131 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:56-349904 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:56-350113 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:47:56-353324 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:47:56-353515 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:47:56-356484 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:47:56-357040 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:47:56-357252 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:47:56-360362 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:47:56-360611 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:47:56-360854 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:47:56-361031 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:47:56-361227 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:47:56-361400 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:47:56-361621 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:47:56-361799 cadet-con-8620 DEBUG  ACK 71
Jul 07 20:47:56-361978 cadet-con-8620 DEBUG  last pid 7, last ack 70, qmax 11, q 0
Jul 07 20:47:56-362248 cadet-con-8620 INFO --> {               ACK} ( 71) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:47:56-362440 cadet-con-8620 DEBUG  ack 71
Jul 07 20:47:56-362619 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:47:56-362852 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:56-363057 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:56-363367 cadet-p2p-8620 INFO que {               ACK} ( 71) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:47:56-363566 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:47:56-363790 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:56-363973 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:56-364149 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:56-364350 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:47:56-364551 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:56-364752 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:56-364928 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:56-365167 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:56-365371 cadet-p2p-8620 DEBUG QQQ    payload , 71
Jul 07 20:47:56-365547 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:47:56-365782 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:56-365975 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:56-366151 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:56-366351 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:56-366535 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:56-366746 util-scheduler-8620 DEBUG Adding task: 2689 / 0x46620a0
Jul 07 20:47:56-367016 util-scheduler-8620 DEBUG Checking readiness of task: 2689 / 0x46620a0
Jul 07 20:47:56-367213 util-scheduler-8620 DEBUG Checking readiness of task: 2688 / 0x4d5e5d8
Jul 07 20:47:56-367405 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-367596 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-367785 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:56-367975 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-368165 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-368353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-368542 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-368734 util-scheduler-8620 DEBUG Running task: 2688 / 0x4d5e5d8
Jul 07 20:47:56-368920 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:56-369108 util-8620 DEBUG process_notify is running
Jul 07 20:47:56-369306 util-8620 DEBUG client_notify is running
Jul 07 20:47:56-369549 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:47:56-369758 util-scheduler-8620 DEBUG Adding task: 2690 / 0x4d5e5d8
Jul 07 20:47:56-369960 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:47:56-370222 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:56-370421 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:47:56-370662 util-scheduler-8620 DEBUG Checking readiness of task: 2690 / 0x4d5e5d8
Jul 07 20:47:56-370857 util-scheduler-8620 DEBUG Checking readiness of task: 2689 / 0x46620a0
Jul 07 20:47:56-371048 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-371241 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-371432 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:56-371622 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-371811 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-372000 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-372188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-372378 util-scheduler-8620 DEBUG Running task: 2690 / 0x4d5e5d8
Jul 07 20:47:56-372561 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:47:56-372736 util-8620 DEBUG process_notify is running
Jul 07 20:47:56-372905 util-8620 DEBUG client_notify is running
Jul 07 20:47:56-373115 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:47:56-373392 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:47:56-845140 util-scheduler-8620 DEBUG Checking readiness of task: 2689 / 0x46620a0
Jul 07 20:47:56-845491 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-845688 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-845908 util-scheduler-8620 DEBUG Checking readiness of task: 1634 / 0x465ee60
Jul 07 20:47:56-846105 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-846298 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-846489 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-846679 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-846873 util-scheduler-8620 DEBUG Running task: 1634 / 0x465ee60
Jul 07 20:47:56-847294 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:47:56-847547 util-scheduler-8620 DEBUG Adding task: 2691 / 0x465f008
Jul 07 20:47:56-847817 util-scheduler-8620 DEBUG Checking readiness of task: 2689 / 0x46620a0
Jul 07 20:47:56-848010 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:56-848200 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:56-848390 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:56-848579 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:56-848769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:56-848957 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:56-849146 util-scheduler-8620 DEBUG Running task: 2691 / 0x465f008
Jul 07 20:47:56-849365 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:47:56-849602 nse-api-8620 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 20:47:56-849890 cadet-hll-8620 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 08:47:56 2014
Jul 07 20:47:56-850114 cadet-p2p-8620 DEBUG set hello for STRN
Jul 07 20:47:56-850412 cadet-p2p-8620 DEBUG  merge into 0x5901998 (90 bytes)
Jul 07 20:47:56-850608 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:56-850819 util-scheduler-8620 DEBUG Adding task: 2692 / 0x465ee60
Jul 07 20:47:57-694160 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:57-694548 util-scheduler-8620 DEBUG Checking readiness of task: 2689 / 0x46620a0
Jul 07 20:47:57-694755 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:57-694949 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:57-695141 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:57-695333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:57-695523 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:57-695713 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:57-695908 util-scheduler-8620 DEBUG Running task: 2689 / 0x46620a0
Jul 07 20:47:57-696339 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:57-696593 util-scheduler-8620 DEBUG Adding task: 2693 / 0x4662248
Jul 07 20:47:57-696869 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:57-697061 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:57-697280 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:57-697472 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:57-697662 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:57-697852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:57-698041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:57-698230 util-scheduler-8620 DEBUG Running task: 2693 / 0x4662248
Jul 07 20:47:57-698420 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:57-698619 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:57-698876 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:57-699082 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:57-699288 util-scheduler-8620 DEBUG Adding task: 2694 / 0x46620a0
Jul 07 20:47:57-699475 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:57-699681 util-scheduler-8620 DEBUG Adding task: 2695 / 0x46620a0
Jul 07 20:47:57-699936 util-scheduler-8620 DEBUG Checking readiness of task: 2695 / 0x46620a0
Jul 07 20:47:57-700128 util-scheduler-8620 DEBUG Checking readiness of task: 2694 / 0x46620a0
Jul 07 20:47:57-700319 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:57-700509 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:57-700699 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:57-700889 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:57-701077 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:57-701310 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:57-701500 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:57-701691 util-scheduler-8620 DEBUG Running task: 2694 / 0x46620a0
Jul 07 20:47:57-701875 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:57-702052 util-8620 DEBUG process_notify is running
Jul 07 20:47:57-702223 util-8620 DEBUG client_notify is running
Jul 07 20:47:57-702412 util-scheduler-8620 DEBUG Canceling task: 2684 / 0x4d6ff98
Jul 07 20:47:57-702635 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:57-702855 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:57-703093 cadet-p2p-8620 DEBUG Checking 0x58f8b58 towards NCSKBW46 (->V8XX)
Jul 07 20:47:57-703326 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:57-703503 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:47:57-703693 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:47:57-703965 cadet-p2p-8620 INFO snd {               ACK} ( 71) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:47:57-704159 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:57-704338 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:57-704526 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:47:57-704699 cadet-con-8620 DEBUG  calling cont
Jul 07 20:47:57-704882 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:47:57-705056 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:57-705348 cadet-p2p-8620 DEBUG Checking 0x58eb1e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:57-705588 cadet-p2p-8620 DEBUG Checking 0x58eb1e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:57-705766 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:47:57-705973 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:57-706186 util-scheduler-8620 DEBUG Adding task: 2696 / 0x4d6ff98
Jul 07 20:47:57-706364 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:57-706540 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:47:57-706739 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:57-706913 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:57-707088 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:57-707327 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:57-707522 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:57-707699 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:57-707897 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:57-708100 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:47:57-708282 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:47:57-708485 util-scheduler-8620 DEBUG Adding task: 2697 / 0x4d6ff98
Jul 07 20:47:57-708705 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:57-708899 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:57-709118 util-scheduler-8620 DEBUG Adding task: 2698 / 0x46620a0
Jul 07 20:47:57-709349 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:47:57-709601 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:57-709797 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:47:57-710043 util-scheduler-8620 DEBUG Checking readiness of task: 2698 / 0x46620a0
Jul 07 20:47:57-710237 util-scheduler-8620 DEBUG Checking readiness of task: 2695 / 0x46620a0
Jul 07 20:47:57-710427 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:57-710617 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:57-710807 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:57-710996 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:57-711185 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:57-711374 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:57-711562 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:57-711752 util-scheduler-8620 DEBUG Running task: 2698 / 0x46620a0
Jul 07 20:47:57-711936 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:57-712111 util-8620 DEBUG process_notify is running
Jul 07 20:47:57-712281 util-8620 DEBUG client_notify is running
Jul 07 20:47:57-712457 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:57-712651 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:57-712839 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:57-713080 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:57-713312 util-scheduler-8620 DEBUG Running task: 2696 / 0x4d6ff98
Jul 07 20:47:57-713504 util-scheduler-8620 DEBUG Canceling task: 2697 / 0x4d6ff98
Jul 07 20:47:57-713716 util-scheduler-8620 DEBUG Adding task: 2699 / 0x4d6ff98
Jul 07 20:47:57-713935 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:57-714128 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:57-714325 util-scheduler-8620 DEBUG Adding task: 2700 / 0x46620a0
Jul 07 20:47:57-714563 util-scheduler-8620 DEBUG Checking readiness of task: 2700 / 0x46620a0
Jul 07 20:47:57-714755 util-scheduler-8620 DEBUG Checking readiness of task: 2695 / 0x46620a0
Jul 07 20:47:57-714945 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:57-715135 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:57-715324 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:57-715514 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:57-715703 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:57-715892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:57-716081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:57-716270 util-scheduler-8620 DEBUG Running task: 2700 / 0x46620a0
Jul 07 20:47:57-716454 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:57-716628 util-8620 DEBUG process_notify is running
Jul 07 20:47:57-716797 util-8620 DEBUG client_notify is running
Jul 07 20:47:57-716973 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:57-717161 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:57-717374 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:57-717614 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:58-832645 util-scheduler-8620 DEBUG Checking readiness of task: 2695 / 0x46620a0
Jul 07 20:47:58-833034 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:58-833259 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:58-833455 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:58-833648 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:58-833839 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:58-834030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:58-834220 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:58-834416 util-scheduler-8620 DEBUG Running task: 2695 / 0x46620a0
Jul 07 20:47:58-834837 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:47:58-835092 util-scheduler-8620 DEBUG Adding task: 2701 / 0x4662248
Jul 07 20:47:58-835371 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:58-835564 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:58-835755 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:58-835945 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:58-836148 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:58-836337 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:58-836526 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:58-836716 util-scheduler-8620 DEBUG Running task: 2701 / 0x4662248
Jul 07 20:47:58-836907 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:47:58-837105 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:47:58-837360 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:47:58-837565 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:58-837772 util-scheduler-8620 DEBUG Adding task: 2702 / 0x46620a0
Jul 07 20:47:58-837959 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:47:58-838165 util-scheduler-8620 DEBUG Adding task: 2703 / 0x46620a0
Jul 07 20:47:58-838409 util-scheduler-8620 DEBUG Checking readiness of task: 2703 / 0x46620a0
Jul 07 20:47:58-838601 util-scheduler-8620 DEBUG Checking readiness of task: 2702 / 0x46620a0
Jul 07 20:47:58-838793 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:58-838984 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:58-839174 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:58-839364 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:58-839554 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:58-839743 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:58-839932 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:58-840126 util-scheduler-8620 DEBUG Running task: 2702 / 0x46620a0
Jul 07 20:47:58-840311 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:58-840490 util-8620 DEBUG process_notify is running
Jul 07 20:47:58-840662 util-8620 DEBUG client_notify is running
Jul 07 20:47:58-840850 util-scheduler-8620 DEBUG Canceling task: 2699 / 0x4d6ff98
Jul 07 20:47:58-841080 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:47:58-841323 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:47:58-841563 cadet-p2p-8620 DEBUG Checking 0x58eb1e8 towards NCSKBW46 (->V8XX)
Jul 07 20:47:58-841797 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:47:58-841974 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:47:58-842165 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:47:58-842450 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:47:58-842663 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:47:58-842845 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:47:58-843034 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:47:58-843223 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:47:58-843400 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:47:58-843586 util-scheduler-8620 DEBUG Canceling task: 2667 / 0x52cba38
Jul 07 20:47:58-843799 util-scheduler-8620 DEBUG Adding task: 2704 / 0x52cba38
Jul 07 20:47:58-844049 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:47:58-844220 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:47:58-844400 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:47:58-844605 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:58-844779 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:47:58-844954 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:47:58-845154 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:58-845383 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:47:58-845566 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:47:58-845745 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:58-845936 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:47:58-846184 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:47:59-505270 util-scheduler-8620 DEBUG Checking readiness of task: 2703 / 0x46620a0
Jul 07 20:47:59-505603 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:59-510793 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:59-511014 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:59-511212 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:59-511405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:59-511596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:59-511787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:59-511980 util-scheduler-8620 DEBUG Running task: 2683 / 0x52cbfb8
Jul 07 20:47:59-512213 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:47:59-512459 cadet-tun-8620 DEBUG  kx started 35 s ago
Jul 07 20:47:59-512666 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:47:59-512866 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:47:59-513069 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:47:59-513328 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:47:59-513509 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:47:59-513731 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:47:59-514019 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:47:59-514215 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:47:59-514451 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:47:59-514659 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:47:59-514973 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:47:59-515173 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:47:59-515399 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:47:59-515582 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:47:59-515758 cadet-con-8620 DEBUG  sendable
Jul 07 20:47:59-515964 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:47:59-516178 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:47:59-516401 util-scheduler-8620 DEBUG Adding task: 2705 / 0x4d6ff98
Jul 07 20:47:59-516581 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:47:59-516810 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:47:59-516988 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:47:59-517164 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:47:59-517427 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:47:59-517623 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:47:59-517800 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:47:59-517999 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:47:59-518244 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:47:59-518441 util-scheduler-8620 DEBUG Adding task: 2706 / 0x52cbfb8
Jul 07 20:47:59-518700 util-scheduler-8620 DEBUG Checking readiness of task: 2703 / 0x46620a0
Jul 07 20:47:59-518893 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:59-519084 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:59-519274 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:59-519464 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:59-519653 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:59-519842 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:59-520031 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:59-520223 util-scheduler-8620 DEBUG Running task: 2705 / 0x4d6ff98
Jul 07 20:47:59-520430 util-scheduler-8620 DEBUG Adding task: 2707 / 0x4d6ff98
Jul 07 20:47:59-520650 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:47:59-520851 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:47:59-521059 util-scheduler-8620 DEBUG Adding task: 2708 / 0x46620a0
Jul 07 20:47:59-521340 util-scheduler-8620 DEBUG Checking readiness of task: 2708 / 0x46620a0
Jul 07 20:47:59-521533 util-scheduler-8620 DEBUG Checking readiness of task: 2703 / 0x46620a0
Jul 07 20:47:59-521724 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:47:59-521913 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:47:59-522103 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:47:59-522293 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:47:59-522482 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:47:59-522671 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:47:59-522860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:47:59-523052 util-scheduler-8620 DEBUG Running task: 2708 / 0x46620a0
Jul 07 20:47:59-523236 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:47:59-523415 util-8620 DEBUG process_notify is running
Jul 07 20:47:59-523587 util-8620 DEBUG client_notify is running
Jul 07 20:47:59-523765 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:47:59-523960 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:47:59-524149 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:47:59-524404 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:00-865029 util-scheduler-8620 DEBUG Checking readiness of task: 2703 / 0x46620a0
Jul 07 20:48:00-865413 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:00-865614 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:00-865809 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:00-866003 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:00-866195 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:00-866386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:00-866576 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:00-866800 util-scheduler-8620 DEBUG Running task: 2703 / 0x46620a0
Jul 07 20:48:00-867224 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:00-867476 util-scheduler-8620 DEBUG Adding task: 2709 / 0x4662248
Jul 07 20:48:00-867750 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:00-867942 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:00-868133 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:00-868323 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:00-868513 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:00-868702 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:00-868891 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:00-869081 util-scheduler-8620 DEBUG Running task: 2709 / 0x4662248
Jul 07 20:48:00-869298 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:48:00-869498 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:48:00-869728 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:48:00-869991 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:48:00-870236 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:48:00-870464 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:00-870673 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:00-870868 cadet-con-8620 DEBUG  PID 8 (expected 8+)
Jul 07 20:48:00-871048 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:00-871235 util-scheduler-8620 DEBUG Canceling task: 2687 / 0x52cba38
Jul 07 20:48:00-871456 util-scheduler-8620 DEBUG Adding task: 2710 / 0x52cba38
Jul 07 20:48:00-871638 cadet-con-8620 DEBUG   message for us!
Jul 07 20:48:00-871897 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:00-872112 util-scheduler-8620 DEBUG Adding task: 2711 / 0x4d5e5d8
Jul 07 20:48:00-872296 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:00-872465 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:00-876025 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:00-877315 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:00-877515 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:48:00-880623 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:00-880799 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:00-883782 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:00-884434 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:00-884641 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:48:00-887818 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:48:00-888065 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:48:00-888308 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:48:00-888486 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:48:00-888659 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:48:00-888830 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:48:00-889050 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:48:00-889253 cadet-con-8620 DEBUG  ACK 72
Jul 07 20:48:00-889435 cadet-con-8620 DEBUG  last pid 8, last ack 71, qmax 11, q 0
Jul 07 20:48:00-889703 cadet-con-8620 INFO --> {               ACK} ( 72) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:48:00-889894 cadet-con-8620 DEBUG  ack 72
Jul 07 20:48:00-890075 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:48:00-890309 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:00-890515 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:00-890810 cadet-p2p-8620 INFO que {               ACK} ( 72) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:48:00-891010 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:48:00-891257 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:00-891441 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:00-891633 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:00-891834 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:48:00-892037 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:00-892213 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:00-892387 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:00-892623 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:00-892807 cadet-p2p-8620 DEBUG QQQ    payload , 72
Jul 07 20:48:00-892982 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:48:00-893241 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:00-893437 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:00-893613 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:00-893811 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:00-893995 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:00-894206 util-scheduler-8620 DEBUG Adding task: 2712 / 0x46620a0
Jul 07 20:48:00-894477 util-scheduler-8620 DEBUG Checking readiness of task: 2712 / 0x46620a0
Jul 07 20:48:00-894675 util-scheduler-8620 DEBUG Checking readiness of task: 2711 / 0x4d5e5d8
Jul 07 20:48:00-894868 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:00-895060 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:00-895251 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:00-895442 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:00-895631 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:00-895820 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:00-896008 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:00-896201 util-scheduler-8620 DEBUG Running task: 2711 / 0x4d5e5d8
Jul 07 20:48:00-896387 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:00-896566 util-8620 DEBUG process_notify is running
Jul 07 20:48:00-896738 util-8620 DEBUG client_notify is running
Jul 07 20:48:00-896980 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:00-897187 util-scheduler-8620 DEBUG Adding task: 2713 / 0x4d5e5d8
Jul 07 20:48:00-897415 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:48:00-897670 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:00-897870 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:00-898113 util-scheduler-8620 DEBUG Checking readiness of task: 2713 / 0x4d5e5d8
Jul 07 20:48:00-898306 util-scheduler-8620 DEBUG Checking readiness of task: 2712 / 0x46620a0
Jul 07 20:48:00-898497 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:00-898686 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:00-898876 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:00-899066 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:00-899255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:00-899444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:00-899633 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:00-899823 util-scheduler-8620 DEBUG Running task: 2713 / 0x4d5e5d8
Jul 07 20:48:00-900006 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:00-900180 util-8620 DEBUG process_notify is running
Jul 07 20:48:00-900349 util-8620 DEBUG client_notify is running
Jul 07 20:48:00-900558 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:48:00-900820 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:01-531291 util-scheduler-8620 DEBUG Checking readiness of task: 2712 / 0x46620a0
Jul 07 20:48:01-531596 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:01-531795 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:01-531987 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:01-532180 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:01-532371 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:01-532563 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:01-532754 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:01-532951 util-scheduler-8620 DEBUG Running task: 2712 / 0x46620a0
Jul 07 20:48:01-533393 util-8620 DEBUG receive_ready read 144/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:01-533643 util-scheduler-8620 DEBUG Adding task: 2714 / 0x4662248
Jul 07 20:48:01-533911 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:01-534105 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:01-534296 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:01-534486 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:01-534676 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:01-534867 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:01-535056 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:01-535246 util-scheduler-8620 DEBUG Running task: 2714 / 0x4662248
Jul 07 20:48:01-535437 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:48:01-535637 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:48:01-535860 core-api-8620 DEBUG Received message of type 266 and size 36 from peer `D3TJ'
Jul 07 20:48:01-536116 cadet-con-8620 INFO <-- {CONNECTION_DESTROY} on connection 1KSG9GE2 from D3TJ
Jul 07 20:48:01-536738 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:01-536972 util-scheduler-8620 DEBUG Adding task: 2715 / 0x4d5e5d8
Jul 07 20:48:01-537961 cadet-con-8620 DEBUG   connection unknown: already destroyed?
Jul 07 20:48:01-538378 util-scheduler-8620 DEBUG Adding task: 2716 / 0x4662248
Jul 07 20:48:01-538637 util-scheduler-8620 DEBUG Checking readiness of task: 2715 / 0x4d5e5d8
Jul 07 20:48:01-538836 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:01-539030 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:01-539223 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:01-539415 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:01-539604 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:01-539794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:01-539982 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:01-540176 util-scheduler-8620 DEBUG Running task: 2715 / 0x4d5e5d8
Jul 07 20:48:01-540367 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:01-540570 util-8620 DEBUG process_notify is running
Jul 07 20:48:01-540743 util-8620 DEBUG client_notify is running
Jul 07 20:48:01-540970 util-8620 DEBUG Transmitting message of type 168 and size 54 to statistics service.
Jul 07 20:48:01-541241 util-8620 DEBUG Connection transmitted 54/54 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:01-541455 util-scheduler-8620 DEBUG Running task: 2716 / 0x4662248
Jul 07 20:48:01-541648 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:48:01-541870 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:48:01-542093 core-api-8620 DEBUG Received message of type 266 and size 36 from peer `D3TJ'
Jul 07 20:48:01-542339 cadet-con-8620 INFO <-- {CONNECTION_DESTROY} on connection BFARXZN9 from D3TJ
Jul 07 20:48:01-542592 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:01-542800 util-scheduler-8620 DEBUG Adding task: 2717 / 0x4d5e5d8
Jul 07 20:48:01-543091 cadet-con-8620 DEBUG   connection unknown: already destroyed?
Jul 07 20:48:01-543274 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:01-543490 util-scheduler-8620 DEBUG Adding task: 2718 / 0x46620a0
Jul 07 20:48:01-543748 util-scheduler-8620 DEBUG Checking readiness of task: 2718 / 0x46620a0
Jul 07 20:48:01-543944 util-scheduler-8620 DEBUG Checking readiness of task: 2717 / 0x4d5e5d8
Jul 07 20:48:01-544138 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:01-544329 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:01-544520 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:01-544710 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:01-544919 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:01-545109 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:01-545321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:01-545515 util-scheduler-8620 DEBUG Running task: 2717 / 0x4d5e5d8
Jul 07 20:48:01-545699 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:01-545874 util-8620 DEBUG process_notify is running
Jul 07 20:48:01-546045 util-8620 DEBUG client_notify is running
Jul 07 20:48:01-546260 util-8620 DEBUG Transmitting message of type 168 and size 54 to statistics service.
Jul 07 20:48:01-546506 util-8620 DEBUG Connection transmitted 54/54 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:03-324187 util-scheduler-8620 DEBUG Checking readiness of task: 2718 / 0x46620a0
Jul 07 20:48:03-324549 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:03-324747 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:03-324940 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:03-325132 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:03-325346 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:03-325537 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:03-325727 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:03-325923 util-scheduler-8620 DEBUG Running task: 2718 / 0x46620a0
Jul 07 20:48:03-326342 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:03-326594 util-scheduler-8620 DEBUG Adding task: 2719 / 0x4662248
Jul 07 20:48:03-326869 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:03-327063 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:03-327254 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:03-327445 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:03-327635 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:03-327824 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:03-328014 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:03-328204 util-scheduler-8620 DEBUG Running task: 2719 / 0x4662248
Jul 07 20:48:03-328395 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:03-328594 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:03-328853 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:03-329059 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:03-329285 util-scheduler-8620 DEBUG Adding task: 2720 / 0x46620a0
Jul 07 20:48:03-329473 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:03-329677 util-scheduler-8620 DEBUG Adding task: 2721 / 0x46620a0
Jul 07 20:48:03-329920 util-scheduler-8620 DEBUG Checking readiness of task: 2721 / 0x46620a0
Jul 07 20:48:03-330113 util-scheduler-8620 DEBUG Checking readiness of task: 2720 / 0x46620a0
Jul 07 20:48:03-330306 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:03-330496 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:03-330687 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:03-330877 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:03-331066 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:03-331255 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:03-331444 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:03-331635 util-scheduler-8620 DEBUG Running task: 2720 / 0x46620a0
Jul 07 20:48:03-331820 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:03-331998 util-8620 DEBUG process_notify is running
Jul 07 20:48:03-332172 util-8620 DEBUG client_notify is running
Jul 07 20:48:03-332360 util-scheduler-8620 DEBUG Canceling task: 2707 / 0x4d6ff98
Jul 07 20:48:03-332585 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:03-332806 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:03-333046 cadet-p2p-8620 DEBUG Checking 0x5920ba0 towards NCSKBW46 (->V8XX)
Jul 07 20:48:03-333301 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:03-333480 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:48:03-333673 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:48:03-333942 cadet-p2p-8620 INFO snd {               ACK} ( 72) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:48:03-334138 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:03-334318 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:03-334507 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:48:03-334682 cadet-con-8620 DEBUG  calling cont
Jul 07 20:48:03-334864 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:48:03-335039 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:03-335261 cadet-p2p-8620 DEBUG Checking 0x58f3790 towards NCSKBW46 (->V8XX)
Jul 07 20:48:03-335499 cadet-p2p-8620 DEBUG Checking 0x58f3790 towards NCSKBW46 (->V8XX)
Jul 07 20:48:03-335678 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:48:03-335886 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:03-336097 util-scheduler-8620 DEBUG Adding task: 2722 / 0x4d6ff98
Jul 07 20:48:03-336277 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:03-336454 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:48:03-336652 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:03-336828 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:03-337003 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:03-337261 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:03-337458 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:03-337636 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:03-337835 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:03-338039 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:48:03-338222 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:48:03-338424 util-scheduler-8620 DEBUG Adding task: 2723 / 0x4d6ff98
Jul 07 20:48:03-338643 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:03-338838 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:03-339054 util-scheduler-8620 DEBUG Adding task: 2724 / 0x46620a0
Jul 07 20:48:03-339257 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:48:03-339505 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:03-339701 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:48:03-339945 util-scheduler-8620 DEBUG Checking readiness of task: 2724 / 0x46620a0
Jul 07 20:48:03-340140 util-scheduler-8620 DEBUG Checking readiness of task: 2721 / 0x46620a0
Jul 07 20:48:03-340331 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:03-340521 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:03-340711 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:03-340902 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:03-341092 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:03-341301 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:03-341490 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:03-341681 util-scheduler-8620 DEBUG Running task: 2724 / 0x46620a0
Jul 07 20:48:03-341865 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:03-342041 util-8620 DEBUG process_notify is running
Jul 07 20:48:03-342213 util-8620 DEBUG client_notify is running
Jul 07 20:48:03-342392 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:03-342587 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:03-342776 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:03-343016 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:03-343222 util-scheduler-8620 DEBUG Running task: 2722 / 0x4d6ff98
Jul 07 20:48:03-343414 util-scheduler-8620 DEBUG Canceling task: 2723 / 0x4d6ff98
Jul 07 20:48:03-343628 util-scheduler-8620 DEBUG Adding task: 2725 / 0x4d6ff98
Jul 07 20:48:03-343856 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:03-344051 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:03-344248 util-scheduler-8620 DEBUG Adding task: 2726 / 0x46620a0
Jul 07 20:48:03-344487 util-scheduler-8620 DEBUG Checking readiness of task: 2726 / 0x46620a0
Jul 07 20:48:03-344680 util-scheduler-8620 DEBUG Checking readiness of task: 2721 / 0x46620a0
Jul 07 20:48:03-344871 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:03-345060 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:03-345270 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:03-345461 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:03-345650 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:03-345839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:03-346029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:03-346219 util-scheduler-8620 DEBUG Running task: 2726 / 0x46620a0
Jul 07 20:48:03-346402 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:03-346577 util-8620 DEBUG process_notify is running
Jul 07 20:48:03-346746 util-8620 DEBUG client_notify is running
Jul 07 20:48:03-346922 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:03-347110 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:03-347299 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:03-347538 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:04-519746 util-scheduler-8620 DEBUG Checking readiness of task: 2721 / 0x46620a0
Jul 07 20:48:04-520081 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-522802 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-523020 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-523217 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-523410 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-523600 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-523791 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-523984 util-scheduler-8620 DEBUG Running task: 2706 / 0x52cbfb8
Jul 07 20:48:04-524216 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:04-524461 cadet-tun-8620 DEBUG  kx started 40 s ago
Jul 07 20:48:04-524668 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:04-524868 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:04-525071 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:04-525333 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:04-525514 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:04-525738 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:04-526028 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:04-526226 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:48:04-526463 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:04-526671 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:04-526986 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:04-527187 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:04-527412 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:04-527596 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:04-527771 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:04-527976 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:48:04-528179 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:04-528357 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:48:04-528532 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:04-528770 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:04-528966 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:04-529143 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:04-529400 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:04-529594 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:04-529771 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:04-529969 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:04-530212 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:04-530416 util-scheduler-8620 DEBUG Adding task: 2727 / 0x52cbfb8
Jul 07 20:48:04-680884 util-scheduler-8620 DEBUG Checking readiness of task: 2721 / 0x46620a0
Jul 07 20:48:04-681214 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-681413 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-681606 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-681798 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-681989 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-682180 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-682369 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-682563 util-scheduler-8620 DEBUG Running task: 2721 / 0x46620a0
Jul 07 20:48:04-682979 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:04-683255 util-scheduler-8620 DEBUG Adding task: 2728 / 0x4662248
Jul 07 20:48:04-683520 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-683714 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-683905 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-684096 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-684286 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-684477 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-684666 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-684856 util-scheduler-8620 DEBUG Running task: 2728 / 0x4662248
Jul 07 20:48:04-685046 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:04-685267 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:04-685495 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:04-685700 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:04-685908 util-scheduler-8620 DEBUG Adding task: 2729 / 0x46620a0
Jul 07 20:48:04-686097 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:04-686302 util-scheduler-8620 DEBUG Adding task: 2730 / 0x46620a0
Jul 07 20:48:04-686545 util-scheduler-8620 DEBUG Checking readiness of task: 2730 / 0x46620a0
Jul 07 20:48:04-686737 util-scheduler-8620 DEBUG Checking readiness of task: 2729 / 0x46620a0
Jul 07 20:48:04-686929 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-687119 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-687309 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-687498 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-687689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-687882 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-688071 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-688262 util-scheduler-8620 DEBUG Running task: 2729 / 0x46620a0
Jul 07 20:48:04-688447 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:04-688625 util-8620 DEBUG process_notify is running
Jul 07 20:48:04-688797 util-8620 DEBUG client_notify is running
Jul 07 20:48:04-688985 util-scheduler-8620 DEBUG Canceling task: 2725 / 0x4d6ff98
Jul 07 20:48:04-689232 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:04-689453 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:04-689690 cadet-p2p-8620 DEBUG Checking 0x58f3790 towards NCSKBW46 (->V8XX)
Jul 07 20:48:04-689924 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:04-690115 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:04-690305 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:04-690589 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:04-690785 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:04-690966 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:04-691154 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:04-691343 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:48:04-691521 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:04-691707 util-scheduler-8620 DEBUG Canceling task: 2704 / 0x52cba38
Jul 07 20:48:04-691918 util-scheduler-8620 DEBUG Adding task: 2731 / 0x52cba38
Jul 07 20:48:04-692181 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:04-692353 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:04-692574 cadet-p2p-8620 DEBUG Checking 0x5926a68 towards NCSKBW46 (->V8XX)
Jul 07 20:48:04-692813 cadet-p2p-8620 DEBUG Checking 0x5926a68 towards NCSKBW46 (->V8XX)
Jul 07 20:48:04-693009 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:48:04-693239 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:04-693453 util-scheduler-8620 DEBUG Adding task: 2732 / 0x4d6ff98
Jul 07 20:48:04-693633 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:04-693812 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:04-694011 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:04-694186 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:04-694361 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:04-694599 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:04-694794 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:04-694971 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:04-695170 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:04-695375 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:04-695559 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:04-695763 util-scheduler-8620 DEBUG Adding task: 2733 / 0x4d6ff98
Jul 07 20:48:04-695981 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:04-696177 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:04-696377 util-scheduler-8620 DEBUG Adding task: 2734 / 0x46620a0
Jul 07 20:48:04-696576 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:04-696827 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:04-697025 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:48:04-697494 util-scheduler-8620 DEBUG Checking readiness of task: 2734 / 0x46620a0
Jul 07 20:48:04-697697 util-scheduler-8620 DEBUG Checking readiness of task: 2730 / 0x46620a0
Jul 07 20:48:04-697891 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-698084 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-698275 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-698466 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-698656 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-698846 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-699037 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-699229 util-scheduler-8620 DEBUG Running task: 2734 / 0x46620a0
Jul 07 20:48:04-699414 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:04-699592 util-8620 DEBUG process_notify is running
Jul 07 20:48:04-699765 util-8620 DEBUG client_notify is running
Jul 07 20:48:04-699943 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:04-700139 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:04-700329 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:04-700563 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:04-700771 util-scheduler-8620 DEBUG Running task: 2732 / 0x4d6ff98
Jul 07 20:48:04-700964 util-scheduler-8620 DEBUG Canceling task: 2733 / 0x4d6ff98
Jul 07 20:48:04-701182 util-scheduler-8620 DEBUG Adding task: 2735 / 0x4d6ff98
Jul 07 20:48:04-701425 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:04-701622 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:04-701821 util-scheduler-8620 DEBUG Adding task: 2736 / 0x46620a0
Jul 07 20:48:04-702062 util-scheduler-8620 DEBUG Checking readiness of task: 2736 / 0x46620a0
Jul 07 20:48:04-702257 util-scheduler-8620 DEBUG Checking readiness of task: 2730 / 0x46620a0
Jul 07 20:48:04-702447 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-702652 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-702843 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-703033 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-703224 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-703412 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-703601 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-703792 util-scheduler-8620 DEBUG Running task: 2730 / 0x46620a0
Jul 07 20:48:04-704195 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:04-704419 util-scheduler-8620 DEBUG Adding task: 2737 / 0x4662248
Jul 07 20:48:04-704628 util-scheduler-8620 DEBUG Running task: 2736 / 0x46620a0
Jul 07 20:48:04-704814 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:04-704989 util-8620 DEBUG process_notify is running
Jul 07 20:48:04-705158 util-8620 DEBUG client_notify is running
Jul 07 20:48:04-705358 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:04-705549 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:04-705741 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:04-705982 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:04-706226 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-706420 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-706610 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-706801 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-706989 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-707178 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-707367 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-707557 util-scheduler-8620 DEBUG Running task: 2737 / 0x4662248
Jul 07 20:48:04-707746 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:04-707940 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:04-708152 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:04-708332 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:04-708533 util-scheduler-8620 DEBUG Adding task: 2738 / 0x46620a0
Jul 07 20:48:04-708771 util-scheduler-8620 DEBUG Checking readiness of task: 2738 / 0x46620a0
Jul 07 20:48:04-708965 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-709156 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-709369 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-709560 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-709749 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-709939 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-710128 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-710318 util-scheduler-8620 DEBUG Running task: 2738 / 0x46620a0
Jul 07 20:48:04-710719 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:04-710939 util-scheduler-8620 DEBUG Adding task: 2739 / 0x4662248
Jul 07 20:48:04-711185 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-711378 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-711580 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-711788 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-711979 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-712167 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-712357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-712546 util-scheduler-8620 DEBUG Running task: 2739 / 0x4662248
Jul 07 20:48:04-712735 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:04-712926 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:04-713136 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:04-713355 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:04-713551 util-scheduler-8620 DEBUG Adding task: 2740 / 0x46620a0
Jul 07 20:48:04-713734 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:04-713930 util-scheduler-8620 DEBUG Adding task: 2741 / 0x46620a0
Jul 07 20:48:04-714168 util-scheduler-8620 DEBUG Checking readiness of task: 2741 / 0x46620a0
Jul 07 20:48:04-714361 util-scheduler-8620 DEBUG Checking readiness of task: 2740 / 0x46620a0
Jul 07 20:48:04-714553 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:04-714743 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:04-714932 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:04-715122 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:04-715310 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:04-715500 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:04-715689 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:04-715883 util-scheduler-8620 DEBUG Running task: 2740 / 0x46620a0
Jul 07 20:48:04-716066 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:04-716240 util-8620 DEBUG process_notify is running
Jul 07 20:48:04-716410 util-8620 DEBUG client_notify is running
Jul 07 20:48:04-716590 util-scheduler-8620 DEBUG Canceling task: 2735 / 0x4d6ff98
Jul 07 20:48:04-716809 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:04-717022 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:04-717275 cadet-p2p-8620 DEBUG Checking 0x5926a68 towards NCSKBW46 (->V8XX)
Jul 07 20:48:04-717508 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:04-717687 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:04-717874 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:04-718155 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:04-718349 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:04-718528 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:04-718714 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:04-718902 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:04-719077 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:04-719262 util-scheduler-8620 DEBUG Canceling task: 2731 / 0x52cba38
Jul 07 20:48:04-719472 util-scheduler-8620 DEBUG Adding task: 2742 / 0x52cba38
Jul 07 20:48:04-719714 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:04-719884 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:04-720062 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:04-720262 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:04-720437 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:04-720610 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:04-720807 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:04-721011 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:04-721215 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:04-721395 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:04-721599 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:04-721843 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:05-489140 util-scheduler-8620 DEBUG Checking readiness of task: 2741 / 0x46620a0
Jul 07 20:48:05-489502 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:05-489699 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:05-489894 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:05-490086 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:05-490278 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:05-490469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:05-490659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:05-490854 util-scheduler-8620 DEBUG Running task: 2741 / 0x46620a0
Jul 07 20:48:05-491271 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:05-491521 util-scheduler-8620 DEBUG Adding task: 2743 / 0x4662248
Jul 07 20:48:05-491792 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:05-491987 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:05-492180 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:05-492371 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:05-492562 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:05-492753 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:05-492942 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:05-493132 util-scheduler-8620 DEBUG Running task: 2743 / 0x4662248
Jul 07 20:48:05-493350 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:48:05-493551 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:48:05-493782 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:48:05-494046 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:48:05-494293 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:48:05-494523 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:05-494731 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:05-494928 cadet-con-8620 DEBUG  PID 9 (expected 9+)
Jul 07 20:48:05-495109 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:05-495296 util-scheduler-8620 DEBUG Canceling task: 2710 / 0x52cba38
Jul 07 20:48:05-495521 util-scheduler-8620 DEBUG Adding task: 2744 / 0x52cba38
Jul 07 20:48:05-495701 cadet-con-8620 DEBUG   message for us!
Jul 07 20:48:05-495958 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:05-496174 util-scheduler-8620 DEBUG Adding task: 2745 / 0x4d5e5d8
Jul 07 20:48:05-496359 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:05-496528 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:05-500132 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:05-500984 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:05-501220 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:48:05-504420 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:05-504625 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:05-507667 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:05-508861 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:05-509070 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:48:05-512262 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:48:05-512512 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:48:05-512754 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:48:05-512959 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:48:05-513134 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:48:05-513331 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:48:05-513556 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:48:05-513735 cadet-con-8620 DEBUG  ACK 73
Jul 07 20:48:05-513915 cadet-con-8620 DEBUG  last pid 9, last ack 72, qmax 11, q 0
Jul 07 20:48:05-514184 cadet-con-8620 INFO --> {               ACK} ( 73) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:48:05-514378 cadet-con-8620 DEBUG  ack 73
Jul 07 20:48:05-514557 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:05-514792 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:05-514998 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:05-515294 cadet-p2p-8620 INFO que {               ACK} ( 73) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:48:05-515492 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:48:05-515718 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:05-515901 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:05-516079 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:05-516285 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:48:05-516501 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:48:05-516723 util-scheduler-8620 DEBUG Adding task: 2746 / 0x4d6ff98
Jul 07 20:48:05-516903 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:05-517105 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:05-517306 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:05-517482 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:05-517719 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:05-517903 cadet-p2p-8620 DEBUG QQQ    payload , 73
Jul 07 20:48:05-518078 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:48:05-518275 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:05-518457 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:05-518669 util-scheduler-8620 DEBUG Adding task: 2747 / 0x46620a0
Jul 07 20:48:05-518935 util-scheduler-8620 DEBUG Checking readiness of task: 2747 / 0x46620a0
Jul 07 20:48:05-519132 util-scheduler-8620 DEBUG Checking readiness of task: 2745 / 0x4d5e5d8
Jul 07 20:48:05-519324 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:05-519515 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:05-519704 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:05-519895 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:05-520083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:05-520273 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:05-520461 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:05-520654 util-scheduler-8620 DEBUG Running task: 2745 / 0x4d5e5d8
Jul 07 20:48:05-520839 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:05-521018 util-8620 DEBUG process_notify is running
Jul 07 20:48:05-521210 util-8620 DEBUG client_notify is running
Jul 07 20:48:05-521456 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:05-521663 util-scheduler-8620 DEBUG Adding task: 2748 / 0x4d5e5d8
Jul 07 20:48:05-521866 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:48:05-522126 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:05-522324 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:05-522521 util-scheduler-8620 DEBUG Running task: 2746 / 0x4d6ff98
Jul 07 20:48:05-522727 util-scheduler-8620 DEBUG Adding task: 2749 / 0x4d6ff98
Jul 07 20:48:05-522947 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:05-523159 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:05-523357 util-scheduler-8620 DEBUG Adding task: 2750 / 0x46620a0
Jul 07 20:48:05-523601 util-scheduler-8620 DEBUG Checking readiness of task: 2750 / 0x46620a0
Jul 07 20:48:05-523796 util-scheduler-8620 DEBUG Checking readiness of task: 2748 / 0x4d5e5d8
Jul 07 20:48:05-523987 util-scheduler-8620 DEBUG Checking readiness of task: 2747 / 0x46620a0
Jul 07 20:48:05-524177 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:05-524366 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:05-524557 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:05-524746 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:05-524936 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:05-525125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:05-525338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:05-525530 util-scheduler-8620 DEBUG Running task: 2748 / 0x4d5e5d8
Jul 07 20:48:05-525713 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:05-525888 util-8620 DEBUG process_notify is running
Jul 07 20:48:05-526059 util-8620 DEBUG client_notify is running
Jul 07 20:48:05-526270 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:48:05-526514 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:05-526723 util-scheduler-8620 DEBUG Running task: 2750 / 0x46620a0
Jul 07 20:48:05-526907 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:05-527081 util-8620 DEBUG process_notify is running
Jul 07 20:48:05-527251 util-8620 DEBUG client_notify is running
Jul 07 20:48:05-527429 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:05-527623 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:05-527812 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:05-528052 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:06-199154 util-scheduler-8620 DEBUG Checking readiness of task: 2747 / 0x46620a0
Jul 07 20:48:06-199465 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:06-199680 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:06-199873 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:06-200065 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:06-200256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:06-200449 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:06-200701 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:06-200911 util-scheduler-8620 DEBUG Running task: 2747 / 0x46620a0
Jul 07 20:48:06-201354 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:06-201604 util-scheduler-8620 DEBUG Adding task: 2751 / 0x4662248
Jul 07 20:48:06-201995 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:06-202304 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:06-202499 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:06-202983 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:06-203177 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:06-203371 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:06-203562 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:06-203781 util-scheduler-8620 DEBUG Running task: 2751 / 0x4662248
Jul 07 20:48:06-203976 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:06-204184 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:06-204416 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:06-204625 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:06-204831 util-scheduler-8620 DEBUG Adding task: 2752 / 0x46620a0
Jul 07 20:48:06-205021 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:06-205251 util-scheduler-8620 DEBUG Adding task: 2753 / 0x46620a0
Jul 07 20:48:06-205509 util-scheduler-8620 DEBUG Checking readiness of task: 2753 / 0x46620a0
Jul 07 20:48:06-205715 util-scheduler-8620 DEBUG Checking readiness of task: 2752 / 0x46620a0
Jul 07 20:48:06-205915 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:06-206106 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:06-206295 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:06-206485 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:06-206676 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:06-206867 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:06-207056 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:06-207250 util-scheduler-8620 DEBUG Running task: 2752 / 0x46620a0
Jul 07 20:48:06-207435 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:06-207612 util-8620 DEBUG process_notify is running
Jul 07 20:48:06-207784 util-8620 DEBUG client_notify is running
Jul 07 20:48:06-207972 util-scheduler-8620 DEBUG Canceling task: 2749 / 0x4d6ff98
Jul 07 20:48:06-208201 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:48:06-208421 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:06-208659 cadet-p2p-8620 DEBUG Checking 0x5955120 towards NCSKBW46 (->V8XX)
Jul 07 20:48:06-208892 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:06-209070 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:48:06-209284 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:48:06-209556 cadet-p2p-8620 INFO snd {               ACK} ( 73) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:48:06-209751 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:06-209931 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:06-210120 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:48:06-210293 cadet-con-8620 DEBUG  calling cont
Jul 07 20:48:06-210476 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:06-210650 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:06-210832 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:48:06-211032 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:06-211207 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:06-211382 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:06-211580 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:06-211784 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:48:06-211967 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:48:06-212146 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:06-212337 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:48:06-212585 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:09-533896 util-scheduler-8620 DEBUG Checking readiness of task: 2753 / 0x46620a0
Jul 07 20:48:09-534276 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:09-535289 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:09-535489 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:09-535760 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:09-535969 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:09-536161 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:09-536351 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:09-536544 util-scheduler-8620 DEBUG Running task: 2727 / 0x52cbfb8
Jul 07 20:48:09-536779 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:09-537025 cadet-tun-8620 DEBUG  kx started 45 s ago
Jul 07 20:48:09-537252 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:09-537458 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:09-537660 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:09-537896 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:09-538077 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:09-538298 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:09-538590 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:09-538787 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:09-539025 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:09-539233 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:09-539550 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:09-539751 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:09-539977 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:09-540160 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:09-540336 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:09-540542 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:09-540757 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:09-540983 util-scheduler-8620 DEBUG Adding task: 2754 / 0x4d6ff98
Jul 07 20:48:09-541163 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:09-541387 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:09-541565 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:09-541741 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:09-541978 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:09-542175 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:09-542353 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:09-542552 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:09-542795 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:09-542994 util-scheduler-8620 DEBUG Adding task: 2755 / 0x52cbfb8
Jul 07 20:48:09-543253 util-scheduler-8620 DEBUG Checking readiness of task: 2753 / 0x46620a0
Jul 07 20:48:09-543447 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:09-543640 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:09-543830 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:09-544020 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:09-544210 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:09-544398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:09-544587 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:09-544776 util-scheduler-8620 DEBUG Running task: 2754 / 0x4d6ff98
Jul 07 20:48:09-544985 util-scheduler-8620 DEBUG Adding task: 2756 / 0x4d6ff98
Jul 07 20:48:09-545239 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:09-545445 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:09-545655 util-scheduler-8620 DEBUG Adding task: 2757 / 0x46620a0
Jul 07 20:48:09-545899 util-scheduler-8620 DEBUG Checking readiness of task: 2757 / 0x46620a0
Jul 07 20:48:09-546112 util-scheduler-8620 DEBUG Checking readiness of task: 2753 / 0x46620a0
Jul 07 20:48:09-546304 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:09-546494 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:09-546683 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:09-546873 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:09-547063 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:09-547252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:09-547441 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:09-547632 util-scheduler-8620 DEBUG Running task: 2757 / 0x46620a0
Jul 07 20:48:09-547818 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:09-547997 util-8620 DEBUG process_notify is running
Jul 07 20:48:09-548169 util-8620 DEBUG client_notify is running
Jul 07 20:48:09-548350 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:09-548546 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:09-548735 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:09-548991 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:10-191206 util-scheduler-8620 DEBUG Checking readiness of task: 2753 / 0x46620a0
Jul 07 20:48:10-191612 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:10-191810 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:10-192003 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:10-192196 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:10-192387 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:10-192578 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:10-192787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:10-192984 util-scheduler-8620 DEBUG Running task: 2753 / 0x46620a0
Jul 07 20:48:10-193434 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:10-193695 util-scheduler-8620 DEBUG Adding task: 2758 / 0x4662248
Jul 07 20:48:10-194132 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:10-194328 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:10-194525 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:10-194842 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:10-195245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:10-195439 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:10-195630 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:10-195837 util-scheduler-8620 DEBUG Running task: 2758 / 0x4662248
Jul 07 20:48:10-196075 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:48:10-196277 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:48:10-196529 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:48:10-196797 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:48:10-197060 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:48:10-197317 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:10-197529 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:10-197728 cadet-con-8620 DEBUG  PID 10 (expected 10+)
Jul 07 20:48:10-197925 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:10-198114 util-scheduler-8620 DEBUG Canceling task: 2744 / 0x52cba38
Jul 07 20:48:10-198369 util-scheduler-8620 DEBUG Adding task: 2759 / 0x52cba38
Jul 07 20:48:10-198550 cadet-con-8620 DEBUG   message for us!
Jul 07 20:48:10-198812 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:10-199047 util-scheduler-8620 DEBUG Adding task: 2760 / 0x4d5e5d8
Jul 07 20:48:10-199235 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:10-199403 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:10-203107 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:10-203991 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:10-204202 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:48:10-207479 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:10-207691 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:10-210809 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:10-211484 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:10-211689 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:48:10-214934 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:48:10-215208 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:48:10-215455 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:48:10-215633 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:48:10-215806 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:48:10-215978 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:48:10-216215 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:48:10-216396 cadet-con-8620 DEBUG  ACK 74
Jul 07 20:48:10-216576 cadet-con-8620 DEBUG  last pid 10, last ack 73, qmax 11, q 0
Jul 07 20:48:10-216846 cadet-con-8620 INFO --> {               ACK} ( 74) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:48:10-217039 cadet-con-8620 DEBUG  ack 74
Jul 07 20:48:10-217255 cadet-con-8620 DEBUG   C_P+ 0x52cba38 1
Jul 07 20:48:10-217493 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:10-217699 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:10-217997 cadet-p2p-8620 INFO que {               ACK} ( 74) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:48:10-218209 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:48:10-218451 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:10-218635 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:10-218811 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:10-219012 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:48:10-219215 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:10-219391 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:10-219583 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:10-219820 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:10-220015 cadet-p2p-8620 DEBUG QQQ    payload , 74
Jul 07 20:48:10-220191 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:48:10-220426 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:10-220647 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:10-220823 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:10-221021 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:10-221226 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:10-221443 util-scheduler-8620 DEBUG Adding task: 2761 / 0x46620a0
Jul 07 20:48:10-221734 util-scheduler-8620 DEBUG Checking readiness of task: 2761 / 0x46620a0
Jul 07 20:48:10-221931 util-scheduler-8620 DEBUG Checking readiness of task: 2760 / 0x4d5e5d8
Jul 07 20:48:10-222124 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:10-222314 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:10-222524 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:10-222715 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:10-222904 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:10-223117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:10-223307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:10-223500 util-scheduler-8620 DEBUG Running task: 2760 / 0x4d5e5d8
Jul 07 20:48:10-223686 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:10-223864 util-8620 DEBUG process_notify is running
Jul 07 20:48:10-224054 util-8620 DEBUG client_notify is running
Jul 07 20:48:10-224300 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:10-224507 util-scheduler-8620 DEBUG Adding task: 2762 / 0x4d5e5d8
Jul 07 20:48:10-224731 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:48:10-224994 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:10-225213 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:10-225458 util-scheduler-8620 DEBUG Checking readiness of task: 2762 / 0x4d5e5d8
Jul 07 20:48:10-225652 util-scheduler-8620 DEBUG Checking readiness of task: 2761 / 0x46620a0
Jul 07 20:48:10-225860 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:10-226054 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:10-226244 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:10-226434 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:10-226623 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:10-226827 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:10-227016 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:10-227207 util-scheduler-8620 DEBUG Running task: 2762 / 0x4d5e5d8
Jul 07 20:48:10-227391 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:10-227565 util-8620 DEBUG process_notify is running
Jul 07 20:48:10-227735 util-8620 DEBUG client_notify is running
Jul 07 20:48:10-227962 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:48:10-228211 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:11-745582 util-scheduler-8620 DEBUG Checking readiness of task: 2761 / 0x46620a0
Jul 07 20:48:11-746096 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-746518 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-746725 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-746927 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-747120 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-747312 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-747504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-747701 util-scheduler-8620 DEBUG Running task: 2761 / 0x46620a0
Jul 07 20:48:11-748124 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:11-748381 util-scheduler-8620 DEBUG Adding task: 2763 / 0x4662248
Jul 07 20:48:11-748666 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-748861 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-749054 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-749277 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-749468 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-749658 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-749847 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-750037 util-scheduler-8620 DEBUG Running task: 2763 / 0x4662248
Jul 07 20:48:11-750261 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:11-750464 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:11-750696 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:11-750905 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:11-751113 util-scheduler-8620 DEBUG Adding task: 2764 / 0x46620a0
Jul 07 20:48:11-751302 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:11-751509 util-scheduler-8620 DEBUG Adding task: 2765 / 0x46620a0
Jul 07 20:48:11-751757 util-scheduler-8620 DEBUG Checking readiness of task: 2765 / 0x46620a0
Jul 07 20:48:11-751952 util-scheduler-8620 DEBUG Checking readiness of task: 2764 / 0x46620a0
Jul 07 20:48:11-752145 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-752336 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-752529 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-752720 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-752910 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-753099 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-754127 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-754378 util-scheduler-8620 DEBUG Running task: 2764 / 0x46620a0
Jul 07 20:48:11-754578 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:11-754759 util-8620 DEBUG process_notify is running
Jul 07 20:48:11-754933 util-8620 DEBUG client_notify is running
Jul 07 20:48:11-755122 util-scheduler-8620 DEBUG Canceling task: 2756 / 0x4d6ff98
Jul 07 20:48:11-755351 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:11-755571 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:11-755811 cadet-p2p-8620 DEBUG Checking 0x5980170 towards NCSKBW46 (->V8XX)
Jul 07 20:48:11-756046 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:11-756225 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:48:11-756417 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:48:11-756687 cadet-p2p-8620 INFO snd {               ACK} ( 74) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:48:11-756882 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:11-757062 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:11-757277 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:48:11-757451 cadet-con-8620 DEBUG  calling cont
Jul 07 20:48:11-757636 cadet-con-8620 DEBUG  C_P- 0x52cba38 2
Jul 07 20:48:11-757811 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:11-758034 cadet-p2p-8620 DEBUG Checking 0x5958230 towards NCSKBW46 (->V8XX)
Jul 07 20:48:11-758271 cadet-p2p-8620 DEBUG Checking 0x5958230 towards NCSKBW46 (->V8XX)
Jul 07 20:48:11-758463 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:48:11-758671 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:11-758886 util-scheduler-8620 DEBUG Adding task: 2766 / 0x4d6ff98
Jul 07 20:48:11-759065 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:11-759241 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:48:11-759438 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:11-759612 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:11-759786 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:11-760025 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:11-760220 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:11-760397 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:11-760595 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:11-760802 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:48:11-760985 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:48:11-761547 util-scheduler-8620 DEBUG Adding task: 2767 / 0x4d6ff98
Jul 07 20:48:11-761789 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:11-761988 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:11-762192 util-scheduler-8620 DEBUG Adding task: 2768 / 0x46620a0
Jul 07 20:48:11-762394 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:48:11-763217 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:11-763418 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:48:11-763670 util-scheduler-8620 DEBUG Checking readiness of task: 2768 / 0x46620a0
Jul 07 20:48:11-763865 util-scheduler-8620 DEBUG Checking readiness of task: 2765 / 0x46620a0
Jul 07 20:48:11-764055 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-764249 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-764438 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-764628 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-764818 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-765006 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-765216 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-765410 util-scheduler-8620 DEBUG Running task: 2768 / 0x46620a0
Jul 07 20:48:11-765594 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:11-765771 util-8620 DEBUG process_notify is running
Jul 07 20:48:11-765940 util-8620 DEBUG client_notify is running
Jul 07 20:48:11-766119 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:11-766314 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:11-766504 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:11-766745 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:11-766950 util-scheduler-8620 DEBUG Running task: 2766 / 0x4d6ff98
Jul 07 20:48:11-767141 util-scheduler-8620 DEBUG Canceling task: 2767 / 0x4d6ff98
Jul 07 20:48:11-767355 util-scheduler-8620 DEBUG Adding task: 2769 / 0x4d6ff98
Jul 07 20:48:11-767570 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:11-767764 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:11-767962 util-scheduler-8620 DEBUG Adding task: 2770 / 0x46620a0
Jul 07 20:48:11-768201 util-scheduler-8620 DEBUG Checking readiness of task: 2770 / 0x46620a0
Jul 07 20:48:11-768396 util-scheduler-8620 DEBUG Checking readiness of task: 2765 / 0x46620a0
Jul 07 20:48:11-768585 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-768775 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-768965 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-769155 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-769365 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-769554 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-769742 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-769933 util-scheduler-8620 DEBUG Running task: 2770 / 0x46620a0
Jul 07 20:48:11-770132 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:11-770306 util-8620 DEBUG process_notify is running
Jul 07 20:48:11-770475 util-8620 DEBUG client_notify is running
Jul 07 20:48:11-770651 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:11-770839 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:11-771027 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:11-771285 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:11-890296 util-scheduler-8620 DEBUG Checking readiness of task: 2765 / 0x46620a0
Jul 07 20:48:11-890568 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-890767 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-890961 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-891153 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-891344 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-891534 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-891723 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-891924 util-scheduler-8620 DEBUG Running task: 2765 / 0x46620a0
Jul 07 20:48:11-892350 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:11-892606 util-scheduler-8620 DEBUG Adding task: 2771 / 0x4662248
Jul 07 20:48:11-892886 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-893081 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-893302 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-893494 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-893683 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-893875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-894064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-894253 util-scheduler-8620 DEBUG Running task: 2771 / 0x4662248
Jul 07 20:48:11-894444 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:11-894645 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:11-894877 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:11-895084 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:11-895292 util-scheduler-8620 DEBUG Adding task: 2772 / 0x46620a0
Jul 07 20:48:11-895481 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:11-895686 util-scheduler-8620 DEBUG Adding task: 2773 / 0x46620a0
Jul 07 20:48:11-895932 util-scheduler-8620 DEBUG Checking readiness of task: 2773 / 0x46620a0
Jul 07 20:48:11-896124 util-scheduler-8620 DEBUG Checking readiness of task: 2772 / 0x46620a0
Jul 07 20:48:11-896316 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:11-896506 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:11-896697 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:11-896886 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:11-897075 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:11-897290 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:11-897481 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:11-897673 util-scheduler-8620 DEBUG Running task: 2772 / 0x46620a0
Jul 07 20:48:11-897858 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:11-898036 util-8620 DEBUG process_notify is running
Jul 07 20:48:11-898208 util-8620 DEBUG client_notify is running
Jul 07 20:48:11-898396 util-scheduler-8620 DEBUG Canceling task: 2769 / 0x4d6ff98
Jul 07 20:48:11-898622 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:11-898843 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:11-899083 cadet-p2p-8620 DEBUG Checking 0x5958230 towards NCSKBW46 (->V8XX)
Jul 07 20:48:11-899317 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:11-899543 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:11-899734 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:11-900021 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:11-900216 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:11-900396 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:11-900583 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:11-900772 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:11-900951 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:11-901137 util-scheduler-8620 DEBUG Canceling task: 2742 / 0x52cba38
Jul 07 20:48:11-901376 util-scheduler-8620 DEBUG Adding task: 2774 / 0x52cba38
Jul 07 20:48:11-901628 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:11-901804 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:11-901985 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:11-902186 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:11-902361 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:11-902535 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:11-902733 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:11-902938 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:11-903122 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:11-903301 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:11-903491 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:11-903744 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:14-545803 util-scheduler-8620 DEBUG Checking readiness of task: 2773 / 0x46620a0
Jul 07 20:48:14-546196 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:14-550806 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:14-551004 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:14-551199 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:14-551393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:14-551584 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:14-551772 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:14-551966 util-scheduler-8620 DEBUG Running task: 2755 / 0x52cbfb8
Jul 07 20:48:14-552204 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:14-552455 cadet-tun-8620 DEBUG  kx started 50 s ago
Jul 07 20:48:14-552662 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:14-552863 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:14-553066 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:14-553332 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:14-553516 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:14-553737 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:14-554029 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:14-554227 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:14-554464 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:14-554671 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:14-554988 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:14-555188 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:14-555413 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:14-555596 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:14-555771 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:14-555978 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:14-556229 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:14-556455 util-scheduler-8620 DEBUG Adding task: 2775 / 0x4d6ff98
Jul 07 20:48:14-556634 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:14-556838 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:14-557014 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:14-557214 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:14-557455 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:14-557652 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:14-557830 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:14-558028 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:14-558272 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:14-558469 util-scheduler-8620 DEBUG Adding task: 2776 / 0x52cbfb8
Jul 07 20:48:14-558727 util-scheduler-8620 DEBUG Checking readiness of task: 2773 / 0x46620a0
Jul 07 20:48:14-558920 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:14-559109 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:14-559299 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:14-559488 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:14-559677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:14-559865 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:14-560053 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:14-560242 util-scheduler-8620 DEBUG Running task: 2775 / 0x4d6ff98
Jul 07 20:48:14-560449 util-scheduler-8620 DEBUG Adding task: 2777 / 0x4d6ff98
Jul 07 20:48:14-560672 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:14-560876 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:14-561082 util-scheduler-8620 DEBUG Adding task: 2778 / 0x46620a0
Jul 07 20:48:14-561353 util-scheduler-8620 DEBUG Checking readiness of task: 2778 / 0x46620a0
Jul 07 20:48:14-561548 util-scheduler-8620 DEBUG Checking readiness of task: 2773 / 0x46620a0
Jul 07 20:48:14-561738 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:14-561927 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:14-562117 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:14-562305 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:14-562498 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:14-562686 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:14-562875 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:14-563065 util-scheduler-8620 DEBUG Running task: 2778 / 0x46620a0
Jul 07 20:48:14-563250 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:14-563428 util-8620 DEBUG process_notify is running
Jul 07 20:48:14-563600 util-8620 DEBUG client_notify is running
Jul 07 20:48:14-563778 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:14-563973 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:14-564164 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:14-564422 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:16-193712 util-scheduler-8620 DEBUG Checking readiness of task: 2773 / 0x46620a0
Jul 07 20:48:16-194100 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:16-194301 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:16-194497 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:16-194694 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:16-194917 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:16-195110 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:16-195305 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:16-195501 util-scheduler-8620 DEBUG Running task: 2773 / 0x46620a0
Jul 07 20:48:16-195929 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:16-196189 util-scheduler-8620 DEBUG Adding task: 2779 / 0x4662248
Jul 07 20:48:16-196471 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:16-196678 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:16-196869 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:16-197058 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:16-197286 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:16-197476 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:16-197665 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:16-197853 util-scheduler-8620 DEBUG Running task: 2779 / 0x4662248
Jul 07 20:48:16-198044 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:16-198242 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:16-198475 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:16-198681 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:16-198892 util-scheduler-8620 DEBUG Adding task: 2780 / 0x46620a0
Jul 07 20:48:16-199088 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:16-199306 util-scheduler-8620 DEBUG Adding task: 2781 / 0x46620a0
Jul 07 20:48:16-199577 util-scheduler-8620 DEBUG Checking readiness of task: 2781 / 0x46620a0
Jul 07 20:48:16-199775 util-scheduler-8620 DEBUG Checking readiness of task: 2780 / 0x46620a0
Jul 07 20:48:16-199969 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:16-200161 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:16-200353 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:16-200543 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:16-200735 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:16-200924 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:16-201115 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:16-201331 util-scheduler-8620 DEBUG Running task: 2780 / 0x46620a0
Jul 07 20:48:16-201518 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:16-201699 util-8620 DEBUG process_notify is running
Jul 07 20:48:16-201870 util-8620 DEBUG client_notify is running
Jul 07 20:48:16-202059 util-scheduler-8620 DEBUG Canceling task: 2777 / 0x4d6ff98
Jul 07 20:48:16-202292 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:16-202514 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:16-202756 cadet-p2p-8620 DEBUG Checking 0x59851b0 towards NCSKBW46 (->V8XX)
Jul 07 20:48:16-202992 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:16-203173 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:16-203365 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:16-203657 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:16-203855 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:16-204035 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:16-204225 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:16-204416 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:16-204595 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:16-204802 util-scheduler-8620 DEBUG Canceling task: 2774 / 0x52cba38
Jul 07 20:48:16-205021 util-scheduler-8620 DEBUG Adding task: 2782 / 0x52cba38
Jul 07 20:48:16-205296 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:16-205469 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:16-205651 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:16-205853 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:16-206030 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:16-206205 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:16-206405 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:16-206610 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:16-206794 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:16-206975 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:16-207166 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:16-207410 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:16-910901 util-scheduler-8620 DEBUG Checking readiness of task: 2781 / 0x46620a0
Jul 07 20:48:16-911225 util-scheduler-8620 DEBUG Checking readiness of task: 2692 / 0x465ee60
Jul 07 20:48:16-911424 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:16-911616 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:16-911809 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:16-912002 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:16-912192 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:16-912385 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:16-912582 util-scheduler-8620 DEBUG Running task: 2692 / 0x465ee60
Jul 07 20:48:16-913021 util-8620 DEBUG receive_ready read 104/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:48:16-913308 util-scheduler-8620 DEBUG Adding task: 2783 / 0x465f008
Jul 07 20:48:16-913587 util-scheduler-8620 DEBUG Checking readiness of task: 2781 / 0x46620a0
Jul 07 20:48:16-913782 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:16-913976 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:16-914169 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:16-914360 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:16-914549 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:16-914738 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:16-914928 util-scheduler-8620 DEBUG Running task: 2783 / 0x465f008
Jul 07 20:48:16-915119 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 20:48:16-915356 nse-api-8620 DEBUG Received information about peer `KNAS' from peerinfo database
Jul 07 20:48:16-915641 cadet-hll-8620 DEBUG  hello for KNAS (64 bytes), expires on Tue Jul 08 08:48:16 2014
Jul 07 20:48:16-915867 cadet-p2p-8620 DEBUG set hello for KNAS
Jul 07 20:48:16-916145 cadet-p2p-8620 DEBUG  merge into 0x59879a8 (64 bytes)
Jul 07 20:48:16-916339 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:16-916553 util-scheduler-8620 DEBUG Adding task: 2784 / 0x465ee60
Jul 07 20:48:18-457515 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-457889 util-scheduler-8620 DEBUG Checking readiness of task: 2781 / 0x46620a0
Jul 07 20:48:18-458088 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-458281 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-458474 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-458664 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-458885 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-459076 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-459272 util-scheduler-8620 DEBUG Running task: 2781 / 0x46620a0
Jul 07 20:48:18-459697 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:18-459957 util-scheduler-8620 DEBUG Adding task: 2785 / 0x4662248
Jul 07 20:48:18-460236 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-460430 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-460621 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-460811 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-461001 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-461214 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-461407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-461598 util-scheduler-8620 DEBUG Running task: 2785 / 0x4662248
Jul 07 20:48:18-461790 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:48:18-461989 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:48:18-462218 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:48:18-462484 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:48:18-462730 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:48:18-462974 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:18-463183 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:18-463380 cadet-con-8620 DEBUG  PID 11 (expected 11+)
Jul 07 20:48:18-463560 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:18-463747 util-scheduler-8620 DEBUG Canceling task: 2759 / 0x52cba38
Jul 07 20:48:18-463971 util-scheduler-8620 DEBUG Adding task: 2786 / 0x52cba38
Jul 07 20:48:18-464175 cadet-con-8620 DEBUG   message for us!
Jul 07 20:48:18-464434 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:18-464654 util-scheduler-8620 DEBUG Adding task: 2787 / 0x4d5e5d8
Jul 07 20:48:18-464838 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:18-465007 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:18-472246 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:18-473144 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:18-473387 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:48:18-476571 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:18-476758 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:18-479804 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:18-480444 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:18-480646 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:48:18-483827 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:48:18-484089 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:48:18-484337 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:48:18-484516 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:48:18-484689 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:48:18-484860 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:48:18-485080 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:48:18-485283 cadet-con-8620 DEBUG  ACK 75
Jul 07 20:48:18-485464 cadet-con-8620 DEBUG  last pid 11, last ack 74, qmax 11, q 0
Jul 07 20:48:18-485734 cadet-con-8620 INFO --> {               ACK} ( 75) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:48:18-485926 cadet-con-8620 DEBUG  ack 75
Jul 07 20:48:18-486108 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:18-486342 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:18-486550 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:18-486871 cadet-p2p-8620 INFO que {               ACK} ( 75) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:48:18-487071 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:48:18-487297 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:18-487479 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:18-487655 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:18-487859 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:48:18-488075 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:48:18-488302 util-scheduler-8620 DEBUG Adding task: 2788 / 0x4d6ff98
Jul 07 20:48:18-488482 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:18-488686 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:18-488862 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:18-489036 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:18-489293 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:18-489478 cadet-p2p-8620 DEBUG QQQ    payload , 75
Jul 07 20:48:18-489656 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:48:18-489854 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:18-490037 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:18-490248 util-scheduler-8620 DEBUG Adding task: 2789 / 0x46620a0
Jul 07 20:48:18-490565 util-scheduler-8620 DEBUG Checking readiness of task: 2789 / 0x46620a0
Jul 07 20:48:18-490763 util-scheduler-8620 DEBUG Checking readiness of task: 2787 / 0x4d5e5d8
Jul 07 20:48:18-490956 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-491145 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-491335 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-491525 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-491714 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-491902 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-492091 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-492284 util-scheduler-8620 DEBUG Running task: 2787 / 0x4d5e5d8
Jul 07 20:48:18-492469 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:18-492648 util-8620 DEBUG process_notify is running
Jul 07 20:48:18-492821 util-8620 DEBUG client_notify is running
Jul 07 20:48:18-493067 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:18-493296 util-scheduler-8620 DEBUG Adding task: 2790 / 0x4d5e5d8
Jul 07 20:48:18-493500 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:48:18-493762 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:18-493960 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:18-494157 util-scheduler-8620 DEBUG Running task: 2788 / 0x4d6ff98
Jul 07 20:48:18-494364 util-scheduler-8620 DEBUG Adding task: 2791 / 0x4d6ff98
Jul 07 20:48:18-494586 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:18-494781 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:18-494977 util-scheduler-8620 DEBUG Adding task: 2792 / 0x46620a0
Jul 07 20:48:18-495218 util-scheduler-8620 DEBUG Checking readiness of task: 2792 / 0x46620a0
Jul 07 20:48:18-495413 util-scheduler-8620 DEBUG Checking readiness of task: 2790 / 0x4d5e5d8
Jul 07 20:48:18-495603 util-scheduler-8620 DEBUG Checking readiness of task: 2789 / 0x46620a0
Jul 07 20:48:18-495792 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-495981 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-496185 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-496373 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-496581 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-496769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-496959 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-497149 util-scheduler-8620 DEBUG Running task: 2790 / 0x4d5e5d8
Jul 07 20:48:18-497378 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:18-497554 util-8620 DEBUG process_notify is running
Jul 07 20:48:18-497723 util-8620 DEBUG client_notify is running
Jul 07 20:48:18-497935 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:48:18-498183 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:18-498392 util-scheduler-8620 DEBUG Running task: 2792 / 0x46620a0
Jul 07 20:48:18-498576 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:18-498751 util-8620 DEBUG process_notify is running
Jul 07 20:48:18-498919 util-8620 DEBUG client_notify is running
Jul 07 20:48:18-499097 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:18-499291 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:18-499479 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:18-499725 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:18-621290 util-scheduler-8620 DEBUG Checking readiness of task: 2789 / 0x46620a0
Jul 07 20:48:18-621674 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-621871 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-622063 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-622258 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-622449 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-622640 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-622831 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-623027 util-scheduler-8620 DEBUG Running task: 2789 / 0x46620a0
Jul 07 20:48:18-623450 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:18-623710 util-scheduler-8620 DEBUG Adding task: 2793 / 0x4662248
Jul 07 20:48:18-623990 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-624184 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-624375 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-624564 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-624754 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-624943 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-625131 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-625352 util-scheduler-8620 DEBUG Running task: 2793 / 0x4662248
Jul 07 20:48:18-625543 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:18-625743 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:18-625975 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:18-626182 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:18-626388 util-scheduler-8620 DEBUG Adding task: 2794 / 0x46620a0
Jul 07 20:48:18-626577 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:18-626783 util-scheduler-8620 DEBUG Adding task: 2795 / 0x46620a0
Jul 07 20:48:18-627031 util-scheduler-8620 DEBUG Checking readiness of task: 2795 / 0x46620a0
Jul 07 20:48:18-627224 util-scheduler-8620 DEBUG Checking readiness of task: 2794 / 0x46620a0
Jul 07 20:48:18-627445 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:18-627635 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:18-627825 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:18-628015 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:18-628203 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:18-628392 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:18-628582 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:18-628773 util-scheduler-8620 DEBUG Running task: 2794 / 0x46620a0
Jul 07 20:48:18-628959 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:18-629137 util-8620 DEBUG process_notify is running
Jul 07 20:48:18-629334 util-8620 DEBUG client_notify is running
Jul 07 20:48:18-629522 util-scheduler-8620 DEBUG Canceling task: 2791 / 0x4d6ff98
Jul 07 20:48:18-629750 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:48:18-629970 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:18-630209 cadet-p2p-8620 DEBUG Checking 0x59aed78 towards NCSKBW46 (->V8XX)
Jul 07 20:48:18-630443 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:18-630621 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:48:18-630813 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:48:18-631082 cadet-p2p-8620 INFO snd {               ACK} ( 75) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:48:18-631276 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:18-631455 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:18-631643 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:48:18-631817 cadet-con-8620 DEBUG  calling cont
Jul 07 20:48:18-632000 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:18-632174 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:18-632356 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:48:18-632556 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:18-632730 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:18-632904 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:18-633103 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:18-633331 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:48:18-633515 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:48:18-633696 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:18-633887 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:48:18-634133 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:19-559543 util-scheduler-8620 DEBUG Checking readiness of task: 2795 / 0x46620a0
Jul 07 20:48:19-559896 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:19-563223 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:19-563421 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:19-563614 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:19-563806 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:19-563999 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:19-564190 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:19-564382 util-scheduler-8620 DEBUG Running task: 2776 / 0x52cbfb8
Jul 07 20:48:19-564614 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:19-564860 cadet-tun-8620 DEBUG  kx started 55 s ago
Jul 07 20:48:19-565066 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:19-565292 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:19-565496 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:19-565729 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:19-565941 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:19-566164 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:19-566456 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:19-566654 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:19-566891 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:19-567098 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:19-567434 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:19-567635 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:19-567861 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:19-568044 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:19-568221 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:19-568427 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:19-568642 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:19-568865 util-scheduler-8620 DEBUG Adding task: 2796 / 0x4d6ff98
Jul 07 20:48:19-569046 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:19-569275 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:19-569453 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:19-569628 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:19-569867 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:19-570064 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:19-570241 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:19-570439 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:19-570682 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:19-570881 util-scheduler-8620 DEBUG Adding task: 2797 / 0x52cbfb8
Jul 07 20:48:19-571135 util-scheduler-8620 DEBUG Checking readiness of task: 2795 / 0x46620a0
Jul 07 20:48:19-571329 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:19-571519 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:19-571709 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:19-571899 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:19-572087 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:19-572276 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:19-572465 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:19-572654 util-scheduler-8620 DEBUG Running task: 2796 / 0x4d6ff98
Jul 07 20:48:19-572862 util-scheduler-8620 DEBUG Adding task: 2798 / 0x4d6ff98
Jul 07 20:48:19-573084 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:19-573316 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:19-573526 util-scheduler-8620 DEBUG Adding task: 2799 / 0x46620a0
Jul 07 20:48:19-573770 util-scheduler-8620 DEBUG Checking readiness of task: 2799 / 0x46620a0
Jul 07 20:48:19-573966 util-scheduler-8620 DEBUG Checking readiness of task: 2795 / 0x46620a0
Jul 07 20:48:19-574156 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:19-574346 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:19-574535 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:19-574724 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:19-574913 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:19-575101 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:19-575291 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:19-575482 util-scheduler-8620 DEBUG Running task: 2799 / 0x46620a0
Jul 07 20:48:19-575685 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:19-575863 util-8620 DEBUG process_notify is running
Jul 07 20:48:19-576036 util-8620 DEBUG client_notify is running
Jul 07 20:48:19-576215 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:19-576411 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:19-576601 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:19-576858 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:21-102835 util-scheduler-8620 DEBUG Checking readiness of task: 2795 / 0x46620a0
Jul 07 20:48:21-103225 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:21-103426 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:21-103623 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:21-103817 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:21-104008 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:21-104200 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:21-104390 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:21-104585 util-scheduler-8620 DEBUG Running task: 2795 / 0x46620a0
Jul 07 20:48:21-105010 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:21-105287 util-scheduler-8620 DEBUG Adding task: 2800 / 0x4662248
Jul 07 20:48:21-105568 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:21-105762 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:21-105954 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:21-106144 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:21-106337 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:21-106526 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:21-106716 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:21-106906 util-scheduler-8620 DEBUG Running task: 2800 / 0x4662248
Jul 07 20:48:21-107098 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:21-107298 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:21-107533 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:21-107740 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:21-107947 util-scheduler-8620 DEBUG Adding task: 2801 / 0x46620a0
Jul 07 20:48:21-108135 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:21-108341 util-scheduler-8620 DEBUG Adding task: 2802 / 0x46620a0
Jul 07 20:48:21-108588 util-scheduler-8620 DEBUG Checking readiness of task: 2802 / 0x46620a0
Jul 07 20:48:21-108780 util-scheduler-8620 DEBUG Checking readiness of task: 2801 / 0x46620a0
Jul 07 20:48:21-108973 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:21-109163 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:21-109382 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:21-109574 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:21-109764 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:21-109954 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:21-110144 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:21-110336 util-scheduler-8620 DEBUG Running task: 2801 / 0x46620a0
Jul 07 20:48:21-110521 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:21-110705 util-8620 DEBUG process_notify is running
Jul 07 20:48:21-110912 util-8620 DEBUG client_notify is running
Jul 07 20:48:21-111106 util-scheduler-8620 DEBUG Canceling task: 2798 / 0x4d6ff98
Jul 07 20:48:21-111337 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:21-111558 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:21-111799 cadet-p2p-8620 DEBUG Checking 0x59b1e50 towards NCSKBW46 (->V8XX)
Jul 07 20:48:21-112035 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:21-112214 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:21-112404 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:21-112693 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:21-112889 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:21-113071 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:21-113283 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:21-113474 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:21-113652 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:21-113838 util-scheduler-8620 DEBUG Canceling task: 2782 / 0x52cba38
Jul 07 20:48:21-114053 util-scheduler-8620 DEBUG Adding task: 2803 / 0x52cba38
Jul 07 20:48:21-114304 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:21-114476 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:21-114659 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:21-114873 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:21-115051 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:21-115226 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:21-115425 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:21-115631 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:21-115815 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:21-115995 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:21-116187 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:21-116993 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:24-573377 util-scheduler-8620 DEBUG Checking readiness of task: 2802 / 0x46620a0
Jul 07 20:48:24-573768 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:24-576028 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:24-576242 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:24-576439 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:24-576653 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:24-576847 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:24-577040 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:24-577259 util-scheduler-8620 DEBUG Running task: 2797 / 0x52cbfb8
Jul 07 20:48:24-577499 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:24-577759 cadet-tun-8620 DEBUG  kx started 1 m ago
Jul 07 20:48:24-577966 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:24-578167 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:24-578371 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:24-578611 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:24-578793 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:24-579014 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:24-579306 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:24-579503 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:24-579740 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:24-579948 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:24-580264 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:24-580491 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:24-580720 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:24-580905 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:24-581083 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:24-581313 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:24-581529 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:24-581757 util-scheduler-8620 DEBUG Adding task: 2804 / 0x4d6ff98
Jul 07 20:48:24-581937 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:24-582149 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:24-582336 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:24-582514 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:24-582757 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:24-582960 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:24-583137 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:24-583336 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:24-583584 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:24-583786 util-scheduler-8620 DEBUG Adding task: 2805 / 0x52cbfb8
Jul 07 20:48:24-584049 util-scheduler-8620 DEBUG Checking readiness of task: 2802 / 0x46620a0
Jul 07 20:48:24-584244 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:24-584434 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:24-584623 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:24-584814 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:24-585002 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:24-585210 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:24-585402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:24-585596 util-scheduler-8620 DEBUG Running task: 2804 / 0x4d6ff98
Jul 07 20:48:24-585812 util-scheduler-8620 DEBUG Adding task: 2806 / 0x4d6ff98
Jul 07 20:48:24-586042 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:24-586248 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:24-586459 util-scheduler-8620 DEBUG Adding task: 2807 / 0x46620a0
Jul 07 20:48:24-586712 util-scheduler-8620 DEBUG Checking readiness of task: 2807 / 0x46620a0
Jul 07 20:48:24-586908 util-scheduler-8620 DEBUG Checking readiness of task: 2802 / 0x46620a0
Jul 07 20:48:24-587099 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:24-587290 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:24-587481 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:24-587671 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:24-587863 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:24-588053 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:24-588242 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:24-588439 util-scheduler-8620 DEBUG Running task: 2807 / 0x46620a0
Jul 07 20:48:24-588626 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:24-588805 util-8620 DEBUG process_notify is running
Jul 07 20:48:24-588978 util-8620 DEBUG client_notify is running
Jul 07 20:48:24-589160 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:24-589381 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:24-589576 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:24-589826 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:26-066355 util-scheduler-8620 DEBUG Checking readiness of task: 2802 / 0x46620a0
Jul 07 20:48:26-066813 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:26-067015 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:26-067222 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:26-067419 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:26-067627 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:26-067821 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:26-068031 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:26-068230 util-scheduler-8620 DEBUG Running task: 2802 / 0x46620a0
Jul 07 20:48:26-068654 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:26-068913 util-scheduler-8620 DEBUG Adding task: 2808 / 0x4662248
Jul 07 20:48:26-069226 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:26-069424 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:26-069618 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:26-069812 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:26-070004 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:26-070196 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:26-070389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:26-070581 util-scheduler-8620 DEBUG Running task: 2808 / 0x4662248
Jul 07 20:48:26-070776 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:26-070978 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:26-071213 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:26-071423 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:26-071634 util-scheduler-8620 DEBUG Adding task: 2809 / 0x46620a0
Jul 07 20:48:26-071826 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:26-072046 util-scheduler-8620 DEBUG Adding task: 2810 / 0x46620a0
Jul 07 20:48:26-072295 util-scheduler-8620 DEBUG Checking readiness of task: 2810 / 0x46620a0
Jul 07 20:48:26-072491 util-scheduler-8620 DEBUG Checking readiness of task: 2809 / 0x46620a0
Jul 07 20:48:26-072685 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:26-072878 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:26-073070 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:26-073701 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:26-073899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:26-074093 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:26-074298 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:26-074494 util-scheduler-8620 DEBUG Running task: 2809 / 0x46620a0
Jul 07 20:48:26-074707 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:26-074890 util-8620 DEBUG process_notify is running
Jul 07 20:48:26-075067 util-8620 DEBUG client_notify is running
Jul 07 20:48:26-075261 util-scheduler-8620 DEBUG Canceling task: 2806 / 0x4d6ff98
Jul 07 20:48:26-075493 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:26-075717 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:26-075960 cadet-p2p-8620 DEBUG Checking 0x59b4a08 towards NCSKBW46 (->V8XX)
Jul 07 20:48:26-076198 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:26-076379 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:26-076574 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:26-076860 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:26-077076 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:26-077286 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:26-077477 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:26-077669 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:26-077850 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:26-078037 util-scheduler-8620 DEBUG Canceling task: 2803 / 0x52cba38
Jul 07 20:48:26-078253 util-scheduler-8620 DEBUG Adding task: 2811 / 0x52cba38
Jul 07 20:48:26-078508 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:26-078682 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:26-078866 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:26-079070 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:26-079248 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:26-079425 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:26-079627 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:26-079834 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:26-080021 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:26-080204 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:26-080399 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:26-080643 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:29-587454 util-scheduler-8620 DEBUG Checking readiness of task: 2810 / 0x46620a0
Jul 07 20:48:29-587846 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:29-590264 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:29-590641 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:29-590845 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:29-591038 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:29-591228 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:29-591418 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:29-591612 util-scheduler-8620 DEBUG Running task: 2805 / 0x52cbfb8
Jul 07 20:48:29-591850 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:29-592099 cadet-tun-8620 DEBUG  kx started 65 s ago
Jul 07 20:48:29-592307 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:29-592507 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:29-592710 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:29-592951 cadet-tun-8620 DEBUG   connection NCSKBW46 (->V8XX): 3
Jul 07 20:48:29-593133 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:29-593382 cadet-tun-8620 DEBUG  selected: connection NCSKBW46 (->V8XX)
Jul 07 20:48:29-593676 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (196 bytes)
Jul 07 20:48:29-593873 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:29-594110 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:29-594318 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:29-594637 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 196)
Jul 07 20:48:29-594838 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:29-595064 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:29-595247 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:29-595423 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:29-595628 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:29-595843 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:29-596070 util-scheduler-8620 DEBUG Adding task: 2812 / 0x4d6ff98
Jul 07 20:48:29-596253 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:29-596490 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:29-596669 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:29-596845 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:29-597082 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:29-597307 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:29-597485 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:29-597684 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:29-597927 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:29-598125 util-scheduler-8620 DEBUG Adding task: 2813 / 0x52cbfb8
Jul 07 20:48:29-598392 util-scheduler-8620 DEBUG Checking readiness of task: 2810 / 0x46620a0
Jul 07 20:48:29-598585 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:29-598775 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:29-598965 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:29-599154 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:29-599345 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:29-599533 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:29-599724 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:29-599913 util-scheduler-8620 DEBUG Running task: 2812 / 0x4d6ff98
Jul 07 20:48:29-600121 util-scheduler-8620 DEBUG Adding task: 2814 / 0x4d6ff98
Jul 07 20:48:29-600343 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:29-600548 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:29-600757 util-scheduler-8620 DEBUG Adding task: 2815 / 0x46620a0
Jul 07 20:48:29-601001 util-scheduler-8620 DEBUG Checking readiness of task: 2815 / 0x46620a0
Jul 07 20:48:29-601222 util-scheduler-8620 DEBUG Checking readiness of task: 2810 / 0x46620a0
Jul 07 20:48:29-601415 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:29-601605 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:29-601795 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:29-601984 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:29-602173 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:29-602361 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:29-602550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:29-602740 util-scheduler-8620 DEBUG Running task: 2815 / 0x46620a0
Jul 07 20:48:29-602945 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:29-603122 util-8620 DEBUG process_notify is running
Jul 07 20:48:29-603296 util-8620 DEBUG client_notify is running
Jul 07 20:48:29-603475 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:29-603671 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:29-603861 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:29-604120 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:31-599273 util-scheduler-8620 DEBUG Checking readiness of task: 2810 / 0x46620a0
Jul 07 20:48:31-599670 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-599875 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-600067 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-600263 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-600459 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-600659 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-600848 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-601075 util-scheduler-8620 DEBUG Running task: 2810 / 0x46620a0
Jul 07 20:48:31-601520 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:31-601781 util-scheduler-8620 DEBUG Adding task: 2816 / 0x4662248
Jul 07 20:48:31-602062 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-602257 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-602447 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-602637 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-602984 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-603187 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-603377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-603569 util-scheduler-8620 DEBUG Running task: 2816 / 0x4662248
Jul 07 20:48:31-603762 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:31-603961 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:31-604203 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:31-604412 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:31-604621 util-scheduler-8620 DEBUG Adding task: 2817 / 0x46620a0
Jul 07 20:48:31-604810 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-605023 util-scheduler-8620 DEBUG Adding task: 2818 / 0x46620a0
Jul 07 20:48:31-605419 util-scheduler-8620 DEBUG Checking readiness of task: 2818 / 0x46620a0
Jul 07 20:48:31-605622 util-scheduler-8620 DEBUG Checking readiness of task: 2817 / 0x46620a0
Jul 07 20:48:31-605814 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-606003 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-606195 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-606388 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-607004 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-607204 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-607399 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-607593 util-scheduler-8620 DEBUG Running task: 2817 / 0x46620a0
Jul 07 20:48:31-607778 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:31-607957 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-608131 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-608326 util-scheduler-8620 DEBUG Canceling task: 2814 / 0x4d6ff98
Jul 07 20:48:31-608566 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:31-608791 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:31-609034 cadet-p2p-8620 DEBUG Checking 0x59b76b8 towards NCSKBW46 (->V8XX)
Jul 07 20:48:31-609295 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:31-609479 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:31-609672 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:31-609967 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 196)
Jul 07 20:48:31-610164 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:31-610351 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:31-610548 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:48:31-610737 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:31-610915 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:31-611102 util-scheduler-8620 DEBUG Canceling task: 2811 / 0x52cba38
Jul 07 20:48:31-611318 util-scheduler-8620 DEBUG Adding task: 2819 / 0x52cba38
Jul 07 20:48:31-611571 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:31-611769 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:31-611952 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:31-612154 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:31-612329 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:31-612504 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:31-612702 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:31-612906 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:31-613092 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:31-613300 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:31-613495 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:31-613749 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:31-613961 util-scheduler-8620 DEBUG Running task: 2818 / 0x46620a0
Jul 07 20:48:31-614687 util-8620 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:31-614932 util-scheduler-8620 DEBUG Adding task: 2820 / 0x4662248
Jul 07 20:48:31-615201 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-615397 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-615590 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-615781 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-615974 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-616165 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-616355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-616546 util-scheduler-8620 DEBUG Running task: 2820 / 0x4662248
Jul 07 20:48:31-616736 util-8620 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 20:48:31-616934 core-api-8620 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 20:48:31-617156 core-api-8620 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 20:48:31-617440 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection NCSKBW46 from V8XX
Jul 07 20:48:31-617683 cadet-con-8620 DEBUG   connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-617913 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-618122 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:31-618320 cadet-con-8620 DEBUG  PID 12 (expected 12+)
Jul 07 20:48:31-618500 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:31-618685 util-scheduler-8620 DEBUG Canceling task: 2786 / 0x52cba38
Jul 07 20:48:31-618909 util-scheduler-8620 DEBUG Adding task: 2821 / 0x52cba38
Jul 07 20:48:31-619089 cadet-con-8620 DEBUG   message for us!
Jul 07 20:48:31-619348 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:31-619565 util-scheduler-8620 DEBUG Adding task: 2822 / 0x4d5e5d8
Jul 07 20:48:31-619751 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:31-619919 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:31-623600 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:31-624983 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:31-625221 cadet-tun-8620 INFO   HMAC with key 9J1RHJ8Z
Jul 07 20:48:31-628273 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:48:31-628501 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:48:31-632121 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:48:31-632862 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:48:31-633073 cadet-tun-8620 INFO   HMAC with key 00000000
Jul 07 20:48:31-636326 cadet-8620 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 20:48:31-636587 cadet-8620 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 20:48:31-636836 cadet-con-8620 DEBUG GMC send FWD ACK on NCSKBW46 (->V8XX)
Jul 07 20:48:31-637014 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:48:31-637209 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:48:31-637410 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:48:31-637633 cadet-con-8620 DEBUG connection send FWD ack on NCSKBW46 (->V8XX)
Jul 07 20:48:31-637812 cadet-con-8620 DEBUG  ACK 76
Jul 07 20:48:31-637992 cadet-con-8620 DEBUG  last pid 12, last ack 75, qmax 11, q 0
Jul 07 20:48:31-638266 cadet-con-8620 INFO --> {               ACK} ( 76) on connection NCSKBW46 (->V8XX) (40 bytes)
Jul 07 20:48:31-638460 cadet-con-8620 DEBUG  ack 76
Jul 07 20:48:31-638640 cadet-con-8620 DEBUG   C_P+ 0x52cba38 0
Jul 07 20:48:31-638876 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-639084 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:31-639385 cadet-p2p-8620 INFO que {               ACK} ( 76) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK towards V8XX (size 40)
Jul 07 20:48:31-639585 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:48:31-639810 cadet-con-8620 DEBUG  checking sendability of BCK traffic on NCSKBW46 (->V8XX)
Jul 07 20:48:31-639994 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:31-640170 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:31-640379 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 20:48:31-640596 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 20:48:31-640823 util-scheduler-8620 DEBUG Adding task: 2823 / 0x4d6ff98
Jul 07 20:48:31-641005 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:31-641230 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:31-641410 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:31-641585 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d6ffc4
Jul 07 20:48:31-641825 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on NCSKBW46 (->V8XX)
Jul 07 20:48:31-642010 cadet-p2p-8620 DEBUG QQQ    payload , 76
Jul 07 20:48:31-642186 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:48:31-642385 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:31-642569 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-642782 util-scheduler-8620 DEBUG Adding task: 2824 / 0x46620a0
Jul 07 20:48:31-643053 util-scheduler-8620 DEBUG Checking readiness of task: 2824 / 0x46620a0
Jul 07 20:48:31-643252 util-scheduler-8620 DEBUG Checking readiness of task: 2822 / 0x4d5e5d8
Jul 07 20:48:31-643445 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-643636 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-643827 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-644018 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-644208 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-644398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-644587 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-644780 util-scheduler-8620 DEBUG Running task: 2822 / 0x4d5e5d8
Jul 07 20:48:31-644967 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:31-645146 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-645342 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-645589 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:31-645800 util-scheduler-8620 DEBUG Adding task: 2825 / 0x4d5e5d8
Jul 07 20:48:31-646004 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:48:31-646310 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:31-646577 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:31-646777 util-scheduler-8620 DEBUG Running task: 2823 / 0x4d6ff98
Jul 07 20:48:31-646990 util-scheduler-8620 DEBUG Adding task: 2826 / 0x4d6ff98
Jul 07 20:48:31-647213 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:31-647410 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:31-647626 util-scheduler-8620 DEBUG Adding task: 2827 / 0x46620a0
Jul 07 20:48:31-647873 util-scheduler-8620 DEBUG Checking readiness of task: 2827 / 0x46620a0
Jul 07 20:48:31-648069 util-scheduler-8620 DEBUG Checking readiness of task: 2825 / 0x4d5e5d8
Jul 07 20:48:31-648261 util-scheduler-8620 DEBUG Checking readiness of task: 2824 / 0x46620a0
Jul 07 20:48:31-648452 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-648642 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-648833 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-649024 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-649235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-649427 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-649617 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-649810 util-scheduler-8620 DEBUG Running task: 2825 / 0x4d5e5d8
Jul 07 20:48:31-649994 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:31-650170 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-650343 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-650555 util-8620 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 20:48:31-650795 util-8620 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:31-651006 util-scheduler-8620 DEBUG Running task: 2827 / 0x46620a0
Jul 07 20:48:31-651191 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:31-651367 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-651536 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-651716 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:31-651924 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:31-652113 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:31-652464 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:31-652717 util-scheduler-8620 DEBUG Checking readiness of task: 2824 / 0x46620a0
Jul 07 20:48:31-652913 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-653105 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-653318 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-653509 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-653699 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-653890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-654080 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-654273 util-scheduler-8620 DEBUG Running task: 2824 / 0x46620a0
Jul 07 20:48:31-654679 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:31-654910 util-scheduler-8620 DEBUG Adding task: 2828 / 0x4662248
Jul 07 20:48:31-655159 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-655353 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-655544 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-655734 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-655925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-656114 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-656305 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-656495 util-scheduler-8620 DEBUG Running task: 2828 / 0x4662248
Jul 07 20:48:31-656703 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:31-656900 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:31-657117 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:31-657335 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:31-657535 util-scheduler-8620 DEBUG Adding task: 2829 / 0x46620a0
Jul 07 20:48:31-657720 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-657919 util-scheduler-8620 DEBUG Adding task: 2830 / 0x46620a0
Jul 07 20:48:31-658160 util-scheduler-8620 DEBUG Checking readiness of task: 2830 / 0x46620a0
Jul 07 20:48:31-658355 util-scheduler-8620 DEBUG Checking readiness of task: 2829 / 0x46620a0
Jul 07 20:48:31-658547 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-658737 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-658927 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-659117 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-659306 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-659496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-659685 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-659878 util-scheduler-8620 DEBUG Running task: 2829 / 0x46620a0
Jul 07 20:48:31-660061 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:31-660238 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-660409 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-660593 util-scheduler-8620 DEBUG Canceling task: 2826 / 0x4d6ff98
Jul 07 20:48:31-660817 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 20:48:31-661035 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:31-661290 cadet-p2p-8620 DEBUG Checking 0x59e0d20 towards NCSKBW46 (->V8XX)
Jul 07 20:48:31-661524 cadet-p2p-8620 DEBUG   on connection NCSKBW46 (->V8XX) BCK
Jul 07 20:48:31-661703 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:48:31-661891 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:48:31-662157 cadet-p2p-8620 INFO snd {               ACK} ( 76) on connection NCSKBW46 (->V8XX) (0x52cba38) BCK (size 40)
Jul 07 20:48:31-662352 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:31-662531 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:31-662719 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:48:31-662893 cadet-con-8620 DEBUG  calling cont
Jul 07 20:48:31-663076 cadet-con-8620 DEBUG  C_P- 0x52cba38 1
Jul 07 20:48:31-663250 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:31-663432 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:48:31-663631 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:31-663805 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:31-663979 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:31-664178 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:31-664381 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 20:48:31-664566 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:48:31-664745 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:31-664935 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:48:31-666556 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:31-930573 util-scheduler-8620 DEBUG Checking readiness of task: 2830 / 0x46620a0
Jul 07 20:48:31-931308 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-931506 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-931703 util-scheduler-8620 DEBUG Checking readiness of task: 2002 / 0x4663d68
Jul 07 20:48:31-931899 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-932120 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-932312 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-932504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-932701 util-scheduler-8620 DEBUG Running task: 2002 / 0x4663d68
Jul 07 20:48:31-933124 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:48:31-933439 util-scheduler-8620 DEBUG Adding task: 2831 / 0x4663f10
Jul 07 20:48:31-933723 util-scheduler-8620 DEBUG Checking readiness of task: 2830 / 0x46620a0
Jul 07 20:48:31-933923 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-934118 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-934308 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-934503 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-934696 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-934887 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-935083 util-scheduler-8620 DEBUG Running task: 2830 / 0x46620a0
Jul 07 20:48:31-935501 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:31-935912 util-scheduler-8620 DEBUG Adding task: 2832 / 0x4662248
Jul 07 20:48:31-936186 util-scheduler-8620 DEBUG Running task: 2831 / 0x4663f10
Jul 07 20:48:31-936392 util-8620 DEBUG Received message of type 362 and size 40 from transport service.
Jul 07 20:48:31-936599 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-936825 util-scheduler-8620 DEBUG Adding task: 2833 / 0x4663d68
Jul 07 20:48:31-938569 transport-api-8620 DEBUG Receiving `DISCONNECT' message for `V8XX'.
Jul 07 20:48:31-942098 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:31-942372 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-942569 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-942761 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-942950 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-943143 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-943333 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-943525 util-scheduler-8620 DEBUG Running task: 2832 / 0x4662248
Jul 07 20:48:31-943718 util-8620 DEBUG Received message of type 68 and size 40 from core service.
Jul 07 20:48:31-943917 core-api-8620 DEBUG Processing message of type 68 and size 40 from core service
Jul 07 20:48:31-945690 core-api-8620 DEBUG Received notification about disconnect from `V8XX'.
Jul 07 20:48:31-949463 cadet-p2p-8620 INFO DISCONNECTED GN10 <= V8XX
Jul 07 20:48:31-953553 cadet-p2p-8620 DEBUG   notifying NCSKBW46 (->V8XX) due to V8XX
Jul 07 20:48:31-955257 cadet-con-8620 DEBUG  notify broken on NCSKBW46 (->V8XX) due to V8XX disconnect
Jul 07 20:48:31-955744 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-955960 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:31-956736 cadet-con-8620 DEBUG destroying connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-956929 cadet-con-8620 DEBUG  fc's f: 0x52cba3c, b: 0x52cba70
Jul 07 20:48:31-957113 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:48:31-957365 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-957607 cadet-con-8620 DEBUG  get next hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-957826 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:48:31-958077 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-958320 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-958535 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:31-958816 cadet-con-8620 DEBUG  get next hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-959034 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:48:31-959277 cadet-p2p-8620 DEBUG removing connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-959506 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:48:31-959719 cadet-p2p-8620 DEBUG peer GN10 ok, has 2 connections.
Jul 07 20:48:31-959977 cadet-con-8620 DEBUG  get prev hop NCSKBW46 (->V8XX) [1/2]
Jul 07 20:48:31-960193 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:31-960444 cadet-p2p-8620 DEBUG removing connection NCSKBW46 (->V8XX)
Jul 07 20:48:31-960658 cadet-p2p-8620 DEBUG from peer V8XX
Jul 07 20:48:31-960867 cadet-p2p-8620 DEBUG peer V8XX ok, has 1 connections.
Jul 07 20:48:31-961069 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:48:31-961362 cadet-tun-8620 DEBUG Removing connection NCSKBW46 (->V8XX) from tunnel V8XX
Jul 07 20:48:31-962470 cadet-tun-8620 DEBUG   no more connections, getting new ones
Jul 07 20:48:31-963071 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_READY => CADET_TUNNEL_SEARCHING
Jul 07 20:48:31-963682 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:48:31-963966 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:31-964163 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:31-964385 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:31-964604 util-scheduler-8620 DEBUG Adding task: 2834 / 0x46624e8
Jul 07 20:48:31-964820 cadet-p2p-8620 DEBUG   Starting DHT GET for peer V8XX
Jul 07 20:48:31-965024 cadet-dht-8620 DEBUG   Starting DHT GET for peer V8XX
Jul 07 20:48:31-965283 dht-api-8620 DEBUG Sending query for V8XXK9GA to DHT 0x46642c0
Jul 07 20:48:31-965526 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:48:31-965736 util-scheduler-8620 DEBUG Adding task: 2835 / 0x4665be0
Jul 07 20:48:31-966189 util-scheduler-8620 DEBUG Canceling task: 2821 / 0x52cba38
Jul 07 20:48:31-966399 util-scheduler-8620 DEBUG Canceling task: 2819 / 0x52cba38
Jul 07 20:48:31-966690 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:31-966898 util-scheduler-8620 DEBUG Adding task: 2836 / 0x4d5e5d8
Jul 07 20:48:31-973094 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-973341 util-scheduler-8620 DEBUG Adding task: 2837 / 0x46620a0
Jul 07 20:48:31-973619 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:31-973818 util-scheduler-8620 DEBUG Checking readiness of task: 2836 / 0x4d5e5d8
Jul 07 20:48:31-974011 util-scheduler-8620 DEBUG Checking readiness of task: 2835 / 0x4665be0
Jul 07 20:48:31-974204 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:31-974395 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-974586 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-974777 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-974967 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-975156 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-975347 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-975541 util-scheduler-8620 DEBUG Running task: 2835 / 0x4665be0
Jul 07 20:48:31-975728 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:48:31-975907 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-976081 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-976263 dht-api-8620 DEBUG Forwarded request of 88 bytes to DHT service
Jul 07 20:48:31-976461 util-8620 DEBUG Transmitting message of type 143 and size 88 to dht service.
Jul 07 20:48:31-976722 util-8620 DEBUG Connection transmitted 88/88 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:48:31-976937 util-scheduler-8620 DEBUG Running task: 2836 / 0x4d5e5d8
Jul 07 20:48:31-977122 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:31-977360 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-977535 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-977775 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:31-977983 util-scheduler-8620 DEBUG Adding task: 2838 / 0x4d5e5d8
Jul 07 20:48:31-978183 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:48:31-978427 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:31-978623 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:48:31-978820 util-scheduler-8620 DEBUG Running task: 2834 / 0x46624e8
Jul 07 20:48:31-979003 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:31-979194 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:31-979391 util-scheduler-8620 DEBUG Adding task: 2839 / 0x4663d68
Jul 07 20:48:31-979636 util-scheduler-8620 DEBUG Checking readiness of task: 2839 / 0x4663d68
Jul 07 20:48:31-979831 util-scheduler-8620 DEBUG Checking readiness of task: 2838 / 0x4d5e5d8
Jul 07 20:48:31-980023 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:31-980212 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:31-980405 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-980595 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-980786 util-scheduler-8620 DEBUG Checking readiness of task: 288 / 0x4665be0
Jul 07 20:48:31-980976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-981164 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-981378 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-981567 util-scheduler-8620 DEBUG Running task: 288 / 0x4665be0
Jul 07 20:48:31-981974 util-8620 DEBUG receive_ready read 715/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:48:31-982248 util-scheduler-8620 DEBUG Adding task: 2840 / 0x4665d88
Jul 07 20:48:31-982460 util-scheduler-8620 DEBUG Running task: 2838 / 0x4d5e5d8
Jul 07 20:48:31-982645 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:31-982821 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-982992 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-983210 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:48:31-983457 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:31-983669 util-scheduler-8620 DEBUG Running task: 2839 / 0x4663d68
Jul 07 20:48:31-983854 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:31-984028 util-8620 DEBUG process_notify is running
Jul 07 20:48:31-984198 util-8620 DEBUG client_notify is running
Jul 07 20:48:31-984373 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:31-984587 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:31-984803 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:31-985003 util-scheduler-8620 DEBUG Adding task: 2841 / 0x46624e8
Jul 07 20:48:31-985241 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:31-985444 util-scheduler-8620 DEBUG Canceling task: 2841 / 0x46624e8
Jul 07 20:48:31-985667 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:31-985864 util-scheduler-8620 DEBUG Adding task: 2842 / 0x46624e8
Jul 07 20:48:31-986049 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:31-986242 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:31-986490 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:31-986743 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:31-986954 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:31-987145 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:31-987335 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:31-987524 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:31-987714 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:31-987903 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:31-988092 util-scheduler-8620 DEBUG Running task: 2842 / 0x46624e8
Jul 07 20:48:31-988272 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:31-988461 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:31-988662 util-scheduler-8620 DEBUG Adding task: 2843 / 0x4663d68
Jul 07 20:48:31-988859 util-scheduler-8620 DEBUG Running task: 2840 / 0x4665d88
Jul 07 20:48:31-989050 util-8620 DEBUG Received message of type 145 and size 715 from dht service.
Jul 07 20:48:31-989271 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:31-989473 util-scheduler-8620 DEBUG Adding task: 2844 / 0x4665be0
Jul 07 20:48:31-989678 dht-api-8620 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46642c0
Jul 07 20:48:31-989887 dht-api-8620 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 20:48:31-991325 cadet-dht-8620 DEBUG    GET has 0 hops.
Jul 07 20:48:31-991633 cadet-dht-8620 DEBUG    PUT has 4 hops.
Jul 07 20:48:31-991855 cadet-dht-8620 DEBUG    Adding from PUT: STRN.
Jul 07 20:48:31-992072 cadet-dht-8620 DEBUG    Adding from PUT: WAKN.
Jul 07 20:48:31-992299 cadet-dht-8620 DEBUG    Adding from PUT: GN10.
Jul 07 20:48:31-992507 cadet-dht-8620 DEBUG    Adding from PUT: V8XX.
Jul 07 20:48:31-992821 cadet-dht-8620 DEBUG    (first of PUT: V8XX)
Jul 07 20:48:31-993002 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:48:31-993237 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:48:31-993443 cadet-dht-8620 DEBUG        4: V8XX
Jul 07 20:48:31-993747 cadet-dht-8620 INFO Got path from DHT:  GN10 V8XX
Jul 07 20:48:31-993967 cadet-dht-8620 DEBUG Got HELLO for V8XX
Jul 07 20:48:31-994196 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:48:31-994376 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:48:31-995305 cadet-p2p-8620 DEBUG  ... connect!
Jul 07 20:48:31-995857 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:48:31-996120 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:31-996315 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:31-996530 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:31-996733 util-scheduler-8620 DEBUG Adding task: 2845 / 0x46624e8
Jul 07 20:48:31-996959 cadet-p2p-8620 DEBUG set hello for V8XX
Jul 07 20:48:31-997671 cadet-p2p-8620 DEBUG  merge into 0x59dfc18 (491 bytes)
Jul 07 20:48:31-997937 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:31-998130 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:31-998324 util-scheduler-8620 DEBUG Canceling task: 2845 / 0x46624e8
Jul 07 20:48:31-998543 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:31-998741 util-scheduler-8620 DEBUG Adding task: 2846 / 0x46624e8
Jul 07 20:48:31-999333 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:31-999533 util-scheduler-8620 DEBUG Checking readiness of task: 2843 / 0x4663d68
Jul 07 20:48:31-999728 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:31-999919 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-000110 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-000308 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-000500 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-000712 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-000904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-001098 util-scheduler-8620 DEBUG Running task: 2843 / 0x4663d68
Jul 07 20:48:32-001312 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:32-001493 util-8620 DEBUG process_notify is running
Jul 07 20:48:32-001665 util-8620 DEBUG client_notify is running
Jul 07 20:48:32-001873 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:32-002079 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:48:32-002286 util-scheduler-8620 DEBUG Canceling task: 2846 / 0x46624e8
Jul 07 20:48:32-002506 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:32-002704 util-scheduler-8620 DEBUG Adding task: 2847 / 0x46624e8
Jul 07 20:48:32-002888 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:48:32-003085 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:48:32-003342 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:32-003595 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-003790 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-003982 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-004173 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-004364 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-004555 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-004745 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-004936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-005127 util-scheduler-8620 DEBUG Running task: 2847 / 0x46624e8
Jul 07 20:48:32-005340 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:32-005535 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:32-005741 util-scheduler-8620 DEBUG Adding task: 2848 / 0x4663d68
Jul 07 20:48:32-005984 util-scheduler-8620 DEBUG Checking readiness of task: 2848 / 0x4663d68
Jul 07 20:48:32-006181 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-006374 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-006566 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-006759 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-006950 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-007141 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-007332 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-007523 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-007716 util-scheduler-8620 DEBUG Running task: 2848 / 0x4663d68
Jul 07 20:48:32-007900 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:32-008076 util-8620 DEBUG process_notify is running
Jul 07 20:48:32-008246 util-8620 DEBUG client_notify is running
Jul 07 20:48:32-008420 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:32-008627 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:32-008839 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:32-009050 util-scheduler-8620 DEBUG Adding task: 2849 / 0x46624e8
Jul 07 20:48:32-009911 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:32-010120 util-scheduler-8620 DEBUG Canceling task: 2849 / 0x46624e8
Jul 07 20:48:32-010347 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:32-010563 util-scheduler-8620 DEBUG Adding task: 2850 / 0x46624e8
Jul 07 20:48:32-010749 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:32-010944 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:32-011197 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:32-011447 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-011642 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-011835 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-012028 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-012220 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-012411 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-012602 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-012792 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-012984 util-scheduler-8620 DEBUG Running task: 2850 / 0x46624e8
Jul 07 20:48:32-013165 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:32-013385 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:32-013585 util-scheduler-8620 DEBUG Adding task: 2851 / 0x4663d68
Jul 07 20:48:32-013826 util-scheduler-8620 DEBUG Checking readiness of task: 2851 / 0x4663d68
Jul 07 20:48:32-014020 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-014213 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-014405 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-014597 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-014788 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-014980 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-015170 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-015360 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-015552 util-scheduler-8620 DEBUG Running task: 2851 / 0x4663d68
Jul 07 20:48:32-015737 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:32-015913 util-8620 DEBUG process_notify is running
Jul 07 20:48:32-016083 util-8620 DEBUG client_notify is running
Jul 07 20:48:32-016257 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:32-016459 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:32-016671 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:32-016868 util-scheduler-8620 DEBUG Adding task: 2852 / 0x46624e8
Jul 07 20:48:32-017389 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:32-017595 util-scheduler-8620 DEBUG Canceling task: 2852 / 0x46624e8
Jul 07 20:48:32-017818 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:32-018019 util-scheduler-8620 DEBUG Adding task: 2853 / 0x46624e8
Jul 07 20:48:32-018203 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:32-018399 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:32-018652 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:32-018901 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-019097 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-019288 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-019481 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-019673 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-019884 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-020076 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-020267 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-020460 util-scheduler-8620 DEBUG Running task: 2853 / 0x46624e8
Jul 07 20:48:32-020644 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:32-020835 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:32-021034 util-scheduler-8620 DEBUG Adding task: 2854 / 0x4663d68
Jul 07 20:48:32-021299 util-scheduler-8620 DEBUG Checking readiness of task: 2854 / 0x4663d68
Jul 07 20:48:32-021495 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:32-021688 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:32-021880 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:32-022072 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:32-022263 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:32-022455 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:32-022647 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:32-022837 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:32-023030 util-scheduler-8620 DEBUG Running task: 2854 / 0x4663d68
Jul 07 20:48:32-023214 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:32-023391 util-8620 DEBUG process_notify is running
Jul 07 20:48:32-023561 util-8620 DEBUG client_notify is running
Jul 07 20:48:32-023764 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:32-024609 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:48:32-024836 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:32-025035 transport-api-8620 DEBUG Added 40 bytes of control message at 40
Jul 07 20:48:32-025254 transport-api-8620 DEBUG Transmitting 80 bytes to transport service
Jul 07 20:48:32-025453 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:48:32-025702 util-8620 DEBUG Connection transmitted 80/80 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:33-461551 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:33-461926 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:33-462122 util-scheduler-8620 DEBUG Checking readiness of task: 2833 / 0x4663d68
Jul 07 20:48:33-462318 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:33-462510 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:33-462702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:33-462892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:33-463082 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:33-463278 util-scheduler-8620 DEBUG Running task: 2833 / 0x4663d68
Jul 07 20:48:33-463698 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:48:33-463954 util-scheduler-8620 DEBUG Adding task: 2855 / 0x4663f10
Jul 07 20:48:33-464232 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:33-464426 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:33-464616 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:33-464807 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:33-464997 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:33-465186 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:33-465432 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:33-465624 util-scheduler-8620 DEBUG Running task: 2855 / 0x4663f10
Jul 07 20:48:33-465942 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:48:33-466172 util-scheduler-8620 DEBUG Adding task: 2856 / 0x4663f10
Jul 07 20:48:33-466400 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX'.
Jul 07 20:48:33-466612 transport-api-8620 DEBUG Creating entry for neighbour `V8XX'.
Jul 07 20:48:33-466808 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:48:33-467024 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 initialized with 1024 Bps and max carry 5
Jul 07 20:48:33-467257 util-scheduler-8620 DEBUG Adding task: 2857 / 0x59ecf18
Jul 07 20:48:33-467487 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX' with quota 10893
Jul 07 20:48:33-467680 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 bandwidth changed to 10893 Bps
Jul 07 20:48:33-467930 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 updated, have 1024 Bps, last update was 887 µs ago
Jul 07 20:48:33-468144 util-scheduler-8620 DEBUG Canceling task: 2857 / 0x59ecf18
Jul 07 20:48:33-468358 util-scheduler-8620 DEBUG Adding task: 2858 / 0x59ecf18
Jul 07 20:48:33-468599 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:33-468791 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:33-468981 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:33-469171 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:33-469383 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:33-469573 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:33-469762 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:33-469951 util-scheduler-8620 DEBUG Running task: 2856 / 0x4663f10
Jul 07 20:48:33-470140 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:48:33-470330 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:33-470544 util-scheduler-8620 DEBUG Adding task: 2859 / 0x4663d68
Jul 07 20:48:33-470734 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:48:33-470951 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 10893
Jul 07 20:48:33-471143 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 bandwidth changed to 10893 Bps
Jul 07 20:48:33-471371 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 updated, have 10893 Bps, last update was 3448 µs ago
Jul 07 20:48:33-471575 util-scheduler-8620 DEBUG Canceling task: 2858 / 0x59ecf18
Jul 07 20:48:33-471787 util-scheduler-8620 DEBUG Adding task: 2860 / 0x59ecf18
Jul 07 20:48:33-972972 util-scheduler-8620 DEBUG Checking readiness of task: 2859 / 0x4663d68
Jul 07 20:48:33-973314 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:33-973511 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:33-973705 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:33-973896 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:33-974088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:33-974278 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:33-974467 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:33-974662 util-scheduler-8620 DEBUG Running task: 2859 / 0x4663d68
Jul 07 20:48:33-975078 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:48:33-975324 util-scheduler-8620 DEBUG Adding task: 2861 / 0x4663f10
Jul 07 20:48:33-975591 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:33-975784 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:33-975976 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:33-976195 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:33-976386 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:33-976574 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:33-976764 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:33-976952 util-scheduler-8620 DEBUG Running task: 2861 / 0x4663f10
Jul 07 20:48:33-977144 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:48:33-977365 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:33-977575 util-scheduler-8620 DEBUG Adding task: 2862 / 0x4663d68
Jul 07 20:48:33-977760 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:48:33-977984 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 10893
Jul 07 20:48:33-978176 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 bandwidth changed to 10893 Bps
Jul 07 20:48:33-978421 util-bandwidth-8620 DEBUG Tracker 0x59ecf18 updated, have 10893 Bps, last update was 507 ms ago
Jul 07 20:48:33-978636 util-scheduler-8620 DEBUG Canceling task: 2860 / 0x59ecf18
Jul 07 20:48:33-978850 util-scheduler-8620 DEBUG Adding task: 2863 / 0x59ecf18
Jul 07 20:48:34-598869 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:34-599189 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:34-602801 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:34-603167 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:34-603363 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:34-603556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:34-603746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:34-603936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:34-604130 util-scheduler-8620 DEBUG Running task: 2813 / 0x52cbfb8
Jul 07 20:48:34-604373 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:34-604619 cadet-tun-8620 DEBUG  kx started 70 s ago
Jul 07 20:48:34-604827 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:34-605029 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:34-605455 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:34-605746 cadet-tun-8620 DEBUG  selected: connection NULL
Jul 07 20:48:34-606586 cadet-tun-8620 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:48:34-606856 cadet-tun-8620 WARNING TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:48:34-607050 cadet-tun-8620 WARNING TTT  kx_ctx 0x5789e78, rekey_task 0
Jul 07 20:48:34-607236 cadet-tun-8620 WARNING TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:48:34-607416 cadet-tun-8620 WARNING TTT  destroy 0
Jul 07 20:48:34-607587 cadet-tun-8620 WARNING TTT  channels:
Jul 07 20:48:34-607757 cadet-tun-8620 WARNING TTT  connections:
Jul 07 20:48:34-607925 cadet-tun-8620 WARNING TTT DEBUG TUNNEL END
Jul 07 20:48:34-608421 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:34-608635 util-scheduler-8620 DEBUG Adding task: 2864 / 0x52cbfb8
Jul 07 20:48:37-920594 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-920969 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-921166 util-scheduler-8620 DEBUG Checking readiness of task: 2837 / 0x46620a0
Jul 07 20:48:37-921393 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-921586 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-921780 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-921972 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-922163 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-922359 util-scheduler-8620 DEBUG Running task: 2837 / 0x46620a0
Jul 07 20:48:37-922822 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:37-923080 util-scheduler-8620 DEBUG Adding task: 2865 / 0x4662248
Jul 07 20:48:37-923361 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-923557 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-923748 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-923940 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-924131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-924321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-924511 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-924702 util-scheduler-8620 DEBUG Running task: 2865 / 0x4662248
Jul 07 20:48:37-924894 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:48:37-925095 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:48:37-925839 core-api-8620 DEBUG Received notification about connection from `V8XX'.
Jul 07 20:48:37-926118 cadet-p2p-8620 INFO CONNECTED GN10 <= V8XX
Jul 07 20:48:37-926406 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:37-926626 util-scheduler-8620 DEBUG Adding task: 2866 / 0x4d5e5d8
Jul 07 20:48:37-926849 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:48:37-927030 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:48:37-927205 cadet-p2p-8620 DEBUG   added last
Jul 07 20:48:37-927428 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:48:37-927693 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:37-927888 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:37-928105 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:37-928324 util-scheduler-8620 DEBUG Adding task: 2867 / 0x46624e8
Jul 07 20:48:37-928507 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:48:37-928813 cadet-p2p-8620 DEBUG   path to use:  GN10 V8XX
Jul 07 20:48:37-929275 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:37-929488 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:37-929728 cadet-con-8620 DEBUG  get prev hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:37-929937 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:48:37-930173 cadet-con-8620 DEBUG register neighbors for connection 2FDYFV0X (->V8XX)
Jul 07 20:48:37-930336 cadet-8620 DEBUG PATH:
Jul 07 20:48:37-930519 cadet-8620 DEBUG   GN10
Jul 07 20:48:37-930701 cadet-8620 DEBUG   V8XX
Jul 07 20:48:37-930859 cadet-8620 DEBUG END
Jul 07 20:48:37-931028 cadet-con-8620 DEBUG own pos 0
Jul 07 20:48:37-931254 cadet-con-8620 DEBUG putting connection 2FDYFV0X (->V8XX) to next peer 0x4d64970
Jul 07 20:48:37-931463 cadet-con-8620 DEBUG next peer 0x4d64970 V8XX
Jul 07 20:48:37-931693 cadet-con-8620 DEBUG putting connection 2FDYFV0X (->V8XX) to prev peer 0x4d5be88
Jul 07 20:48:37-931901 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:48:37-932129 cadet-p2p-8620 DEBUG adding connection 2FDYFV0X (->V8XX)
Jul 07 20:48:37-932328 cadet-p2p-8620 DEBUG to peer V8XX
Jul 07 20:48:37-932530 cadet-p2p-8620 DEBUG peer V8XX ok, has 0 connections.
Jul 07 20:48:37-932721 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:48:37-932895 cadet-p2p-8620 DEBUG result 1
Jul 07 20:48:37-933114 cadet-p2p-8620 DEBUG adding connection 2FDYFV0X (->V8XX)
Jul 07 20:48:37-933590 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:48:37-933796 cadet-p2p-8620 DEBUG peer GN10 ok, has 1 connections.
Jul 07 20:48:37-934115 cadet-p2p-8620 DEBUG  now has 2 connections.
Jul 07 20:48:37-934347 cadet-p2p-8620 DEBUG result 1
Jul 07 20:48:37-934675 cadet-tun-8620 DEBUG add connection 2FDYFV0X (->V8XX)
Jul 07 20:48:37-935030 cadet-tun-8620 DEBUG  to tunnel V8XX
Jul 07 20:48:37-935246 util-scheduler-8620 DEBUG Adding task: 2868 / 0x52cbfb8
Jul 07 20:48:37-935578 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 2FDYFV0X (->V8XX)  (100 bytes)
Jul 07 20:48:37-935950 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0 (create)
Jul 07 20:48:37-936334 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:37-936618 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:37-937160 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 100)
Jul 07 20:48:37-937697 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:37-937933 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:37-938120 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:37-938297 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:37-938505 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:48:37-938778 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:48:37-938996 util-scheduler-8620 DEBUG Adding task: 2869 / 0x59ee8a0
Jul 07 20:48:37-939176 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:37-939383 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:37-939561 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:37-939737 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:37-940058 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:37-940244 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:37-940422 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:48:37-940623 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:37-940839 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_SEARCHING => CADET_TUNNEL_WAITING
Jul 07 20:48:37-941082 cadet-con-8620 DEBUG Connection 2FDYFV0X (->V8XX) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:48:37-941300 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:37-941511 util-scheduler-8620 DEBUG Adding task: 2870 / 0x46620a0
Jul 07 20:48:37-941771 util-scheduler-8620 DEBUG Checking readiness of task: 2870 / 0x46620a0
Jul 07 20:48:37-941966 util-scheduler-8620 DEBUG Checking readiness of task: 2866 / 0x4d5e5d8
Jul 07 20:48:37-942158 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-942349 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-942540 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-942732 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-942922 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-943112 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-943301 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-943494 util-scheduler-8620 DEBUG Running task: 2866 / 0x4d5e5d8
Jul 07 20:48:37-943680 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:37-943859 util-8620 DEBUG process_notify is running
Jul 07 20:48:37-944032 util-8620 DEBUG client_notify is running
Jul 07 20:48:37-944260 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:48:37-944575 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:37-944928 util-scheduler-8620 DEBUG Running task: 2869 / 0x59ee8a0
Jul 07 20:48:37-945301 util-scheduler-8620 DEBUG Adding task: 2871 / 0x59ee8a0
Jul 07 20:48:37-945661 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:37-945934 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:37-946138 util-scheduler-8620 DEBUG Adding task: 2872 / 0x46620a0
Jul 07 20:48:37-946337 util-scheduler-8620 DEBUG Running task: 2868 / 0x52cbfb8
Jul 07 20:48:37-946536 util-scheduler-8620 DEBUG Running task: 2867 / 0x46624e8
Jul 07 20:48:37-946721 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:37-946930 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:37-947129 util-scheduler-8620 DEBUG Adding task: 2873 / 0x4663d68
Jul 07 20:48:37-947375 util-scheduler-8620 DEBUG Checking readiness of task: 2873 / 0x4663d68
Jul 07 20:48:37-947570 util-scheduler-8620 DEBUG Checking readiness of task: 2872 / 0x46620a0
Jul 07 20:48:37-947761 util-scheduler-8620 DEBUG Checking readiness of task: 2870 / 0x46620a0
Jul 07 20:48:37-947952 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-948143 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-948334 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-948525 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-948715 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-948906 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-949096 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-949313 util-scheduler-8620 DEBUG Running task: 2872 / 0x46620a0
Jul 07 20:48:37-949498 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:37-949676 util-8620 DEBUG process_notify is running
Jul 07 20:48:37-949845 util-8620 DEBUG client_notify is running
Jul 07 20:48:37-950024 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:37-950223 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:37-950412 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:37-950646 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:37-950857 util-scheduler-8620 DEBUG Running task: 2873 / 0x4663d68
Jul 07 20:48:37-951043 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:37-951218 util-8620 DEBUG process_notify is running
Jul 07 20:48:37-951388 util-8620 DEBUG client_notify is running
Jul 07 20:48:37-951565 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:37-951776 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:37-952000 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:37-952199 util-scheduler-8620 DEBUG Adding task: 2874 / 0x46624e8
Jul 07 20:48:37-952399 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:37-952602 util-scheduler-8620 DEBUG Canceling task: 2874 / 0x46624e8
Jul 07 20:48:37-952825 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:37-953022 util-scheduler-8620 DEBUG Adding task: 2875 / 0x46624e8
Jul 07 20:48:37-953231 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:37-953426 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:37-953665 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:37-954007 util-scheduler-8620 DEBUG Checking readiness of task: 2870 / 0x46620a0
Jul 07 20:48:37-954203 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-954395 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-954587 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-954778 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-954969 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-955159 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-955349 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-955541 util-scheduler-8620 DEBUG Running task: 2870 / 0x46620a0
Jul 07 20:48:37-955944 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:37-956190 util-scheduler-8620 DEBUG Adding task: 2876 / 0x4662248
Jul 07 20:48:37-956400 util-scheduler-8620 DEBUG Running task: 2875 / 0x46624e8
Jul 07 20:48:37-956582 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:37-956771 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:37-956970 util-scheduler-8620 DEBUG Adding task: 2877 / 0x4663d68
Jul 07 20:48:37-957228 util-scheduler-8620 DEBUG Checking readiness of task: 2877 / 0x4663d68
Jul 07 20:48:37-957424 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-957615 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-957806 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-957996 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-958187 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-958376 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-958565 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-958756 util-scheduler-8620 DEBUG Running task: 2877 / 0x4663d68
Jul 07 20:48:37-958940 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:37-959115 util-8620 DEBUG process_notify is running
Jul 07 20:48:37-959285 util-8620 DEBUG client_notify is running
Jul 07 20:48:37-959490 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:37-959692 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:48:37-959884 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:48:37-960078 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:48:37-960625 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:37-960980 util-scheduler-8620 DEBUG Running task: 2876 / 0x4662248
Jul 07 20:48:37-961269 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:37-961469 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:37-961687 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:37-961887 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:37-962087 util-scheduler-8620 DEBUG Adding task: 2878 / 0x46620a0
Jul 07 20:48:37-962272 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:37-962472 util-scheduler-8620 DEBUG Adding task: 2879 / 0x46620a0
Jul 07 20:48:37-962714 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:37-962909 util-scheduler-8620 DEBUG Checking readiness of task: 2878 / 0x46620a0
Jul 07 20:48:37-963100 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:37-963291 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:37-963482 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:37-963673 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:37-963864 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:37-964054 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:37-964243 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:37-964434 util-scheduler-8620 DEBUG Running task: 2878 / 0x46620a0
Jul 07 20:48:37-964618 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:37-964793 util-8620 DEBUG process_notify is running
Jul 07 20:48:37-964963 util-8620 DEBUG client_notify is running
Jul 07 20:48:37-965147 util-scheduler-8620 DEBUG Canceling task: 2871 / 0x59ee8a0
Jul 07 20:48:37-965395 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:48:37-965613 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:37-965848 cadet-p2p-8620 DEBUG Checking 0x59f0160 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:37-966099 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:37-966279 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:48:37-966450 cadet-p2p-8620 DEBUG   path create
Jul 07 20:48:37-966620 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:48:37-966802 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:48:37-967067 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 100)
Jul 07 20:48:37-967260 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:37-967441 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:37-968143 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:48:37-968395 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:37-968609 util-scheduler-8620 DEBUG Adding task: 2880 / 0x59e8808
Jul 07 20:48:37-968853 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:48:37-969027 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:37-969234 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:48:37-969437 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:37-969614 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:37-969789 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:37-969987 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:37-970192 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:48:37-970377 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:48:37-970556 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:37-970749 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:48:37-970986 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:38-922180 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-922557 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-922753 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-922945 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-923137 util-scheduler-8620 DEBUG Checking readiness of task: 2130 / 0x4d5c418
Jul 07 20:48:38-923331 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-923521 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-923710 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-923908 util-scheduler-8620 DEBUG Running task: 2130 / 0x4d5c418
Jul 07 20:48:38-924305 util-8620 DEBUG receive_ready read 48/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:48:38-924518 util-8620 DEBUG Server receives 48 bytes from `<unbound UNIX client>'.
Jul 07 20:48:38-924712 util-8620 DEBUG Server-mst receives 48 bytes with 0 bytes already in private buffer
Jul 07 20:48:38-924899 util-8620 DEBUG Server-mst has 48 bytes left in inbound buffer
Jul 07 20:48:38-925083 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:48:38-925294 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:48:38-925527 util-scheduler-8620 DEBUG Adding task: 2881 / 0x4d5c578
Jul 07 20:48:38-925719 cadet-loc-8620 DEBUG 
Jul 07 20:48:38-925889 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:48:38-926062 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:48:38-926285 cadet-chn-8620 DEBUG   towards V8XX:19
Jul 07 20:48:38-926512 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:48:38-926787 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:38-926980 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:38-927199 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:38-927401 util-scheduler-8620 DEBUG Adding task: 2882 / 0x46624e8
Jul 07 20:48:38-927584 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:48:38-928920 cadet-p2p-8620 DEBUG   but is NULL, all paths are in use
Jul 07 20:48:38-929357 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:48:38-929583 util-scheduler-8620 DEBUG Adding task: 2883 / 0x4d5e5d8
Jul 07 20:48:38-929797 cadet-tun-8620 DEBUG Adding channel 0x5845ae0 to tunnel 0x52cbfb8
Jul 07 20:48:38-929996 cadet-tun-8620 DEBUG  adding 0x59f3cd0 to (nil)
Jul 07 20:48:38-930247 cadet-chn-8620 DEBUG CREATED CHANNEL V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:48:38-930503 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:48:38-930724 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:48:38-930929 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:48:38-931111 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:48:38-931296 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 2864
Jul 07 20:48:38-931476 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:48:38-931654 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:48:38-931823 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:48:38-932039 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:48:38-932217 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:48:38-932456 cadet-tun-8620 DEBUG TTT  - 2FDYFV0X (->V8XX) [1] buf: 11/11 (qn 0/0)
Jul 07 20:48:38-932641 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:48:38-932842 cadet-tun-8620 DEBUG queue data on Tunnel V8XX
Jul 07 20:48:38-933041 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:48:38-933238 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:48:38-933422 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 2864
Jul 07 20:48:38-933601 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:48:38-933776 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:48:38-933944 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:48:38-934158 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:48:38-934331 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:48:38-934558 cadet-tun-8620 DEBUG TTT  - 2FDYFV0X (->V8XX) [1] buf: 11/11 (qn 0/0)
Jul 07 20:48:38-934743 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:48:38-934951 util-scheduler-8620 DEBUG Canceling task: 2881 / 0x4d5c578
Jul 07 20:48:38-935145 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:48:38-935327 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:48:38-935532 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:48:38-935740 util-scheduler-8620 DEBUG Adding task: 2884 / 0x4d5c418
Jul 07 20:48:38-935941 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:48:38-936232 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-936428 util-scheduler-8620 DEBUG Checking readiness of task: 2883 / 0x4d5e5d8
Jul 07 20:48:38-936619 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-936809 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-936997 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-937207 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-937399 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-937589 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-937776 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-937969 util-scheduler-8620 DEBUG Running task: 2883 / 0x4d5e5d8
Jul 07 20:48:38-938155 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:48:38-938332 util-8620 DEBUG process_notify is running
Jul 07 20:48:38-938505 util-8620 DEBUG client_notify is running
Jul 07 20:48:38-938731 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:48:38-939008 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:48:38-939218 util-scheduler-8620 DEBUG Running task: 2882 / 0x46624e8
Jul 07 20:48:38-939403 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:38-939594 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:38-939795 util-scheduler-8620 DEBUG Adding task: 2885 / 0x4663d68
Jul 07 20:48:38-940036 util-scheduler-8620 DEBUG Checking readiness of task: 2885 / 0x4663d68
Jul 07 20:48:38-940229 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-940419 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-940610 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-940799 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-940989 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-941178 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-941387 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-941575 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-941765 util-scheduler-8620 DEBUG Running task: 2885 / 0x4663d68
Jul 07 20:48:38-941948 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:38-942127 util-8620 DEBUG process_notify is running
Jul 07 20:48:38-942295 util-8620 DEBUG client_notify is running
Jul 07 20:48:38-942471 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:38-942682 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:38-942894 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:38-943096 util-scheduler-8620 DEBUG Adding task: 2886 / 0x46624e8
Jul 07 20:48:38-943296 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:38-943494 util-scheduler-8620 DEBUG Canceling task: 2886 / 0x46624e8
Jul 07 20:48:38-943712 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:38-943908 util-scheduler-8620 DEBUG Adding task: 2887 / 0x46624e8
Jul 07 20:48:38-944090 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:38-944283 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:38-944530 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:38-944783 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-944976 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-945167 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-945400 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-945590 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-945780 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-945969 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-946157 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-946346 util-scheduler-8620 DEBUG Running task: 2887 / 0x46624e8
Jul 07 20:48:38-946524 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:38-946713 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:38-946912 util-scheduler-8620 DEBUG Adding task: 2888 / 0x4663d68
Jul 07 20:48:38-947150 util-scheduler-8620 DEBUG Checking readiness of task: 2888 / 0x4663d68
Jul 07 20:48:38-947342 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-947532 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-947721 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-947910 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-948117 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-948319 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-948507 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-948696 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-948886 util-scheduler-8620 DEBUG Running task: 2888 / 0x4663d68
Jul 07 20:48:38-949070 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:38-949263 util-8620 DEBUG process_notify is running
Jul 07 20:48:38-949433 util-8620 DEBUG client_notify is running
Jul 07 20:48:38-949639 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:38-949837 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:48:38-950028 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:48:38-950222 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:48:38-950466 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:38-968722 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-968922 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-969115 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-969325 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-969516 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-969706 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-969896 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-970084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-970274 util-scheduler-8620 DEBUG Running task: 2880 / 0x59e8808
Jul 07 20:48:38-970511 cadet-con-8620 DEBUG FWD keepalive for 2FDYFV0X (->V8XX)
Jul 07 20:48:38-970689 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:48:38-970931 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 2FDYFV0X (->V8XX)  (100 bytes)
Jul 07 20:48:38-971129 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0 (create)
Jul 07 20:48:38-971362 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:38-971571 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:38-971872 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 100)
Jul 07 20:48:38-972070 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:38-972299 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:38-972482 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:38-972658 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:38-972864 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:48:38-973079 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:48:38-973319 util-scheduler-8620 DEBUG Adding task: 2889 / 0x59ee8a0
Jul 07 20:48:38-973499 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:38-973703 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:38-973878 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:38-974053 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:38-974291 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:38-974475 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:38-974650 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:48:38-974849 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:38-975084 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-975276 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-975467 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-975674 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-975864 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-976053 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-976242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-976430 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-976619 util-scheduler-8620 DEBUG Running task: 2889 / 0x59ee8a0
Jul 07 20:48:38-976826 util-scheduler-8620 DEBUG Adding task: 2890 / 0x59ee8a0
Jul 07 20:48:38-977048 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:38-977265 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:38-977466 util-scheduler-8620 DEBUG Adding task: 2891 / 0x46620a0
Jul 07 20:48:38-977706 util-scheduler-8620 DEBUG Checking readiness of task: 2891 / 0x46620a0
Jul 07 20:48:38-977899 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:38-978090 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:38-978280 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:38-978469 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:38-978660 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:38-978850 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:38-979039 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:38-979228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:38-979419 util-scheduler-8620 DEBUG Running task: 2891 / 0x46620a0
Jul 07 20:48:38-979602 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:38-979779 util-8620 DEBUG process_notify is running
Jul 07 20:48:38-979948 util-8620 DEBUG client_notify is running
Jul 07 20:48:38-980127 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:38-980323 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:38-980513 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:38-980758 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:39-044977 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-045233 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-045433 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-045630 util-scheduler-8620 DEBUG Checking readiness of task: 2844 / 0x4665be0
Jul 07 20:48:39-045825 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-046024 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-046220 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-046416 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-046612 util-scheduler-8620 DEBUG Running task: 2844 / 0x4665be0
Jul 07 20:48:39-047025 util-8620 DEBUG receive_ready read 747/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:48:39-047323 util-scheduler-8620 DEBUG Adding task: 2892 / 0x4665d88
Jul 07 20:48:39-047587 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-047783 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-047977 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-048171 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-048363 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-048558 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-048749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-048963 util-scheduler-8620 DEBUG Running task: 2892 / 0x4665d88
Jul 07 20:48:39-049159 util-8620 DEBUG Received message of type 145 and size 747 from dht service.
Jul 07 20:48:39-049388 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:39-049601 util-scheduler-8620 DEBUG Adding task: 2893 / 0x4665be0
Jul 07 20:48:39-049810 dht-api-8620 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46642c0
Jul 07 20:48:39-050022 dht-api-8620 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 20:48:39-051467 cadet-dht-8620 DEBUG    GET has 1 hops.
Jul 07 20:48:39-051693 cadet-dht-8620 DEBUG    Adding from GET: KNAS.
Jul 07 20:48:39-051888 cadet-dht-8620 DEBUG    PUT has 4 hops.
Jul 07 20:48:39-052095 cadet-dht-8620 DEBUG    Adding from PUT: STRN.
Jul 07 20:48:39-052307 cadet-dht-8620 DEBUG    Adding from PUT: TZQE.
Jul 07 20:48:39-052537 cadet-dht-8620 DEBUG    Adding from PUT: GN10.
Jul 07 20:48:39-052973 cadet-dht-8620 DEBUG    Adding from PUT: V8XX.
Jul 07 20:48:39-053184 cadet-dht-8620 DEBUG    (first of GET: KNAS)
Jul 07 20:48:39-053417 cadet-dht-8620 DEBUG    (first of PUT: V8XX)
Jul 07 20:48:39-053594 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:48:39-053799 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:48:39-054004 cadet-dht-8620 DEBUG        4: V8XX
Jul 07 20:48:39-054311 cadet-dht-8620 INFO Got path from DHT:  GN10 V8XX
Jul 07 20:48:39-054531 cadet-dht-8620 DEBUG Got HELLO for V8XX
Jul 07 20:48:39-054761 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:48:39-054943 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:48:39-055171 cadet-p2p-8620 DEBUG set hello for V8XX
Jul 07 20:48:39-055686 cadet-p2p-8620 DEBUG  merge into 0x59f8410 (491 bytes)
Jul 07 20:48:39-055953 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:48:39-056148 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:48:39-056367 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:39-056573 util-scheduler-8620 DEBUG Adding task: 2894 / 0x46624e8
Jul 07 20:48:39-056837 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-057035 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-057250 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-057444 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-057638 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-057829 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-058020 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-058211 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-058403 util-scheduler-8620 DEBUG Running task: 2894 / 0x46624e8
Jul 07 20:48:39-058591 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:39-058788 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:39-058993 util-scheduler-8620 DEBUG Adding task: 2895 / 0x4663d68
Jul 07 20:48:39-059236 util-scheduler-8620 DEBUG Checking readiness of task: 2895 / 0x4663d68
Jul 07 20:48:39-059432 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-059624 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-059817 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-060009 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-060201 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-060393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-060584 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-060775 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-060967 util-scheduler-8620 DEBUG Running task: 2895 / 0x4663d68
Jul 07 20:48:39-061174 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:39-061379 util-8620 DEBUG process_notify is running
Jul 07 20:48:39-061553 util-8620 DEBUG client_notify is running
Jul 07 20:48:39-061730 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:48:39-061940 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:48:39-062153 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:39-062350 util-scheduler-8620 DEBUG Adding task: 2896 / 0x46624e8
Jul 07 20:48:39-062551 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:48:39-062753 util-scheduler-8620 DEBUG Canceling task: 2896 / 0x46624e8
Jul 07 20:48:39-062976 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:48:39-063175 util-scheduler-8620 DEBUG Adding task: 2897 / 0x46624e8
Jul 07 20:48:39-063359 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:48:39-063556 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:48:39-063820 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:39-064074 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-064268 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-064461 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-064653 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-064845 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-065037 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-065248 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-065441 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-065632 util-scheduler-8620 DEBUG Running task: 2897 / 0x46624e8
Jul 07 20:48:39-065813 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:48:39-066005 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:48:39-066204 util-scheduler-8620 DEBUG Adding task: 2898 / 0x4663d68
Jul 07 20:48:39-066444 util-scheduler-8620 DEBUG Checking readiness of task: 2898 / 0x4663d68
Jul 07 20:48:39-066639 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-066832 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-067024 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-067217 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-067407 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-067600 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-067791 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-067982 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-068173 util-scheduler-8620 DEBUG Running task: 2898 / 0x4663d68
Jul 07 20:48:39-068358 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:48:39-068534 util-8620 DEBUG process_notify is running
Jul 07 20:48:39-068708 util-8620 DEBUG client_notify is running
Jul 07 20:48:39-068913 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:48:39-069114 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:48:39-069330 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:48:39-069527 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:48:39-069772 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:48:39-484858 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-485240 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-485437 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-485631 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-485823 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-486013 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-486204 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-486394 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-486586 util-scheduler-8620 DEBUG Running task: 2863 / 0x59ecf18
Jul 07 20:48:39-608921 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-609311 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-609506 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-609699 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-609890 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-610081 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-610271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-610459 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-610651 util-scheduler-8620 DEBUG Running task: 2864 / 0x52cbfb8
Jul 07 20:48:39-610886 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:39-611146 cadet-tun-8620 DEBUG  kx started 75 s ago
Jul 07 20:48:39-611354 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:39-611554 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:39-611757 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:39-611994 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 1
Jul 07 20:48:39-612174 cadet-tun-8620 DEBUG  selected: connection NULL
Jul 07 20:48:39-612379 cadet-tun-8620 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:48:39-612561 cadet-tun-8620 WARNING TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:48:39-612743 cadet-tun-8620 WARNING TTT  kx_ctx 0x5789e78, rekey_task 0
Jul 07 20:48:39-612927 cadet-tun-8620 WARNING TTT  tq_head 0x59f45c0, tq_tail 0x59f45c0
Jul 07 20:48:39-613107 cadet-tun-8620 WARNING TTT  destroy 0
Jul 07 20:48:39-613301 cadet-tun-8620 WARNING TTT  channels:
Jul 07 20:48:39-613523 cadet-tun-8620 WARNING TTT  - V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:48:39-613698 cadet-tun-8620 WARNING TTT  connections:
Jul 07 20:48:39-613936 cadet-tun-8620 WARNING TTT  - 2FDYFV0X (->V8XX) [1] buf: 11/11 (qn 0/0)
Jul 07 20:48:39-614122 cadet-tun-8620 WARNING TTT DEBUG TUNNEL END
Jul 07 20:48:39-614366 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:39-614573 util-scheduler-8620 DEBUG Adding task: 2899 / 0x52cbfb8
Jul 07 20:48:39-930411 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-930823 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-931035 util-scheduler-8620 DEBUG Checking readiness of task: 2879 / 0x46620a0
Jul 07 20:48:39-931232 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-931431 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-931635 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-931843 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-932042 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-932238 util-scheduler-8620 DEBUG Running task: 2879 / 0x46620a0
Jul 07 20:48:39-932663 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:39-932920 util-scheduler-8620 DEBUG Adding task: 2900 / 0x4662248
Jul 07 20:48:39-933227 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-933458 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-933649 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-933839 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-934027 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-934214 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-934402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-934591 util-scheduler-8620 DEBUG Running task: 2900 / 0x4662248
Jul 07 20:48:39-934781 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:39-934981 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:39-935211 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:39-935417 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:39-935624 util-scheduler-8620 DEBUG Adding task: 2901 / 0x46620a0
Jul 07 20:48:39-935817 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:39-936028 util-scheduler-8620 DEBUG Adding task: 2902 / 0x46620a0
Jul 07 20:48:39-936288 util-scheduler-8620 DEBUG Checking readiness of task: 2902 / 0x46620a0
Jul 07 20:48:39-936487 util-scheduler-8620 DEBUG Checking readiness of task: 2901 / 0x46620a0
Jul 07 20:48:39-936683 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:39-936881 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:39-937074 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:39-937291 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:39-937491 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:39-937683 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:39-937875 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:39-938070 util-scheduler-8620 DEBUG Running task: 2901 / 0x46620a0
Jul 07 20:48:39-938256 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:39-938435 util-8620 DEBUG process_notify is running
Jul 07 20:48:39-938606 util-8620 DEBUG client_notify is running
Jul 07 20:48:39-938795 util-scheduler-8620 DEBUG Canceling task: 2890 / 0x59ee8a0
Jul 07 20:48:39-939028 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:48:39-939249 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:39-939488 cadet-p2p-8620 DEBUG Checking 0x59f6590 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:39-939720 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:39-939899 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:48:39-940067 cadet-p2p-8620 DEBUG   path create
Jul 07 20:48:39-940238 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:48:39-940416 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:48:39-940684 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 100)
Jul 07 20:48:39-940876 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:39-941054 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:39-941264 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:48:39-941445 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:39-941660 util-scheduler-8620 DEBUG Adding task: 2903 / 0x59e8808
Jul 07 20:48:39-941897 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:48:39-942067 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:39-942247 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:48:39-942449 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:39-942625 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:39-942799 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:39-942997 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:39-943201 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:48:39-943409 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:48:39-943591 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:39-943782 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:48:39-944507 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:41-733138 util-scheduler-8620 DEBUG Checking readiness of task: 2902 / 0x46620a0
Jul 07 20:48:41-733541 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-733738 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-733931 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-734122 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-734313 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-734503 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-734692 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-734885 util-scheduler-8620 DEBUG Running task: 2596 / 0x4d68be8
Jul 07 20:48:41-735159 cadet-con-8620 DEBUG FWD keepalive for KT5Q8VM8 (->P00P)
Jul 07 20:48:41-735337 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:48:41-735585 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection KT5Q8VM8 (->P00P)  (100 bytes)
Jul 07 20:48:41-735775 cadet-con-8620 DEBUG   C_P+ 0x4d68be8 0 (create)
Jul 07 20:48:41-736007 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:48:41-736216 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:48:41-736522 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD towards P00P (size 100)
Jul 07 20:48:41-736724 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:41-736954 cadet-con-8620 DEBUG  checking sendability of FWD traffic on KT5Q8VM8 (->P00P)
Jul 07 20:48:41-737139 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:41-737339 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:41-737561 cadet-p2p-8620 DEBUG calling core tmt rdy towards P00P for 100 bytes
Jul 07 20:48:41-737781 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `P00P'
Jul 07 20:48:41-738011 util-scheduler-8620 DEBUG Adding task: 2904 / 0x4d683b0
Jul 07 20:48:41-738197 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:41-738406 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:48:41-738585 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:41-738763 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d683dc
Jul 07 20:48:41-739096 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on KT5Q8VM8 (->P00P)
Jul 07 20:48:41-739333 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:41-739510 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:48:41-739712 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:48:41-739975 util-scheduler-8620 DEBUG Checking readiness of task: 2902 / 0x46620a0
Jul 07 20:48:41-740168 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-740359 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-740549 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-740739 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-740928 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-741116 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-741327 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-741517 util-scheduler-8620 DEBUG Running task: 2904 / 0x4d683b0
Jul 07 20:48:41-741726 util-scheduler-8620 DEBUG Adding task: 2905 / 0x4d683b0
Jul 07 20:48:41-741949 core-api-8620 DEBUG Adding SEND REQUEST for peer `P00P' to message queue
Jul 07 20:48:41-742183 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:41-742393 util-scheduler-8620 DEBUG Adding task: 2906 / 0x46620a0
Jul 07 20:48:41-742636 util-scheduler-8620 DEBUG Checking readiness of task: 2906 / 0x46620a0
Jul 07 20:48:41-742833 util-scheduler-8620 DEBUG Checking readiness of task: 2902 / 0x46620a0
Jul 07 20:48:41-743023 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-743213 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-743402 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-743592 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-743781 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-743968 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-744158 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-744349 util-scheduler-8620 DEBUG Running task: 2906 / 0x46620a0
Jul 07 20:48:41-744532 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:41-744711 util-8620 DEBUG process_notify is running
Jul 07 20:48:41-744882 util-8620 DEBUG client_notify is running
Jul 07 20:48:41-745062 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:41-745279 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:41-745471 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:41-745787 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:41-746037 util-scheduler-8620 DEBUG Checking readiness of task: 2902 / 0x46620a0
Jul 07 20:48:41-746230 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-746421 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-746610 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-746800 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-746988 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-747177 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-747365 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-747555 util-scheduler-8620 DEBUG Running task: 2902 / 0x46620a0
Jul 07 20:48:41-747958 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:41-748187 util-scheduler-8620 DEBUG Adding task: 2907 / 0x4662248
Jul 07 20:48:41-748433 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-748625 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-748814 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-749003 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-749212 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-749402 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-749590 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-749779 util-scheduler-8620 DEBUG Running task: 2907 / 0x4662248
Jul 07 20:48:41-749972 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:41-750172 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:41-750394 core-api-8620 DEBUG Received notification about transmission readiness to `P00P'.
Jul 07 20:48:41-750593 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:41-750795 util-scheduler-8620 DEBUG Adding task: 2908 / 0x46620a0
Jul 07 20:48:41-750981 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:41-751187 util-scheduler-8620 DEBUG Adding task: 2909 / 0x46620a0
Jul 07 20:48:41-751460 util-scheduler-8620 DEBUG Checking readiness of task: 2909 / 0x46620a0
Jul 07 20:48:41-751657 util-scheduler-8620 DEBUG Checking readiness of task: 2908 / 0x46620a0
Jul 07 20:48:41-751851 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-752040 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-752233 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-752424 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-752614 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-752805 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-752995 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-753184 util-scheduler-8620 DEBUG Running task: 2908 / 0x46620a0
Jul 07 20:48:41-753392 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:41-753567 util-8620 DEBUG process_notify is running
Jul 07 20:48:41-753737 util-8620 DEBUG client_notify is running
Jul 07 20:48:41-753923 util-scheduler-8620 DEBUG Canceling task: 2905 / 0x4d683b0
Jul 07 20:48:41-754149 core-api-8620 DEBUG Transmitting SEND request to `P00P' with 100 bytes.
Jul 07 20:48:41-754366 cadet-p2p-8620 DEBUG Queue send towards P00P (max 196)
Jul 07 20:48:41-754598 cadet-p2p-8620 DEBUG Checking 0x59fd740 towards KT5Q8VM8 (->P00P)
Jul 07 20:48:41-754830 cadet-p2p-8620 DEBUG   on connection KT5Q8VM8 (->P00P) FWD
Jul 07 20:48:41-755007 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:48:41-755176 cadet-p2p-8620 DEBUG   path create
Jul 07 20:48:41-755343 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:48:41-755523 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:48:41-755783 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection KT5Q8VM8 (->P00P) (0x4d68be8) FWD (size 100)
Jul 07 20:48:41-755975 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:41-756154 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:41-756341 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:48:41-756520 cadet-con-8620 DEBUG  C_P- 0x4d68be8 1
Jul 07 20:48:41-756730 util-scheduler-8620 DEBUG Adding task: 2910 / 0x4d68be8
Jul 07 20:48:41-756967 cadet-con-8620 DEBUG next keepalive in 64 s
Jul 07 20:48:41-757137 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:41-757336 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:48:41-757535 cadet-p2p-8620 DEBUG QQQ Message queue towards P00P
Jul 07 20:48:41-757709 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:41-757882 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:41-758079 cadet-p2p-8620 DEBUG QQQ End queue towards P00P
Jul 07 20:48:41-758282 core-api-8620 DEBUG Transmitting SEND request to `P00P' yielded 100 bytes.
Jul 07 20:48:41-758465 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:48:41-758642 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:41-758831 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:48:41-759557 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:41-941949 util-scheduler-8620 DEBUG Checking readiness of task: 2909 / 0x46620a0
Jul 07 20:48:41-942222 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-942417 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-942610 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-942801 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-942991 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-943180 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-943369 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-943558 util-scheduler-8620 DEBUG Running task: 2903 / 0x59e8808
Jul 07 20:48:41-943836 cadet-con-8620 DEBUG FWD keepalive for 2FDYFV0X (->V8XX)
Jul 07 20:48:41-944013 cadet-con-8620 DEBUG sending connection recreate
Jul 07 20:48:41-944255 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 2FDYFV0X (->V8XX)  (100 bytes)
Jul 07 20:48:41-944444 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0 (create)
Jul 07 20:48:41-944676 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:41-944883 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:41-945181 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 100)
Jul 07 20:48:41-945402 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:41-945625 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:41-945807 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:41-945982 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:41-946187 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:48:41-946401 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:48:41-946619 util-scheduler-8620 DEBUG Adding task: 2911 / 0x59ee8a0
Jul 07 20:48:41-946798 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:41-947001 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:41-947175 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:41-947350 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:41-947587 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:41-947770 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:41-947944 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:48:41-948142 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:41-948384 util-scheduler-8620 DEBUG Checking readiness of task: 2909 / 0x46620a0
Jul 07 20:48:41-948577 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-948766 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-948954 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-949144 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-949357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-949546 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-949733 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-949922 util-scheduler-8620 DEBUG Running task: 2911 / 0x59ee8a0
Jul 07 20:48:41-950126 util-scheduler-8620 DEBUG Adding task: 2912 / 0x59ee8a0
Jul 07 20:48:41-950346 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:41-950546 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:41-950750 util-scheduler-8620 DEBUG Adding task: 2913 / 0x46620a0
Jul 07 20:48:41-950989 util-scheduler-8620 DEBUG Checking readiness of task: 2913 / 0x46620a0
Jul 07 20:48:41-951183 util-scheduler-8620 DEBUG Checking readiness of task: 2909 / 0x46620a0
Jul 07 20:48:41-951373 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:41-951562 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:41-951751 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:41-951940 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:41-952130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:41-952320 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:41-952510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:41-952700 util-scheduler-8620 DEBUG Running task: 2913 / 0x46620a0
Jul 07 20:48:41-952886 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:41-953064 util-8620 DEBUG process_notify is running
Jul 07 20:48:41-953257 util-8620 DEBUG client_notify is running
Jul 07 20:48:41-953455 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:41-953658 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:41-953849 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:41-954150 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:42-389297 util-scheduler-8620 DEBUG Checking readiness of task: 2909 / 0x46620a0
Jul 07 20:48:42-389632 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:42-389830 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:42-390023 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:42-390215 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:42-390407 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:42-390598 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:42-390788 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:42-390983 util-scheduler-8620 DEBUG Running task: 2909 / 0x46620a0
Jul 07 20:48:42-391399 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:42-391648 util-scheduler-8620 DEBUG Adding task: 2914 / 0x4662248
Jul 07 20:48:42-391918 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:42-392111 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:42-392302 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:42-392493 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:42-392683 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:42-392874 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:42-393064 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:42-393278 util-scheduler-8620 DEBUG Running task: 2914 / 0x4662248
Jul 07 20:48:42-393473 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:48:42-393674 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:48:42-393912 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:48:42-394179 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 2FDYFV0X from V8XX
Jul 07 20:48:42-394396 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:48:42-394637 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:42-394845 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:42-395028 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:48:42-395260 cadet-con-8620 DEBUG Connection 2FDYFV0X (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:48:42-395446 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:42-395653 util-scheduler-8620 DEBUG Adding task: 2915 / 0x59e8808
Jul 07 20:48:42-395902 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:48:42-396084 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:48:42-396274 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:48:42-396448 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:42-396648 util-scheduler-8620 DEBUG Adding task: 2916 / 0x59e8808
Jul 07 20:48:42-396887 cadet-con-8620 DEBUG next keepalive in 4 s
Jul 07 20:48:42-397119 cadet-con-8620 DEBUG Connection 2FDYFV0X (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:48:42-397381 cadet-con-8620 INFO ===> {           BCK ACK} on connection 2FDYFV0X (->V8XX)
Jul 07 20:48:42-397617 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:42-397823 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:42-398132 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 36)
Jul 07 20:48:42-398411 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:42-398639 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:42-398822 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:42-398997 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:42-399199 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:48:42-399403 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:42-399578 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:48:42-399753 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:42-399991 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:42-400175 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:42-400351 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:48:42-400585 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:42-400766 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:42-400940 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:48:42-401136 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:42-401370 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:48:42-401933 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:42-402157 util-scheduler-8620 DEBUG Adding task: 2917 / 0x46620a0
Jul 07 20:48:43-035664 util-scheduler-8620 DEBUG Checking readiness of task: 2917 / 0x46620a0
Jul 07 20:48:43-035999 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-036202 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-036396 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-036594 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-036787 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-036980 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-037178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-037414 util-scheduler-8620 DEBUG Running task: 2917 / 0x46620a0
Jul 07 20:48:43-037833 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:43-038089 util-scheduler-8620 DEBUG Adding task: 2918 / 0x4662248
Jul 07 20:48:43-038373 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-038570 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-038765 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-038959 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-039151 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-039343 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-039540 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-039731 util-scheduler-8620 DEBUG Running task: 2918 / 0x4662248
Jul 07 20:48:43-039923 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:43-040121 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:43-040350 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:43-040558 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:43-040768 util-scheduler-8620 DEBUG Adding task: 2919 / 0x46620a0
Jul 07 20:48:43-040957 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:43-041161 util-scheduler-8620 DEBUG Adding task: 2920 / 0x46620a0
Jul 07 20:48:43-041431 util-scheduler-8620 DEBUG Checking readiness of task: 2920 / 0x46620a0
Jul 07 20:48:43-041627 util-scheduler-8620 DEBUG Checking readiness of task: 2919 / 0x46620a0
Jul 07 20:48:43-041820 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-042018 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-042246 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-042439 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-042630 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-042819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-043010 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-043207 util-scheduler-8620 DEBUG Running task: 2919 / 0x46620a0
Jul 07 20:48:43-043401 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:43-043582 util-8620 DEBUG process_notify is running
Jul 07 20:48:43-043757 util-8620 DEBUG client_notify is running
Jul 07 20:48:43-043945 util-scheduler-8620 DEBUG Canceling task: 2912 / 0x59ee8a0
Jul 07 20:48:43-044179 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:48:43-044404 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:43-044652 cadet-p2p-8620 DEBUG Checking 0x59ffe28 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:43-044893 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:43-045083 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:48:43-045299 cadet-p2p-8620 DEBUG   path create
Jul 07 20:48:43-045473 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:48:43-045656 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:48:43-045927 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 100)
Jul 07 20:48:43-046123 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:43-046304 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:43-046493 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:48:43-046678 cadet-con-8620 DEBUG  C_P- 0x59e8808 2
Jul 07 20:48:43-046870 util-scheduler-8620 DEBUG Canceling task: 2916 / 0x59e8808
Jul 07 20:48:43-047091 util-scheduler-8620 DEBUG Adding task: 2921 / 0x59e8808
Jul 07 20:48:43-047344 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:43-047517 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:43-047739 cadet-p2p-8620 DEBUG Checking 0x5a01af0 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:43-047982 cadet-p2p-8620 DEBUG Checking 0x5a01af0 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:43-048163 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:48:43-048371 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:48:43-048589 util-scheduler-8620 DEBUG Adding task: 2922 / 0x59ee8a0
Jul 07 20:48:43-048771 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:43-048950 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:48:43-049150 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:43-049353 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:43-049530 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:43-049774 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:43-049960 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:43-050137 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:48:43-050337 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:43-050544 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:48:43-050729 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:48:43-050933 util-scheduler-8620 DEBUG Adding task: 2923 / 0x59ee8a0
Jul 07 20:48:43-051154 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:43-051355 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:43-051561 util-scheduler-8620 DEBUG Adding task: 2924 / 0x46620a0
Jul 07 20:48:43-051764 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:48:43-052019 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:43-052218 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:48:43-052493 util-scheduler-8620 DEBUG Checking readiness of task: 2924 / 0x46620a0
Jul 07 20:48:43-052692 util-scheduler-8620 DEBUG Checking readiness of task: 2920 / 0x46620a0
Jul 07 20:48:43-052887 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-053080 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-053309 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-053502 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-053694 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-053884 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-054076 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-054268 util-scheduler-8620 DEBUG Running task: 2924 / 0x46620a0
Jul 07 20:48:43-054455 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:43-054634 util-8620 DEBUG process_notify is running
Jul 07 20:48:43-054807 util-8620 DEBUG client_notify is running
Jul 07 20:48:43-054993 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:43-055200 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:43-055397 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:43-055643 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:43-055853 util-scheduler-8620 DEBUG Running task: 2922 / 0x59ee8a0
Jul 07 20:48:43-056052 util-scheduler-8620 DEBUG Canceling task: 2923 / 0x59ee8a0
Jul 07 20:48:43-056272 util-scheduler-8620 DEBUG Adding task: 2925 / 0x59ee8a0
Jul 07 20:48:43-056498 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:43-056695 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:43-056897 util-scheduler-8620 DEBUG Adding task: 2926 / 0x46620a0
Jul 07 20:48:43-057145 util-scheduler-8620 DEBUG Checking readiness of task: 2926 / 0x46620a0
Jul 07 20:48:43-057374 util-scheduler-8620 DEBUG Checking readiness of task: 2920 / 0x46620a0
Jul 07 20:48:43-057567 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-057760 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-057952 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-058144 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-058336 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-058526 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-058717 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-058910 util-scheduler-8620 DEBUG Running task: 2926 / 0x46620a0
Jul 07 20:48:43-059095 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:43-059274 util-8620 DEBUG process_notify is running
Jul 07 20:48:43-059445 util-8620 DEBUG client_notify is running
Jul 07 20:48:43-059628 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:43-059822 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:43-060013 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:43-060259 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:43-291930 util-scheduler-8620 DEBUG Checking readiness of task: 2920 / 0x46620a0
Jul 07 20:48:43-292267 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-292476 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-292670 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-292863 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-293084 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-293297 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-293505 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-293707 util-scheduler-8620 DEBUG Running task: 2920 / 0x46620a0
Jul 07 20:48:43-294132 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:43-294382 util-scheduler-8620 DEBUG Adding task: 2927 / 0x4662248
Jul 07 20:48:43-294654 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-294849 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-295039 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-295229 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-295419 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-295607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-295795 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-295985 util-scheduler-8620 DEBUG Running task: 2927 / 0x4662248
Jul 07 20:48:43-296174 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:43-296375 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:43-296605 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:43-296810 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:43-297017 util-scheduler-8620 DEBUG Adding task: 2928 / 0x46620a0
Jul 07 20:48:43-297223 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:43-297431 util-scheduler-8620 DEBUG Adding task: 2929 / 0x46620a0
Jul 07 20:48:43-297675 util-scheduler-8620 DEBUG Checking readiness of task: 2929 / 0x46620a0
Jul 07 20:48:43-297868 util-scheduler-8620 DEBUG Checking readiness of task: 2928 / 0x46620a0
Jul 07 20:48:43-298060 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:43-298250 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:43-298442 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:43-298631 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:43-298821 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:43-299008 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:43-299198 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:43-299389 util-scheduler-8620 DEBUG Running task: 2928 / 0x46620a0
Jul 07 20:48:43-299574 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:43-299750 util-8620 DEBUG process_notify is running
Jul 07 20:48:43-299922 util-8620 DEBUG client_notify is running
Jul 07 20:48:43-300108 util-scheduler-8620 DEBUG Canceling task: 2925 / 0x59ee8a0
Jul 07 20:48:43-300331 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:48:43-300551 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:43-300790 cadet-p2p-8620 DEBUG Checking 0x5a01af0 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:43-301022 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:43-301219 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:48:43-301391 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:48:43-301562 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:48:43-301733 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:48:43-301991 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 36)
Jul 07 20:48:43-302186 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:43-302366 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:43-302553 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:48:43-302734 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:43-302928 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:43-303112 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:48:43-303311 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:43-303486 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:43-303660 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:43-303857 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:43-304061 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:48:43-304244 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:48:43-304423 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:43-304613 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:48:43-304857 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:44-616033 util-scheduler-8620 DEBUG Checking readiness of task: 2929 / 0x46620a0
Jul 07 20:48:44-616383 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:44-616580 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:44-616772 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:44-616964 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:44-617155 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:44-617380 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:44-617571 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:44-617763 util-scheduler-8620 DEBUG Running task: 2899 / 0x52cbfb8
Jul 07 20:48:44-617998 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:44-618244 cadet-tun-8620 DEBUG  kx started 80 s ago
Jul 07 20:48:44-618453 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:44-618653 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:44-618856 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:44-619091 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:48:44-619271 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:44-619492 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:48:44-619785 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:48:44-619982 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:48:44-620220 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:44-620428 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:44-620746 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:48:44-620947 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:44-621171 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:44-621377 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:44-621553 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:44-621760 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:44-621974 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:44-622197 util-scheduler-8620 DEBUG Adding task: 2930 / 0x59ee8a0
Jul 07 20:48:44-622377 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:44-622580 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:44-622756 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:44-622930 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:44-623167 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:44-623363 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:44-623542 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:44-623740 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:44-623984 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:44-624182 util-scheduler-8620 DEBUG Adding task: 2931 / 0x52cbfb8
Jul 07 20:48:44-624464 util-scheduler-8620 DEBUG Checking readiness of task: 2929 / 0x46620a0
Jul 07 20:48:44-624658 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:44-624849 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:44-625039 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:44-625250 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:44-625441 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:44-625630 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:44-625818 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:44-626008 util-scheduler-8620 DEBUG Running task: 2930 / 0x59ee8a0
Jul 07 20:48:44-626215 util-scheduler-8620 DEBUG Adding task: 2932 / 0x59ee8a0
Jul 07 20:48:44-626436 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:44-626639 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:44-626847 util-scheduler-8620 DEBUG Adding task: 2933 / 0x46620a0
Jul 07 20:48:44-627090 util-scheduler-8620 DEBUG Checking readiness of task: 2933 / 0x46620a0
Jul 07 20:48:44-627285 util-scheduler-8620 DEBUG Checking readiness of task: 2929 / 0x46620a0
Jul 07 20:48:44-627476 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:44-627665 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:44-627855 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:44-628045 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:44-628235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:44-628423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:44-628612 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:44-628803 util-scheduler-8620 DEBUG Running task: 2933 / 0x46620a0
Jul 07 20:48:44-628988 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:44-629166 util-8620 DEBUG process_notify is running
Jul 07 20:48:44-629359 util-8620 DEBUG client_notify is running
Jul 07 20:48:44-629539 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:44-629733 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:44-629924 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:44-630177 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:48-325949 util-scheduler-8620 DEBUG Checking readiness of task: 2929 / 0x46620a0
Jul 07 20:48:48-326370 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:48-326572 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:48-326766 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:48-326970 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:48-327180 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:48-327372 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:48-327563 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:48-327759 util-scheduler-8620 DEBUG Running task: 2929 / 0x46620a0
Jul 07 20:48:48-328186 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:48-328444 util-scheduler-8620 DEBUG Adding task: 2934 / 0x4662248
Jul 07 20:48:48-328724 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:48-328919 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:48-329111 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:48-329326 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:48-329552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:48-329743 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:48-329933 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:48-330126 util-scheduler-8620 DEBUG Running task: 2934 / 0x4662248
Jul 07 20:48:48-330317 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:48-330518 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:48-330752 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:48-330961 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:48-331169 util-scheduler-8620 DEBUG Adding task: 2935 / 0x46620a0
Jul 07 20:48:48-331357 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:48-331566 util-scheduler-8620 DEBUG Adding task: 2936 / 0x46620a0
Jul 07 20:48:48-331814 util-scheduler-8620 DEBUG Checking readiness of task: 2936 / 0x46620a0
Jul 07 20:48:48-332008 util-scheduler-8620 DEBUG Checking readiness of task: 2935 / 0x46620a0
Jul 07 20:48:48-332201 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:48-332393 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:48-332583 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:48-332772 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:48-332963 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:48-333151 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:48-333362 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:48-333554 util-scheduler-8620 DEBUG Running task: 2935 / 0x46620a0
Jul 07 20:48:48-333741 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:48-333922 util-8620 DEBUG process_notify is running
Jul 07 20:48:48-334103 util-8620 DEBUG client_notify is running
Jul 07 20:48:48-334293 util-scheduler-8620 DEBUG Canceling task: 2932 / 0x59ee8a0
Jul 07 20:48:48-334527 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:48-334764 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:48-335006 cadet-p2p-8620 DEBUG Checking 0x5a060e8 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:48-335242 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:48-335421 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:48-335613 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:48-335902 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:48:48-336099 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:48-336280 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:48-336470 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:48:48-336666 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:48-336852 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:48-337047 util-scheduler-8620 DEBUG Canceling task: 2921 / 0x59e8808
Jul 07 20:48:48-337287 util-scheduler-8620 DEBUG Adding task: 2937 / 0x59e8808
Jul 07 20:48:48-337538 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:48-337708 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:48-337890 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:48-338092 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:48-338267 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:48-338442 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:48-338640 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:48-338845 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:48-339029 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:48-339207 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:48-339419 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:48-339664 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:49-625393 util-scheduler-8620 DEBUG Checking readiness of task: 2936 / 0x46620a0
Jul 07 20:48:49-625755 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:49-625952 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:49-626144 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:49-626337 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:49-626528 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:49-626719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:49-626910 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:49-627102 util-scheduler-8620 DEBUG Running task: 2931 / 0x52cbfb8
Jul 07 20:48:49-627340 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:49-627609 cadet-tun-8620 DEBUG  kx started 85 s ago
Jul 07 20:48:49-627817 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:49-628018 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:49-628221 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:49-628457 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:48:49-628637 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:49-628859 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:48:49-629150 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:48:49-629369 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:48:49-629606 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:49-629816 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:49-630153 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:48:49-630365 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:49-630595 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:49-630779 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:49-630954 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:49-631161 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:49-631374 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:49-631600 util-scheduler-8620 DEBUG Adding task: 2938 / 0x59ee8a0
Jul 07 20:48:49-631779 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:49-631982 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:49-632158 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:49-632333 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:49-632571 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:49-632766 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:49-632943 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:49-633141 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:49-633406 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:49-633604 util-scheduler-8620 DEBUG Adding task: 2939 / 0x52cbfb8
Jul 07 20:48:49-633860 util-scheduler-8620 DEBUG Checking readiness of task: 2936 / 0x46620a0
Jul 07 20:48:49-634053 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:49-634243 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:49-634433 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:49-634622 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:49-634815 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:49-635003 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:49-635218 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:49-635408 util-scheduler-8620 DEBUG Running task: 2938 / 0x59ee8a0
Jul 07 20:48:49-635616 util-scheduler-8620 DEBUG Adding task: 2940 / 0x59ee8a0
Jul 07 20:48:49-635838 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:49-636041 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:49-636249 util-scheduler-8620 DEBUG Adding task: 2941 / 0x46620a0
Jul 07 20:48:49-636492 util-scheduler-8620 DEBUG Checking readiness of task: 2941 / 0x46620a0
Jul 07 20:48:49-636687 util-scheduler-8620 DEBUG Checking readiness of task: 2936 / 0x46620a0
Jul 07 20:48:49-636877 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:49-637067 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:49-637277 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:49-637468 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:49-637657 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:49-637845 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:49-638033 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:49-638224 util-scheduler-8620 DEBUG Running task: 2941 / 0x46620a0
Jul 07 20:48:49-638411 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:49-638588 util-8620 DEBUG process_notify is running
Jul 07 20:48:49-638762 util-8620 DEBUG client_notify is running
Jul 07 20:48:49-638941 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:49-639138 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:49-639328 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:49-639581 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:52-768518 util-scheduler-8620 DEBUG Checking readiness of task: 2936 / 0x46620a0
Jul 07 20:48:52-768897 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:52-769095 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:52-769320 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:52-769515 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:52-769707 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:52-769898 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:52-770087 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:52-770284 util-scheduler-8620 DEBUG Running task: 2936 / 0x46620a0
Jul 07 20:48:52-770719 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:52-770976 util-scheduler-8620 DEBUG Adding task: 2942 / 0x4662248
Jul 07 20:48:52-771254 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:52-771448 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:52-771643 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:52-771832 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:52-772022 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:52-772210 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:52-772400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:52-772590 util-scheduler-8620 DEBUG Running task: 2942 / 0x4662248
Jul 07 20:48:52-772780 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:48:52-772981 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:48:52-773304 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:48:52-773604 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 2FDYFV0X from V8XX
Jul 07 20:48:52-773822 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:48:52-774065 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:52-774274 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:52-774458 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:48:52-774630 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:48:52-774817 util-scheduler-8620 DEBUG Canceling task: 2915 / 0x59e8808
Jul 07 20:48:52-775043 util-scheduler-8620 DEBUG Adding task: 2943 / 0x59e8808
Jul 07 20:48:52-775288 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:48:52-775470 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:48:52-775661 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:48:52-775894 cadet-con-8620 DEBUG Connection 2FDYFV0X (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:48:52-776133 cadet-con-8620 INFO ===> {           BCK ACK} on connection 2FDYFV0X (->V8XX)
Jul 07 20:48:52-776366 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:52-776572 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:52-776867 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 36)
Jul 07 20:48:52-777065 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:52-777311 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:52-777494 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:52-777670 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:52-777873 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:48:52-778077 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:52-778253 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:48:52-778427 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:52-778666 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:52-778862 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:52-779040 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:52-779273 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:52-779454 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:52-779628 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:48:52-779824 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:52-780009 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:52-780220 util-scheduler-8620 DEBUG Adding task: 2944 / 0x46620a0
Jul 07 20:48:54-174290 util-scheduler-8620 DEBUG Checking readiness of task: 2944 / 0x46620a0
Jul 07 20:48:54-174639 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-174836 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-175029 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-175220 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-175411 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-175603 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-175796 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-175990 util-scheduler-8620 DEBUG Running task: 2944 / 0x46620a0
Jul 07 20:48:54-176409 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:54-176658 util-scheduler-8620 DEBUG Adding task: 2945 / 0x4662248
Jul 07 20:48:54-176930 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-177124 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-177352 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-177563 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-178915 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-179122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-179315 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-179509 util-scheduler-8620 DEBUG Running task: 2945 / 0x4662248
Jul 07 20:48:54-179702 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:54-179903 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:54-180138 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:54-180348 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:54-180558 util-scheduler-8620 DEBUG Adding task: 2946 / 0x46620a0
Jul 07 20:48:54-180747 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:54-180953 util-scheduler-8620 DEBUG Adding task: 2947 / 0x46620a0
Jul 07 20:48:54-181229 util-scheduler-8620 DEBUG Checking readiness of task: 2947 / 0x46620a0
Jul 07 20:48:54-181426 util-scheduler-8620 DEBUG Checking readiness of task: 2946 / 0x46620a0
Jul 07 20:48:54-181620 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-181811 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-182001 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-182191 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-182383 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-182572 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-182763 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-182954 util-scheduler-8620 DEBUG Running task: 2946 / 0x46620a0
Jul 07 20:48:54-183141 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:54-183321 util-8620 DEBUG process_notify is running
Jul 07 20:48:54-183495 util-8620 DEBUG client_notify is running
Jul 07 20:48:54-183683 util-scheduler-8620 DEBUG Canceling task: 2940 / 0x59ee8a0
Jul 07 20:48:54-183911 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:54-184160 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:54-184424 cadet-p2p-8620 DEBUG Checking 0x5a08d30 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:54-184661 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:54-184840 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:54-185065 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:54-185864 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:48:54-186117 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:54-186311 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:54-186500 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:48:54-186692 cadet-con-8620 DEBUG  C_P- 0x59e8808 2
Jul 07 20:48:54-186873 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:54-187060 util-scheduler-8620 DEBUG Canceling task: 2937 / 0x59e8808
Jul 07 20:48:54-187277 util-scheduler-8620 DEBUG Adding task: 2948 / 0x59e8808
Jul 07 20:48:54-187530 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:54-187702 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:54-187938 cadet-p2p-8620 DEBUG Checking 0x5a0a880 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:54-188199 cadet-p2p-8620 DEBUG Checking 0x5a0a880 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:54-188381 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:48:54-188587 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:48:54-188803 util-scheduler-8620 DEBUG Adding task: 2949 / 0x59ee8a0
Jul 07 20:48:54-188983 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:54-189176 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:54-189400 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:54-189579 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:54-189784 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:54-190037 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:54-190222 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:48:54-190397 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:48:54-190594 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:54-190800 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:54-190983 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:54-191191 util-scheduler-8620 DEBUG Adding task: 2950 / 0x59ee8a0
Jul 07 20:48:54-191410 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:54-191608 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:54-191812 util-scheduler-8620 DEBUG Adding task: 2951 / 0x46620a0
Jul 07 20:48:54-192016 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:54-192260 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:54-192456 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:48:54-192710 util-scheduler-8620 DEBUG Checking readiness of task: 2951 / 0x46620a0
Jul 07 20:48:54-192904 util-scheduler-8620 DEBUG Checking readiness of task: 2947 / 0x46620a0
Jul 07 20:48:54-193096 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-193310 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-193520 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-193710 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-193900 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-194089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-194277 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-194469 util-scheduler-8620 DEBUG Running task: 2951 / 0x46620a0
Jul 07 20:48:54-194653 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:54-194830 util-8620 DEBUG process_notify is running
Jul 07 20:48:54-195001 util-8620 DEBUG client_notify is running
Jul 07 20:48:54-195180 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:54-195374 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:54-195564 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:54-195807 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:54-196027 util-scheduler-8620 DEBUG Running task: 2949 / 0x59ee8a0
Jul 07 20:48:54-196220 util-scheduler-8620 DEBUG Canceling task: 2950 / 0x59ee8a0
Jul 07 20:48:54-196448 util-scheduler-8620 DEBUG Adding task: 2952 / 0x59ee8a0
Jul 07 20:48:54-196662 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:54-196857 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:54-197053 util-scheduler-8620 DEBUG Adding task: 2953 / 0x46620a0
Jul 07 20:48:54-197313 util-scheduler-8620 DEBUG Checking readiness of task: 2953 / 0x46620a0
Jul 07 20:48:54-197507 util-scheduler-8620 DEBUG Checking readiness of task: 2947 / 0x46620a0
Jul 07 20:48:54-197697 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-197887 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-198078 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-198267 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-198456 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-198646 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-198834 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-199043 util-scheduler-8620 DEBUG Running task: 2953 / 0x46620a0
Jul 07 20:48:54-199227 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:54-199402 util-8620 DEBUG process_notify is running
Jul 07 20:48:54-199571 util-8620 DEBUG client_notify is running
Jul 07 20:48:54-199748 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:54-199952 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:54-200141 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:54-200380 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:54-441185 util-scheduler-8620 DEBUG Checking readiness of task: 2947 / 0x46620a0
Jul 07 20:48:54-441450 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-441648 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-441842 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-442034 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-442224 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-442417 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-442606 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-442798 util-scheduler-8620 DEBUG Running task: 2947 / 0x46620a0
Jul 07 20:48:54-443205 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:54-443441 util-scheduler-8620 DEBUG Adding task: 2954 / 0x4662248
Jul 07 20:48:54-443698 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-443892 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-444083 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-444273 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-444463 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-444652 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-444840 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-445031 util-scheduler-8620 DEBUG Running task: 2954 / 0x4662248
Jul 07 20:48:54-445241 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:54-445440 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:54-445658 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:54-445858 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:54-446058 util-scheduler-8620 DEBUG Adding task: 2955 / 0x46620a0
Jul 07 20:48:54-446242 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:54-446445 util-scheduler-8620 DEBUG Adding task: 2956 / 0x46620a0
Jul 07 20:48:54-446686 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:54-446879 util-scheduler-8620 DEBUG Checking readiness of task: 2955 / 0x46620a0
Jul 07 20:48:54-447071 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-447261 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-447453 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-447642 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-447832 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-448020 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-448211 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-448401 util-scheduler-8620 DEBUG Running task: 2955 / 0x46620a0
Jul 07 20:48:54-448610 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:54-448786 util-8620 DEBUG process_notify is running
Jul 07 20:48:54-448957 util-8620 DEBUG client_notify is running
Jul 07 20:48:54-449139 util-scheduler-8620 DEBUG Canceling task: 2952 / 0x59ee8a0
Jul 07 20:48:54-449384 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:48:54-449601 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:54-449846 cadet-p2p-8620 DEBUG Checking 0x5a0a880 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:54-450076 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:54-450253 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:48:54-450423 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:48:54-450591 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:48:54-450762 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:48:54-451015 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 36)
Jul 07 20:48:54-451207 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:54-451384 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:54-451570 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:48:54-451750 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:54-451923 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:54-452101 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:48:54-452299 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:54-452477 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:54-452650 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:54-452847 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:54-453049 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:48:54-453255 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:48:54-453434 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:54-453622 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:48:54-453865 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:54-633891 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:54-634169 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-634363 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-634555 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-634746 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-634937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-635127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-635317 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-635507 util-scheduler-8620 DEBUG Running task: 2939 / 0x52cbfb8
Jul 07 20:48:54-635730 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:54-635971 cadet-tun-8620 DEBUG  kx started 90 s ago
Jul 07 20:48:54-636179 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:54-636379 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:54-636582 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:54-636814 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:48:54-636994 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:54-637239 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:48:54-637527 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:48:54-637724 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:48:54-637961 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:54-638169 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:54-638482 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:48:54-638684 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:54-638930 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:54-639114 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:54-639290 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:54-639497 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:54-639711 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:54-639930 util-scheduler-8620 DEBUG Adding task: 2957 / 0x59ee8a0
Jul 07 20:48:54-640110 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:54-640313 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:54-640489 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:54-640663 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:54-640899 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:54-641095 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:54-641294 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:54-641493 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:54-641735 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:54-641933 util-scheduler-8620 DEBUG Adding task: 2958 / 0x52cbfb8
Jul 07 20:48:54-642179 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:54-642371 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-642564 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-642753 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-642943 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-643133 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-643321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-643510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-643700 util-scheduler-8620 DEBUG Running task: 2957 / 0x59ee8a0
Jul 07 20:48:54-643906 util-scheduler-8620 DEBUG Adding task: 2959 / 0x59ee8a0
Jul 07 20:48:54-644125 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:54-644325 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:54-644530 util-scheduler-8620 DEBUG Adding task: 2960 / 0x46620a0
Jul 07 20:48:54-644770 util-scheduler-8620 DEBUG Checking readiness of task: 2960 / 0x46620a0
Jul 07 20:48:54-644963 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:54-645154 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:54-645366 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:54-645555 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:54-645746 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:54-645936 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:54-646124 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:54-646313 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:54-646504 util-scheduler-8620 DEBUG Running task: 2960 / 0x46620a0
Jul 07 20:48:54-646687 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:54-646864 util-8620 DEBUG process_notify is running
Jul 07 20:48:54-647035 util-8620 DEBUG client_notify is running
Jul 07 20:48:54-647212 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:54-647405 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:54-647594 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:54-647841 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:56-508274 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:56-508641 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:56-508840 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:56-509035 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:56-509256 util-scheduler-8620 DEBUG Checking readiness of task: 2784 / 0x465ee60
Jul 07 20:48:56-509453 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:56-509644 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:56-509836 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:56-510033 util-scheduler-8620 DEBUG Running task: 2784 / 0x465ee60
Jul 07 20:48:56-510456 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:48:56-510711 util-scheduler-8620 DEBUG Adding task: 2961 / 0x465f008
Jul 07 20:48:56-510987 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:56-511195 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:56-511386 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:56-511576 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:56-511767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:56-511956 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:56-512144 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:56-512333 util-scheduler-8620 DEBUG Running task: 2961 / 0x465f008
Jul 07 20:48:56-512526 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:48:56-512765 nse-api-8620 DEBUG Received information about peer `TZQE' from peerinfo database
Jul 07 20:48:56-513058 cadet-hll-8620 DEBUG  hello for TZQE (90 bytes), expires on Tue Jul 08 08:48:56 2014
Jul 07 20:48:56-513312 cadet-p2p-8620 DEBUG set hello for TZQE
Jul 07 20:48:56-513610 cadet-p2p-8620 DEBUG  merge into 0x5a102e8 (90 bytes)
Jul 07 20:48:56-513806 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:56-514018 util-scheduler-8620 DEBUG Adding task: 2962 / 0x465ee60
Jul 07 20:48:57-970297 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:57-970669 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:57-970867 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:57-971060 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:57-971253 util-scheduler-8620 DEBUG Checking readiness of task: 2862 / 0x4663d68
Jul 07 20:48:57-971447 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:57-971637 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:57-971827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:57-972021 util-scheduler-8620 DEBUG Running task: 2862 / 0x4663d68
Jul 07 20:48:57-972445 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:48:57-972700 util-scheduler-8620 DEBUG Adding task: 2963 / 0x4663f10
Jul 07 20:48:57-972978 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:57-973171 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:57-973393 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:57-973585 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:57-973775 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:57-973965 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:57-974153 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:57-974344 util-scheduler-8620 DEBUG Running task: 2963 / 0x4663f10
Jul 07 20:48:57-974574 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:48:57-974773 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:57-974987 util-scheduler-8620 DEBUG Adding task: 2964 / 0x4663d68
Jul 07 20:48:57-975175 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:48:57-975403 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `TZQE' with quota 9216
Jul 07 20:48:57-975598 util-bandwidth-8620 DEBUG Tracker 0x4d73060 bandwidth changed to 9216 Bps
Jul 07 20:48:57-975860 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 14036 Bps, last update was 184 s ago
Jul 07 20:48:57-976097 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 9216 Bps, last update was 269 µs ago
Jul 07 20:48:57-976316 util-scheduler-8620 DEBUG Adding task: 2965 / 0x4d73060
Jul 07 20:48:57-976557 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:57-976749 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:57-976939 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:57-977129 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:57-977346 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:57-977538 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:57-977726 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:57-977915 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:57-978104 util-scheduler-8620 DEBUG Running task: 2965 / 0x4d73060
Jul 07 20:48:58-903747 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:58-904144 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:58-904342 util-scheduler-8620 DEBUG Checking readiness of task: 2956 / 0x46620a0
Jul 07 20:48:58-904537 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:58-904730 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:58-904923 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:58-905129 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:58-905349 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:58-905547 util-scheduler-8620 DEBUG Running task: 2956 / 0x46620a0
Jul 07 20:48:58-905973 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:48:58-906234 util-scheduler-8620 DEBUG Adding task: 2966 / 0x4662248
Jul 07 20:48:58-906516 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:58-906711 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:58-906904 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:58-907095 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:58-907287 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:58-907477 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:58-907666 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:58-907858 util-scheduler-8620 DEBUG Running task: 2966 / 0x4662248
Jul 07 20:48:58-908050 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:48:58-908250 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:48:58-908484 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:48:58-908692 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:58-908900 util-scheduler-8620 DEBUG Adding task: 2967 / 0x46620a0
Jul 07 20:48:58-909091 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:48:58-909325 util-scheduler-8620 DEBUG Adding task: 2968 / 0x46620a0
Jul 07 20:48:58-909574 util-scheduler-8620 DEBUG Checking readiness of task: 2968 / 0x46620a0
Jul 07 20:48:58-909806 util-scheduler-8620 DEBUG Checking readiness of task: 2967 / 0x46620a0
Jul 07 20:48:58-910000 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:58-910191 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:58-910382 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:58-910573 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:58-910764 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:58-910953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:58-911144 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:58-911336 util-scheduler-8620 DEBUG Running task: 2967 / 0x46620a0
Jul 07 20:48:58-911522 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:58-911702 util-8620 DEBUG process_notify is running
Jul 07 20:48:58-911876 util-8620 DEBUG client_notify is running
Jul 07 20:48:58-912065 util-scheduler-8620 DEBUG Canceling task: 2959 / 0x59ee8a0
Jul 07 20:48:58-912293 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:48:58-912515 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:48:58-912758 cadet-p2p-8620 DEBUG Checking 0x5a0f060 towards 2FDYFV0X (->V8XX)
Jul 07 20:48:58-912993 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:48:58-913170 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:48:58-913387 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:48:58-913673 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:48:58-913868 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:48:58-914049 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:48:58-914236 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:48:58-914425 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:48:58-914604 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:48:58-914789 util-scheduler-8620 DEBUG Canceling task: 2948 / 0x59e8808
Jul 07 20:48:58-915013 util-scheduler-8620 DEBUG Adding task: 2969 / 0x59e8808
Jul 07 20:48:58-915262 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:48:58-915432 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:48:58-915615 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:48:58-915817 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:58-915994 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:48:58-916183 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:48:58-916384 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:58-916589 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:48:58-916772 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:48:58-916952 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:58-917144 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:48:58-917432 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:48:59-642807 util-scheduler-8620 DEBUG Checking readiness of task: 2968 / 0x46620a0
Jul 07 20:48:59-643162 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:59-643357 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:59-643549 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:59-643741 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:59-643933 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:59-644123 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:59-644313 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:59-644506 util-scheduler-8620 DEBUG Running task: 2958 / 0x52cbfb8
Jul 07 20:48:59-644768 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:48:59-645015 cadet-tun-8620 DEBUG  kx started 95 s ago
Jul 07 20:48:59-645244 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:48:59-645444 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:48:59-645647 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:48:59-645881 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:48:59-646063 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:48:59-646286 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:48:59-646577 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:48:59-646775 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:48:59-647012 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:48:59-647220 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:48:59-647538 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:48:59-647739 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:48:59-647963 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:48:59-648147 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:48:59-648323 cadet-con-8620 DEBUG  sendable
Jul 07 20:48:59-648529 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:48:59-648744 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:48:59-648970 util-scheduler-8620 DEBUG Adding task: 2970 / 0x59ee8a0
Jul 07 20:48:59-649150 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:48:59-649375 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:48:59-649551 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:48:59-649727 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:48:59-649966 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:48:59-650162 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:48:59-650339 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:48:59-650538 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:48:59-650780 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:48:59-650977 util-scheduler-8620 DEBUG Adding task: 2971 / 0x52cbfb8
Jul 07 20:48:59-651234 util-scheduler-8620 DEBUG Checking readiness of task: 2968 / 0x46620a0
Jul 07 20:48:59-651428 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:59-651617 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:59-651807 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:59-651995 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:59-652185 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:59-652374 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:59-652562 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:59-652750 util-scheduler-8620 DEBUG Running task: 2970 / 0x59ee8a0
Jul 07 20:48:59-652959 util-scheduler-8620 DEBUG Adding task: 2972 / 0x59ee8a0
Jul 07 20:48:59-653181 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:48:59-653405 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:48:59-653613 util-scheduler-8620 DEBUG Adding task: 2973 / 0x46620a0
Jul 07 20:48:59-653855 util-scheduler-8620 DEBUG Checking readiness of task: 2973 / 0x46620a0
Jul 07 20:48:59-654050 util-scheduler-8620 DEBUG Checking readiness of task: 2968 / 0x46620a0
Jul 07 20:48:59-654241 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:48:59-654431 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:48:59-654620 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:48:59-654810 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:48:59-655018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:48:59-655208 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:48:59-655396 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:48:59-655588 util-scheduler-8620 DEBUG Running task: 2973 / 0x46620a0
Jul 07 20:48:59-655773 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:48:59-655950 util-8620 DEBUG process_notify is running
Jul 07 20:48:59-656123 util-8620 DEBUG client_notify is running
Jul 07 20:48:59-656305 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:48:59-656500 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:48:59-656691 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:48:59-656946 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:01-040076 util-scheduler-8620 DEBUG Checking readiness of task: 2968 / 0x46620a0
Jul 07 20:49:01-040445 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:01-040645 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:01-040840 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:01-041036 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:01-041255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:01-041451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:01-041643 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:01-041841 util-scheduler-8620 DEBUG Running task: 2968 / 0x46620a0
Jul 07 20:49:01-042265 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:01-042521 util-scheduler-8620 DEBUG Adding task: 2974 / 0x4662248
Jul 07 20:49:01-042800 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:01-042995 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:01-043188 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:01-043382 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:01-043575 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:01-043778 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:01-043970 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:01-044165 util-scheduler-8620 DEBUG Running task: 2974 / 0x4662248
Jul 07 20:49:01-044359 util-8620 DEBUG Received message of type 68 and size 40 from core service.
Jul 07 20:49:01-044560 core-api-8620 DEBUG Processing message of type 68 and size 40 from core service
Jul 07 20:49:01-045008 core-api-8620 DEBUG Received notification about disconnect from `TZQE'.
Jul 07 20:49:01-045462 cadet-p2p-8620 INFO DISCONNECTED GN10 <= TZQE
Jul 07 20:49:01-045765 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:49:01-045985 util-scheduler-8620 DEBUG Adding task: 2975 / 0x4d5e5d8
Jul 07 20:49:01-046218 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:01-046428 util-scheduler-8620 DEBUG Adding task: 2976 / 0x46620a0
Jul 07 20:49:01-046686 util-scheduler-8620 DEBUG Checking readiness of task: 2976 / 0x46620a0
Jul 07 20:49:01-046882 util-scheduler-8620 DEBUG Checking readiness of task: 2975 / 0x4d5e5d8
Jul 07 20:49:01-047078 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:01-047271 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:01-047463 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:01-047655 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:01-047847 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:01-048072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:01-048264 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:01-048459 util-scheduler-8620 DEBUG Running task: 2975 / 0x4d5e5d8
Jul 07 20:49:01-048646 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:49:01-048828 util-8620 DEBUG process_notify is running
Jul 07 20:49:01-049001 util-8620 DEBUG client_notify is running
Jul 07 20:49:01-049252 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:49:01-049511 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:49:02-803077 util-scheduler-8620 DEBUG Checking readiness of task: 2976 / 0x46620a0
Jul 07 20:49:02-803475 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:02-803674 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:02-803869 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:02-804064 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:02-804257 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:02-804450 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:02-804641 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:02-804851 util-scheduler-8620 DEBUG Running task: 2976 / 0x46620a0
Jul 07 20:49:02-805298 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:02-805557 util-scheduler-8620 DEBUG Adding task: 2977 / 0x4662248
Jul 07 20:49:02-805849 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:02-806044 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:02-806237 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:02-806428 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:02-806619 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:02-806819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:02-807012 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:02-807203 util-scheduler-8620 DEBUG Running task: 2977 / 0x4662248
Jul 07 20:49:02-807394 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:02-807594 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:02-807840 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:02-808049 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:02-808255 util-scheduler-8620 DEBUG Adding task: 2978 / 0x46620a0
Jul 07 20:49:02-808463 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:02-808670 util-scheduler-8620 DEBUG Adding task: 2979 / 0x46620a0
Jul 07 20:49:02-808928 util-scheduler-8620 DEBUG Checking readiness of task: 2979 / 0x46620a0
Jul 07 20:49:02-809122 util-scheduler-8620 DEBUG Checking readiness of task: 2978 / 0x46620a0
Jul 07 20:49:02-809336 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:02-809527 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:02-809717 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:02-809918 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:02-810109 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:02-810299 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:02-810488 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:02-810681 util-scheduler-8620 DEBUG Running task: 2978 / 0x46620a0
Jul 07 20:49:02-810876 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:02-811083 util-8620 DEBUG process_notify is running
Jul 07 20:49:02-811257 util-8620 DEBUG client_notify is running
Jul 07 20:49:02-811447 util-scheduler-8620 DEBUG Canceling task: 2972 / 0x59ee8a0
Jul 07 20:49:02-811674 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:02-811904 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:02-812145 cadet-p2p-8620 DEBUG Checking 0x5a12b78 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:02-812379 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:02-812557 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:02-812748 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:02-813045 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:02-813261 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:02-813442 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:02-813630 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:02-813829 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:02-814009 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:02-814192 util-scheduler-8620 DEBUG Canceling task: 2969 / 0x59e8808
Jul 07 20:49:02-814405 util-scheduler-8620 DEBUG Adding task: 2980 / 0x59e8808
Jul 07 20:49:02-814656 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:02-814836 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:02-815022 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:02-815223 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:02-815399 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:02-815575 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:02-815775 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:02-815989 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:02-816174 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:02-816354 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:02-816545 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:02-817486 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:04-297444 util-scheduler-8620 DEBUG Checking readiness of task: 2979 / 0x46620a0
Jul 07 20:49:04-297813 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-298012 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-298207 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-298401 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:04-298595 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-298785 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-298977 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-299174 util-scheduler-8620 DEBUG Running task: 2979 / 0x46620a0
Jul 07 20:49:04-299596 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:04-299855 util-scheduler-8620 DEBUG Adding task: 2981 / 0x4662248
Jul 07 20:49:04-300131 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-300326 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-300517 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-300709 util-scheduler-8620 DEBUG Checking readiness of task: 2884 / 0x4d5c418
Jul 07 20:49:04-300901 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-301091 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-301725 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-301923 util-scheduler-8620 DEBUG Running task: 2884 / 0x4d5c418
Jul 07 20:49:04-302337 util-8620 DEBUG receive_ready read 48/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:49:04-302547 util-8620 DEBUG Server receives 48 bytes from `<unbound UNIX client>'.
Jul 07 20:49:04-302743 util-8620 DEBUG Server-mst receives 48 bytes with 0 bytes already in private buffer
Jul 07 20:49:04-302928 util-8620 DEBUG Server-mst has 48 bytes left in inbound buffer
Jul 07 20:49:04-303111 util-8620 DEBUG Tokenizer gives server message of type 274 from client
Jul 07 20:49:04-303302 util-8620 DEBUG Server schedules transmission of 48-byte message of type 274 to client.
Jul 07 20:49:04-303520 util-scheduler-8620 DEBUG Adding task: 2982 / 0x4d5c578
Jul 07 20:49:04-304681 cadet-loc-8620 DEBUG Got a DESTROY CHANNEL from client!
Jul 07 20:49:04-305910 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:49:04-307246 cadet-loc-8620 DEBUG   for channel 80000000
Jul 07 20:49:04-309476 cadet-chn-8620 DEBUG  Client 0 is owner.
Jul 07 20:49:04-312001 cadet-chn-8620 INFO ===> {   CHANNEL_DESTROY} FWD on channel P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:49:04-312229 cadet-tun-8620 DEBUG GMT Send on Tunnel P00P
Jul 07 20:49:04-312435 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:49:04-312626 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:49:04-312811 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:49:04-312995 cadet-tun-8620 DEBUG TTT  tq_head 0x4d613d8, tq_tail 0x4d613d8
Jul 07 20:49:04-313176 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:49:04-313375 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:49:04-313604 cadet-tun-8620 DEBUG TTT  - P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:49:04-313781 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:49:04-314021 cadet-tun-8620 DEBUG TTT  - KT5Q8VM8 (->P00P) [1] buf: 11/11 (qn 0/0)
Jul 07 20:49:04-314207 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:49:04-314408 cadet-tun-8620 DEBUG queue data on Tunnel P00P
Jul 07 20:49:04-314608 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:49:04-314793 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_UNINITIALIZED
Jul 07 20:49:04-314975 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:49:04-315155 cadet-tun-8620 DEBUG TTT  tq_head 0x4d613d8, tq_tail 0x4d613d8
Jul 07 20:49:04-315334 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:49:04-315503 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:49:04-315717 cadet-tun-8620 DEBUG TTT  - P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:49:04-315891 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:49:04-316121 cadet-tun-8620 DEBUG TTT  - KT5Q8VM8 (->P00P) [1] buf: 11/11 (qn 0/0)
Jul 07 20:49:04-316305 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:49:04-317051 cadet-chn-8620 DEBUG destroying channel P00P:1073741824
Jul 07 20:49:04-317296 cadet-chn-8620 DEBUG Channel P00P:40000000 (0x4d60800)
Jul 07 20:49:04-317486 cadet-chn-8620 DEBUG   root (nil)/0x4d60a60
Jul 07 20:49:04-317755 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:49:04-318690 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:49:04-318893 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:49:04-319440 cadet-tun-8620 DEBUG Removing channel 0x4d60800 from tunnel 0x4d60080
Jul 07 20:49:04-319680 cadet-tun-8620 DEBUG  found! P00P:19 gid:40000000 (80000000 / 0)
Jul 07 20:49:04-319973 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:49:04-320193 util-scheduler-8620 DEBUG Adding task: 2983 / 0x4d5e5d8
Jul 07 20:49:04-320417 cadet-tun-8620 DEBUG Tunnel P00P destroy if empty
Jul 07 20:49:04-320621 cadet-tun-8620 DEBUG Tunnel P00P empty: destroying scheduled
Jul 07 20:49:04-320824 util-scheduler-8620 DEBUG Adding task: 2984 / 0x4d60080
Jul 07 20:49:04-321018 cadet-tun-8620 DEBUG Scheduled destroy of 0x4d60080 as BA8
Jul 07 20:49:04-321472 util-scheduler-8620 DEBUG Canceling task: 2982 / 0x4d5c578
Jul 07 20:49:04-321676 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:49:04-321881 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:49:04-322091 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:49:04-322298 util-scheduler-8620 DEBUG Adding task: 2985 / 0x4d5c418
Jul 07 20:49:04-322500 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:49:04-322723 util-scheduler-8620 DEBUG Running task: 2981 / 0x4662248
Jul 07 20:49:04-322918 util-8620 DEBUG Received message of type 68 and size 40 from core service.
Jul 07 20:49:04-323116 core-api-8620 DEBUG Processing message of type 68 and size 40 from core service
Jul 07 20:49:04-323330 core-api-8620 DEBUG Received notification about disconnect from `P00P'.
Jul 07 20:49:04-323572 cadet-p2p-8620 INFO DISCONNECTED GN10 <= P00P
Jul 07 20:49:04-323989 cadet-p2p-8620 DEBUG   notifying KT5Q8VM8 (->P00P) due to P00P
Jul 07 20:49:04-324396 cadet-con-8620 DEBUG  notify broken on KT5Q8VM8 (->P00P) due to P00P disconnect
Jul 07 20:49:04-324637 cadet-con-8620 DEBUG  get prev hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:49:04-324850 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:49:04-325217 cadet-con-8620 DEBUG destroying connection KT5Q8VM8 (->P00P)
Jul 07 20:49:04-325407 cadet-con-8620 DEBUG  fc's f: 0x4d68bec, b: 0x4d68c20
Jul 07 20:49:04-325592 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:49:04-325823 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection KT5Q8VM8 (->P00P)
Jul 07 20:49:04-326056 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:49:04-326263 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:49:04-326500 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection KT5Q8VM8 (->P00P)
Jul 07 20:49:04-326731 cadet-con-8620 DEBUG  get prev hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:49:04-326936 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:49:04-327174 cadet-con-8620 DEBUG  get next hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:49:04-327382 cadet-con-8620 DEBUG   ID: P00P (3)
Jul 07 20:49:04-327616 cadet-p2p-8620 DEBUG removing connection KT5Q8VM8 (->P00P)
Jul 07 20:49:04-327817 cadet-p2p-8620 DEBUG from peer P00P
Jul 07 20:49:04-328017 cadet-p2p-8620 DEBUG peer P00P ok, has 1 connections.
Jul 07 20:49:04-328260 cadet-con-8620 DEBUG  get prev hop KT5Q8VM8 (->P00P) [0/2]
Jul 07 20:49:04-328465 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:49:04-328694 cadet-p2p-8620 DEBUG removing connection KT5Q8VM8 (->P00P)
Jul 07 20:49:04-328892 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:49:04-329090 cadet-p2p-8620 DEBUG peer GN10 ok, has 2 connections.
Jul 07 20:49:04-329305 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:49:04-329552 cadet-tun-8620 DEBUG Removing connection KT5Q8VM8 (->P00P) from tunnel P00P
Jul 07 20:49:04-329756 util-scheduler-8620 DEBUG Canceling task: 2910 / 0x4d68be8
Jul 07 20:49:04-330260 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:04-330472 util-scheduler-8620 DEBUG Adding task: 2986 / 0x46620a0
Jul 07 20:49:04-330740 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-330936 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-331126 util-scheduler-8620 DEBUG Checking readiness of task: 2983 / 0x4d5e5d8
Jul 07 20:49:04-331321 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-331511 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-331702 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-331892 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-332083 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-332271 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-332465 util-scheduler-8620 DEBUG Running task: 2983 / 0x4d5e5d8
Jul 07 20:49:04-332651 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:49:04-332829 util-8620 DEBUG process_notify is running
Jul 07 20:49:04-333015 util-8620 DEBUG client_notify is running
Jul 07 20:49:04-333292 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:49:04-333502 util-scheduler-8620 DEBUG Adding task: 2987 / 0x4d5e5d8
Jul 07 20:49:04-333704 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:49:04-333966 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:49:04-334164 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:49:04-334406 util-scheduler-8620 DEBUG Checking readiness of task: 2987 / 0x4d5e5d8
Jul 07 20:49:04-334599 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-334794 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-334984 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-335176 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-335366 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-335557 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-335745 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-335936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-336126 util-scheduler-8620 DEBUG Running task: 2987 / 0x4d5e5d8
Jul 07 20:49:04-336311 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:49:04-336485 util-8620 DEBUG process_notify is running
Jul 07 20:49:04-336655 util-8620 DEBUG client_notify is running
Jul 07 20:49:04-336879 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:49:04-337085 util-scheduler-8620 DEBUG Adding task: 2988 / 0x4d5e5d8
Jul 07 20:49:04-337306 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:49:04-337550 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:49:04-337746 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:49:04-337984 util-scheduler-8620 DEBUG Checking readiness of task: 2988 / 0x4d5e5d8
Jul 07 20:49:04-338178 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-338369 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-338560 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-338749 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-338939 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-339129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-339320 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-339508 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-339699 util-scheduler-8620 DEBUG Running task: 2988 / 0x4d5e5d8
Jul 07 20:49:04-339883 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:49:04-340057 util-8620 DEBUG process_notify is running
Jul 07 20:49:04-340226 util-8620 DEBUG client_notify is running
Jul 07 20:49:04-340434 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:49:04-340677 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:49:04-651451 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-651828 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-652025 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-652217 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-652410 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-652608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-652832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-653022 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-653237 util-scheduler-8620 DEBUG Running task: 2971 / 0x52cbfb8
Jul 07 20:49:04-653478 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:04-653724 cadet-tun-8620 DEBUG  kx started 100 s ago
Jul 07 20:49:04-653931 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:04-654131 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:04-654334 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:04-654570 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:04-654750 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:04-654974 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:04-655265 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:04-655462 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:04-655698 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:04-655906 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:04-656223 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:04-656424 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:04-656648 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:04-656830 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:04-657005 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:04-657234 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:04-657452 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:04-657683 util-scheduler-8620 DEBUG Adding task: 2989 / 0x59ee8a0
Jul 07 20:49:04-657865 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:04-658073 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:04-658250 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:04-658427 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:04-658666 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:04-658866 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:04-659045 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:04-659248 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:04-659497 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:04-659701 util-scheduler-8620 DEBUG Adding task: 2990 / 0x52cbfb8
Jul 07 20:49:04-659962 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-660157 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-660346 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-660535 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-660724 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-660913 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-661100 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-661313 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-661502 util-scheduler-8620 DEBUG Running task: 2989 / 0x59ee8a0
Jul 07 20:49:04-661711 util-scheduler-8620 DEBUG Adding task: 2991 / 0x59ee8a0
Jul 07 20:49:04-661934 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:04-662139 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:04-662347 util-scheduler-8620 DEBUG Adding task: 2992 / 0x46620a0
Jul 07 20:49:04-662589 util-scheduler-8620 DEBUG Checking readiness of task: 2992 / 0x46620a0
Jul 07 20:49:04-662783 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:04-662973 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:04-663184 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:04-663373 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:04-663563 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:04-663752 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:04-663941 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:04-664128 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:04-664320 util-scheduler-8620 DEBUG Running task: 2992 / 0x46620a0
Jul 07 20:49:04-664504 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:04-664683 util-8620 DEBUG process_notify is running
Jul 07 20:49:04-664869 util-8620 DEBUG client_notify is running
Jul 07 20:49:04-665050 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:04-665266 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:04-665459 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:04-665774 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:07-415962 util-scheduler-8620 DEBUG Checking readiness of task: 2986 / 0x46620a0
Jul 07 20:49:07-416375 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-416581 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-416795 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-417002 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-417219 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-417413 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-417608 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-417803 util-scheduler-8620 DEBUG Running task: 2986 / 0x46620a0
Jul 07 20:49:07-418223 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:07-418482 util-scheduler-8620 DEBUG Adding task: 2993 / 0x4662248
Jul 07 20:49:07-418766 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-418962 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-419154 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-419344 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-419535 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-419725 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-422345 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-422553 util-scheduler-8620 DEBUG Running task: 2993 / 0x4662248
Jul 07 20:49:07-422750 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:07-422953 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:07-423192 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:07-423404 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:07-423615 util-scheduler-8620 DEBUG Adding task: 2994 / 0x46620a0
Jul 07 20:49:07-423807 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:07-424016 util-scheduler-8620 DEBUG Adding task: 2995 / 0x46620a0
Jul 07 20:49:07-424273 util-scheduler-8620 DEBUG Checking readiness of task: 2995 / 0x46620a0
Jul 07 20:49:07-424473 util-scheduler-8620 DEBUG Checking readiness of task: 2994 / 0x46620a0
Jul 07 20:49:07-424666 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-424858 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-425052 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-425301 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-425495 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-425686 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-425875 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-426075 util-scheduler-8620 DEBUG Running task: 2994 / 0x46620a0
Jul 07 20:49:07-426262 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:07-426444 util-8620 DEBUG process_notify is running
Jul 07 20:49:07-426619 util-8620 DEBUG client_notify is running
Jul 07 20:49:07-426810 util-scheduler-8620 DEBUG Canceling task: 2991 / 0x59ee8a0
Jul 07 20:49:07-427047 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:07-427271 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:07-427517 cadet-p2p-8620 DEBUG Checking 0x5a18f08 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:07-427761 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:07-427942 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:07-428135 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:07-428428 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:07-428654 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:07-428869 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:07-429124 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:07-429357 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:07-429541 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:07-429759 util-scheduler-8620 DEBUG Canceling task: 2980 / 0x59e8808
Jul 07 20:49:07-429980 util-scheduler-8620 DEBUG Adding task: 2996 / 0x59e8808
Jul 07 20:49:07-430237 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:07-430415 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:07-430600 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:07-430809 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:07-430987 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:07-431186 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:07-431390 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:07-431597 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:07-431782 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:07-431964 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:07-432157 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:07-433023 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:07-433273 util-scheduler-8620 DEBUG Running task: 2995 / 0x46620a0
Jul 07 20:49:07-433684 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:07-433923 util-scheduler-8620 DEBUG Adding task: 2997 / 0x4662248
Jul 07 20:49:07-434190 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-434410 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-435091 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-435285 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-435478 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-435670 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-435860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-436051 util-scheduler-8620 DEBUG Running task: 2997 / 0x4662248
Jul 07 20:49:07-436242 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:49:07-436441 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:49:07-436691 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:49:07-436951 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 2FDYFV0X from V8XX
Jul 07 20:49:07-437169 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:49:07-437433 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:07-437646 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:07-437830 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:49:07-438002 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:49:07-438188 util-scheduler-8620 DEBUG Canceling task: 2943 / 0x59e8808
Jul 07 20:49:07-438414 util-scheduler-8620 DEBUG Adding task: 2998 / 0x59e8808
Jul 07 20:49:07-438661 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:49:07-438842 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:49:07-439038 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:49:07-439274 cadet-con-8620 DEBUG Connection 2FDYFV0X (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:49:07-439515 cadet-con-8620 INFO ===> {           BCK ACK} on connection 2FDYFV0X (->V8XX)
Jul 07 20:49:07-439755 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:07-439963 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:07-440262 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 36)
Jul 07 20:49:07-440461 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:07-440700 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:07-440885 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:07-441061 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:07-441291 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:49:07-441508 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:49:07-441730 util-scheduler-8620 DEBUG Adding task: 2999 / 0x59ee8a0
Jul 07 20:49:07-441911 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:07-442118 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:07-442295 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:07-442471 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:07-442711 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:07-442899 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:49:07-443075 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:49:07-443275 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:07-443460 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:07-443671 util-scheduler-8620 DEBUG Adding task: 3000 / 0x46620a0
Jul 07 20:49:07-443926 util-scheduler-8620 DEBUG Checking readiness of task: 3000 / 0x46620a0
Jul 07 20:49:07-444123 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-444316 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-444507 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-444699 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-444889 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-445079 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-445292 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-445485 util-scheduler-8620 DEBUG Running task: 2999 / 0x59ee8a0
Jul 07 20:49:07-445697 util-scheduler-8620 DEBUG Adding task: 3001 / 0x59ee8a0
Jul 07 20:49:07-445923 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:07-446126 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:07-446330 util-scheduler-8620 DEBUG Adding task: 3002 / 0x46620a0
Jul 07 20:49:07-446574 util-scheduler-8620 DEBUG Checking readiness of task: 3002 / 0x46620a0
Jul 07 20:49:07-446768 util-scheduler-8620 DEBUG Checking readiness of task: 3000 / 0x46620a0
Jul 07 20:49:07-446985 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:07-447178 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:07-447369 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:07-447560 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:07-447751 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:07-447941 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:07-448132 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:07-448325 util-scheduler-8620 DEBUG Running task: 3002 / 0x46620a0
Jul 07 20:49:07-448511 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:07-448690 util-8620 DEBUG process_notify is running
Jul 07 20:49:07-448864 util-8620 DEBUG client_notify is running
Jul 07 20:49:07-449047 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:07-449266 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:07-449459 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:07-449762 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:08-137538 util-scheduler-8620 DEBUG Checking readiness of task: 3000 / 0x46620a0
Jul 07 20:49:08-137920 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:08-138117 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:08-138309 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:08-138501 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:08-138692 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:08-138881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:08-139073 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:08-139268 util-scheduler-8620 DEBUG Running task: 3000 / 0x46620a0
Jul 07 20:49:08-139688 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:08-139940 util-scheduler-8620 DEBUG Adding task: 3003 / 0x4662248
Jul 07 20:49:08-140217 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:08-140412 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:08-140606 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:08-140801 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:08-140996 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:08-142935 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:08-143808 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:08-144042 util-scheduler-8620 DEBUG Running task: 3003 / 0x4662248
Jul 07 20:49:08-144237 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:08-144440 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:08-144681 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:08-144890 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:08-145098 util-scheduler-8620 DEBUG Adding task: 3004 / 0x46620a0
Jul 07 20:49:08-145310 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:08-145518 util-scheduler-8620 DEBUG Adding task: 3005 / 0x46620a0
Jul 07 20:49:08-145777 util-scheduler-8620 DEBUG Checking readiness of task: 3005 / 0x46620a0
Jul 07 20:49:08-145972 util-scheduler-8620 DEBUG Checking readiness of task: 3004 / 0x46620a0
Jul 07 20:49:08-146165 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:08-146355 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:08-146579 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:08-146770 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:08-146959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:08-147148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:08-147338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:08-147528 util-scheduler-8620 DEBUG Running task: 3004 / 0x46620a0
Jul 07 20:49:08-147713 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:08-147892 util-8620 DEBUG process_notify is running
Jul 07 20:49:08-148064 util-8620 DEBUG client_notify is running
Jul 07 20:49:08-148251 util-scheduler-8620 DEBUG Canceling task: 3001 / 0x59ee8a0
Jul 07 20:49:08-148477 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:49:08-148699 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:08-148937 cadet-p2p-8620 DEBUG Checking 0x5a1d678 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:08-149173 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:08-149372 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:49:08-149542 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:49:08-149711 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:49:08-149882 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:49:08-150143 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 36)
Jul 07 20:49:08-150337 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:08-150517 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:08-150704 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:49:08-150916 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:08-151091 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:08-151270 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:49:08-151471 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:08-151646 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:08-151820 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:08-152019 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:08-152223 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:49:08-152418 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:49:08-152597 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:08-152787 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:49:08-154084 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:09-661375 util-scheduler-8620 DEBUG Checking readiness of task: 3005 / 0x46620a0
Jul 07 20:49:09-661734 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:09-661930 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:09-662125 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:09-662318 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:09-662509 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:09-662701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:09-662892 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:09-663085 util-scheduler-8620 DEBUG Running task: 2990 / 0x52cbfb8
Jul 07 20:49:09-663323 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:09-663572 cadet-tun-8620 DEBUG  kx started 105 s ago
Jul 07 20:49:09-663780 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:09-663981 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:09-664183 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:09-664420 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:09-664600 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:09-664822 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:09-665139 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:09-665359 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:09-665598 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:09-665808 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:09-666128 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:09-666329 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:09-666554 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:09-666738 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:09-666915 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:09-667122 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:09-667337 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:09-667562 util-scheduler-8620 DEBUG Adding task: 3006 / 0x59ee8a0
Jul 07 20:49:09-667743 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:09-667947 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:09-668126 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:09-668301 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:09-668539 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:09-668735 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:09-668913 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:09-669112 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:09-669375 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:09-669577 util-scheduler-8620 DEBUG Adding task: 3007 / 0x52cbfb8
Jul 07 20:49:09-669834 util-scheduler-8620 DEBUG Checking readiness of task: 3005 / 0x46620a0
Jul 07 20:49:09-670027 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:09-670217 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:09-670407 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:09-670596 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:09-670788 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:09-670977 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:09-671167 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:09-671356 util-scheduler-8620 DEBUG Running task: 3006 / 0x59ee8a0
Jul 07 20:49:09-671565 util-scheduler-8620 DEBUG Adding task: 3008 / 0x59ee8a0
Jul 07 20:49:09-671787 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:09-671991 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:09-672199 util-scheduler-8620 DEBUG Adding task: 3009 / 0x46620a0
Jul 07 20:49:09-672443 util-scheduler-8620 DEBUG Checking readiness of task: 3009 / 0x46620a0
Jul 07 20:49:09-672637 util-scheduler-8620 DEBUG Checking readiness of task: 3005 / 0x46620a0
Jul 07 20:49:09-672827 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:09-673016 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:09-673226 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:09-673417 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:09-673608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:09-673797 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:09-673986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:09-674179 util-scheduler-8620 DEBUG Running task: 3009 / 0x46620a0
Jul 07 20:49:09-674364 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:09-674544 util-8620 DEBUG process_notify is running
Jul 07 20:49:09-674732 util-8620 DEBUG client_notify is running
Jul 07 20:49:09-674913 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:09-675109 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:09-675300 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:09-675555 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:12-725122 util-scheduler-8620 DEBUG Checking readiness of task: 3005 / 0x46620a0
Jul 07 20:49:12-725548 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:12-725752 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:12-725960 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:12-726154 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:12-726345 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:12-726535 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:12-726724 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:12-726919 util-scheduler-8620 DEBUG Running task: 3005 / 0x46620a0
Jul 07 20:49:12-727340 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:12-727595 util-scheduler-8620 DEBUG Adding task: 3010 / 0x4662248
Jul 07 20:49:12-727876 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:12-728071 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:12-728264 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:12-728459 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:12-728650 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:12-728839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:12-729028 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:12-733273 util-scheduler-8620 DEBUG Running task: 3010 / 0x4662248
Jul 07 20:49:12-733499 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:12-733706 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:12-733943 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:12-734151 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:12-734360 util-scheduler-8620 DEBUG Adding task: 3011 / 0x46620a0
Jul 07 20:49:12-734547 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:12-734755 util-scheduler-8620 DEBUG Adding task: 3012 / 0x46620a0
Jul 07 20:49:12-735006 util-scheduler-8620 DEBUG Checking readiness of task: 3012 / 0x46620a0
Jul 07 20:49:12-735200 util-scheduler-8620 DEBUG Checking readiness of task: 3011 / 0x46620a0
Jul 07 20:49:12-735392 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:12-735581 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:12-735786 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:12-735975 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:12-736164 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:12-736352 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:12-736541 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:12-736731 util-scheduler-8620 DEBUG Running task: 3011 / 0x46620a0
Jul 07 20:49:12-736920 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:12-737097 util-8620 DEBUG process_notify is running
Jul 07 20:49:12-737291 util-8620 DEBUG client_notify is running
Jul 07 20:49:12-737479 util-scheduler-8620 DEBUG Canceling task: 3008 / 0x59ee8a0
Jul 07 20:49:12-737736 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:12-737957 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:12-738198 cadet-p2p-8620 DEBUG Checking 0x5a1ffc0 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:12-738432 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:12-738609 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:12-738799 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:12-739083 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:12-739278 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:12-739457 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:12-739645 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:12-739834 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:12-740014 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:12-740204 util-scheduler-8620 DEBUG Canceling task: 2996 / 0x59e8808
Jul 07 20:49:12-740423 util-scheduler-8620 DEBUG Adding task: 3013 / 0x59e8808
Jul 07 20:49:12-740677 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:12-740850 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:12-741035 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:12-741262 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:12-741442 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:12-741618 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:12-741819 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:12-742028 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:12-742213 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:12-742394 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:12-742587 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:12-743376 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:14-671669 util-scheduler-8620 DEBUG Checking readiness of task: 3012 / 0x46620a0
Jul 07 20:49:14-672050 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:14-672246 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:14-672438 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:14-672631 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:14-672822 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:14-673011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:14-673227 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:14-673422 util-scheduler-8620 DEBUG Running task: 3007 / 0x52cbfb8
Jul 07 20:49:14-673661 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:14-673907 cadet-tun-8620 DEBUG  kx started 110 s ago
Jul 07 20:49:14-674114 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:14-674315 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:14-674518 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:14-674752 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:14-674933 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:14-675154 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:14-675445 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:14-675642 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:14-675880 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:14-676089 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:14-676409 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:14-676610 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:14-676835 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:14-677052 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:14-677252 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:14-677464 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:14-677679 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:14-677906 util-scheduler-8620 DEBUG Adding task: 3014 / 0x59ee8a0
Jul 07 20:49:14-678086 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:14-678291 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:14-678469 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:14-678645 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:14-678884 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:14-679079 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:14-679257 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:14-679454 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:14-679697 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:14-679895 util-scheduler-8620 DEBUG Adding task: 3015 / 0x52cbfb8
Jul 07 20:49:14-680153 util-scheduler-8620 DEBUG Checking readiness of task: 3012 / 0x46620a0
Jul 07 20:49:14-680347 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:14-680538 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:14-680728 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:14-680918 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:14-681107 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:14-681321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:14-681510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:14-681701 util-scheduler-8620 DEBUG Running task: 3014 / 0x59ee8a0
Jul 07 20:49:14-681908 util-scheduler-8620 DEBUG Adding task: 3016 / 0x59ee8a0
Jul 07 20:49:14-682131 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:14-682334 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:14-682542 util-scheduler-8620 DEBUG Adding task: 3017 / 0x46620a0
Jul 07 20:49:14-682786 util-scheduler-8620 DEBUG Checking readiness of task: 3017 / 0x46620a0
Jul 07 20:49:14-682980 util-scheduler-8620 DEBUG Checking readiness of task: 3012 / 0x46620a0
Jul 07 20:49:14-683171 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:14-683360 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:14-683550 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:14-683739 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:14-683930 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:14-684118 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:14-684308 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:14-684498 util-scheduler-8620 DEBUG Running task: 3017 / 0x46620a0
Jul 07 20:49:14-684684 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:14-684862 util-8620 DEBUG process_notify is running
Jul 07 20:49:14-685035 util-8620 DEBUG client_notify is running
Jul 07 20:49:14-685236 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:14-685433 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:14-685625 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:14-685894 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:18-039660 util-scheduler-8620 DEBUG Checking readiness of task: 3012 / 0x46620a0
Jul 07 20:49:18-040052 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:18-040283 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:18-040479 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:18-040678 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:18-040872 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:18-041064 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:18-041284 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:18-041482 util-scheduler-8620 DEBUG Running task: 3012 / 0x46620a0
Jul 07 20:49:18-041907 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:18-042165 util-scheduler-8620 DEBUG Adding task: 3018 / 0x4662248
Jul 07 20:49:18-042448 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:18-042644 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:18-042837 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:18-043029 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:18-043222 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:18-043414 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:18-043605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:18-043796 util-scheduler-8620 DEBUG Running task: 3018 / 0x4662248
Jul 07 20:49:18-043988 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:18-044191 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:18-044426 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:18-044635 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:18-044845 util-scheduler-8620 DEBUG Adding task: 3019 / 0x46620a0
Jul 07 20:49:18-045034 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:18-045340 util-scheduler-8620 DEBUG Adding task: 3020 / 0x46620a0
Jul 07 20:49:18-045592 util-scheduler-8620 DEBUG Checking readiness of task: 3020 / 0x46620a0
Jul 07 20:49:18-045789 util-scheduler-8620 DEBUG Checking readiness of task: 3019 / 0x46620a0
Jul 07 20:49:18-045984 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:18-046176 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:18-046367 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:18-046559 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:18-046751 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:18-046942 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:18-047134 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:18-047327 util-scheduler-8620 DEBUG Running task: 3019 / 0x46620a0
Jul 07 20:49:18-047516 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:18-047696 util-8620 DEBUG process_notify is running
Jul 07 20:49:18-047871 util-8620 DEBUG client_notify is running
Jul 07 20:49:18-048061 util-scheduler-8620 DEBUG Canceling task: 3016 / 0x59ee8a0
Jul 07 20:49:18-048290 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:18-048515 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:18-048757 cadet-p2p-8620 DEBUG Checking 0x5a22cb0 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:18-048993 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:18-049173 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:18-049391 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:18-049678 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:18-049876 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:18-050077 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:18-050268 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:18-050460 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:18-050645 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:18-050831 util-scheduler-8620 DEBUG Canceling task: 3013 / 0x59e8808
Jul 07 20:49:18-051046 util-scheduler-8620 DEBUG Adding task: 3021 / 0x59e8808
Jul 07 20:49:18-051298 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:18-051471 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:18-051653 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:18-051858 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:18-052035 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:18-052212 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:18-052413 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:18-052620 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:18-052806 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:18-052987 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:18-053182 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:18-056693 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:19-681692 util-scheduler-8620 DEBUG Checking readiness of task: 3020 / 0x46620a0
Jul 07 20:49:19-682088 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:19-682992 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:19-683194 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:19-683387 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:19-683579 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:19-683770 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:19-683959 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:19-684154 util-scheduler-8620 DEBUG Running task: 3015 / 0x52cbfb8
Jul 07 20:49:19-684393 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:19-684641 cadet-tun-8620 DEBUG  kx started 115 s ago
Jul 07 20:49:19-684849 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:19-685049 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:19-685279 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:19-685517 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:19-685698 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:19-685921 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:19-686213 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:19-686410 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:19-686646 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:19-686854 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:19-687172 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:19-687375 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:19-687601 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:19-687784 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:19-687959 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:19-688164 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:19-688383 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:19-688609 util-scheduler-8620 DEBUG Adding task: 3022 / 0x59ee8a0
Jul 07 20:49:19-688789 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:19-688993 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:19-689171 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:19-689425 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:19-689888 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:19-690260 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:19-690622 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:19-690883 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:19-691138 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:19-691339 util-scheduler-8620 DEBUG Adding task: 3023 / 0x52cbfb8
Jul 07 20:49:19-691604 util-scheduler-8620 DEBUG Checking readiness of task: 3020 / 0x46620a0
Jul 07 20:49:19-691798 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:19-691988 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:19-692183 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:19-692376 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:19-692571 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:19-692769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:19-692969 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:19-693170 util-scheduler-8620 DEBUG Running task: 3022 / 0x59ee8a0
Jul 07 20:49:19-693427 util-scheduler-8620 DEBUG Adding task: 3024 / 0x59ee8a0
Jul 07 20:49:19-693668 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:19-693881 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:19-694098 util-scheduler-8620 DEBUG Adding task: 3025 / 0x46620a0
Jul 07 20:49:19-694369 util-scheduler-8620 DEBUG Checking readiness of task: 3025 / 0x46620a0
Jul 07 20:49:19-694572 util-scheduler-8620 DEBUG Checking readiness of task: 3020 / 0x46620a0
Jul 07 20:49:19-694768 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:19-694967 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:19-695163 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:19-695364 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:19-695563 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:19-695764 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:19-695960 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:19-696158 util-scheduler-8620 DEBUG Running task: 3025 / 0x46620a0
Jul 07 20:49:19-696349 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:19-696536 util-8620 DEBUG process_notify is running
Jul 07 20:49:19-696716 util-8620 DEBUG client_notify is running
Jul 07 20:49:19-696901 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:19-697112 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:19-697344 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:19-697714 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:20-433005 util-scheduler-8620 DEBUG Checking readiness of task: 3020 / 0x46620a0
Jul 07 20:49:20-433414 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:20-433614 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:20-433807 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:20-433999 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:20-434194 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:20-434399 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:20-434623 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:20-434820 util-scheduler-8620 DEBUG Running task: 3020 / 0x46620a0
Jul 07 20:49:20-435275 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:20-435534 util-scheduler-8620 DEBUG Adding task: 3026 / 0x4662248
Jul 07 20:49:20-435814 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:20-436008 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:20-436200 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:20-436389 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:20-436581 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:20-436770 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:20-436959 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:20-437149 util-scheduler-8620 DEBUG Running task: 3026 / 0x4662248
Jul 07 20:49:20-437367 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:20-437567 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:20-437799 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:20-438005 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:20-438212 util-scheduler-8620 DEBUG Adding task: 3027 / 0x46620a0
Jul 07 20:49:20-438401 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:20-438607 util-scheduler-8620 DEBUG Adding task: 3028 / 0x46620a0
Jul 07 20:49:20-438851 util-scheduler-8620 DEBUG Checking readiness of task: 3028 / 0x46620a0
Jul 07 20:49:20-439044 util-scheduler-8620 DEBUG Checking readiness of task: 3027 / 0x46620a0
Jul 07 20:49:20-439236 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:20-439426 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:20-439616 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:20-439807 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:20-439996 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:20-440185 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:20-440373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:20-440565 util-scheduler-8620 DEBUG Running task: 3027 / 0x46620a0
Jul 07 20:49:20-440748 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:20-440927 util-8620 DEBUG process_notify is running
Jul 07 20:49:20-441099 util-8620 DEBUG client_notify is running
Jul 07 20:49:20-441307 util-scheduler-8620 DEBUG Canceling task: 3024 / 0x59ee8a0
Jul 07 20:49:20-441533 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:20-441754 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:20-441994 cadet-p2p-8620 DEBUG Checking 0x5a25898 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:20-442227 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:20-442405 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:20-442596 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:20-442882 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:20-443078 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:20-443257 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:20-443445 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:20-443633 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:20-443812 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:20-443996 util-scheduler-8620 DEBUG Canceling task: 3021 / 0x59e8808
Jul 07 20:49:20-444207 util-scheduler-8620 DEBUG Adding task: 3029 / 0x59e8808
Jul 07 20:49:20-444459 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:20-444630 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:20-444810 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:20-445030 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:20-445226 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:20-445404 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:20-445603 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:20-445808 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:20-445992 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:20-446172 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:20-446362 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:20-446611 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:24-695744 util-scheduler-8620 DEBUG Checking readiness of task: 3028 / 0x46620a0
Jul 07 20:49:24-696129 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:24-698108 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:24-698321 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:24-698518 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:24-698725 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:24-698916 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:24-699107 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:24-699299 util-scheduler-8620 DEBUG Running task: 3023 / 0x52cbfb8
Jul 07 20:49:24-699538 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:24-699796 cadet-tun-8620 DEBUG  kx started 2 m ago
Jul 07 20:49:24-700002 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:24-700204 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:24-700407 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:24-700641 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:24-700822 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:24-701044 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:24-701364 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:24-701562 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:24-701800 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:24-702011 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:24-702334 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:24-702535 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:24-702760 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:24-702943 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:24-703119 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:24-703324 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:24-703540 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:24-703766 util-scheduler-8620 DEBUG Adding task: 3030 / 0x59ee8a0
Jul 07 20:49:24-703949 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:24-704152 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:24-704330 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:24-704505 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:24-704744 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:24-704939 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:24-705116 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:24-705338 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:24-705582 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:24-705781 util-scheduler-8620 DEBUG Adding task: 3031 / 0x52cbfb8
Jul 07 20:49:24-706040 util-scheduler-8620 DEBUG Checking readiness of task: 3028 / 0x46620a0
Jul 07 20:49:24-706260 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:24-706452 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:24-706642 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:24-706832 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:24-707024 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:24-707213 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:24-707401 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:24-707590 util-scheduler-8620 DEBUG Running task: 3030 / 0x59ee8a0
Jul 07 20:49:24-707798 util-scheduler-8620 DEBUG Adding task: 3032 / 0x59ee8a0
Jul 07 20:49:24-708020 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:24-708224 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:24-708432 util-scheduler-8620 DEBUG Adding task: 3033 / 0x46620a0
Jul 07 20:49:24-708676 util-scheduler-8620 DEBUG Checking readiness of task: 3033 / 0x46620a0
Jul 07 20:49:24-708870 util-scheduler-8620 DEBUG Checking readiness of task: 3028 / 0x46620a0
Jul 07 20:49:24-709060 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:24-709273 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:24-709463 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:24-709653 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:24-709842 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:24-710030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:24-710220 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:24-710411 util-scheduler-8620 DEBUG Running task: 3033 / 0x46620a0
Jul 07 20:49:24-710595 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:24-710773 util-8620 DEBUG process_notify is running
Jul 07 20:49:24-710945 util-8620 DEBUG client_notify is running
Jul 07 20:49:24-711125 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:24-711319 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:24-711511 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:24-711767 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:25-008441 util-scheduler-8620 DEBUG Checking readiness of task: 3028 / 0x46620a0
Jul 07 20:49:25-008706 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:25-008908 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:25-009231 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:25-009428 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:25-009625 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:25-009822 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:25-010026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:25-010221 util-scheduler-8620 DEBUG Running task: 3028 / 0x46620a0
Jul 07 20:49:25-010633 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:25-010878 util-scheduler-8620 DEBUG Adding task: 3034 / 0x4662248
Jul 07 20:49:25-011140 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:25-011336 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:25-011528 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:25-011719 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:25-011912 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:25-012126 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:25-012319 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:25-012511 util-scheduler-8620 DEBUG Running task: 3034 / 0x4662248
Jul 07 20:49:25-012704 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:25-012904 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:25-013130 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:25-013357 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:25-013562 util-scheduler-8620 DEBUG Adding task: 3035 / 0x46620a0
Jul 07 20:49:25-013750 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:25-013957 util-scheduler-8620 DEBUG Adding task: 3036 / 0x46620a0
Jul 07 20:49:25-014200 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:25-014396 util-scheduler-8620 DEBUG Checking readiness of task: 3035 / 0x46620a0
Jul 07 20:49:25-014590 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:25-014783 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:25-014976 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:25-015167 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:25-015359 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:25-015549 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:25-015741 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:25-015933 util-scheduler-8620 DEBUG Running task: 3035 / 0x46620a0
Jul 07 20:49:25-016120 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:25-016297 util-8620 DEBUG process_notify is running
Jul 07 20:49:25-016470 util-8620 DEBUG client_notify is running
Jul 07 20:49:25-016670 util-scheduler-8620 DEBUG Canceling task: 3032 / 0x59ee8a0
Jul 07 20:49:25-016897 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:25-017117 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:25-017376 cadet-p2p-8620 DEBUG Checking 0x5a284a8 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:25-017612 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:25-017792 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:25-017983 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:25-018268 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:25-018465 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:25-018646 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:25-018834 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:25-019024 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:25-019204 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:25-019389 util-scheduler-8620 DEBUG Canceling task: 3029 / 0x59e8808
Jul 07 20:49:25-019606 util-scheduler-8620 DEBUG Adding task: 3037 / 0x59e8808
Jul 07 20:49:25-019854 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:25-020027 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:25-020210 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:25-020413 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:25-020591 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:25-020766 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:25-020966 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:25-021173 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:25-021378 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:25-021559 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:25-021751 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:25-022016 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:29-707239 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-707630 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-709585 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-709794 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:29-709989 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-710183 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-710374 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-710563 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-710758 util-scheduler-8620 DEBUG Running task: 3031 / 0x52cbfb8
Jul 07 20:49:29-710997 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:29-711243 cadet-tun-8620 DEBUG  kx started 125 s ago
Jul 07 20:49:29-711450 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:29-711650 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:29-711852 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:29-712088 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:29-712269 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:29-712489 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:29-712781 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:29-712978 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:29-713287 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:29-713501 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:29-713824 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:29-714025 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:29-714250 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:29-714434 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:29-714609 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:29-714815 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:29-715033 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:29-715260 util-scheduler-8620 DEBUG Adding task: 3038 / 0x59ee8a0
Jul 07 20:49:29-715441 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:29-715644 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:29-715821 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:29-715996 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:29-716233 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:29-716429 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:29-716607 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:29-716805 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:29-717048 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:29-717266 util-scheduler-8620 DEBUG Adding task: 3039 / 0x52cbfb8
Jul 07 20:49:29-717529 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-717722 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-717912 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-718100 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:29-718290 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-718479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-718669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-718857 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-719046 util-scheduler-8620 DEBUG Running task: 3038 / 0x59ee8a0
Jul 07 20:49:29-719281 util-scheduler-8620 DEBUG Adding task: 3040 / 0x59ee8a0
Jul 07 20:49:29-719504 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:29-719708 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:29-719916 util-scheduler-8620 DEBUG Adding task: 3041 / 0x46620a0
Jul 07 20:49:29-720159 util-scheduler-8620 DEBUG Checking readiness of task: 3041 / 0x46620a0
Jul 07 20:49:29-720353 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-720544 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-720733 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-720923 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:29-721112 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-721325 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-721514 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-721705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-721895 util-scheduler-8620 DEBUG Running task: 3041 / 0x46620a0
Jul 07 20:49:29-722081 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:29-722259 util-8620 DEBUG process_notify is running
Jul 07 20:49:29-722432 util-8620 DEBUG client_notify is running
Jul 07 20:49:29-722611 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:29-722807 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:29-722998 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:29-723254 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:29-725484 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-725745 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-725941 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-726132 util-scheduler-8620 DEBUG Checking readiness of task: 2962 / 0x465ee60
Jul 07 20:49:29-726327 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-726522 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-726711 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-726913 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-727105 util-scheduler-8620 DEBUG Running task: 2962 / 0x465ee60
Jul 07 20:49:29-727523 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:49:29-727772 util-scheduler-8620 DEBUG Adding task: 3042 / 0x465f008
Jul 07 20:49:29-728034 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-728228 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-728418 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-728607 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-728798 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-728987 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-729175 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-729394 util-scheduler-8620 DEBUG Running task: 3042 / 0x465f008
Jul 07 20:49:29-729589 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:49:29-729824 nse-api-8620 DEBUG Received information about peer `F61H' from peerinfo database
Jul 07 20:49:29-730011 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:49:29-730220 util-scheduler-8620 DEBUG Adding task: 3043 / 0x465f008
Jul 07 20:49:29-730484 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:29-730677 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:29-730867 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:29-731056 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:29-731246 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:29-731435 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:29-731624 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:29-731812 util-scheduler-8620 DEBUG Running task: 3043 / 0x465f008
Jul 07 20:49:29-732001 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:49:29-732217 nse-api-8620 DEBUG Received information about peer `F61H' from peerinfo database
Jul 07 20:49:29-732490 cadet-hll-8620 DEBUG  hello for F61H (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:49:29-732746 cadet-p2p-8620 DEBUG set hello for F61H
Jul 07 20:49:29-732923 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:49:29-733111 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:29-733345 util-scheduler-8620 DEBUG Adding task: 3044 / 0x465ee60
Jul 07 20:49:31-245629 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:31-246018 util-scheduler-8620 DEBUG Checking readiness of task: 3036 / 0x46620a0
Jul 07 20:49:31-246219 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:31-246411 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:31-246604 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:31-246796 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:31-246989 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:31-247179 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:31-247376 util-scheduler-8620 DEBUG Running task: 3036 / 0x46620a0
Jul 07 20:49:31-247801 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:31-248058 util-scheduler-8620 DEBUG Adding task: 3045 / 0x4662248
Jul 07 20:49:31-248338 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:31-248532 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:31-248722 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:31-248914 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:31-249105 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:31-249325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:31-249515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:31-249706 util-scheduler-8620 DEBUG Running task: 3045 / 0x4662248
Jul 07 20:49:31-249897 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:31-250104 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:31-250338 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:31-250547 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:31-250755 util-scheduler-8620 DEBUG Adding task: 3046 / 0x46620a0
Jul 07 20:49:31-250944 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:31-251150 util-scheduler-8620 DEBUG Adding task: 3047 / 0x46620a0
Jul 07 20:49:31-251399 util-scheduler-8620 DEBUG Checking readiness of task: 3047 / 0x46620a0
Jul 07 20:49:31-251596 util-scheduler-8620 DEBUG Checking readiness of task: 3046 / 0x46620a0
Jul 07 20:49:31-251789 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:31-251979 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:31-252200 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:31-252393 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:31-252582 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:31-252772 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:31-252960 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:31-253153 util-scheduler-8620 DEBUG Running task: 3046 / 0x46620a0
Jul 07 20:49:31-253365 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:31-253544 util-8620 DEBUG process_notify is running
Jul 07 20:49:31-253717 util-8620 DEBUG client_notify is running
Jul 07 20:49:31-253909 util-scheduler-8620 DEBUG Canceling task: 3040 / 0x59ee8a0
Jul 07 20:49:31-254135 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:31-254356 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:31-254596 cadet-p2p-8620 DEBUG Checking 0x5a2b1c0 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:31-254831 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:31-255009 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:31-255201 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:31-255485 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:31-255681 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:31-255861 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:31-256050 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:31-256239 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:31-256417 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:31-256603 util-scheduler-8620 DEBUG Canceling task: 3037 / 0x59e8808
Jul 07 20:49:31-256816 util-scheduler-8620 DEBUG Adding task: 3048 / 0x59e8808
Jul 07 20:49:31-257067 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:31-257263 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:31-257446 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:31-257649 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:31-257826 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:31-258001 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:31-258199 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:31-258404 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:31-258588 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:31-258768 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:31-258960 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:31-259970 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:34-720921 util-scheduler-8620 DEBUG Checking readiness of task: 3047 / 0x46620a0
Jul 07 20:49:34-721339 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:34-722615 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:34-722983 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:34-723179 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:34-723372 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:34-723562 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:34-723764 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:34-723958 util-scheduler-8620 DEBUG Running task: 3039 / 0x52cbfb8
Jul 07 20:49:34-724198 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:34-724445 cadet-tun-8620 DEBUG  kx started 130 s ago
Jul 07 20:49:34-724651 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:34-724852 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:34-725055 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:34-725375 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:34-725561 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:34-725784 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:34-726077 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:34-726275 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:34-726512 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:34-726721 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:34-727041 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:34-727243 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:34-727468 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:34-727651 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:34-727827 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:34-728034 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:34-728250 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:34-728476 util-scheduler-8620 DEBUG Adding task: 3049 / 0x59ee8a0
Jul 07 20:49:34-728656 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:34-728859 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:34-729037 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:34-729237 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:34-729497 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:34-729694 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:34-729871 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:34-730070 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:34-730315 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:34-730513 util-scheduler-8620 DEBUG Adding task: 3050 / 0x52cbfb8
Jul 07 20:49:34-730779 util-scheduler-8620 DEBUG Checking readiness of task: 3047 / 0x46620a0
Jul 07 20:49:34-730972 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:34-731162 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:34-731352 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:34-731541 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:34-731733 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:34-731922 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:34-732110 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:34-732301 util-scheduler-8620 DEBUG Running task: 3049 / 0x59ee8a0
Jul 07 20:49:34-732508 util-scheduler-8620 DEBUG Adding task: 3051 / 0x59ee8a0
Jul 07 20:49:34-732732 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:34-732935 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:34-733143 util-scheduler-8620 DEBUG Adding task: 3052 / 0x46620a0
Jul 07 20:49:34-733417 util-scheduler-8620 DEBUG Checking readiness of task: 3052 / 0x46620a0
Jul 07 20:49:34-733613 util-scheduler-8620 DEBUG Checking readiness of task: 3047 / 0x46620a0
Jul 07 20:49:34-733803 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:34-733993 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:34-734183 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:34-734373 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:34-734562 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:34-734750 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:34-734939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:34-735130 util-scheduler-8620 DEBUG Running task: 3052 / 0x46620a0
Jul 07 20:49:34-735331 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:34-735514 util-8620 DEBUG process_notify is running
Jul 07 20:49:34-735686 util-8620 DEBUG client_notify is running
Jul 07 20:49:34-735866 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:34-736062 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:34-736254 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:34-736513 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:39-202011 util-scheduler-8620 DEBUG Checking readiness of task: 3047 / 0x46620a0
Jul 07 20:49:39-202405 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-202603 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-202796 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-203002 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-203195 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-203386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-203579 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-203776 util-scheduler-8620 DEBUG Running task: 3047 / 0x46620a0
Jul 07 20:49:39-204198 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:39-204456 util-scheduler-8620 DEBUG Adding task: 3053 / 0x4662248
Jul 07 20:49:39-204735 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-204929 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-205119 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-205341 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-205533 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-205725 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-205914 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-206103 util-scheduler-8620 DEBUG Running task: 3053 / 0x4662248
Jul 07 20:49:39-206294 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:39-206495 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:39-206731 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:39-206941 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:39-207149 util-scheduler-8620 DEBUG Adding task: 3054 / 0x46620a0
Jul 07 20:49:39-207338 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:39-207544 util-scheduler-8620 DEBUG Adding task: 3055 / 0x46620a0
Jul 07 20:49:39-207787 util-scheduler-8620 DEBUG Checking readiness of task: 3055 / 0x46620a0
Jul 07 20:49:39-207980 util-scheduler-8620 DEBUG Checking readiness of task: 3054 / 0x46620a0
Jul 07 20:49:39-208173 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-208365 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-208555 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-208747 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-208937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-209125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-209342 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-209686 util-scheduler-8620 DEBUG Running task: 3054 / 0x46620a0
Jul 07 20:49:39-209878 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:39-210058 util-8620 DEBUG process_notify is running
Jul 07 20:49:39-210272 util-8620 DEBUG client_notify is running
Jul 07 20:49:39-210463 util-scheduler-8620 DEBUG Canceling task: 3051 / 0x59ee8a0
Jul 07 20:49:39-210695 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:39-210918 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:39-211173 cadet-p2p-8620 DEBUG Checking 0x5a2e7b0 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:39-211409 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:39-211588 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:39-211780 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:39-212067 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:39-212670 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:39-212854 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:39-213042 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:39-213253 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:39-213436 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:39-213621 util-scheduler-8620 DEBUG Canceling task: 3048 / 0x59e8808
Jul 07 20:49:39-213833 util-scheduler-8620 DEBUG Adding task: 3056 / 0x59e8808
Jul 07 20:49:39-214084 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:39-214253 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:39-214434 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:39-214635 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:39-214809 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:39-214983 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:39-215181 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:39-215385 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:39-215567 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:39-215746 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:39-215937 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:39-216189 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:39-731184 util-scheduler-8620 DEBUG Checking readiness of task: 3055 / 0x46620a0
Jul 07 20:49:39-731555 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-734788 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-735151 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-735352 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-735545 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-735737 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-735928 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-736121 util-scheduler-8620 DEBUG Running task: 3050 / 0x52cbfb8
Jul 07 20:49:39-736361 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:39-736609 cadet-tun-8620 DEBUG  kx started 135 s ago
Jul 07 20:49:39-736819 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:39-737019 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:39-737306 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:39-737544 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:39-737726 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:39-737947 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:39-738238 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:39-738436 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:39-738673 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:39-738882 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:39-739203 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:39-739439 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:39-739665 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:39-739849 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:39-740026 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:39-740232 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:39-740446 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:39-740671 util-scheduler-8620 DEBUG Adding task: 3057 / 0x59ee8a0
Jul 07 20:49:39-740850 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:39-741054 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:39-741258 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:39-741436 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:39-741674 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:39-741869 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:39-742047 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:39-742245 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:39-742490 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:39-742687 util-scheduler-8620 DEBUG Adding task: 3058 / 0x52cbfb8
Jul 07 20:49:39-742953 util-scheduler-8620 DEBUG Checking readiness of task: 3055 / 0x46620a0
Jul 07 20:49:39-743147 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-743337 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-743527 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-743716 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-743906 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-744094 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-744283 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-744472 util-scheduler-8620 DEBUG Running task: 3057 / 0x59ee8a0
Jul 07 20:49:39-744680 util-scheduler-8620 DEBUG Adding task: 3059 / 0x59ee8a0
Jul 07 20:49:39-744902 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:39-745106 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:39-745342 util-scheduler-8620 DEBUG Adding task: 3060 / 0x46620a0
Jul 07 20:49:39-745587 util-scheduler-8620 DEBUG Checking readiness of task: 3060 / 0x46620a0
Jul 07 20:49:39-745783 util-scheduler-8620 DEBUG Checking readiness of task: 3055 / 0x46620a0
Jul 07 20:49:39-745974 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:39-746162 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:39-746353 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:39-746542 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:39-746732 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:39-746925 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:39-747114 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:39-747304 util-scheduler-8620 DEBUG Running task: 3060 / 0x46620a0
Jul 07 20:49:39-747490 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:39-747667 util-8620 DEBUG process_notify is running
Jul 07 20:49:39-747841 util-8620 DEBUG client_notify is running
Jul 07 20:49:39-748020 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:39-748214 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:39-748406 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:39-748665 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:43-775580 util-scheduler-8620 DEBUG Checking readiness of task: 3055 / 0x46620a0
Jul 07 20:49:43-775986 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:43-776184 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:43-776384 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:43-776594 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:43-776791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:43-776982 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:43-777170 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:43-777392 util-scheduler-8620 DEBUG Running task: 3055 / 0x46620a0
Jul 07 20:49:43-777833 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:43-778091 util-scheduler-8620 DEBUG Adding task: 3061 / 0x4662248
Jul 07 20:49:43-778373 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:43-778566 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:43-778756 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:43-778946 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:43-779137 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:43-779332 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:43-779522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:43-779712 util-scheduler-8620 DEBUG Running task: 3061 / 0x4662248
Jul 07 20:49:43-779910 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:43-780112 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:43-780352 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:43-780562 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:43-780769 util-scheduler-8620 DEBUG Adding task: 3062 / 0x46620a0
Jul 07 20:49:43-780954 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:43-781160 util-scheduler-8620 DEBUG Adding task: 3063 / 0x46620a0
Jul 07 20:49:43-781433 util-scheduler-8620 DEBUG Checking readiness of task: 3063 / 0x46620a0
Jul 07 20:49:43-781627 util-scheduler-8620 DEBUG Checking readiness of task: 3062 / 0x46620a0
Jul 07 20:49:43-781820 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:43-782010 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:43-782201 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:43-782394 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:43-782584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:43-782777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:43-782969 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:43-783162 util-scheduler-8620 DEBUG Running task: 3062 / 0x46620a0
Jul 07 20:49:43-783349 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:43-783527 util-8620 DEBUG process_notify is running
Jul 07 20:49:43-783699 util-8620 DEBUG client_notify is running
Jul 07 20:49:43-783890 util-scheduler-8620 DEBUG Canceling task: 3059 / 0x59ee8a0
Jul 07 20:49:43-784122 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:43-784344 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:43-784590 cadet-p2p-8620 DEBUG Checking 0x5a31480 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:43-784835 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:43-785014 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:43-785685 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:43-786030 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:43-786231 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:43-786415 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:43-786604 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:43-786795 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:43-786975 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:43-787164 util-scheduler-8620 DEBUG Canceling task: 3056 / 0x59e8808
Jul 07 20:49:43-787382 util-scheduler-8620 DEBUG Adding task: 3064 / 0x59e8808
Jul 07 20:49:43-787637 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:43-787809 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:43-787992 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:43-788194 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:43-788371 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:43-788547 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:43-788747 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:43-788953 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:43-789138 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:43-789344 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:43-789537 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:43-789871 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:44-743823 util-scheduler-8620 DEBUG Checking readiness of task: 3063 / 0x46620a0
Jul 07 20:49:44-744212 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:44-744409 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:44-744601 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:44-744794 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:44-744986 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:44-745176 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:44-745393 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:44-745588 util-scheduler-8620 DEBUG Running task: 3058 / 0x52cbfb8
Jul 07 20:49:44-745826 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:44-746071 cadet-tun-8620 DEBUG  kx started 140 s ago
Jul 07 20:49:44-746278 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:44-746479 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:44-746681 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:44-746917 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:44-747098 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:44-747320 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:44-747610 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:44-747809 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:44-748049 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:44-748259 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:44-748579 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:44-748781 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:44-749005 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:44-749211 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:44-749390 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:44-749597 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:44-749811 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:44-750036 util-scheduler-8620 DEBUG Adding task: 3065 / 0x59ee8a0
Jul 07 20:49:44-750218 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:44-750452 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:44-750630 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:44-750806 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:44-751044 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:44-751240 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:44-751419 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:44-751616 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:44-751861 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:44-752058 util-scheduler-8620 DEBUG Adding task: 3066 / 0x52cbfb8
Jul 07 20:49:44-752316 util-scheduler-8620 DEBUG Checking readiness of task: 3063 / 0x46620a0
Jul 07 20:49:44-752508 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:44-752698 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:44-752888 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:44-753078 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:44-755860 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:44-756088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:44-756296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:44-756488 util-scheduler-8620 DEBUG Running task: 3065 / 0x59ee8a0
Jul 07 20:49:44-756705 util-scheduler-8620 DEBUG Adding task: 3067 / 0x59ee8a0
Jul 07 20:49:44-756935 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:44-757140 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:44-757379 util-scheduler-8620 DEBUG Adding task: 3068 / 0x46620a0
Jul 07 20:49:44-757633 util-scheduler-8620 DEBUG Checking readiness of task: 3068 / 0x46620a0
Jul 07 20:49:44-757828 util-scheduler-8620 DEBUG Checking readiness of task: 3063 / 0x46620a0
Jul 07 20:49:44-758022 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:44-758213 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:44-758402 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:44-758592 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:44-758782 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:44-758970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:44-759158 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:44-759351 util-scheduler-8620 DEBUG Running task: 3068 / 0x46620a0
Jul 07 20:49:44-759537 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:44-759714 util-8620 DEBUG process_notify is running
Jul 07 20:49:44-759888 util-8620 DEBUG client_notify is running
Jul 07 20:49:44-760067 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:44-760264 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:44-760456 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:44-760771 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:46-538844 util-scheduler-8620 DEBUG Checking readiness of task: 3063 / 0x46620a0
Jul 07 20:49:46-539205 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:46-539412 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:46-539607 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:46-539800 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:46-539992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:46-540183 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:46-540407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:46-540603 util-scheduler-8620 DEBUG Running task: 3063 / 0x46620a0
Jul 07 20:49:46-541022 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:46-541303 util-scheduler-8620 DEBUG Adding task: 3069 / 0x4662248
Jul 07 20:49:46-541578 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:46-543517 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:46-543711 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:46-543904 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:46-544095 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:46-544286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:46-544479 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:46-544669 util-scheduler-8620 DEBUG Running task: 3069 / 0x4662248
Jul 07 20:49:46-544861 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:46-545060 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:46-545319 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:46-545526 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:46-545732 util-scheduler-8620 DEBUG Adding task: 3070 / 0x46620a0
Jul 07 20:49:46-545921 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:46-546127 util-scheduler-8620 DEBUG Adding task: 3071 / 0x46620a0
Jul 07 20:49:46-546374 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:46-546567 util-scheduler-8620 DEBUG Checking readiness of task: 3070 / 0x46620a0
Jul 07 20:49:46-546760 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:46-546950 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:46-547141 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:46-547332 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:46-547521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:46-547712 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:46-547900 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:46-548093 util-scheduler-8620 DEBUG Running task: 3070 / 0x46620a0
Jul 07 20:49:46-548278 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:46-548459 util-8620 DEBUG process_notify is running
Jul 07 20:49:46-548631 util-8620 DEBUG client_notify is running
Jul 07 20:49:46-548819 util-scheduler-8620 DEBUG Canceling task: 3067 / 0x59ee8a0
Jul 07 20:49:46-549045 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:46-549290 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:46-549531 cadet-p2p-8620 DEBUG Checking 0x5a340e8 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:46-549767 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:46-549945 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:46-550136 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:46-550422 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:46-550619 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:46-550800 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:46-550989 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:46-551179 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:46-551359 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:46-551543 util-scheduler-8620 DEBUG Canceling task: 3064 / 0x59e8808
Jul 07 20:49:46-551756 util-scheduler-8620 DEBUG Adding task: 3072 / 0x59e8808
Jul 07 20:49:46-552026 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:46-552199 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:46-552381 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:46-552583 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:46-552760 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:46-552936 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:46-553135 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:46-553365 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:46-553550 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:46-553730 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:46-553921 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:46-554736 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:47-611358 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:47-611744 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:47-611940 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:47-612133 util-scheduler-8620 DEBUG Checking readiness of task: 2964 / 0x4663d68
Jul 07 20:49:47-612327 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:47-612519 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:47-612709 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:47-612899 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:47-613093 util-scheduler-8620 DEBUG Running task: 2964 / 0x4663d68
Jul 07 20:49:47-613546 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:49:47-613806 util-scheduler-8620 DEBUG Adding task: 3073 / 0x4663f10
Jul 07 20:49:47-614086 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:47-614279 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:47-614469 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:47-614660 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:47-614849 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:47-615051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:47-615239 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:47-615429 util-scheduler-8620 DEBUG Running task: 3073 / 0x4663f10
Jul 07 20:49:47-615620 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:49:47-615820 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:47-616036 util-scheduler-8620 DEBUG Adding task: 3074 / 0x4663d68
Jul 07 20:49:47-616222 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:49:47-616453 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `TZQE' with quota 9216
Jul 07 20:49:47-616648 util-bandwidth-8620 DEBUG Tracker 0x4d73060 bandwidth changed to 9216 Bps
Jul 07 20:49:47-616907 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 9216 Bps, last update was 49 s ago
Jul 07 20:49:47-617129 util-scheduler-8620 DEBUG Adding task: 3075 / 0x4d73060
Jul 07 20:49:47-617661 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:47-617859 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:47-618050 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:47-618240 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:47-618432 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:47-618621 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:47-618810 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:47-619029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:47-619220 util-scheduler-8620 DEBUG Running task: 3075 / 0x4d73060
Jul 07 20:49:48-265508 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:48-265884 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:48-266080 util-scheduler-8620 DEBUG Checking readiness of task: 3044 / 0x465ee60
Jul 07 20:49:48-266275 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:48-266467 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:48-266658 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:48-266850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:48-267044 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:48-267240 util-scheduler-8620 DEBUG Running task: 3044 / 0x465ee60
Jul 07 20:49:48-267664 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:49:48-267920 util-scheduler-8620 DEBUG Adding task: 3076 / 0x465f008
Jul 07 20:49:48-268199 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:48-268393 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:48-268584 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:48-268775 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:48-268965 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:48-269154 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:48-269377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:48-269568 util-scheduler-8620 DEBUG Running task: 3076 / 0x465f008
Jul 07 20:49:48-269759 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:49:48-270001 nse-api-8620 DEBUG Received information about peer `Z1WM' from peerinfo database
Jul 07 20:49:48-270191 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:49:48-270403 util-scheduler-8620 DEBUG Adding task: 3077 / 0x465f008
Jul 07 20:49:48-270642 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:48-270905 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:48-271098 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:48-271289 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:48-271479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:48-271668 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:48-271857 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:48-272045 util-scheduler-8620 DEBUG Running task: 3077 / 0x465f008
Jul 07 20:49:48-272235 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:49:48-272452 nse-api-8620 DEBUG Received information about peer `Z1WM' from peerinfo database
Jul 07 20:49:48-272722 cadet-hll-8620 DEBUG  hello for Z1WM (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:49:48-273281 cadet-p2p-8620 DEBUG set hello for Z1WM
Jul 07 20:49:48-273465 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:49:48-273655 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:48-273868 util-scheduler-8620 DEBUG Adding task: 3078 / 0x465ee60
Jul 07 20:49:49-753417 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:49-753819 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:49-754016 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:49-755134 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:49-755524 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:49-755723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:49-755914 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:49-756104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:49-756305 util-scheduler-8620 DEBUG Running task: 3066 / 0x52cbfb8
Jul 07 20:49:49-756544 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:49-756793 cadet-tun-8620 DEBUG  kx started 145 s ago
Jul 07 20:49:49-757001 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:49-757227 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:49-757435 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:49-757671 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:49-757853 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:49-758074 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:49-758367 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:49-758565 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:49-758801 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:49-759010 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:49-759329 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:49-759530 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:49-759754 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:49-760050 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:49-760229 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:49-760435 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:49-760652 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:49-760878 util-scheduler-8620 DEBUG Adding task: 3079 / 0x59ee8a0
Jul 07 20:49:49-761059 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:49-761286 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:49-761464 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:49-761639 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:49-761877 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:49-762073 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:49-762249 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:49-762448 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:49-762691 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:49-762889 util-scheduler-8620 DEBUG Adding task: 3080 / 0x52cbfb8
Jul 07 20:49:49-763154 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:49-763346 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:49-763535 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:49-763725 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:49-763915 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:49-764117 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:49-764307 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:49-764495 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:49-764686 util-scheduler-8620 DEBUG Running task: 3079 / 0x59ee8a0
Jul 07 20:49:49-764894 util-scheduler-8620 DEBUG Adding task: 3081 / 0x59ee8a0
Jul 07 20:49:49-765119 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:49-765348 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:49-765559 util-scheduler-8620 DEBUG Adding task: 3082 / 0x46620a0
Jul 07 20:49:49-765805 util-scheduler-8620 DEBUG Checking readiness of task: 3082 / 0x46620a0
Jul 07 20:49:49-765999 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:49-766205 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:49-766399 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:49-766588 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:49-766779 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:49-766969 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:49-767158 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:49-767347 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:49-767540 util-scheduler-8620 DEBUG Running task: 3082 / 0x46620a0
Jul 07 20:49:49-767725 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:49-767903 util-8620 DEBUG process_notify is running
Jul 07 20:49:49-768076 util-8620 DEBUG client_notify is running
Jul 07 20:49:49-768255 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:49-768451 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:49-768642 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:49-768955 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:52-625937 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:52-626327 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:52-626524 util-scheduler-8620 DEBUG Checking readiness of task: 3071 / 0x46620a0
Jul 07 20:49:52-626720 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:52-626918 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:52-627140 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:52-627331 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:52-627522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:52-627717 util-scheduler-8620 DEBUG Running task: 3071 / 0x46620a0
Jul 07 20:49:52-628140 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:52-628396 util-scheduler-8620 DEBUG Adding task: 3083 / 0x4662248
Jul 07 20:49:52-628676 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:52-628870 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:52-629061 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:52-629282 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:52-629474 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:52-629666 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:52-634888 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:52-635775 util-scheduler-8620 DEBUG Running task: 3083 / 0x4662248
Jul 07 20:49:52-636089 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:52-636404 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:52-636855 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:52-637173 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:52-637511 util-scheduler-8620 DEBUG Adding task: 3084 / 0x46620a0
Jul 07 20:49:52-637703 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:52-637911 util-scheduler-8620 DEBUG Adding task: 3085 / 0x46620a0
Jul 07 20:49:52-638189 util-scheduler-8620 DEBUG Checking readiness of task: 3085 / 0x46620a0
Jul 07 20:49:52-638385 util-scheduler-8620 DEBUG Checking readiness of task: 3084 / 0x46620a0
Jul 07 20:49:52-638580 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:52-638803 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:52-638996 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:52-639185 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:52-639378 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:52-639567 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:52-639757 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:52-639948 util-scheduler-8620 DEBUG Running task: 3084 / 0x46620a0
Jul 07 20:49:52-640134 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:52-640313 util-8620 DEBUG process_notify is running
Jul 07 20:49:52-640485 util-8620 DEBUG client_notify is running
Jul 07 20:49:52-640673 util-scheduler-8620 DEBUG Canceling task: 3081 / 0x59ee8a0
Jul 07 20:49:52-640902 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:52-641124 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:52-641394 cadet-p2p-8620 DEBUG Checking 0x5a37fd0 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:52-641630 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:52-641809 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:52-642002 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:52-642294 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:52-642491 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:52-642673 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:52-642861 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:52-643050 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:52-643230 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:52-643413 util-scheduler-8620 DEBUG Canceling task: 3072 / 0x59e8808
Jul 07 20:49:52-643632 util-scheduler-8620 DEBUG Adding task: 3086 / 0x59e8808
Jul 07 20:49:52-643884 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:52-644539 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:52-644722 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:52-644927 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:52-645105 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:52-645306 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:52-645507 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:52-645712 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:52-645897 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:52-646077 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:52-646268 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:52-647106 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:54-765183 util-scheduler-8620 DEBUG Checking readiness of task: 3085 / 0x46620a0
Jul 07 20:49:54-765599 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:54-765796 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:54-765990 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:54-766182 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:54-766374 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:54-766564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:54-766754 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:54-766946 util-scheduler-8620 DEBUG Running task: 3080 / 0x52cbfb8
Jul 07 20:49:54-767187 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:54-767435 cadet-tun-8620 DEBUG  kx started 150 s ago
Jul 07 20:49:54-767642 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:54-767842 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:54-768077 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:54-768326 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:54-768507 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:54-768729 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:54-769020 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:54-769353 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:54-770247 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:54-770494 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:54-770817 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:54-771019 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:54-771244 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:54-771428 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:54-771604 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:54-771810 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:54-772025 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:54-772254 util-scheduler-8620 DEBUG Adding task: 3087 / 0x59ee8a0
Jul 07 20:49:54-772435 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:54-772638 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:54-772815 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:54-772989 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:54-773254 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:54-773452 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:54-773629 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:54-773826 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:54-774072 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:54-774269 util-scheduler-8620 DEBUG Adding task: 3088 / 0x52cbfb8
Jul 07 20:49:54-774530 util-scheduler-8620 DEBUG Checking readiness of task: 3085 / 0x46620a0
Jul 07 20:49:54-774725 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:54-774914 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:54-775105 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:54-775293 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:54-775484 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:54-775672 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:54-775861 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:54-776050 util-scheduler-8620 DEBUG Running task: 3087 / 0x59ee8a0
Jul 07 20:49:54-776259 util-scheduler-8620 DEBUG Adding task: 3089 / 0x59ee8a0
Jul 07 20:49:54-776481 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:54-776686 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:54-776893 util-scheduler-8620 DEBUG Adding task: 3090 / 0x46620a0
Jul 07 20:49:54-777139 util-scheduler-8620 DEBUG Checking readiness of task: 3090 / 0x46620a0
Jul 07 20:49:54-777355 util-scheduler-8620 DEBUG Checking readiness of task: 3085 / 0x46620a0
Jul 07 20:49:54-777546 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:54-777735 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:54-777925 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:54-778116 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:54-778306 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:54-778496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:54-778683 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:54-778896 util-scheduler-8620 DEBUG Running task: 3090 / 0x46620a0
Jul 07 20:49:54-779082 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:54-779261 util-8620 DEBUG process_notify is running
Jul 07 20:49:54-779434 util-8620 DEBUG client_notify is running
Jul 07 20:49:54-779613 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:54-779810 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:54-780001 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:54-780328 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:55-815948 util-scheduler-8620 DEBUG Checking readiness of task: 3085 / 0x46620a0
Jul 07 20:49:55-816337 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:55-816535 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:55-816726 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:55-816919 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:55-817135 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:55-817354 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:55-817544 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:55-817741 util-scheduler-8620 DEBUG Running task: 3085 / 0x46620a0
Jul 07 20:49:55-818164 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:49:55-818419 util-scheduler-8620 DEBUG Adding task: 3091 / 0x4662248
Jul 07 20:49:55-818697 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:55-818892 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:55-819099 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:55-819290 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:55-819481 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:55-819673 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:55-819862 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:55-820924 util-scheduler-8620 DEBUG Running task: 3091 / 0x4662248
Jul 07 20:49:55-821122 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:49:55-821349 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:49:55-821585 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:49:55-821792 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:55-822055 util-scheduler-8620 DEBUG Adding task: 3092 / 0x46620a0
Jul 07 20:49:55-822245 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:49:55-822453 util-scheduler-8620 DEBUG Adding task: 3093 / 0x46620a0
Jul 07 20:49:55-822703 util-scheduler-8620 DEBUG Checking readiness of task: 3093 / 0x46620a0
Jul 07 20:49:55-823004 util-scheduler-8620 DEBUG Checking readiness of task: 3092 / 0x46620a0
Jul 07 20:49:55-823198 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:55-823504 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:55-823696 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:55-824733 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:55-824927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:55-825120 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:55-825335 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:55-825580 util-scheduler-8620 DEBUG Running task: 3092 / 0x46620a0
Jul 07 20:49:55-825799 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:55-825980 util-8620 DEBUG process_notify is running
Jul 07 20:49:55-826153 util-8620 DEBUG client_notify is running
Jul 07 20:49:55-826556 util-scheduler-8620 DEBUG Canceling task: 3089 / 0x59ee8a0
Jul 07 20:49:55-826900 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:49:55-827125 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:49:55-827367 cadet-p2p-8620 DEBUG Checking 0x5a3abf8 towards 2FDYFV0X (->V8XX)
Jul 07 20:49:55-827602 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:49:55-827781 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:49:55-828026 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:49:55-828314 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:49:55-828511 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:49:55-828705 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:49:55-829099 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:49:55-829517 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:49:55-830043 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:49:55-830436 util-scheduler-8620 DEBUG Canceling task: 3086 / 0x59e8808
Jul 07 20:49:55-830654 util-scheduler-8620 DEBUG Adding task: 3094 / 0x59e8808
Jul 07 20:49:55-831071 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:49:55-831244 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:49:55-831429 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:49:55-831630 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:55-831807 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:49:55-831983 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:49:55-832183 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:55-832389 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:49:55-832574 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:49:55-832754 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:55-832946 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:49:55-833746 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:49:59-778382 util-scheduler-8620 DEBUG Checking readiness of task: 3093 / 0x46620a0
Jul 07 20:49:59-778778 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:59-779628 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:59-779842 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:59-780038 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:59-780231 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:59-780421 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:59-780613 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:59-780806 util-scheduler-8620 DEBUG Running task: 3088 / 0x52cbfb8
Jul 07 20:49:59-781047 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:49:59-781354 cadet-tun-8620 DEBUG  kx started 155 s ago
Jul 07 20:49:59-781563 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:49:59-781764 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:49:59-781966 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:49:59-782207 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:49:59-782388 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:49:59-782609 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:49:59-782900 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:49:59-783097 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:49:59-783335 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:49:59-783544 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:49:59-783892 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:49:59-784094 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:49:59-784318 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:49:59-784502 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:49:59-784678 cadet-con-8620 DEBUG  sendable
Jul 07 20:49:59-784884 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:49:59-785098 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:49:59-785348 util-scheduler-8620 DEBUG Adding task: 3095 / 0x59ee8a0
Jul 07 20:49:59-785529 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:49:59-785732 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:49:59-785909 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:49:59-786084 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:49:59-786322 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:49:59-786519 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:49:59-786696 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:49:59-786895 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:49:59-787138 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:49:59-787336 util-scheduler-8620 DEBUG Adding task: 3096 / 0x52cbfb8
Jul 07 20:49:59-787596 util-scheduler-8620 DEBUG Checking readiness of task: 3093 / 0x46620a0
Jul 07 20:49:59-787790 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:59-787980 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:59-788170 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:59-788361 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:59-788550 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:59-788739 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:59-788928 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:59-789120 util-scheduler-8620 DEBUG Running task: 3095 / 0x59ee8a0
Jul 07 20:49:59-789351 util-scheduler-8620 DEBUG Adding task: 3097 / 0x59ee8a0
Jul 07 20:49:59-789578 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:49:59-789784 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:49:59-789993 util-scheduler-8620 DEBUG Adding task: 3098 / 0x46620a0
Jul 07 20:49:59-790238 util-scheduler-8620 DEBUG Checking readiness of task: 3098 / 0x46620a0
Jul 07 20:49:59-790432 util-scheduler-8620 DEBUG Checking readiness of task: 3093 / 0x46620a0
Jul 07 20:49:59-790623 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:49:59-790812 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:49:59-791003 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:49:59-791192 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:49:59-791381 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:49:59-791571 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:49:59-791759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:49:59-791952 util-scheduler-8620 DEBUG Running task: 3098 / 0x46620a0
Jul 07 20:49:59-792137 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:49:59-792315 util-8620 DEBUG process_notify is running
Jul 07 20:49:59-792488 util-8620 DEBUG client_notify is running
Jul 07 20:49:59-792666 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:49:59-792863 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:49:59-793054 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:49:59-793332 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:00-033370 util-scheduler-8620 DEBUG Checking readiness of task: 3093 / 0x46620a0
Jul 07 20:50:00-033649 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:00-033851 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:00-034045 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:00-034237 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:00-038416 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:00-038631 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:00-038827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:00-039023 util-scheduler-8620 DEBUG Running task: 3093 / 0x46620a0
Jul 07 20:50:00-039440 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:00-039692 util-scheduler-8620 DEBUG Adding task: 3099 / 0x4662248
Jul 07 20:50:00-039965 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:00-040511 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:00-041222 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:00-041913 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:00-042606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:00-043311 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:00-044023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:00-044723 util-scheduler-8620 DEBUG Running task: 3099 / 0x4662248
Jul 07 20:50:00-045325 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:00-045796 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:00-046385 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:00-046931 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:00-047148 util-scheduler-8620 DEBUG Adding task: 3100 / 0x46620a0
Jul 07 20:50:00-047341 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:00-047553 util-scheduler-8620 DEBUG Adding task: 3101 / 0x46620a0
Jul 07 20:50:00-047810 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:00-048007 util-scheduler-8620 DEBUG Checking readiness of task: 3100 / 0x46620a0
Jul 07 20:50:00-048204 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:00-048398 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:00-048592 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:00-048785 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:00-048980 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:00-049173 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:00-049389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:00-049584 util-scheduler-8620 DEBUG Running task: 3100 / 0x46620a0
Jul 07 20:50:00-049774 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:00-049955 util-8620 DEBUG process_notify is running
Jul 07 20:50:00-050130 util-8620 DEBUG client_notify is running
Jul 07 20:50:00-050321 util-scheduler-8620 DEBUG Canceling task: 3097 / 0x59ee8a0
Jul 07 20:50:00-050554 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:00-050777 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:00-051021 cadet-p2p-8620 DEBUG Checking 0x5a3d7b8 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:00-051260 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:00-051441 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:00-051661 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:00-051954 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:00-052154 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:00-052338 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:00-052529 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:00-052723 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:00-052905 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:00-053093 util-scheduler-8620 DEBUG Canceling task: 3094 / 0x59e8808
Jul 07 20:50:00-053335 util-scheduler-8620 DEBUG Adding task: 3102 / 0x59e8808
Jul 07 20:50:00-053588 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:00-053763 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:00-053949 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:00-054155 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:00-054334 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:00-054512 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:00-054715 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:00-054924 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:00-055111 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:00-055293 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:00-055488 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:00-056992 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:04-325288 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:04-325671 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:04-325868 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:04-326060 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:04-326253 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:04-326444 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:04-326636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:04-326826 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:04-327020 util-scheduler-8620 DEBUG Running task: 2984 / 0x4d60080
Jul 07 20:50:04-327207 cadet-tun-8620 DEBUG delayed destroying tunnel 0x4d60080
Jul 07 20:50:04-327442 cadet-tun-8620 DEBUG destroying tunnel P00P
Jul 07 20:50:04-327741 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:50:04-327963 util-scheduler-8620 DEBUG Adding task: 3103 / 0x4d5e5d8
Jul 07 20:50:04-328500 dht-api-8620 DEBUG Sending STOP for P00PHXNA to DHT via 0x46642c0
Jul 07 20:50:04-328762 util-8620 DEBUG Scheduling transmission (0x4665be0).
Jul 07 20:50:04-328963 util-scheduler-8620 DEBUG Adding task: 3104 / 0x4665be0
Jul 07 20:50:04-329267 util-scheduler-8620 DEBUG Checking readiness of task: 3104 / 0x4665be0
Jul 07 20:50:04-329468 util-scheduler-8620 DEBUG Checking readiness of task: 3103 / 0x4d5e5d8
Jul 07 20:50:04-329661 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:04-329870 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:04-330075 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:04-330267 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:04-330473 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:04-330677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:04-330880 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:04-331084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:04-331278 util-scheduler-8620 DEBUG Running task: 3103 / 0x4d5e5d8
Jul 07 20:50:04-331494 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:50:04-331674 util-8620 DEBUG process_notify is running
Jul 07 20:50:04-331848 util-8620 DEBUG client_notify is running
Jul 07 20:50:04-332077 util-8620 DEBUG Transmitting message of type 168 and size 32 to statistics service.
Jul 07 20:50:04-332345 util-8620 DEBUG Connection transmitted 32/32 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:50:04-332556 util-scheduler-8620 DEBUG Running task: 3104 / 0x4665be0
Jul 07 20:50:04-332741 util-8620 DEBUG transmit_ready running (0x4665be0).
Jul 07 20:50:04-332916 util-8620 DEBUG process_notify is running
Jul 07 20:50:04-333086 util-8620 DEBUG client_notify is running
Jul 07 20:50:04-333299 dht-api-8620 DEBUG Forwarded request of 80 bytes to DHT service
Jul 07 20:50:04-333493 util-8620 DEBUG Transmitting message of type 144 and size 80 to dht service.
Jul 07 20:50:04-333737 util-8620 DEBUG Connection transmitted 80/80 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)
Jul 07 20:50:04-787940 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:04-788298 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:04-788986 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:04-789185 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:04-789467 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:04-789683 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:04-789874 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:04-790065 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:04-790258 util-scheduler-8620 DEBUG Running task: 3096 / 0x52cbfb8
Jul 07 20:50:04-790497 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:04-790743 cadet-tun-8620 DEBUG  kx started 160 s ago
Jul 07 20:50:04-790952 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:04-791153 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:04-791354 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:04-791589 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:04-791769 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:04-792004 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:04-792294 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:04-792492 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:04-792728 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:04-792936 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:04-793273 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:04-793478 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:04-793702 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:04-793886 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:04-794082 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:04-794301 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:04-794518 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:04-794745 util-scheduler-8620 DEBUG Adding task: 3105 / 0x59ee8a0
Jul 07 20:50:04-794926 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:04-795130 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:04-795307 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:04-795483 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:04-795722 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:04-795918 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:04-796096 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:04-796295 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:04-796573 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:04-796771 util-scheduler-8620 DEBUG Adding task: 3106 / 0x52cbfb8
Jul 07 20:50:04-797028 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:04-797241 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:04-797432 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:04-797623 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:04-797812 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:04-798003 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:04-798192 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:04-798381 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:04-798570 util-scheduler-8620 DEBUG Running task: 3105 / 0x59ee8a0
Jul 07 20:50:04-798778 util-scheduler-8620 DEBUG Adding task: 3107 / 0x59ee8a0
Jul 07 20:50:04-799000 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:04-799237 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:04-799444 util-scheduler-8620 DEBUG Adding task: 3108 / 0x46620a0
Jul 07 20:50:04-799690 util-scheduler-8620 DEBUG Checking readiness of task: 3108 / 0x46620a0
Jul 07 20:50:04-799885 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:04-800076 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:04-800266 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:04-800456 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:04-800645 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:04-800835 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:04-801025 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:04-801232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:04-801425 util-scheduler-8620 DEBUG Running task: 3108 / 0x46620a0
Jul 07 20:50:04-801610 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:04-801788 util-8620 DEBUG process_notify is running
Jul 07 20:50:04-801960 util-8620 DEBUG client_notify is running
Jul 07 20:50:04-802142 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:04-802338 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:04-802530 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:04-802785 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:05-720685 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:05-721064 util-scheduler-8620 DEBUG Checking readiness of task: 3078 / 0x465ee60
Jul 07 20:50:05-721298 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:05-721494 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:05-721688 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:05-721881 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:05-722072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:05-722264 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:05-722461 util-scheduler-8620 DEBUG Running task: 3078 / 0x465ee60
Jul 07 20:50:05-722886 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:50:05-723143 util-scheduler-8620 DEBUG Adding task: 3109 / 0x465f008
Jul 07 20:50:05-723427 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:05-723622 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:05-723845 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:05-724037 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:05-724229 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:05-724419 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:05-724609 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:05-724801 util-scheduler-8620 DEBUG Running task: 3109 / 0x465f008
Jul 07 20:50:05-724995 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:50:05-725493 nse-api-8620 DEBUG Received information about peer `FKFC' from peerinfo database
Jul 07 20:50:05-725689 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:50:05-726022 util-scheduler-8620 DEBUG Adding task: 3110 / 0x465f008
Jul 07 20:50:05-726265 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:05-726460 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:05-726652 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:05-726843 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:05-727033 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:05-727223 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:05-727412 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:05-727603 util-scheduler-8620 DEBUG Running task: 3110 / 0x465f008
Jul 07 20:50:05-727791 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:50:05-728010 nse-api-8620 DEBUG Received information about peer `FKFC' from peerinfo database
Jul 07 20:50:05-728283 cadet-hll-8620 DEBUG  hello for FKFC (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:50:05-728543 cadet-p2p-8620 DEBUG set hello for FKFC
Jul 07 20:50:05-728722 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:50:05-728911 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:05-729124 util-scheduler-8620 DEBUG Adding task: 3111 / 0x465ee60
Jul 07 20:50:08-956383 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:08-956771 util-scheduler-8620 DEBUG Checking readiness of task: 3101 / 0x46620a0
Jul 07 20:50:08-956971 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:08-957166 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:08-957390 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:08-957583 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:08-957776 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:08-957967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:08-958164 util-scheduler-8620 DEBUG Running task: 3101 / 0x46620a0
Jul 07 20:50:08-958589 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:08-958847 util-scheduler-8620 DEBUG Adding task: 3112 / 0x4662248
Jul 07 20:50:08-959141 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:08-959336 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:08-959529 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:08-959720 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:08-959914 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:08-960105 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:08-960296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:08-960486 util-scheduler-8620 DEBUG Running task: 3112 / 0x4662248
Jul 07 20:50:08-960679 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:08-960910 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:08-961146 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:08-963348 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:08-963564 util-scheduler-8620 DEBUG Adding task: 3113 / 0x46620a0
Jul 07 20:50:08-963757 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:08-963965 util-scheduler-8620 DEBUG Adding task: 3114 / 0x46620a0
Jul 07 20:50:08-964218 util-scheduler-8620 DEBUG Checking readiness of task: 3114 / 0x46620a0
Jul 07 20:50:08-964413 util-scheduler-8620 DEBUG Checking readiness of task: 3113 / 0x46620a0
Jul 07 20:50:08-964607 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:08-964799 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:08-964991 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:08-965182 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:08-965401 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:08-965591 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:08-965782 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:08-965976 util-scheduler-8620 DEBUG Running task: 3113 / 0x46620a0
Jul 07 20:50:08-966164 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:08-966344 util-8620 DEBUG process_notify is running
Jul 07 20:50:08-966519 util-8620 DEBUG client_notify is running
Jul 07 20:50:08-966709 util-scheduler-8620 DEBUG Canceling task: 3107 / 0x59ee8a0
Jul 07 20:50:08-966937 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:08-967160 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:08-967402 cadet-p2p-8620 DEBUG Checking 0x5a41690 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:08-967637 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:08-967860 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:08-968053 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:08-968342 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:08-968539 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:08-968721 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:08-968910 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:08-969099 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:08-969770 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:08-969960 util-scheduler-8620 DEBUG Canceling task: 3102 / 0x59e8808
Jul 07 20:50:08-970179 util-scheduler-8620 DEBUG Adding task: 3115 / 0x59e8808
Jul 07 20:50:08-970431 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:08-970603 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:08-970789 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:08-970993 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:08-971170 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:08-971346 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:08-971547 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:08-971756 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:08-971941 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:08-972122 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:08-972315 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:08-973501 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:09-797765 util-scheduler-8620 DEBUG Checking readiness of task: 3114 / 0x46620a0
Jul 07 20:50:09-798154 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:09-798381 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:09-798576 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:09-798767 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:09-798959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:09-799148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:09-799338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:09-799531 util-scheduler-8620 DEBUG Running task: 3106 / 0x52cbfb8
Jul 07 20:50:09-799771 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:09-800017 cadet-tun-8620 DEBUG  kx started 165 s ago
Jul 07 20:50:09-800225 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:09-800426 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:09-800630 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:09-800870 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:09-801051 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:09-801300 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:09-801593 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:09-801790 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:09-802031 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:09-802240 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:09-802560 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:09-802763 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:09-802988 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:09-803171 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:09-803347 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:09-803554 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:09-803770 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:09-803994 util-scheduler-8620 DEBUG Adding task: 3116 / 0x59ee8a0
Jul 07 20:50:09-804175 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:09-804380 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:09-804557 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:09-804733 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:09-804972 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:09-805168 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:09-806144 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:09-806375 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:09-806625 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:09-806824 util-scheduler-8620 DEBUG Adding task: 3117 / 0x52cbfb8
Jul 07 20:50:09-807086 util-scheduler-8620 DEBUG Checking readiness of task: 3114 / 0x46620a0
Jul 07 20:50:09-807281 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:09-807472 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:09-807663 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:09-807854 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:09-808043 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:09-808233 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:09-808421 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:09-808612 util-scheduler-8620 DEBUG Running task: 3116 / 0x59ee8a0
Jul 07 20:50:09-808831 util-scheduler-8620 DEBUG Adding task: 3118 / 0x59ee8a0
Jul 07 20:50:09-809056 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:09-809286 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:09-809516 util-scheduler-8620 DEBUG Adding task: 3119 / 0x46620a0
Jul 07 20:50:09-809765 util-scheduler-8620 DEBUG Checking readiness of task: 3119 / 0x46620a0
Jul 07 20:50:09-809960 util-scheduler-8620 DEBUG Checking readiness of task: 3114 / 0x46620a0
Jul 07 20:50:09-810150 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:09-810341 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:09-810531 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:09-810720 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:09-810914 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:09-811102 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:09-811292 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:09-811483 util-scheduler-8620 DEBUG Running task: 3119 / 0x46620a0
Jul 07 20:50:09-811669 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:09-811848 util-8620 DEBUG process_notify is running
Jul 07 20:50:09-812021 util-8620 DEBUG client_notify is running
Jul 07 20:50:09-812202 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:09-812399 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:09-813008 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:09-813342 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:11-802960 util-scheduler-8620 DEBUG Checking readiness of task: 3114 / 0x46620a0
Jul 07 20:50:11-803368 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:11-803565 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:11-803763 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:11-803977 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:11-804169 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:11-804359 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:11-804550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:11-804745 util-scheduler-8620 DEBUG Running task: 3114 / 0x46620a0
Jul 07 20:50:11-805169 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:11-805456 util-scheduler-8620 DEBUG Adding task: 3120 / 0x4662248
Jul 07 20:50:11-805740 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:11-805935 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:11-806125 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:11-806353 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:11-806543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:11-806736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:11-806924 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:11-807116 util-scheduler-8620 DEBUG Running task: 3120 / 0x4662248
Jul 07 20:50:11-807307 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:11-807507 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:11-807740 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:11-807948 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:11-808156 util-scheduler-8620 DEBUG Adding task: 3121 / 0x46620a0
Jul 07 20:50:11-808343 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:11-808550 util-scheduler-8620 DEBUG Adding task: 3122 / 0x46620a0
Jul 07 20:50:11-808794 util-scheduler-8620 DEBUG Checking readiness of task: 3122 / 0x46620a0
Jul 07 20:50:11-809021 util-scheduler-8620 DEBUG Checking readiness of task: 3121 / 0x46620a0
Jul 07 20:50:11-809237 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:11-809429 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:11-809619 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:11-809808 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:11-809997 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:11-810186 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:11-810377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:11-810567 util-scheduler-8620 DEBUG Running task: 3121 / 0x46620a0
Jul 07 20:50:11-810753 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:11-810931 util-8620 DEBUG process_notify is running
Jul 07 20:50:11-811104 util-8620 DEBUG client_notify is running
Jul 07 20:50:11-811291 util-scheduler-8620 DEBUG Canceling task: 3118 / 0x59ee8a0
Jul 07 20:50:11-811518 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:11-811739 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:11-811980 cadet-p2p-8620 DEBUG Checking 0x5a44d58 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:11-812213 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:11-812392 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:11-812585 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:11-812869 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:11-813065 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:11-813264 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:11-813453 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:11-813642 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:11-813820 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:11-814003 util-scheduler-8620 DEBUG Canceling task: 3115 / 0x59e8808
Jul 07 20:50:11-814215 util-scheduler-8620 DEBUG Adding task: 3123 / 0x59e8808
Jul 07 20:50:11-814465 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:11-814637 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:11-814817 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:11-815018 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:11-815193 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:11-815368 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:11-815566 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:11-815771 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:11-815954 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:11-816132 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:11-816323 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:11-816572 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:14-809984 util-scheduler-8620 DEBUG Checking readiness of task: 3122 / 0x46620a0
Jul 07 20:50:14-810378 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:14-811015 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:14-811216 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:14-811478 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:14-811690 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:14-811881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:14-812071 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:14-812264 util-scheduler-8620 DEBUG Running task: 3117 / 0x52cbfb8
Jul 07 20:50:14-812502 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:14-812783 cadet-tun-8620 DEBUG  kx started 170 s ago
Jul 07 20:50:14-812990 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:14-813212 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:14-813419 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:14-813657 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:14-813838 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:14-814059 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:14-814349 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:14-814564 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:14-814801 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:14-815009 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:14-815331 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:14-815532 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:14-815756 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:14-815939 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:14-816115 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:14-816323 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:14-816537 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:14-816763 util-scheduler-8620 DEBUG Adding task: 3124 / 0x59ee8a0
Jul 07 20:50:14-816943 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:14-817148 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:14-817346 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:14-817521 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:14-817759 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:14-817957 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:14-818134 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:14-818332 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:14-818576 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:14-818773 util-scheduler-8620 DEBUG Adding task: 3125 / 0x52cbfb8
Jul 07 20:50:14-819033 util-scheduler-8620 DEBUG Checking readiness of task: 3122 / 0x46620a0
Jul 07 20:50:14-819226 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:14-819416 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:14-819605 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:14-819795 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:14-819984 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:14-820174 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:14-820362 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:14-820552 util-scheduler-8620 DEBUG Running task: 3124 / 0x59ee8a0
Jul 07 20:50:14-820759 util-scheduler-8620 DEBUG Adding task: 3126 / 0x59ee8a0
Jul 07 20:50:14-820982 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:14-821186 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:14-821415 util-scheduler-8620 DEBUG Adding task: 3127 / 0x46620a0
Jul 07 20:50:14-821658 util-scheduler-8620 DEBUG Checking readiness of task: 3127 / 0x46620a0
Jul 07 20:50:14-821853 util-scheduler-8620 DEBUG Checking readiness of task: 3122 / 0x46620a0
Jul 07 20:50:14-822043 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:14-822232 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:14-822422 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:14-822611 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:14-822800 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:14-823005 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:14-823195 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:14-823386 util-scheduler-8620 DEBUG Running task: 3127 / 0x46620a0
Jul 07 20:50:14-823571 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:14-823749 util-8620 DEBUG process_notify is running
Jul 07 20:50:14-823923 util-8620 DEBUG client_notify is running
Jul 07 20:50:14-824101 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:14-824297 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:14-824492 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:14-824750 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:17-081801 util-scheduler-8620 DEBUG Checking readiness of task: 3122 / 0x46620a0
Jul 07 20:50:17-082204 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:17-082402 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:17-082601 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:17-082795 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:17-082988 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:17-083182 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:17-083373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:17-083572 util-scheduler-8620 DEBUG Running task: 3122 / 0x46620a0
Jul 07 20:50:17-083997 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:17-084257 util-scheduler-8620 DEBUG Adding task: 3128 / 0x4662248
Jul 07 20:50:17-084539 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:17-084736 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:17-084931 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:17-085122 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:17-085349 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:17-085542 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:17-085734 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:17-085925 util-scheduler-8620 DEBUG Running task: 3128 / 0x4662248
Jul 07 20:50:17-086121 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:17-086323 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:17-086561 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:17-086772 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:17-086981 util-scheduler-8620 DEBUG Adding task: 3129 / 0x46620a0
Jul 07 20:50:17-087172 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:17-087380 util-scheduler-8620 DEBUG Adding task: 3130 / 0x46620a0
Jul 07 20:50:17-087631 util-scheduler-8620 DEBUG Checking readiness of task: 3130 / 0x46620a0
Jul 07 20:50:17-087827 util-scheduler-8620 DEBUG Checking readiness of task: 3129 / 0x46620a0
Jul 07 20:50:17-088022 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:17-088216 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:17-088409 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:17-088602 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:17-088794 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:17-088989 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:17-089256 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:17-089455 util-scheduler-8620 DEBUG Running task: 3129 / 0x46620a0
Jul 07 20:50:17-089643 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:17-089826 util-8620 DEBUG process_notify is running
Jul 07 20:50:17-090000 util-8620 DEBUG client_notify is running
Jul 07 20:50:17-090193 util-scheduler-8620 DEBUG Canceling task: 3126 / 0x59ee8a0
Jul 07 20:50:17-090421 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:17-090646 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:17-090889 cadet-p2p-8620 DEBUG Checking 0x5a47958 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:17-091126 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:17-091308 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:17-091500 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:17-091788 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:17-091986 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:17-092170 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:17-092360 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:17-092555 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:17-092738 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:17-092938 util-scheduler-8620 DEBUG Canceling task: 3123 / 0x59e8808
Jul 07 20:50:17-093154 util-scheduler-8620 DEBUG Adding task: 3131 / 0x59e8808
Jul 07 20:50:17-093435 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:17-093609 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:17-093795 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:17-093999 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:17-094177 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:17-094355 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:17-094557 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:17-094765 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:17-094952 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:17-095135 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:17-095330 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:17-096154 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:19-821666 util-scheduler-8620 DEBUG Checking readiness of task: 3130 / 0x46620a0
Jul 07 20:50:19-822063 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:19-822699 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:19-822931 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:19-823167 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:19-823365 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:19-823555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:19-823747 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:19-823939 util-scheduler-8620 DEBUG Running task: 3125 / 0x52cbfb8
Jul 07 20:50:19-824179 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:19-824427 cadet-tun-8620 DEBUG  kx started 175 s ago
Jul 07 20:50:19-824633 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:19-824834 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:19-825035 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:19-825291 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:19-825475 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:19-825695 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:19-825990 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:19-826279 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:19-826589 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:19-826798 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:19-827119 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:19-827321 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:19-827545 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:19-827729 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:19-827905 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:19-828111 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:19-828327 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:19-828555 util-scheduler-8620 DEBUG Adding task: 3132 / 0x59ee8a0
Jul 07 20:50:19-828735 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:19-828939 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:19-829116 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:19-829313 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:19-829552 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:19-829747 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:19-829924 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:19-830123 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:19-830367 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:19-830565 util-scheduler-8620 DEBUG Adding task: 3133 / 0x52cbfb8
Jul 07 20:50:19-830825 util-scheduler-8620 DEBUG Checking readiness of task: 3130 / 0x46620a0
Jul 07 20:50:19-831019 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:19-831209 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:19-831399 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:19-831589 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:19-831779 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:19-831968 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:19-832156 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:19-832348 util-scheduler-8620 DEBUG Running task: 3132 / 0x59ee8a0
Jul 07 20:50:19-832558 util-scheduler-8620 DEBUG Adding task: 3134 / 0x59ee8a0
Jul 07 20:50:19-832800 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:19-833006 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:19-833236 util-scheduler-8620 DEBUG Adding task: 3135 / 0x46620a0
Jul 07 20:50:19-833484 util-scheduler-8620 DEBUG Checking readiness of task: 3135 / 0x46620a0
Jul 07 20:50:19-833679 util-scheduler-8620 DEBUG Checking readiness of task: 3130 / 0x46620a0
Jul 07 20:50:19-833869 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:19-834058 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:19-834248 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:19-834437 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:19-834627 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:19-834819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:19-835009 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:19-835201 util-scheduler-8620 DEBUG Running task: 3135 / 0x46620a0
Jul 07 20:50:19-835387 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:19-835567 util-8620 DEBUG process_notify is running
Jul 07 20:50:19-835740 util-8620 DEBUG client_notify is running
Jul 07 20:50:19-835919 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:19-836116 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:19-836325 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:19-836579 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:23-348669 util-scheduler-8620 DEBUG Checking readiness of task: 3130 / 0x46620a0
Jul 07 20:50:23-349069 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:23-349287 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:23-349483 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:23-349694 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:23-349886 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:23-350099 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:23-350289 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:23-350485 util-scheduler-8620 DEBUG Running task: 3130 / 0x46620a0
Jul 07 20:50:23-350911 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:23-351169 util-scheduler-8620 DEBUG Adding task: 3136 / 0x4662248
Jul 07 20:50:23-351447 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:23-351641 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:23-351830 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:23-352020 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:23-352209 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:23-352397 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:23-352585 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:23-352773 util-scheduler-8620 DEBUG Running task: 3136 / 0x4662248
Jul 07 20:50:23-352964 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:23-353176 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:23-353432 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:23-353638 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:23-353844 util-scheduler-8620 DEBUG Adding task: 3137 / 0x46620a0
Jul 07 20:50:23-354032 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:23-354237 util-scheduler-8620 DEBUG Adding task: 3138 / 0x46620a0
Jul 07 20:50:23-354485 util-scheduler-8620 DEBUG Checking readiness of task: 3138 / 0x46620a0
Jul 07 20:50:23-354682 util-scheduler-8620 DEBUG Checking readiness of task: 3137 / 0x46620a0
Jul 07 20:50:23-354876 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:23-355068 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:23-355260 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:23-355450 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:23-355643 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:23-355832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:23-356028 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:23-356223 util-scheduler-8620 DEBUG Running task: 3137 / 0x46620a0
Jul 07 20:50:23-356411 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:23-356592 util-8620 DEBUG process_notify is running
Jul 07 20:50:23-356767 util-8620 DEBUG client_notify is running
Jul 07 20:50:23-356958 util-scheduler-8620 DEBUG Canceling task: 3134 / 0x59ee8a0
Jul 07 20:50:23-357216 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:23-357440 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:23-357713 cadet-p2p-8620 DEBUG Checking 0x5a4a5f0 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:23-357951 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:23-358128 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:23-358319 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:23-358605 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:23-358800 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:23-358980 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:23-359168 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:23-359355 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:23-359532 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:23-359715 util-scheduler-8620 DEBUG Canceling task: 3131 / 0x59e8808
Jul 07 20:50:23-359929 util-scheduler-8620 DEBUG Adding task: 3139 / 0x59e8808
Jul 07 20:50:23-360179 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:23-360350 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:23-360529 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:23-360728 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:23-360903 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:23-361077 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:23-361295 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:23-361500 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:23-361682 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:23-361861 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:23-362051 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:23-362814 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:24-832204 util-scheduler-8620 DEBUG Checking readiness of task: 3138 / 0x46620a0
Jul 07 20:50:24-832593 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:24-833400 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:24-833610 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:24-833804 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:24-833996 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:24-834187 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:24-834376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:24-834569 util-scheduler-8620 DEBUG Running task: 3133 / 0x52cbfb8
Jul 07 20:50:24-834805 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:24-835063 cadet-tun-8620 DEBUG  kx started 3 m ago
Jul 07 20:50:24-835269 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:24-835469 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:24-835672 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:24-835909 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:24-836089 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:24-836309 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:24-836599 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:24-836795 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:24-837032 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:24-837261 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:24-837582 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:24-837783 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:24-838007 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:24-838192 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:24-838367 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:24-838599 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:24-838814 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:24-839039 util-scheduler-8620 DEBUG Adding task: 3140 / 0x59ee8a0
Jul 07 20:50:24-839219 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:24-839421 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:24-839599 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:24-839773 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:24-840010 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:24-840206 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:24-840382 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:24-840579 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:24-840822 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:24-841019 util-scheduler-8620 DEBUG Adding task: 3141 / 0x52cbfb8
Jul 07 20:50:24-841313 util-scheduler-8620 DEBUG Checking readiness of task: 3138 / 0x46620a0
Jul 07 20:50:24-841507 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:24-841697 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:24-841886 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:24-842075 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:24-842263 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:24-842451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:24-842638 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:24-842831 util-scheduler-8620 DEBUG Running task: 3140 / 0x59ee8a0
Jul 07 20:50:24-843044 util-scheduler-8620 DEBUG Adding task: 3142 / 0x59ee8a0
Jul 07 20:50:24-843277 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:24-843484 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:24-843698 util-scheduler-8620 DEBUG Adding task: 3143 / 0x46620a0
Jul 07 20:50:24-843961 util-scheduler-8620 DEBUG Checking readiness of task: 3143 / 0x46620a0
Jul 07 20:50:24-844159 util-scheduler-8620 DEBUG Checking readiness of task: 3138 / 0x46620a0
Jul 07 20:50:24-844354 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:24-844545 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:24-844738 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:24-844942 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:24-845131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:24-845345 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:24-845535 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:24-845726 util-scheduler-8620 DEBUG Running task: 3143 / 0x46620a0
Jul 07 20:50:24-845911 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:24-846089 util-8620 DEBUG process_notify is running
Jul 07 20:50:24-846263 util-8620 DEBUG client_notify is running
Jul 07 20:50:24-846441 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:24-846639 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:24-846830 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:24-847130 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:26-484446 util-scheduler-8620 DEBUG Checking readiness of task: 3138 / 0x46620a0
Jul 07 20:50:26-484831 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:26-485034 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:26-485249 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:26-485472 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:26-485665 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:26-485858 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:26-486049 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:26-486247 util-scheduler-8620 DEBUG Running task: 3138 / 0x46620a0
Jul 07 20:50:26-486671 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:26-486926 util-scheduler-8620 DEBUG Adding task: 3144 / 0x4662248
Jul 07 20:50:26-487204 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:26-487400 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:26-487591 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:26-487781 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:26-487971 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:26-488159 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:26-488348 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:26-488538 util-scheduler-8620 DEBUG Running task: 3144 / 0x4662248
Jul 07 20:50:26-488728 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:26-488928 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:26-489160 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:26-489497 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:26-489709 util-scheduler-8620 DEBUG Adding task: 3145 / 0x46620a0
Jul 07 20:50:26-489900 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:26-490108 util-scheduler-8620 DEBUG Adding task: 3146 / 0x46620a0
Jul 07 20:50:26-490355 util-scheduler-8620 DEBUG Checking readiness of task: 3146 / 0x46620a0
Jul 07 20:50:26-490550 util-scheduler-8620 DEBUG Checking readiness of task: 3145 / 0x46620a0
Jul 07 20:50:26-490743 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:26-490935 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:26-491125 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:26-491318 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:26-491508 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:26-491699 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:26-491888 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:26-492083 util-scheduler-8620 DEBUG Running task: 3145 / 0x46620a0
Jul 07 20:50:26-492270 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:26-492457 util-8620 DEBUG process_notify is running
Jul 07 20:50:26-492634 util-8620 DEBUG client_notify is running
Jul 07 20:50:26-492828 util-scheduler-8620 DEBUG Canceling task: 3142 / 0x59ee8a0
Jul 07 20:50:26-493059 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:26-493303 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:26-493542 cadet-p2p-8620 DEBUG Checking 0x5a4d2c0 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:26-493781 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:26-493961 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:26-494158 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:26-494450 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:26-494649 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:26-494828 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:26-495015 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:26-495204 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:26-495406 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:26-495595 util-scheduler-8620 DEBUG Canceling task: 3139 / 0x59e8808
Jul 07 20:50:26-495813 util-scheduler-8620 DEBUG Adding task: 3147 / 0x59e8808
Jul 07 20:50:26-496066 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:26-496237 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:26-496421 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:26-496626 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:26-496802 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:26-496976 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:26-497175 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:26-497405 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:26-497589 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:26-497769 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:26-497959 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:26-498694 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:29-844532 util-scheduler-8620 DEBUG Checking readiness of task: 3146 / 0x46620a0
Jul 07 20:50:29-844924 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:29-845515 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:29-845749 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:29-845984 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:29-846180 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:29-846371 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:29-846561 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:29-846754 util-scheduler-8620 DEBUG Running task: 3141 / 0x52cbfb8
Jul 07 20:50:29-846993 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:29-847239 cadet-tun-8620 DEBUG  kx started 185 s ago
Jul 07 20:50:29-847447 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:29-847648 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:29-847851 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:29-848086 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:29-848267 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:29-848487 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:29-848778 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:29-848978 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:29-849238 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:29-849452 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:29-849772 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:29-849973 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:29-850197 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:29-850381 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:29-850570 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:29-850776 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:29-850993 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:29-851217 util-scheduler-8620 DEBUG Adding task: 3148 / 0x59ee8a0
Jul 07 20:50:29-851400 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:29-851603 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:29-851781 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:29-851956 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:29-852195 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:29-852417 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:29-852595 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:29-852794 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:29-853037 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:29-853254 util-scheduler-8620 DEBUG Adding task: 3149 / 0x52cbfb8
Jul 07 20:50:29-853516 util-scheduler-8620 DEBUG Checking readiness of task: 3146 / 0x46620a0
Jul 07 20:50:29-853708 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:29-853898 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:29-854087 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:29-854278 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:29-854466 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:29-854656 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:29-854844 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:29-855034 util-scheduler-8620 DEBUG Running task: 3148 / 0x59ee8a0
Jul 07 20:50:29-855242 util-scheduler-8620 DEBUG Adding task: 3150 / 0x59ee8a0
Jul 07 20:50:29-855464 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:29-855668 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:29-855876 util-scheduler-8620 DEBUG Adding task: 3151 / 0x46620a0
Jul 07 20:50:29-856119 util-scheduler-8620 DEBUG Checking readiness of task: 3151 / 0x46620a0
Jul 07 20:50:29-856314 util-scheduler-8620 DEBUG Checking readiness of task: 3146 / 0x46620a0
Jul 07 20:50:29-856504 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:29-856715 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:29-856908 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:29-857098 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:29-857312 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:29-857502 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:29-857691 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:29-857882 util-scheduler-8620 DEBUG Running task: 3151 / 0x46620a0
Jul 07 20:50:29-858067 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:29-858245 util-8620 DEBUG process_notify is running
Jul 07 20:50:29-858437 util-8620 DEBUG client_notify is running
Jul 07 20:50:29-858624 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:29-858822 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:29-859015 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:29-859266 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:30-986978 util-scheduler-8620 DEBUG Checking readiness of task: 3146 / 0x46620a0
Jul 07 20:50:30-987358 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:30-987555 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:30-987746 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:30-987938 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:30-988129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:30-988319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:30-988508 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:30-988703 util-scheduler-8620 DEBUG Running task: 3146 / 0x46620a0
Jul 07 20:50:30-989126 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:30-989406 util-scheduler-8620 DEBUG Adding task: 3152 / 0x4662248
Jul 07 20:50:30-989716 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:30-989911 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:30-990101 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:30-990291 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:30-990481 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:30-990669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:30-990857 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:30-991047 util-scheduler-8620 DEBUG Running task: 3152 / 0x4662248
Jul 07 20:50:30-991237 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:30-991435 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:30-991666 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:30-991872 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:30-992080 util-scheduler-8620 DEBUG Adding task: 3153 / 0x46620a0
Jul 07 20:50:30-992269 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:30-992482 util-scheduler-8620 DEBUG Adding task: 3154 / 0x46620a0
Jul 07 20:50:30-992736 util-scheduler-8620 DEBUG Checking readiness of task: 3154 / 0x46620a0
Jul 07 20:50:30-992933 util-scheduler-8620 DEBUG Checking readiness of task: 3153 / 0x46620a0
Jul 07 20:50:30-993131 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:30-995874 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:30-996100 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:30-996291 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:30-996483 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:30-996672 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:30-996863 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:30-997057 util-scheduler-8620 DEBUG Running task: 3153 / 0x46620a0
Jul 07 20:50:30-997268 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:30-997447 util-8620 DEBUG process_notify is running
Jul 07 20:50:30-997619 util-8620 DEBUG client_notify is running
Jul 07 20:50:30-997809 util-scheduler-8620 DEBUG Canceling task: 3150 / 0x59ee8a0
Jul 07 20:50:30-998049 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:30-998271 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:30-998511 cadet-p2p-8620 DEBUG Checking 0x5a4fea0 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:30-998745 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:30-998922 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:30-999112 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:30-999399 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:30-999597 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:30-999777 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:30-999963 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:31-000151 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:31-000333 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:31-000518 util-scheduler-8620 DEBUG Canceling task: 3147 / 0x59e8808
Jul 07 20:50:31-000735 util-scheduler-8620 DEBUG Adding task: 3155 / 0x59e8808
Jul 07 20:50:31-000989 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:31-001161 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:31-001363 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:31-001565 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:31-001742 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:31-001917 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:31-002141 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:31-002347 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:31-002545 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:31-002726 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:31-002919 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:31-003702 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:34-857288 util-scheduler-8620 DEBUG Checking readiness of task: 3154 / 0x46620a0
Jul 07 20:50:34-857703 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-857901 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-858095 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-858288 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-858480 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-858672 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-858862 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-859058 util-scheduler-8620 DEBUG Running task: 3149 / 0x52cbfb8
Jul 07 20:50:34-859298 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:34-859556 cadet-tun-8620 DEBUG  kx started 190 s ago
Jul 07 20:50:34-860561 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:34-860802 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:34-861006 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:34-861262 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:34-861444 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:34-861738 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:34-862031 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:34-862231 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:34-862468 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:34-862676 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:34-862995 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:34-863197 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:34-863420 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:34-863603 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:34-863778 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:34-863984 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:34-864199 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:34-864425 util-scheduler-8620 DEBUG Adding task: 3156 / 0x59ee8a0
Jul 07 20:50:34-864603 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:34-864808 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:34-864983 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:34-865158 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:34-865416 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:34-865613 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:34-865791 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:34-865989 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:34-866241 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:34-866445 util-scheduler-8620 DEBUG Adding task: 3157 / 0x52cbfb8
Jul 07 20:50:34-866712 util-scheduler-8620 DEBUG Checking readiness of task: 3154 / 0x46620a0
Jul 07 20:50:34-866907 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-867099 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-867322 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-867515 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-867712 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-867903 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-868100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-868292 util-scheduler-8620 DEBUG Running task: 3156 / 0x59ee8a0
Jul 07 20:50:34-868505 util-scheduler-8620 DEBUG Adding task: 3158 / 0x59ee8a0
Jul 07 20:50:34-868736 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:34-868942 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:34-869153 util-scheduler-8620 DEBUG Adding task: 3159 / 0x46620a0
Jul 07 20:50:34-869432 util-scheduler-8620 DEBUG Checking readiness of task: 3159 / 0x46620a0
Jul 07 20:50:34-869627 util-scheduler-8620 DEBUG Checking readiness of task: 3154 / 0x46620a0
Jul 07 20:50:34-869818 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-870007 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-870197 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-870388 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-870578 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-870766 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-870955 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-871146 util-scheduler-8620 DEBUG Running task: 3159 / 0x46620a0
Jul 07 20:50:34-871331 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:34-871508 util-8620 DEBUG process_notify is running
Jul 07 20:50:34-871682 util-8620 DEBUG client_notify is running
Jul 07 20:50:34-871860 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:34-872056 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:34-872247 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:34-872548 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:34-892934 util-scheduler-8620 DEBUG Checking readiness of task: 3154 / 0x46620a0
Jul 07 20:50:34-893221 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-893419 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-893613 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-893887 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-894086 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-894279 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-894902 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-895105 util-scheduler-8620 DEBUG Running task: 3154 / 0x46620a0
Jul 07 20:50:34-895520 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:34-895765 util-scheduler-8620 DEBUG Adding task: 3160 / 0x4662248
Jul 07 20:50:34-896028 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-896223 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-896413 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-896602 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-896793 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-896981 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-897170 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-897404 util-scheduler-8620 DEBUG Running task: 3160 / 0x4662248
Jul 07 20:50:34-897597 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:34-897795 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:34-898020 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:34-898223 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:34-898425 util-scheduler-8620 DEBUG Adding task: 3161 / 0x46620a0
Jul 07 20:50:34-898610 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:34-898814 util-scheduler-8620 DEBUG Adding task: 3162 / 0x46620a0
Jul 07 20:50:34-899056 util-scheduler-8620 DEBUG Checking readiness of task: 3162 / 0x46620a0
Jul 07 20:50:34-899247 util-scheduler-8620 DEBUG Checking readiness of task: 3161 / 0x46620a0
Jul 07 20:50:34-899439 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:34-899640 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:34-899829 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:34-900020 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:34-900209 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:34-900400 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:34-900587 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:34-900778 util-scheduler-8620 DEBUG Running task: 3161 / 0x46620a0
Jul 07 20:50:34-900961 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:34-901135 util-8620 DEBUG process_notify is running
Jul 07 20:50:34-901327 util-8620 DEBUG client_notify is running
Jul 07 20:50:34-901512 util-scheduler-8620 DEBUG Canceling task: 3158 / 0x59ee8a0
Jul 07 20:50:34-901736 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:34-901954 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:34-902190 cadet-p2p-8620 DEBUG Checking 0x5a52ab8 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:34-902423 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:34-902601 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:34-902788 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:34-903071 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:34-903265 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:34-903443 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:34-903629 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:34-903816 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:34-903994 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:34-904176 util-scheduler-8620 DEBUG Canceling task: 3155 / 0x59e8808
Jul 07 20:50:34-904386 util-scheduler-8620 DEBUG Adding task: 3163 / 0x59e8808
Jul 07 20:50:34-904631 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:34-904801 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:34-904980 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:34-905183 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:34-905381 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:34-905555 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:34-905755 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:34-905960 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:34-906147 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:34-906329 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:34-906520 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:34-907223 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:39-871574 util-scheduler-8620 DEBUG Checking readiness of task: 3162 / 0x46620a0
Jul 07 20:50:39-872009 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:39-872634 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:39-872835 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:39-873101 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:39-873344 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:39-873536 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:39-873726 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:39-873919 util-scheduler-8620 DEBUG Running task: 3157 / 0x52cbfb8
Jul 07 20:50:39-874158 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:39-874407 cadet-tun-8620 DEBUG  kx started 195 s ago
Jul 07 20:50:39-874634 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:39-874837 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:39-875057 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:39-875293 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:39-875474 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:39-875695 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:39-875990 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:39-876187 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:39-876425 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:39-876633 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:39-876952 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:39-877154 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:39-877422 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:39-877641 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:39-877818 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:39-878025 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:39-878240 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:39-878466 util-scheduler-8620 DEBUG Adding task: 3164 / 0x59ee8a0
Jul 07 20:50:39-878646 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:39-878850 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:39-879026 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:39-879202 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:39-879440 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:39-879638 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:39-879818 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:39-880016 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:39-880261 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:39-880459 util-scheduler-8620 DEBUG Adding task: 3165 / 0x52cbfb8
Jul 07 20:50:39-880718 util-scheduler-8620 DEBUG Checking readiness of task: 3162 / 0x46620a0
Jul 07 20:50:39-880912 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:39-881102 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:39-881313 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:39-881504 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:39-881694 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:39-881883 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:39-882074 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:39-882264 util-scheduler-8620 DEBUG Running task: 3164 / 0x59ee8a0
Jul 07 20:50:39-882471 util-scheduler-8620 DEBUG Adding task: 3166 / 0x59ee8a0
Jul 07 20:50:39-882696 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:39-882926 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:39-883136 util-scheduler-8620 DEBUG Adding task: 3167 / 0x46620a0
Jul 07 20:50:39-883381 util-scheduler-8620 DEBUG Checking readiness of task: 3167 / 0x46620a0
Jul 07 20:50:39-883575 util-scheduler-8620 DEBUG Checking readiness of task: 3162 / 0x46620a0
Jul 07 20:50:39-883766 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:39-883956 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:39-884146 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:39-884336 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:39-884525 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:39-884715 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:39-884902 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:39-885094 util-scheduler-8620 DEBUG Running task: 3167 / 0x46620a0
Jul 07 20:50:39-885300 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:39-885479 util-8620 DEBUG process_notify is running
Jul 07 20:50:39-885652 util-8620 DEBUG client_notify is running
Jul 07 20:50:39-885831 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:39-886026 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:39-886231 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:39-886489 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:40-735727 util-scheduler-8620 DEBUG Checking readiness of task: 3162 / 0x46620a0
Jul 07 20:50:40-736120 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:40-736318 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:40-736513 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:40-736706 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:40-736898 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:40-737089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:40-737304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:40-737501 util-scheduler-8620 DEBUG Running task: 3162 / 0x46620a0
Jul 07 20:50:40-737923 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:40-738183 util-scheduler-8620 DEBUG Adding task: 3168 / 0x4662248
Jul 07 20:50:40-738466 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:40-738660 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:40-738853 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:40-739043 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:40-739234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:40-739424 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:40-739614 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:40-739805 util-scheduler-8620 DEBUG Running task: 3168 / 0x4662248
Jul 07 20:50:40-739998 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:40-740197 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:40-740432 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:40-740639 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:40-740848 util-scheduler-8620 DEBUG Adding task: 3169 / 0x46620a0
Jul 07 20:50:40-741037 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:40-741303 util-scheduler-8620 DEBUG Adding task: 3170 / 0x46620a0
Jul 07 20:50:40-741552 util-scheduler-8620 DEBUG Checking readiness of task: 3170 / 0x46620a0
Jul 07 20:50:40-741746 util-scheduler-8620 DEBUG Checking readiness of task: 3169 / 0x46620a0
Jul 07 20:50:40-741940 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:40-742130 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:40-742321 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:40-742513 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:40-742703 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:40-742894 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:40-743084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:40-743276 util-scheduler-8620 DEBUG Running task: 3169 / 0x46620a0
Jul 07 20:50:40-743463 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:40-743642 util-8620 DEBUG process_notify is running
Jul 07 20:50:40-743816 util-8620 DEBUG client_notify is running
Jul 07 20:50:40-744004 util-scheduler-8620 DEBUG Canceling task: 3166 / 0x59ee8a0
Jul 07 20:50:40-744230 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:40-744453 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:40-744695 cadet-p2p-8620 DEBUG Checking 0x5a55698 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:40-744930 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:40-745108 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:40-745324 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:40-745609 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:40-745805 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:40-745986 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:40-746173 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:40-746361 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:40-746540 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:40-746724 util-scheduler-8620 DEBUG Canceling task: 3163 / 0x59e8808
Jul 07 20:50:40-746936 util-scheduler-8620 DEBUG Adding task: 3171 / 0x59e8808
Jul 07 20:50:40-747187 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:40-747359 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:40-747541 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:40-747742 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:40-747917 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:40-748094 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:40-748294 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:40-748498 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:40-748683 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:40-748862 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:40-749053 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:40-749320 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:44-881379 util-scheduler-8620 DEBUG Checking readiness of task: 3170 / 0x46620a0
Jul 07 20:50:44-881775 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:44-882669 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:44-882883 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:44-883076 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:44-883268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:44-883458 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:44-883648 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:44-883865 util-scheduler-8620 DEBUG Running task: 3165 / 0x52cbfb8
Jul 07 20:50:44-884105 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:44-884349 cadet-tun-8620 DEBUG  kx started 200 s ago
Jul 07 20:50:44-884556 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:44-884756 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:44-884957 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:44-885213 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:44-885395 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:44-885616 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:44-885906 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:44-886102 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:44-886338 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:44-886548 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:44-886865 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:44-887067 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:44-887290 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:44-887473 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:44-887648 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:44-887854 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:44-888068 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:44-888294 util-scheduler-8620 DEBUG Adding task: 3172 / 0x59ee8a0
Jul 07 20:50:44-888474 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:44-888677 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:44-888854 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:44-889028 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:44-889305 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:44-889515 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:44-889692 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:44-889890 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:44-890132 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:44-890329 util-scheduler-8620 DEBUG Adding task: 3173 / 0x52cbfb8
Jul 07 20:50:44-890589 util-scheduler-8620 DEBUG Checking readiness of task: 3170 / 0x46620a0
Jul 07 20:50:44-890781 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:44-890970 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:44-891159 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:44-891349 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:44-891537 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:44-891726 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:44-891915 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:44-892104 util-scheduler-8620 DEBUG Running task: 3172 / 0x59ee8a0
Jul 07 20:50:44-892314 util-scheduler-8620 DEBUG Adding task: 3174 / 0x59ee8a0
Jul 07 20:50:44-892542 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:44-892748 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:44-892958 util-scheduler-8620 DEBUG Adding task: 3175 / 0x46620a0
Jul 07 20:50:44-893230 util-scheduler-8620 DEBUG Checking readiness of task: 3175 / 0x46620a0
Jul 07 20:50:44-893426 util-scheduler-8620 DEBUG Checking readiness of task: 3170 / 0x46620a0
Jul 07 20:50:44-893618 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:44-893815 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:44-894010 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:44-894225 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:44-894422 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:44-894614 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:44-894806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:44-895001 util-scheduler-8620 DEBUG Running task: 3175 / 0x46620a0
Jul 07 20:50:44-895187 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:44-895367 util-8620 DEBUG process_notify is running
Jul 07 20:50:44-895539 util-8620 DEBUG client_notify is running
Jul 07 20:50:44-895718 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:44-895915 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:44-896107 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:44-896410 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:48-126054 util-scheduler-8620 DEBUG Checking readiness of task: 3170 / 0x46620a0
Jul 07 20:50:48-126435 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:48-126632 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:48-126824 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:48-127016 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:48-127208 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:48-127399 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:48-127589 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:48-127784 util-scheduler-8620 DEBUG Running task: 3170 / 0x46620a0
Jul 07 20:50:48-128204 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:48-128458 util-scheduler-8620 DEBUG Adding task: 3176 / 0x4662248
Jul 07 20:50:48-128735 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:48-128930 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:48-129120 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:48-129344 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:48-129536 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:48-129728 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:48-129920 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:48-130111 util-scheduler-8620 DEBUG Running task: 3176 / 0x4662248
Jul 07 20:50:48-130301 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:48-130502 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:48-130733 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:48-130940 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:48-131146 util-scheduler-8620 DEBUG Adding task: 3177 / 0x46620a0
Jul 07 20:50:48-131332 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:48-131540 util-scheduler-8620 DEBUG Adding task: 3178 / 0x46620a0
Jul 07 20:50:48-131784 util-scheduler-8620 DEBUG Checking readiness of task: 3178 / 0x46620a0
Jul 07 20:50:48-131978 util-scheduler-8620 DEBUG Checking readiness of task: 3177 / 0x46620a0
Jul 07 20:50:48-132170 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:48-132361 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:48-132550 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:48-132740 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:48-132930 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:48-133156 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:48-133372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:48-133565 util-scheduler-8620 DEBUG Running task: 3177 / 0x46620a0
Jul 07 20:50:48-133749 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:48-133927 util-8620 DEBUG process_notify is running
Jul 07 20:50:48-134100 util-8620 DEBUG client_notify is running
Jul 07 20:50:48-134287 util-scheduler-8620 DEBUG Canceling task: 3174 / 0x59ee8a0
Jul 07 20:50:48-134513 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:48-134733 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:48-134973 cadet-p2p-8620 DEBUG Checking 0x5a58460 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:48-135207 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:48-135385 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:48-135575 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:48-135858 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:48-136054 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:48-136234 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:48-136422 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:48-136611 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:48-136789 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:48-136972 util-scheduler-8620 DEBUG Canceling task: 3171 / 0x59e8808
Jul 07 20:50:48-137184 util-scheduler-8620 DEBUG Adding task: 3179 / 0x59e8808
Jul 07 20:50:48-137460 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:48-137631 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:48-137812 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:48-138012 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:48-138188 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:48-138362 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:48-138562 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:48-138766 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:48-138949 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:48-139128 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:48-139319 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:48-139569 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:49-892227 util-scheduler-8620 DEBUG Checking readiness of task: 3178 / 0x46620a0
Jul 07 20:50:49-892581 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:49-893377 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:49-893824 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:49-894038 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:49-894232 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:49-894423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:49-894613 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:49-894808 util-scheduler-8620 DEBUG Running task: 3173 / 0x52cbfb8
Jul 07 20:50:49-895049 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:49-895296 cadet-tun-8620 DEBUG  kx started 205 s ago
Jul 07 20:50:49-895503 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:49-895705 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:49-895907 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:49-896144 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:49-896324 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:49-896545 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:49-896873 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:49-897071 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:49-897333 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:49-897543 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:49-897863 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:49-898065 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:49-898290 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:49-898473 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:49-898649 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:49-898855 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:49-899070 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:49-899297 util-scheduler-8620 DEBUG Adding task: 3180 / 0x59ee8a0
Jul 07 20:50:49-899479 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:49-899683 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:49-899861 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:49-900036 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:49-900274 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:49-900470 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:49-900646 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:49-900847 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:49-901090 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:49-901309 util-scheduler-8620 DEBUG Adding task: 3181 / 0x52cbfb8
Jul 07 20:50:49-901577 util-scheduler-8620 DEBUG Checking readiness of task: 3178 / 0x46620a0
Jul 07 20:50:49-901772 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:49-901962 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:49-902153 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:49-902343 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:49-902535 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:49-902724 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:49-902913 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:49-903101 util-scheduler-8620 DEBUG Running task: 3180 / 0x59ee8a0
Jul 07 20:50:49-903330 util-scheduler-8620 DEBUG Adding task: 3182 / 0x59ee8a0
Jul 07 20:50:49-903554 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:49-903760 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:49-903970 util-scheduler-8620 DEBUG Adding task: 3183 / 0x46620a0
Jul 07 20:50:49-904214 util-scheduler-8620 DEBUG Checking readiness of task: 3183 / 0x46620a0
Jul 07 20:50:49-904409 util-scheduler-8620 DEBUG Checking readiness of task: 3178 / 0x46620a0
Jul 07 20:50:49-904599 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:49-904789 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:49-904978 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:49-905167 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:49-905381 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:49-905570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:49-905758 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:49-905950 util-scheduler-8620 DEBUG Running task: 3183 / 0x46620a0
Jul 07 20:50:49-906134 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:49-906314 util-8620 DEBUG process_notify is running
Jul 07 20:50:49-906486 util-8620 DEBUG client_notify is running
Jul 07 20:50:49-906683 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:49-906879 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:49-907071 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:49-907329 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:53-148377 util-scheduler-8620 DEBUG Checking readiness of task: 3178 / 0x46620a0
Jul 07 20:50:53-148764 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:53-148961 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:53-149154 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:53-149374 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:53-149567 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:53-149761 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:53-149963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:53-150160 util-scheduler-8620 DEBUG Running task: 3178 / 0x46620a0
Jul 07 20:50:53-150585 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:53-150842 util-scheduler-8620 DEBUG Adding task: 3184 / 0x4662248
Jul 07 20:50:53-151120 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:53-151315 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:53-151506 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:53-151696 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:53-151887 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:53-152077 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:53-152265 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:53-152456 util-scheduler-8620 DEBUG Running task: 3184 / 0x4662248
Jul 07 20:50:53-152646 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:53-152847 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:53-153082 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:53-153312 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:53-153518 util-scheduler-8620 DEBUG Adding task: 3185 / 0x46620a0
Jul 07 20:50:53-153706 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:53-153911 util-scheduler-8620 DEBUG Adding task: 3186 / 0x46620a0
Jul 07 20:50:53-154158 util-scheduler-8620 DEBUG Checking readiness of task: 3186 / 0x46620a0
Jul 07 20:50:53-154350 util-scheduler-8620 DEBUG Checking readiness of task: 3185 / 0x46620a0
Jul 07 20:50:53-154542 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:53-154732 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:53-154924 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:53-155113 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:53-155303 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:53-155490 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:53-155680 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:53-155870 util-scheduler-8620 DEBUG Running task: 3185 / 0x46620a0
Jul 07 20:50:53-156055 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:53-156233 util-8620 DEBUG process_notify is running
Jul 07 20:50:53-156405 util-8620 DEBUG client_notify is running
Jul 07 20:50:53-156606 util-scheduler-8620 DEBUG Canceling task: 3182 / 0x59ee8a0
Jul 07 20:50:53-156832 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:53-157088 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:53-157350 cadet-p2p-8620 DEBUG Checking 0x5a5b060 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:53-157585 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:53-157764 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:53-157954 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:53-158239 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:53-158435 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:53-158615 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:53-158803 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:53-158994 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:53-159173 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:53-159356 util-scheduler-8620 DEBUG Canceling task: 3179 / 0x59e8808
Jul 07 20:50:53-159568 util-scheduler-8620 DEBUG Adding task: 3187 / 0x59e8808
Jul 07 20:50:53-159819 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:53-159990 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:53-160171 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:53-160372 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:53-160548 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:53-160722 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:53-160922 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:53-161126 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:53-161330 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:53-161510 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:53-161700 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:53-161953 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:54-903209 util-scheduler-8620 DEBUG Checking readiness of task: 3186 / 0x46620a0
Jul 07 20:50:54-903594 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:54-904944 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:54-905330 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:54-905532 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:54-905725 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:54-905917 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:54-906107 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:54-906300 util-scheduler-8620 DEBUG Running task: 3181 / 0x52cbfb8
Jul 07 20:50:54-906540 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:54-906787 cadet-tun-8620 DEBUG  kx started 210 s ago
Jul 07 20:50:54-906995 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:54-907195 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:54-907398 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:54-907633 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:54-907815 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:54-908037 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:54-908328 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:54-908525 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:54-908762 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:54-908972 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:54-909316 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:54-909520 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:54-909744 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:54-909966 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:54-910143 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:54-910350 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:54-910585 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:54-910812 util-scheduler-8620 DEBUG Adding task: 3188 / 0x59ee8a0
Jul 07 20:50:54-910993 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:54-911197 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:54-911374 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:54-911551 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:54-911789 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:54-911986 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:54-912163 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:54-912361 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:54-912604 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:54-912802 util-scheduler-8620 DEBUG Adding task: 3189 / 0x52cbfb8
Jul 07 20:50:54-913069 util-scheduler-8620 DEBUG Checking readiness of task: 3186 / 0x46620a0
Jul 07 20:50:54-913290 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:54-913483 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:54-913673 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:54-913865 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:54-914054 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:54-914243 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:54-914431 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:54-914622 util-scheduler-8620 DEBUG Running task: 3188 / 0x59ee8a0
Jul 07 20:50:54-914829 util-scheduler-8620 DEBUG Adding task: 3190 / 0x59ee8a0
Jul 07 20:50:54-915052 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:54-915256 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:54-915464 util-scheduler-8620 DEBUG Adding task: 3191 / 0x46620a0
Jul 07 20:50:54-915710 util-scheduler-8620 DEBUG Checking readiness of task: 3191 / 0x46620a0
Jul 07 20:50:54-915903 util-scheduler-8620 DEBUG Checking readiness of task: 3186 / 0x46620a0
Jul 07 20:50:54-916093 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:54-916283 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:54-916472 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:54-916661 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:54-916852 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:54-917040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:54-917252 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:54-917444 util-scheduler-8620 DEBUG Running task: 3191 / 0x46620a0
Jul 07 20:50:54-917629 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:54-917809 util-8620 DEBUG process_notify is running
Jul 07 20:50:54-917981 util-8620 DEBUG client_notify is running
Jul 07 20:50:54-918163 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:54-918359 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:54-918550 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:54-918806 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:56-582281 util-scheduler-8620 DEBUG Checking readiness of task: 3186 / 0x46620a0
Jul 07 20:50:56-582667 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:56-582864 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:56-583087 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:56-583281 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:56-583475 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:56-583681 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:56-583887 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:56-584082 util-scheduler-8620 DEBUG Running task: 3186 / 0x46620a0
Jul 07 20:50:56-584504 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:56-584760 util-scheduler-8620 DEBUG Adding task: 3192 / 0x4662248
Jul 07 20:50:56-585041 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:56-585259 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:56-585452 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:56-585642 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:56-585832 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:56-586023 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:56-586211 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:56-586401 util-scheduler-8620 DEBUG Running task: 3192 / 0x4662248
Jul 07 20:50:56-586591 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:56-586791 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:56-587025 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:56-587231 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:56-587439 util-scheduler-8620 DEBUG Adding task: 3193 / 0x46620a0
Jul 07 20:50:56-587627 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:56-587833 util-scheduler-8620 DEBUG Adding task: 3194 / 0x46620a0
Jul 07 20:50:56-588077 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:56-588273 util-scheduler-8620 DEBUG Checking readiness of task: 3193 / 0x46620a0
Jul 07 20:50:56-588466 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:56-588656 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:56-588846 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:56-589036 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:56-589245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:56-589435 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:56-589626 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:56-589817 util-scheduler-8620 DEBUG Running task: 3193 / 0x46620a0
Jul 07 20:50:56-590001 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:56-590179 util-8620 DEBUG process_notify is running
Jul 07 20:50:56-590351 util-8620 DEBUG client_notify is running
Jul 07 20:50:56-590537 util-scheduler-8620 DEBUG Canceling task: 3190 / 0x59ee8a0
Jul 07 20:50:56-590764 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:56-590984 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:56-591223 cadet-p2p-8620 DEBUG Checking 0x5a5dd00 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:56-591457 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:56-591634 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:56-591825 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:56-592110 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:56-592305 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:56-592486 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:56-592693 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:56-592883 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:56-593062 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:56-593265 util-scheduler-8620 DEBUG Canceling task: 3187 / 0x59e8808
Jul 07 20:50:56-593478 util-scheduler-8620 DEBUG Adding task: 3195 / 0x59e8808
Jul 07 20:50:56-593729 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:56-593902 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:56-594083 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:56-594285 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:56-594460 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:56-594635 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:56-594833 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:56-595037 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:56-595221 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:56-595400 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:56-595592 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:56-595841 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:58-107118 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:58-107469 util-scheduler-8620 DEBUG Checking readiness of task: 3111 / 0x465ee60
Jul 07 20:50:58-107670 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:58-107863 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:58-108056 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:58-108248 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:58-108440 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:58-108630 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:58-108828 util-scheduler-8620 DEBUG Running task: 3111 / 0x465ee60
Jul 07 20:50:58-109277 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:50:58-109539 util-scheduler-8620 DEBUG Adding task: 3196 / 0x465f008
Jul 07 20:50:58-109818 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:58-110012 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:58-110205 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:58-110397 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:58-110590 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:58-110780 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:58-110971 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:58-111160 util-scheduler-8620 DEBUG Running task: 3196 / 0x465f008
Jul 07 20:50:58-111353 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 20:50:58-111593 nse-api-8620 DEBUG Received information about peer `TZQE' from peerinfo database
Jul 07 20:50:58-111883 cadet-hll-8620 DEBUG  hello for TZQE (90 bytes), expires on Tue Jul 08 08:50:58 2014
Jul 07 20:50:58-112108 cadet-p2p-8620 DEBUG set hello for TZQE
Jul 07 20:50:58-112408 cadet-p2p-8620 DEBUG  merge into 0x5a604a8 (90 bytes)
Jul 07 20:50:58-112604 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:58-112817 util-scheduler-8620 DEBUG Adding task: 3197 / 0x465ee60
Jul 07 20:50:59-914753 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-915114 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:59-915312 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-916278 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-916476 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-916669 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-916861 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-917053 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-917269 util-scheduler-8620 DEBUG Running task: 3189 / 0x52cbfb8
Jul 07 20:50:59-917508 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:50:59-917756 cadet-tun-8620 DEBUG  kx started 215 s ago
Jul 07 20:50:59-917963 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:50:59-918164 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:50:59-918368 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:50:59-918603 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:50:59-918783 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:50:59-919004 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:50:59-919295 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:50:59-919507 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:50:59-919743 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:50:59-919952 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:50:59-920271 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:50:59-920474 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:50:59-920701 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:50:59-920886 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:50:59-921062 cadet-con-8620 DEBUG  sendable
Jul 07 20:50:59-921291 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:50:59-921509 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:50:59-921735 util-scheduler-8620 DEBUG Adding task: 3198 / 0x59ee8a0
Jul 07 20:50:59-921915 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:50:59-922119 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:59-922295 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:50:59-922470 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:50:59-922708 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:50:59-922904 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:50:59-923081 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:50:59-923279 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:59-923523 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:50:59-923722 util-scheduler-8620 DEBUG Adding task: 3199 / 0x52cbfb8
Jul 07 20:50:59-923978 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-924171 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:59-924361 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-924551 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-924741 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-924932 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-925122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-925333 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-925524 util-scheduler-8620 DEBUG Running task: 3198 / 0x59ee8a0
Jul 07 20:50:59-925737 util-scheduler-8620 DEBUG Adding task: 3200 / 0x59ee8a0
Jul 07 20:50:59-925960 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:50:59-926166 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:59-926373 util-scheduler-8620 DEBUG Adding task: 3201 / 0x46620a0
Jul 07 20:50:59-926615 util-scheduler-8620 DEBUG Checking readiness of task: 3201 / 0x46620a0
Jul 07 20:50:59-926829 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-927021 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:59-927211 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-927401 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-927591 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-927780 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-927969 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-928158 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-928349 util-scheduler-8620 DEBUG Running task: 3201 / 0x46620a0
Jul 07 20:50:59-928535 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:59-928712 util-8620 DEBUG process_notify is running
Jul 07 20:50:59-928886 util-8620 DEBUG client_notify is running
Jul 07 20:50:59-929065 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:50:59-929286 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:59-929477 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:50:59-929730 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:50:59-943524 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-943744 util-scheduler-8620 DEBUG Checking readiness of task: 3194 / 0x46620a0
Jul 07 20:50:59-943939 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-944130 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-944322 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-944511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-944701 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-944890 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-945082 util-scheduler-8620 DEBUG Running task: 3194 / 0x46620a0
Jul 07 20:50:59-945514 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:50:59-945752 util-scheduler-8620 DEBUG Adding task: 3202 / 0x4662248
Jul 07 20:50:59-946003 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-946195 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-946386 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-946575 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-946767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-946956 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-947145 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-947333 util-scheduler-8620 DEBUG Running task: 3202 / 0x4662248
Jul 07 20:50:59-947525 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:50:59-947721 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:50:59-947939 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:50:59-948137 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:50:59-948356 util-scheduler-8620 DEBUG Adding task: 3203 / 0x46620a0
Jul 07 20:50:59-948543 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:50:59-948749 util-scheduler-8620 DEBUG Adding task: 3204 / 0x46620a0
Jul 07 20:50:59-948989 util-scheduler-8620 DEBUG Checking readiness of task: 3204 / 0x46620a0
Jul 07 20:50:59-949182 util-scheduler-8620 DEBUG Checking readiness of task: 3203 / 0x46620a0
Jul 07 20:50:59-949414 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:50:59-949605 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:50:59-949795 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:50:59-949985 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:50:59-950174 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:50:59-950362 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:50:59-950552 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:50:59-950742 util-scheduler-8620 DEBUG Running task: 3203 / 0x46620a0
Jul 07 20:50:59-950927 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:50:59-951101 util-8620 DEBUG process_notify is running
Jul 07 20:50:59-951271 util-8620 DEBUG client_notify is running
Jul 07 20:50:59-951457 util-scheduler-8620 DEBUG Canceling task: 3200 / 0x59ee8a0
Jul 07 20:50:59-951680 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:50:59-951897 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:50:59-952130 cadet-p2p-8620 DEBUG Checking 0x5a61120 towards 2FDYFV0X (->V8XX)
Jul 07 20:50:59-952363 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:50:59-952541 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:50:59-952728 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:50:59-953011 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:50:59-953227 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:50:59-953408 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:50:59-953595 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:50:59-953784 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:50:59-953963 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:50:59-954157 util-scheduler-8620 DEBUG Canceling task: 3195 / 0x59e8808
Jul 07 20:50:59-954369 util-scheduler-8620 DEBUG Adding task: 3205 / 0x59e8808
Jul 07 20:50:59-954615 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:50:59-954785 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:50:59-954964 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:50:59-955169 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:50:59-955346 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:50:59-955521 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:50:59-955721 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:50:59-955928 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:50:59-956113 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:50:59-956293 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:50:59-956482 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:50:59-956724 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:04-928850 util-scheduler-8620 DEBUG Checking readiness of task: 3204 / 0x46620a0
Jul 07 20:51:04-929262 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:04-929860 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:04-930102 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:04-930343 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:04-930539 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:04-930731 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:04-930921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:04-931115 util-scheduler-8620 DEBUG Running task: 3199 / 0x52cbfb8
Jul 07 20:51:04-931354 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:04-931601 cadet-tun-8620 DEBUG  kx started 220 s ago
Jul 07 20:51:04-931830 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:04-932034 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:04-932238 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:04-932473 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:04-932654 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:04-932876 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:04-933166 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:04-933389 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:04-933649 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:04-933861 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:04-934182 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:04-934384 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:04-934609 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:04-934793 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:04-934969 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:04-935175 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:04-935390 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:04-935615 util-scheduler-8620 DEBUG Adding task: 3206 / 0x59ee8a0
Jul 07 20:51:04-935798 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:04-936001 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:04-936178 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:04-936354 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:04-936592 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:04-936788 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:04-936965 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:04-937164 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:04-937429 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:04-937626 util-scheduler-8620 DEBUG Adding task: 3207 / 0x52cbfb8
Jul 07 20:51:04-937887 util-scheduler-8620 DEBUG Checking readiness of task: 3204 / 0x46620a0
Jul 07 20:51:04-938081 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:04-938272 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:04-938462 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:04-938652 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:04-938841 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:04-939030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:04-939220 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:04-939408 util-scheduler-8620 DEBUG Running task: 3206 / 0x59ee8a0
Jul 07 20:51:04-939618 util-scheduler-8620 DEBUG Adding task: 3208 / 0x59ee8a0
Jul 07 20:51:04-939840 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:04-940067 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:04-940277 util-scheduler-8620 DEBUG Adding task: 3209 / 0x46620a0
Jul 07 20:51:04-940521 util-scheduler-8620 DEBUG Checking readiness of task: 3209 / 0x46620a0
Jul 07 20:51:04-940716 util-scheduler-8620 DEBUG Checking readiness of task: 3204 / 0x46620a0
Jul 07 20:51:04-940928 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:04-941119 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:04-941330 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:04-941522 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:04-941711 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:04-941901 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:04-942106 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:04-942300 util-scheduler-8620 DEBUG Running task: 3209 / 0x46620a0
Jul 07 20:51:04-942485 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:04-942666 util-8620 DEBUG process_notify is running
Jul 07 20:51:04-942838 util-8620 DEBUG client_notify is running
Jul 07 20:51:04-943018 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:04-943214 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:04-943407 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:04-943662 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:07-416048 util-scheduler-8620 DEBUG Checking readiness of task: 3204 / 0x46620a0
Jul 07 20:51:07-416428 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:07-416625 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:07-416818 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:07-417011 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:07-417230 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:07-417424 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:07-417627 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:07-417823 util-scheduler-8620 DEBUG Running task: 3204 / 0x46620a0
Jul 07 20:51:07-418243 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:07-418497 util-scheduler-8620 DEBUG Adding task: 3210 / 0x4662248
Jul 07 20:51:07-418777 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:07-418970 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:07-419161 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:07-419352 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:07-419542 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:07-419732 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:07-419921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:07-420112 util-scheduler-8620 DEBUG Running task: 3210 / 0x4662248
Jul 07 20:51:07-420303 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:07-420515 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:07-420746 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:07-420953 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:07-421160 util-scheduler-8620 DEBUG Adding task: 3211 / 0x46620a0
Jul 07 20:51:07-421369 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:07-421576 util-scheduler-8620 DEBUG Adding task: 3212 / 0x46620a0
Jul 07 20:51:07-421819 util-scheduler-8620 DEBUG Checking readiness of task: 3212 / 0x46620a0
Jul 07 20:51:07-422012 util-scheduler-8620 DEBUG Checking readiness of task: 3211 / 0x46620a0
Jul 07 20:51:07-422205 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:07-422397 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:07-422589 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:07-422779 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:07-422972 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:07-423162 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:07-423351 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:07-423571 util-scheduler-8620 DEBUG Running task: 3211 / 0x46620a0
Jul 07 20:51:07-423758 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:07-423937 util-8620 DEBUG process_notify is running
Jul 07 20:51:07-424110 util-8620 DEBUG client_notify is running
Jul 07 20:51:07-424298 util-scheduler-8620 DEBUG Canceling task: 3208 / 0x59ee8a0
Jul 07 20:51:07-424525 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:07-424746 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:07-424987 cadet-p2p-8620 DEBUG Checking 0x5a63bd8 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:07-425244 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:07-425425 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:07-425617 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:07-425902 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:07-426099 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:07-426281 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:07-426471 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:07-426660 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:07-426839 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:07-427023 util-scheduler-8620 DEBUG Canceling task: 3205 / 0x59e8808
Jul 07 20:51:07-427239 util-scheduler-8620 DEBUG Adding task: 3213 / 0x59e8808
Jul 07 20:51:07-427490 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:07-427662 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:07-427842 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:07-428043 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:07-428219 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:07-428393 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:07-428591 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:07-428797 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:07-428980 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:07-429159 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:07-429372 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:07-429624 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:09-940295 util-scheduler-8620 DEBUG Checking readiness of task: 3212 / 0x46620a0
Jul 07 20:51:09-940681 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:09-941283 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:09-941481 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:09-941728 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:09-941936 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:09-942128 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:09-942317 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:09-942511 util-scheduler-8620 DEBUG Running task: 3207 / 0x52cbfb8
Jul 07 20:51:09-942764 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:09-943013 cadet-tun-8620 DEBUG  kx started 225 s ago
Jul 07 20:51:09-943223 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:09-943424 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:09-943627 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:09-943863 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:09-944045 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:09-944269 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:09-944558 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:09-944755 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:09-944992 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:09-945248 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:09-945573 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:09-945793 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:09-946018 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:09-946202 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:09-946378 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:09-946607 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:09-946823 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:09-947063 util-scheduler-8620 DEBUG Adding task: 3214 / 0x59ee8a0
Jul 07 20:51:09-947258 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:09-947465 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:09-947642 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:09-947820 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:09-948059 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:09-948256 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:09-948434 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:09-948633 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:09-948877 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:09-949075 util-scheduler-8620 DEBUG Adding task: 3215 / 0x52cbfb8
Jul 07 20:51:09-949354 util-scheduler-8620 DEBUG Checking readiness of task: 3212 / 0x46620a0
Jul 07 20:51:09-949549 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:09-949740 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:09-949931 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:09-950121 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:09-950311 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:09-950499 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:09-950689 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:09-950878 util-scheduler-8620 DEBUG Running task: 3214 / 0x59ee8a0
Jul 07 20:51:09-951087 util-scheduler-8620 DEBUG Adding task: 3216 / 0x59ee8a0
Jul 07 20:51:09-951310 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:09-951514 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:09-951723 util-scheduler-8620 DEBUG Adding task: 3217 / 0x46620a0
Jul 07 20:51:09-951965 util-scheduler-8620 DEBUG Checking readiness of task: 3217 / 0x46620a0
Jul 07 20:51:09-952161 util-scheduler-8620 DEBUG Checking readiness of task: 3212 / 0x46620a0
Jul 07 20:51:09-952352 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:09-952541 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:09-952730 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:09-952932 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:09-953121 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:09-953331 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:09-953520 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:09-953713 util-scheduler-8620 DEBUG Running task: 3217 / 0x46620a0
Jul 07 20:51:09-953897 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:09-954077 util-8620 DEBUG process_notify is running
Jul 07 20:51:09-954249 util-8620 DEBUG client_notify is running
Jul 07 20:51:09-954429 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:09-954625 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:09-954815 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:09-955086 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:10-544562 util-scheduler-8620 DEBUG Checking readiness of task: 3212 / 0x46620a0
Jul 07 20:51:10-544907 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:10-545103 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:10-545322 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:10-545515 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:10-545709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:10-545911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:10-546102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:10-546296 util-scheduler-8620 DEBUG Running task: 3212 / 0x46620a0
Jul 07 20:51:10-546713 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:10-546963 util-scheduler-8620 DEBUG Adding task: 3218 / 0x4662248
Jul 07 20:51:10-547236 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:10-547430 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:10-547621 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:10-547811 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:10-548004 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:10-548193 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:10-548384 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:10-548572 util-scheduler-8620 DEBUG Running task: 3218 / 0x4662248
Jul 07 20:51:10-548764 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:10-548964 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:10-549212 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:10-549420 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:10-549624 util-scheduler-8620 DEBUG Adding task: 3219 / 0x46620a0
Jul 07 20:51:10-549813 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:10-550019 util-scheduler-8620 DEBUG Adding task: 3220 / 0x46620a0
Jul 07 20:51:10-550262 util-scheduler-8620 DEBUG Checking readiness of task: 3220 / 0x46620a0
Jul 07 20:51:10-550455 util-scheduler-8620 DEBUG Checking readiness of task: 3219 / 0x46620a0
Jul 07 20:51:10-550646 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:10-550836 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:10-551025 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:10-551217 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:10-551406 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:10-551596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:10-551785 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:10-551976 util-scheduler-8620 DEBUG Running task: 3219 / 0x46620a0
Jul 07 20:51:10-552162 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:10-552339 util-8620 DEBUG process_notify is running
Jul 07 20:51:10-552511 util-8620 DEBUG client_notify is running
Jul 07 20:51:10-552699 util-scheduler-8620 DEBUG Canceling task: 3216 / 0x59ee8a0
Jul 07 20:51:10-552924 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:10-553144 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:10-553403 cadet-p2p-8620 DEBUG Checking 0x523c2f8 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:10-553637 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:10-553842 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:10-554034 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:10-554320 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:10-554517 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:10-554697 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:10-554887 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:10-555075 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:10-555253 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:10-555438 util-scheduler-8620 DEBUG Canceling task: 3213 / 0x59e8808
Jul 07 20:51:10-555650 util-scheduler-8620 DEBUG Adding task: 3221 / 0x59e8808
Jul 07 20:51:10-555900 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:10-556071 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:10-556252 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:10-556454 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:10-556628 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:10-556802 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:10-557001 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:10-557225 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:10-557411 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:10-557589 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:10-557779 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:10-558029 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:14-951447 util-scheduler-8620 DEBUG Checking readiness of task: 3220 / 0x46620a0
Jul 07 20:51:14-951840 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-952485 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-952692 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-952942 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-953150 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-953362 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-953552 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-953745 util-scheduler-8620 DEBUG Running task: 3215 / 0x52cbfb8
Jul 07 20:51:14-953982 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:14-954230 cadet-tun-8620 DEBUG  kx started 230 s ago
Jul 07 20:51:14-954437 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:14-954655 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:14-955123 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:14-955362 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:14-955544 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:14-955824 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:14-956192 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:14-956392 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:14-956630 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:14-956839 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:14-957157 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:14-957380 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:14-957605 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:14-957789 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:14-957978 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:14-958184 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:14-958428 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:14-958656 util-scheduler-8620 DEBUG Adding task: 3222 / 0x59ee8a0
Jul 07 20:51:14-958838 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:14-959044 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:14-959220 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:14-959394 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:14-959633 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:14-959830 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:14-960007 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:14-960206 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:14-960450 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:14-960647 util-scheduler-8620 DEBUG Adding task: 3223 / 0x52cbfb8
Jul 07 20:51:14-960908 util-scheduler-8620 DEBUG Checking readiness of task: 3220 / 0x46620a0
Jul 07 20:51:14-961101 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-961311 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-961501 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-961691 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-961881 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-962069 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-962258 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-962446 util-scheduler-8620 DEBUG Running task: 3222 / 0x59ee8a0
Jul 07 20:51:14-962655 util-scheduler-8620 DEBUG Adding task: 3224 / 0x59ee8a0
Jul 07 20:51:14-962876 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:14-963079 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:14-963289 util-scheduler-8620 DEBUG Adding task: 3225 / 0x46620a0
Jul 07 20:51:14-963531 util-scheduler-8620 DEBUG Checking readiness of task: 3225 / 0x46620a0
Jul 07 20:51:14-963725 util-scheduler-8620 DEBUG Checking readiness of task: 3220 / 0x46620a0
Jul 07 20:51:14-963916 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-964105 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-964294 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-964483 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-964672 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-964860 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-965049 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-965258 util-scheduler-8620 DEBUG Running task: 3225 / 0x46620a0
Jul 07 20:51:14-965445 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:14-965624 util-8620 DEBUG process_notify is running
Jul 07 20:51:14-965797 util-8620 DEBUG client_notify is running
Jul 07 20:51:14-965976 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:14-966175 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:14-966367 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:14-966612 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:14-966861 util-scheduler-8620 DEBUG Checking readiness of task: 3220 / 0x46620a0
Jul 07 20:51:14-967053 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-967244 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-967432 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-967622 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-967828 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-968017 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-968205 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-968395 util-scheduler-8620 DEBUG Running task: 3220 / 0x46620a0
Jul 07 20:51:14-968804 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:14-969035 util-scheduler-8620 DEBUG Adding task: 3226 / 0x4662248
Jul 07 20:51:14-969300 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-969493 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-969683 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-969872 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-970063 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-970251 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-970439 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-970628 util-scheduler-8620 DEBUG Running task: 3226 / 0x4662248
Jul 07 20:51:14-970818 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:14-971014 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:14-971230 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:14-971427 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:14-971627 util-scheduler-8620 DEBUG Adding task: 3227 / 0x46620a0
Jul 07 20:51:14-971813 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:14-972018 util-scheduler-8620 DEBUG Adding task: 3228 / 0x46620a0
Jul 07 20:51:14-972260 util-scheduler-8620 DEBUG Checking readiness of task: 3228 / 0x46620a0
Jul 07 20:51:14-972452 util-scheduler-8620 DEBUG Checking readiness of task: 3227 / 0x46620a0
Jul 07 20:51:14-972643 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:14-972831 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:14-973021 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:14-973233 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:14-973424 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:14-973614 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:14-973802 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:14-973993 util-scheduler-8620 DEBUG Running task: 3227 / 0x46620a0
Jul 07 20:51:14-974176 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:14-974350 util-8620 DEBUG process_notify is running
Jul 07 20:51:14-974519 util-8620 DEBUG client_notify is running
Jul 07 20:51:14-974704 util-scheduler-8620 DEBUG Canceling task: 3224 / 0x59ee8a0
Jul 07 20:51:14-974927 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:14-975143 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:14-975373 cadet-p2p-8620 DEBUG Checking 0x5a695e8 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:14-975606 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:14-975784 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:14-975969 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:14-976251 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:14-976445 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:14-976623 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:14-976809 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:14-976997 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:14-977175 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:14-977398 util-scheduler-8620 DEBUG Canceling task: 3221 / 0x59e8808
Jul 07 20:51:14-977610 util-scheduler-8620 DEBUG Adding task: 3229 / 0x59e8808
Jul 07 20:51:14-977855 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:14-978024 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:14-978205 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:14-978404 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:14-978578 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:14-978752 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:14-978951 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:14-979155 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:14-979563 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:14-979743 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:14-979932 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:14-980178 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:19-965800 util-scheduler-8620 DEBUG Checking readiness of task: 3228 / 0x46620a0
Jul 07 20:51:19-966239 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:19-966483 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:19-966679 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:19-966925 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:19-967133 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:19-967324 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:19-967515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:19-967708 util-scheduler-8620 DEBUG Running task: 3223 / 0x52cbfb8
Jul 07 20:51:19-967950 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:19-968196 cadet-tun-8620 DEBUG  kx started 235 s ago
Jul 07 20:51:19-968402 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:19-968603 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:19-968805 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:19-969040 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:19-969240 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:19-969464 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:19-969754 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:19-969952 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:19-970189 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:19-970401 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:19-970719 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:19-970922 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:19-971146 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:19-971330 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:19-971506 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:19-971714 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:19-971930 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:19-972155 util-scheduler-8620 DEBUG Adding task: 3230 / 0x59ee8a0
Jul 07 20:51:19-972336 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:19-972538 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:19-972716 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:19-972891 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:19-973130 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:19-973351 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:19-973529 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:19-973752 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:19-973996 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:19-974194 util-scheduler-8620 DEBUG Adding task: 3231 / 0x52cbfb8
Jul 07 20:51:19-974455 util-scheduler-8620 DEBUG Checking readiness of task: 3228 / 0x46620a0
Jul 07 20:51:19-974647 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:19-974837 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:19-975026 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:19-975218 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:19-975408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:19-975597 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:19-975785 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:19-975975 util-scheduler-8620 DEBUG Running task: 3230 / 0x59ee8a0
Jul 07 20:51:19-976183 util-scheduler-8620 DEBUG Adding task: 3232 / 0x59ee8a0
Jul 07 20:51:19-976406 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:19-976610 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:19-976818 util-scheduler-8620 DEBUG Adding task: 3233 / 0x46620a0
Jul 07 20:51:19-977062 util-scheduler-8620 DEBUG Checking readiness of task: 3233 / 0x46620a0
Jul 07 20:51:19-977276 util-scheduler-8620 DEBUG Checking readiness of task: 3228 / 0x46620a0
Jul 07 20:51:19-977468 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:19-977657 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:19-977871 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:19-978062 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:19-978252 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:19-978440 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:19-978630 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:19-978821 util-scheduler-8620 DEBUG Running task: 3233 / 0x46620a0
Jul 07 20:51:19-979006 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:19-979185 util-8620 DEBUG process_notify is running
Jul 07 20:51:19-979358 util-8620 DEBUG client_notify is running
Jul 07 20:51:19-979559 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:19-979757 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:19-979948 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:19-980204 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:24-030144 util-scheduler-8620 DEBUG Checking readiness of task: 3228 / 0x46620a0
Jul 07 20:51:24-030527 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-030727 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-030933 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-031129 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-031326 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-031521 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-031714 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-031913 util-scheduler-8620 DEBUG Running task: 3228 / 0x46620a0
Jul 07 20:51:24-032335 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:24-032593 util-scheduler-8620 DEBUG Adding task: 3234 / 0x4662248
Jul 07 20:51:24-032871 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-033100 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-033325 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-033520 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-033715 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-033908 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-034100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-034293 util-scheduler-8620 DEBUG Running task: 3234 / 0x4662248
Jul 07 20:51:24-034486 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:24-034688 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:24-034921 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:24-035130 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:24-035338 util-scheduler-8620 DEBUG Adding task: 3235 / 0x46620a0
Jul 07 20:51:24-035529 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:24-035738 util-scheduler-8620 DEBUG Adding task: 3236 / 0x46620a0
Jul 07 20:51:24-035984 util-scheduler-8620 DEBUG Checking readiness of task: 3236 / 0x46620a0
Jul 07 20:51:24-036178 util-scheduler-8620 DEBUG Checking readiness of task: 3235 / 0x46620a0
Jul 07 20:51:24-036373 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-036578 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-036770 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-036962 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-037155 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-037369 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-037562 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-037755 util-scheduler-8620 DEBUG Running task: 3235 / 0x46620a0
Jul 07 20:51:24-037944 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:24-038126 util-8620 DEBUG process_notify is running
Jul 07 20:51:24-038301 util-8620 DEBUG client_notify is running
Jul 07 20:51:24-038491 util-scheduler-8620 DEBUG Canceling task: 3232 / 0x59ee8a0
Jul 07 20:51:24-038724 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:24-038946 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:24-039187 cadet-p2p-8620 DEBUG Checking 0x5a6c260 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:24-039424 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:24-039603 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:24-039795 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:24-040082 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:24-040279 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:24-040462 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:24-040652 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:24-040844 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:24-041024 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:24-041233 util-scheduler-8620 DEBUG Canceling task: 3229 / 0x59e8808
Jul 07 20:51:24-041451 util-scheduler-8620 DEBUG Adding task: 3237 / 0x59e8808
Jul 07 20:51:24-041703 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:24-041877 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:24-042060 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:24-042263 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:24-042440 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:24-042617 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:24-042818 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:24-043025 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:24-043229 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:24-043412 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:24-043604 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:24-043856 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:24-975262 util-scheduler-8620 DEBUG Checking readiness of task: 3236 / 0x46620a0
Jul 07 20:51:24-975602 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-976477 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-976698 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-976894 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-977102 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-977316 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-977508 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-977702 util-scheduler-8620 DEBUG Running task: 3231 / 0x52cbfb8
Jul 07 20:51:24-977934 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:24-978190 cadet-tun-8620 DEBUG  kx started 4 m ago
Jul 07 20:51:24-978395 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:24-978596 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:24-978799 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:24-979033 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:24-979213 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:24-979433 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:24-979722 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:24-979918 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:24-980155 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:24-980366 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:24-980685 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:24-980888 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:24-981112 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:24-981319 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:24-981495 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:24-981703 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:24-981917 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:24-982141 util-scheduler-8620 DEBUG Adding task: 3238 / 0x59ee8a0
Jul 07 20:51:24-982321 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:24-982524 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:24-982703 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:24-982880 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:24-983117 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:24-983312 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:24-983489 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:24-983687 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:24-983930 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:24-984127 util-scheduler-8620 DEBUG Adding task: 3239 / 0x52cbfb8
Jul 07 20:51:24-984380 util-scheduler-8620 DEBUG Checking readiness of task: 3236 / 0x46620a0
Jul 07 20:51:24-984574 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-984764 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-984954 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-985145 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-985379 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-985570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-985758 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-985949 util-scheduler-8620 DEBUG Running task: 3238 / 0x59ee8a0
Jul 07 20:51:24-986155 util-scheduler-8620 DEBUG Adding task: 3240 / 0x59ee8a0
Jul 07 20:51:24-986378 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:24-986579 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:24-986785 util-scheduler-8620 DEBUG Adding task: 3241 / 0x46620a0
Jul 07 20:51:24-987028 util-scheduler-8620 DEBUG Checking readiness of task: 3241 / 0x46620a0
Jul 07 20:51:24-987221 util-scheduler-8620 DEBUG Checking readiness of task: 3236 / 0x46620a0
Jul 07 20:51:24-987412 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:24-987602 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:24-987793 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:24-987985 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:24-988176 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:24-988365 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:24-988555 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:24-988746 util-scheduler-8620 DEBUG Running task: 3241 / 0x46620a0
Jul 07 20:51:24-988931 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:24-989110 util-8620 DEBUG process_notify is running
Jul 07 20:51:24-989305 util-8620 DEBUG client_notify is running
Jul 07 20:51:24-989486 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:24-989681 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:24-989885 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:24-990135 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:27-098779 util-scheduler-8620 DEBUG Checking readiness of task: 3236 / 0x46620a0
Jul 07 20:51:27-099134 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:27-099335 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:27-099530 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:27-099724 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:27-099919 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:27-100116 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:27-100307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:27-100501 util-scheduler-8620 DEBUG Running task: 3236 / 0x46620a0
Jul 07 20:51:27-100919 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:27-101169 util-scheduler-8620 DEBUG Adding task: 3242 / 0x4662248
Jul 07 20:51:27-101466 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:27-101659 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:27-101851 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:27-102041 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:27-102232 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:27-102420 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:27-102611 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:27-102800 util-scheduler-8620 DEBUG Running task: 3242 / 0x4662248
Jul 07 20:51:27-103018 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:27-103218 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:27-103448 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:27-103653 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:27-103859 util-scheduler-8620 DEBUG Adding task: 3243 / 0x46620a0
Jul 07 20:51:27-104046 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:27-104251 util-scheduler-8620 DEBUG Adding task: 3244 / 0x46620a0
Jul 07 20:51:27-104495 util-scheduler-8620 DEBUG Checking readiness of task: 3244 / 0x46620a0
Jul 07 20:51:27-104688 util-scheduler-8620 DEBUG Checking readiness of task: 3243 / 0x46620a0
Jul 07 20:51:27-104880 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:27-105070 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:27-105283 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:27-105473 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:27-105663 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:27-105852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:27-106040 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:27-106231 util-scheduler-8620 DEBUG Running task: 3243 / 0x46620a0
Jul 07 20:51:27-106415 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:27-106594 util-8620 DEBUG process_notify is running
Jul 07 20:51:27-106764 util-8620 DEBUG client_notify is running
Jul 07 20:51:27-106951 util-scheduler-8620 DEBUG Canceling task: 3240 / 0x59ee8a0
Jul 07 20:51:27-107175 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:27-107394 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:27-107632 cadet-p2p-8620 DEBUG Checking 0x5a6ef00 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:27-107867 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:27-108044 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:27-108233 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:27-108517 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:27-108712 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:27-108892 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:27-109080 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:27-109291 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:27-109470 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:27-109654 util-scheduler-8620 DEBUG Canceling task: 3237 / 0x59e8808
Jul 07 20:51:27-109865 util-scheduler-8620 DEBUG Adding task: 3245 / 0x59e8808
Jul 07 20:51:27-110114 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:27-110285 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:27-110465 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:27-110665 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:27-110843 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:27-111017 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:27-111218 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:27-111423 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:27-111608 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:27-111786 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:27-111976 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:27-112225 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:29-985924 util-scheduler-8620 DEBUG Checking readiness of task: 3244 / 0x46620a0
Jul 07 20:51:29-986309 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:29-987383 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:29-987744 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:29-987940 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:29-988134 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:29-988324 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:29-988515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:29-988708 util-scheduler-8620 DEBUG Running task: 3239 / 0x52cbfb8
Jul 07 20:51:29-988948 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:29-989227 cadet-tun-8620 DEBUG  kx started 245 s ago
Jul 07 20:51:29-989438 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:29-989638 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:29-989840 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:29-990077 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:29-990259 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:29-990480 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:29-990771 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:29-990968 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:29-991206 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:29-991414 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:29-991732 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:29-991939 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:29-992164 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:29-992350 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:29-992526 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:29-992732 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:29-992948 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:29-993175 util-scheduler-8620 DEBUG Adding task: 3246 / 0x59ee8a0
Jul 07 20:51:29-993384 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:29-993588 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:29-993766 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:29-993942 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:29-994180 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:29-994390 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:29-994568 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:29-994766 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:29-995011 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:29-995209 util-scheduler-8620 DEBUG Adding task: 3247 / 0x52cbfb8
Jul 07 20:51:29-995475 util-scheduler-8620 DEBUG Checking readiness of task: 3244 / 0x46620a0
Jul 07 20:51:29-995669 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:29-995860 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:29-996050 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:29-996240 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:29-996431 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:29-996621 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:29-996810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:29-997000 util-scheduler-8620 DEBUG Running task: 3246 / 0x59ee8a0
Jul 07 20:51:29-997235 util-scheduler-8620 DEBUG Adding task: 3248 / 0x59ee8a0
Jul 07 20:51:29-997460 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:29-997664 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:29-997894 util-scheduler-8620 DEBUG Adding task: 3249 / 0x46620a0
Jul 07 20:51:29-998139 util-scheduler-8620 DEBUG Checking readiness of task: 3249 / 0x46620a0
Jul 07 20:51:29-998334 util-scheduler-8620 DEBUG Checking readiness of task: 3244 / 0x46620a0
Jul 07 20:51:29-998523 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:29-998713 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:29-998904 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:29-999093 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:29-999283 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:29-999472 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:29-999662 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:29-999853 util-scheduler-8620 DEBUG Running task: 3249 / 0x46620a0
Jul 07 20:51:30-000039 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:30-000221 util-8620 DEBUG process_notify is running
Jul 07 20:51:30-000397 util-8620 DEBUG client_notify is running
Jul 07 20:51:30-000578 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:30-000776 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:30-000970 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:30-001254 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:32-783157 util-scheduler-8620 DEBUG Checking readiness of task: 3244 / 0x46620a0
Jul 07 20:51:32-783543 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:32-783741 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:32-783933 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:32-784125 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:32-784317 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:32-784509 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:32-784705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:32-784902 util-scheduler-8620 DEBUG Running task: 3244 / 0x46620a0
Jul 07 20:51:32-785355 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:32-785614 util-scheduler-8620 DEBUG Adding task: 3250 / 0x4662248
Jul 07 20:51:32-785892 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:32-786087 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:32-786277 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:32-786468 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:32-786658 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:32-786847 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:32-787036 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:32-787225 util-scheduler-8620 DEBUG Running task: 3250 / 0x4662248
Jul 07 20:51:32-787417 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:32-787615 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:32-787847 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:32-788054 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:32-788260 util-scheduler-8620 DEBUG Adding task: 3251 / 0x46620a0
Jul 07 20:51:32-788448 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:32-788653 util-scheduler-8620 DEBUG Adding task: 3252 / 0x46620a0
Jul 07 20:51:32-788896 util-scheduler-8620 DEBUG Checking readiness of task: 3252 / 0x46620a0
Jul 07 20:51:32-789118 util-scheduler-8620 DEBUG Checking readiness of task: 3251 / 0x46620a0
Jul 07 20:51:32-789337 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:32-789528 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:32-789718 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:32-789908 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:32-790099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:32-790287 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:32-790477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:32-790667 util-scheduler-8620 DEBUG Running task: 3251 / 0x46620a0
Jul 07 20:51:32-790852 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:32-791031 util-8620 DEBUG process_notify is running
Jul 07 20:51:32-791202 util-8620 DEBUG client_notify is running
Jul 07 20:51:32-791390 util-scheduler-8620 DEBUG Canceling task: 3248 / 0x59ee8a0
Jul 07 20:51:32-791615 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:32-791835 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:32-792075 cadet-p2p-8620 DEBUG Checking 0x5a71b10 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:32-792309 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:32-792487 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:32-792677 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:32-792963 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:32-793161 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:32-793366 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:32-793557 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:32-793746 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:32-793925 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:32-794107 util-scheduler-8620 DEBUG Canceling task: 3245 / 0x59e8808
Jul 07 20:51:32-794319 util-scheduler-8620 DEBUG Adding task: 3253 / 0x59e8808
Jul 07 20:51:32-794571 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:32-794743 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:32-794925 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:32-795125 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:32-795299 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:32-795475 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:32-795673 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:32-795878 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:32-796061 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:32-796240 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:32-796431 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:32-797220 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:34-997580 util-scheduler-8620 DEBUG Checking readiness of task: 3252 / 0x46620a0
Jul 07 20:51:34-997977 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:34-998947 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:34-999159 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:34-999434 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:34-999630 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:34-999820 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:35-000010 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:35-000208 util-scheduler-8620 DEBUG Running task: 3247 / 0x52cbfb8
Jul 07 20:51:35-000474 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:35-000724 cadet-tun-8620 DEBUG  kx started 250 s ago
Jul 07 20:51:35-000932 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:35-001134 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:35-001363 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:35-001602 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:35-001787 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:35-002010 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:35-002303 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:35-002504 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:35-002743 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:35-002955 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:35-003278 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:35-003481 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:35-003706 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:35-003892 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:35-004070 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:35-004278 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:35-004496 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:35-004724 util-scheduler-8620 DEBUG Adding task: 3254 / 0x59ee8a0
Jul 07 20:51:35-004906 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:35-005114 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:35-005316 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:35-005494 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:35-005735 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:35-005933 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:35-006112 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:35-006313 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:35-006558 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:35-006758 util-scheduler-8620 DEBUG Adding task: 3255 / 0x52cbfb8
Jul 07 20:51:35-007021 util-scheduler-8620 DEBUG Checking readiness of task: 3252 / 0x46620a0
Jul 07 20:51:35-007216 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:35-007408 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:35-007600 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:35-007791 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:35-007983 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:35-008175 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:35-008365 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:35-008557 util-scheduler-8620 DEBUG Running task: 3254 / 0x59ee8a0
Jul 07 20:51:35-008765 util-scheduler-8620 DEBUG Adding task: 3256 / 0x59ee8a0
Jul 07 20:51:35-009011 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:35-009240 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:35-009455 util-scheduler-8620 DEBUG Adding task: 3257 / 0x46620a0
Jul 07 20:51:35-009706 util-scheduler-8620 DEBUG Checking readiness of task: 3257 / 0x46620a0
Jul 07 20:51:35-009903 util-scheduler-8620 DEBUG Checking readiness of task: 3252 / 0x46620a0
Jul 07 20:51:35-010097 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:35-010289 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:35-010481 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:35-010674 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:35-010883 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:35-011075 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:35-011266 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:35-011460 util-scheduler-8620 DEBUG Running task: 3257 / 0x46620a0
Jul 07 20:51:35-011647 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:35-011828 util-8620 DEBUG process_notify is running
Jul 07 20:51:35-012004 util-8620 DEBUG client_notify is running
Jul 07 20:51:35-012184 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:35-012382 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:35-012577 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:35-012833 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:38-404554 util-scheduler-8620 DEBUG Checking readiness of task: 3252 / 0x46620a0
Jul 07 20:51:38-404933 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:38-405131 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:38-405352 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:38-405544 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:38-405739 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:38-405939 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:38-406131 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:38-406326 util-scheduler-8620 DEBUG Running task: 3252 / 0x46620a0
Jul 07 20:51:38-406747 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:38-407000 util-scheduler-8620 DEBUG Adding task: 3258 / 0x4662248
Jul 07 20:51:38-407278 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:38-407473 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:38-407663 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:38-407854 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:38-408045 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:38-408234 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:38-408422 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:38-408611 util-scheduler-8620 DEBUG Running task: 3258 / 0x4662248
Jul 07 20:51:38-408803 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:38-409002 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:38-409254 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:38-409463 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:38-409670 util-scheduler-8620 DEBUG Adding task: 3259 / 0x46620a0
Jul 07 20:51:38-409858 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:38-410065 util-scheduler-8620 DEBUG Adding task: 3260 / 0x46620a0
Jul 07 20:51:38-410308 util-scheduler-8620 DEBUG Checking readiness of task: 3260 / 0x46620a0
Jul 07 20:51:38-410510 util-scheduler-8620 DEBUG Checking readiness of task: 3259 / 0x46620a0
Jul 07 20:51:38-410703 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:38-410894 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:38-411083 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:38-411272 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:38-411463 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:38-411652 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:38-411874 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:38-412067 util-scheduler-8620 DEBUG Running task: 3259 / 0x46620a0
Jul 07 20:51:38-412253 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:38-412431 util-8620 DEBUG process_notify is running
Jul 07 20:51:38-412614 util-8620 DEBUG client_notify is running
Jul 07 20:51:38-412802 util-scheduler-8620 DEBUG Canceling task: 3256 / 0x59ee8a0
Jul 07 20:51:38-413029 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:38-413269 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:38-413510 cadet-p2p-8620 DEBUG Checking 0x5a74740 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:38-413744 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:38-413921 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:38-414112 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:38-414397 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:38-414592 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:38-414772 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:38-414960 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:38-415148 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:38-415326 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:38-415509 util-scheduler-8620 DEBUG Canceling task: 3253 / 0x59e8808
Jul 07 20:51:38-415721 util-scheduler-8620 DEBUG Adding task: 3261 / 0x59e8808
Jul 07 20:51:38-415975 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:38-416146 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:38-416327 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:38-416527 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:38-416701 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:38-416875 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:38-417074 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:38-417299 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:38-417484 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:38-417662 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:38-417853 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:38-418101 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:40-008496 util-scheduler-8620 DEBUG Checking readiness of task: 3260 / 0x46620a0
Jul 07 20:51:40-008856 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:40-009752 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:40-009951 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:40-010200 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:40-010409 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:40-010602 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:40-010794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:40-010988 util-scheduler-8620 DEBUG Running task: 3255 / 0x52cbfb8
Jul 07 20:51:40-011224 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:40-011470 cadet-tun-8620 DEBUG  kx started 255 s ago
Jul 07 20:51:40-011679 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:40-011882 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:40-012087 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:40-012327 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:40-012509 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:40-012733 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:40-013024 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:40-013267 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:40-013509 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:40-013720 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:40-014039 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:40-014242 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:40-014468 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:40-014653 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:40-014884 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:40-015169 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:40-015389 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:40-015618 util-scheduler-8620 DEBUG Adding task: 3262 / 0x59ee8a0
Jul 07 20:51:40-015801 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:40-016031 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:40-016212 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:40-016389 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:40-016631 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:40-016830 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:40-017009 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:40-017229 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:40-017476 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:40-017677 util-scheduler-8620 DEBUG Adding task: 3263 / 0x52cbfb8
Jul 07 20:51:40-017935 util-scheduler-8620 DEBUG Checking readiness of task: 3260 / 0x46620a0
Jul 07 20:51:40-018131 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:40-018323 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:40-018516 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:40-018707 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:40-018900 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:40-019091 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:40-019281 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:40-019473 util-scheduler-8620 DEBUG Running task: 3262 / 0x59ee8a0
Jul 07 20:51:40-019682 util-scheduler-8620 DEBUG Adding task: 3264 / 0x59ee8a0
Jul 07 20:51:40-019906 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:40-020111 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:40-020319 util-scheduler-8620 DEBUG Adding task: 3265 / 0x46620a0
Jul 07 20:51:40-020564 util-scheduler-8620 DEBUG Checking readiness of task: 3265 / 0x46620a0
Jul 07 20:51:40-020760 util-scheduler-8620 DEBUG Checking readiness of task: 3260 / 0x46620a0
Jul 07 20:51:40-020953 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:40-021144 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:40-021358 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:40-021550 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:40-021744 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:40-021934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:40-022126 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:40-022321 util-scheduler-8620 DEBUG Running task: 3265 / 0x46620a0
Jul 07 20:51:40-022510 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:40-022691 util-8620 DEBUG process_notify is running
Jul 07 20:51:40-022865 util-8620 DEBUG client_notify is running
Jul 07 20:51:40-023046 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:40-023259 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:40-023453 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:40-023707 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:43-448029 util-scheduler-8620 DEBUG Checking readiness of task: 3260 / 0x46620a0
Jul 07 20:51:43-448391 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:43-448588 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:43-448780 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:43-448973 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:43-449165 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:43-449402 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:43-449595 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:43-449791 util-scheduler-8620 DEBUG Running task: 3260 / 0x46620a0
Jul 07 20:51:43-450213 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:43-450469 util-scheduler-8620 DEBUG Adding task: 3266 / 0x4662248
Jul 07 20:51:43-450746 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:43-450939 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:43-451130 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:43-451320 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:43-451509 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:43-451699 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:43-451890 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:43-452079 util-scheduler-8620 DEBUG Running task: 3266 / 0x4662248
Jul 07 20:51:43-452272 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:43-452473 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:43-452704 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:43-452910 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:43-453119 util-scheduler-8620 DEBUG Adding task: 3267 / 0x46620a0
Jul 07 20:51:43-453329 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:43-453536 util-scheduler-8620 DEBUG Adding task: 3268 / 0x46620a0
Jul 07 20:51:43-453781 util-scheduler-8620 DEBUG Checking readiness of task: 3268 / 0x46620a0
Jul 07 20:51:43-453974 util-scheduler-8620 DEBUG Checking readiness of task: 3267 / 0x46620a0
Jul 07 20:51:43-454165 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:43-454355 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:43-454545 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:43-454736 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:43-454925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:43-455114 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:43-455302 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:43-455493 util-scheduler-8620 DEBUG Running task: 3267 / 0x46620a0
Jul 07 20:51:43-455678 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:43-455856 util-8620 DEBUG process_notify is running
Jul 07 20:51:43-456027 util-8620 DEBUG client_notify is running
Jul 07 20:51:43-456214 util-scheduler-8620 DEBUG Canceling task: 3264 / 0x59ee8a0
Jul 07 20:51:43-456440 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:43-456660 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:43-456928 cadet-p2p-8620 DEBUG Checking 0x5a773b8 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:43-457164 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:43-457361 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:43-457551 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:43-457836 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:43-458031 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:43-458210 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:43-458398 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:43-458584 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:43-458762 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:43-458946 util-scheduler-8620 DEBUG Canceling task: 3261 / 0x59e8808
Jul 07 20:51:43-459160 util-scheduler-8620 DEBUG Adding task: 3269 / 0x59e8808
Jul 07 20:51:43-459411 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:43-459582 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:43-459763 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:43-459964 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:43-460138 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:43-460311 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:43-460509 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:43-460714 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:43-460897 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:43-461076 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:43-461286 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:43-461534 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:45-019390 util-scheduler-8620 DEBUG Checking readiness of task: 3268 / 0x46620a0
Jul 07 20:51:45-019757 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:45-020400 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:45-020600 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:45-020850 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:45-021060 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:45-021274 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:45-021466 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:45-021661 util-scheduler-8620 DEBUG Running task: 3263 / 0x52cbfb8
Jul 07 20:51:45-021898 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:45-022145 cadet-tun-8620 DEBUG  kx started 260 s ago
Jul 07 20:51:45-022354 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:45-022556 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:45-022761 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:45-022999 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:45-023181 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:45-023404 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:45-023694 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:45-023895 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:45-024134 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:45-024345 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:45-024662 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:45-024866 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:45-025092 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:45-025297 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:45-025476 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:45-025709 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:45-025926 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:45-026152 util-scheduler-8620 DEBUG Adding task: 3270 / 0x59ee8a0
Jul 07 20:51:45-026334 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:45-026539 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:45-026719 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:45-026896 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:45-027136 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:45-027336 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:45-027515 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:45-027715 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:45-027959 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:45-028158 util-scheduler-8620 DEBUG Adding task: 3271 / 0x52cbfb8
Jul 07 20:51:45-028415 util-scheduler-8620 DEBUG Checking readiness of task: 3268 / 0x46620a0
Jul 07 20:51:45-028610 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:45-028803 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:45-029007 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:45-029218 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:45-029411 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:45-029603 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:45-029793 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:45-029985 util-scheduler-8620 DEBUG Running task: 3270 / 0x59ee8a0
Jul 07 20:51:45-030194 util-scheduler-8620 DEBUG Adding task: 3272 / 0x59ee8a0
Jul 07 20:51:45-030418 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:45-030622 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:45-030832 util-scheduler-8620 DEBUG Adding task: 3273 / 0x46620a0
Jul 07 20:51:45-031077 util-scheduler-8620 DEBUG Checking readiness of task: 3273 / 0x46620a0
Jul 07 20:51:45-031274 util-scheduler-8620 DEBUG Checking readiness of task: 3268 / 0x46620a0
Jul 07 20:51:45-031466 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:45-031659 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:45-031850 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:45-032043 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:45-032235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:45-032425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:45-032620 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:45-032813 util-scheduler-8620 DEBUG Running task: 3273 / 0x46620a0
Jul 07 20:51:45-033002 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:45-033183 util-8620 DEBUG process_notify is running
Jul 07 20:51:45-033379 util-8620 DEBUG client_notify is running
Jul 07 20:51:45-033560 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:45-033756 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:45-033951 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:45-034208 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:48-473569 util-scheduler-8620 DEBUG Checking readiness of task: 3268 / 0x46620a0
Jul 07 20:51:48-473971 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:48-474169 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:48-474362 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:48-474599 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:48-474796 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:48-474988 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:48-475179 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:48-475379 util-scheduler-8620 DEBUG Running task: 3268 / 0x46620a0
Jul 07 20:51:48-475809 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:48-476067 util-scheduler-8620 DEBUG Adding task: 3274 / 0x4662248
Jul 07 20:51:48-476350 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:48-476550 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:48-476742 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:48-476934 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:48-477126 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:48-477342 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:48-477533 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:48-477723 util-scheduler-8620 DEBUG Running task: 3274 / 0x4662248
Jul 07 20:51:48-477918 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:48-478118 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:48-478354 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:48-478562 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:48-478772 util-scheduler-8620 DEBUG Adding task: 3275 / 0x46620a0
Jul 07 20:51:48-478962 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:48-479170 util-scheduler-8620 DEBUG Adding task: 3276 / 0x46620a0
Jul 07 20:51:48-479418 util-scheduler-8620 DEBUG Checking readiness of task: 3276 / 0x46620a0
Jul 07 20:51:48-479613 util-scheduler-8620 DEBUG Checking readiness of task: 3275 / 0x46620a0
Jul 07 20:51:48-479806 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:48-479996 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:48-480189 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:48-480379 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:48-480570 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:48-480761 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:48-480952 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:48-481143 util-scheduler-8620 DEBUG Running task: 3275 / 0x46620a0
Jul 07 20:51:48-481351 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:48-481531 util-8620 DEBUG process_notify is running
Jul 07 20:51:48-481705 util-8620 DEBUG client_notify is running
Jul 07 20:51:48-481893 util-scheduler-8620 DEBUG Canceling task: 3272 / 0x59ee8a0
Jul 07 20:51:48-482122 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:48-482344 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:48-482586 cadet-p2p-8620 DEBUG Checking 0x5240970 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:48-482823 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:48-483002 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:48-483193 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:48-483480 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:48-483677 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:48-483859 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:48-484048 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:48-484258 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:48-484442 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:48-484627 util-scheduler-8620 DEBUG Canceling task: 3269 / 0x59e8808
Jul 07 20:51:48-484842 util-scheduler-8620 DEBUG Adding task: 3277 / 0x59e8808
Jul 07 20:51:48-485093 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:48-485288 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:48-485472 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:48-485674 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:48-485850 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:48-486025 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:48-486226 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:48-486432 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:48-486617 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:48-486796 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:48-486989 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:48-487724 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:50-029843 util-scheduler-8620 DEBUG Checking readiness of task: 3276 / 0x46620a0
Jul 07 20:51:50-030198 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-031231 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-031432 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-031627 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-031820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-032013 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-032205 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-032398 util-scheduler-8620 DEBUG Running task: 3271 / 0x52cbfb8
Jul 07 20:51:50-032635 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:50-032881 cadet-tun-8620 DEBUG  kx started 265 s ago
Jul 07 20:51:50-033091 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:50-033331 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:50-033536 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:50-033772 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:50-033956 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:50-034180 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:50-034475 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:50-034680 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:50-034921 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:50-035133 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:50-035452 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:50-035656 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:50-035881 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:50-036065 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:50-036242 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:50-036451 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:50-036673 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:50-036907 util-scheduler-8620 DEBUG Adding task: 3278 / 0x59ee8a0
Jul 07 20:51:50-037091 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:50-037321 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:50-037500 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:50-037677 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:50-037917 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:50-038141 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:50-038322 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:50-038522 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:50-038770 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:50-038970 util-scheduler-8620 DEBUG Adding task: 3279 / 0x52cbfb8
Jul 07 20:51:50-039230 util-scheduler-8620 DEBUG Checking readiness of task: 3276 / 0x46620a0
Jul 07 20:51:50-039426 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-039618 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-039811 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-040004 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-040196 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-040387 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-040577 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-040769 util-scheduler-8620 DEBUG Running task: 3278 / 0x59ee8a0
Jul 07 20:51:50-040979 util-scheduler-8620 DEBUG Adding task: 3280 / 0x59ee8a0
Jul 07 20:51:50-041227 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:50-041435 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:50-041645 util-scheduler-8620 DEBUG Adding task: 3281 / 0x46620a0
Jul 07 20:51:50-041890 util-scheduler-8620 DEBUG Checking readiness of task: 3281 / 0x46620a0
Jul 07 20:51:50-042086 util-scheduler-8620 DEBUG Checking readiness of task: 3276 / 0x46620a0
Jul 07 20:51:50-042278 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-042470 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-042663 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-042854 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-043046 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-043236 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-043427 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-043620 util-scheduler-8620 DEBUG Running task: 3281 / 0x46620a0
Jul 07 20:51:50-043807 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:50-043986 util-8620 DEBUG process_notify is running
Jul 07 20:51:50-044162 util-8620 DEBUG client_notify is running
Jul 07 20:51:50-044342 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:50-044540 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:50-044732 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:50-044990 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:50-045262 util-scheduler-8620 DEBUG Checking readiness of task: 3276 / 0x46620a0
Jul 07 20:51:50-045459 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-045650 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-045843 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-046034 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-046225 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-046415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-046605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-046798 util-scheduler-8620 DEBUG Running task: 3276 / 0x46620a0
Jul 07 20:51:50-047202 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:50-047449 util-scheduler-8620 DEBUG Adding task: 3282 / 0x4662248
Jul 07 20:51:50-047699 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-047895 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-048087 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-048278 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-048471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-048662 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-048853 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-049043 util-scheduler-8620 DEBUG Running task: 3282 / 0x4662248
Jul 07 20:51:50-049257 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:50-049455 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:50-049674 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:50-049873 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:50-050073 util-scheduler-8620 DEBUG Adding task: 3283 / 0x46620a0
Jul 07 20:51:50-050260 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:50-050465 util-scheduler-8620 DEBUG Adding task: 3284 / 0x46620a0
Jul 07 20:51:50-050708 util-scheduler-8620 DEBUG Checking readiness of task: 3284 / 0x46620a0
Jul 07 20:51:50-050903 util-scheduler-8620 DEBUG Checking readiness of task: 3283 / 0x46620a0
Jul 07 20:51:50-051096 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:50-051287 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:50-051480 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:50-051671 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:50-051862 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:50-052053 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:50-052243 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:50-052437 util-scheduler-8620 DEBUG Running task: 3283 / 0x46620a0
Jul 07 20:51:50-052622 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:50-052798 util-8620 DEBUG process_notify is running
Jul 07 20:51:50-052970 util-8620 DEBUG client_notify is running
Jul 07 20:51:50-053155 util-scheduler-8620 DEBUG Canceling task: 3280 / 0x59ee8a0
Jul 07 20:51:50-053404 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:50-053622 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:50-053855 cadet-p2p-8620 DEBUG Checking 0x5a7ccc0 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:50-054089 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:50-054269 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:50-054456 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:50-054750 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:50-054950 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:50-055130 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:50-055319 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:50-055510 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:50-055690 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:50-055875 util-scheduler-8620 DEBUG Canceling task: 3277 / 0x59e8808
Jul 07 20:51:50-056087 util-scheduler-8620 DEBUG Adding task: 3285 / 0x59e8808
Jul 07 20:51:50-056333 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:50-056506 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:50-056687 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:50-056889 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:50-057065 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:50-057262 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:50-057477 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:50-057684 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:50-057869 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:50-058048 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:50-058239 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:50-058485 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:55-044109 util-scheduler-8620 DEBUG Checking readiness of task: 3284 / 0x46620a0
Jul 07 20:51:55-044495 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:55-045066 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:55-045321 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:55-045559 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:55-045756 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:55-045950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:55-046142 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:55-046337 util-scheduler-8620 DEBUG Running task: 3279 / 0x52cbfb8
Jul 07 20:51:55-046575 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:51:55-046823 cadet-tun-8620 DEBUG  kx started 270 s ago
Jul 07 20:51:55-047031 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:51:55-047234 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:51:55-047438 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:51:55-047674 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:51:55-047859 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:51:55-048082 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:51:55-048373 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:51:55-048572 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:51:55-048811 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:51:55-049023 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:51:55-049362 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:51:55-049565 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:51:55-049793 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:51:55-049979 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:51:55-050176 cadet-con-8620 DEBUG  sendable
Jul 07 20:51:55-050394 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:51:55-050614 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:51:55-050842 util-scheduler-8620 DEBUG Adding task: 3286 / 0x59ee8a0
Jul 07 20:51:55-051024 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:51:55-051229 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:55-051408 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:51:55-051586 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:51:55-051826 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:51:55-052024 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:51:55-052203 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:51:55-052404 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:55-052649 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:51:55-052848 util-scheduler-8620 DEBUG Adding task: 3287 / 0x52cbfb8
Jul 07 20:51:55-053107 util-scheduler-8620 DEBUG Checking readiness of task: 3284 / 0x46620a0
Jul 07 20:51:55-053322 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:55-053516 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:55-053737 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:55-053930 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:55-054122 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:55-054312 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:55-054503 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:55-054695 util-scheduler-8620 DEBUG Running task: 3286 / 0x59ee8a0
Jul 07 20:51:55-054903 util-scheduler-8620 DEBUG Adding task: 3288 / 0x59ee8a0
Jul 07 20:51:55-055129 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:51:55-055335 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:55-055545 util-scheduler-8620 DEBUG Adding task: 3289 / 0x46620a0
Jul 07 20:51:55-055789 util-scheduler-8620 DEBUG Checking readiness of task: 3289 / 0x46620a0
Jul 07 20:51:55-055985 util-scheduler-8620 DEBUG Checking readiness of task: 3284 / 0x46620a0
Jul 07 20:51:55-056178 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:55-056369 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:55-056561 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:55-056752 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:55-056944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:55-057134 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:55-057345 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:55-057540 util-scheduler-8620 DEBUG Running task: 3289 / 0x46620a0
Jul 07 20:51:55-057725 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:55-057907 util-8620 DEBUG process_notify is running
Jul 07 20:51:55-058082 util-8620 DEBUG client_notify is running
Jul 07 20:51:55-058262 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:51:55-058461 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:55-058654 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:51:55-058910 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:51:59-013482 util-scheduler-8620 DEBUG Checking readiness of task: 3284 / 0x46620a0
Jul 07 20:51:59-013875 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:59-014074 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:59-014269 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:59-014464 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:59-014658 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:59-014852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:59-015058 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:59-015256 util-scheduler-8620 DEBUG Running task: 3284 / 0x46620a0
Jul 07 20:51:59-015680 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:51:59-015941 util-scheduler-8620 DEBUG Adding task: 3290 / 0x4662248
Jul 07 20:51:59-016222 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:59-016419 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:59-016623 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:59-016816 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:59-017008 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:59-017226 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:59-017420 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:59-017647 util-scheduler-8620 DEBUG Running task: 3290 / 0x4662248
Jul 07 20:51:59-017843 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:51:59-018046 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:51:59-018283 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:51:59-018492 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:51:59-018703 util-scheduler-8620 DEBUG Adding task: 3291 / 0x46620a0
Jul 07 20:51:59-018892 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:51:59-019102 util-scheduler-8620 DEBUG Adding task: 3292 / 0x46620a0
Jul 07 20:51:59-019350 util-scheduler-8620 DEBUG Checking readiness of task: 3292 / 0x46620a0
Jul 07 20:51:59-019544 util-scheduler-8620 DEBUG Checking readiness of task: 3291 / 0x46620a0
Jul 07 20:51:59-019739 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:51:59-019932 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:51:59-020123 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:51:59-020315 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:51:59-020508 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:51:59-020698 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:51:59-020890 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:51:59-021083 util-scheduler-8620 DEBUG Running task: 3291 / 0x46620a0
Jul 07 20:51:59-021297 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:51:59-021477 util-8620 DEBUG process_notify is running
Jul 07 20:51:59-021652 util-8620 DEBUG client_notify is running
Jul 07 20:51:59-021842 util-scheduler-8620 DEBUG Canceling task: 3288 / 0x59ee8a0
Jul 07 20:51:59-022069 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:51:59-022293 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:51:59-022534 cadet-p2p-8620 DEBUG Checking 0x5a7f9a0 towards 2FDYFV0X (->V8XX)
Jul 07 20:51:59-022771 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:51:59-022951 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:51:59-023143 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:51:59-023430 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:51:59-023627 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:51:59-023810 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:51:59-024000 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:51:59-024191 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:51:59-024371 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:51:59-024557 util-scheduler-8620 DEBUG Canceling task: 3285 / 0x59e8808
Jul 07 20:51:59-024772 util-scheduler-8620 DEBUG Adding task: 3293 / 0x59e8808
Jul 07 20:51:59-025025 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:51:59-025217 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:51:59-025402 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:51:59-025607 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:51:59-025785 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:51:59-025961 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:51:59-026163 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:51:59-026371 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:51:59-026556 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:51:59-026737 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:51:59-026931 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:51:59-027184 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:00-054038 util-scheduler-8620 DEBUG Checking readiness of task: 3292 / 0x46620a0
Jul 07 20:52:00-054458 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-055040 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-055266 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-055502 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-055698 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-055892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-056084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-056280 util-scheduler-8620 DEBUG Running task: 3287 / 0x52cbfb8
Jul 07 20:52:00-056518 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:00-056766 cadet-tun-8620 DEBUG  kx started 275 s ago
Jul 07 20:52:00-056975 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:00-057178 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:00-057407 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:00-057644 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:00-057827 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:00-058051 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:00-058344 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:00-058544 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:00-058784 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:00-058994 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:00-059314 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:00-059518 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:00-059744 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:00-059930 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:00-060107 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:00-060316 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:00-060533 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:00-060759 util-scheduler-8620 DEBUG Adding task: 3294 / 0x59ee8a0
Jul 07 20:52:00-060944 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:00-061150 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:00-061349 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:00-061527 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:00-061768 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:00-061966 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:00-062146 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:00-062347 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:00-062593 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:00-062794 util-scheduler-8620 DEBUG Adding task: 3295 / 0x52cbfb8
Jul 07 20:52:00-063052 util-scheduler-8620 DEBUG Checking readiness of task: 3292 / 0x46620a0
Jul 07 20:52:00-063249 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-063441 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-063634 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-063825 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-064018 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-064210 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-064400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-064593 util-scheduler-8620 DEBUG Running task: 3294 / 0x59ee8a0
Jul 07 20:52:00-064802 util-scheduler-8620 DEBUG Adding task: 3296 / 0x59ee8a0
Jul 07 20:52:00-065026 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:00-065286 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:00-065499 util-scheduler-8620 DEBUG Adding task: 3297 / 0x46620a0
Jul 07 20:52:00-065746 util-scheduler-8620 DEBUG Checking readiness of task: 3297 / 0x46620a0
Jul 07 20:52:00-065943 util-scheduler-8620 DEBUG Checking readiness of task: 3292 / 0x46620a0
Jul 07 20:52:00-066136 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-066328 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-066519 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-066711 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-066902 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-067093 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-067285 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-067540 util-scheduler-8620 DEBUG Running task: 3297 / 0x46620a0
Jul 07 20:52:00-067795 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:00-067977 util-8620 DEBUG process_notify is running
Jul 07 20:52:00-068154 util-8620 DEBUG client_notify is running
Jul 07 20:52:00-068338 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:00-068537 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:00-068732 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:00-068987 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:00-069258 util-scheduler-8620 DEBUG Checking readiness of task: 3292 / 0x46620a0
Jul 07 20:52:00-069455 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-069647 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-069839 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-070032 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-070224 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-070415 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-070605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-070797 util-scheduler-8620 DEBUG Running task: 3292 / 0x46620a0
Jul 07 20:52:00-071208 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:00-071440 util-scheduler-8620 DEBUG Adding task: 3298 / 0x4662248
Jul 07 20:52:00-071691 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-071886 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-072078 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-072270 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-072462 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-072654 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-072845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-073036 util-scheduler-8620 DEBUG Running task: 3298 / 0x4662248
Jul 07 20:52:00-073246 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:00-073447 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:00-073667 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:00-073866 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:00-074090 util-scheduler-8620 DEBUG Adding task: 3299 / 0x46620a0
Jul 07 20:52:00-074279 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:00-074503 util-scheduler-8620 DEBUG Adding task: 3300 / 0x46620a0
Jul 07 20:52:00-074748 util-scheduler-8620 DEBUG Checking readiness of task: 3300 / 0x46620a0
Jul 07 20:52:00-074944 util-scheduler-8620 DEBUG Checking readiness of task: 3299 / 0x46620a0
Jul 07 20:52:00-075138 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:00-075330 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:00-075522 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:00-075715 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:00-075907 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:00-076097 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:00-076288 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:00-076481 util-scheduler-8620 DEBUG Running task: 3299 / 0x46620a0
Jul 07 20:52:00-076667 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:00-076845 util-8620 DEBUG process_notify is running
Jul 07 20:52:00-077016 util-8620 DEBUG client_notify is running
Jul 07 20:52:00-077224 util-scheduler-8620 DEBUG Canceling task: 3296 / 0x59ee8a0
Jul 07 20:52:00-077451 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:00-077670 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:00-077905 cadet-p2p-8620 DEBUG Checking 0x5a825c8 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:00-078141 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:00-078322 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:00-078511 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:00-078795 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:00-078992 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:00-079172 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:00-079402 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:00-079595 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:00-079776 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:00-079963 util-scheduler-8620 DEBUG Canceling task: 3293 / 0x59e8808
Jul 07 20:52:00-080177 util-scheduler-8620 DEBUG Adding task: 3301 / 0x59e8808
Jul 07 20:52:00-080424 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:00-080596 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:00-080778 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:00-080984 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:00-081161 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:00-081358 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:00-081558 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:00-081766 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:00-081952 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:00-082132 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:00-082323 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:00-082569 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:05-067937 util-scheduler-8620 DEBUG Checking readiness of task: 3300 / 0x46620a0
Jul 07 20:52:05-068334 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-068948 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-069146 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-069431 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-069645 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-069840 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-070034 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-070257 util-scheduler-8620 DEBUG Running task: 3295 / 0x52cbfb8
Jul 07 20:52:05-070499 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:05-070748 cadet-tun-8620 DEBUG  kx started 280 s ago
Jul 07 20:52:05-070957 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:05-071160 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:05-071364 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:05-071602 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:05-071785 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:05-072012 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:05-072305 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:05-072505 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:05-072758 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:05-072971 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:05-073312 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:05-073518 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:05-073745 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:05-073931 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:05-074108 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:05-074318 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:05-074535 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:05-074764 util-scheduler-8620 DEBUG Adding task: 3302 / 0x59ee8a0
Jul 07 20:52:05-074946 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:05-075152 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:05-075332 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:05-075509 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:05-075750 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:05-075948 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:05-076130 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:05-076330 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:05-076577 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:05-076779 util-scheduler-8620 DEBUG Adding task: 3303 / 0x52cbfb8
Jul 07 20:52:05-077044 util-scheduler-8620 DEBUG Checking readiness of task: 3300 / 0x46620a0
Jul 07 20:52:05-077261 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-077456 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-077648 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-077840 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-078034 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-078225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-078415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-078606 util-scheduler-8620 DEBUG Running task: 3302 / 0x59ee8a0
Jul 07 20:52:05-078818 util-scheduler-8620 DEBUG Adding task: 3304 / 0x59ee8a0
Jul 07 20:52:05-079043 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:05-079250 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:05-079461 util-scheduler-8620 DEBUG Adding task: 3305 / 0x46620a0
Jul 07 20:52:05-079706 util-scheduler-8620 DEBUG Checking readiness of task: 3305 / 0x46620a0
Jul 07 20:52:05-079903 util-scheduler-8620 DEBUG Checking readiness of task: 3300 / 0x46620a0
Jul 07 20:52:05-080096 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-080288 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-080480 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-080689 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-080883 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-081075 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-081285 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-081480 util-scheduler-8620 DEBUG Running task: 3305 / 0x46620a0
Jul 07 20:52:05-081667 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:05-081848 util-8620 DEBUG process_notify is running
Jul 07 20:52:05-082028 util-8620 DEBUG client_notify is running
Jul 07 20:52:05-082211 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:05-082409 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:05-082603 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:05-082859 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:05-100928 util-scheduler-8620 DEBUG Checking readiness of task: 3300 / 0x46620a0
Jul 07 20:52:05-101148 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-101364 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-101556 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-101748 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-101939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-102135 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-102328 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-102528 util-scheduler-8620 DEBUG Running task: 3300 / 0x46620a0
Jul 07 20:52:05-102936 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:05-103172 util-scheduler-8620 DEBUG Adding task: 3306 / 0x4662248
Jul 07 20:52:05-103424 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-103618 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-103809 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-103999 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-104189 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-104378 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-104566 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-104757 util-scheduler-8620 DEBUG Running task: 3306 / 0x4662248
Jul 07 20:52:05-104947 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:05-105146 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:05-105392 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:05-105596 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:05-105799 util-scheduler-8620 DEBUG Adding task: 3307 / 0x46620a0
Jul 07 20:52:05-105986 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:05-106193 util-scheduler-8620 DEBUG Adding task: 3308 / 0x46620a0
Jul 07 20:52:05-106438 util-scheduler-8620 DEBUG Checking readiness of task: 3308 / 0x46620a0
Jul 07 20:52:05-106632 util-scheduler-8620 DEBUG Checking readiness of task: 3307 / 0x46620a0
Jul 07 20:52:05-106823 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:05-107012 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:05-107204 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:05-107393 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:05-107605 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:05-107795 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:05-107985 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:05-108176 util-scheduler-8620 DEBUG Running task: 3307 / 0x46620a0
Jul 07 20:52:05-108360 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:05-108536 util-8620 DEBUG process_notify is running
Jul 07 20:52:05-108707 util-8620 DEBUG client_notify is running
Jul 07 20:52:05-108893 util-scheduler-8620 DEBUG Canceling task: 3304 / 0x59ee8a0
Jul 07 20:52:05-109120 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:05-109363 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:05-109598 cadet-p2p-8620 DEBUG Checking 0x524b4f0 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:05-109833 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:05-110012 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:05-110199 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:05-110483 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:05-110679 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:05-110858 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:05-111045 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:05-111233 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:05-111412 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:05-111595 util-scheduler-8620 DEBUG Canceling task: 3301 / 0x59e8808
Jul 07 20:52:05-111816 util-scheduler-8620 DEBUG Adding task: 3309 / 0x59e8808
Jul 07 20:52:05-112066 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:05-112237 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:05-112419 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:05-112620 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:05-112795 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:05-112970 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:05-113167 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:05-113393 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:05-113576 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:05-113754 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:05-113943 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:05-114188 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:10-081901 util-scheduler-8620 DEBUG Checking readiness of task: 3308 / 0x46620a0
Jul 07 20:52:10-082275 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:10-083291 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:10-083499 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:10-083699 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:10-083894 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:10-084086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:10-084278 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:10-084473 util-scheduler-8620 DEBUG Running task: 3303 / 0x52cbfb8
Jul 07 20:52:10-084711 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:10-084959 cadet-tun-8620 DEBUG  kx started 285 s ago
Jul 07 20:52:10-085166 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:10-085396 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:10-085601 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:10-085838 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:10-086022 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:10-086245 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:10-086566 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:10-086766 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:10-087006 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:10-087218 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:10-087537 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:10-087740 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:10-087966 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:10-088152 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:10-088328 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:10-088537 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:10-088753 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:10-088980 util-scheduler-8620 DEBUG Adding task: 3310 / 0x59ee8a0
Jul 07 20:52:10-089162 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:10-089391 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:10-089573 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:10-089750 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:10-089989 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:10-090187 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:10-090365 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:10-090567 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:10-090811 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:10-091011 util-scheduler-8620 DEBUG Adding task: 3311 / 0x52cbfb8
Jul 07 20:52:10-091270 util-scheduler-8620 DEBUG Checking readiness of task: 3308 / 0x46620a0
Jul 07 20:52:10-091466 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:10-091658 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:10-091850 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:10-092043 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:10-092234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:10-092425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:10-092615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:10-092807 util-scheduler-8620 DEBUG Running task: 3310 / 0x59ee8a0
Jul 07 20:52:10-093016 util-scheduler-8620 DEBUG Adding task: 3312 / 0x59ee8a0
Jul 07 20:52:10-093262 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:10-093468 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:10-093678 util-scheduler-8620 DEBUG Adding task: 3313 / 0x46620a0
Jul 07 20:52:10-093923 util-scheduler-8620 DEBUG Checking readiness of task: 3313 / 0x46620a0
Jul 07 20:52:10-094118 util-scheduler-8620 DEBUG Checking readiness of task: 3308 / 0x46620a0
Jul 07 20:52:10-094310 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:10-094501 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:10-094693 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:10-094884 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:10-095075 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:10-095266 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:10-095457 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:10-095650 util-scheduler-8620 DEBUG Running task: 3313 / 0x46620a0
Jul 07 20:52:10-095836 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:10-096016 util-8620 DEBUG process_notify is running
Jul 07 20:52:10-096190 util-8620 DEBUG client_notify is running
Jul 07 20:52:10-096388 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:10-096585 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:10-096778 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:10-097035 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:12-357273 util-scheduler-8620 DEBUG Checking readiness of task: 3308 / 0x46620a0
Jul 07 20:52:12-357631 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:12-357837 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:12-358032 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:12-358224 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:12-358417 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:12-358610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:12-358809 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:12-359003 util-scheduler-8620 DEBUG Running task: 3308 / 0x46620a0
Jul 07 20:52:12-359421 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:12-359671 util-scheduler-8620 DEBUG Adding task: 3314 / 0x4662248
Jul 07 20:52:12-359943 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:12-360137 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:12-360359 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:12-360563 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:12-360754 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:12-360943 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:12-361134 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:12-361365 util-scheduler-8620 DEBUG Running task: 3314 / 0x4662248
Jul 07 20:52:12-361560 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:12-361775 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:12-362035 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:12-362273 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:12-362483 util-scheduler-8620 DEBUG Adding task: 3315 / 0x46620a0
Jul 07 20:52:12-362673 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:12-362879 util-scheduler-8620 DEBUG Adding task: 3316 / 0x46620a0
Jul 07 20:52:12-363131 util-scheduler-8620 DEBUG Checking readiness of task: 3316 / 0x46620a0
Jul 07 20:52:12-363325 util-scheduler-8620 DEBUG Checking readiness of task: 3315 / 0x46620a0
Jul 07 20:52:12-363518 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:12-363709 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:12-363903 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:12-364095 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:12-364285 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:12-364475 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:12-364665 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:12-364857 util-scheduler-8620 DEBUG Running task: 3315 / 0x46620a0
Jul 07 20:52:12-365044 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:12-365242 util-8620 DEBUG process_notify is running
Jul 07 20:52:12-365418 util-8620 DEBUG client_notify is running
Jul 07 20:52:12-365607 util-scheduler-8620 DEBUG Canceling task: 3312 / 0x59ee8a0
Jul 07 20:52:12-365833 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:12-366087 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:12-366329 cadet-p2p-8620 DEBUG Checking 0x5a87eb8 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:12-366565 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:12-366744 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:12-366934 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:12-367221 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:12-367418 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:12-367597 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:12-367787 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:12-367976 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:12-368155 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:12-368340 util-scheduler-8620 DEBUG Canceling task: 3309 / 0x59e8808
Jul 07 20:52:12-368555 util-scheduler-8620 DEBUG Adding task: 3317 / 0x59e8808
Jul 07 20:52:12-368805 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:12-368977 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:12-369158 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:12-369382 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:12-369558 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:12-369732 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:12-369932 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:12-370138 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:12-370322 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:12-370501 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:12-370692 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:12-370933 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:15-093890 util-scheduler-8620 DEBUG Checking readiness of task: 3316 / 0x46620a0
Jul 07 20:52:15-094270 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:15-095467 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:15-095676 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:15-095874 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:15-096068 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:15-096262 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:15-096454 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:15-096652 util-scheduler-8620 DEBUG Running task: 3311 / 0x52cbfb8
Jul 07 20:52:15-096890 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:15-097155 cadet-tun-8620 DEBUG  kx started 290 s ago
Jul 07 20:52:15-097387 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:15-097592 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:15-097798 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:15-098035 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:15-098218 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:15-098441 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:15-098734 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:15-098933 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:15-099172 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:15-099383 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:15-099705 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:15-099908 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:15-100134 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:15-100344 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:15-100521 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:15-100728 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:15-100945 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:15-101171 util-scheduler-8620 DEBUG Adding task: 3318 / 0x59ee8a0
Jul 07 20:52:15-101375 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:15-101579 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:15-101756 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:15-101932 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:15-102170 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:15-102365 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:15-102543 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:15-102741 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:15-102984 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:15-103182 util-scheduler-8620 DEBUG Adding task: 3319 / 0x52cbfb8
Jul 07 20:52:15-103439 util-scheduler-8620 DEBUG Checking readiness of task: 3316 / 0x46620a0
Jul 07 20:52:15-103631 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:15-103822 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:15-104012 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:15-104201 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:15-104392 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:15-104581 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:15-104770 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:15-104959 util-scheduler-8620 DEBUG Running task: 3318 / 0x59ee8a0
Jul 07 20:52:15-105167 util-scheduler-8620 DEBUG Adding task: 3320 / 0x59ee8a0
Jul 07 20:52:15-105412 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:15-105617 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:15-105824 util-scheduler-8620 DEBUG Adding task: 3321 / 0x46620a0
Jul 07 20:52:15-106068 util-scheduler-8620 DEBUG Checking readiness of task: 3321 / 0x46620a0
Jul 07 20:52:15-106263 util-scheduler-8620 DEBUG Checking readiness of task: 3316 / 0x46620a0
Jul 07 20:52:15-106454 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:15-106645 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:15-106837 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:15-107026 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:15-107231 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:15-107420 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:15-107608 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:15-107799 util-scheduler-8620 DEBUG Running task: 3321 / 0x46620a0
Jul 07 20:52:15-107984 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:15-108162 util-8620 DEBUG process_notify is running
Jul 07 20:52:15-108335 util-8620 DEBUG client_notify is running
Jul 07 20:52:15-108513 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:15-108709 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:15-108901 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:15-109147 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:16-063828 util-scheduler-8620 DEBUG Checking readiness of task: 3316 / 0x46620a0
Jul 07 20:52:16-064224 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:16-064457 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:16-064653 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:16-064847 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:16-065040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:16-065281 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:16-065476 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:16-065674 util-scheduler-8620 DEBUG Running task: 3316 / 0x46620a0
Jul 07 20:52:16-066099 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:16-066360 util-scheduler-8620 DEBUG Adding task: 3322 / 0x4662248
Jul 07 20:52:16-066644 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:16-066841 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:16-067035 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:16-067229 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:16-067422 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:16-067613 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:16-067804 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:16-067995 util-scheduler-8620 DEBUG Running task: 3322 / 0x4662248
Jul 07 20:52:16-068190 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:16-068391 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:16-068627 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:16-068836 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:16-069045 util-scheduler-8620 DEBUG Adding task: 3323 / 0x46620a0
Jul 07 20:52:16-069258 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:16-069467 util-scheduler-8620 DEBUG Adding task: 3324 / 0x46620a0
Jul 07 20:52:16-069715 util-scheduler-8620 DEBUG Checking readiness of task: 3324 / 0x46620a0
Jul 07 20:52:16-069909 util-scheduler-8620 DEBUG Checking readiness of task: 3323 / 0x46620a0
Jul 07 20:52:16-070104 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:16-070295 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:16-070489 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:16-070681 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:16-070872 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:16-071064 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:16-071255 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:16-071450 util-scheduler-8620 DEBUG Running task: 3323 / 0x46620a0
Jul 07 20:52:16-071636 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:16-071818 util-8620 DEBUG process_notify is running
Jul 07 20:52:16-071991 util-8620 DEBUG client_notify is running
Jul 07 20:52:16-072182 util-scheduler-8620 DEBUG Canceling task: 3320 / 0x59ee8a0
Jul 07 20:52:16-072409 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:16-072631 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:16-072872 cadet-p2p-8620 DEBUG Checking 0x5a8aae8 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:16-073109 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:16-073310 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:16-073503 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:16-073788 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:16-073987 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:16-074186 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:16-074378 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:16-074570 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:16-074750 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:16-074936 util-scheduler-8620 DEBUG Canceling task: 3317 / 0x59e8808
Jul 07 20:52:16-075150 util-scheduler-8620 DEBUG Adding task: 3325 / 0x59e8808
Jul 07 20:52:16-075402 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:16-075575 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:16-075757 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:16-075960 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:16-076138 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:16-076315 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:16-076519 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:16-076726 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:16-076912 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:16-077093 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:16-077305 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:16-077560 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:20-107377 util-scheduler-8620 DEBUG Checking readiness of task: 3324 / 0x46620a0
Jul 07 20:52:20-107773 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-108422 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-108625 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-108893 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-109105 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-109319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-109509 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-109703 util-scheduler-8620 DEBUG Running task: 3319 / 0x52cbfb8
Jul 07 20:52:20-109940 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:20-110186 cadet-tun-8620 DEBUG  kx started 295 s ago
Jul 07 20:52:20-110393 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:20-110593 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:20-110794 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:20-111029 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:20-111211 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:20-111433 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:20-111723 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:20-111921 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:20-112158 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:20-112368 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:20-112687 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:20-112888 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:20-113113 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:20-113317 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:20-113506 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:20-113713 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:20-113928 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:20-114153 util-scheduler-8620 DEBUG Adding task: 3326 / 0x59ee8a0
Jul 07 20:52:20-114333 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:20-114537 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:20-114714 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:20-114923 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:20-115163 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:20-115359 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:20-115536 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:20-115735 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:20-115997 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:20-116197 util-scheduler-8620 DEBUG Adding task: 3327 / 0x52cbfb8
Jul 07 20:52:20-116460 util-scheduler-8620 DEBUG Checking readiness of task: 3324 / 0x46620a0
Jul 07 20:52:20-116653 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-116844 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-117033 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-117243 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-117434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-117627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-117815 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-118006 util-scheduler-8620 DEBUG Running task: 3326 / 0x59ee8a0
Jul 07 20:52:20-118214 util-scheduler-8620 DEBUG Adding task: 3328 / 0x59ee8a0
Jul 07 20:52:20-118437 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:20-118642 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:20-118851 util-scheduler-8620 DEBUG Adding task: 3329 / 0x46620a0
Jul 07 20:52:20-119095 util-scheduler-8620 DEBUG Checking readiness of task: 3329 / 0x46620a0
Jul 07 20:52:20-119289 util-scheduler-8620 DEBUG Checking readiness of task: 3324 / 0x46620a0
Jul 07 20:52:20-119480 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-119669 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-119860 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-120049 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-120238 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-120427 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-120616 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-120807 util-scheduler-8620 DEBUG Running task: 3329 / 0x46620a0
Jul 07 20:52:20-120991 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:20-121171 util-8620 DEBUG process_notify is running
Jul 07 20:52:20-121364 util-8620 DEBUG client_notify is running
Jul 07 20:52:20-121543 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:20-121738 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:20-121929 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:20-122186 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:20-122433 util-scheduler-8620 DEBUG Checking readiness of task: 3324 / 0x46620a0
Jul 07 20:52:20-122626 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-122816 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-123006 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-123195 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-123385 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-123573 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-123762 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-123953 util-scheduler-8620 DEBUG Running task: 3324 / 0x46620a0
Jul 07 20:52:20-124359 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:20-124604 util-scheduler-8620 DEBUG Adding task: 3330 / 0x4662248
Jul 07 20:52:20-124851 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-125045 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-125256 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-125446 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-125635 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-125825 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-126013 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-126202 util-scheduler-8620 DEBUG Running task: 3330 / 0x4662248
Jul 07 20:52:20-126391 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:20-126588 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:20-126804 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:20-127002 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:20-127200 util-scheduler-8620 DEBUG Adding task: 3331 / 0x46620a0
Jul 07 20:52:20-127384 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:20-127592 util-scheduler-8620 DEBUG Adding task: 3332 / 0x46620a0
Jul 07 20:52:20-127833 util-scheduler-8620 DEBUG Checking readiness of task: 3332 / 0x46620a0
Jul 07 20:52:20-128026 util-scheduler-8620 DEBUG Checking readiness of task: 3331 / 0x46620a0
Jul 07 20:52:20-128218 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:20-128407 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:20-128597 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:20-128787 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:20-128977 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:20-129165 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:20-129374 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:20-129565 util-scheduler-8620 DEBUG Running task: 3331 / 0x46620a0
Jul 07 20:52:20-129748 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:20-129924 util-8620 DEBUG process_notify is running
Jul 07 20:52:20-130092 util-8620 DEBUG client_notify is running
Jul 07 20:52:20-130278 util-scheduler-8620 DEBUG Canceling task: 3328 / 0x59ee8a0
Jul 07 20:52:20-130500 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:20-130716 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:20-130946 cadet-p2p-8620 DEBUG Checking 0x5a8d738 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:20-131179 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:20-131358 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:20-131545 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:20-131826 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:20-132021 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:20-132199 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:20-132387 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:20-132575 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:20-132753 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:20-132935 util-scheduler-8620 DEBUG Canceling task: 3325 / 0x59e8808
Jul 07 20:52:20-133145 util-scheduler-8620 DEBUG Adding task: 3333 / 0x59e8808
Jul 07 20:52:20-133410 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:20-133582 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:20-133763 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:20-133963 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:20-134154 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:20-134329 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:20-134526 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:20-134731 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:20-134925 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:20-135102 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:20-135291 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:20-135537 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:25-121363 util-scheduler-8620 DEBUG Checking readiness of task: 3332 / 0x46620a0
Jul 07 20:52:25-121757 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:25-122314 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:25-122515 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:25-122777 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:25-122989 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:25-123181 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:25-123374 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:25-123568 util-scheduler-8620 DEBUG Running task: 3327 / 0x52cbfb8
Jul 07 20:52:25-123806 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:25-124066 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:25-124274 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:25-124476 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:25-124678 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:25-124913 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:25-125094 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:25-125336 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:25-125629 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:25-125826 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:25-126064 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:25-126273 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:25-126591 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:25-126793 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:25-127018 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:25-127201 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:25-127377 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:25-127584 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:25-127801 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:25-128027 util-scheduler-8620 DEBUG Adding task: 3334 / 0x59ee8a0
Jul 07 20:52:25-128208 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:25-128411 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:25-128588 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:25-128763 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:25-129000 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:25-129217 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:25-129396 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:25-129595 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:25-129838 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:25-130037 util-scheduler-8620 DEBUG Adding task: 3335 / 0x52cbfb8
Jul 07 20:52:25-130297 util-scheduler-8620 DEBUG Checking readiness of task: 3332 / 0x46620a0
Jul 07 20:52:25-130490 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:25-130712 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:25-130903 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:25-131093 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:25-131284 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:25-131472 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:25-131661 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:25-131851 util-scheduler-8620 DEBUG Running task: 3334 / 0x59ee8a0
Jul 07 20:52:25-132059 util-scheduler-8620 DEBUG Adding task: 3336 / 0x59ee8a0
Jul 07 20:52:25-132282 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:25-132486 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:25-132693 util-scheduler-8620 DEBUG Adding task: 3337 / 0x46620a0
Jul 07 20:52:25-132937 util-scheduler-8620 DEBUG Checking readiness of task: 3337 / 0x46620a0
Jul 07 20:52:25-133132 util-scheduler-8620 DEBUG Checking readiness of task: 3332 / 0x46620a0
Jul 07 20:52:25-133345 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:25-133535 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:25-133726 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:25-133915 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:25-134105 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:25-134293 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:25-134482 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:25-134673 util-scheduler-8620 DEBUG Running task: 3337 / 0x46620a0
Jul 07 20:52:25-134859 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:25-135037 util-8620 DEBUG process_notify is running
Jul 07 20:52:25-135283 util-8620 DEBUG client_notify is running
Jul 07 20:52:25-135537 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:25-135737 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:25-135929 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:25-136187 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:29-120211 util-scheduler-8620 DEBUG Checking readiness of task: 3332 / 0x46620a0
Jul 07 20:52:29-120595 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:29-120798 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:29-120993 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:29-121185 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:29-121407 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:29-121597 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:29-121788 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:29-121986 util-scheduler-8620 DEBUG Running task: 3332 / 0x46620a0
Jul 07 20:52:29-122417 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:29-122702 util-scheduler-8620 DEBUG Adding task: 3338 / 0x4662248
Jul 07 20:52:29-122995 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:29-123192 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:29-123382 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:29-123571 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:29-123761 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:29-123983 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:29-124178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:29-124369 util-scheduler-8620 DEBUG Running task: 3338 / 0x4662248
Jul 07 20:52:29-124563 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:29-124764 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:29-125000 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:29-125237 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:29-125453 util-scheduler-8620 DEBUG Adding task: 3339 / 0x46620a0
Jul 07 20:52:29-125644 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:29-125850 util-scheduler-8620 DEBUG Adding task: 3340 / 0x46620a0
Jul 07 20:52:29-126101 util-scheduler-8620 DEBUG Checking readiness of task: 3340 / 0x46620a0
Jul 07 20:52:29-126295 util-scheduler-8620 DEBUG Checking readiness of task: 3339 / 0x46620a0
Jul 07 20:52:29-126488 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:29-126678 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:29-126882 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:29-127073 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:29-127265 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:29-127455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:29-127646 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:29-127844 util-scheduler-8620 DEBUG Running task: 3339 / 0x46620a0
Jul 07 20:52:29-128032 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:29-128211 util-8620 DEBUG process_notify is running
Jul 07 20:52:29-128382 util-8620 DEBUG client_notify is running
Jul 07 20:52:29-128572 util-scheduler-8620 DEBUG Canceling task: 3336 / 0x59ee8a0
Jul 07 20:52:29-128801 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:29-129024 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:29-129288 cadet-p2p-8620 DEBUG Checking 0x5a90338 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:29-129526 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:29-129706 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:29-129897 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:29-130186 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:29-130384 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:29-130565 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:29-130754 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:29-130942 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:29-131120 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:29-131305 util-scheduler-8620 DEBUG Canceling task: 3333 / 0x59e8808
Jul 07 20:52:29-131519 util-scheduler-8620 DEBUG Adding task: 3341 / 0x59e8808
Jul 07 20:52:29-131769 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:29-131940 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:29-132120 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:29-132322 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:29-132497 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:29-132672 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:29-132870 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:29-133075 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:29-133282 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:29-133463 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:29-133654 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:29-133904 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:30-131168 util-scheduler-8620 DEBUG Checking readiness of task: 3340 / 0x46620a0
Jul 07 20:52:30-131492 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:30-132095 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:30-132328 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:30-132564 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:30-132758 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:30-132948 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:30-133139 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:30-133354 util-scheduler-8620 DEBUG Running task: 3335 / 0x52cbfb8
Jul 07 20:52:30-133585 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:30-134064 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:30-134277 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:30-134482 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:30-134686 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:30-134921 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:30-135102 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:30-135324 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:30-135611 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:30-135809 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:30-136047 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:30-136255 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:30-136572 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:30-136773 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:30-136998 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:30-137182 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:30-137378 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:30-137584 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:30-137799 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:30-138022 util-scheduler-8620 DEBUG Adding task: 3342 / 0x59ee8a0
Jul 07 20:52:30-138201 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:30-138403 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:30-138581 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:30-138755 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:30-138994 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:30-139189 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:30-139366 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:30-139564 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:30-139807 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:30-140004 util-scheduler-8620 DEBUG Adding task: 3343 / 0x52cbfb8
Jul 07 20:52:30-140257 util-scheduler-8620 DEBUG Checking readiness of task: 3340 / 0x46620a0
Jul 07 20:52:30-140449 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:30-140639 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:30-140829 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:30-141019 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:30-141227 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:30-141419 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:30-141607 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:30-141797 util-scheduler-8620 DEBUG Running task: 3342 / 0x59ee8a0
Jul 07 20:52:30-142030 util-scheduler-8620 DEBUG Adding task: 3344 / 0x59ee8a0
Jul 07 20:52:30-142254 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:30-142455 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:30-142662 util-scheduler-8620 DEBUG Adding task: 3345 / 0x46620a0
Jul 07 20:52:30-142904 util-scheduler-8620 DEBUG Checking readiness of task: 3345 / 0x46620a0
Jul 07 20:52:30-143097 util-scheduler-8620 DEBUG Checking readiness of task: 3340 / 0x46620a0
Jul 07 20:52:30-143287 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:30-143477 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:30-143667 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:30-143857 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:30-144066 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:30-144271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:30-144465 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:30-144656 util-scheduler-8620 DEBUG Running task: 3345 / 0x46620a0
Jul 07 20:52:30-144840 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:30-145018 util-8620 DEBUG process_notify is running
Jul 07 20:52:30-145214 util-8620 DEBUG client_notify is running
Jul 07 20:52:30-145397 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:30-145591 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:30-145794 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:30-146045 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:32-460257 util-scheduler-8620 DEBUG Checking readiness of task: 3340 / 0x46620a0
Jul 07 20:52:32-460616 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:32-460813 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:32-461005 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:32-461225 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:32-461421 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:32-461615 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:32-461805 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:32-462000 util-scheduler-8620 DEBUG Running task: 3340 / 0x46620a0
Jul 07 20:52:32-462418 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:32-462672 util-scheduler-8620 DEBUG Adding task: 3346 / 0x4662248
Jul 07 20:52:32-462948 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:32-463145 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:32-463336 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:32-463526 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:32-463716 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:32-463906 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:32-464096 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:32-464286 util-scheduler-8620 DEBUG Running task: 3346 / 0x4662248
Jul 07 20:52:32-464479 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:32-464678 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:32-464909 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:32-465114 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:32-465372 util-scheduler-8620 DEBUG Adding task: 3347 / 0x46620a0
Jul 07 20:52:32-465559 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:32-465766 util-scheduler-8620 DEBUG Adding task: 3348 / 0x46620a0
Jul 07 20:52:32-466009 util-scheduler-8620 DEBUG Checking readiness of task: 3348 / 0x46620a0
Jul 07 20:52:32-466202 util-scheduler-8620 DEBUG Checking readiness of task: 3347 / 0x46620a0
Jul 07 20:52:32-466395 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:32-466585 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:32-466777 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:32-466966 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:32-467157 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:32-467345 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:32-467535 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:32-467726 util-scheduler-8620 DEBUG Running task: 3347 / 0x46620a0
Jul 07 20:52:32-467912 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:32-468090 util-8620 DEBUG process_notify is running
Jul 07 20:52:32-468261 util-8620 DEBUG client_notify is running
Jul 07 20:52:32-468449 util-scheduler-8620 DEBUG Canceling task: 3344 / 0x59ee8a0
Jul 07 20:52:32-468676 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:32-468895 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:32-469132 cadet-p2p-8620 DEBUG Checking 0x5a92fc8 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:32-469391 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:32-469569 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:32-469759 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:32-470044 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:32-470240 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:32-470419 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:32-470606 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:32-470794 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:32-470972 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:32-471155 util-scheduler-8620 DEBUG Canceling task: 3341 / 0x59e8808
Jul 07 20:52:32-471367 util-scheduler-8620 DEBUG Adding task: 3349 / 0x59e8808
Jul 07 20:52:32-471616 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:32-471786 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:32-471967 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:32-472167 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:32-472343 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:32-472516 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:32-472715 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:32-472920 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:32-473105 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:32-473306 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:32-473497 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:32-473745 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:35-142822 util-scheduler-8620 DEBUG Checking readiness of task: 3348 / 0x46620a0
Jul 07 20:52:35-143187 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:35-143752 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:35-143984 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:35-144220 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:35-144414 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:35-144631 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:35-144822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:35-145018 util-scheduler-8620 DEBUG Running task: 3343 / 0x52cbfb8
Jul 07 20:52:35-145275 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:35-145531 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:35-145739 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:35-145940 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:35-146143 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:35-146377 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:35-146557 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:35-146780 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:35-147078 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:35-147276 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:35-147513 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:35-147721 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:35-148038 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:35-148239 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:35-148463 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:35-148647 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:35-148823 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:35-149029 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:35-149277 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:35-149507 util-scheduler-8620 DEBUG Adding task: 3350 / 0x59ee8a0
Jul 07 20:52:35-149689 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:35-149896 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:35-150074 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:35-150250 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:35-150489 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:35-150697 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:35-150875 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:35-151072 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:35-151316 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:35-151513 util-scheduler-8620 DEBUG Adding task: 3351 / 0x52cbfb8
Jul 07 20:52:35-151770 util-scheduler-8620 DEBUG Checking readiness of task: 3348 / 0x46620a0
Jul 07 20:52:35-151964 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:35-152154 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:35-152344 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:35-152533 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:35-152723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:35-152911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:35-153099 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:35-153312 util-scheduler-8620 DEBUG Running task: 3350 / 0x59ee8a0
Jul 07 20:52:35-153523 util-scheduler-8620 DEBUG Adding task: 3352 / 0x59ee8a0
Jul 07 20:52:35-153746 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:35-153950 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:35-154158 util-scheduler-8620 DEBUG Adding task: 3353 / 0x46620a0
Jul 07 20:52:35-154403 util-scheduler-8620 DEBUG Checking readiness of task: 3353 / 0x46620a0
Jul 07 20:52:35-154596 util-scheduler-8620 DEBUG Checking readiness of task: 3348 / 0x46620a0
Jul 07 20:52:35-154786 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:35-154976 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:35-155185 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:35-155375 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:35-155566 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:35-155758 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:35-155948 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:35-156139 util-scheduler-8620 DEBUG Running task: 3353 / 0x46620a0
Jul 07 20:52:35-156325 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:35-156503 util-8620 DEBUG process_notify is running
Jul 07 20:52:35-156676 util-8620 DEBUG client_notify is running
Jul 07 20:52:35-156855 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:35-157049 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:35-157259 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:35-157512 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:36-498932 util-scheduler-8620 DEBUG Checking readiness of task: 3348 / 0x46620a0
Jul 07 20:52:36-499264 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:36-499460 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:36-499652 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:36-499842 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:36-500034 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:36-500228 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:36-500427 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:36-500621 util-scheduler-8620 DEBUG Running task: 3348 / 0x46620a0
Jul 07 20:52:36-501037 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:36-501331 util-scheduler-8620 DEBUG Adding task: 3354 / 0x4662248
Jul 07 20:52:36-501603 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:36-501797 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:36-501988 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:36-502178 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:36-502368 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:36-502557 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:36-502747 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:36-502935 util-scheduler-8620 DEBUG Running task: 3354 / 0x4662248
Jul 07 20:52:36-503126 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:36-503325 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:36-503553 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:36-503759 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:36-503964 util-scheduler-8620 DEBUG Adding task: 3355 / 0x46620a0
Jul 07 20:52:36-504150 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:36-504356 util-scheduler-8620 DEBUG Adding task: 3356 / 0x46620a0
Jul 07 20:52:36-504598 util-scheduler-8620 DEBUG Checking readiness of task: 3356 / 0x46620a0
Jul 07 20:52:36-504792 util-scheduler-8620 DEBUG Checking readiness of task: 3355 / 0x46620a0
Jul 07 20:52:36-504984 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:36-505175 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:36-505387 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:36-505603 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:36-505793 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:36-505984 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:36-506174 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:36-506364 util-scheduler-8620 DEBUG Running task: 3355 / 0x46620a0
Jul 07 20:52:36-506550 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:36-506728 util-8620 DEBUG process_notify is running
Jul 07 20:52:36-506898 util-8620 DEBUG client_notify is running
Jul 07 20:52:36-507084 util-scheduler-8620 DEBUG Canceling task: 3352 / 0x59ee8a0
Jul 07 20:52:36-507307 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:36-507526 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:36-507763 cadet-p2p-8620 DEBUG Checking 0x5a95c80 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:36-507996 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:36-508175 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:36-508364 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:36-508650 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:36-508847 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:36-509026 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:36-509234 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:36-509423 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:36-509601 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:36-509784 util-scheduler-8620 DEBUG Canceling task: 3349 / 0x59e8808
Jul 07 20:52:36-509995 util-scheduler-8620 DEBUG Adding task: 3357 / 0x59e8808
Jul 07 20:52:36-510244 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:36-510415 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:36-510594 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:36-510795 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:36-510970 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:36-511144 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:36-511343 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:36-511546 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:36-511730 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:36-511907 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:36-512097 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:36-512344 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:40-155305 util-scheduler-8620 DEBUG Checking readiness of task: 3356 / 0x46620a0
Jul 07 20:52:40-155665 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-156243 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-156440 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-156685 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-156908 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-157098 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-157311 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-157504 util-scheduler-8620 DEBUG Running task: 3351 / 0x52cbfb8
Jul 07 20:52:40-157738 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:40-157994 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:40-158200 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:40-158401 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:40-158602 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:40-158836 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:40-159041 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:40-159263 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:40-159553 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:40-159750 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:40-159986 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:40-160194 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:40-160510 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:40-160711 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:40-160935 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:40-161119 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:40-161316 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:40-161524 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:40-161738 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:40-161961 util-scheduler-8620 DEBUG Adding task: 3358 / 0x59ee8a0
Jul 07 20:52:40-162142 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:40-162345 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:40-162522 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:40-162697 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:40-162934 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:40-163131 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:40-163308 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:40-163506 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:40-163749 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:40-163946 util-scheduler-8620 DEBUG Adding task: 3359 / 0x52cbfb8
Jul 07 20:52:40-164201 util-scheduler-8620 DEBUG Checking readiness of task: 3356 / 0x46620a0
Jul 07 20:52:40-164394 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-164584 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-164774 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-164964 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-165153 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-165364 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-165553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-165742 util-scheduler-8620 DEBUG Running task: 3358 / 0x59ee8a0
Jul 07 20:52:40-165950 util-scheduler-8620 DEBUG Adding task: 3360 / 0x59ee8a0
Jul 07 20:52:40-166171 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:40-166374 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:40-166580 util-scheduler-8620 DEBUG Adding task: 3361 / 0x46620a0
Jul 07 20:52:40-166825 util-scheduler-8620 DEBUG Checking readiness of task: 3361 / 0x46620a0
Jul 07 20:52:40-167020 util-scheduler-8620 DEBUG Checking readiness of task: 3356 / 0x46620a0
Jul 07 20:52:40-167210 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-167400 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-167589 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-167779 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-167968 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-168157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-168346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-168536 util-scheduler-8620 DEBUG Running task: 3361 / 0x46620a0
Jul 07 20:52:40-168721 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:40-168915 util-8620 DEBUG process_notify is running
Jul 07 20:52:40-169090 util-8620 DEBUG client_notify is running
Jul 07 20:52:40-169287 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:40-169484 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:40-169675 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:40-169928 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:40-170176 util-scheduler-8620 DEBUG Checking readiness of task: 3356 / 0x46620a0
Jul 07 20:52:40-170370 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-170559 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-170749 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-170939 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-171129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-171316 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-171505 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-171694 util-scheduler-8620 DEBUG Running task: 3356 / 0x46620a0
Jul 07 20:52:40-172098 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:40-172327 util-scheduler-8620 DEBUG Adding task: 3362 / 0x4662248
Jul 07 20:52:40-172575 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-172768 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-172958 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-173147 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-173360 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-173549 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-173739 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-173927 util-scheduler-8620 DEBUG Running task: 3362 / 0x4662248
Jul 07 20:52:40-174117 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:40-174313 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:40-174529 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:40-174725 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:40-174923 util-scheduler-8620 DEBUG Adding task: 3363 / 0x46620a0
Jul 07 20:52:40-175108 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:40-175310 util-scheduler-8620 DEBUG Adding task: 3364 / 0x46620a0
Jul 07 20:52:40-175551 util-scheduler-8620 DEBUG Checking readiness of task: 3364 / 0x46620a0
Jul 07 20:52:40-175743 util-scheduler-8620 DEBUG Checking readiness of task: 3363 / 0x46620a0
Jul 07 20:52:40-175934 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:40-176123 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:40-176329 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:40-176521 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:40-176714 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:40-176906 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:40-177097 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:40-177306 util-scheduler-8620 DEBUG Running task: 3363 / 0x46620a0
Jul 07 20:52:40-177492 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:40-177667 util-8620 DEBUG process_notify is running
Jul 07 20:52:40-177837 util-8620 DEBUG client_notify is running
Jul 07 20:52:40-178049 util-scheduler-8620 DEBUG Canceling task: 3360 / 0x59ee8a0
Jul 07 20:52:40-178274 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:40-178490 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:40-178720 cadet-p2p-8620 DEBUG Checking 0x5a98918 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:40-178954 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:40-179132 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:40-179317 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:40-179600 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:40-179795 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:40-179973 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:40-180162 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:40-180350 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:40-180527 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:40-180711 util-scheduler-8620 DEBUG Canceling task: 3357 / 0x59e8808
Jul 07 20:52:40-180920 util-scheduler-8620 DEBUG Adding task: 3365 / 0x59e8808
Jul 07 20:52:40-181163 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:40-181353 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:40-181534 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:40-181734 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:40-181909 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:40-182084 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:40-182281 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:40-182485 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:40-182667 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:40-182845 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:40-183033 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:40-183276 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:45-169091 util-scheduler-8620 DEBUG Checking readiness of task: 3364 / 0x46620a0
Jul 07 20:52:45-169503 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-170096 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-170323 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-170555 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-170749 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-170940 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-171129 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-171322 util-scheduler-8620 DEBUG Running task: 3359 / 0x52cbfb8
Jul 07 20:52:45-171559 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:45-171817 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:45-172023 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:45-172224 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:45-172426 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:45-172661 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:45-172860 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:45-173083 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:45-173398 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:45-173596 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:45-173832 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:45-174042 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:45-174360 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:45-174589 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:45-174818 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:45-175002 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:45-175178 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:45-175385 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:45-175600 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:45-175825 util-scheduler-8620 DEBUG Adding task: 3366 / 0x59ee8a0
Jul 07 20:52:45-176004 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:45-176208 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:45-176385 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:45-176560 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:45-176798 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:45-176994 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:45-177171 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:45-177391 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:45-177636 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:45-177832 util-scheduler-8620 DEBUG Adding task: 3367 / 0x52cbfb8
Jul 07 20:52:45-178093 util-scheduler-8620 DEBUG Checking readiness of task: 3364 / 0x46620a0
Jul 07 20:52:45-178285 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-178476 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-178665 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-178855 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-179045 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-179235 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-179424 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-179612 util-scheduler-8620 DEBUG Running task: 3366 / 0x59ee8a0
Jul 07 20:52:45-179821 util-scheduler-8620 DEBUG Adding task: 3368 / 0x59ee8a0
Jul 07 20:52:45-180043 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:45-180247 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:45-180455 util-scheduler-8620 DEBUG Adding task: 3369 / 0x46620a0
Jul 07 20:52:45-180698 util-scheduler-8620 DEBUG Checking readiness of task: 3369 / 0x46620a0
Jul 07 20:52:45-180893 util-scheduler-8620 DEBUG Checking readiness of task: 3364 / 0x46620a0
Jul 07 20:52:45-181084 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-181293 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-181483 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-181675 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-181864 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-182052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-182240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-182433 util-scheduler-8620 DEBUG Running task: 3369 / 0x46620a0
Jul 07 20:52:45-182617 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:45-182797 util-8620 DEBUG process_notify is running
Jul 07 20:52:45-182969 util-8620 DEBUG client_notify is running
Jul 07 20:52:45-183148 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:45-183343 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:45-183534 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:45-183789 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:45-184038 util-scheduler-8620 DEBUG Checking readiness of task: 3364 / 0x46620a0
Jul 07 20:52:45-184248 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-184438 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-184628 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-184816 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-185005 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-185211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-185415 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-185606 util-scheduler-8620 DEBUG Running task: 3364 / 0x46620a0
Jul 07 20:52:45-186009 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:45-186240 util-scheduler-8620 DEBUG Adding task: 3370 / 0x4662248
Jul 07 20:52:45-186487 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-186680 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-186870 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-187059 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-187250 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-187438 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-187626 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-187815 util-scheduler-8620 DEBUG Running task: 3370 / 0x4662248
Jul 07 20:52:45-188009 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:45-188206 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:45-188490 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:45-188757 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:45-188959 util-scheduler-8620 DEBUG Adding task: 3371 / 0x46620a0
Jul 07 20:52:45-189144 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:45-189369 util-scheduler-8620 DEBUG Adding task: 3372 / 0x46620a0
Jul 07 20:52:45-189612 util-scheduler-8620 DEBUG Checking readiness of task: 3372 / 0x46620a0
Jul 07 20:52:45-189806 util-scheduler-8620 DEBUG Checking readiness of task: 3371 / 0x46620a0
Jul 07 20:52:45-189999 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:45-190187 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:45-190378 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:45-190567 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:45-190757 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:45-190945 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:45-191134 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:45-191323 util-scheduler-8620 DEBUG Running task: 3371 / 0x46620a0
Jul 07 20:52:45-191507 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:45-191682 util-8620 DEBUG process_notify is running
Jul 07 20:52:45-191852 util-8620 DEBUG client_notify is running
Jul 07 20:52:45-192037 util-scheduler-8620 DEBUG Canceling task: 3368 / 0x59ee8a0
Jul 07 20:52:45-192261 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:45-192478 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:45-192709 cadet-p2p-8620 DEBUG Checking 0x5a9b430 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:45-192943 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:45-193121 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:45-193328 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:45-193611 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:45-193825 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:45-194007 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:45-194196 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:45-194384 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:45-194562 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:45-194746 util-scheduler-8620 DEBUG Canceling task: 3365 / 0x59e8808
Jul 07 20:52:45-194958 util-scheduler-8620 DEBUG Adding task: 3373 / 0x59e8808
Jul 07 20:52:45-195201 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:45-195372 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:45-195551 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:45-195752 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:45-195927 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:45-196144 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:45-196344 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:45-196549 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:45-196732 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:45-196910 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:45-197099 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:45-197363 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:50-182970 util-scheduler-8620 DEBUG Checking readiness of task: 3372 / 0x46620a0
Jul 07 20:52:50-183349 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-184201 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-184411 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-184608 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-184801 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-184993 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-185182 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-185398 util-scheduler-8620 DEBUG Running task: 3367 / 0x52cbfb8
Jul 07 20:52:50-185633 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:50-185889 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:50-186094 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:50-186294 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:50-186497 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:50-186730 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:50-186911 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:50-187132 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:50-187422 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:50-187617 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:50-187854 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:50-188064 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:50-188382 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:50-188584 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:50-188808 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:50-188991 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:50-189166 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:50-189398 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:50-189614 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:50-189837 util-scheduler-8620 DEBUG Adding task: 3374 / 0x59ee8a0
Jul 07 20:52:50-190018 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:50-190221 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:50-190426 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:50-190603 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:50-190841 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:50-191038 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:50-191215 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:50-191413 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:50-191657 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:50-191855 util-scheduler-8620 DEBUG Adding task: 3375 / 0x52cbfb8
Jul 07 20:52:50-192109 util-scheduler-8620 DEBUG Checking readiness of task: 3372 / 0x46620a0
Jul 07 20:52:50-192302 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-192492 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-192681 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-192882 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-193075 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-193286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-193475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-193666 util-scheduler-8620 DEBUG Running task: 3374 / 0x59ee8a0
Jul 07 20:52:50-193872 util-scheduler-8620 DEBUG Adding task: 3376 / 0x59ee8a0
Jul 07 20:52:50-194095 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:50-194298 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:50-194506 util-scheduler-8620 DEBUG Adding task: 3377 / 0x46620a0
Jul 07 20:52:50-194749 util-scheduler-8620 DEBUG Checking readiness of task: 3377 / 0x46620a0
Jul 07 20:52:50-194945 util-scheduler-8620 DEBUG Checking readiness of task: 3372 / 0x46620a0
Jul 07 20:52:50-195135 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-195325 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-195514 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-195704 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-195895 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-196083 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-196272 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-196462 util-scheduler-8620 DEBUG Running task: 3377 / 0x46620a0
Jul 07 20:52:50-196648 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:50-196826 util-8620 DEBUG process_notify is running
Jul 07 20:52:50-196998 util-8620 DEBUG client_notify is running
Jul 07 20:52:50-197176 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:50-197396 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:50-197587 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:50-197840 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:50-729365 util-scheduler-8620 DEBUG Checking readiness of task: 3372 / 0x46620a0
Jul 07 20:52:50-729615 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-729809 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-730001 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-730192 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-730382 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-730574 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-730766 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-730979 util-scheduler-8620 DEBUG Running task: 3372 / 0x46620a0
Jul 07 20:52:50-731390 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:50-731630 util-scheduler-8620 DEBUG Adding task: 3378 / 0x4662248
Jul 07 20:52:50-731889 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-732083 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-732274 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-732464 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-732655 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-732843 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-733032 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-733257 util-scheduler-8620 DEBUG Running task: 3378 / 0x4662248
Jul 07 20:52:50-733451 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:50-733648 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:50-733872 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:50-734072 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:50-734272 util-scheduler-8620 DEBUG Adding task: 3379 / 0x46620a0
Jul 07 20:52:50-734457 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:50-734662 util-scheduler-8620 DEBUG Adding task: 3380 / 0x46620a0
Jul 07 20:52:50-734904 util-scheduler-8620 DEBUG Checking readiness of task: 3380 / 0x46620a0
Jul 07 20:52:50-735096 util-scheduler-8620 DEBUG Checking readiness of task: 3379 / 0x46620a0
Jul 07 20:52:50-735288 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:50-735478 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:50-735667 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:50-735857 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:50-736046 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:50-736236 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:50-736424 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:50-736616 util-scheduler-8620 DEBUG Running task: 3379 / 0x46620a0
Jul 07 20:52:50-736800 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:50-736979 util-8620 DEBUG process_notify is running
Jul 07 20:52:50-737149 util-8620 DEBUG client_notify is running
Jul 07 20:52:50-737361 util-scheduler-8620 DEBUG Canceling task: 3376 / 0x59ee8a0
Jul 07 20:52:50-737586 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:50-737804 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:50-738039 cadet-p2p-8620 DEBUG Checking 0x5a9e1e0 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:50-738272 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:50-738450 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:50-738638 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:50-738922 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:50-739117 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:50-739296 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:50-739483 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:50-739672 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:50-739850 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:50-740032 util-scheduler-8620 DEBUG Canceling task: 3373 / 0x59e8808
Jul 07 20:52:50-740243 util-scheduler-8620 DEBUG Adding task: 3381 / 0x59e8808
Jul 07 20:52:50-740489 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:50-740660 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:50-740857 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:50-741059 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:50-741257 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:50-741432 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:50-741631 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:50-741837 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:50-742021 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:50-742199 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:50-742388 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:50-742634 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:55-196473 util-scheduler-8620 DEBUG Checking readiness of task: 3380 / 0x46620a0
Jul 07 20:52:55-196861 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:55-197612 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:55-198065 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:55-198266 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:55-198461 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:55-198651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:55-198842 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:55-199036 util-scheduler-8620 DEBUG Running task: 3375 / 0x52cbfb8
Jul 07 20:52:55-199277 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:52:55-199536 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:52:55-199742 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:52:55-199944 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:52:55-200153 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:52:55-200403 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:52:55-200584 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:52:55-200805 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:52:55-201099 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:52:55-201322 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:52:55-201560 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:52:55-201770 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:52:55-202089 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:52:55-202291 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:52:55-202515 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:52:55-202699 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:52:55-202876 cadet-con-8620 DEBUG  sendable
Jul 07 20:52:55-203082 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:52:55-203297 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:52:55-203524 util-scheduler-8620 DEBUG Adding task: 3382 / 0x59ee8a0
Jul 07 20:52:55-203704 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:52:55-203909 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:55-204086 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:52:55-204262 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:52:55-204501 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:52:55-204697 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:52:55-204874 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:52:55-205073 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:55-205339 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:52:55-205536 util-scheduler-8620 DEBUG Adding task: 3383 / 0x52cbfb8
Jul 07 20:52:55-205840 util-scheduler-8620 DEBUG Checking readiness of task: 3380 / 0x46620a0
Jul 07 20:52:55-206034 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:55-206224 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:55-206414 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:55-206606 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:55-206796 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:55-206984 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:55-207172 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:55-207363 util-scheduler-8620 DEBUG Running task: 3382 / 0x59ee8a0
Jul 07 20:52:55-207570 util-scheduler-8620 DEBUG Adding task: 3384 / 0x59ee8a0
Jul 07 20:52:55-207794 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:52:55-207998 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:55-208206 util-scheduler-8620 DEBUG Adding task: 3385 / 0x46620a0
Jul 07 20:52:55-208451 util-scheduler-8620 DEBUG Checking readiness of task: 3385 / 0x46620a0
Jul 07 20:52:55-208645 util-scheduler-8620 DEBUG Checking readiness of task: 3380 / 0x46620a0
Jul 07 20:52:55-208835 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:55-209025 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:55-209234 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:55-209427 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:55-209617 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:55-209806 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:55-209994 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:55-210187 util-scheduler-8620 DEBUG Running task: 3385 / 0x46620a0
Jul 07 20:52:55-210371 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:55-210550 util-8620 DEBUG process_notify is running
Jul 07 20:52:55-210723 util-8620 DEBUG client_notify is running
Jul 07 20:52:55-210902 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:52:55-211099 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:55-211290 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:52:55-211548 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:52:56-698227 util-scheduler-8620 DEBUG Checking readiness of task: 3380 / 0x46620a0
Jul 07 20:52:56-698576 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:56-698773 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:56-698966 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:56-699157 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:56-699351 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:56-699542 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:56-699743 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:56-699939 util-scheduler-8620 DEBUG Running task: 3380 / 0x46620a0
Jul 07 20:52:56-700361 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:52:56-700615 util-scheduler-8620 DEBUG Adding task: 3386 / 0x4662248
Jul 07 20:52:56-700893 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:56-701089 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:56-701307 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:56-701499 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:56-701720 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:56-701912 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:56-702101 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:56-702291 util-scheduler-8620 DEBUG Running task: 3386 / 0x4662248
Jul 07 20:52:56-702483 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:52:56-702682 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:52:56-702915 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:52:56-703121 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:52:56-703328 util-scheduler-8620 DEBUG Adding task: 3387 / 0x46620a0
Jul 07 20:52:56-703516 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:52:56-703722 util-scheduler-8620 DEBUG Adding task: 3388 / 0x46620a0
Jul 07 20:52:56-703967 util-scheduler-8620 DEBUG Checking readiness of task: 3388 / 0x46620a0
Jul 07 20:52:56-704160 util-scheduler-8620 DEBUG Checking readiness of task: 3387 / 0x46620a0
Jul 07 20:52:56-704352 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:52:56-704541 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:52:56-704731 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:52:56-704920 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:52:56-705111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:52:56-705321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:52:56-705511 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:52:56-705702 util-scheduler-8620 DEBUG Running task: 3387 / 0x46620a0
Jul 07 20:52:56-705888 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:52:56-706065 util-8620 DEBUG process_notify is running
Jul 07 20:52:56-706238 util-8620 DEBUG client_notify is running
Jul 07 20:52:56-706425 util-scheduler-8620 DEBUG Canceling task: 3384 / 0x59ee8a0
Jul 07 20:52:56-706649 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:52:56-706869 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:52:56-707109 cadet-p2p-8620 DEBUG Checking 0x5aa0df8 towards 2FDYFV0X (->V8XX)
Jul 07 20:52:56-707342 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:52:56-707520 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:52:56-707710 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:52:56-707995 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:52:56-708203 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:52:56-708383 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:52:56-708570 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:52:56-708758 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:52:56-708936 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:52:56-709119 util-scheduler-8620 DEBUG Canceling task: 3381 / 0x59e8808
Jul 07 20:52:56-709353 util-scheduler-8620 DEBUG Adding task: 3389 / 0x59e8808
Jul 07 20:52:56-709604 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:52:56-709775 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:52:56-709956 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:52:56-710157 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:52:56-710333 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:52:56-710507 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:52:56-710706 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:52:56-710913 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:52:56-711097 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:52:56-711277 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:52:56-711488 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:52:56-712236 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:00-205789 util-scheduler-8620 DEBUG Checking readiness of task: 3388 / 0x46620a0
Jul 07 20:53:00-206178 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:00-206651 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:00-206884 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:00-207121 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:00-207315 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:00-207507 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:00-207698 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:00-207891 util-scheduler-8620 DEBUG Running task: 3383 / 0x52cbfb8
Jul 07 20:53:00-208128 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:00-208388 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:53:00-208595 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:00-208795 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:00-208998 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:00-209256 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:00-209439 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:00-209661 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:00-209953 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:00-210150 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:00-210387 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:00-210595 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:00-210913 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:00-211115 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:00-211340 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:00-211525 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:00-211702 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:00-211909 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:00-212124 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:00-212348 util-scheduler-8620 DEBUG Adding task: 3390 / 0x59ee8a0
Jul 07 20:53:00-212533 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:00-212737 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:00-212914 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:00-213090 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:00-213348 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:00-213545 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:00-213723 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:00-213921 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:00-214166 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:00-214364 util-scheduler-8620 DEBUG Adding task: 3391 / 0x52cbfb8
Jul 07 20:53:00-214620 util-scheduler-8620 DEBUG Checking readiness of task: 3388 / 0x46620a0
Jul 07 20:53:00-214813 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:00-215003 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:00-215193 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:00-215382 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:00-215573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:00-215761 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:00-215975 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:00-216167 util-scheduler-8620 DEBUG Running task: 3390 / 0x59ee8a0
Jul 07 20:53:00-216375 util-scheduler-8620 DEBUG Adding task: 3392 / 0x59ee8a0
Jul 07 20:53:00-216598 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:00-216801 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:00-217008 util-scheduler-8620 DEBUG Adding task: 3393 / 0x46620a0
Jul 07 20:53:00-217272 util-scheduler-8620 DEBUG Checking readiness of task: 3393 / 0x46620a0
Jul 07 20:53:00-217467 util-scheduler-8620 DEBUG Checking readiness of task: 3388 / 0x46620a0
Jul 07 20:53:00-217658 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:00-217848 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:00-218038 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:00-218228 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:00-218418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:00-218607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:00-218796 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:00-218988 util-scheduler-8620 DEBUG Running task: 3393 / 0x46620a0
Jul 07 20:53:00-219174 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:00-219352 util-8620 DEBUG process_notify is running
Jul 07 20:53:00-219526 util-8620 DEBUG client_notify is running
Jul 07 20:53:00-219704 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:00-219899 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:00-220092 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:00-220345 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:02-733684 util-scheduler-8620 DEBUG Checking readiness of task: 3388 / 0x46620a0
Jul 07 20:53:02-734055 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:02-734254 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:02-734447 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:02-734641 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:02-734834 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:02-735030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:02-735229 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:02-735424 util-scheduler-8620 DEBUG Running task: 3388 / 0x46620a0
Jul 07 20:53:02-735844 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:02-736096 util-scheduler-8620 DEBUG Adding task: 3394 / 0x4662248
Jul 07 20:53:02-736372 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:02-736566 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:02-736757 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:02-736947 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:02-737149 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:02-737366 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:02-737556 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:02-737745 util-scheduler-8620 DEBUG Running task: 3394 / 0x4662248
Jul 07 20:53:02-737937 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:02-738135 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:02-738365 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:02-738604 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:02-738810 util-scheduler-8620 DEBUG Adding task: 3395 / 0x46620a0
Jul 07 20:53:02-738998 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:02-739203 util-scheduler-8620 DEBUG Adding task: 3396 / 0x46620a0
Jul 07 20:53:02-739447 util-scheduler-8620 DEBUG Checking readiness of task: 3396 / 0x46620a0
Jul 07 20:53:02-739639 util-scheduler-8620 DEBUG Checking readiness of task: 3395 / 0x46620a0
Jul 07 20:53:02-739831 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:02-740021 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:02-740210 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:02-740399 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:02-740591 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:02-740779 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:02-740967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:02-741158 util-scheduler-8620 DEBUG Running task: 3395 / 0x46620a0
Jul 07 20:53:02-741366 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:02-741543 util-8620 DEBUG process_notify is running
Jul 07 20:53:02-741715 util-8620 DEBUG client_notify is running
Jul 07 20:53:02-741903 util-scheduler-8620 DEBUG Canceling task: 3392 / 0x59ee8a0
Jul 07 20:53:02-742128 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:02-742351 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:02-742590 cadet-p2p-8620 DEBUG Checking 0x5aa3a50 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:02-742824 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:02-743001 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:02-743191 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:02-743475 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:02-743670 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:02-743848 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:02-744036 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:02-744223 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:02-744402 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:02-744584 util-scheduler-8620 DEBUG Canceling task: 3389 / 0x59e8808
Jul 07 20:53:02-744795 util-scheduler-8620 DEBUG Adding task: 3397 / 0x59e8808
Jul 07 20:53:02-745045 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:02-745233 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:02-745415 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:02-745616 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:02-745794 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:02-745972 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:02-746174 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:02-746382 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:02-746566 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:02-746746 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:02-746942 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:02-747680 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:05-216172 util-scheduler-8620 DEBUG Checking readiness of task: 3396 / 0x46620a0
Jul 07 20:53:05-216563 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-217171 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-217418 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-217652 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-217872 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-218065 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-218254 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-218448 util-scheduler-8620 DEBUG Running task: 3391 / 0x52cbfb8
Jul 07 20:53:05-218686 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:05-218943 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:53:05-219150 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:05-219351 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:05-219554 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:05-219791 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:05-219972 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:05-220192 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:05-220483 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:05-220681 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:05-220919 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:05-221128 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:05-221469 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:05-221671 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:05-221896 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:05-222080 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:05-222255 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:05-222461 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:05-222677 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:05-222906 util-scheduler-8620 DEBUG Adding task: 3398 / 0x59ee8a0
Jul 07 20:53:05-223088 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:05-223291 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:05-223469 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:05-223644 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:05-223882 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:05-224079 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:05-224255 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:05-224454 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:05-224698 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:05-224896 util-scheduler-8620 DEBUG Adding task: 3399 / 0x52cbfb8
Jul 07 20:53:05-225153 util-scheduler-8620 DEBUG Checking readiness of task: 3396 / 0x46620a0
Jul 07 20:53:05-225366 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-225556 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-225747 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-225936 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-226127 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-226315 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-226504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-226695 util-scheduler-8620 DEBUG Running task: 3398 / 0x59ee8a0
Jul 07 20:53:05-226902 util-scheduler-8620 DEBUG Adding task: 3400 / 0x59ee8a0
Jul 07 20:53:05-227125 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:05-227329 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:05-227537 util-scheduler-8620 DEBUG Adding task: 3401 / 0x46620a0
Jul 07 20:53:05-227793 util-scheduler-8620 DEBUG Checking readiness of task: 3401 / 0x46620a0
Jul 07 20:53:05-227989 util-scheduler-8620 DEBUG Checking readiness of task: 3396 / 0x46620a0
Jul 07 20:53:05-228243 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-228437 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-228630 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-228820 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-229009 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-229217 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-229408 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-229600 util-scheduler-8620 DEBUG Running task: 3401 / 0x46620a0
Jul 07 20:53:05-229786 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:05-229965 util-8620 DEBUG process_notify is running
Jul 07 20:53:05-230138 util-8620 DEBUG client_notify is running
Jul 07 20:53:05-230317 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:05-230515 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:05-230706 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:05-230959 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:05-777652 util-scheduler-8620 DEBUG Checking readiness of task: 3396 / 0x46620a0
Jul 07 20:53:05-777910 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-778109 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-778301 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-778496 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-778689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-778878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-779068 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-779261 util-scheduler-8620 DEBUG Running task: 3396 / 0x46620a0
Jul 07 20:53:05-779676 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:05-779921 util-scheduler-8620 DEBUG Adding task: 3402 / 0x4662248
Jul 07 20:53:05-780179 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-780374 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-780566 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-780756 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-780948 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-781136 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-781357 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-781547 util-scheduler-8620 DEBUG Running task: 3402 / 0x4662248
Jul 07 20:53:05-781739 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:05-781937 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:05-782159 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:05-782361 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:05-782563 util-scheduler-8620 DEBUG Adding task: 3403 / 0x46620a0
Jul 07 20:53:05-782750 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:05-782955 util-scheduler-8620 DEBUG Adding task: 3404 / 0x46620a0
Jul 07 20:53:05-783199 util-scheduler-8620 DEBUG Checking readiness of task: 3404 / 0x46620a0
Jul 07 20:53:05-783392 util-scheduler-8620 DEBUG Checking readiness of task: 3403 / 0x46620a0
Jul 07 20:53:05-783583 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:05-783774 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:05-783987 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:05-784179 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:05-784369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:05-784560 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:05-784749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:05-784940 util-scheduler-8620 DEBUG Running task: 3403 / 0x46620a0
Jul 07 20:53:05-785124 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:05-785325 util-8620 DEBUG process_notify is running
Jul 07 20:53:05-785496 util-8620 DEBUG client_notify is running
Jul 07 20:53:05-785683 util-scheduler-8620 DEBUG Canceling task: 3400 / 0x59ee8a0
Jul 07 20:53:05-785907 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:05-786126 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:05-786361 cadet-p2p-8620 DEBUG Checking 0x5aa66b0 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:05-786595 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:05-786774 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:05-786966 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:05-787250 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:05-787445 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:05-787624 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:05-787813 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:05-788001 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:05-788180 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:05-788363 util-scheduler-8620 DEBUG Canceling task: 3397 / 0x59e8808
Jul 07 20:53:05-788573 util-scheduler-8620 DEBUG Adding task: 3405 / 0x59e8808
Jul 07 20:53:05-788819 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:05-788989 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:05-789170 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:05-789394 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:05-789569 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:05-789744 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:05-789940 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:05-790144 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:05-790328 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:05-790506 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:05-790694 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:05-790940 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:10-225806 util-scheduler-8620 DEBUG Checking readiness of task: 3404 / 0x46620a0
Jul 07 20:53:10-226195 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:10-226765 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:10-226990 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:10-227226 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:10-227421 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:10-227612 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:10-227802 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:10-227996 util-scheduler-8620 DEBUG Running task: 3399 / 0x52cbfb8
Jul 07 20:53:10-228233 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:10-228489 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:53:10-228695 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:10-228896 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:10-229123 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:10-229380 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:10-229561 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:10-229782 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:10-230071 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:10-230267 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:10-230505 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:10-230714 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:10-231046 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:10-231248 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:10-231474 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:10-231658 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:10-231834 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:10-232039 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:10-232254 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:10-232479 util-scheduler-8620 DEBUG Adding task: 3406 / 0x59ee8a0
Jul 07 20:53:10-232659 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:10-232863 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:10-233042 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:10-233238 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:10-233480 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:10-233678 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:10-233854 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:10-234053 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:10-234298 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:10-234496 util-scheduler-8620 DEBUG Adding task: 3407 / 0x52cbfb8
Jul 07 20:53:10-234753 util-scheduler-8620 DEBUG Checking readiness of task: 3404 / 0x46620a0
Jul 07 20:53:10-234946 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:10-235136 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:10-235325 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:10-235514 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:10-235704 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:10-235892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:10-236081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:10-236270 util-scheduler-8620 DEBUG Running task: 3406 / 0x59ee8a0
Jul 07 20:53:10-236478 util-scheduler-8620 DEBUG Adding task: 3408 / 0x59ee8a0
Jul 07 20:53:10-236699 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:10-236902 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:10-237109 util-scheduler-8620 DEBUG Adding task: 3409 / 0x46620a0
Jul 07 20:53:10-237372 util-scheduler-8620 DEBUG Checking readiness of task: 3409 / 0x46620a0
Jul 07 20:53:10-237608 util-scheduler-8620 DEBUG Checking readiness of task: 3404 / 0x46620a0
Jul 07 20:53:10-237799 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:10-237991 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:10-238180 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:10-238370 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:10-238559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:10-238748 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:10-238936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:10-239145 util-scheduler-8620 DEBUG Running task: 3409 / 0x46620a0
Jul 07 20:53:10-239330 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:10-239509 util-8620 DEBUG process_notify is running
Jul 07 20:53:10-239681 util-8620 DEBUG client_notify is running
Jul 07 20:53:10-239861 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:10-240079 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:10-240271 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:10-240523 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:11-799885 util-scheduler-8620 DEBUG Checking readiness of task: 3404 / 0x46620a0
Jul 07 20:53:11-800196 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:11-800392 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:11-800589 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:11-800781 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:11-800983 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:11-801174 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:11-801398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:11-801598 util-scheduler-8620 DEBUG Running task: 3404 / 0x46620a0
Jul 07 20:53:11-802014 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:11-802261 util-scheduler-8620 DEBUG Adding task: 3410 / 0x4662248
Jul 07 20:53:11-802529 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:11-802721 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:11-802912 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:11-803103 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:11-803292 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:11-803481 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:11-803669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:11-803858 util-scheduler-8620 DEBUG Running task: 3410 / 0x4662248
Jul 07 20:53:11-804046 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:11-804245 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:11-804479 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:11-804694 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:11-804898 util-scheduler-8620 DEBUG Adding task: 3411 / 0x46620a0
Jul 07 20:53:11-805084 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:11-805310 util-scheduler-8620 DEBUG Adding task: 3412 / 0x46620a0
Jul 07 20:53:11-805554 util-scheduler-8620 DEBUG Checking readiness of task: 3412 / 0x46620a0
Jul 07 20:53:11-805752 util-scheduler-8620 DEBUG Checking readiness of task: 3411 / 0x46620a0
Jul 07 20:53:11-805950 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:11-806142 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:11-806331 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:11-806520 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:11-806709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:11-806897 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:11-807093 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:11-807290 util-scheduler-8620 DEBUG Running task: 3411 / 0x46620a0
Jul 07 20:53:11-807479 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:11-807693 util-8620 DEBUG process_notify is running
Jul 07 20:53:11-807870 util-8620 DEBUG client_notify is running
Jul 07 20:53:11-808060 util-scheduler-8620 DEBUG Canceling task: 3408 / 0x59ee8a0
Jul 07 20:53:11-808297 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:11-808520 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:11-808759 cadet-p2p-8620 DEBUG Checking 0x5aa9298 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:11-808995 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:11-809173 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:11-809427 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:11-809718 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:11-809914 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:11-810095 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:11-810284 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:11-810473 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:11-810652 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:11-810839 util-scheduler-8620 DEBUG Canceling task: 3405 / 0x59e8808
Jul 07 20:53:11-811057 util-scheduler-8620 DEBUG Adding task: 3413 / 0x59e8808
Jul 07 20:53:11-811306 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:11-811479 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:11-811673 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:11-811878 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:11-812055 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:11-812232 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:11-812431 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:11-812637 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:11-812821 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:11-813001 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:11-813214 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:11-813471 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:15-237377 util-scheduler-8620 DEBUG Checking readiness of task: 3412 / 0x46620a0
Jul 07 20:53:15-237784 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-238648 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-238857 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-239054 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-239246 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-239436 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-239626 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-239819 util-scheduler-8620 DEBUG Running task: 3407 / 0x52cbfb8
Jul 07 20:53:15-240058 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:15-240320 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:53:15-240532 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:15-240742 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:15-240953 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:15-241226 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:15-241419 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:15-241654 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:15-241960 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:15-242168 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:15-242417 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:15-242636 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:15-242963 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:15-243199 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:15-243426 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:15-243611 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:15-243785 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:15-243992 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:15-244206 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:15-244435 util-scheduler-8620 DEBUG Adding task: 3414 / 0x59ee8a0
Jul 07 20:53:15-244616 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:15-244820 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:15-244998 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:15-245172 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:15-245457 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:15-245652 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:15-245829 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:15-246026 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:15-246273 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:15-246470 util-scheduler-8620 DEBUG Adding task: 3415 / 0x52cbfb8
Jul 07 20:53:15-246734 util-scheduler-8620 DEBUG Checking readiness of task: 3412 / 0x46620a0
Jul 07 20:53:15-246927 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-247117 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-247305 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-247494 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-247682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-247870 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-248059 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-248248 util-scheduler-8620 DEBUG Running task: 3414 / 0x59ee8a0
Jul 07 20:53:15-248456 util-scheduler-8620 DEBUG Adding task: 3416 / 0x59ee8a0
Jul 07 20:53:15-248676 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:15-248879 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:15-249090 util-scheduler-8620 DEBUG Adding task: 3417 / 0x46620a0
Jul 07 20:53:15-249353 util-scheduler-8620 DEBUG Checking readiness of task: 3417 / 0x46620a0
Jul 07 20:53:15-249548 util-scheduler-8620 DEBUG Checking readiness of task: 3412 / 0x46620a0
Jul 07 20:53:15-249738 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-249927 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-250117 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-250305 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-250494 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-250682 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-250870 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-251060 util-scheduler-8620 DEBUG Running task: 3417 / 0x46620a0
Jul 07 20:53:15-251245 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:15-251422 util-8620 DEBUG process_notify is running
Jul 07 20:53:15-251594 util-8620 DEBUG client_notify is running
Jul 07 20:53:15-251772 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:15-251968 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:15-252158 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:15-252479 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:15-252745 util-scheduler-8620 DEBUG Checking readiness of task: 3412 / 0x46620a0
Jul 07 20:53:15-252939 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-253128 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-253341 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-253531 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-253723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-253914 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-254105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-254297 util-scheduler-8620 DEBUG Running task: 3412 / 0x46620a0
Jul 07 20:53:15-254710 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:15-254945 util-scheduler-8620 DEBUG Adding task: 3418 / 0x4662248
Jul 07 20:53:15-255196 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-255389 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-255578 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-255767 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-255957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-256145 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-256332 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-256520 util-scheduler-8620 DEBUG Running task: 3418 / 0x4662248
Jul 07 20:53:15-256710 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:15-256906 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:15-257123 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:15-257344 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:15-257544 util-scheduler-8620 DEBUG Adding task: 3419 / 0x46620a0
Jul 07 20:53:15-257740 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:15-257945 util-scheduler-8620 DEBUG Adding task: 3420 / 0x46620a0
Jul 07 20:53:15-258185 util-scheduler-8620 DEBUG Checking readiness of task: 3420 / 0x46620a0
Jul 07 20:53:15-258377 util-scheduler-8620 DEBUG Checking readiness of task: 3419 / 0x46620a0
Jul 07 20:53:15-258567 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:15-258756 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:15-258945 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:15-259136 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:15-259324 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:15-259512 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:15-259700 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:15-259889 util-scheduler-8620 DEBUG Running task: 3419 / 0x46620a0
Jul 07 20:53:15-260073 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:15-260247 util-8620 DEBUG process_notify is running
Jul 07 20:53:15-260416 util-8620 DEBUG client_notify is running
Jul 07 20:53:15-260600 util-scheduler-8620 DEBUG Canceling task: 3416 / 0x59ee8a0
Jul 07 20:53:15-260824 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:15-261040 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:15-261290 cadet-p2p-8620 DEBUG Checking 0x5aabf38 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:15-261524 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:15-261701 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:15-261887 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:15-262186 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:15-262380 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:15-262558 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:15-262745 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:15-262932 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:15-263109 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:15-263291 util-scheduler-8620 DEBUG Canceling task: 3413 / 0x59e8808
Jul 07 20:53:15-263500 util-scheduler-8620 DEBUG Adding task: 3421 / 0x59e8808
Jul 07 20:53:15-263743 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:15-263913 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:15-264092 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:15-264291 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:15-264465 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:15-265049 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:15-265272 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:15-265482 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:15-265668 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:15-265850 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:15-266048 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:15-267589 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:20-251644 util-scheduler-8620 DEBUG Checking readiness of task: 3420 / 0x46620a0
Jul 07 20:53:20-252065 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:20-252631 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:20-252829 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:20-253076 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:20-253305 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:20-253496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:20-253688 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:20-253881 util-scheduler-8620 DEBUG Running task: 3415 / 0x52cbfb8
Jul 07 20:53:20-254121 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:20-254379 cadet-tun-8620 DEBUG  kx started 5 m ago
Jul 07 20:53:20-254587 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:20-254789 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:20-254990 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:20-255226 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:20-255406 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:20-255627 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:20-255919 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:20-256118 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:20-256355 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:20-256563 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:20-256882 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:20-257082 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:20-257328 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:20-257511 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:20-257687 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:20-257893 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:20-258110 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:20-258334 util-scheduler-8620 DEBUG Adding task: 3422 / 0x59ee8a0
Jul 07 20:53:20-258543 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:20-258748 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:20-258925 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:20-259101 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:20-259339 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:20-259536 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:20-259714 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:20-259911 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:20-260157 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:20-260357 util-scheduler-8620 DEBUG Adding task: 3423 / 0x52cbfb8
Jul 07 20:53:20-260616 util-scheduler-8620 DEBUG Checking readiness of task: 3420 / 0x46620a0
Jul 07 20:53:20-260810 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:20-261001 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:20-261209 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:20-261401 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:20-261591 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:20-261780 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:20-261968 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:20-262159 util-scheduler-8620 DEBUG Running task: 3422 / 0x59ee8a0
Jul 07 20:53:20-262367 util-scheduler-8620 DEBUG Adding task: 3424 / 0x59ee8a0
Jul 07 20:53:20-262590 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:20-262794 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:20-263002 util-scheduler-8620 DEBUG Adding task: 3425 / 0x46620a0
Jul 07 20:53:20-263247 util-scheduler-8620 DEBUG Checking readiness of task: 3425 / 0x46620a0
Jul 07 20:53:20-263443 util-scheduler-8620 DEBUG Checking readiness of task: 3420 / 0x46620a0
Jul 07 20:53:20-263633 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:20-263824 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:20-264013 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:20-264204 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:20-264393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:20-264582 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:20-264771 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:20-264974 util-scheduler-8620 DEBUG Running task: 3425 / 0x46620a0
Jul 07 20:53:20-265160 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:20-265389 util-8620 DEBUG process_notify is running
Jul 07 20:53:20-265564 util-8620 DEBUG client_notify is running
Jul 07 20:53:20-265742 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:20-265938 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:20-266129 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:20-266384 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:21-072436 util-scheduler-8620 DEBUG Checking readiness of task: 3420 / 0x46620a0
Jul 07 20:53:21-072749 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:21-072948 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:21-073143 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:21-073381 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:21-073576 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:21-073773 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:21-073990 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:21-074187 util-scheduler-8620 DEBUG Running task: 3420 / 0x46620a0
Jul 07 20:53:21-074601 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:21-074853 util-scheduler-8620 DEBUG Adding task: 3426 / 0x4662248
Jul 07 20:53:21-075120 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:21-075315 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:21-075508 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:21-075700 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:21-075893 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:21-076084 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:21-076275 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:21-076466 util-scheduler-8620 DEBUG Running task: 3426 / 0x4662248
Jul 07 20:53:21-076662 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:21-076861 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:21-077091 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:21-077318 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:21-077524 util-scheduler-8620 DEBUG Adding task: 3427 / 0x46620a0
Jul 07 20:53:21-077714 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:21-077921 util-scheduler-8620 DEBUG Adding task: 3428 / 0x46620a0
Jul 07 20:53:21-078166 util-scheduler-8620 DEBUG Checking readiness of task: 3428 / 0x46620a0
Jul 07 20:53:21-078360 util-scheduler-8620 DEBUG Checking readiness of task: 3427 / 0x46620a0
Jul 07 20:53:21-078555 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:21-078746 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:21-078938 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:21-079130 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:21-079322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:21-079511 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:21-079703 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:21-079895 util-scheduler-8620 DEBUG Running task: 3427 / 0x46620a0
Jul 07 20:53:21-080082 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:21-080260 util-8620 DEBUG process_notify is running
Jul 07 20:53:21-080433 util-8620 DEBUG client_notify is running
Jul 07 20:53:21-080622 util-scheduler-8620 DEBUG Canceling task: 3424 / 0x59ee8a0
Jul 07 20:53:21-080849 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:21-081071 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:21-081333 cadet-p2p-8620 DEBUG Checking 0x5aae958 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:21-081570 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:21-081750 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:21-081942 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:21-082227 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:21-082425 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:21-082605 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:21-082796 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:21-082987 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:21-083167 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:21-083353 util-scheduler-8620 DEBUG Canceling task: 3421 / 0x59e8808
Jul 07 20:53:21-083566 util-scheduler-8620 DEBUG Adding task: 3429 / 0x59e8808
Jul 07 20:53:21-083835 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:21-084008 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:21-084191 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:21-084394 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:21-084570 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:21-084747 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:21-084947 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:21-085154 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:21-085364 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:21-085544 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:21-085737 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:21-085987 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:25-264700 util-scheduler-8620 DEBUG Checking readiness of task: 3428 / 0x46620a0
Jul 07 20:53:25-265092 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:25-265695 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:25-265928 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:25-266183 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:25-266378 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:25-266570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:25-266759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:25-266952 util-scheduler-8620 DEBUG Running task: 3423 / 0x52cbfb8
Jul 07 20:53:25-267191 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:25-267466 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:25-267676 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:25-267878 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:25-268080 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:25-268332 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:25-268514 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:25-268736 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:25-269026 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:25-269244 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:25-269501 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:25-269711 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:25-270030 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:25-270231 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:25-270472 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:25-270657 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:25-270833 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:25-271040 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:25-271254 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:25-271508 util-scheduler-8620 DEBUG Adding task: 3430 / 0x59ee8a0
Jul 07 20:53:25-271690 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:25-271895 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:25-272072 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:25-272247 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:25-272485 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:25-272699 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:25-272876 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:25-273074 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:25-273340 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:25-273564 util-scheduler-8620 DEBUG Adding task: 3431 / 0x52cbfb8
Jul 07 20:53:25-273844 util-scheduler-8620 DEBUG Checking readiness of task: 3428 / 0x46620a0
Jul 07 20:53:25-274038 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:25-274229 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:25-274419 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:25-274611 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:25-274818 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:25-275008 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:25-275197 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:25-275388 util-scheduler-8620 DEBUG Running task: 3430 / 0x59ee8a0
Jul 07 20:53:25-275596 util-scheduler-8620 DEBUG Adding task: 3432 / 0x59ee8a0
Jul 07 20:53:25-275835 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:25-276039 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:25-276248 util-scheduler-8620 DEBUG Adding task: 3433 / 0x46620a0
Jul 07 20:53:25-276490 util-scheduler-8620 DEBUG Checking readiness of task: 3433 / 0x46620a0
Jul 07 20:53:25-276686 util-scheduler-8620 DEBUG Checking readiness of task: 3428 / 0x46620a0
Jul 07 20:53:25-276895 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:25-277086 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:25-277296 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:25-277487 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:25-277680 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:25-277871 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:25-278076 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:25-278268 util-scheduler-8620 DEBUG Running task: 3433 / 0x46620a0
Jul 07 20:53:25-278452 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:25-278631 util-8620 DEBUG process_notify is running
Jul 07 20:53:25-278804 util-8620 DEBUG client_notify is running
Jul 07 20:53:25-278999 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:25-279195 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:25-279387 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:25-279644 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:27-089998 util-scheduler-8620 DEBUG Checking readiness of task: 3428 / 0x46620a0
Jul 07 20:53:27-090356 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:27-090555 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:27-090749 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:27-090944 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:27-091139 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:27-091343 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:27-091535 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:27-091733 util-scheduler-8620 DEBUG Running task: 3428 / 0x46620a0
Jul 07 20:53:27-092154 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:27-092407 util-scheduler-8620 DEBUG Adding task: 3434 / 0x4662248
Jul 07 20:53:27-092684 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:27-092879 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:27-093072 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:27-093322 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:27-093517 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:27-093708 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:27-093900 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:27-094092 util-scheduler-8620 DEBUG Running task: 3434 / 0x4662248
Jul 07 20:53:27-094284 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:27-094485 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:27-094717 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:27-094924 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:27-095132 util-scheduler-8620 DEBUG Adding task: 3435 / 0x46620a0
Jul 07 20:53:27-095320 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:27-095528 util-scheduler-8620 DEBUG Adding task: 3436 / 0x46620a0
Jul 07 20:53:27-095774 util-scheduler-8620 DEBUG Checking readiness of task: 3436 / 0x46620a0
Jul 07 20:53:27-095970 util-scheduler-8620 DEBUG Checking readiness of task: 3435 / 0x46620a0
Jul 07 20:53:27-096165 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:27-096357 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:27-096550 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:27-096742 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:27-096935 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:27-097125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:27-097338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:27-097532 util-scheduler-8620 DEBUG Running task: 3435 / 0x46620a0
Jul 07 20:53:27-097719 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:27-097899 util-8620 DEBUG process_notify is running
Jul 07 20:53:27-098075 util-8620 DEBUG client_notify is running
Jul 07 20:53:27-098265 util-scheduler-8620 DEBUG Canceling task: 3432 / 0x59ee8a0
Jul 07 20:53:27-098503 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:27-098727 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:27-098966 cadet-p2p-8620 DEBUG Checking 0x5ab1790 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:27-099203 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:27-099383 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:27-099575 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:27-099860 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:27-100058 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:27-100237 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:27-100425 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:27-100613 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:27-100791 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:27-100974 util-scheduler-8620 DEBUG Canceling task: 3429 / 0x59e8808
Jul 07 20:53:27-101185 util-scheduler-8620 DEBUG Adding task: 3437 / 0x59e8808
Jul 07 20:53:27-101455 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:27-101625 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:27-101806 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:27-102007 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:27-102182 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:27-102356 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:27-102554 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:27-102758 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:27-102941 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:27-103138 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:27-103330 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:27-103591 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:30-276903 util-scheduler-8620 DEBUG Checking readiness of task: 3436 / 0x46620a0
Jul 07 20:53:30-277317 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:30-277845 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:30-278045 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:30-278308 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:30-278521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:30-278713 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:30-278904 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:30-279098 util-scheduler-8620 DEBUG Running task: 3431 / 0x52cbfb8
Jul 07 20:53:30-279337 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:30-279596 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:30-279804 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:30-280007 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:30-280208 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:30-280445 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:30-280626 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:30-280847 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:30-281139 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:30-281365 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:30-281603 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:30-281811 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:30-282152 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:30-282365 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:30-282591 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:30-282776 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:30-282954 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:30-283161 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:30-283377 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:30-283604 util-scheduler-8620 DEBUG Adding task: 3438 / 0x59ee8a0
Jul 07 20:53:30-283785 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:30-283988 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:30-284166 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:30-284341 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:30-284579 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:30-284776 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:30-284953 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:30-285152 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:30-285420 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:30-285617 util-scheduler-8620 DEBUG Adding task: 3439 / 0x52cbfb8
Jul 07 20:53:30-285879 util-scheduler-8620 DEBUG Checking readiness of task: 3436 / 0x46620a0
Jul 07 20:53:30-286073 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:30-286263 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:30-286452 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:30-286642 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:30-286831 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:30-287054 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:30-287244 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:30-287434 util-scheduler-8620 DEBUG Running task: 3438 / 0x59ee8a0
Jul 07 20:53:30-287643 util-scheduler-8620 DEBUG Adding task: 3440 / 0x59ee8a0
Jul 07 20:53:30-287866 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:30-288070 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:30-288279 util-scheduler-8620 DEBUG Adding task: 3441 / 0x46620a0
Jul 07 20:53:30-288522 util-scheduler-8620 DEBUG Checking readiness of task: 3441 / 0x46620a0
Jul 07 20:53:30-288717 util-scheduler-8620 DEBUG Checking readiness of task: 3436 / 0x46620a0
Jul 07 20:53:30-288907 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:30-289097 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:30-289308 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:30-289498 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:30-289687 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:30-289876 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:30-290066 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:30-290256 util-scheduler-8620 DEBUG Running task: 3441 / 0x46620a0
Jul 07 20:53:30-290442 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:30-290620 util-8620 DEBUG process_notify is running
Jul 07 20:53:30-290793 util-8620 DEBUG client_notify is running
Jul 07 20:53:30-290971 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:30-291167 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:30-291358 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:30-291615 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:33-060161 util-scheduler-8620 DEBUG Checking readiness of task: 3436 / 0x46620a0
Jul 07 20:53:33-060546 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:33-060746 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:33-060940 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:33-061135 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:33-061367 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:33-061562 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:33-061754 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:33-061951 util-scheduler-8620 DEBUG Running task: 3436 / 0x46620a0
Jul 07 20:53:33-062373 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:33-062631 util-scheduler-8620 DEBUG Adding task: 3442 / 0x4662248
Jul 07 20:53:33-062910 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:33-063106 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:33-063301 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:33-063494 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:33-063688 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:33-063879 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:33-064070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:33-064261 util-scheduler-8620 DEBUG Running task: 3442 / 0x4662248
Jul 07 20:53:33-064454 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:33-064655 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:33-064919 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:33-065128 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:33-065365 util-scheduler-8620 DEBUG Adding task: 3443 / 0x46620a0
Jul 07 20:53:33-065555 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:33-065763 util-scheduler-8620 DEBUG Adding task: 3444 / 0x46620a0
Jul 07 20:53:33-066009 util-scheduler-8620 DEBUG Checking readiness of task: 3444 / 0x46620a0
Jul 07 20:53:33-066204 util-scheduler-8620 DEBUG Checking readiness of task: 3443 / 0x46620a0
Jul 07 20:53:33-066398 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:33-066590 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:33-066781 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:33-066973 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:33-067166 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:33-067369 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:33-067561 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:33-067753 util-scheduler-8620 DEBUG Running task: 3443 / 0x46620a0
Jul 07 20:53:33-067940 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:33-068121 util-8620 DEBUG process_notify is running
Jul 07 20:53:33-068294 util-8620 DEBUG client_notify is running
Jul 07 20:53:33-068483 util-scheduler-8620 DEBUG Canceling task: 3440 / 0x59ee8a0
Jul 07 20:53:33-068709 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:33-068931 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:33-069173 cadet-p2p-8620 DEBUG Checking 0x5ab4470 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:33-069455 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:33-069635 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:33-069827 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:33-070113 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:33-070310 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:33-070492 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:33-070681 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:33-070871 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:33-071053 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:33-071237 util-scheduler-8620 DEBUG Canceling task: 3437 / 0x59e8808
Jul 07 20:53:33-071452 util-scheduler-8620 DEBUG Adding task: 3445 / 0x59e8808
Jul 07 20:53:33-071705 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:33-071878 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:33-072060 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:33-072263 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:33-072440 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:33-072617 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:33-072816 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:33-073022 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:33-073234 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:33-073421 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:33-073615 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:33-073868 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:35-287977 util-scheduler-8620 DEBUG Checking readiness of task: 3444 / 0x46620a0
Jul 07 20:53:35-288337 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:35-288940 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:35-289171 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:35-289460 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:35-289655 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:35-289846 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:35-290037 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:35-290229 util-scheduler-8620 DEBUG Running task: 3439 / 0x52cbfb8
Jul 07 20:53:35-290463 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:35-290717 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:35-290923 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:35-291124 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:35-291325 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:35-291560 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:35-291741 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:35-291961 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:35-292250 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:35-292446 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:35-292683 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:35-292891 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:35-293230 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:35-293432 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:35-293657 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:35-293841 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:35-294018 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:35-294224 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:35-294438 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:35-294661 util-scheduler-8620 DEBUG Adding task: 3446 / 0x59ee8a0
Jul 07 20:53:35-294840 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:35-295042 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:35-295218 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:35-295392 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:35-295635 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:35-295831 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:35-296009 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:35-296206 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:35-296451 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:35-296649 util-scheduler-8620 DEBUG Adding task: 3447 / 0x52cbfb8
Jul 07 20:53:35-296906 util-scheduler-8620 DEBUG Checking readiness of task: 3444 / 0x46620a0
Jul 07 20:53:35-297101 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:35-297311 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:35-297502 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:35-297692 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:35-297881 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:35-298070 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:35-298258 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:35-298449 util-scheduler-8620 DEBUG Running task: 3446 / 0x59ee8a0
Jul 07 20:53:35-298657 util-scheduler-8620 DEBUG Adding task: 3448 / 0x59ee8a0
Jul 07 20:53:35-298878 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:35-299080 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:35-299287 util-scheduler-8620 DEBUG Adding task: 3449 / 0x46620a0
Jul 07 20:53:35-299529 util-scheduler-8620 DEBUG Checking readiness of task: 3449 / 0x46620a0
Jul 07 20:53:35-299740 util-scheduler-8620 DEBUG Checking readiness of task: 3444 / 0x46620a0
Jul 07 20:53:35-299932 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:35-300121 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:35-300312 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:35-300501 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:35-300691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:35-300880 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:35-301070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:35-301281 util-scheduler-8620 DEBUG Running task: 3449 / 0x46620a0
Jul 07 20:53:35-301468 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:35-301646 util-8620 DEBUG process_notify is running
Jul 07 20:53:35-301819 util-8620 DEBUG client_notify is running
Jul 07 20:53:35-301999 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:35-302193 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:35-302418 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:35-302672 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:36-056517 util-scheduler-8620 DEBUG Checking readiness of task: 3444 / 0x46620a0
Jul 07 20:53:36-056832 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:36-057031 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:36-057251 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:36-057448 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:36-057643 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:36-057839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:36-058031 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:36-058228 util-scheduler-8620 DEBUG Running task: 3444 / 0x46620a0
Jul 07 20:53:36-058642 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:36-058892 util-scheduler-8620 DEBUG Adding task: 3450 / 0x4662248
Jul 07 20:53:36-059161 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:36-059357 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:36-059550 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:36-059742 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:36-059934 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:36-060125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:36-060318 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:36-060510 util-scheduler-8620 DEBUG Running task: 3450 / 0x4662248
Jul 07 20:53:36-060702 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:36-060903 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:36-061131 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:36-061362 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:36-061568 util-scheduler-8620 DEBUG Adding task: 3451 / 0x46620a0
Jul 07 20:53:36-061757 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:36-061964 util-scheduler-8620 DEBUG Adding task: 3452 / 0x46620a0
Jul 07 20:53:36-062208 util-scheduler-8620 DEBUG Checking readiness of task: 3452 / 0x46620a0
Jul 07 20:53:36-062403 util-scheduler-8620 DEBUG Checking readiness of task: 3451 / 0x46620a0
Jul 07 20:53:36-062620 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:36-062813 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:36-063006 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:36-063197 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:36-063435 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:36-063635 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:36-063829 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:36-064025 util-scheduler-8620 DEBUG Running task: 3451 / 0x46620a0
Jul 07 20:53:36-064216 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:36-064396 util-8620 DEBUG process_notify is running
Jul 07 20:53:36-064571 util-8620 DEBUG client_notify is running
Jul 07 20:53:36-064760 util-scheduler-8620 DEBUG Canceling task: 3448 / 0x59ee8a0
Jul 07 20:53:36-064990 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:36-065255 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:36-065499 cadet-p2p-8620 DEBUG Checking 0x5ab7108 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:36-065736 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:36-065916 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:36-066109 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:36-066393 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:36-066590 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:36-066771 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:36-066960 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:36-067150 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:36-067330 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:36-067515 util-scheduler-8620 DEBUG Canceling task: 3445 / 0x59e8808
Jul 07 20:53:36-067728 util-scheduler-8620 DEBUG Adding task: 3453 / 0x59e8808
Jul 07 20:53:36-067979 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:36-068152 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:36-068335 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:36-068537 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:36-068715 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:36-068891 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:36-069092 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:36-069343 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:36-069530 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:36-069712 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:36-069903 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:36-100175 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:40-301011 util-scheduler-8620 DEBUG Checking readiness of task: 3452 / 0x46620a0
Jul 07 20:53:40-301425 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:40-302507 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:40-302977 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:40-303180 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:40-303374 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:40-303566 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:40-303774 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:40-303968 util-scheduler-8620 DEBUG Running task: 3447 / 0x52cbfb8
Jul 07 20:53:40-304207 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:40-304466 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:40-304708 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:40-304936 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:40-305140 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:40-305399 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:40-305582 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:40-305821 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:40-306115 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:40-306315 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:40-306552 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:40-306762 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:40-307097 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:40-307300 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:40-307525 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:40-307708 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:40-307885 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:40-308108 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:40-308343 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:40-308583 util-scheduler-8620 DEBUG Adding task: 3454 / 0x59ee8a0
Jul 07 20:53:40-308774 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:40-308979 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:40-309174 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:40-309373 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:40-309612 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:40-309809 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:40-309986 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:40-310203 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:40-310462 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:40-310661 util-scheduler-8620 DEBUG Adding task: 3455 / 0x52cbfb8
Jul 07 20:53:40-310929 util-scheduler-8620 DEBUG Checking readiness of task: 3452 / 0x46620a0
Jul 07 20:53:40-311121 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:40-311329 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:40-311519 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:40-311709 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:40-311899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:40-312088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:40-312293 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:40-312483 util-scheduler-8620 DEBUG Running task: 3454 / 0x59ee8a0
Jul 07 20:53:40-312692 util-scheduler-8620 DEBUG Adding task: 3456 / 0x59ee8a0
Jul 07 20:53:40-312913 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:40-313118 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:40-313362 util-scheduler-8620 DEBUG Adding task: 3457 / 0x46620a0
Jul 07 20:53:40-313609 util-scheduler-8620 DEBUG Checking readiness of task: 3457 / 0x46620a0
Jul 07 20:53:40-313805 util-scheduler-8620 DEBUG Checking readiness of task: 3452 / 0x46620a0
Jul 07 20:53:40-313996 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:40-314186 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:40-314391 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:40-314582 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:40-314772 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:40-314960 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:40-315167 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:40-315359 util-scheduler-8620 DEBUG Running task: 3457 / 0x46620a0
Jul 07 20:53:40-315565 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:40-315743 util-8620 DEBUG process_notify is running
Jul 07 20:53:40-315917 util-8620 DEBUG client_notify is running
Jul 07 20:53:40-316095 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:40-316292 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:40-316501 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:40-316762 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:42-100812 util-scheduler-8620 DEBUG Checking readiness of task: 3452 / 0x46620a0
Jul 07 20:53:42-101177 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:42-101427 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:42-101622 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:42-101815 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:42-102011 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:42-102210 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:42-102400 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:42-102595 util-scheduler-8620 DEBUG Running task: 3452 / 0x46620a0
Jul 07 20:53:42-103016 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:42-103273 util-scheduler-8620 DEBUG Adding task: 3458 / 0x4662248
Jul 07 20:53:42-103552 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:42-103745 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:42-103935 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:42-104124 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:42-104314 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:42-104503 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:42-104693 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:42-104882 util-scheduler-8620 DEBUG Running task: 3458 / 0x4662248
Jul 07 20:53:42-105073 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:42-105292 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:42-105527 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:42-105733 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:42-105940 util-scheduler-8620 DEBUG Adding task: 3459 / 0x46620a0
Jul 07 20:53:42-106128 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:42-106337 util-scheduler-8620 DEBUG Adding task: 3460 / 0x46620a0
Jul 07 20:53:42-106583 util-scheduler-8620 DEBUG Checking readiness of task: 3460 / 0x46620a0
Jul 07 20:53:42-106776 util-scheduler-8620 DEBUG Checking readiness of task: 3459 / 0x46620a0
Jul 07 20:53:42-106968 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:42-107158 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:42-107347 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:42-107536 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:42-107727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:42-107915 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:42-108104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:42-108324 util-scheduler-8620 DEBUG Running task: 3459 / 0x46620a0
Jul 07 20:53:42-108511 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:42-108688 util-8620 DEBUG process_notify is running
Jul 07 20:53:42-108861 util-8620 DEBUG client_notify is running
Jul 07 20:53:42-109048 util-scheduler-8620 DEBUG Canceling task: 3456 / 0x59ee8a0
Jul 07 20:53:42-109295 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:42-109517 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:42-109757 cadet-p2p-8620 DEBUG Checking 0x5ab9c98 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:42-109992 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:42-110170 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:42-110360 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:42-110646 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:42-110841 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:42-111021 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:42-111208 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:42-111395 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:42-111573 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:42-111760 util-scheduler-8620 DEBUG Canceling task: 3453 / 0x59e8808
Jul 07 20:53:42-111973 util-scheduler-8620 DEBUG Adding task: 3461 / 0x59e8808
Jul 07 20:53:42-112223 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:42-112394 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:42-112575 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:42-112775 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:42-112950 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:42-113124 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:42-113343 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:42-113548 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:42-113731 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:42-113910 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:42-114101 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:42-114351 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:45-313185 util-scheduler-8620 DEBUG Checking readiness of task: 3460 / 0x46620a0
Jul 07 20:53:45-313585 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:45-314190 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:45-314423 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:45-314660 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:45-314854 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:45-315045 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:45-315248 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:45-315442 util-scheduler-8620 DEBUG Running task: 3455 / 0x52cbfb8
Jul 07 20:53:45-315678 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:45-315934 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:45-316140 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:45-316342 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:45-316544 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:45-316778 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:45-316960 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:45-317182 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:45-317494 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:45-317691 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:45-317928 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:45-318165 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:45-318484 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:45-318685 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:45-318909 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:45-319093 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:45-319268 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:45-319475 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:45-319690 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:45-319914 util-scheduler-8620 DEBUG Adding task: 3462 / 0x59ee8a0
Jul 07 20:53:45-320093 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:45-320297 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:45-320474 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:45-320649 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:45-320887 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:45-321083 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:45-321280 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:45-321480 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:45-321723 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:45-321920 util-scheduler-8620 DEBUG Adding task: 3463 / 0x52cbfb8
Jul 07 20:53:45-322178 util-scheduler-8620 DEBUG Checking readiness of task: 3460 / 0x46620a0
Jul 07 20:53:45-322371 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:45-322563 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:45-322753 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:45-322943 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:45-323133 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:45-323321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:45-323510 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:45-323698 util-scheduler-8620 DEBUG Running task: 3462 / 0x59ee8a0
Jul 07 20:53:45-323907 util-scheduler-8620 DEBUG Adding task: 3464 / 0x59ee8a0
Jul 07 20:53:45-324129 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:45-324332 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:45-324539 util-scheduler-8620 DEBUG Adding task: 3465 / 0x46620a0
Jul 07 20:53:45-324782 util-scheduler-8620 DEBUG Checking readiness of task: 3465 / 0x46620a0
Jul 07 20:53:45-324976 util-scheduler-8620 DEBUG Checking readiness of task: 3460 / 0x46620a0
Jul 07 20:53:45-325167 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:45-325377 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:45-325567 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:45-325760 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:45-325950 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:45-326138 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:45-326326 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:45-326518 util-scheduler-8620 DEBUG Running task: 3465 / 0x46620a0
Jul 07 20:53:45-326719 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:45-326902 util-8620 DEBUG process_notify is running
Jul 07 20:53:45-327085 util-8620 DEBUG client_notify is running
Jul 07 20:53:45-327266 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:45-327461 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:45-327653 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:45-327921 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:48-137500 util-scheduler-8620 DEBUG Checking readiness of task: 3460 / 0x46620a0
Jul 07 20:53:48-137893 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:48-138091 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:48-138285 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:48-138489 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:48-138681 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:48-138870 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:48-139060 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:48-139255 util-scheduler-8620 DEBUG Running task: 3460 / 0x46620a0
Jul 07 20:53:48-139676 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:48-139930 util-scheduler-8620 DEBUG Adding task: 3466 / 0x4662248
Jul 07 20:53:48-140209 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:48-140402 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:48-140593 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:48-140783 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:48-140973 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:48-141163 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:48-141380 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:48-141572 util-scheduler-8620 DEBUG Running task: 3466 / 0x4662248
Jul 07 20:53:48-141763 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:48-141963 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:48-142195 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:48-142403 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:48-142608 util-scheduler-8620 DEBUG Adding task: 3467 / 0x46620a0
Jul 07 20:53:48-142795 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:48-143002 util-scheduler-8620 DEBUG Adding task: 3468 / 0x46620a0
Jul 07 20:53:48-143246 util-scheduler-8620 DEBUG Checking readiness of task: 3468 / 0x46620a0
Jul 07 20:53:48-143439 util-scheduler-8620 DEBUG Checking readiness of task: 3467 / 0x46620a0
Jul 07 20:53:48-143632 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:48-143822 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:48-144013 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:48-144202 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:48-144392 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:48-144580 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:48-144770 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:48-144961 util-scheduler-8620 DEBUG Running task: 3467 / 0x46620a0
Jul 07 20:53:48-145147 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:48-145348 util-8620 DEBUG process_notify is running
Jul 07 20:53:48-145569 util-8620 DEBUG client_notify is running
Jul 07 20:53:48-145762 util-scheduler-8620 DEBUG Canceling task: 3464 / 0x59ee8a0
Jul 07 20:53:48-145991 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:48-146226 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:48-146466 cadet-p2p-8620 DEBUG Checking 0x5abca00 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:48-146702 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:48-146911 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:48-147103 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:48-147388 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:48-147588 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:48-147768 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:48-147956 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:48-148146 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:48-148324 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:48-148508 util-scheduler-8620 DEBUG Canceling task: 3461 / 0x59e8808
Jul 07 20:53:48-148721 util-scheduler-8620 DEBUG Adding task: 3469 / 0x59e8808
Jul 07 20:53:48-148970 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:48-149142 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:48-149344 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:48-149546 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:48-149722 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:48-149896 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:48-150095 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:48-150300 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:48-150483 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:48-150662 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:48-150854 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:48-151106 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:50-324260 util-scheduler-8620 DEBUG Checking readiness of task: 3468 / 0x46620a0
Jul 07 20:53:50-324650 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:50-325312 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:50-325511 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:50-325773 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:50-325986 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:50-326176 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:50-326365 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:50-326559 util-scheduler-8620 DEBUG Running task: 3463 / 0x52cbfb8
Jul 07 20:53:50-326799 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:50-327057 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:50-327263 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:50-327464 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:50-327667 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:50-327904 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:50-328087 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:50-328309 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:50-328599 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:50-328796 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:50-329032 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:50-329261 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:50-329583 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:50-329784 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:50-330008 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:50-330192 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:50-330367 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:50-330573 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:50-330787 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:50-331047 util-scheduler-8620 DEBUG Adding task: 3470 / 0x59ee8a0
Jul 07 20:53:50-331230 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:50-331434 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:50-331611 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:50-331786 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:50-332024 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:50-332221 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:50-332399 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:50-332599 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:50-332844 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:50-333043 util-scheduler-8620 DEBUG Adding task: 3471 / 0x52cbfb8
Jul 07 20:53:50-333325 util-scheduler-8620 DEBUG Checking readiness of task: 3468 / 0x46620a0
Jul 07 20:53:50-333519 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:50-333708 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:50-333897 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:50-334086 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:50-334275 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:50-334465 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:50-334652 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:50-334841 util-scheduler-8620 DEBUG Running task: 3470 / 0x59ee8a0
Jul 07 20:53:50-335049 util-scheduler-8620 DEBUG Adding task: 3472 / 0x59ee8a0
Jul 07 20:53:50-335272 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:50-335475 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:50-335683 util-scheduler-8620 DEBUG Adding task: 3473 / 0x46620a0
Jul 07 20:53:50-335926 util-scheduler-8620 DEBUG Checking readiness of task: 3473 / 0x46620a0
Jul 07 20:53:50-336121 util-scheduler-8620 DEBUG Checking readiness of task: 3468 / 0x46620a0
Jul 07 20:53:50-336312 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:50-336502 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:50-336693 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:50-336882 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:50-337072 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:50-337281 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:50-337472 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:50-337663 util-scheduler-8620 DEBUG Running task: 3473 / 0x46620a0
Jul 07 20:53:50-337849 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:50-338031 util-8620 DEBUG process_notify is running
Jul 07 20:53:50-338205 util-8620 DEBUG client_notify is running
Jul 07 20:53:50-338384 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:50-338580 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:50-338771 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:50-339028 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:51-264671 util-scheduler-8620 DEBUG Checking readiness of task: 3468 / 0x46620a0
Jul 07 20:53:51-265054 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:51-265290 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:51-265486 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:51-265678 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:51-265899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:51-266090 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:51-266280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:51-266477 util-scheduler-8620 DEBUG Running task: 3468 / 0x46620a0
Jul 07 20:53:51-266908 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:51-267161 util-scheduler-8620 DEBUG Adding task: 3474 / 0x4662248
Jul 07 20:53:51-267440 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:51-267633 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:51-267828 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:51-268018 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:51-268209 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:51-268397 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:51-268588 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:51-268776 util-scheduler-8620 DEBUG Running task: 3474 / 0x4662248
Jul 07 20:53:51-268967 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:51-269168 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:51-269428 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:51-269635 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:51-269841 util-scheduler-8620 DEBUG Adding task: 3475 / 0x46620a0
Jul 07 20:53:51-270029 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:51-270234 util-scheduler-8620 DEBUG Adding task: 3476 / 0x46620a0
Jul 07 20:53:51-270481 util-scheduler-8620 DEBUG Checking readiness of task: 3476 / 0x46620a0
Jul 07 20:53:51-270675 util-scheduler-8620 DEBUG Checking readiness of task: 3475 / 0x46620a0
Jul 07 20:53:51-270867 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:51-271058 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:51-271247 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:51-271438 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:51-271628 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:51-271818 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:51-272007 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:51-272199 util-scheduler-8620 DEBUG Running task: 3475 / 0x46620a0
Jul 07 20:53:51-272387 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:51-272566 util-8620 DEBUG process_notify is running
Jul 07 20:53:51-272737 util-8620 DEBUG client_notify is running
Jul 07 20:53:51-272925 util-scheduler-8620 DEBUG Canceling task: 3472 / 0x59ee8a0
Jul 07 20:53:51-273150 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:51-273415 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:51-273656 cadet-p2p-8620 DEBUG Checking 0x5abf638 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:51-273889 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:51-274068 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:51-274258 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:51-274543 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:51-274739 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:51-274918 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:51-275105 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:51-275294 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:51-275472 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:51-275674 util-scheduler-8620 DEBUG Canceling task: 3469 / 0x59e8808
Jul 07 20:53:51-275886 util-scheduler-8620 DEBUG Adding task: 3477 / 0x59e8808
Jul 07 20:53:51-276137 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:51-276307 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:51-276488 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:51-276690 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:51-276865 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:51-277039 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:51-277262 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:51-277468 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:51-277651 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:51-277834 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:51-278025 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:51-278276 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:55-337286 util-scheduler-8620 DEBUG Checking readiness of task: 3476 / 0x46620a0
Jul 07 20:53:55-337677 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:55-337893 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:55-338092 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:55-338285 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:55-338482 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:55-338673 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:55-338863 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:55-339057 util-scheduler-8620 DEBUG Running task: 3471 / 0x52cbfb8
Jul 07 20:53:55-339295 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:53:55-339552 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:53:55-339759 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:53:55-339960 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:53:55-340163 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:53:55-340398 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:53:55-340579 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:53:55-340800 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:53:55-341091 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:53:55-341312 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:53:55-341553 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:53:55-341761 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:53:55-342082 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:53:55-342282 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:53:55-342507 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:53:55-342691 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:53:55-342867 cadet-con-8620 DEBUG  sendable
Jul 07 20:53:55-343073 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:53:55-343290 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:53:55-343514 util-scheduler-8620 DEBUG Adding task: 3478 / 0x59ee8a0
Jul 07 20:53:55-343697 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:53:55-343902 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:55-344079 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:53:55-344254 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:53:55-344491 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:53:55-344686 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:53:55-344863 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:53:55-345087 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:55-345356 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:53:55-345555 util-scheduler-8620 DEBUG Adding task: 3479 / 0x52cbfb8
Jul 07 20:53:55-345814 util-scheduler-8620 DEBUG Checking readiness of task: 3476 / 0x46620a0
Jul 07 20:53:55-346007 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:55-346197 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:55-346387 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:55-346577 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:55-346767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:55-346956 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:55-347158 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:55-347349 util-scheduler-8620 DEBUG Running task: 3478 / 0x59ee8a0
Jul 07 20:53:55-347557 util-scheduler-8620 DEBUG Adding task: 3480 / 0x59ee8a0
Jul 07 20:53:55-347779 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:53:55-347982 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:55-348190 util-scheduler-8620 DEBUG Adding task: 3481 / 0x46620a0
Jul 07 20:53:55-348435 util-scheduler-8620 DEBUG Checking readiness of task: 3481 / 0x46620a0
Jul 07 20:53:55-348630 util-scheduler-8620 DEBUG Checking readiness of task: 3476 / 0x46620a0
Jul 07 20:53:55-348820 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:55-349010 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:55-349220 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:55-349413 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:55-349603 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:55-349793 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:55-349981 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:55-350173 util-scheduler-8620 DEBUG Running task: 3481 / 0x46620a0
Jul 07 20:53:55-350357 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:55-350537 util-8620 DEBUG process_notify is running
Jul 07 20:53:55-350709 util-8620 DEBUG client_notify is running
Jul 07 20:53:55-350889 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:53:55-351083 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:55-351275 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:53:55-351531 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:53:57-283446 util-scheduler-8620 DEBUG Checking readiness of task: 3476 / 0x46620a0
Jul 07 20:53:57-283834 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:57-284032 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:57-284225 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:57-284418 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:57-284610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:57-284802 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:57-284992 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:57-285213 util-scheduler-8620 DEBUG Running task: 3476 / 0x46620a0
Jul 07 20:53:57-285640 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:53:57-285897 util-scheduler-8620 DEBUG Adding task: 3482 / 0x4662248
Jul 07 20:53:57-286175 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:57-286400 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:57-286593 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:57-286785 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:57-286975 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:57-287165 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:57-287354 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:57-287543 util-scheduler-8620 DEBUG Running task: 3482 / 0x4662248
Jul 07 20:53:57-287735 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:53:57-287934 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:53:57-288169 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:53:57-288376 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:53:57-288583 util-scheduler-8620 DEBUG Adding task: 3483 / 0x46620a0
Jul 07 20:53:57-288772 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:53:57-288978 util-scheduler-8620 DEBUG Adding task: 3484 / 0x46620a0
Jul 07 20:53:57-289246 util-scheduler-8620 DEBUG Checking readiness of task: 3484 / 0x46620a0
Jul 07 20:53:57-289441 util-scheduler-8620 DEBUG Checking readiness of task: 3483 / 0x46620a0
Jul 07 20:53:57-289635 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:53:57-289826 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:53:57-290017 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:53:57-290207 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:53:57-290398 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:53:57-290587 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:53:57-290778 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:53:57-290971 util-scheduler-8620 DEBUG Running task: 3483 / 0x46620a0
Jul 07 20:53:57-291155 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:53:57-291335 util-8620 DEBUG process_notify is running
Jul 07 20:53:57-291506 util-8620 DEBUG client_notify is running
Jul 07 20:53:57-291696 util-scheduler-8620 DEBUG Canceling task: 3480 / 0x59ee8a0
Jul 07 20:53:57-291921 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:53:57-292144 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:53:57-292383 cadet-p2p-8620 DEBUG Checking 0x5ac22e8 towards 2FDYFV0X (->V8XX)
Jul 07 20:53:57-292617 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:53:57-292795 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:53:57-292985 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:53:57-293294 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:53:57-293492 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:53:57-293673 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:53:57-293861 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:53:57-294050 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:53:57-294229 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:53:57-294412 util-scheduler-8620 DEBUG Canceling task: 3477 / 0x59e8808
Jul 07 20:53:57-294624 util-scheduler-8620 DEBUG Adding task: 3485 / 0x59e8808
Jul 07 20:53:57-294873 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:53:57-295044 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:53:57-295225 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:53:57-295424 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:53:57-295604 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:53:57-295779 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:53:57-295977 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:53:57-296182 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:53:57-296385 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:53:57-296565 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:53:57-296756 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:53:57-297009 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:00-346891 util-scheduler-8620 DEBUG Checking readiness of task: 3484 / 0x46620a0
Jul 07 20:54:00-347286 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-347902 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-348105 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-348301 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-348495 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-348685 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-348876 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-349068 util-scheduler-8620 DEBUG Running task: 3479 / 0x52cbfb8
Jul 07 20:54:00-349333 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:00-349592 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:54:00-349801 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:00-350004 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:00-350208 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:00-350447 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:00-350629 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:00-350865 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:00-351159 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:00-351360 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:00-351601 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:00-351812 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:00-352134 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:00-352337 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:00-352564 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:00-352749 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:00-352926 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:00-353134 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:00-353374 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:00-353600 util-scheduler-8620 DEBUG Adding task: 3486 / 0x59ee8a0
Jul 07 20:54:00-353783 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:00-353990 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:00-354168 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:00-354344 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:00-354584 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:00-354782 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:00-354960 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:00-355159 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:00-355408 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:00-355608 util-scheduler-8620 DEBUG Adding task: 3487 / 0x52cbfb8
Jul 07 20:54:00-355869 util-scheduler-8620 DEBUG Checking readiness of task: 3484 / 0x46620a0
Jul 07 20:54:00-356064 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-356258 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-356449 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-356641 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-356859 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-357052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-357263 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-357455 util-scheduler-8620 DEBUG Running task: 3486 / 0x59ee8a0
Jul 07 20:54:00-357664 util-scheduler-8620 DEBUG Adding task: 3488 / 0x59ee8a0
Jul 07 20:54:00-357890 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:00-358096 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:00-358304 util-scheduler-8620 DEBUG Adding task: 3489 / 0x46620a0
Jul 07 20:54:00-358551 util-scheduler-8620 DEBUG Checking readiness of task: 3489 / 0x46620a0
Jul 07 20:54:00-358746 util-scheduler-8620 DEBUG Checking readiness of task: 3484 / 0x46620a0
Jul 07 20:54:00-358938 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-359129 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-359322 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-359512 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-359703 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-359893 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-360084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-360277 util-scheduler-8620 DEBUG Running task: 3489 / 0x46620a0
Jul 07 20:54:00-360463 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:00-360644 util-8620 DEBUG process_notify is running
Jul 07 20:54:00-360818 util-8620 DEBUG client_notify is running
Jul 07 20:54:00-360999 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:00-361216 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:00-361412 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:00-361660 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:00-361911 util-scheduler-8620 DEBUG Checking readiness of task: 3484 / 0x46620a0
Jul 07 20:54:00-362106 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-362297 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-362488 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-362679 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-362870 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-363060 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-363250 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-363441 util-scheduler-8620 DEBUG Running task: 3484 / 0x46620a0
Jul 07 20:54:00-363848 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:00-364080 util-scheduler-8620 DEBUG Adding task: 3490 / 0x4662248
Jul 07 20:54:00-364332 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-364525 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-364717 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-364908 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-365099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-365311 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-365502 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-365692 util-scheduler-8620 DEBUG Running task: 3490 / 0x4662248
Jul 07 20:54:00-365883 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:00-366099 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:00-366323 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:00-366523 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:00-366725 util-scheduler-8620 DEBUG Adding task: 3491 / 0x46620a0
Jul 07 20:54:00-366911 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:00-367117 util-scheduler-8620 DEBUG Adding task: 3492 / 0x46620a0
Jul 07 20:54:00-367360 util-scheduler-8620 DEBUG Checking readiness of task: 3492 / 0x46620a0
Jul 07 20:54:00-367555 util-scheduler-8620 DEBUG Checking readiness of task: 3491 / 0x46620a0
Jul 07 20:54:00-367747 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:00-367940 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:00-368130 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:00-368324 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:00-368515 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:00-368706 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:00-368894 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:00-369088 util-scheduler-8620 DEBUG Running task: 3491 / 0x46620a0
Jul 07 20:54:00-369293 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:00-369472 util-8620 DEBUG process_notify is running
Jul 07 20:54:00-369643 util-8620 DEBUG client_notify is running
Jul 07 20:54:00-369830 util-scheduler-8620 DEBUG Canceling task: 3488 / 0x59ee8a0
Jul 07 20:54:00-370057 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:00-370275 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:00-370510 cadet-p2p-8620 DEBUG Checking 0x5ac4ee0 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:00-370745 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:00-370924 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:00-371113 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:00-371399 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:00-371596 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:00-371774 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:00-371964 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:00-372165 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:00-372345 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:00-372530 util-scheduler-8620 DEBUG Canceling task: 3485 / 0x59e8808
Jul 07 20:54:00-372743 util-scheduler-8620 DEBUG Adding task: 3493 / 0x59e8808
Jul 07 20:54:00-372988 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:00-373159 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:00-373363 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:00-373567 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:00-373743 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:00-373917 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:00-374116 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:00-374322 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:00-374507 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:00-374686 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:00-374877 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:00-376993 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:05-360764 util-scheduler-8620 DEBUG Checking readiness of task: 3492 / 0x46620a0
Jul 07 20:54:05-361140 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-362069 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-362275 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-362471 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-362663 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-362854 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-363044 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-363237 util-scheduler-8620 DEBUG Running task: 3487 / 0x52cbfb8
Jul 07 20:54:05-363472 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:05-363730 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:54:05-363936 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:05-364138 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:05-364341 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:05-364576 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:05-364757 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:05-364977 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:05-365292 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:05-365495 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:05-365734 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:05-365942 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:05-366260 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:05-366461 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:05-366685 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:05-366870 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:05-367044 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:05-367251 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:05-367468 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:05-367694 util-scheduler-8620 DEBUG Adding task: 3494 / 0x59ee8a0
Jul 07 20:54:05-367875 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:05-368079 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:05-368256 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:05-368432 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:05-368670 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:05-368866 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:05-369044 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:05-369263 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:05-369509 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:05-369708 util-scheduler-8620 DEBUG Adding task: 3495 / 0x52cbfb8
Jul 07 20:54:05-369966 util-scheduler-8620 DEBUG Checking readiness of task: 3492 / 0x46620a0
Jul 07 20:54:05-370159 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-370349 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-370539 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-370730 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-370920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-371109 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-371297 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-371488 util-scheduler-8620 DEBUG Running task: 3494 / 0x59ee8a0
Jul 07 20:54:05-371696 util-scheduler-8620 DEBUG Adding task: 3496 / 0x59ee8a0
Jul 07 20:54:05-371918 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:05-372122 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:05-372346 util-scheduler-8620 DEBUG Adding task: 3497 / 0x46620a0
Jul 07 20:54:05-372590 util-scheduler-8620 DEBUG Checking readiness of task: 3497 / 0x46620a0
Jul 07 20:54:05-372786 util-scheduler-8620 DEBUG Checking readiness of task: 3492 / 0x46620a0
Jul 07 20:54:05-372977 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-373167 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-373381 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-373572 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-373763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-373953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-374142 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-374333 util-scheduler-8620 DEBUG Running task: 3497 / 0x46620a0
Jul 07 20:54:05-374519 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:05-374697 util-8620 DEBUG process_notify is running
Jul 07 20:54:05-374871 util-8620 DEBUG client_notify is running
Jul 07 20:54:05-375049 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:05-375245 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:05-375436 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:05-375690 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:05-375938 util-scheduler-8620 DEBUG Checking readiness of task: 3492 / 0x46620a0
Jul 07 20:54:05-376132 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-376323 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-376513 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-376702 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-376892 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-377080 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-377290 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-377485 util-scheduler-8620 DEBUG Running task: 3492 / 0x46620a0
Jul 07 20:54:05-377890 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:05-378120 util-scheduler-8620 DEBUG Adding task: 3498 / 0x4662248
Jul 07 20:54:05-378368 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-378561 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-378751 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-378941 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-379131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-379319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-379508 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-379711 util-scheduler-8620 DEBUG Running task: 3498 / 0x4662248
Jul 07 20:54:05-379902 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:05-380097 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:05-380316 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:05-380512 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:05-380710 util-scheduler-8620 DEBUG Adding task: 3499 / 0x46620a0
Jul 07 20:54:05-380895 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:05-381098 util-scheduler-8620 DEBUG Adding task: 3500 / 0x46620a0
Jul 07 20:54:05-381362 util-scheduler-8620 DEBUG Checking readiness of task: 3500 / 0x46620a0
Jul 07 20:54:05-381572 util-scheduler-8620 DEBUG Checking readiness of task: 3499 / 0x46620a0
Jul 07 20:54:05-381764 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:05-381954 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:05-382145 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:05-382338 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:05-382529 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:05-382719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:05-382907 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:05-383099 util-scheduler-8620 DEBUG Running task: 3499 / 0x46620a0
Jul 07 20:54:05-383283 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:05-383460 util-8620 DEBUG process_notify is running
Jul 07 20:54:05-383629 util-8620 DEBUG client_notify is running
Jul 07 20:54:05-383814 util-scheduler-8620 DEBUG Canceling task: 3496 / 0x59ee8a0
Jul 07 20:54:05-384036 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:05-384252 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:05-384483 cadet-p2p-8620 DEBUG Checking 0x5ac7bb0 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:05-384717 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:05-384894 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:05-385082 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:05-385389 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:05-385584 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:05-385763 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:05-385950 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:05-386138 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:05-386316 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:05-386499 util-scheduler-8620 DEBUG Canceling task: 3493 / 0x59e8808
Jul 07 20:54:05-386710 util-scheduler-8620 DEBUG Adding task: 3501 / 0x59e8808
Jul 07 20:54:05-386954 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:05-387124 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:05-387305 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:05-387509 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:05-387684 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:05-387859 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:05-388056 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:05-388260 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:05-388443 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:05-388622 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:05-388810 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:05-389054 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:10-374848 util-scheduler-8620 DEBUG Checking readiness of task: 3500 / 0x46620a0
Jul 07 20:54:10-375231 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:10-375818 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:10-376052 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:10-376288 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:10-376483 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:10-376674 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:10-376864 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:10-377056 util-scheduler-8620 DEBUG Running task: 3495 / 0x52cbfb8
Jul 07 20:54:10-377314 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:10-377596 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:54:10-377803 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:10-378004 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:10-378206 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:10-378442 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:10-378624 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:10-378845 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:10-379134 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:10-379333 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:10-379570 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:10-379777 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:10-380094 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:10-380294 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:10-380519 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:10-380703 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:10-380879 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:10-381084 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:10-381320 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:10-381546 util-scheduler-8620 DEBUG Adding task: 3502 / 0x59ee8a0
Jul 07 20:54:10-381725 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:10-381929 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:10-382106 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:10-382281 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:10-382522 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:10-382717 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:10-382894 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:10-383093 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:10-383335 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:10-383552 util-scheduler-8620 DEBUG Adding task: 3503 / 0x52cbfb8
Jul 07 20:54:10-383813 util-scheduler-8620 DEBUG Checking readiness of task: 3500 / 0x46620a0
Jul 07 20:54:10-384008 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:10-384199 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:10-384389 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:10-384579 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:10-384769 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:10-384957 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:10-385146 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:10-385356 util-scheduler-8620 DEBUG Running task: 3502 / 0x59ee8a0
Jul 07 20:54:10-385565 util-scheduler-8620 DEBUG Adding task: 3504 / 0x59ee8a0
Jul 07 20:54:10-385788 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:10-385993 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:10-386200 util-scheduler-8620 DEBUG Adding task: 3505 / 0x46620a0
Jul 07 20:54:10-386445 util-scheduler-8620 DEBUG Checking readiness of task: 3505 / 0x46620a0
Jul 07 20:54:10-386639 util-scheduler-8620 DEBUG Checking readiness of task: 3500 / 0x46620a0
Jul 07 20:54:10-386841 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:10-387031 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:10-387220 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:10-387411 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:10-387600 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:10-387807 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:10-387996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:10-388189 util-scheduler-8620 DEBUG Running task: 3505 / 0x46620a0
Jul 07 20:54:10-388373 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:10-388553 util-8620 DEBUG process_notify is running
Jul 07 20:54:10-388725 util-8620 DEBUG client_notify is running
Jul 07 20:54:10-388905 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:10-389098 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:10-389310 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:10-389562 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:11-372945 util-scheduler-8620 DEBUG Checking readiness of task: 3500 / 0x46620a0
Jul 07 20:54:11-373317 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:11-373515 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:11-373708 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:11-373900 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:11-374092 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:11-374285 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:11-374475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:11-374669 util-scheduler-8620 DEBUG Running task: 3500 / 0x46620a0
Jul 07 20:54:11-375085 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:11-375335 util-scheduler-8620 DEBUG Adding task: 3506 / 0x4662248
Jul 07 20:54:11-375607 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:11-375801 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:11-375992 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:11-376182 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:11-376371 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:11-376561 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:11-376749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:11-376939 util-scheduler-8620 DEBUG Running task: 3506 / 0x4662248
Jul 07 20:54:11-377129 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:11-377353 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:11-377583 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:11-377789 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:11-377993 util-scheduler-8620 DEBUG Adding task: 3507 / 0x46620a0
Jul 07 20:54:11-378179 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:11-378385 util-scheduler-8620 DEBUG Adding task: 3508 / 0x46620a0
Jul 07 20:54:11-378628 util-scheduler-8620 DEBUG Checking readiness of task: 3508 / 0x46620a0
Jul 07 20:54:11-378822 util-scheduler-8620 DEBUG Checking readiness of task: 3507 / 0x46620a0
Jul 07 20:54:11-379015 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:11-379206 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:11-379395 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:11-379585 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:11-379774 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:11-379963 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:11-380180 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:11-380372 util-scheduler-8620 DEBUG Running task: 3507 / 0x46620a0
Jul 07 20:54:11-380559 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:11-380737 util-8620 DEBUG process_notify is running
Jul 07 20:54:11-380909 util-8620 DEBUG client_notify is running
Jul 07 20:54:11-381095 util-scheduler-8620 DEBUG Canceling task: 3504 / 0x59ee8a0
Jul 07 20:54:11-381344 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:11-381564 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:11-381802 cadet-p2p-8620 DEBUG Checking 0x5aca718 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:11-382035 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:11-382213 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:11-382403 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:11-382687 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:11-382882 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:11-383061 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:11-383248 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:11-383437 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:11-383615 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:11-383797 util-scheduler-8620 DEBUG Canceling task: 3501 / 0x59e8808
Jul 07 20:54:11-384010 util-scheduler-8620 DEBUG Adding task: 3509 / 0x59e8808
Jul 07 20:54:11-384258 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:11-384429 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:11-384609 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:11-384809 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:11-384985 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:11-385159 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:11-385381 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:11-385585 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:11-385768 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:11-385946 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:11-386136 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:11-386383 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:15-386217 util-scheduler-8620 DEBUG Checking readiness of task: 3508 / 0x46620a0
Jul 07 20:54:15-386612 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-386811 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-387005 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-387197 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-387390 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-387581 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-387781 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-387976 util-scheduler-8620 DEBUG Running task: 3503 / 0x52cbfb8
Jul 07 20:54:15-388215 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:15-388473 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:54:15-388681 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:15-388883 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:15-389086 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:15-389348 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:15-389531 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:15-389754 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:15-390046 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:15-390275 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:15-390515 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:15-390724 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:15-391047 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:15-391263 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:15-391489 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:15-391674 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:15-391850 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:15-392057 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:15-392272 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:15-392499 util-scheduler-8620 DEBUG Adding task: 3510 / 0x59ee8a0
Jul 07 20:54:15-392680 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:15-392886 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:15-393064 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:15-394464 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:15-394876 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:15-395229 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:15-395564 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:15-395921 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:15-396324 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:15-396681 util-scheduler-8620 DEBUG Adding task: 3511 / 0x52cbfb8
Jul 07 20:54:15-397267 util-scheduler-8620 DEBUG Checking readiness of task: 3508 / 0x46620a0
Jul 07 20:54:15-397619 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-397968 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-398314 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-398614 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-398959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-399305 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-399604 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-399951 util-scheduler-8620 DEBUG Running task: 3510 / 0x59ee8a0
Jul 07 20:54:15-400365 util-scheduler-8620 DEBUG Adding task: 3512 / 0x59ee8a0
Jul 07 20:54:15-400790 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:15-401147 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:15-401535 util-scheduler-8620 DEBUG Adding task: 3513 / 0x46620a0
Jul 07 20:54:15-401940 util-scheduler-8620 DEBUG Checking readiness of task: 3513 / 0x46620a0
Jul 07 20:54:15-402288 util-scheduler-8620 DEBUG Checking readiness of task: 3508 / 0x46620a0
Jul 07 20:54:15-402634 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-402979 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-403328 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-403676 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-404020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-404368 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-404669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-405152 util-scheduler-8620 DEBUG Running task: 3513 / 0x46620a0
Jul 07 20:54:15-405519 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:15-405851 util-8620 DEBUG process_notify is running
Jul 07 20:54:15-406178 util-8620 DEBUG client_notify is running
Jul 07 20:54:15-406467 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:15-406767 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:15-407183 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:15-407562 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:15-407821 util-scheduler-8620 DEBUG Checking readiness of task: 3508 / 0x46620a0
Jul 07 20:54:15-408017 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-408210 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-408401 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-408593 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-408783 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-408974 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-409163 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-409379 util-scheduler-8620 DEBUG Running task: 3508 / 0x46620a0
Jul 07 20:54:15-409785 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:15-410018 util-scheduler-8620 DEBUG Adding task: 3514 / 0x4662248
Jul 07 20:54:15-410268 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-410462 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-410654 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-410845 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-411036 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-411225 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-411416 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-411607 util-scheduler-8620 DEBUG Running task: 3514 / 0x4662248
Jul 07 20:54:15-411800 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:15-411997 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:15-412218 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:15-412417 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:15-412617 util-scheduler-8620 DEBUG Adding task: 3515 / 0x46620a0
Jul 07 20:54:15-412804 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:15-413009 util-scheduler-8620 DEBUG Adding task: 3516 / 0x46620a0
Jul 07 20:54:15-413278 util-scheduler-8620 DEBUG Checking readiness of task: 3516 / 0x46620a0
Jul 07 20:54:15-413473 util-scheduler-8620 DEBUG Checking readiness of task: 3515 / 0x46620a0
Jul 07 20:54:15-413669 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:15-413861 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:15-414052 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:15-414245 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:15-414435 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:15-414625 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:15-414814 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:15-415006 util-scheduler-8620 DEBUG Running task: 3515 / 0x46620a0
Jul 07 20:54:15-415192 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:15-415367 util-8620 DEBUG process_notify is running
Jul 07 20:54:15-415538 util-8620 DEBUG client_notify is running
Jul 07 20:54:15-415724 util-scheduler-8620 DEBUG Canceling task: 3512 / 0x59ee8a0
Jul 07 20:54:15-415948 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:15-416203 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:15-416453 cadet-p2p-8620 DEBUG Checking 0x5acd2f8 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:15-416688 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:15-416867 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:15-417055 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:15-417363 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:15-417560 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:15-417740 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:15-417929 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:15-418119 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:15-418297 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:15-418481 util-scheduler-8620 DEBUG Canceling task: 3509 / 0x59e8808
Jul 07 20:54:15-418693 util-scheduler-8620 DEBUG Adding task: 3517 / 0x59e8808
Jul 07 20:54:15-418938 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:15-419109 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:15-419292 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:15-419493 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:15-419669 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:15-419854 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:15-420053 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:15-420258 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:15-420483 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:15-420664 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:15-420895 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:15-422282 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:16-253888 util-scheduler-8620 DEBUG Checking readiness of task: 3516 / 0x46620a0
Jul 07 20:54:16-254276 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-254472 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-254665 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-254857 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-255049 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-255239 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-255429 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-255625 util-scheduler-8620 DEBUG Running task: 3516 / 0x46620a0
Jul 07 20:54:16-256049 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:16-256308 util-scheduler-8620 DEBUG Adding task: 3518 / 0x4662248
Jul 07 20:54:16-256587 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-256781 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-256973 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-257164 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-257383 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-257576 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-257765 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-257956 util-scheduler-8620 DEBUG Running task: 3518 / 0x4662248
Jul 07 20:54:16-258147 util-8620 DEBUG Received message of type 70 and size 200 from core service.
Jul 07 20:54:16-258350 core-api-8620 DEBUG Processing message of type 70 and size 200 from core service
Jul 07 20:54:16-258580 core-api-8620 DEBUG Received message of type 256 and size 164 from peer `KNAS'
Jul 07 20:54:16-258784 cadet-con-8620 DEBUG     path has 4 hops.
Jul 07 20:54:16-259058 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection M9KEP6HP from KNAS
Jul 07 20:54:16-259266 cadet-con-8620 DEBUG     origin: P00P
Jul 07 20:54:16-259445 cadet-con-8620 DEBUG   Creating path...
Jul 07 20:54:16-259657 cadet-con-8620 DEBUG   - 0: taking P00P
Jul 07 20:54:16-259842 cadet-con-8620 DEBUG     storing at 0
Jul 07 20:54:16-260043 cadet-con-8620 DEBUG   - 1: taking STRN
Jul 07 20:54:16-260225 cadet-con-8620 DEBUG     storing at 1
Jul 07 20:54:16-260425 cadet-con-8620 DEBUG   - 2: taking KNAS
Jul 07 20:54:16-260612 cadet-con-8620 DEBUG     storing at 2
Jul 07 20:54:16-260811 cadet-con-8620 DEBUG   - 3: taking GN10
Jul 07 20:54:16-260991 cadet-con-8620 DEBUG     storing at 3
Jul 07 20:54:16-261164 cadet-con-8620 DEBUG   Own position: 3
Jul 07 20:54:16-261362 cadet-con-8620 DEBUG   Creating connection
Jul 07 20:54:16-261605 cadet-con-8620 DEBUG  get next hop M9KEP6HP [3/4]
Jul 07 20:54:16-261817 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:54:16-262023 cadet-con-8620 DEBUG  get prev hop M9KEP6HP [3/4]
Jul 07 20:54:16-262230 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:16-262431 cadet-con-8620 DEBUG register neighbors for connection M9KEP6HP
Jul 07 20:54:16-262592 cadet-8620 DEBUG PATH:
Jul 07 20:54:16-262775 cadet-8620 DEBUG   P00P
Jul 07 20:54:16-262956 cadet-8620 DEBUG   STRN
Jul 07 20:54:16-263137 cadet-8620 DEBUG   KNAS
Jul 07 20:54:16-263316 cadet-8620 DEBUG   GN10
Jul 07 20:54:16-263468 cadet-8620 DEBUG END
Jul 07 20:54:16-263637 cadet-con-8620 DEBUG own pos 3
Jul 07 20:54:16-263827 cadet-con-8620 DEBUG putting connection M9KEP6HP to next peer 0x4d5be88
Jul 07 20:54:16-264039 cadet-con-8620 DEBUG next peer 0x4d5be88 GN10
Jul 07 20:54:16-264238 cadet-con-8620 DEBUG putting connection M9KEP6HP to prev peer 0x4d5cb40
Jul 07 20:54:16-264447 cadet-con-8620 DEBUG prev peer 0x4d5cb40 KNAS
Jul 07 20:54:16-264640 cadet-p2p-8620 DEBUG adding connection M9KEP6HP
Jul 07 20:54:16-264839 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:54:16-265042 cadet-p2p-8620 DEBUG peer GN10 ok, has 1 connections.
Jul 07 20:54:16-265259 cadet-p2p-8620 DEBUG  now has 2 connections.
Jul 07 20:54:16-265434 cadet-p2p-8620 DEBUG result 1
Jul 07 20:54:16-265618 cadet-p2p-8620 DEBUG adding connection M9KEP6HP
Jul 07 20:54:16-265817 cadet-p2p-8620 DEBUG to peer KNAS
Jul 07 20:54:16-266016 cadet-p2p-8620 DEBUG peer KNAS ok, has 0 connections.
Jul 07 20:54:16-266204 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:54:16-266377 cadet-p2p-8620 DEBUG result 1
Jul 07 20:54:16-266726 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:16-266944 util-scheduler-8620 DEBUG Adding task: 3519 / 0x53a5de0
Jul 07 20:54:16-267151 cadet-con-8620 DEBUG Connection M9KEP6HP state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:54:16-267347 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:54:16-268039 cadet-p2p-8620 DEBUG adding path [4] to peer P00P
Jul 07 20:54:16-268408 cadet-p2p-8620 DEBUG  final length: 4
Jul 07 20:54:16-268591 cadet-p2p-8620 DEBUG   added last
Jul 07 20:54:16-268844 cadet-tun-8620 DEBUG add connection M9KEP6HP (->P00P)
Jul 07 20:54:16-269047 cadet-tun-8620 DEBUG  to tunnel P00P
Jul 07 20:54:16-269283 util-scheduler-8620 DEBUG Adding task: 3520 / 0x53a63f8
Jul 07 20:54:16-269503 cadet-tun-8620 DEBUG Tunnel P00P cstate CADET_TUNNEL_NEW => CADET_TUNNEL_WAITING
Jul 07 20:54:16-269740 cadet-con-8620 INFO ===> {           FWD ACK} on connection M9KEP6HP (->P00P)
Jul 07 20:54:16-269977 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:16-270183 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:16-270480 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 36)
Jul 07 20:54:16-270678 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:16-270904 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:16-271088 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:16-271263 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:16-271469 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 36 bytes
Jul 07 20:54:16-271704 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `KNAS'
Jul 07 20:54:16-271918 util-scheduler-8620 DEBUG Adding task: 3521 / 0x4d5c9e8
Jul 07 20:54:16-272098 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:16-272302 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:16-272478 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:16-272654 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:16-272893 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:16-273078 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:54:16-273279 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:54:16-273481 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:16-273716 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_SENT -> CADET_CONNECTION_SENT
Jul 07 20:54:16-273961 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:54:16-274173 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:16-274386 util-scheduler-8620 DEBUG Adding task: 3522 / 0x46620a0
Jul 07 20:54:16-274641 util-scheduler-8620 DEBUG Checking readiness of task: 3522 / 0x46620a0
Jul 07 20:54:16-274846 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-275037 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-275227 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-275417 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-275606 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-275796 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-275984 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-276175 util-scheduler-8620 DEBUG Running task: 3521 / 0x4d5c9e8
Jul 07 20:54:16-276381 util-scheduler-8620 DEBUG Adding task: 3523 / 0x4d5c9e8
Jul 07 20:54:16-276603 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:16-276806 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:16-277008 util-scheduler-8620 DEBUG Adding task: 3524 / 0x46620a0
Jul 07 20:54:16-277231 util-scheduler-8620 DEBUG Running task: 3520 / 0x53a63f8
Jul 07 20:54:16-277478 util-scheduler-8620 DEBUG Checking readiness of task: 3524 / 0x46620a0
Jul 07 20:54:16-277672 util-scheduler-8620 DEBUG Checking readiness of task: 3522 / 0x46620a0
Jul 07 20:54:16-277862 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-278052 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-278241 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-278431 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-278620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-278808 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-278997 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-279189 util-scheduler-8620 DEBUG Running task: 3524 / 0x46620a0
Jul 07 20:54:16-279375 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:16-279553 util-8620 DEBUG process_notify is running
Jul 07 20:54:16-279725 util-8620 DEBUG client_notify is running
Jul 07 20:54:16-279904 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:16-280100 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:16-280291 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:16-280547 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:16-281153 util-scheduler-8620 DEBUG Checking readiness of task: 3522 / 0x46620a0
Jul 07 20:54:16-281379 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-281594 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-281785 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-281975 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-282165 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-282353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-282542 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-282732 util-scheduler-8620 DEBUG Running task: 3522 / 0x46620a0
Jul 07 20:54:16-283134 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:16-283364 util-scheduler-8620 DEBUG Adding task: 3525 / 0x4662248
Jul 07 20:54:16-283612 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-283805 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-283998 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-284188 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-284377 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-284565 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-284755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-284944 util-scheduler-8620 DEBUG Running task: 3525 / 0x4662248
Jul 07 20:54:16-285132 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:16-285353 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:16-285570 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:16-285768 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:16-285967 util-scheduler-8620 DEBUG Adding task: 3526 / 0x46620a0
Jul 07 20:54:16-286149 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:16-286348 util-scheduler-8620 DEBUG Adding task: 3527 / 0x46620a0
Jul 07 20:54:16-286588 util-scheduler-8620 DEBUG Checking readiness of task: 3527 / 0x46620a0
Jul 07 20:54:16-286781 util-scheduler-8620 DEBUG Checking readiness of task: 3526 / 0x46620a0
Jul 07 20:54:16-286973 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:16-287162 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:16-287353 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:16-287542 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:16-287732 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:16-287922 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:16-288109 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:16-288300 util-scheduler-8620 DEBUG Running task: 3526 / 0x46620a0
Jul 07 20:54:16-288484 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:16-288660 util-8620 DEBUG process_notify is running
Jul 07 20:54:16-288828 util-8620 DEBUG client_notify is running
Jul 07 20:54:16-289015 util-scheduler-8620 DEBUG Canceling task: 3523 / 0x4d5c9e8
Jul 07 20:54:16-289263 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 36 bytes.
Jul 07 20:54:16-289482 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:16-289715 cadet-p2p-8620 DEBUG Checking 0x5ad1288 towards M9KEP6HP (->P00P)
Jul 07 20:54:16-289948 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:16-290126 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:54:16-290295 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:54:16-290464 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:54:16-290634 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:54:16-290889 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 36)
Jul 07 20:54:16-291098 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:16-291280 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:16-291467 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:54:16-291648 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:16-291858 util-scheduler-8620 DEBUG Adding task: 3528 / 0x53a5de0
Jul 07 20:54:16-292097 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:54:16-292267 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:16-292448 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:54:16-292647 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:16-292823 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:16-292996 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:16-293218 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:16-293426 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 36 bytes.
Jul 07 20:54:16-293609 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:54:16-293787 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:16-293979 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:54:16-294225 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:17-254870 util-scheduler-8620 DEBUG Checking readiness of task: 3527 / 0x46620a0
Jul 07 20:54:17-255227 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:17-255424 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:17-255617 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:17-255809 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:17-256000 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:17-256190 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:17-256381 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:17-256576 util-scheduler-8620 DEBUG Running task: 3527 / 0x46620a0
Jul 07 20:54:17-256994 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:17-257289 util-scheduler-8620 DEBUG Adding task: 3529 / 0x4662248
Jul 07 20:54:17-257568 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:17-257762 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:17-257954 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:17-258145 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:17-258337 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:17-258527 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:17-258716 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:17-258907 util-scheduler-8620 DEBUG Running task: 3529 / 0x4662248
Jul 07 20:54:17-259099 util-8620 DEBUG Received message of type 70 and size 200 from core service.
Jul 07 20:54:17-259300 core-api-8620 DEBUG Processing message of type 70 and size 200 from core service
Jul 07 20:54:17-259527 core-api-8620 DEBUG Received message of type 256 and size 164 from peer `KNAS'
Jul 07 20:54:17-259727 cadet-con-8620 DEBUG     path has 4 hops.
Jul 07 20:54:17-259969 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection M9KEP6HP from KNAS
Jul 07 20:54:17-260175 cadet-con-8620 DEBUG     origin: P00P
Jul 07 20:54:17-260396 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:54:17-260619 cadet-p2p-8620 DEBUG adding path [4] to peer P00P
Jul 07 20:54:17-260800 cadet-p2p-8620 DEBUG  final length: 4
Jul 07 20:54:17-260975 cadet-p2p-8620 DEBUG   already known
Jul 07 20:54:17-261244 cadet-tun-8620 DEBUG add connection M9KEP6HP (->P00P)
Jul 07 20:54:17-261474 cadet-tun-8620 DEBUG  to tunnel P00P
Jul 07 20:54:17-261704 cadet-con-8620 INFO ===> {           FWD ACK} on connection M9KEP6HP (->P00P)
Jul 07 20:54:17-261939 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:17-262147 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:17-262462 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 36)
Jul 07 20:54:17-262661 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:17-262887 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:17-263070 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:17-263245 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:17-263451 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 36 bytes
Jul 07 20:54:17-263666 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `KNAS'
Jul 07 20:54:17-263881 util-scheduler-8620 DEBUG Adding task: 3530 / 0x4d5c9e8
Jul 07 20:54:17-264062 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:17-264266 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:17-264440 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:17-264615 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:17-264853 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:17-265038 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:54:17-265234 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:54:17-265432 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:17-265665 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 20:54:17-265908 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:54:17-266116 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:17-266329 util-scheduler-8620 DEBUG Adding task: 3531 / 0x46620a0
Jul 07 20:54:17-266572 util-scheduler-8620 DEBUG Checking readiness of task: 3531 / 0x46620a0
Jul 07 20:54:17-266765 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:17-266955 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:17-267145 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:17-267336 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:17-267527 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:17-267716 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:17-267905 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:17-268094 util-scheduler-8620 DEBUG Running task: 3530 / 0x4d5c9e8
Jul 07 20:54:17-268300 util-scheduler-8620 DEBUG Adding task: 3532 / 0x4d5c9e8
Jul 07 20:54:17-268521 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:17-268724 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:17-268924 util-scheduler-8620 DEBUG Adding task: 3533 / 0x46620a0
Jul 07 20:54:17-269165 util-scheduler-8620 DEBUG Checking readiness of task: 3533 / 0x46620a0
Jul 07 20:54:17-269396 util-scheduler-8620 DEBUG Checking readiness of task: 3531 / 0x46620a0
Jul 07 20:54:17-269588 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:17-269778 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:17-269967 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:17-270158 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:17-270347 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:17-270536 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:17-270724 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:17-270916 util-scheduler-8620 DEBUG Running task: 3533 / 0x46620a0
Jul 07 20:54:17-271102 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:17-271299 util-8620 DEBUG process_notify is running
Jul 07 20:54:17-271473 util-8620 DEBUG client_notify is running
Jul 07 20:54:17-271652 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:17-271847 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:17-272038 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:17-272287 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:17-291977 util-scheduler-8620 DEBUG Checking readiness of task: 3531 / 0x46620a0
Jul 07 20:54:17-292180 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:17-292373 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:17-292564 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:17-292755 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:17-292946 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:17-293135 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:17-293344 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:17-293534 util-scheduler-8620 DEBUG Running task: 3528 / 0x53a5de0
Jul 07 20:54:17-293769 cadet-con-8620 DEBUG BCK keepalive for M9KEP6HP (->P00P)
Jul 07 20:54:18-085478 util-scheduler-8620 DEBUG Checking readiness of task: 3531 / 0x46620a0
Jul 07 20:54:18-085839 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:18-086038 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:18-086233 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:18-086427 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:18-086620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:18-086811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:18-087003 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:18-087201 util-scheduler-8620 DEBUG Running task: 3531 / 0x46620a0
Jul 07 20:54:18-087625 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:18-087880 util-scheduler-8620 DEBUG Adding task: 3534 / 0x4662248
Jul 07 20:54:18-088157 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:18-088353 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:18-088546 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:18-088739 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:18-088931 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:18-089124 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:18-089348 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:18-089542 util-scheduler-8620 DEBUG Running task: 3534 / 0x4662248
Jul 07 20:54:18-089750 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:18-089952 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:18-090182 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:18-090391 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:18-090599 util-scheduler-8620 DEBUG Adding task: 3535 / 0x46620a0
Jul 07 20:54:18-090790 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:18-090997 util-scheduler-8620 DEBUG Adding task: 3536 / 0x46620a0
Jul 07 20:54:18-091242 util-scheduler-8620 DEBUG Checking readiness of task: 3536 / 0x46620a0
Jul 07 20:54:18-091437 util-scheduler-8620 DEBUG Checking readiness of task: 3535 / 0x46620a0
Jul 07 20:54:18-091658 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:18-091852 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:18-092044 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:18-092236 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:18-092429 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:18-092620 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:18-092810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:18-093004 util-scheduler-8620 DEBUG Running task: 3535 / 0x46620a0
Jul 07 20:54:18-093213 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:18-093398 util-8620 DEBUG process_notify is running
Jul 07 20:54:18-093667 util-8620 DEBUG client_notify is running
Jul 07 20:54:18-093861 util-scheduler-8620 DEBUG Canceling task: 3532 / 0x4d5c9e8
Jul 07 20:54:18-094089 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 36 bytes.
Jul 07 20:54:18-094315 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:18-094555 cadet-p2p-8620 DEBUG Checking 0x5ad41c0 towards M9KEP6HP (->P00P)
Jul 07 20:54:18-094791 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:18-094971 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:54:18-095143 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:54:18-095314 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:54:18-095485 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:54:18-095744 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 36)
Jul 07 20:54:18-095940 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:18-096121 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:18-096310 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:54:18-096491 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:18-096704 util-scheduler-8620 DEBUG Adding task: 3537 / 0x53a5de0
Jul 07 20:54:18-096943 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:54:18-097117 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:18-097325 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:54:18-097529 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:18-097707 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:18-097884 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:18-098083 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:18-098290 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 36 bytes.
Jul 07 20:54:18-098476 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:54:18-098656 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:18-098848 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:54:18-099100 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:19-255520 util-scheduler-8620 DEBUG Checking readiness of task: 3536 / 0x46620a0
Jul 07 20:54:19-255875 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:19-256073 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:19-256265 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:19-256457 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:19-256649 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:19-256838 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:19-257029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:19-257251 util-scheduler-8620 DEBUG Running task: 3536 / 0x46620a0
Jul 07 20:54:19-257673 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:19-257928 util-scheduler-8620 DEBUG Adding task: 3538 / 0x4662248
Jul 07 20:54:19-258230 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:19-258425 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:19-258616 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:19-258807 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:19-258999 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:19-259187 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:19-259376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:19-259565 util-scheduler-8620 DEBUG Running task: 3538 / 0x4662248
Jul 07 20:54:19-259757 util-8620 DEBUG Received message of type 70 and size 200 from core service.
Jul 07 20:54:19-259956 core-api-8620 DEBUG Processing message of type 70 and size 200 from core service
Jul 07 20:54:19-260182 core-api-8620 DEBUG Received message of type 256 and size 164 from peer `KNAS'
Jul 07 20:54:19-260379 cadet-con-8620 DEBUG     path has 4 hops.
Jul 07 20:54:19-260620 cadet-con-8620 INFO <-- { CONNECTION_CREATE} on connection M9KEP6HP from KNAS
Jul 07 20:54:19-260827 cadet-con-8620 DEBUG     origin: P00P
Jul 07 20:54:19-261045 cadet-con-8620 DEBUG   It's for us!
Jul 07 20:54:19-261290 cadet-p2p-8620 DEBUG adding path [4] to peer P00P
Jul 07 20:54:19-261471 cadet-p2p-8620 DEBUG  final length: 4
Jul 07 20:54:19-261646 cadet-p2p-8620 DEBUG   already known
Jul 07 20:54:19-261886 cadet-tun-8620 DEBUG add connection M9KEP6HP (->P00P)
Jul 07 20:54:19-262085 cadet-tun-8620 DEBUG  to tunnel P00P
Jul 07 20:54:19-262315 cadet-con-8620 INFO ===> {           FWD ACK} on connection M9KEP6HP (->P00P)
Jul 07 20:54:19-262549 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:19-262756 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:19-263050 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 36)
Jul 07 20:54:19-263246 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:19-263470 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:19-263653 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:19-263828 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:19-264032 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 36 bytes
Jul 07 20:54:19-264246 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `KNAS'
Jul 07 20:54:19-264462 util-scheduler-8620 DEBUG Adding task: 3539 / 0x4d5c9e8
Jul 07 20:54:19-264641 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:19-264844 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:19-265020 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:19-265213 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:19-265454 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:19-265637 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:54:19-265812 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:54:19-266010 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:19-266265 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 20:54:19-266539 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:54:19-266745 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:19-266955 util-scheduler-8620 DEBUG Adding task: 3540 / 0x46620a0
Jul 07 20:54:19-267198 util-scheduler-8620 DEBUG Checking readiness of task: 3540 / 0x46620a0
Jul 07 20:54:19-267421 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:19-267613 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:19-267804 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:19-267994 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:19-268203 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:19-268393 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:19-268600 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:19-268790 util-scheduler-8620 DEBUG Running task: 3539 / 0x4d5c9e8
Jul 07 20:54:19-268996 util-scheduler-8620 DEBUG Adding task: 3541 / 0x4d5c9e8
Jul 07 20:54:19-269237 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:19-269441 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:19-269661 util-scheduler-8620 DEBUG Adding task: 3542 / 0x46620a0
Jul 07 20:54:19-269902 util-scheduler-8620 DEBUG Checking readiness of task: 3542 / 0x46620a0
Jul 07 20:54:19-270096 util-scheduler-8620 DEBUG Checking readiness of task: 3540 / 0x46620a0
Jul 07 20:54:19-270287 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:19-270477 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:19-270684 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:19-270875 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:19-271064 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:19-271254 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:19-271444 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:19-271635 util-scheduler-8620 DEBUG Running task: 3542 / 0x46620a0
Jul 07 20:54:19-271840 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:19-272020 util-8620 DEBUG process_notify is running
Jul 07 20:54:19-272192 util-8620 DEBUG client_notify is running
Jul 07 20:54:19-272369 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:19-272564 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:19-272773 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:19-273024 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:20-097673 util-scheduler-8620 DEBUG Checking readiness of task: 3540 / 0x46620a0
Jul 07 20:54:20-098029 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-098227 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-098422 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-098617 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-098812 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-099005 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-099198 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-099393 util-scheduler-8620 DEBUG Running task: 3537 / 0x53a5de0
Jul 07 20:54:20-099659 cadet-con-8620 DEBUG BCK keepalive for M9KEP6HP (->P00P)
Jul 07 20:54:20-136871 util-scheduler-8620 DEBUG Checking readiness of task: 3540 / 0x46620a0
Jul 07 20:54:20-137274 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-137473 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-137669 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-137861 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-138051 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-138242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-138431 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-138627 util-scheduler-8620 DEBUG Running task: 3540 / 0x46620a0
Jul 07 20:54:20-139049 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:20-139331 util-scheduler-8620 DEBUG Adding task: 3543 / 0x4662248
Jul 07 20:54:20-139630 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-139827 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-140019 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-140211 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-140401 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-140592 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-140781 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-140970 util-scheduler-8620 DEBUG Running task: 3543 / 0x4662248
Jul 07 20:54:20-141160 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:20-141388 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:20-141618 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:20-141825 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:20-142032 util-scheduler-8620 DEBUG Adding task: 3544 / 0x46620a0
Jul 07 20:54:20-142218 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:20-142424 util-scheduler-8620 DEBUG Adding task: 3545 / 0x46620a0
Jul 07 20:54:20-142666 util-scheduler-8620 DEBUG Checking readiness of task: 3545 / 0x46620a0
Jul 07 20:54:20-142859 util-scheduler-8620 DEBUG Checking readiness of task: 3544 / 0x46620a0
Jul 07 20:54:20-143051 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-143241 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-143431 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-143621 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-143810 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-144000 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-144188 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-144379 util-scheduler-8620 DEBUG Running task: 3544 / 0x46620a0
Jul 07 20:54:20-144563 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:20-144745 util-8620 DEBUG process_notify is running
Jul 07 20:54:20-144917 util-8620 DEBUG client_notify is running
Jul 07 20:54:20-145105 util-scheduler-8620 DEBUG Canceling task: 3541 / 0x4d5c9e8
Jul 07 20:54:20-145356 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 36 bytes.
Jul 07 20:54:20-145579 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:20-145818 cadet-p2p-8620 DEBUG Checking 0x5ad7260 towards M9KEP6HP (->P00P)
Jul 07 20:54:20-146052 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:20-146229 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:54:20-146399 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:54:20-146567 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:54:20-146736 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:54:20-146993 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 36)
Jul 07 20:54:20-147187 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:20-147366 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:20-147553 cadet-con-8620 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 20:54:20-147733 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:20-147941 util-scheduler-8620 DEBUG Adding task: 3546 / 0x53a5de0
Jul 07 20:54:20-148182 cadet-con-8620 DEBUG next keepalive in 4 s
Jul 07 20:54:20-148352 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:20-148532 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:54:20-148732 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:20-148906 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:20-149080 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:20-149321 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:20-149527 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 36 bytes.
Jul 07 20:54:20-149712 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:54:20-149891 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:20-150080 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:54:20-150330 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:20-306622 util-scheduler-8620 DEBUG Checking readiness of task: 3545 / 0x46620a0
Jul 07 20:54:20-306913 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-307109 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-307301 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-307493 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-307684 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-307923 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-308116 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-308310 util-scheduler-8620 DEBUG Running task: 3545 / 0x46620a0
Jul 07 20:54:20-308730 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:20-309027 util-scheduler-8620 DEBUG Adding task: 3547 / 0x4662248
Jul 07 20:54:20-309323 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-309519 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-309712 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-309904 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-310096 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-310288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-310478 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-310670 util-scheduler-8620 DEBUG Running task: 3547 / 0x4662248
Jul 07 20:54:20-310862 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:54:20-311063 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:54:20-311287 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `KNAS'
Jul 07 20:54:20-311549 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection M9KEP6HP from KNAS
Jul 07 20:54:20-311766 cadet-con-8620 DEBUG   via peer KNAS
Jul 07 20:54:20-312005 cadet-con-8620 DEBUG  get next hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:20-312215 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:54:20-312456 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:20-312664 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:20-312845 cadet-con-8620 DEBUG   ACK
Jul 07 20:54:20-313073 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:54:20-313282 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:20-313471 util-scheduler-8620 DEBUG Canceling task: 3519 / 0x53a5de0
Jul 07 20:54:20-313695 util-scheduler-8620 DEBUG Adding task: 3548 / 0x53a5de0
Jul 07 20:54:20-313879 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:54:20-314052 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:54:20-314236 util-scheduler-8620 DEBUG Canceling task: 3546 / 0x53a5de0
Jul 07 20:54:20-314448 util-scheduler-8620 DEBUG Adding task: 3549 / 0x53a5de0
Jul 07 20:54:20-314702 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:20-314911 cadet-tun-8620 DEBUG Tunnel P00P cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:54:20-315092 cadet-tun-8620 DEBUG   cstate triggered rekey
Jul 07 20:54:20-315319 cadet-tun-8620 INFO Re-key Tunnel P00P
Jul 07 20:54:20-315522 cadet-tun-8620 INFO   new kx ctx for P00P
Jul 07 20:54:20-438959 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:54:20-439306 cadet-tun-8620 INFO PE: 00000000
Jul 07 20:54:20-440264 cadet-tun-8620 INFO KM: SY1Y2DBY
Jul 07 20:54:20-440456 cadet-tun-8620 INFO EK: R7NK9DDZ
Jul 07 20:54:20-440714 cadet-tun-8620 INFO DK: 0R58TWQP
Jul 07 20:54:20-440985 cadet-tun-8620 INFO ===> EPHM for P00P
Jul 07 20:54:20-441208 cadet-tun-8620 DEBUG GMT KX on Tunnel P00P
Jul 07 20:54:20-441415 cadet-tun-8620 DEBUG tunnel_get_connection P00P
Jul 07 20:54:20-441646 cadet-tun-8620 DEBUG   connection M9KEP6HP (->P00P): 3
Jul 07 20:54:20-441827 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:20-442048 cadet-tun-8620 DEBUG  selected: connection M9KEP6HP (->P00P)
Jul 07 20:54:20-442334 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection M9KEP6HP (->P00P) (196 bytes)
Jul 07 20:54:20-442536 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 0
Jul 07 20:54:20-442772 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:20-442980 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:20-443293 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 196)
Jul 07 20:54:20-443494 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:20-443720 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:20-443903 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:20-444078 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:20-444285 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 196 bytes
Jul 07 20:54:20-444500 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `KNAS'
Jul 07 20:54:20-444733 util-scheduler-8620 DEBUG Adding task: 3550 / 0x4d5c9e8
Jul 07 20:54:20-444913 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:20-445119 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:20-445313 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:20-445500 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:20-445739 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:20-445935 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:20-446111 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:20-446311 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:20-446560 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:20-446754 util-scheduler-8620 DEBUG Adding task: 3551 / 0x53a63f8
Jul 07 20:54:20-446946 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:20-447162 util-scheduler-8620 DEBUG Adding task: 3552 / 0x46620a0
Jul 07 20:54:20-447437 util-scheduler-8620 DEBUG Checking readiness of task: 3552 / 0x46620a0
Jul 07 20:54:20-447635 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-447825 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-448015 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-448205 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-448395 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-448584 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-448772 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-448965 util-scheduler-8620 DEBUG Running task: 3552 / 0x46620a0
Jul 07 20:54:20-449399 util-8620 DEBUG receive_ready read 304/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:20-449628 util-scheduler-8620 DEBUG Adding task: 3553 / 0x4662248
Jul 07 20:54:20-449837 util-scheduler-8620 DEBUG Running task: 3550 / 0x4d5c9e8
Jul 07 20:54:20-450043 util-scheduler-8620 DEBUG Adding task: 3554 / 0x4d5c9e8
Jul 07 20:54:20-450263 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:20-450495 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:20-450699 util-scheduler-8620 DEBUG Adding task: 3555 / 0x46620a0
Jul 07 20:54:20-450896 util-scheduler-8620 DEBUG Running task: 3511 / 0x52cbfb8
Jul 07 20:54:20-451105 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:20-451351 cadet-tun-8620 DEBUG  kx started 6 m ago
Jul 07 20:54:20-451554 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:20-451751 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:20-451950 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:20-452174 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:20-452352 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:20-452570 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:20-452842 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:20-453036 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:20-453289 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:20-453498 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:20-453804 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:20-454003 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:20-454225 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:20-454408 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:20-454582 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:20-454787 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:20-454996 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:20-455206 util-scheduler-8620 DEBUG Adding task: 3556 / 0x59ee8a0
Jul 07 20:54:20-455383 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:20-455584 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:20-455759 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:20-455933 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:20-456168 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:20-456362 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:20-456538 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:20-456734 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:20-456965 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:20-457162 util-scheduler-8620 DEBUG Adding task: 3557 / 0x52cbfb8
Jul 07 20:54:20-457421 util-scheduler-8620 DEBUG Checking readiness of task: 3555 / 0x46620a0
Jul 07 20:54:20-457615 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:20-457806 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:20-457995 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:20-458186 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:20-458376 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:20-458564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:20-458753 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:20-458944 util-scheduler-8620 DEBUG Running task: 3555 / 0x46620a0
Jul 07 20:54:20-459129 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:20-459308 util-8620 DEBUG process_notify is running
Jul 07 20:54:20-459480 util-8620 DEBUG client_notify is running
Jul 07 20:54:20-459660 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:20-459854 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:20-460046 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:20-460299 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:20-460507 util-scheduler-8620 DEBUG Running task: 3556 / 0x59ee8a0
Jul 07 20:54:20-460733 util-scheduler-8620 DEBUG Adding task: 3558 / 0x59ee8a0
Jul 07 20:54:20-460948 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:20-461141 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:20-461366 util-scheduler-8620 DEBUG Adding task: 3559 / 0x46620a0
Jul 07 20:54:20-461562 util-scheduler-8620 DEBUG Running task: 3553 / 0x4662248
Jul 07 20:54:20-461753 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:54:20-461951 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:54:20-462167 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `KNAS'
Jul 07 20:54:20-462418 cadet-con-8620 INFO <-- {                KX} on connection M9KEP6HP from KNAS
Jul 07 20:54:20-462653 cadet-con-8620 DEBUG  on connection M9KEP6HP (->P00P)
Jul 07 20:54:20-462881 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:20-463086 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:20-463279 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:20-463465 util-scheduler-8620 DEBUG Canceling task: 3548 / 0x53a5de0
Jul 07 20:54:20-463683 util-scheduler-8620 DEBUG Adding task: 3560 / 0x53a5de0
Jul 07 20:54:20-463862 cadet-con-8620 DEBUG   message for us!
Jul 07 20:54:20-464111 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:54:20-464316 util-scheduler-8620 DEBUG Adding task: 3561 / 0x4d5e5d8
Jul 07 20:54:20-464496 cadet-tun-8620 DEBUG kx message received
Jul 07 20:54:20-464697 cadet-tun-8620 INFO <=== EPHM for P00P
Jul 07 20:54:21-274925 cadet-tun-8620 INFO ME: C2VJ982H
Jul 07 20:54:21-275243 cadet-tun-8620 INFO PE: 1B4T7TPQ
Jul 07 20:54:21-275431 cadet-tun-8620 INFO KM: QKZ4C262
Jul 07 20:54:21-275614 cadet-tun-8620 INFO EK: 1BR3R993
Jul 07 20:54:21-275798 cadet-tun-8620 INFO DK: X5GG98S2
Jul 07 20:54:21-275971 cadet-tun-8620 DEBUG   our key was sent, sending ping
Jul 07 20:54:21-276195 cadet-tun-8620 INFO ===> PING for P00P
Jul 07 20:54:21-276487 cadet-tun-8620 DEBUG   sending 3469575226
Jul 07 20:54:21-276690 cadet-tun-8620 DEBUG   towards P00P
Jul 07 20:54:21-276861 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:54:21-277043 cadet-tun-8620 INFO   ENC with key 1BR3R993
Jul 07 20:54:21-280166 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:54:21-280958 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:54:21-281144 cadet-tun-8620 DEBUG   e sending 587222099
Jul 07 20:54:21-281383 cadet-tun-8620 DEBUG   e towards 7G6X
Jul 07 20:54:21-281587 cadet-tun-8620 DEBUG GMT KX on Tunnel P00P
Jul 07 20:54:21-281788 cadet-tun-8620 DEBUG tunnel_get_connection P00P
Jul 07 20:54:21-282018 cadet-tun-8620 DEBUG   connection M9KEP6HP (->P00P): 3
Jul 07 20:54:21-282198 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:21-282420 cadet-tun-8620 DEBUG  selected: connection M9KEP6HP (->P00P)
Jul 07 20:54:21-282703 cadet-con-8620 INFO --> {                KX} ({           KX_PING} 0) on connection M9KEP6HP (->P00P) (80 bytes)
Jul 07 20:54:21-282901 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 1
Jul 07 20:54:21-283137 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:21-283344 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:21-283655 cadet-p2p-8620 INFO que {                KX} ({           KX_PING} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 80)
Jul 07 20:54:21-283854 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:21-284079 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:21-284261 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:21-284436 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:21-284639 cadet-p2p-8620 DEBUG core tmt rdy towards KNAS already called
Jul 07 20:54:21-284841 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:21-285016 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:54:21-285209 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:21-285450 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:21-285674 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:21-285852 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:21-286087 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:21-286279 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:54:21-286455 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:54:21-286651 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:21-286880 util-scheduler-8620 DEBUG Adding task: 3562 / 0x4662248
Jul 07 20:54:21-287165 util-scheduler-8620 DEBUG Checking readiness of task: 3561 / 0x4d5e5d8
Jul 07 20:54:21-287364 util-scheduler-8620 DEBUG Checking readiness of task: 3559 / 0x46620a0
Jul 07 20:54:21-287556 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-287746 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-287935 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-288124 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-288314 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-288502 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-288690 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-288883 util-scheduler-8620 DEBUG Running task: 3559 / 0x46620a0
Jul 07 20:54:21-289068 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-289267 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-289440 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-289621 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:21-289817 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:21-290008 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:21-290269 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:21-290479 util-scheduler-8620 DEBUG Running task: 3561 / 0x4d5e5d8
Jul 07 20:54:21-290662 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:54:21-290836 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-291005 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-291229 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:54:21-291473 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:54:21-291685 util-scheduler-8620 DEBUG Running task: 3562 / 0x4662248
Jul 07 20:54:21-291875 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:54:21-292069 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:54:21-292285 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `KNAS'
Jul 07 20:54:21-292533 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection M9KEP6HP from KNAS
Jul 07 20:54:21-292746 cadet-con-8620 DEBUG   via peer KNAS
Jul 07 20:54:21-292980 cadet-con-8620 DEBUG  get next hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:21-293186 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:54:21-293445 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:21-293651 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:21-293833 cadet-con-8620 DEBUG   ACK
Jul 07 20:54:21-294063 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:54:21-294247 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:21-294464 util-scheduler-8620 DEBUG Canceling task: 3560 / 0x53a5de0
Jul 07 20:54:21-294688 util-scheduler-8620 DEBUG Adding task: 3563 / 0x53a5de0
Jul 07 20:54:21-294872 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:54:21-295050 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:21-295262 util-scheduler-8620 DEBUG Adding task: 3564 / 0x46620a0
Jul 07 20:54:21-295526 util-scheduler-8620 DEBUG Checking readiness of task: 3564 / 0x46620a0
Jul 07 20:54:21-295720 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-295910 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-296100 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-296290 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-296479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-296667 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-296856 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-297046 util-scheduler-8620 DEBUG Running task: 3564 / 0x46620a0
Jul 07 20:54:21-297474 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:21-297703 util-scheduler-8620 DEBUG Adding task: 3565 / 0x4662248
Jul 07 20:54:21-297963 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-298155 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-298346 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-298535 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-298725 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-298913 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-299102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-299291 util-scheduler-8620 DEBUG Running task: 3565 / 0x4662248
Jul 07 20:54:21-299478 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:21-299669 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:21-299882 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:21-300086 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:21-300286 util-scheduler-8620 DEBUG Adding task: 3566 / 0x46620a0
Jul 07 20:54:21-300470 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:21-300666 util-scheduler-8620 DEBUG Adding task: 3567 / 0x46620a0
Jul 07 20:54:21-300905 util-scheduler-8620 DEBUG Checking readiness of task: 3567 / 0x46620a0
Jul 07 20:54:21-301098 util-scheduler-8620 DEBUG Checking readiness of task: 3566 / 0x46620a0
Jul 07 20:54:21-301325 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-301516 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-301709 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-301899 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-302088 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-302276 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-302464 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-302655 util-scheduler-8620 DEBUG Running task: 3566 / 0x46620a0
Jul 07 20:54:21-302838 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-303013 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-303182 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-303364 util-scheduler-8620 DEBUG Canceling task: 3558 / 0x59ee8a0
Jul 07 20:54:21-303584 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:21-303801 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:21-304032 cadet-p2p-8620 DEBUG Checking 0x5b46480 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:21-304264 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:21-304441 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:21-304628 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:21-304927 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:21-305122 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:21-305323 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:21-305512 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:21-305701 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:21-305878 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:21-306060 util-scheduler-8620 DEBUG Canceling task: 3517 / 0x59e8808
Jul 07 20:54:21-306270 util-scheduler-8620 DEBUG Adding task: 3568 / 0x59e8808
Jul 07 20:54:21-306520 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:21-306691 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:21-306872 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:21-307071 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:21-307246 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:21-307420 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:21-307617 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:21-307821 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:21-308004 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:21-308181 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:21-308370 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:21-308618 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:21-420853 util-scheduler-8620 DEBUG Checking readiness of task: 3567 / 0x46620a0
Jul 07 20:54:21-421302 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-421500 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-421693 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-421885 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-422076 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-422265 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-422458 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-422654 util-scheduler-8620 DEBUG Running task: 3567 / 0x46620a0
Jul 07 20:54:21-423082 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:21-423336 util-scheduler-8620 DEBUG Adding task: 3569 / 0x4662248
Jul 07 20:54:21-423616 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-423808 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-423999 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-424189 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-424379 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-424568 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-424757 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-424946 util-scheduler-8620 DEBUG Running task: 3569 / 0x4662248
Jul 07 20:54:21-425139 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:21-425365 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:21-425594 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:21-425800 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:21-426008 util-scheduler-8620 DEBUG Adding task: 3570 / 0x46620a0
Jul 07 20:54:21-426195 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:21-426399 util-scheduler-8620 DEBUG Adding task: 3571 / 0x46620a0
Jul 07 20:54:21-426646 util-scheduler-8620 DEBUG Checking readiness of task: 3571 / 0x46620a0
Jul 07 20:54:21-426870 util-scheduler-8620 DEBUG Checking readiness of task: 3570 / 0x46620a0
Jul 07 20:54:21-427062 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-427252 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-427442 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-427652 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-427844 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-428034 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-428223 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-428414 util-scheduler-8620 DEBUG Running task: 3570 / 0x46620a0
Jul 07 20:54:21-428599 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-428777 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-428949 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-429137 util-scheduler-8620 DEBUG Canceling task: 3554 / 0x4d5c9e8
Jul 07 20:54:21-429387 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 196 bytes.
Jul 07 20:54:21-429606 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:21-429844 cadet-p2p-8620 DEBUG Checking 0x5b44fd8 towards M9KEP6HP (->P00P)
Jul 07 20:54:21-430079 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:21-430256 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:21-430447 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:21-430732 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 196)
Jul 07 20:54:21-430927 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:21-431107 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:21-431295 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:54:21-431495 cadet-con-8620 DEBUG  C_P- 0x53a5de0 2
Jul 07 20:54:21-431672 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:54:21-431856 util-scheduler-8620 DEBUG Canceling task: 3549 / 0x53a5de0
Jul 07 20:54:21-432069 util-scheduler-8620 DEBUG Adding task: 3572 / 0x53a5de0
Jul 07 20:54:21-432319 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:21-432491 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:21-432713 cadet-p2p-8620 DEBUG Checking 0x5df8608 towards M9KEP6HP (->P00P)
Jul 07 20:54:21-432955 cadet-p2p-8620 DEBUG Checking 0x5df8608 towards M9KEP6HP (->P00P)
Jul 07 20:54:21-433133 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:54:21-433367 core-api-8620 DEBUG Asking core for transmission of 80 bytes to `KNAS'
Jul 07 20:54:21-433580 util-scheduler-8620 DEBUG Adding task: 3573 / 0x4d5c9e8
Jul 07 20:54:21-433760 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:21-433938 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:21-434138 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:21-434313 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:21-434489 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:21-434727 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:21-434922 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 20:54:21-435102 cadet-p2p-8620 DEBUG QQQ    size: 80 bytes
Jul 07 20:54:21-435301 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:21-435505 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 196 bytes.
Jul 07 20:54:21-435687 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:21-435888 util-scheduler-8620 DEBUG Adding task: 3574 / 0x4d5c9e8
Jul 07 20:54:21-436105 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:21-436299 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:21-436498 util-scheduler-8620 DEBUG Adding task: 3575 / 0x46620a0
Jul 07 20:54:21-436698 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:21-436968 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:21-437165 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:54:21-437435 util-scheduler-8620 DEBUG Checking readiness of task: 3575 / 0x46620a0
Jul 07 20:54:21-437629 util-scheduler-8620 DEBUG Checking readiness of task: 3571 / 0x46620a0
Jul 07 20:54:21-437819 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-438009 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-438198 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-438388 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-438577 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-438766 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-438954 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-439144 util-scheduler-8620 DEBUG Running task: 3575 / 0x46620a0
Jul 07 20:54:21-439327 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-439501 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-439671 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-439847 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:21-440040 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:21-440228 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:21-440468 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:21-440673 util-scheduler-8620 DEBUG Running task: 3573 / 0x4d5c9e8
Jul 07 20:54:21-440864 util-scheduler-8620 DEBUG Canceling task: 3574 / 0x4d5c9e8
Jul 07 20:54:21-441075 util-scheduler-8620 DEBUG Adding task: 3576 / 0x4d5c9e8
Jul 07 20:54:21-441314 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:21-441509 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:21-441707 util-scheduler-8620 DEBUG Adding task: 3577 / 0x46620a0
Jul 07 20:54:21-441945 util-scheduler-8620 DEBUG Checking readiness of task: 3577 / 0x46620a0
Jul 07 20:54:21-442137 util-scheduler-8620 DEBUG Checking readiness of task: 3571 / 0x46620a0
Jul 07 20:54:21-442327 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-442516 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-442705 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-442894 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-443083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-443271 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-443460 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-443650 util-scheduler-8620 DEBUG Running task: 3577 / 0x46620a0
Jul 07 20:54:21-443835 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-444009 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-444177 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-444352 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:21-444541 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:21-444727 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:21-444968 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:21-887573 util-scheduler-8620 DEBUG Checking readiness of task: 3571 / 0x46620a0
Jul 07 20:54:21-887857 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-888075 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-888267 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-888458 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-888650 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-888839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-889029 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-889257 util-scheduler-8620 DEBUG Running task: 3571 / 0x46620a0
Jul 07 20:54:21-889670 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:21-889913 util-scheduler-8620 DEBUG Adding task: 3578 / 0x4662248
Jul 07 20:54:21-890176 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-890368 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-890559 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-890749 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-890938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-891127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-891315 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-891505 util-scheduler-8620 DEBUG Running task: 3578 / 0x4662248
Jul 07 20:54:21-891694 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:21-891890 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:21-892112 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:21-892314 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:21-892516 util-scheduler-8620 DEBUG Adding task: 3579 / 0x46620a0
Jul 07 20:54:21-892701 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:21-892902 util-scheduler-8620 DEBUG Adding task: 3580 / 0x46620a0
Jul 07 20:54:21-893144 util-scheduler-8620 DEBUG Checking readiness of task: 3580 / 0x46620a0
Jul 07 20:54:21-893367 util-scheduler-8620 DEBUG Checking readiness of task: 3579 / 0x46620a0
Jul 07 20:54:21-893559 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:21-893749 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:21-893938 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:21-894129 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:21-894318 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:21-894506 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:21-894694 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:21-894885 util-scheduler-8620 DEBUG Running task: 3579 / 0x46620a0
Jul 07 20:54:21-895081 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:21-895260 util-8620 DEBUG process_notify is running
Jul 07 20:54:21-895431 util-8620 DEBUG client_notify is running
Jul 07 20:54:21-895616 util-scheduler-8620 DEBUG Canceling task: 3576 / 0x4d5c9e8
Jul 07 20:54:21-895837 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 80 bytes.
Jul 07 20:54:21-896054 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:21-896288 cadet-p2p-8620 DEBUG Checking 0x5df8608 towards M9KEP6HP (->P00P)
Jul 07 20:54:21-896520 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:21-896697 cadet-p2p-8620 DEBUG   size 80 ok
Jul 07 20:54:21-896886 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:21-897168 cadet-p2p-8620 INFO snd {                KX} ({           KX_PING} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 80)
Jul 07 20:54:21-897404 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:21-897601 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:21-897790 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:54:21-897978 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:21-898155 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:54:21-898338 util-scheduler-8620 DEBUG Canceling task: 3572 / 0x53a5de0
Jul 07 20:54:21-898548 util-scheduler-8620 DEBUG Adding task: 3581 / 0x53a5de0
Jul 07 20:54:21-898793 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:21-898964 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:21-899145 cadet-p2p-8620 DEBUG   return 80
Jul 07 20:54:21-899345 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:21-899519 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:21-899692 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:21-899891 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:21-900094 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 80 bytes.
Jul 07 20:54:21-900276 core-api-8620 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 20:54:21-900454 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:21-900643 util-8620 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 20:54:21-900893 util-8620 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:23-035808 util-scheduler-8620 DEBUG Checking readiness of task: 3580 / 0x46620a0
Jul 07 20:54:23-036170 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-036368 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-036563 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-036756 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-036950 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-037143 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-037364 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-037563 util-scheduler-8620 DEBUG Running task: 3580 / 0x46620a0
Jul 07 20:54:23-037991 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:23-038247 util-scheduler-8620 DEBUG Adding task: 3582 / 0x4662248
Jul 07 20:54:23-038527 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-038722 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-038916 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-039109 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-039321 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-039513 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-039705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-039896 util-scheduler-8620 DEBUG Running task: 3582 / 0x4662248
Jul 07 20:54:23-040089 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:54:23-040291 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:54:23-040521 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `KNAS'
Jul 07 20:54:23-040781 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection M9KEP6HP from KNAS
Jul 07 20:54:23-040995 cadet-con-8620 DEBUG   via peer KNAS
Jul 07 20:54:23-041259 cadet-con-8620 DEBUG  get next hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:23-041470 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:54:23-041712 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:23-041921 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:23-042104 cadet-con-8620 DEBUG   ACK
Jul 07 20:54:23-042334 cadet-con-8620 DEBUG Connection M9KEP6HP (->P00P) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 20:54:23-042551 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:23-042742 util-scheduler-8620 DEBUG Canceling task: 3563 / 0x53a5de0
Jul 07 20:54:23-042966 util-scheduler-8620 DEBUG Adding task: 3583 / 0x53a5de0
Jul 07 20:54:23-043151 cadet-con-8620 DEBUG   Connection ACK for us!
Jul 07 20:54:23-043332 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:23-043543 util-scheduler-8620 DEBUG Adding task: 3584 / 0x46620a0
Jul 07 20:54:23-099591 util-scheduler-8620 DEBUG Checking readiness of task: 3584 / 0x46620a0
Jul 07 20:54:23-099818 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-100015 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-100336 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-100556 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-100750 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-100956 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-101166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-101390 util-scheduler-8620 DEBUG Running task: 3584 / 0x46620a0
Jul 07 20:54:23-101810 util-8620 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:23-102056 util-scheduler-8620 DEBUG Adding task: 3585 / 0x4662248
Jul 07 20:54:23-102322 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-102515 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-102706 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-102895 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-103114 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-103319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-103521 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-103725 util-scheduler-8620 DEBUG Running task: 3585 / 0x4662248
Jul 07 20:54:23-103914 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:54:23-104111 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:54:23-104328 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `KNAS'
Jul 07 20:54:23-104576 cadet-con-8620 INFO <-- {                KX} on connection M9KEP6HP from KNAS
Jul 07 20:54:23-104811 cadet-con-8620 DEBUG  on connection M9KEP6HP (->P00P)
Jul 07 20:54:23-105039 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:23-105267 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:23-105464 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:23-105649 util-scheduler-8620 DEBUG Canceling task: 3583 / 0x53a5de0
Jul 07 20:54:23-105865 util-scheduler-8620 DEBUG Adding task: 3586 / 0x53a5de0
Jul 07 20:54:23-106045 cadet-con-8620 DEBUG   message for us!
Jul 07 20:54:23-106304 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:54:23-106515 util-scheduler-8620 DEBUG Adding task: 3587 / 0x4d5e5d8
Jul 07 20:54:23-106697 cadet-tun-8620 DEBUG kx message received
Jul 07 20:54:23-106895 cadet-tun-8620 INFO <=== PING for P00P
Jul 07 20:54:23-107081 cadet-tun-8620 DEBUG   t_decrypt with X5GG98S2
Jul 07 20:54:23-107253 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:54:23-107420 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:54:23-110981 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:54:23-111810 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:54:23-112028 cadet-tun-8620 INFO ===> PONG for P00P
Jul 07 20:54:23-112320 cadet-tun-8620 DEBUG   sending 2466691451
Jul 07 20:54:23-112496 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:54:23-112680 cadet-tun-8620 INFO   ENC with key 1BR3R993
Jul 07 20:54:23-116251 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:54:23-116844 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:54:23-117027 cadet-tun-8620 DEBUG   e sending 3758070893
Jul 07 20:54:23-117254 cadet-tun-8620 DEBUG GMT KX on Tunnel P00P
Jul 07 20:54:23-117458 cadet-tun-8620 DEBUG tunnel_get_connection P00P
Jul 07 20:54:23-117685 cadet-tun-8620 DEBUG   connection M9KEP6HP (->P00P): 3
Jul 07 20:54:23-117864 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:23-118085 cadet-tun-8620 DEBUG  selected: connection M9KEP6HP (->P00P)
Jul 07 20:54:23-118361 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (48 bytes)
Jul 07 20:54:23-118559 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 0
Jul 07 20:54:23-118796 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:23-119004 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:23-119313 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 48)
Jul 07 20:54:23-119512 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:23-119737 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:23-119920 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:23-120096 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:23-120302 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 48 bytes
Jul 07 20:54:23-120516 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `KNAS'
Jul 07 20:54:23-120739 util-scheduler-8620 DEBUG Adding task: 3588 / 0x4d5c9e8
Jul 07 20:54:23-120919 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:23-121122 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:23-121320 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:23-121495 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:23-121734 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:23-121929 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:54:23-122106 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:54:23-122304 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:23-122511 util-scheduler-8620 DEBUG Adding task: 3589 / 0x4662248
Jul 07 20:54:23-122773 util-scheduler-8620 DEBUG Checking readiness of task: 3587 / 0x4d5e5d8
Jul 07 20:54:23-122970 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-123160 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-123350 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-123539 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-123727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-123916 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-124104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-124295 util-scheduler-8620 DEBUG Running task: 3587 / 0x4d5e5d8
Jul 07 20:54:23-124480 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:54:23-124658 util-8620 DEBUG process_notify is running
Jul 07 20:54:23-124830 util-8620 DEBUG client_notify is running
Jul 07 20:54:23-125057 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:54:23-125337 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:54:23-125552 util-scheduler-8620 DEBUG Running task: 3589 / 0x4662248
Jul 07 20:54:23-125740 util-8620 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 20:54:23-125933 core-api-8620 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 20:54:23-126148 core-api-8620 DEBUG Received message of type 262 and size 48 from peer `KNAS'
Jul 07 20:54:23-126394 cadet-con-8620 INFO <-- {                KX} on connection M9KEP6HP from KNAS
Jul 07 20:54:23-126625 cadet-con-8620 DEBUG  on connection M9KEP6HP (->P00P)
Jul 07 20:54:23-126881 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:23-127088 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:23-127278 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:23-127465 util-scheduler-8620 DEBUG Canceling task: 3586 / 0x53a5de0
Jul 07 20:54:23-127686 util-scheduler-8620 DEBUG Adding task: 3590 / 0x53a5de0
Jul 07 20:54:23-127865 cadet-con-8620 DEBUG   message for us!
Jul 07 20:54:23-128107 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:54:23-128319 util-scheduler-8620 DEBUG Adding task: 3591 / 0x4d5e5d8
Jul 07 20:54:23-128500 cadet-tun-8620 DEBUG kx message received
Jul 07 20:54:23-128696 cadet-tun-8620 INFO <=== PONG for P00P
Jul 07 20:54:23-128881 cadet-tun-8620 DEBUG   t_decrypt with X5GG98S2
Jul 07 20:54:23-129051 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:54:23-129234 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:54:23-132343 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:54:23-132929 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:54:23-133117 util-scheduler-8620 DEBUG Canceling task: 3551 / 0x53a63f8
Jul 07 20:54:23-133370 util-scheduler-8620 DEBUG Adding task: 3592 / 0x53a63f8
Jul 07 20:54:23-133587 cadet-tun-8620 DEBUG Tunnel P00P estate was CADET_TUNNEL_KEY_PING
Jul 07 20:54:23-133794 cadet-tun-8620 DEBUG Tunnel P00P estate is now CADET_TUNNEL_KEY_OK
Jul 07 20:54:23-133998 cadet-tun-8620 DEBUG GCT_send_queued_data on tunnel P00P
Jul 07 20:54:23-134201 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:54:23-134381 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:54:23-134565 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5ada570, rekey_task 0
Jul 07 20:54:23-134745 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:54:23-134921 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:54:23-135104 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:54:23-135270 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:54:23-135507 cadet-tun-8620 DEBUG TTT  - M9KEP6HP (->P00P) [3] buf: 11/11 (qn 0/0)
Jul 07 20:54:23-135691 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:54:23-135891 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:54:23-136067 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:54:23-136248 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5ada570, rekey_task 0
Jul 07 20:54:23-136426 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:54:23-136600 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:54:23-136768 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:54:23-136932 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:54:23-137159 cadet-tun-8620 DEBUG TTT  - M9KEP6HP (->P00P) [3] buf: 11/11 (qn 0/0)
Jul 07 20:54:23-137363 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:54:23-137538 cadet-tun-8620 DEBUG   buffer space: 11
Jul 07 20:54:23-137711 cadet-tun-8620 DEBUG   tq head: (nil)
Jul 07 20:54:23-138080 cadet-tun-8620 DEBUG GCT_send_queued_data end
Jul 07 20:54:23-138263 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:23-138471 util-scheduler-8620 DEBUG Adding task: 3593 / 0x46620a0
Jul 07 20:54:23-138672 util-scheduler-8620 DEBUG Running task: 3588 / 0x4d5c9e8
Jul 07 20:54:23-138880 util-scheduler-8620 DEBUG Adding task: 3594 / 0x4d5c9e8
Jul 07 20:54:23-139102 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:23-139299 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:23-139496 util-scheduler-8620 DEBUG Adding task: 3595 / 0x46620a0
Jul 07 20:54:23-139749 util-scheduler-8620 DEBUG Checking readiness of task: 3595 / 0x46620a0
Jul 07 20:54:23-139943 util-scheduler-8620 DEBUG Checking readiness of task: 3593 / 0x46620a0
Jul 07 20:54:23-140133 util-scheduler-8620 DEBUG Checking readiness of task: 3591 / 0x4d5e5d8
Jul 07 20:54:23-140324 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-140514 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-140704 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-140915 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-141104 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-141315 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-141504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-141695 util-scheduler-8620 DEBUG Running task: 3591 / 0x4d5e5d8
Jul 07 20:54:23-141879 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:54:23-142055 util-8620 DEBUG process_notify is running
Jul 07 20:54:23-142225 util-8620 DEBUG client_notify is running
Jul 07 20:54:23-142443 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:54:23-142698 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:54:23-142909 util-scheduler-8620 DEBUG Running task: 3595 / 0x46620a0
Jul 07 20:54:23-143092 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:23-143266 util-8620 DEBUG process_notify is running
Jul 07 20:54:23-143435 util-8620 DEBUG client_notify is running
Jul 07 20:54:23-143613 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:23-143806 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:23-143995 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:23-144236 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:23-809847 util-scheduler-8620 DEBUG Checking readiness of task: 3593 / 0x46620a0
Jul 07 20:54:23-810202 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-810398 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-810592 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-810784 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-810977 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-811168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-811358 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-811554 util-scheduler-8620 DEBUG Running task: 3593 / 0x46620a0
Jul 07 20:54:23-811973 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:23-812226 util-scheduler-8620 DEBUG Adding task: 3596 / 0x4662248
Jul 07 20:54:23-812502 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-812696 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-812887 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-813078 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-813320 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-813511 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-813700 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-813890 util-scheduler-8620 DEBUG Running task: 3596 / 0x4662248
Jul 07 20:54:23-814081 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:23-814280 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:23-814529 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:23-814736 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:23-814944 util-scheduler-8620 DEBUG Adding task: 3597 / 0x46620a0
Jul 07 20:54:23-815131 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:23-815335 util-scheduler-8620 DEBUG Adding task: 3598 / 0x46620a0
Jul 07 20:54:23-815580 util-scheduler-8620 DEBUG Checking readiness of task: 3598 / 0x46620a0
Jul 07 20:54:23-815801 util-scheduler-8620 DEBUG Checking readiness of task: 3597 / 0x46620a0
Jul 07 20:54:23-815993 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:23-816184 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:23-816374 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:23-816565 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:23-816755 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:23-816943 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:23-817132 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:23-817352 util-scheduler-8620 DEBUG Running task: 3597 / 0x46620a0
Jul 07 20:54:23-817539 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:23-817716 util-8620 DEBUG process_notify is running
Jul 07 20:54:23-817888 util-8620 DEBUG client_notify is running
Jul 07 20:54:23-818075 util-scheduler-8620 DEBUG Canceling task: 3594 / 0x4d5c9e8
Jul 07 20:54:23-818298 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 48 bytes.
Jul 07 20:54:23-818519 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:23-818756 cadet-p2p-8620 DEBUG Checking 0x5e05808 towards M9KEP6HP (->P00P)
Jul 07 20:54:23-818990 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:23-819167 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:54:23-819358 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:23-819642 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 48)
Jul 07 20:54:23-819836 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:23-820016 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:23-820203 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:54:23-820392 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:23-820569 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:54:23-820752 util-scheduler-8620 DEBUG Canceling task: 3581 / 0x53a5de0
Jul 07 20:54:23-820963 util-scheduler-8620 DEBUG Adding task: 3599 / 0x53a5de0
Jul 07 20:54:23-821238 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:23-821411 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:23-821593 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:54:23-821792 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:23-821966 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:23-822153 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:23-822355 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:23-822560 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 48 bytes.
Jul 07 20:54:23-822742 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:54:23-822921 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:23-823111 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:54:23-823362 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:25-309246 util-scheduler-8620 DEBUG Checking readiness of task: 3598 / 0x46620a0
Jul 07 20:54:25-309613 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-309811 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-310004 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-310197 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-310408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-310651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-310845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-311042 util-scheduler-8620 DEBUG Running task: 3598 / 0x46620a0
Jul 07 20:54:25-311481 util-8620 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:25-311765 util-scheduler-8620 DEBUG Adding task: 3600 / 0x4662248
Jul 07 20:54:25-312042 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-312235 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-312445 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-312636 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-312827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-313016 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-313232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-313425 util-scheduler-8620 DEBUG Running task: 3600 / 0x4662248
Jul 07 20:54:25-313636 util-8620 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 20:54:25-313836 core-api-8620 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 20:54:25-314065 core-api-8620 DEBUG Received message of type 262 and size 196 from peer `KNAS'
Jul 07 20:54:25-314327 cadet-con-8620 INFO <-- {                KX} on connection M9KEP6HP from KNAS
Jul 07 20:54:25-314584 cadet-con-8620 DEBUG  on connection M9KEP6HP (->P00P)
Jul 07 20:54:25-314816 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:25-315024 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:25-315221 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:25-315408 util-scheduler-8620 DEBUG Canceling task: 3590 / 0x53a5de0
Jul 07 20:54:25-315648 util-scheduler-8620 DEBUG Adding task: 3601 / 0x53a5de0
Jul 07 20:54:25-315828 cadet-con-8620 DEBUG   message for us!
Jul 07 20:54:25-316089 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:54:25-316305 util-scheduler-8620 DEBUG Adding task: 3602 / 0x4d5e5d8
Jul 07 20:54:25-316488 cadet-tun-8620 DEBUG kx message received
Jul 07 20:54:25-316705 cadet-tun-8620 INFO <=== EPHM for P00P
Jul 07 20:54:25-916286 util-scheduler-8620 DEBUG Canceling task: 3592 / 0x53a63f8
Jul 07 20:54:25-916725 util-scheduler-8620 DEBUG Adding task: 3603 / 0x53a63f8
Jul 07 20:54:25-916925 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:25-917143 util-scheduler-8620 DEBUG Adding task: 3604 / 0x46620a0
Jul 07 20:54:25-917449 util-scheduler-8620 DEBUG Checking readiness of task: 3604 / 0x46620a0
Jul 07 20:54:25-917650 util-scheduler-8620 DEBUG Checking readiness of task: 3602 / 0x4d5e5d8
Jul 07 20:54:25-917844 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-918034 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-918225 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-918416 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-918608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-918797 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-918987 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-919181 util-scheduler-8620 DEBUG Running task: 3602 / 0x4d5e5d8
Jul 07 20:54:25-919368 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:54:25-919549 util-8620 DEBUG process_notify is running
Jul 07 20:54:25-919722 util-8620 DEBUG client_notify is running
Jul 07 20:54:25-919959 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:54:25-920229 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:54:25-920441 util-scheduler-8620 DEBUG Running task: 3604 / 0x46620a0
Jul 07 20:54:25-920849 util-8620 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:25-921083 util-scheduler-8620 DEBUG Adding task: 3605 / 0x4662248
Jul 07 20:54:25-921345 util-scheduler-8620 DEBUG Running task: 3557 / 0x52cbfb8
Jul 07 20:54:25-921570 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:25-921825 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:25-922034 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:25-922235 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:25-922438 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:25-922670 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:25-922851 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:25-923074 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:25-923361 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:25-923560 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:25-923796 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:25-924005 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:25-924318 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:25-924519 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:25-924744 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:25-924929 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:25-925106 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:25-925340 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:25-925556 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:25-925770 util-scheduler-8620 DEBUG Adding task: 3606 / 0x59ee8a0
Jul 07 20:54:25-925949 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:25-926158 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:25-926334 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:25-926522 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:25-926762 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:25-926958 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:25-927136 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:25-927335 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:25-927577 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:25-927777 util-scheduler-8620 DEBUG Adding task: 3607 / 0x52cbfb8
Jul 07 20:54:25-928021 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-928215 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-928405 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-928598 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-928788 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-928977 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-929166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-929378 util-scheduler-8620 DEBUG Running task: 3606 / 0x59ee8a0
Jul 07 20:54:25-929587 util-scheduler-8620 DEBUG Adding task: 3608 / 0x59ee8a0
Jul 07 20:54:25-929810 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:25-930014 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:25-930218 util-scheduler-8620 DEBUG Adding task: 3609 / 0x46620a0
Jul 07 20:54:25-930416 util-scheduler-8620 DEBUG Running task: 3605 / 0x4662248
Jul 07 20:54:25-930607 util-8620 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 20:54:25-930804 core-api-8620 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 20:54:25-931031 core-api-8620 DEBUG Received message of type 262 and size 80 from peer `KNAS'
Jul 07 20:54:25-931281 cadet-con-8620 INFO <-- {                KX} on connection M9KEP6HP from KNAS
Jul 07 20:54:25-931517 cadet-con-8620 DEBUG  on connection M9KEP6HP (->P00P)
Jul 07 20:54:25-931767 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:25-931976 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:25-932170 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:25-932356 util-scheduler-8620 DEBUG Canceling task: 3601 / 0x53a5de0
Jul 07 20:54:25-932574 util-scheduler-8620 DEBUG Adding task: 3610 / 0x53a5de0
Jul 07 20:54:25-932754 cadet-con-8620 DEBUG   message for us!
Jul 07 20:54:25-932999 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:54:25-933223 util-scheduler-8620 DEBUG Adding task: 3611 / 0x4d5e5d8
Jul 07 20:54:25-933405 cadet-tun-8620 DEBUG kx message received
Jul 07 20:54:25-933602 cadet-tun-8620 INFO <=== PING for P00P
Jul 07 20:54:25-933789 cadet-tun-8620 DEBUG   t_decrypt with X5GG98S2
Jul 07 20:54:25-933961 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:54:25-934128 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:54:25-937717 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:54:25-938638 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:54:25-938870 cadet-tun-8620 INFO ===> PONG for P00P
Jul 07 20:54:25-939167 cadet-tun-8620 DEBUG   sending 2466691451
Jul 07 20:54:25-939343 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:54:25-939530 cadet-tun-8620 INFO   ENC with key 1BR3R993
Jul 07 20:54:25-942636 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:54:25-943774 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:54:25-944035 cadet-tun-8620 DEBUG   e sending 2664150546
Jul 07 20:54:25-944240 cadet-tun-8620 DEBUG GMT KX on Tunnel P00P
Jul 07 20:54:25-944443 cadet-tun-8620 DEBUG tunnel_get_connection P00P
Jul 07 20:54:25-944672 cadet-tun-8620 DEBUG   connection M9KEP6HP (->P00P): 3
Jul 07 20:54:25-944853 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:25-945073 cadet-tun-8620 DEBUG  selected: connection M9KEP6HP (->P00P)
Jul 07 20:54:25-945373 cadet-con-8620 INFO --> {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (48 bytes)
Jul 07 20:54:25-945573 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 0
Jul 07 20:54:25-945808 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:54:25-946016 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:54:25-946328 cadet-p2p-8620 INFO que {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 48)
Jul 07 20:54:25-946528 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:25-946752 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:54:25-946935 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:25-947110 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:25-947315 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 48 bytes
Jul 07 20:54:25-947530 core-api-8620 DEBUG Asking core for transmission of 48 bytes to `KNAS'
Jul 07 20:54:25-947753 util-scheduler-8620 DEBUG Adding task: 3612 / 0x4d5c9e8
Jul 07 20:54:25-947935 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:25-948139 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:25-948316 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:25-948491 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:54:25-948729 cadet-p2p-8620 DEBUG QQQ  - {                KX} BCK on M9KEP6HP (->P00P)
Jul 07 20:54:25-948925 cadet-p2p-8620 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 20:54:25-949103 cadet-p2p-8620 DEBUG QQQ    size: 48 bytes
Jul 07 20:54:25-949321 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:25-949504 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:25-949712 util-scheduler-8620 DEBUG Adding task: 3613 / 0x46620a0
Jul 07 20:54:25-949977 util-scheduler-8620 DEBUG Checking readiness of task: 3613 / 0x46620a0
Jul 07 20:54:25-950174 util-scheduler-8620 DEBUG Checking readiness of task: 3611 / 0x4d5e5d8
Jul 07 20:54:25-950367 util-scheduler-8620 DEBUG Checking readiness of task: 3609 / 0x46620a0
Jul 07 20:54:25-950558 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-950749 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-950962 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-951152 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-951342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-951532 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-951721 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-951916 util-scheduler-8620 DEBUG Running task: 3609 / 0x46620a0
Jul 07 20:54:25-952102 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:25-952280 util-8620 DEBUG process_notify is running
Jul 07 20:54:25-952452 util-8620 DEBUG client_notify is running
Jul 07 20:54:25-952631 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:25-952828 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:25-953020 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:25-953298 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:25-953509 util-scheduler-8620 DEBUG Running task: 3611 / 0x4d5e5d8
Jul 07 20:54:25-953694 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:54:25-953869 util-8620 DEBUG process_notify is running
Jul 07 20:54:25-954039 util-8620 DEBUG client_notify is running
Jul 07 20:54:25-954260 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:54:25-954508 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:54:25-954716 util-scheduler-8620 DEBUG Running task: 3612 / 0x4d5c9e8
Jul 07 20:54:25-954925 util-scheduler-8620 DEBUG Adding task: 3614 / 0x4d5c9e8
Jul 07 20:54:25-955146 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:54:25-955345 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:25-955545 util-scheduler-8620 DEBUG Adding task: 3615 / 0x46620a0
Jul 07 20:54:25-955786 util-scheduler-8620 DEBUG Checking readiness of task: 3615 / 0x46620a0
Jul 07 20:54:25-955981 util-scheduler-8620 DEBUG Checking readiness of task: 3613 / 0x46620a0
Jul 07 20:54:25-956175 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-956365 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-956557 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-956746 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-956937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-957136 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-957345 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-957536 util-scheduler-8620 DEBUG Running task: 3613 / 0x46620a0
Jul 07 20:54:25-957943 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:25-958171 util-scheduler-8620 DEBUG Adding task: 3616 / 0x4662248
Jul 07 20:54:25-958380 util-scheduler-8620 DEBUG Running task: 3615 / 0x46620a0
Jul 07 20:54:25-958567 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:25-958741 util-8620 DEBUG process_notify is running
Jul 07 20:54:25-958912 util-8620 DEBUG client_notify is running
Jul 07 20:54:25-959088 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:25-959276 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:25-959466 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:25-959709 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:25-959955 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-960165 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-960357 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-960548 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-960740 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-960930 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-961120 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-961336 util-scheduler-8620 DEBUG Running task: 3616 / 0x4662248
Jul 07 20:54:25-961528 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:25-961723 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:25-961940 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:25-962139 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:25-962338 util-scheduler-8620 DEBUG Adding task: 3617 / 0x46620a0
Jul 07 20:54:25-962522 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:25-962720 util-scheduler-8620 DEBUG Adding task: 3618 / 0x46620a0
Jul 07 20:54:25-962962 util-scheduler-8620 DEBUG Checking readiness of task: 3618 / 0x46620a0
Jul 07 20:54:25-963155 util-scheduler-8620 DEBUG Checking readiness of task: 3617 / 0x46620a0
Jul 07 20:54:25-963379 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:25-963571 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:25-963762 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:25-963954 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:25-964144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:25-964333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:25-964522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:25-964712 util-scheduler-8620 DEBUG Running task: 3617 / 0x46620a0
Jul 07 20:54:25-964897 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:25-965071 util-8620 DEBUG process_notify is running
Jul 07 20:54:25-965261 util-8620 DEBUG client_notify is running
Jul 07 20:54:25-965446 util-scheduler-8620 DEBUG Canceling task: 3608 / 0x59ee8a0
Jul 07 20:54:25-965671 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:25-965890 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:25-966128 cadet-p2p-8620 DEBUG Checking 0x60502a8 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:25-966362 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:25-966541 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:25-966730 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:25-967017 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:25-967212 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:25-967392 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:25-967581 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:25-967771 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:25-967951 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:25-968134 util-scheduler-8620 DEBUG Canceling task: 3568 / 0x59e8808
Jul 07 20:54:25-968347 util-scheduler-8620 DEBUG Adding task: 3619 / 0x59e8808
Jul 07 20:54:25-968596 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:25-968768 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:25-968949 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:25-969151 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:25-969347 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:25-969522 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:25-969721 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:25-969944 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:25-970130 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:25-970308 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:25-970499 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:25-970747 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:26-860631 util-scheduler-8620 DEBUG Checking readiness of task: 3618 / 0x46620a0
Jul 07 20:54:26-861012 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:26-861239 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:26-861436 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:26-861650 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:26-861844 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:26-862035 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:26-862225 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:26-862420 util-scheduler-8620 DEBUG Running task: 3618 / 0x46620a0
Jul 07 20:54:26-862849 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:26-863107 util-scheduler-8620 DEBUG Adding task: 3620 / 0x4662248
Jul 07 20:54:26-863389 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:26-863585 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:26-863776 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:26-863968 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:26-864159 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:26-864349 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:26-864538 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:26-864727 util-scheduler-8620 DEBUG Running task: 3620 / 0x4662248
Jul 07 20:54:26-864919 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:26-865119 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:26-865374 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:54:26-865582 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:26-865792 util-scheduler-8620 DEBUG Adding task: 3621 / 0x46620a0
Jul 07 20:54:26-865981 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:26-866186 util-scheduler-8620 DEBUG Adding task: 3622 / 0x46620a0
Jul 07 20:54:26-866434 util-scheduler-8620 DEBUG Checking readiness of task: 3622 / 0x46620a0
Jul 07 20:54:26-866629 util-scheduler-8620 DEBUG Checking readiness of task: 3621 / 0x46620a0
Jul 07 20:54:26-866822 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:26-867012 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:26-867204 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:26-867393 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:26-867585 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:26-867774 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:26-867963 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:26-868154 util-scheduler-8620 DEBUG Running task: 3621 / 0x46620a0
Jul 07 20:54:26-868340 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:26-868532 util-8620 DEBUG process_notify is running
Jul 07 20:54:26-868707 util-8620 DEBUG client_notify is running
Jul 07 20:54:26-868895 util-scheduler-8620 DEBUG Canceling task: 3614 / 0x4d5c9e8
Jul 07 20:54:26-869152 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 48 bytes.
Jul 07 20:54:26-869400 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:54:26-869643 cadet-p2p-8620 DEBUG Checking 0x59a9568 towards M9KEP6HP (->P00P)
Jul 07 20:54:26-869880 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:54:26-870059 cadet-p2p-8620 DEBUG   size 48 ok
Jul 07 20:54:26-870250 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:26-870538 cadet-p2p-8620 INFO snd {                KX} ({           KX_PONG} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 48)
Jul 07 20:54:26-870735 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:26-870915 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:26-871103 cadet-con-8620 DEBUG  sent BCK {                KX}
Jul 07 20:54:26-871293 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:54:26-871472 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:54:26-871656 util-scheduler-8620 DEBUG Canceling task: 3599 / 0x53a5de0
Jul 07 20:54:26-871871 util-scheduler-8620 DEBUG Adding task: 3623 / 0x53a5de0
Jul 07 20:54:26-872122 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:26-872294 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:26-872474 cadet-p2p-8620 DEBUG   return 48
Jul 07 20:54:26-872677 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:54:26-872853 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:26-873027 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:26-873250 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:54:26-873457 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 48 bytes.
Jul 07 20:54:26-873642 core-api-8620 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 20:54:26-873821 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:26-874012 util-8620 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 20:54:26-874262 util-8620 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:30-931996 util-scheduler-8620 DEBUG Checking readiness of task: 3622 / 0x46620a0
Jul 07 20:54:30-932391 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-933073 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-933335 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-933586 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-933783 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-933977 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-934172 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-934368 util-scheduler-8620 DEBUG Running task: 3607 / 0x52cbfb8
Jul 07 20:54:30-934608 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:30-934867 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:30-935077 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:30-935279 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:30-935483 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:30-935720 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:30-935902 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:30-936125 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:30-936419 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:30-936617 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:30-936856 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:30-937066 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:30-937408 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:30-937612 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:30-937838 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:30-938061 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:30-938239 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:30-938447 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:30-938662 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:30-938887 util-scheduler-8620 DEBUG Adding task: 3624 / 0x59ee8a0
Jul 07 20:54:30-939068 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:30-939271 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:30-939448 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:30-939622 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:30-939860 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:30-940058 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:30-940235 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:30-940432 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:30-940677 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:30-940873 util-scheduler-8620 DEBUG Adding task: 3625 / 0x52cbfb8
Jul 07 20:54:30-941132 util-scheduler-8620 DEBUG Checking readiness of task: 3622 / 0x46620a0
Jul 07 20:54:30-941349 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-941539 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-941734 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-941924 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-942114 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-942303 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-942492 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-942680 util-scheduler-8620 DEBUG Running task: 3624 / 0x59ee8a0
Jul 07 20:54:30-942888 util-scheduler-8620 DEBUG Adding task: 3626 / 0x59ee8a0
Jul 07 20:54:30-943109 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:30-943314 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:30-943523 util-scheduler-8620 DEBUG Adding task: 3627 / 0x46620a0
Jul 07 20:54:30-943765 util-scheduler-8620 DEBUG Checking readiness of task: 3627 / 0x46620a0
Jul 07 20:54:30-943960 util-scheduler-8620 DEBUG Checking readiness of task: 3622 / 0x46620a0
Jul 07 20:54:30-944150 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-944344 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-944533 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-944722 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-944911 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-945100 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-945308 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-945500 util-scheduler-8620 DEBUG Running task: 3627 / 0x46620a0
Jul 07 20:54:30-945685 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:30-945863 util-8620 DEBUG process_notify is running
Jul 07 20:54:30-946035 util-8620 DEBUG client_notify is running
Jul 07 20:54:30-946215 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:30-946410 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:30-946602 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:30-946857 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:30-947107 util-scheduler-8620 DEBUG Checking readiness of task: 3622 / 0x46620a0
Jul 07 20:54:30-947301 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-947510 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-947703 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-947893 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-948095 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-948284 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-948474 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-948664 util-scheduler-8620 DEBUG Running task: 3622 / 0x46620a0
Jul 07 20:54:30-949068 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:30-949317 util-scheduler-8620 DEBUG Adding task: 3628 / 0x4662248
Jul 07 20:54:30-949565 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-949757 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-949949 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-950139 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-950329 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-950519 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-950708 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-950896 util-scheduler-8620 DEBUG Running task: 3628 / 0x4662248
Jul 07 20:54:30-951086 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:30-951282 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:30-951498 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:30-951696 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:30-951893 util-scheduler-8620 DEBUG Adding task: 3629 / 0x46620a0
Jul 07 20:54:30-952078 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:30-952283 util-scheduler-8620 DEBUG Adding task: 3630 / 0x46620a0
Jul 07 20:54:30-952523 util-scheduler-8620 DEBUG Checking readiness of task: 3630 / 0x46620a0
Jul 07 20:54:30-952716 util-scheduler-8620 DEBUG Checking readiness of task: 3629 / 0x46620a0
Jul 07 20:54:30-952908 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:30-953098 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:30-953307 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:30-953498 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:30-953688 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:30-953878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:30-954066 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:30-954260 util-scheduler-8620 DEBUG Running task: 3629 / 0x46620a0
Jul 07 20:54:30-954444 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:30-954619 util-8620 DEBUG process_notify is running
Jul 07 20:54:30-954788 util-8620 DEBUG client_notify is running
Jul 07 20:54:30-954974 util-scheduler-8620 DEBUG Canceling task: 3626 / 0x59ee8a0
Jul 07 20:54:30-955197 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:30-955415 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:30-955646 cadet-p2p-8620 DEBUG Checking 0x6067b10 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:30-955880 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:30-956058 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:30-956247 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:30-956533 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:30-956729 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:30-956923 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:30-957112 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:30-957321 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:30-957501 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:30-957683 util-scheduler-8620 DEBUG Canceling task: 3619 / 0x59e8808
Jul 07 20:54:30-957896 util-scheduler-8620 DEBUG Adding task: 3631 / 0x59e8808
Jul 07 20:54:30-958143 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:30-958330 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:30-958513 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:30-958717 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:30-958892 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:30-959066 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:30-959264 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:30-959469 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:30-959654 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:30-959832 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:30-960021 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:30-960265 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:35-943147 util-scheduler-8620 DEBUG Checking readiness of task: 3630 / 0x46620a0
Jul 07 20:54:35-943542 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-944009 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-944249 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-944489 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-944685 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-944875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-945065 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-945285 util-scheduler-8620 DEBUG Running task: 3625 / 0x52cbfb8
Jul 07 20:54:35-945525 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:35-945783 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:35-945990 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:35-946191 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:35-946392 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:35-946630 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:35-946811 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:35-947034 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:35-947326 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:35-947524 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:35-947762 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:35-947972 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:35-948292 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:35-948508 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:35-948734 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:35-948917 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:35-949093 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:35-949320 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:35-949535 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:35-949760 util-scheduler-8620 DEBUG Adding task: 3632 / 0x59ee8a0
Jul 07 20:54:35-949941 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:35-950146 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:35-950324 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:35-950524 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:35-950764 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:35-950960 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:35-951156 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:35-951359 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:35-951605 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:35-951804 util-scheduler-8620 DEBUG Adding task: 3633 / 0x52cbfb8
Jul 07 20:54:35-952064 util-scheduler-8620 DEBUG Checking readiness of task: 3630 / 0x46620a0
Jul 07 20:54:35-952258 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-952451 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-952656 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-952847 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-953038 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-953246 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-953438 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-953628 util-scheduler-8620 DEBUG Running task: 3632 / 0x59ee8a0
Jul 07 20:54:35-953837 util-scheduler-8620 DEBUG Adding task: 3634 / 0x59ee8a0
Jul 07 20:54:35-954059 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:35-954262 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:35-954470 util-scheduler-8620 DEBUG Adding task: 3635 / 0x46620a0
Jul 07 20:54:35-954713 util-scheduler-8620 DEBUG Checking readiness of task: 3635 / 0x46620a0
Jul 07 20:54:35-954907 util-scheduler-8620 DEBUG Checking readiness of task: 3630 / 0x46620a0
Jul 07 20:54:35-955098 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-955292 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-955483 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-955672 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-955861 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-956051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-956240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-956432 util-scheduler-8620 DEBUG Running task: 3635 / 0x46620a0
Jul 07 20:54:35-956617 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:35-956795 util-8620 DEBUG process_notify is running
Jul 07 20:54:35-956969 util-8620 DEBUG client_notify is running
Jul 07 20:54:35-957146 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:35-957362 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:35-957556 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:35-957811 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:35-958059 util-scheduler-8620 DEBUG Checking readiness of task: 3630 / 0x46620a0
Jul 07 20:54:35-958252 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-958442 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-958632 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-958823 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-959013 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-959203 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-959391 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-959582 util-scheduler-8620 DEBUG Running task: 3630 / 0x46620a0
Jul 07 20:54:35-960001 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:35-960231 util-scheduler-8620 DEBUG Adding task: 3636 / 0x4662248
Jul 07 20:54:35-960479 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-960672 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-960863 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-961052 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-961261 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-961452 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-961642 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-961832 util-scheduler-8620 DEBUG Running task: 3636 / 0x4662248
Jul 07 20:54:35-962021 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:35-962216 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:35-962432 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:35-962630 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:35-962827 util-scheduler-8620 DEBUG Adding task: 3637 / 0x46620a0
Jul 07 20:54:35-963011 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:35-963215 util-scheduler-8620 DEBUG Adding task: 3638 / 0x46620a0
Jul 07 20:54:35-963456 util-scheduler-8620 DEBUG Checking readiness of task: 3638 / 0x46620a0
Jul 07 20:54:35-963647 util-scheduler-8620 DEBUG Checking readiness of task: 3637 / 0x46620a0
Jul 07 20:54:35-963838 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:35-964027 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:35-964218 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:35-964408 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:35-964598 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:35-964786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:35-964974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:35-965165 util-scheduler-8620 DEBUG Running task: 3637 / 0x46620a0
Jul 07 20:54:35-965371 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:35-965546 util-8620 DEBUG process_notify is running
Jul 07 20:54:35-965714 util-8620 DEBUG client_notify is running
Jul 07 20:54:35-965899 util-scheduler-8620 DEBUG Canceling task: 3634 / 0x59ee8a0
Jul 07 20:54:35-966121 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:35-966336 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:35-966568 cadet-p2p-8620 DEBUG Checking 0x6078300 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:35-966802 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:35-966979 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:35-967166 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:35-967447 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:35-967641 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:35-967819 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:35-968007 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:35-968194 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:35-968371 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:35-968554 util-scheduler-8620 DEBUG Canceling task: 3631 / 0x59e8808
Jul 07 20:54:35-968763 util-scheduler-8620 DEBUG Adding task: 3639 / 0x59e8808
Jul 07 20:54:35-969005 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:35-969175 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:35-969376 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:35-969593 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:35-969767 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:35-969940 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:35-970138 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:35-970342 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:35-970523 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:35-970701 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:35-970889 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:35-971132 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:40-956948 util-scheduler-8620 DEBUG Checking readiness of task: 3638 / 0x46620a0
Jul 07 20:54:40-957361 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-958119 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-958488 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-958692 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-958885 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-959075 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-959265 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-959459 util-scheduler-8620 DEBUG Running task: 3633 / 0x52cbfb8
Jul 07 20:54:40-959697 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:40-959954 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:40-960160 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:40-960373 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:40-960575 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:40-960811 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:40-960991 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:40-961242 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:40-961536 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:40-961732 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:40-961970 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:40-962177 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:40-962494 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:40-962694 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:40-962918 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:40-963102 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:40-963276 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:40-963483 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:40-963697 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:40-963921 util-scheduler-8620 DEBUG Adding task: 3640 / 0x59ee8a0
Jul 07 20:54:40-964101 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:40-964304 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:40-964480 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:40-964654 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:40-964892 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:40-965086 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:40-965291 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:40-965489 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:40-965733 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:40-965930 util-scheduler-8620 DEBUG Adding task: 3641 / 0x52cbfb8
Jul 07 20:54:40-966196 util-scheduler-8620 DEBUG Checking readiness of task: 3638 / 0x46620a0
Jul 07 20:54:40-966428 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-966619 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-966809 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-966999 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-967188 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-967377 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-967566 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-967755 util-scheduler-8620 DEBUG Running task: 3640 / 0x59ee8a0
Jul 07 20:54:40-967963 util-scheduler-8620 DEBUG Adding task: 3642 / 0x59ee8a0
Jul 07 20:54:40-968184 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:40-968387 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:40-968595 util-scheduler-8620 DEBUG Adding task: 3643 / 0x46620a0
Jul 07 20:54:40-968839 util-scheduler-8620 DEBUG Checking readiness of task: 3643 / 0x46620a0
Jul 07 20:54:40-969032 util-scheduler-8620 DEBUG Checking readiness of task: 3638 / 0x46620a0
Jul 07 20:54:40-969246 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-969438 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-969628 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-969818 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-970007 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-970195 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-970382 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-970572 util-scheduler-8620 DEBUG Running task: 3643 / 0x46620a0
Jul 07 20:54:40-970757 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:40-970935 util-8620 DEBUG process_notify is running
Jul 07 20:54:40-971107 util-8620 DEBUG client_notify is running
Jul 07 20:54:40-971286 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:40-971480 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:40-971670 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:40-971926 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:40-972174 util-scheduler-8620 DEBUG Checking readiness of task: 3638 / 0x46620a0
Jul 07 20:54:40-972366 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-972556 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-972745 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-972934 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-973122 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-973341 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-973530 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-973720 util-scheduler-8620 DEBUG Running task: 3638 / 0x46620a0
Jul 07 20:54:40-974124 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:40-974353 util-scheduler-8620 DEBUG Adding task: 3644 / 0x4662248
Jul 07 20:54:40-974601 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-974792 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-974982 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-975172 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-975361 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-975564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-975753 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-975941 util-scheduler-8620 DEBUG Running task: 3644 / 0x4662248
Jul 07 20:54:40-976129 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:40-976325 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:40-976546 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:40-976742 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:40-976941 util-scheduler-8620 DEBUG Adding task: 3645 / 0x46620a0
Jul 07 20:54:40-977125 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:40-977356 util-scheduler-8620 DEBUG Adding task: 3646 / 0x46620a0
Jul 07 20:54:40-977597 util-scheduler-8620 DEBUG Checking readiness of task: 3646 / 0x46620a0
Jul 07 20:54:40-977789 util-scheduler-8620 DEBUG Checking readiness of task: 3645 / 0x46620a0
Jul 07 20:54:40-977981 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:40-978170 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:40-978361 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:40-978551 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:40-978741 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:40-978930 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:40-979118 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:40-979309 util-scheduler-8620 DEBUG Running task: 3645 / 0x46620a0
Jul 07 20:54:40-979492 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:40-979666 util-8620 DEBUG process_notify is running
Jul 07 20:54:40-979835 util-8620 DEBUG client_notify is running
Jul 07 20:54:40-980020 util-scheduler-8620 DEBUG Canceling task: 3642 / 0x59ee8a0
Jul 07 20:54:40-980241 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:40-980456 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:40-980687 cadet-p2p-8620 DEBUG Checking 0x607b0a0 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:40-980920 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:40-981097 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:40-981309 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:40-981605 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:40-981799 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:40-981977 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:40-982163 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:40-982424 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:40-982679 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:40-982865 util-scheduler-8620 DEBUG Canceling task: 3639 / 0x59e8808
Jul 07 20:54:40-983077 util-scheduler-8620 DEBUG Adding task: 3647 / 0x59e8808
Jul 07 20:54:40-983320 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:40-983490 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:40-983671 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:40-983870 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:40-984044 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:40-984217 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:40-984414 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:40-984617 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:40-984799 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:40-984976 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:40-985165 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:40-985453 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:45-971070 util-scheduler-8620 DEBUG Checking readiness of task: 3646 / 0x46620a0
Jul 07 20:54:45-971444 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-972209 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-972667 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-972868 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-973062 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-973283 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-973474 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-973669 util-scheduler-8620 DEBUG Running task: 3641 / 0x52cbfb8
Jul 07 20:54:45-973910 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:45-974167 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:45-974375 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:45-974575 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:45-974779 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:45-975014 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:45-975195 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:45-975416 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:45-975709 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:45-975906 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:45-976144 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:45-976351 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:45-976668 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:45-976868 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:45-977093 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:45-977296 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:45-977473 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:45-977680 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:45-977894 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:45-978120 util-scheduler-8620 DEBUG Adding task: 3648 / 0x59ee8a0
Jul 07 20:54:45-978300 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:45-978504 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:45-978680 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:45-978855 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:45-979093 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:45-979288 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:45-979465 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:45-979664 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:45-979907 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:45-980104 util-scheduler-8620 DEBUG Adding task: 3649 / 0x52cbfb8
Jul 07 20:54:45-980371 util-scheduler-8620 DEBUG Checking readiness of task: 3646 / 0x46620a0
Jul 07 20:54:45-980563 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-980753 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-980943 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-981135 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-981348 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-981538 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-981728 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-981956 util-scheduler-8620 DEBUG Running task: 3648 / 0x59ee8a0
Jul 07 20:54:45-982167 util-scheduler-8620 DEBUG Adding task: 3650 / 0x59ee8a0
Jul 07 20:54:45-982389 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:45-982592 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:45-982800 util-scheduler-8620 DEBUG Adding task: 3651 / 0x46620a0
Jul 07 20:54:45-983045 util-scheduler-8620 DEBUG Checking readiness of task: 3651 / 0x46620a0
Jul 07 20:54:45-983239 util-scheduler-8620 DEBUG Checking readiness of task: 3646 / 0x46620a0
Jul 07 20:54:45-983429 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-983619 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-983809 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-983998 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-984188 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-984405 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-984595 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-984787 util-scheduler-8620 DEBUG Running task: 3651 / 0x46620a0
Jul 07 20:54:45-984972 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:45-985150 util-8620 DEBUG process_notify is running
Jul 07 20:54:45-985343 util-8620 DEBUG client_notify is running
Jul 07 20:54:45-985522 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:45-985718 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:45-985908 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:45-986164 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:45-986413 util-scheduler-8620 DEBUG Checking readiness of task: 3646 / 0x46620a0
Jul 07 20:54:45-986605 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-986797 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-986987 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-987176 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-987366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-987555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-987744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-987933 util-scheduler-8620 DEBUG Running task: 3646 / 0x46620a0
Jul 07 20:54:45-988341 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:45-988573 util-scheduler-8620 DEBUG Adding task: 3652 / 0x4662248
Jul 07 20:54:45-988823 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-989016 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-989227 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-989432 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-989622 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-989811 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-990000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-990189 util-scheduler-8620 DEBUG Running task: 3652 / 0x4662248
Jul 07 20:54:45-990379 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:45-990574 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:45-990790 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:45-990987 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:45-991205 util-scheduler-8620 DEBUG Adding task: 3653 / 0x46620a0
Jul 07 20:54:45-991390 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:45-991595 util-scheduler-8620 DEBUG Adding task: 3654 / 0x46620a0
Jul 07 20:54:45-991836 util-scheduler-8620 DEBUG Checking readiness of task: 3654 / 0x46620a0
Jul 07 20:54:45-992027 util-scheduler-8620 DEBUG Checking readiness of task: 3653 / 0x46620a0
Jul 07 20:54:45-992219 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:45-992410 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:45-992600 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:45-992789 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:45-992979 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:45-993167 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:45-993376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:45-993567 util-scheduler-8620 DEBUG Running task: 3653 / 0x46620a0
Jul 07 20:54:45-993751 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:45-993925 util-8620 DEBUG process_notify is running
Jul 07 20:54:45-994093 util-8620 DEBUG client_notify is running
Jul 07 20:54:45-994278 util-scheduler-8620 DEBUG Canceling task: 3650 / 0x59ee8a0
Jul 07 20:54:45-994500 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:45-994717 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:45-994947 cadet-p2p-8620 DEBUG Checking 0x59ab2c8 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:45-995181 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:45-995358 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:45-995545 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:45-995827 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:45-996021 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:45-996199 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:45-996386 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:45-996574 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:45-996751 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:45-996934 util-scheduler-8620 DEBUG Canceling task: 3647 / 0x59e8808
Jul 07 20:54:45-997145 util-scheduler-8620 DEBUG Adding task: 3655 / 0x59e8808
Jul 07 20:54:45-997408 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:45-997578 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:45-997759 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:45-997959 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:45-998134 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:45-998307 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:45-998505 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:45-998709 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:45-998891 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:45-999069 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:45-999257 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:45-999503 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:50-982005 util-scheduler-8620 DEBUG Checking readiness of task: 3654 / 0x46620a0
Jul 07 20:54:50-982405 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:50-983164 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:50-983607 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:50-983808 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:50-984001 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:50-984227 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:50-984421 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:50-984615 util-scheduler-8620 DEBUG Running task: 3649 / 0x52cbfb8
Jul 07 20:54:50-984852 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:50-985110 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:50-985362 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:50-985565 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:50-985786 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:50-986024 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:50-986258 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:50-986481 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:50-986773 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:50-986970 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:50-987207 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:50-987414 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:50-987730 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:50-987931 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:50-988156 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:50-988338 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:50-988513 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:50-988720 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:50-988934 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:50-989162 util-scheduler-8620 DEBUG Adding task: 3656 / 0x59ee8a0
Jul 07 20:54:50-989365 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:50-989570 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:50-989746 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:50-989921 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:50-990158 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:50-990353 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:50-990531 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:50-990730 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:50-990973 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:50-991170 util-scheduler-8620 DEBUG Adding task: 3657 / 0x52cbfb8
Jul 07 20:54:50-991433 util-scheduler-8620 DEBUG Checking readiness of task: 3654 / 0x46620a0
Jul 07 20:54:50-991628 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:50-991817 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:50-992008 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:50-992198 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:50-992388 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:50-992577 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:50-992766 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:50-992955 util-scheduler-8620 DEBUG Running task: 3656 / 0x59ee8a0
Jul 07 20:54:50-993163 util-scheduler-8620 DEBUG Adding task: 3658 / 0x59ee8a0
Jul 07 20:54:50-993404 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:50-993608 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:50-993828 util-scheduler-8620 DEBUG Adding task: 3659 / 0x46620a0
Jul 07 20:54:50-994073 util-scheduler-8620 DEBUG Checking readiness of task: 3659 / 0x46620a0
Jul 07 20:54:50-994267 util-scheduler-8620 DEBUG Checking readiness of task: 3654 / 0x46620a0
Jul 07 20:54:50-994458 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:50-994664 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:50-994856 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:50-995046 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:50-995235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:50-995423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:50-995612 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:50-995803 util-scheduler-8620 DEBUG Running task: 3659 / 0x46620a0
Jul 07 20:54:50-996008 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:50-996188 util-8620 DEBUG process_notify is running
Jul 07 20:54:50-996362 util-8620 DEBUG client_notify is running
Jul 07 20:54:50-996542 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:50-996737 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:50-996928 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:50-997183 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:50-997454 util-scheduler-8620 DEBUG Checking readiness of task: 3654 / 0x46620a0
Jul 07 20:54:50-997647 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:50-997838 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:50-998027 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:50-998217 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:50-998406 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:50-998595 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:50-998783 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:50-998973 util-scheduler-8620 DEBUG Running task: 3654 / 0x46620a0
Jul 07 20:54:50-999381 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:50-999627 util-scheduler-8620 DEBUG Adding task: 3660 / 0x4662248
Jul 07 20:54:50-999874 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:51-000066 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:51-000259 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:51-000450 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:51-000641 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:51-000832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:51-001023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:51-001238 util-scheduler-8620 DEBUG Running task: 3660 / 0x4662248
Jul 07 20:54:51-001435 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:51-001634 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:51-001854 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:51-002054 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:51-002254 util-scheduler-8620 DEBUG Adding task: 3661 / 0x46620a0
Jul 07 20:54:51-002440 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:51-002646 util-scheduler-8620 DEBUG Adding task: 3662 / 0x46620a0
Jul 07 20:54:51-002888 util-scheduler-8620 DEBUG Checking readiness of task: 3662 / 0x46620a0
Jul 07 20:54:51-003082 util-scheduler-8620 DEBUG Checking readiness of task: 3661 / 0x46620a0
Jul 07 20:54:51-003274 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:51-003466 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:51-003657 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:51-003864 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:51-004057 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:51-004247 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:51-004438 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:51-004630 util-scheduler-8620 DEBUG Running task: 3661 / 0x46620a0
Jul 07 20:54:51-004815 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:51-004991 util-8620 DEBUG process_notify is running
Jul 07 20:54:51-005162 util-8620 DEBUG client_notify is running
Jul 07 20:54:51-005369 util-scheduler-8620 DEBUG Canceling task: 3658 / 0x59ee8a0
Jul 07 20:54:51-005593 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:51-005811 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:51-006043 cadet-p2p-8620 DEBUG Checking 0x59ad458 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:51-006277 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:51-006457 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:51-006645 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:51-006928 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:51-007124 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:51-007304 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:51-007493 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:51-007684 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:51-007864 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:51-008049 util-scheduler-8620 DEBUG Canceling task: 3655 / 0x59e8808
Jul 07 20:54:51-008260 util-scheduler-8620 DEBUG Adding task: 3663 / 0x59e8808
Jul 07 20:54:51-008504 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:51-008676 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:51-008858 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:51-009061 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:51-009263 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:51-009440 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:51-009641 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:51-009847 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:51-010031 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:51-010212 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:51-010403 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:51-010650 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:55-996317 util-scheduler-8620 DEBUG Checking readiness of task: 3662 / 0x46620a0
Jul 07 20:54:55-996709 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:55-997216 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:55-997480 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:55-997724 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:55-997921 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:55-998112 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:55-998302 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:55-998496 util-scheduler-8620 DEBUG Running task: 3657 / 0x52cbfb8
Jul 07 20:54:55-998736 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:54:55-999020 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:54:55-999228 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:54:55-999429 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:54:55-999631 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:54:55-999867 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:54:56-000076 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:54:56-000304 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:54:56-000600 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:54:56-000799 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:54:56-001038 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:54:56-001285 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:54:56-001606 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:54:56-001808 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:54:56-002034 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:54:56-002219 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:54:56-002397 cadet-con-8620 DEBUG  sendable
Jul 07 20:54:56-002606 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:54:56-002821 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:54:56-003047 util-scheduler-8620 DEBUG Adding task: 3664 / 0x59ee8a0
Jul 07 20:54:56-003229 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:54:56-003433 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:56-003611 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:54:56-003787 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:54:56-004026 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:54:56-004221 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:54:56-004400 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:54:56-004602 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:56-004847 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:54:56-005047 util-scheduler-8620 DEBUG Adding task: 3665 / 0x52cbfb8
Jul 07 20:54:56-005327 util-scheduler-8620 DEBUG Checking readiness of task: 3662 / 0x46620a0
Jul 07 20:54:56-005524 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:56-005716 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:56-005908 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:56-006100 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:56-006291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:56-006481 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:56-006672 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:56-006863 util-scheduler-8620 DEBUG Running task: 3664 / 0x59ee8a0
Jul 07 20:54:56-007073 util-scheduler-8620 DEBUG Adding task: 3666 / 0x59ee8a0
Jul 07 20:54:56-007297 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:54:56-007502 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:56-007712 util-scheduler-8620 DEBUG Adding task: 3667 / 0x46620a0
Jul 07 20:54:56-007958 util-scheduler-8620 DEBUG Checking readiness of task: 3667 / 0x46620a0
Jul 07 20:54:56-008154 util-scheduler-8620 DEBUG Checking readiness of task: 3662 / 0x46620a0
Jul 07 20:54:56-008346 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:56-008538 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:56-008729 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:56-008921 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:56-009112 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:56-009323 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:56-009514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:56-009707 util-scheduler-8620 DEBUG Running task: 3667 / 0x46620a0
Jul 07 20:54:56-009909 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:56-010169 util-8620 DEBUG process_notify is running
Jul 07 20:54:56-010423 util-8620 DEBUG client_notify is running
Jul 07 20:54:56-010612 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:54:56-010811 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:56-011003 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:54:56-011262 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:54:56-011515 util-scheduler-8620 DEBUG Checking readiness of task: 3662 / 0x46620a0
Jul 07 20:54:56-011709 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:56-011902 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:56-012094 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:56-012286 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:56-012478 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:56-012668 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:56-012859 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:56-013051 util-scheduler-8620 DEBUG Running task: 3662 / 0x46620a0
Jul 07 20:54:56-013480 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:54:56-013713 util-scheduler-8620 DEBUG Adding task: 3668 / 0x4662248
Jul 07 20:54:56-013964 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:56-014157 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:56-014350 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:56-014542 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:56-014734 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:56-014925 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:56-015116 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:56-015306 util-scheduler-8620 DEBUG Running task: 3668 / 0x4662248
Jul 07 20:54:56-015499 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:54:56-015697 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:54:56-015915 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:54:56-016114 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:54:56-016315 util-scheduler-8620 DEBUG Adding task: 3669 / 0x46620a0
Jul 07 20:54:56-016503 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:54:56-016709 util-scheduler-8620 DEBUG Adding task: 3670 / 0x46620a0
Jul 07 20:54:56-016951 util-scheduler-8620 DEBUG Checking readiness of task: 3670 / 0x46620a0
Jul 07 20:54:56-017145 util-scheduler-8620 DEBUG Checking readiness of task: 3669 / 0x46620a0
Jul 07 20:54:56-017359 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:54:56-017552 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:54:56-017745 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:54:56-017937 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:54:56-018130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:54:56-018322 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:54:56-018513 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:54:56-018707 util-scheduler-8620 DEBUG Running task: 3669 / 0x46620a0
Jul 07 20:54:56-018892 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:54:56-019070 util-8620 DEBUG process_notify is running
Jul 07 20:54:56-019256 util-8620 DEBUG client_notify is running
Jul 07 20:54:56-019444 util-scheduler-8620 DEBUG Canceling task: 3666 / 0x59ee8a0
Jul 07 20:54:56-019669 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:54:56-019887 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:54:56-020120 cadet-p2p-8620 DEBUG Checking 0x607eea8 towards 2FDYFV0X (->V8XX)
Jul 07 20:54:56-020354 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:54:56-020537 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:54:56-020724 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:54:56-021008 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:54:56-021223 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:54:56-021405 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:54:56-021594 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:54:56-021784 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:54:56-021965 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:54:56-022149 util-scheduler-8620 DEBUG Canceling task: 3663 / 0x59e8808
Jul 07 20:54:56-022361 util-scheduler-8620 DEBUG Adding task: 3671 / 0x59e8808
Jul 07 20:54:56-022615 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:54:56-022788 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:54:56-022970 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:54:56-023172 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:54:56-023348 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:54:56-023524 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:54:56-023724 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:54:56-023930 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:54:56-024115 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:54:56-024295 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:54:56-024485 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:54:56-025412 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:01-010205 util-scheduler-8620 DEBUG Checking readiness of task: 3670 / 0x46620a0
Jul 07 20:55:01-010587 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-010805 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-011002 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-011203 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-011403 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-011596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-011789 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-011987 util-scheduler-8620 DEBUG Running task: 3665 / 0x52cbfb8
Jul 07 20:55:01-012227 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:01-012485 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:55:01-012695 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:01-012898 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:01-013101 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:01-013362 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:01-013545 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:01-013769 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:01-014060 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:01-014258 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:01-014498 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:01-014709 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:01-015026 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:01-015253 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:01-015482 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:01-015668 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:01-015846 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:01-016055 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:01-016271 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:01-016497 util-scheduler-8620 DEBUG Adding task: 3672 / 0x59ee8a0
Jul 07 20:55:01-016681 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:01-016886 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:01-017120 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:01-017393 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:01-017639 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:01-017838 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:01-018017 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:01-018219 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:01-018465 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:01-018667 util-scheduler-8620 DEBUG Adding task: 3673 / 0x52cbfb8
Jul 07 20:55:01-018925 util-scheduler-8620 DEBUG Checking readiness of task: 3670 / 0x46620a0
Jul 07 20:55:01-019119 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-019312 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-019504 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-019696 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-019888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-020079 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-020270 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-020462 util-scheduler-8620 DEBUG Running task: 3672 / 0x59ee8a0
Jul 07 20:55:01-020672 util-scheduler-8620 DEBUG Adding task: 3674 / 0x59ee8a0
Jul 07 20:55:01-020896 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:01-021100 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:01-021334 util-scheduler-8620 DEBUG Adding task: 3675 / 0x46620a0
Jul 07 20:55:01-021580 util-scheduler-8620 DEBUG Checking readiness of task: 3675 / 0x46620a0
Jul 07 20:55:01-021775 util-scheduler-8620 DEBUG Checking readiness of task: 3670 / 0x46620a0
Jul 07 20:55:01-021972 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-022165 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-022358 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-022549 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-022741 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-022932 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-023123 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-023316 util-scheduler-8620 DEBUG Running task: 3675 / 0x46620a0
Jul 07 20:55:01-023502 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:01-023683 util-8620 DEBUG process_notify is running
Jul 07 20:55:01-023857 util-8620 DEBUG client_notify is running
Jul 07 20:55:01-024038 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:01-024236 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:01-024430 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:01-024676 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:01-025597 util-scheduler-8620 DEBUG Checking readiness of task: 3670 / 0x46620a0
Jul 07 20:55:01-025828 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-026026 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-026221 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-026414 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-026608 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-026800 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-026991 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-027185 util-scheduler-8620 DEBUG Running task: 3670 / 0x46620a0
Jul 07 20:55:01-027592 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:01-027829 util-scheduler-8620 DEBUG Adding task: 3676 / 0x4662248
Jul 07 20:55:01-028082 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-028278 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-028472 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-028666 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-028859 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-029051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-029263 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-029456 util-scheduler-8620 DEBUG Running task: 3676 / 0x4662248
Jul 07 20:55:01-029649 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:01-029849 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:01-030083 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:01-030284 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:01-030486 util-scheduler-8620 DEBUG Adding task: 3677 / 0x46620a0
Jul 07 20:55:01-030675 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:01-030882 util-scheduler-8620 DEBUG Adding task: 3678 / 0x46620a0
Jul 07 20:55:01-031125 util-scheduler-8620 DEBUG Checking readiness of task: 3678 / 0x46620a0
Jul 07 20:55:01-031320 util-scheduler-8620 DEBUG Checking readiness of task: 3677 / 0x46620a0
Jul 07 20:55:01-031514 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:01-031707 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:01-031899 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:01-032091 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:01-032284 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:01-032475 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:01-032668 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:01-032861 util-scheduler-8620 DEBUG Running task: 3677 / 0x46620a0
Jul 07 20:55:01-033047 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:01-033245 util-8620 DEBUG process_notify is running
Jul 07 20:55:01-033418 util-8620 DEBUG client_notify is running
Jul 07 20:55:01-033606 util-scheduler-8620 DEBUG Canceling task: 3674 / 0x59ee8a0
Jul 07 20:55:01-033832 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:01-034051 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:01-034285 cadet-p2p-8620 DEBUG Checking 0x606afd0 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:01-034524 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:01-034704 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:01-034897 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:01-035184 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:01-035395 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:01-035576 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:01-035765 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:01-035955 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:01-036137 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:01-036322 util-scheduler-8620 DEBUG Canceling task: 3671 / 0x59e8808
Jul 07 20:55:01-036535 util-scheduler-8620 DEBUG Adding task: 3679 / 0x59e8808
Jul 07 20:55:01-036780 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:01-036952 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:01-037134 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:01-037357 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:01-037534 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:01-037710 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:01-037909 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:01-038115 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:01-038300 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:01-038479 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:01-038670 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:01-038917 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:06-023814 util-scheduler-8620 DEBUG Checking readiness of task: 3678 / 0x46620a0
Jul 07 20:55:06-024239 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-025729 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-025946 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-026146 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-026348 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-026543 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-026736 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-026933 util-scheduler-8620 DEBUG Running task: 3673 / 0x52cbfb8
Jul 07 20:55:06-027176 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:06-027436 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:55:06-027646 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:06-027848 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:06-028052 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:06-028290 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:06-028474 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:06-028698 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:06-028990 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:06-029211 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:06-030291 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:06-030538 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:06-030885 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:06-031089 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:06-031317 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:06-031504 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:06-031682 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:06-031890 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:06-032107 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:06-032338 util-scheduler-8620 DEBUG Adding task: 3680 / 0x59ee8a0
Jul 07 20:55:06-032530 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:06-032765 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:06-032945 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:06-033124 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:06-033389 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:06-033588 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:06-033769 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:06-033971 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:06-034217 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:06-034420 util-scheduler-8620 DEBUG Adding task: 3681 / 0x52cbfb8
Jul 07 20:55:06-034778 util-scheduler-8620 DEBUG Checking readiness of task: 3678 / 0x46620a0
Jul 07 20:55:06-034977 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-035170 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-035364 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-035559 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-035753 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-035946 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-036138 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-036330 util-scheduler-8620 DEBUG Running task: 3680 / 0x59ee8a0
Jul 07 20:55:06-036541 util-scheduler-8620 DEBUG Adding task: 3682 / 0x59ee8a0
Jul 07 20:55:06-036766 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:06-036973 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:06-037183 util-scheduler-8620 DEBUG Adding task: 3683 / 0x46620a0
Jul 07 20:55:06-037451 util-scheduler-8620 DEBUG Checking readiness of task: 3683 / 0x46620a0
Jul 07 20:55:06-037648 util-scheduler-8620 DEBUG Checking readiness of task: 3678 / 0x46620a0
Jul 07 20:55:06-037842 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-038034 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-038226 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-038419 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-038623 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-038815 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-039006 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-039200 util-scheduler-8620 DEBUG Running task: 3683 / 0x46620a0
Jul 07 20:55:06-039387 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:06-039569 util-8620 DEBUG process_notify is running
Jul 07 20:55:06-039743 util-8620 DEBUG client_notify is running
Jul 07 20:55:06-039925 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:06-040124 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:06-040317 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:06-040572 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:06-040823 util-scheduler-8620 DEBUG Checking readiness of task: 3678 / 0x46620a0
Jul 07 20:55:06-041019 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-041231 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-041425 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-041617 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-041809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-042000 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-042191 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-042401 util-scheduler-8620 DEBUG Running task: 3678 / 0x46620a0
Jul 07 20:55:06-042807 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:06-043038 util-scheduler-8620 DEBUG Adding task: 3684 / 0x4662248
Jul 07 20:55:06-043289 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-043482 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-043675 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-043867 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-044059 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-044250 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-044441 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-044632 util-scheduler-8620 DEBUG Running task: 3684 / 0x4662248
Jul 07 20:55:06-044824 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:06-045022 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:06-045259 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:06-045460 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:06-045664 util-scheduler-8620 DEBUG Adding task: 3685 / 0x46620a0
Jul 07 20:55:06-045851 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:06-046058 util-scheduler-8620 DEBUG Adding task: 3686 / 0x46620a0
Jul 07 20:55:06-046300 util-scheduler-8620 DEBUG Checking readiness of task: 3686 / 0x46620a0
Jul 07 20:55:06-046495 util-scheduler-8620 DEBUG Checking readiness of task: 3685 / 0x46620a0
Jul 07 20:55:06-046689 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:06-046881 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:06-047073 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:06-047265 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:06-047457 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:06-047649 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:06-047840 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:06-048033 util-scheduler-8620 DEBUG Running task: 3685 / 0x46620a0
Jul 07 20:55:06-048219 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:06-048397 util-8620 DEBUG process_notify is running
Jul 07 20:55:06-048568 util-8620 DEBUG client_notify is running
Jul 07 20:55:06-048754 util-scheduler-8620 DEBUG Canceling task: 3682 / 0x59ee8a0
Jul 07 20:55:06-048979 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:06-049216 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:06-049452 cadet-p2p-8620 DEBUG Checking 0x6081080 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:06-049688 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:06-049868 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:06-050058 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:06-050344 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:06-050542 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:06-050722 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:06-050912 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:06-051102 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:06-051283 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:06-051468 util-scheduler-8620 DEBUG Canceling task: 3679 / 0x59e8808
Jul 07 20:55:06-051680 util-scheduler-8620 DEBUG Adding task: 3687 / 0x59e8808
Jul 07 20:55:06-051926 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:06-052115 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:06-052299 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:06-052501 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:06-052677 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:06-052853 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:06-053053 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:06-053310 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:06-053498 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:06-053679 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:06-053871 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:06-054117 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:11-039561 util-scheduler-8620 DEBUG Checking readiness of task: 3686 / 0x46620a0
Jul 07 20:55:11-039947 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-040567 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-040767 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-041015 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-041245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-041455 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-041658 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-041855 util-scheduler-8620 DEBUG Running task: 3681 / 0x52cbfb8
Jul 07 20:55:11-042095 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:11-042353 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:55:11-042563 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:11-042764 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:11-042968 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:11-043206 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:11-043388 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:11-043612 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:11-043902 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:11-044102 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:11-044342 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:11-044553 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:11-044871 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:11-045073 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:11-045321 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:11-045505 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:11-045696 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:11-045905 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:11-046121 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:11-046347 util-scheduler-8620 DEBUG Adding task: 3688 / 0x59ee8a0
Jul 07 20:55:11-046529 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:11-046737 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:11-046915 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:11-047091 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:11-047332 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:11-047530 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:11-047709 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:11-047910 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:11-048155 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:11-048355 util-scheduler-8620 DEBUG Adding task: 3689 / 0x52cbfb8
Jul 07 20:55:11-048642 util-scheduler-8620 DEBUG Checking readiness of task: 3686 / 0x46620a0
Jul 07 20:55:11-048838 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-049031 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-049242 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-049436 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-049628 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-049819 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-050010 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-050201 util-scheduler-8620 DEBUG Running task: 3688 / 0x59ee8a0
Jul 07 20:55:11-050411 util-scheduler-8620 DEBUG Adding task: 3690 / 0x59ee8a0
Jul 07 20:55:11-050636 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:11-050840 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:11-051050 util-scheduler-8620 DEBUG Adding task: 3691 / 0x46620a0
Jul 07 20:55:11-051295 util-scheduler-8620 DEBUG Checking readiness of task: 3691 / 0x46620a0
Jul 07 20:55:11-051492 util-scheduler-8620 DEBUG Checking readiness of task: 3686 / 0x46620a0
Jul 07 20:55:11-051684 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-051877 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-052068 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-052260 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-052451 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-052642 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-052833 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-053026 util-scheduler-8620 DEBUG Running task: 3691 / 0x46620a0
Jul 07 20:55:11-053231 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:11-053414 util-8620 DEBUG process_notify is running
Jul 07 20:55:11-053589 util-8620 DEBUG client_notify is running
Jul 07 20:55:11-053770 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:11-053965 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:11-054158 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:11-054414 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:11-054663 util-scheduler-8620 DEBUG Checking readiness of task: 3686 / 0x46620a0
Jul 07 20:55:11-054857 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-055049 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-055241 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-055433 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-055625 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-055816 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-056007 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-056199 util-scheduler-8620 DEBUG Running task: 3686 / 0x46620a0
Jul 07 20:55:11-056606 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:11-056845 util-scheduler-8620 DEBUG Adding task: 3692 / 0x4662248
Jul 07 20:55:11-057097 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-057311 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-057504 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-057714 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-057907 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-058098 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-058289 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-058481 util-scheduler-8620 DEBUG Running task: 3692 / 0x4662248
Jul 07 20:55:11-058673 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:11-058872 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:11-059090 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:11-059289 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:11-059490 util-scheduler-8620 DEBUG Adding task: 3693 / 0x46620a0
Jul 07 20:55:11-059677 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:11-059883 util-scheduler-8620 DEBUG Adding task: 3694 / 0x46620a0
Jul 07 20:55:11-060125 util-scheduler-8620 DEBUG Checking readiness of task: 3694 / 0x46620a0
Jul 07 20:55:11-060320 util-scheduler-8620 DEBUG Checking readiness of task: 3693 / 0x46620a0
Jul 07 20:55:11-060514 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:11-060706 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:11-060899 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:11-061092 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:11-061303 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:11-061496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:11-061687 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:11-061880 util-scheduler-8620 DEBUG Running task: 3693 / 0x46620a0
Jul 07 20:55:11-062066 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:11-062242 util-8620 DEBUG process_notify is running
Jul 07 20:55:11-062413 util-8620 DEBUG client_notify is running
Jul 07 20:55:11-062600 util-scheduler-8620 DEBUG Canceling task: 3690 / 0x59ee8a0
Jul 07 20:55:11-062824 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:11-063043 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:11-063275 cadet-p2p-8620 DEBUG Checking 0x606f260 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:11-063511 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:11-063690 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:11-063879 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:11-064162 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:11-064358 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:11-064539 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:11-064727 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:11-064917 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:11-065096 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:11-065300 util-scheduler-8620 DEBUG Canceling task: 3687 / 0x59e8808
Jul 07 20:55:11-065513 util-scheduler-8620 DEBUG Adding task: 3695 / 0x59e8808
Jul 07 20:55:11-065757 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:11-065929 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:11-066111 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:11-066312 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:11-066488 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:11-066666 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:11-066867 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:11-067086 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:11-067270 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:11-067449 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:11-067657 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:11-067905 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:16-053505 util-scheduler-8620 DEBUG Checking readiness of task: 3694 / 0x46620a0
Jul 07 20:55:16-053907 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-055229 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-055596 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-055799 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-055995 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-056190 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-056382 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-056579 util-scheduler-8620 DEBUG Running task: 3689 / 0x52cbfb8
Jul 07 20:55:16-056819 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:16-057080 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:55:16-057323 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:16-057527 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:16-057731 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:16-057969 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:16-058152 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:16-058377 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:16-058669 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:16-058868 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:16-059106 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:16-059316 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:16-059634 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:16-059836 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:16-060063 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:16-060247 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:16-060425 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:16-060634 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:16-060850 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:16-061075 util-scheduler-8620 DEBUG Adding task: 3696 / 0x59ee8a0
Jul 07 20:55:16-061284 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:16-061492 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:16-061670 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:16-061847 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:16-062088 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:16-062285 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:16-062465 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:16-062666 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:16-062912 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:16-063112 util-scheduler-8620 DEBUG Adding task: 3697 / 0x52cbfb8
Jul 07 20:55:16-063379 util-scheduler-8620 DEBUG Checking readiness of task: 3694 / 0x46620a0
Jul 07 20:55:16-063574 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-063767 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-063959 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-064150 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-064342 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-064532 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-064766 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-064959 util-scheduler-8620 DEBUG Running task: 3696 / 0x59ee8a0
Jul 07 20:55:16-065171 util-scheduler-8620 DEBUG Adding task: 3698 / 0x59ee8a0
Jul 07 20:55:16-065422 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:16-065630 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:16-065840 util-scheduler-8620 DEBUG Adding task: 3699 / 0x46620a0
Jul 07 20:55:16-066087 util-scheduler-8620 DEBUG Checking readiness of task: 3699 / 0x46620a0
Jul 07 20:55:16-066283 util-scheduler-8620 DEBUG Checking readiness of task: 3694 / 0x46620a0
Jul 07 20:55:16-066474 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-066666 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-066857 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-067049 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-067241 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-067432 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-067623 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-067816 util-scheduler-8620 DEBUG Running task: 3699 / 0x46620a0
Jul 07 20:55:16-068003 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:16-068183 util-8620 DEBUG process_notify is running
Jul 07 20:55:16-068358 util-8620 DEBUG client_notify is running
Jul 07 20:55:16-068539 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:16-068735 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:16-068928 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:16-069186 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:16-069463 util-scheduler-8620 DEBUG Checking readiness of task: 3694 / 0x46620a0
Jul 07 20:55:16-069659 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-069851 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-070043 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-070235 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-070427 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-070619 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-070809 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-071001 util-scheduler-8620 DEBUG Running task: 3694 / 0x46620a0
Jul 07 20:55:16-071408 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:16-071639 util-scheduler-8620 DEBUG Adding task: 3700 / 0x4662248
Jul 07 20:55:16-071888 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-072082 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-072275 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-072467 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-072659 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-072850 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-073041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-073258 util-scheduler-8620 DEBUG Running task: 3700 / 0x4662248
Jul 07 20:55:16-073452 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:16-073650 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:16-073868 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:16-074082 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:16-074283 util-scheduler-8620 DEBUG Adding task: 3701 / 0x46620a0
Jul 07 20:55:16-074469 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:16-074675 util-scheduler-8620 DEBUG Adding task: 3702 / 0x46620a0
Jul 07 20:55:16-074918 util-scheduler-8620 DEBUG Checking readiness of task: 3702 / 0x46620a0
Jul 07 20:55:16-075112 util-scheduler-8620 DEBUG Checking readiness of task: 3701 / 0x46620a0
Jul 07 20:55:16-075306 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:16-075510 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:16-075706 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:16-075899 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:16-076090 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:16-076281 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:16-076472 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:16-076664 util-scheduler-8620 DEBUG Running task: 3701 / 0x46620a0
Jul 07 20:55:16-076850 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:16-077027 util-8620 DEBUG process_notify is running
Jul 07 20:55:16-077222 util-8620 DEBUG client_notify is running
Jul 07 20:55:16-077412 util-scheduler-8620 DEBUG Canceling task: 3698 / 0x59ee8a0
Jul 07 20:55:16-077638 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:16-077855 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:16-078088 cadet-p2p-8620 DEBUG Checking 0x6071388 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:16-078323 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:16-078502 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:16-078691 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:16-078974 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:16-079170 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:16-079350 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:16-079539 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:16-079729 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:16-079909 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:16-080094 util-scheduler-8620 DEBUG Canceling task: 3695 / 0x59e8808
Jul 07 20:55:16-080305 util-scheduler-8620 DEBUG Adding task: 3703 / 0x59e8808
Jul 07 20:55:16-080549 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:16-080721 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:16-080904 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:16-081105 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:16-081309 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:16-081486 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:16-081689 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:16-081896 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:16-082081 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:16-082260 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:16-082450 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:16-082698 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:21-068253 util-scheduler-8620 DEBUG Checking readiness of task: 3702 / 0x46620a0
Jul 07 20:55:21-068644 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-069218 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-069478 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-069761 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-069959 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-070152 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-070344 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-070539 util-scheduler-8620 DEBUG Running task: 3697 / 0x52cbfb8
Jul 07 20:55:21-070779 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:21-071038 cadet-tun-8620 DEBUG  kx started 7 m ago
Jul 07 20:55:21-071248 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:21-071450 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:21-071653 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:21-071889 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:21-072072 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:21-072296 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:21-072588 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:21-072786 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:21-073026 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:21-073256 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:21-073595 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:21-073801 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:21-074030 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:21-074215 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:21-074393 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:21-074602 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:21-074817 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:21-075044 util-scheduler-8620 DEBUG Adding task: 3704 / 0x59ee8a0
Jul 07 20:55:21-075227 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:21-075433 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:21-075610 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:21-075787 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:21-076027 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:21-076225 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:21-076404 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:21-076604 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:21-076851 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:21-077052 util-scheduler-8620 DEBUG Adding task: 3705 / 0x52cbfb8
Jul 07 20:55:21-077333 util-scheduler-8620 DEBUG Checking readiness of task: 3702 / 0x46620a0
Jul 07 20:55:21-077528 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-077721 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-077913 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-078105 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-078297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-078488 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-078679 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-078870 util-scheduler-8620 DEBUG Running task: 3704 / 0x59ee8a0
Jul 07 20:55:21-079079 util-scheduler-8620 DEBUG Adding task: 3706 / 0x59ee8a0
Jul 07 20:55:21-079302 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:21-079506 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:21-079715 util-scheduler-8620 DEBUG Adding task: 3707 / 0x46620a0
Jul 07 20:55:21-079959 util-scheduler-8620 DEBUG Checking readiness of task: 3707 / 0x46620a0
Jul 07 20:55:21-080154 util-scheduler-8620 DEBUG Checking readiness of task: 3702 / 0x46620a0
Jul 07 20:55:21-080366 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-080559 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-080751 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-080944 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-081138 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-081350 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-081542 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-081736 util-scheduler-8620 DEBUG Running task: 3707 / 0x46620a0
Jul 07 20:55:21-081924 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:21-082105 util-8620 DEBUG process_notify is running
Jul 07 20:55:21-082279 util-8620 DEBUG client_notify is running
Jul 07 20:55:21-082460 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:21-082671 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:21-082864 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:21-083120 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:21-083370 util-scheduler-8620 DEBUG Checking readiness of task: 3702 / 0x46620a0
Jul 07 20:55:21-083565 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-083757 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-083950 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-084142 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-084333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-084524 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-084716 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-084908 util-scheduler-8620 DEBUG Running task: 3702 / 0x46620a0
Jul 07 20:55:21-085333 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:21-085565 util-scheduler-8620 DEBUG Adding task: 3708 / 0x4662248
Jul 07 20:55:21-085815 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-086009 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-086200 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-086392 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-086584 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-086775 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-086970 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-087161 util-scheduler-8620 DEBUG Running task: 3708 / 0x4662248
Jul 07 20:55:21-087352 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:21-087550 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:21-087767 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:21-087967 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:21-088168 util-scheduler-8620 DEBUG Adding task: 3709 / 0x46620a0
Jul 07 20:55:21-088354 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:21-088560 util-scheduler-8620 DEBUG Adding task: 3710 / 0x46620a0
Jul 07 20:55:21-088802 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:21-088996 util-scheduler-8620 DEBUG Checking readiness of task: 3709 / 0x46620a0
Jul 07 20:55:21-089207 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:21-089418 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:21-089611 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:21-089803 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:21-089995 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:21-090187 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:21-090377 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:21-090570 util-scheduler-8620 DEBUG Running task: 3709 / 0x46620a0
Jul 07 20:55:21-090756 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:21-091050 util-8620 DEBUG process_notify is running
Jul 07 20:55:21-091232 util-8620 DEBUG client_notify is running
Jul 07 20:55:21-091421 util-scheduler-8620 DEBUG Canceling task: 3706 / 0x59ee8a0
Jul 07 20:55:21-091646 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:21-091864 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:21-092097 cadet-p2p-8620 DEBUG Checking 0x60846a8 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:21-092332 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:21-092511 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:21-092699 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:21-092982 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:21-093178 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:21-093379 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:21-093568 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:21-093758 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:21-093939 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:21-094125 util-scheduler-8620 DEBUG Canceling task: 3703 / 0x59e8808
Jul 07 20:55:21-094339 util-scheduler-8620 DEBUG Adding task: 3711 / 0x59e8808
Jul 07 20:55:21-094583 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:21-094756 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:21-094939 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:21-095143 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:21-095322 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:21-095498 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:21-095698 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:21-095904 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:21-096089 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:21-096269 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:21-096461 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:21-096707 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:25-919719 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:25-920102 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:25-920302 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:25-920495 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:25-920688 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:25-920879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:25-921079 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:25-921301 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:25-921494 util-scheduler-8620 DEBUG Running task: 3603 / 0x53a63f8
Jul 07 20:55:25-921735 cadet-tun-8620 INFO finish KX for P00P
Jul 07 20:55:26-077301 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:26-077547 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-078206 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-078406 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-078602 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-078797 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-078989 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-079181 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-079375 util-scheduler-8620 DEBUG Running task: 3705 / 0x52cbfb8
Jul 07 20:55:26-079598 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:26-079854 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:26-080063 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:26-080265 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:26-080471 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:26-080707 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:26-080905 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:26-081133 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:26-081450 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:26-081649 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:26-081890 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:26-082101 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:26-082419 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:26-082621 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:26-082862 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:26-083047 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:26-083225 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:26-083434 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:26-083650 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:26-083878 util-scheduler-8620 DEBUG Adding task: 3712 / 0x59ee8a0
Jul 07 20:55:26-084060 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:26-084266 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:26-084444 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:26-084620 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:26-084861 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:26-085058 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:26-085257 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:26-085460 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:26-085705 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:26-085905 util-scheduler-8620 DEBUG Adding task: 3713 / 0x52cbfb8
Jul 07 20:55:26-086154 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:26-086349 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-086542 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-086734 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-086925 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-087117 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-087308 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-087499 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-087691 util-scheduler-8620 DEBUG Running task: 3712 / 0x59ee8a0
Jul 07 20:55:26-087902 util-scheduler-8620 DEBUG Adding task: 3714 / 0x59ee8a0
Jul 07 20:55:26-088127 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:26-088333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:26-088561 util-scheduler-8620 DEBUG Adding task: 3715 / 0x46620a0
Jul 07 20:55:26-088808 util-scheduler-8620 DEBUG Checking readiness of task: 3715 / 0x46620a0
Jul 07 20:55:26-089003 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:26-089218 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-089413 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-089606 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-089798 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-089990 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-090182 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-090376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-090570 util-scheduler-8620 DEBUG Running task: 3715 / 0x46620a0
Jul 07 20:55:26-090757 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:26-090938 util-8620 DEBUG process_notify is running
Jul 07 20:55:26-091112 util-8620 DEBUG client_notify is running
Jul 07 20:55:26-091293 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:26-091490 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:26-091684 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:26-091938 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:26-092189 util-scheduler-8620 DEBUG Checking readiness of task: 3710 / 0x46620a0
Jul 07 20:55:26-092384 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-092576 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-092768 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-092960 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-093152 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-093365 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-093557 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-093749 util-scheduler-8620 DEBUG Running task: 3710 / 0x46620a0
Jul 07 20:55:26-094155 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:26-094387 util-scheduler-8620 DEBUG Adding task: 3716 / 0x4662248
Jul 07 20:55:26-094637 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-094831 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-095024 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-095216 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-095408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-095599 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-095790 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-095981 util-scheduler-8620 DEBUG Running task: 3716 / 0x4662248
Jul 07 20:55:26-096174 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:26-096373 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:26-096593 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:26-096792 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:26-096992 util-scheduler-8620 DEBUG Adding task: 3717 / 0x46620a0
Jul 07 20:55:26-097179 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:26-097408 util-scheduler-8620 DEBUG Adding task: 3718 / 0x46620a0
Jul 07 20:55:26-097650 util-scheduler-8620 DEBUG Checking readiness of task: 3718 / 0x46620a0
Jul 07 20:55:26-097860 util-scheduler-8620 DEBUG Checking readiness of task: 3717 / 0x46620a0
Jul 07 20:55:26-098055 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:26-098247 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:26-098439 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:26-098631 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:26-098823 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:26-099013 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:26-099204 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:26-099397 util-scheduler-8620 DEBUG Running task: 3717 / 0x46620a0
Jul 07 20:55:26-099583 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:26-099760 util-8620 DEBUG process_notify is running
Jul 07 20:55:26-099931 util-8620 DEBUG client_notify is running
Jul 07 20:55:26-100119 util-scheduler-8620 DEBUG Canceling task: 3714 / 0x59ee8a0
Jul 07 20:55:26-100347 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:26-100562 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:26-100793 cadet-p2p-8620 DEBUG Checking 0x6075298 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:26-101025 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:26-101225 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:26-101414 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:26-101697 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:26-101892 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:26-102070 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:26-102257 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:26-102445 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:26-102623 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:26-102807 util-scheduler-8620 DEBUG Canceling task: 3711 / 0x59e8808
Jul 07 20:55:26-103018 util-scheduler-8620 DEBUG Adding task: 3719 / 0x59e8808
Jul 07 20:55:26-103260 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:26-103430 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:26-103610 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:26-103810 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:26-103986 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:26-104174 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:26-104373 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:26-104578 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:26-104761 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:26-104938 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:26-105127 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:26-105397 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:31-086354 util-scheduler-8620 DEBUG Checking readiness of task: 3718 / 0x46620a0
Jul 07 20:55:31-086753 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-087279 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-087509 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-087735 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-087946 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-088139 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-088332 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-088528 util-scheduler-8620 DEBUG Running task: 3713 / 0x52cbfb8
Jul 07 20:55:31-088793 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:31-089056 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:31-089287 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:31-089492 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:31-089697 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:31-089934 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:31-090117 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:31-090341 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:31-090632 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:31-090832 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:31-091071 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:31-091281 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:31-091600 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:31-091803 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:31-092030 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:31-092215 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:31-092393 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:31-092602 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:31-092821 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:31-093051 util-scheduler-8620 DEBUG Adding task: 3720 / 0x59ee8a0
Jul 07 20:55:31-093257 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:31-093463 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:31-093642 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:31-093820 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:31-094060 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:31-094258 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:31-094438 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:31-094638 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:31-094885 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:31-095084 util-scheduler-8620 DEBUG Adding task: 3721 / 0x52cbfb8
Jul 07 20:55:31-095345 util-scheduler-8620 DEBUG Checking readiness of task: 3718 / 0x46620a0
Jul 07 20:55:31-095540 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-095733 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-095924 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-096116 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-096307 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-096498 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-096689 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-096880 util-scheduler-8620 DEBUG Running task: 3720 / 0x59ee8a0
Jul 07 20:55:31-097089 util-scheduler-8620 DEBUG Adding task: 3722 / 0x59ee8a0
Jul 07 20:55:31-097331 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:31-097538 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:31-097747 util-scheduler-8620 DEBUG Adding task: 3723 / 0x46620a0
Jul 07 20:55:31-097992 util-scheduler-8620 DEBUG Checking readiness of task: 3723 / 0x46620a0
Jul 07 20:55:31-098187 util-scheduler-8620 DEBUG Checking readiness of task: 3718 / 0x46620a0
Jul 07 20:55:31-098379 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-098571 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-098763 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-098955 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-099163 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-099356 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-099550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-099743 util-scheduler-8620 DEBUG Running task: 3723 / 0x46620a0
Jul 07 20:55:31-099929 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:31-100109 util-8620 DEBUG process_notify is running
Jul 07 20:55:31-100283 util-8620 DEBUG client_notify is running
Jul 07 20:55:31-100461 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:31-100655 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:31-100848 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:31-101101 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:31-101369 util-scheduler-8620 DEBUG Checking readiness of task: 3718 / 0x46620a0
Jul 07 20:55:31-101564 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-101755 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-101944 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-102134 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-102325 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-102513 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-102701 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-102891 util-scheduler-8620 DEBUG Running task: 3718 / 0x46620a0
Jul 07 20:55:31-103294 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:31-103526 util-scheduler-8620 DEBUG Adding task: 3724 / 0x4662248
Jul 07 20:55:31-103776 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-103969 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-104160 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-104350 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-104539 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-104727 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-104915 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-105104 util-scheduler-8620 DEBUG Running task: 3724 / 0x4662248
Jul 07 20:55:31-105314 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:31-105510 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:31-105728 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:31-105925 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:31-106124 util-scheduler-8620 DEBUG Adding task: 3725 / 0x46620a0
Jul 07 20:55:31-106310 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:31-106513 util-scheduler-8620 DEBUG Adding task: 3726 / 0x46620a0
Jul 07 20:55:31-106765 util-scheduler-8620 DEBUG Checking readiness of task: 3726 / 0x46620a0
Jul 07 20:55:31-106957 util-scheduler-8620 DEBUG Checking readiness of task: 3725 / 0x46620a0
Jul 07 20:55:31-107148 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:31-107337 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:31-107526 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:31-107715 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:31-107906 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:31-108094 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:31-108300 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:31-108493 util-scheduler-8620 DEBUG Running task: 3725 / 0x46620a0
Jul 07 20:55:31-108677 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:31-108852 util-8620 DEBUG process_notify is running
Jul 07 20:55:31-109021 util-8620 DEBUG client_notify is running
Jul 07 20:55:31-109225 util-scheduler-8620 DEBUG Canceling task: 3722 / 0x59ee8a0
Jul 07 20:55:31-109452 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:31-109671 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:31-109902 cadet-p2p-8620 DEBUG Checking 0x6086d60 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:31-110135 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:31-110313 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:31-110500 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:31-110783 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:31-110977 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:31-111154 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:31-111341 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:31-111528 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:31-111705 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:31-111889 util-scheduler-8620 DEBUG Canceling task: 3719 / 0x59e8808
Jul 07 20:55:31-112098 util-scheduler-8620 DEBUG Adding task: 3727 / 0x59e8808
Jul 07 20:55:31-112340 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:31-112510 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:31-112691 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:31-112888 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:31-113062 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:31-113254 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:31-113453 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:31-113657 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:31-113839 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:31-114016 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:31-114204 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:31-114448 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:36-100231 util-scheduler-8620 DEBUG Checking readiness of task: 3726 / 0x46620a0
Jul 07 20:55:36-100615 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-101214 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-101464 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-101701 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-101897 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-102088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-102278 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-102470 util-scheduler-8620 DEBUG Running task: 3721 / 0x52cbfb8
Jul 07 20:55:36-102706 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:36-102963 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:36-103170 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:36-103369 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:36-103571 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:36-103805 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:36-103985 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:36-104208 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:36-104499 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:36-104721 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:36-104960 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:36-105168 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:36-105506 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:36-105707 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:36-105931 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:36-106113 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:36-106289 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:36-106496 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:36-106708 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:36-106931 util-scheduler-8620 DEBUG Adding task: 3728 / 0x59ee8a0
Jul 07 20:55:36-107115 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:36-107335 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:36-107511 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:36-107686 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:36-107927 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:36-108122 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:36-108300 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:36-108500 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:36-108744 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:36-108943 util-scheduler-8620 DEBUG Adding task: 3729 / 0x52cbfb8
Jul 07 20:55:36-109222 util-scheduler-8620 DEBUG Checking readiness of task: 3726 / 0x46620a0
Jul 07 20:55:36-109417 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-109609 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-109799 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-109988 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-110179 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-110367 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-110557 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-110749 util-scheduler-8620 DEBUG Running task: 3728 / 0x59ee8a0
Jul 07 20:55:36-110957 util-scheduler-8620 DEBUG Adding task: 3730 / 0x59ee8a0
Jul 07 20:55:36-111179 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:36-111383 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:36-111590 util-scheduler-8620 DEBUG Adding task: 3731 / 0x46620a0
Jul 07 20:55:36-111833 util-scheduler-8620 DEBUG Checking readiness of task: 3731 / 0x46620a0
Jul 07 20:55:36-112028 util-scheduler-8620 DEBUG Checking readiness of task: 3726 / 0x46620a0
Jul 07 20:55:36-112218 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-112408 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-112597 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-112787 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-112978 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-113168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-113376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-113569 util-scheduler-8620 DEBUG Running task: 3731 / 0x46620a0
Jul 07 20:55:36-113754 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:36-113933 util-8620 DEBUG process_notify is running
Jul 07 20:55:36-114120 util-8620 DEBUG client_notify is running
Jul 07 20:55:36-114299 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:36-114510 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:36-114702 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:36-114955 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:36-115204 util-scheduler-8620 DEBUG Checking readiness of task: 3726 / 0x46620a0
Jul 07 20:55:36-115395 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-115585 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-115776 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-115968 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-116158 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-116347 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-116536 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-116725 util-scheduler-8620 DEBUG Running task: 3726 / 0x46620a0
Jul 07 20:55:36-117128 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:36-117417 util-scheduler-8620 DEBUG Adding task: 3732 / 0x4662248
Jul 07 20:55:36-117666 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-117858 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-118048 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-118238 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-118428 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-118617 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-118805 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-118994 util-scheduler-8620 DEBUG Running task: 3732 / 0x4662248
Jul 07 20:55:36-119184 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:36-119381 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:36-119598 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:36-119797 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:36-119998 util-scheduler-8620 DEBUG Adding task: 3733 / 0x46620a0
Jul 07 20:55:36-120183 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:36-120390 util-scheduler-8620 DEBUG Adding task: 3734 / 0x46620a0
Jul 07 20:55:36-120633 util-scheduler-8620 DEBUG Checking readiness of task: 3734 / 0x46620a0
Jul 07 20:55:36-120832 util-scheduler-8620 DEBUG Checking readiness of task: 3733 / 0x46620a0
Jul 07 20:55:36-121025 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:36-121235 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:36-121427 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:36-121618 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:36-121808 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:36-121998 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:36-122187 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:36-122377 util-scheduler-8620 DEBUG Running task: 3733 / 0x46620a0
Jul 07 20:55:36-122562 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:36-122737 util-8620 DEBUG process_notify is running
Jul 07 20:55:36-122906 util-8620 DEBUG client_notify is running
Jul 07 20:55:36-123093 util-scheduler-8620 DEBUG Canceling task: 3730 / 0x59ee8a0
Jul 07 20:55:36-123316 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:36-123532 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:36-123785 cadet-p2p-8620 DEBUG Checking 0x608a058 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:36-124019 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:36-124197 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:36-124384 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:36-124666 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:36-124859 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:36-125099 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:36-125325 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:36-125516 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:36-125697 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:36-125944 util-scheduler-8620 DEBUG Canceling task: 3727 / 0x59e8808
Jul 07 20:55:36-126160 util-scheduler-8620 DEBUG Adding task: 3735 / 0x59e8808
Jul 07 20:55:36-126477 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:36-126648 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:36-126830 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:36-127034 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:36-127209 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:36-127383 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:36-127583 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:36-127787 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:36-127970 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:36-128151 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:36-128342 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:36-128587 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:41-112403 util-scheduler-8620 DEBUG Checking readiness of task: 3734 / 0x46620a0
Jul 07 20:55:41-112798 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-113744 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-113956 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-114207 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-114417 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-114609 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-114799 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-114993 util-scheduler-8620 DEBUG Running task: 3729 / 0x52cbfb8
Jul 07 20:55:41-115232 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:41-115489 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:41-115696 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:41-115898 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:41-116100 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:41-116335 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:41-116518 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:41-116740 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:41-117031 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:41-117249 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:41-117490 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:41-117698 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:41-118015 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:41-118215 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:41-118440 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:41-118623 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:41-118799 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:41-119030 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:41-119245 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:41-119469 util-scheduler-8620 DEBUG Adding task: 3736 / 0x59ee8a0
Jul 07 20:55:41-119651 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:41-119854 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:41-120043 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:41-120218 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:41-120457 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:41-120652 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:41-120830 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:41-121029 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:41-121292 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:41-121490 util-scheduler-8620 DEBUG Adding task: 3737 / 0x52cbfb8
Jul 07 20:55:41-121773 util-scheduler-8620 DEBUG Checking readiness of task: 3734 / 0x46620a0
Jul 07 20:55:41-121967 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-122157 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-122347 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-122536 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-122727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-122916 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-123104 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-123293 util-scheduler-8620 DEBUG Running task: 3736 / 0x59ee8a0
Jul 07 20:55:41-123500 util-scheduler-8620 DEBUG Adding task: 3738 / 0x59ee8a0
Jul 07 20:55:41-123722 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:41-123930 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:41-124138 util-scheduler-8620 DEBUG Adding task: 3739 / 0x46620a0
Jul 07 20:55:41-124382 util-scheduler-8620 DEBUG Checking readiness of task: 3739 / 0x46620a0
Jul 07 20:55:41-124575 util-scheduler-8620 DEBUG Checking readiness of task: 3734 / 0x46620a0
Jul 07 20:55:41-124766 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-124956 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-125146 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-125366 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-125558 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-125749 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-125939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-126131 util-scheduler-8620 DEBUG Running task: 3739 / 0x46620a0
Jul 07 20:55:41-126316 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:41-126494 util-8620 DEBUG process_notify is running
Jul 07 20:55:41-126669 util-8620 DEBUG client_notify is running
Jul 07 20:55:41-126848 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:41-127044 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:41-127234 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:41-127485 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:41-127735 util-scheduler-8620 DEBUG Checking readiness of task: 3734 / 0x46620a0
Jul 07 20:55:41-127928 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-128118 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-128308 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-128514 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-128704 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-128893 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-129081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-129292 util-scheduler-8620 DEBUG Running task: 3734 / 0x46620a0
Jul 07 20:55:41-129697 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:41-129929 util-scheduler-8620 DEBUG Adding task: 3740 / 0x4662248
Jul 07 20:55:41-130176 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-130368 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-130558 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-130748 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-130939 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-131127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-131316 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-131505 util-scheduler-8620 DEBUG Running task: 3740 / 0x4662248
Jul 07 20:55:41-131694 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:41-131890 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:41-132107 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:41-132306 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:41-132505 util-scheduler-8620 DEBUG Adding task: 3741 / 0x46620a0
Jul 07 20:55:41-132689 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:41-132893 util-scheduler-8620 DEBUG Adding task: 3742 / 0x46620a0
Jul 07 20:55:41-133134 util-scheduler-8620 DEBUG Checking readiness of task: 3742 / 0x46620a0
Jul 07 20:55:41-133346 util-scheduler-8620 DEBUG Checking readiness of task: 3741 / 0x46620a0
Jul 07 20:55:41-133557 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:41-133748 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:41-133942 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:41-134133 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:41-134322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:41-134511 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:41-134699 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:41-134890 util-scheduler-8620 DEBUG Running task: 3741 / 0x46620a0
Jul 07 20:55:41-135074 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:41-135250 util-8620 DEBUG process_notify is running
Jul 07 20:55:41-135419 util-8620 DEBUG client_notify is running
Jul 07 20:55:41-135605 util-scheduler-8620 DEBUG Canceling task: 3738 / 0x59ee8a0
Jul 07 20:55:41-135827 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:41-136043 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:41-136274 cadet-p2p-8620 DEBUG Checking 0x608b540 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:41-136507 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:41-136685 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:41-136873 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:41-137156 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:41-137386 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:41-137567 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:41-137754 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:41-137960 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:41-138138 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:41-138321 util-scheduler-8620 DEBUG Canceling task: 3735 / 0x59e8808
Jul 07 20:55:41-138531 util-scheduler-8620 DEBUG Adding task: 3743 / 0x59e8808
Jul 07 20:55:41-138774 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:41-138943 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:41-139123 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:41-139322 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:41-139495 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:41-139668 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:41-139867 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:41-140071 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:41-140256 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:41-140473 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:41-140666 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:41-140909 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:46-126644 util-scheduler-8620 DEBUG Checking readiness of task: 3742 / 0x46620a0
Jul 07 20:55:46-127050 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-127631 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-127830 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-128092 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-128305 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-128496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-128687 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-128881 util-scheduler-8620 DEBUG Running task: 3737 / 0x52cbfb8
Jul 07 20:55:46-129121 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:46-129407 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:46-129615 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:46-129818 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:46-130020 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:46-130255 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:46-130436 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:46-130657 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:46-130950 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:46-131149 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:46-131388 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:46-131596 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:46-131913 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:46-132114 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:46-132338 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:46-132521 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:46-132696 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:46-132904 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:46-133120 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:46-133367 util-scheduler-8620 DEBUG Adding task: 3744 / 0x59ee8a0
Jul 07 20:55:46-133550 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:46-133754 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:46-133930 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:46-134105 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:46-134343 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:46-134574 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:46-134753 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:46-134952 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:46-135196 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:46-135394 util-scheduler-8620 DEBUG Adding task: 3745 / 0x52cbfb8
Jul 07 20:55:46-135655 util-scheduler-8620 DEBUG Checking readiness of task: 3742 / 0x46620a0
Jul 07 20:55:46-135847 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-136038 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-136227 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-136417 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-136607 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-136796 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-136986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-137176 util-scheduler-8620 DEBUG Running task: 3744 / 0x59ee8a0
Jul 07 20:55:46-137406 util-scheduler-8620 DEBUG Adding task: 3746 / 0x59ee8a0
Jul 07 20:55:46-137628 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:46-137832 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:46-138039 util-scheduler-8620 DEBUG Adding task: 3747 / 0x46620a0
Jul 07 20:55:46-138282 util-scheduler-8620 DEBUG Checking readiness of task: 3747 / 0x46620a0
Jul 07 20:55:46-138474 util-scheduler-8620 DEBUG Checking readiness of task: 3742 / 0x46620a0
Jul 07 20:55:46-138665 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-138854 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-139044 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-139234 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-139423 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-139612 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-139800 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-139992 util-scheduler-8620 DEBUG Running task: 3747 / 0x46620a0
Jul 07 20:55:46-140176 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:46-140356 util-8620 DEBUG process_notify is running
Jul 07 20:55:46-140528 util-8620 DEBUG client_notify is running
Jul 07 20:55:46-140708 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:46-140903 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:46-141094 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:46-141371 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:46-141621 util-scheduler-8620 DEBUG Checking readiness of task: 3742 / 0x46620a0
Jul 07 20:55:46-141813 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-142004 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-142194 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-142383 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-142573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-142763 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-142951 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-143142 util-scheduler-8620 DEBUG Running task: 3742 / 0x46620a0
Jul 07 20:55:46-143555 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:46-143786 util-scheduler-8620 DEBUG Adding task: 3748 / 0x4662248
Jul 07 20:55:46-144050 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-144243 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-144433 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-144623 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-144813 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-145001 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-145208 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-145399 util-scheduler-8620 DEBUG Running task: 3748 / 0x4662248
Jul 07 20:55:46-145634 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:46-145832 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:46-146049 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:46-146247 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:46-146446 util-scheduler-8620 DEBUG Adding task: 3749 / 0x46620a0
Jul 07 20:55:46-146632 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:46-146835 util-scheduler-8620 DEBUG Adding task: 3750 / 0x46620a0
Jul 07 20:55:46-147077 util-scheduler-8620 DEBUG Checking readiness of task: 3750 / 0x46620a0
Jul 07 20:55:46-147268 util-scheduler-8620 DEBUG Checking readiness of task: 3749 / 0x46620a0
Jul 07 20:55:46-147459 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:46-147649 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:46-147864 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:46-148055 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:46-148245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:46-148434 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:46-148623 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:46-148824 util-scheduler-8620 DEBUG Running task: 3749 / 0x46620a0
Jul 07 20:55:46-149007 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:46-149182 util-8620 DEBUG process_notify is running
Jul 07 20:55:46-149372 util-8620 DEBUG client_notify is running
Jul 07 20:55:46-149557 util-scheduler-8620 DEBUG Canceling task: 3746 / 0x59ee8a0
Jul 07 20:55:46-149780 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:46-149998 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:46-150229 cadet-p2p-8620 DEBUG Checking 0x51dcd60 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:46-150463 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:46-150641 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:46-150828 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:46-151109 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:46-151303 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:46-151482 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:46-151669 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:46-151858 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:46-152036 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:46-152219 util-scheduler-8620 DEBUG Canceling task: 3743 / 0x59e8808
Jul 07 20:55:46-152429 util-scheduler-8620 DEBUG Adding task: 3751 / 0x59e8808
Jul 07 20:55:46-152672 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:46-152842 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:46-153023 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:46-153242 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:46-153417 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:46-153594 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:46-153809 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:46-154015 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:46-154197 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:46-154375 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:46-154563 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:46-154810 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:51-140543 util-scheduler-8620 DEBUG Checking readiness of task: 3750 / 0x46620a0
Jul 07 20:55:51-140938 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-141553 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-141777 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-141997 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-142206 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-142398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-142588 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-142782 util-scheduler-8620 DEBUG Running task: 3745 / 0x52cbfb8
Jul 07 20:55:51-143022 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:51-143278 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:51-143485 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:51-143686 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:51-143888 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:51-144123 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:51-144304 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:51-144526 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:51-144817 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:51-145014 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:51-145276 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:51-145485 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:51-145803 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:51-146004 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:51-146231 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:51-146414 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:51-146590 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:51-146797 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:51-147011 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:51-147234 util-scheduler-8620 DEBUG Adding task: 3752 / 0x59ee8a0
Jul 07 20:55:51-147414 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:51-147617 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:51-147793 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:51-147968 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:51-148206 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:51-148401 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:51-148579 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:51-148777 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:51-149020 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:51-149236 util-scheduler-8620 DEBUG Adding task: 3753 / 0x52cbfb8
Jul 07 20:55:51-149499 util-scheduler-8620 DEBUG Checking readiness of task: 3750 / 0x46620a0
Jul 07 20:55:51-149691 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-149918 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-150137 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-150329 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-150519 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-150708 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-150897 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-151087 util-scheduler-8620 DEBUG Running task: 3752 / 0x59ee8a0
Jul 07 20:55:51-151296 util-scheduler-8620 DEBUG Adding task: 3754 / 0x59ee8a0
Jul 07 20:55:51-151519 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:51-151722 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:51-151930 util-scheduler-8620 DEBUG Adding task: 3755 / 0x46620a0
Jul 07 20:55:51-152174 util-scheduler-8620 DEBUG Checking readiness of task: 3755 / 0x46620a0
Jul 07 20:55:51-152368 util-scheduler-8620 DEBUG Checking readiness of task: 3750 / 0x46620a0
Jul 07 20:55:51-152558 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-152748 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-152938 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-153128 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-153340 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-153531 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-153720 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-153912 util-scheduler-8620 DEBUG Running task: 3755 / 0x46620a0
Jul 07 20:55:51-154097 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:51-154276 util-8620 DEBUG process_notify is running
Jul 07 20:55:51-154448 util-8620 DEBUG client_notify is running
Jul 07 20:55:51-154627 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:51-154823 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:51-155013 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:51-155268 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:51-155517 util-scheduler-8620 DEBUG Checking readiness of task: 3750 / 0x46620a0
Jul 07 20:55:51-155710 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-155900 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-156102 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-156296 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-156487 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-156676 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-156865 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-157055 util-scheduler-8620 DEBUG Running task: 3750 / 0x46620a0
Jul 07 20:55:51-157480 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:51-157712 util-scheduler-8620 DEBUG Adding task: 3756 / 0x4662248
Jul 07 20:55:51-157960 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-158152 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-158343 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-158533 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-158723 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-158911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-159100 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-159305 util-scheduler-8620 DEBUG Running task: 3756 / 0x4662248
Jul 07 20:55:51-159495 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:51-159690 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:51-159907 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:51-160104 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:51-160303 util-scheduler-8620 DEBUG Adding task: 3757 / 0x46620a0
Jul 07 20:55:51-160488 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:51-160691 util-scheduler-8620 DEBUG Adding task: 3758 / 0x46620a0
Jul 07 20:55:51-160931 util-scheduler-8620 DEBUG Checking readiness of task: 3758 / 0x46620a0
Jul 07 20:55:51-161123 util-scheduler-8620 DEBUG Checking readiness of task: 3757 / 0x46620a0
Jul 07 20:55:51-161335 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:51-161527 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:51-161717 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:51-161907 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:51-162097 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:51-162286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:51-162475 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:51-162665 util-scheduler-8620 DEBUG Running task: 3757 / 0x46620a0
Jul 07 20:55:51-162849 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:51-163024 util-8620 DEBUG process_notify is running
Jul 07 20:55:51-163193 util-8620 DEBUG client_notify is running
Jul 07 20:55:51-163378 util-scheduler-8620 DEBUG Canceling task: 3754 / 0x59ee8a0
Jul 07 20:55:51-163600 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:51-163817 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:51-164049 cadet-p2p-8620 DEBUG Checking 0x608d920 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:51-164282 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:51-164459 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:51-164646 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:51-164928 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:51-165122 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:51-165320 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:51-165508 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:51-165697 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:51-165875 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:51-166058 util-scheduler-8620 DEBUG Canceling task: 3751 / 0x59e8808
Jul 07 20:55:51-166272 util-scheduler-8620 DEBUG Adding task: 3759 / 0x59e8808
Jul 07 20:55:51-166517 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:51-166688 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:51-166869 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:51-167069 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:51-167243 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:51-167417 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:51-167616 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:51-167820 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:51-168003 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:51-168180 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:51-168369 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:51-168612 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:56-154367 util-scheduler-8620 DEBUG Checking readiness of task: 3758 / 0x46620a0
Jul 07 20:55:56-154792 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-155371 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-155568 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-155814 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-156023 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-156215 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-156406 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-156601 util-scheduler-8620 DEBUG Running task: 3753 / 0x52cbfb8
Jul 07 20:55:56-156841 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:55:56-157097 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:55:56-157328 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:55:56-157530 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:55:56-157732 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:55:56-157967 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:55:56-158148 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:55:56-158370 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:55:56-158662 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:55:56-158858 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:55:56-159096 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:55:56-159305 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:55:56-159622 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:55:56-159823 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:55:56-160049 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:55:56-160232 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:55:56-160408 cadet-con-8620 DEBUG  sendable
Jul 07 20:55:56-160615 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:55:56-160829 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:55:56-161053 util-scheduler-8620 DEBUG Adding task: 3760 / 0x59ee8a0
Jul 07 20:55:56-161253 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:55:56-161458 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:56-161635 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:55:56-161809 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:55:56-162048 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:55:56-162243 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:55:56-162420 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:55:56-162619 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:56-162863 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:55:56-163062 util-scheduler-8620 DEBUG Adding task: 3761 / 0x52cbfb8
Jul 07 20:55:56-163322 util-scheduler-8620 DEBUG Checking readiness of task: 3758 / 0x46620a0
Jul 07 20:55:56-163530 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-163721 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-163912 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-164102 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-164291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-164480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-164669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-164858 util-scheduler-8620 DEBUG Running task: 3760 / 0x59ee8a0
Jul 07 20:55:56-165066 util-scheduler-8620 DEBUG Adding task: 3762 / 0x59ee8a0
Jul 07 20:55:56-165312 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:55:56-165537 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:56-165747 util-scheduler-8620 DEBUG Adding task: 3763 / 0x46620a0
Jul 07 20:55:56-165993 util-scheduler-8620 DEBUG Checking readiness of task: 3763 / 0x46620a0
Jul 07 20:55:56-166186 util-scheduler-8620 DEBUG Checking readiness of task: 3758 / 0x46620a0
Jul 07 20:55:56-166376 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-166566 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-166754 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-166944 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-167133 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-167322 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-167514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-167705 util-scheduler-8620 DEBUG Running task: 3763 / 0x46620a0
Jul 07 20:55:56-167890 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:56-168068 util-8620 DEBUG process_notify is running
Jul 07 20:55:56-168241 util-8620 DEBUG client_notify is running
Jul 07 20:55:56-168420 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:55:56-168615 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:56-168806 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:55:56-169059 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:55:56-169327 util-scheduler-8620 DEBUG Checking readiness of task: 3758 / 0x46620a0
Jul 07 20:55:56-169520 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-169710 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-169900 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-170090 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-170280 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-170469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-170659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-170849 util-scheduler-8620 DEBUG Running task: 3758 / 0x46620a0
Jul 07 20:55:56-171268 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:55:56-171500 util-scheduler-8620 DEBUG Adding task: 3764 / 0x4662248
Jul 07 20:55:56-171747 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-171939 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-172129 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-172320 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-172510 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-172699 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-172887 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-173077 util-scheduler-8620 DEBUG Running task: 3764 / 0x4662248
Jul 07 20:55:56-173289 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:55:56-173486 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:55:56-173704 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:55:56-173902 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:55:56-174100 util-scheduler-8620 DEBUG Adding task: 3765 / 0x46620a0
Jul 07 20:55:56-174285 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:55:56-174505 util-scheduler-8620 DEBUG Adding task: 3766 / 0x46620a0
Jul 07 20:55:56-174747 util-scheduler-8620 DEBUG Checking readiness of task: 3766 / 0x46620a0
Jul 07 20:55:56-174938 util-scheduler-8620 DEBUG Checking readiness of task: 3765 / 0x46620a0
Jul 07 20:55:56-175129 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:55:56-175319 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:55:56-175508 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:55:56-175698 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:55:56-175888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:55:56-176077 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:55:56-176266 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:55:56-176456 util-scheduler-8620 DEBUG Running task: 3765 / 0x46620a0
Jul 07 20:55:56-176640 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:55:56-176815 util-8620 DEBUG process_notify is running
Jul 07 20:55:56-176983 util-8620 DEBUG client_notify is running
Jul 07 20:55:56-177168 util-scheduler-8620 DEBUG Canceling task: 3762 / 0x59ee8a0
Jul 07 20:55:56-177413 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:55:56-177630 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:55:56-177867 cadet-p2p-8620 DEBUG Checking 0x51e0948 towards 2FDYFV0X (->V8XX)
Jul 07 20:55:56-178103 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:55:56-178297 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:55:56-178487 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:55:56-178774 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:55:56-178969 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:55:56-179147 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:55:56-179336 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:55:56-179526 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:55:56-179704 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:55:56-179890 util-scheduler-8620 DEBUG Canceling task: 3759 / 0x59e8808
Jul 07 20:55:56-180104 util-scheduler-8620 DEBUG Adding task: 3767 / 0x59e8808
Jul 07 20:55:56-180348 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:55:56-180519 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:55:56-180700 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:55:56-180899 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:55:56-181074 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:55:56-181277 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:55:56-181477 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:55:56-181680 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:55:56-181862 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:55:56-182039 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:55:56-182227 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:55:56-182472 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:01-168210 util-scheduler-8620 DEBUG Checking readiness of task: 3766 / 0x46620a0
Jul 07 20:56:01-168601 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-169176 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-169419 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-169653 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-169848 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-170040 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-170231 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-170450 util-scheduler-8620 DEBUG Running task: 3761 / 0x52cbfb8
Jul 07 20:56:01-170690 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:01-170960 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:56:01-171167 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:01-171368 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:01-171570 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:01-171824 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:01-172005 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:01-172229 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:01-172524 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:01-172721 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:01-172960 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:01-173168 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:01-173509 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:01-173710 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:01-173934 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:01-174118 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:01-174293 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:01-174499 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:01-174712 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:01-174938 util-scheduler-8620 DEBUG Adding task: 3768 / 0x59ee8a0
Jul 07 20:56:01-175119 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:01-175323 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:01-175499 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:01-175675 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:01-175913 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:01-176109 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:01-176287 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:01-176486 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:01-176729 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:01-176928 util-scheduler-8620 DEBUG Adding task: 3769 / 0x52cbfb8
Jul 07 20:56:01-177187 util-scheduler-8620 DEBUG Checking readiness of task: 3766 / 0x46620a0
Jul 07 20:56:01-177399 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-177590 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-177780 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-177969 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-178160 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-178353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-178547 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-178739 util-scheduler-8620 DEBUG Running task: 3768 / 0x59ee8a0
Jul 07 20:56:01-178950 util-scheduler-8620 DEBUG Adding task: 3770 / 0x59ee8a0
Jul 07 20:56:01-179174 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:01-179378 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:01-179589 util-scheduler-8620 DEBUG Adding task: 3771 / 0x46620a0
Jul 07 20:56:01-179837 util-scheduler-8620 DEBUG Checking readiness of task: 3771 / 0x46620a0
Jul 07 20:56:01-180033 util-scheduler-8620 DEBUG Checking readiness of task: 3766 / 0x46620a0
Jul 07 20:56:01-180223 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-180414 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-180604 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-180815 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-181007 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-181218 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-181410 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-181602 util-scheduler-8620 DEBUG Running task: 3771 / 0x46620a0
Jul 07 20:56:01-181787 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:01-181967 util-8620 DEBUG process_notify is running
Jul 07 20:56:01-182140 util-8620 DEBUG client_notify is running
Jul 07 20:56:01-182319 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:01-182515 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:01-182705 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:01-182958 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:01-183207 util-scheduler-8620 DEBUG Checking readiness of task: 3766 / 0x46620a0
Jul 07 20:56:01-183399 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-183589 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-183779 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-183969 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-184159 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-184346 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-184534 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-184724 util-scheduler-8620 DEBUG Running task: 3766 / 0x46620a0
Jul 07 20:56:01-185129 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:01-185390 util-scheduler-8620 DEBUG Adding task: 3772 / 0x4662248
Jul 07 20:56:01-185640 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-185833 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-186024 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-186214 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-186405 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-186594 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-186783 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-186973 util-scheduler-8620 DEBUG Running task: 3772 / 0x4662248
Jul 07 20:56:01-187163 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:01-187360 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:01-187578 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:01-187776 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:01-187976 util-scheduler-8620 DEBUG Adding task: 3773 / 0x46620a0
Jul 07 20:56:01-188161 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:01-188366 util-scheduler-8620 DEBUG Adding task: 3774 / 0x46620a0
Jul 07 20:56:01-188609 util-scheduler-8620 DEBUG Checking readiness of task: 3774 / 0x46620a0
Jul 07 20:56:01-188842 util-scheduler-8620 DEBUG Checking readiness of task: 3773 / 0x46620a0
Jul 07 20:56:01-189036 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:01-189246 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:01-189438 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:01-189629 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:01-189820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:01-190026 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:01-190216 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:01-190407 util-scheduler-8620 DEBUG Running task: 3773 / 0x46620a0
Jul 07 20:56:01-190592 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:01-190767 util-8620 DEBUG process_notify is running
Jul 07 20:56:01-190937 util-8620 DEBUG client_notify is running
Jul 07 20:56:01-191123 util-scheduler-8620 DEBUG Canceling task: 3770 / 0x59ee8a0
Jul 07 20:56:01-191347 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:01-191563 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:01-191795 cadet-p2p-8620 DEBUG Checking 0x608fc10 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:01-192029 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:01-192218 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:01-192406 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:01-192687 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:01-192882 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:01-193061 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:01-193269 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:01-193459 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:01-193637 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:01-193821 util-scheduler-8620 DEBUG Canceling task: 3767 / 0x59e8808
Jul 07 20:56:01-194032 util-scheduler-8620 DEBUG Adding task: 3775 / 0x59e8808
Jul 07 20:56:01-194275 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:01-194446 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:01-194626 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:01-194825 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:01-194999 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:01-195173 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:01-195371 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:01-195575 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:01-195759 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:01-195938 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:01-196221 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:01-196714 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:06-180180 util-scheduler-8620 DEBUG Checking readiness of task: 3774 / 0x46620a0
Jul 07 20:56:06-180585 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-181042 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-181362 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-181575 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-181772 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-181964 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-182155 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-182350 util-scheduler-8620 DEBUG Running task: 3769 / 0x52cbfb8
Jul 07 20:56:06-182589 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:06-182848 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:56:06-183056 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:06-183256 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:06-183460 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:06-183695 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:06-183875 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:06-184098 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:06-184411 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:06-184612 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:06-184850 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:06-185058 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:06-185416 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:06-185628 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:06-185856 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:06-186039 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:06-186215 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:06-186421 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:06-186636 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:06-186862 util-scheduler-8620 DEBUG Adding task: 3776 / 0x59ee8a0
Jul 07 20:56:06-187043 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:06-187246 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:06-187423 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:06-187598 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:06-187838 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:06-188034 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:06-188211 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:06-188411 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:06-188654 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:06-188852 util-scheduler-8620 DEBUG Adding task: 3777 / 0x52cbfb8
Jul 07 20:56:06-189113 util-scheduler-8620 DEBUG Checking readiness of task: 3774 / 0x46620a0
Jul 07 20:56:06-189334 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-189525 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-189718 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-189908 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-190098 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-190288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-190477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-190667 util-scheduler-8620 DEBUG Running task: 3776 / 0x59ee8a0
Jul 07 20:56:06-190875 util-scheduler-8620 DEBUG Adding task: 3778 / 0x59ee8a0
Jul 07 20:56:06-191098 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:06-191301 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:06-191509 util-scheduler-8620 DEBUG Adding task: 3779 / 0x46620a0
Jul 07 20:56:06-191754 util-scheduler-8620 DEBUG Checking readiness of task: 3779 / 0x46620a0
Jul 07 20:56:06-191947 util-scheduler-8620 DEBUG Checking readiness of task: 3774 / 0x46620a0
Jul 07 20:56:06-192138 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-192328 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-192518 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-192710 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-192901 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-193089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-193299 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-193492 util-scheduler-8620 DEBUG Running task: 3779 / 0x46620a0
Jul 07 20:56:06-193678 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:06-193857 util-8620 DEBUG process_notify is running
Jul 07 20:56:06-194029 util-8620 DEBUG client_notify is running
Jul 07 20:56:06-194225 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:06-194421 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:06-194611 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:06-194866 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:06-195115 util-scheduler-8620 DEBUG Checking readiness of task: 3774 / 0x46620a0
Jul 07 20:56:06-195308 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-195498 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-195688 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-195878 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-196068 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-196256 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-196446 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-196637 util-scheduler-8620 DEBUG Running task: 3774 / 0x46620a0
Jul 07 20:56:06-197040 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:06-197291 util-scheduler-8620 DEBUG Adding task: 3780 / 0x4662248
Jul 07 20:56:06-197540 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-197746 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-197936 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-198126 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-198317 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-198506 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-198695 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-198885 util-scheduler-8620 DEBUG Running task: 3780 / 0x4662248
Jul 07 20:56:06-199075 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:06-199272 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:06-199489 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:06-199689 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:06-199889 util-scheduler-8620 DEBUG Adding task: 3781 / 0x46620a0
Jul 07 20:56:06-200074 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:06-200278 util-scheduler-8620 DEBUG Adding task: 3782 / 0x46620a0
Jul 07 20:56:06-200518 util-scheduler-8620 DEBUG Checking readiness of task: 3782 / 0x46620a0
Jul 07 20:56:06-200710 util-scheduler-8620 DEBUG Checking readiness of task: 3781 / 0x46620a0
Jul 07 20:56:06-200902 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:06-201091 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:06-201301 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:06-201491 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:06-201681 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:06-201871 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:06-202059 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:06-202249 util-scheduler-8620 DEBUG Running task: 3781 / 0x46620a0
Jul 07 20:56:06-202433 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:06-202610 util-8620 DEBUG process_notify is running
Jul 07 20:56:06-202779 util-8620 DEBUG client_notify is running
Jul 07 20:56:06-202963 util-scheduler-8620 DEBUG Canceling task: 3778 / 0x59ee8a0
Jul 07 20:56:06-203186 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:06-203419 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:06-203651 cadet-p2p-8620 DEBUG Checking 0x51e52a0 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:06-203884 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:06-204063 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:06-204249 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:06-204532 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:06-204727 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:06-204906 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:06-205094 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:06-205303 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:06-205481 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:06-205664 util-scheduler-8620 DEBUG Canceling task: 3775 / 0x59e8808
Jul 07 20:56:06-205873 util-scheduler-8620 DEBUG Adding task: 3783 / 0x59e8808
Jul 07 20:56:06-206115 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:06-206285 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:06-206466 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:06-206665 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:06-206840 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:06-207013 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:06-207210 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:06-207415 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:06-207597 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:06-207774 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:06-207963 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:06-208208 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:11-193733 util-scheduler-8620 DEBUG Checking readiness of task: 3782 / 0x46620a0
Jul 07 20:56:11-194131 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-194925 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-195370 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-195571 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-195765 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-195957 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-196152 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-196347 util-scheduler-8620 DEBUG Running task: 3777 / 0x52cbfb8
Jul 07 20:56:11-196588 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:11-196846 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:56:11-197053 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:11-197281 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:11-197485 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:11-197721 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:11-197902 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:11-198141 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:11-198575 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:11-198778 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:11-199017 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:11-199226 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:11-199546 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:11-199747 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:11-199972 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:11-200195 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:11-200373 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:11-200581 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:11-200795 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:11-201025 util-scheduler-8620 DEBUG Adding task: 3784 / 0x59ee8a0
Jul 07 20:56:11-201228 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:11-201433 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:11-201610 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:11-201784 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:11-202022 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:11-202218 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:11-202395 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:11-202593 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:11-202838 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:11-203035 util-scheduler-8620 DEBUG Adding task: 3785 / 0x52cbfb8
Jul 07 20:56:11-203302 util-scheduler-8620 DEBUG Checking readiness of task: 3782 / 0x46620a0
Jul 07 20:56:11-203495 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-203685 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-203874 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-204065 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-204255 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-204444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-204631 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-204820 util-scheduler-8620 DEBUG Running task: 3784 / 0x59ee8a0
Jul 07 20:56:11-205028 util-scheduler-8620 DEBUG Adding task: 3786 / 0x59ee8a0
Jul 07 20:56:11-205284 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:11-205488 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:11-205696 util-scheduler-8620 DEBUG Adding task: 3787 / 0x46620a0
Jul 07 20:56:11-205941 util-scheduler-8620 DEBUG Checking readiness of task: 3787 / 0x46620a0
Jul 07 20:56:11-206135 util-scheduler-8620 DEBUG Checking readiness of task: 3782 / 0x46620a0
Jul 07 20:56:11-206325 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-206516 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-206705 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-206894 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-207083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-207272 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-207461 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-207652 util-scheduler-8620 DEBUG Running task: 3787 / 0x46620a0
Jul 07 20:56:11-207836 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:11-208014 util-8620 DEBUG process_notify is running
Jul 07 20:56:11-208187 util-8620 DEBUG client_notify is running
Jul 07 20:56:11-208366 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:11-208563 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:11-208755 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:11-209011 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:11-209281 util-scheduler-8620 DEBUG Checking readiness of task: 3782 / 0x46620a0
Jul 07 20:56:11-209475 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-209666 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-209872 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-210063 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-210253 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-210441 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-210629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-210818 util-scheduler-8620 DEBUG Running task: 3782 / 0x46620a0
Jul 07 20:56:11-211227 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:11-211457 util-scheduler-8620 DEBUG Adding task: 3788 / 0x4662248
Jul 07 20:56:11-211704 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-211896 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-212086 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-212276 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-212466 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-212655 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-212843 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-213032 util-scheduler-8620 DEBUG Running task: 3788 / 0x4662248
Jul 07 20:56:11-213240 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:11-213438 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:11-213654 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:11-213850 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:11-214048 util-scheduler-8620 DEBUG Adding task: 3789 / 0x46620a0
Jul 07 20:56:11-214232 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:11-214436 util-scheduler-8620 DEBUG Adding task: 3790 / 0x46620a0
Jul 07 20:56:11-214680 util-scheduler-8620 DEBUG Checking readiness of task: 3790 / 0x46620a0
Jul 07 20:56:11-214873 util-scheduler-8620 DEBUG Checking readiness of task: 3789 / 0x46620a0
Jul 07 20:56:11-215066 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:11-215256 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:11-215445 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:11-215635 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:11-215824 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:11-216013 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:11-216201 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:11-216391 util-scheduler-8620 DEBUG Running task: 3789 / 0x46620a0
Jul 07 20:56:11-216575 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:11-216750 util-8620 DEBUG process_notify is running
Jul 07 20:56:11-216918 util-8620 DEBUG client_notify is running
Jul 07 20:56:11-217104 util-scheduler-8620 DEBUG Canceling task: 3786 / 0x59ee8a0
Jul 07 20:56:11-217349 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:11-217565 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:11-217796 cadet-p2p-8620 DEBUG Checking 0x6092620 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:11-218029 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:11-218207 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:11-218394 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:11-218676 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:11-218871 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:11-219049 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:11-219253 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:11-219443 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:11-219621 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:11-219804 util-scheduler-8620 DEBUG Canceling task: 3783 / 0x59e8808
Jul 07 20:56:11-220014 util-scheduler-8620 DEBUG Adding task: 3791 / 0x59e8808
Jul 07 20:56:11-220256 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:11-220427 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:11-220607 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:11-220805 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:11-220983 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:11-221156 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:11-221374 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:11-221578 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:11-221761 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:11-221938 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:11-222126 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:11-222372 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:16-208179 util-scheduler-8620 DEBUG Checking readiness of task: 3790 / 0x46620a0
Jul 07 20:56:16-208573 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-209181 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-209425 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-209646 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-209854 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-210045 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-210235 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-210427 util-scheduler-8620 DEBUG Running task: 3785 / 0x52cbfb8
Jul 07 20:56:16-210667 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:16-210925 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:56:16-211132 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:16-211332 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:16-211534 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:16-211769 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:16-211949 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:16-212173 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:16-212465 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:16-212676 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:16-212915 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:16-213123 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:16-213464 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:16-213663 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:16-213888 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:16-214071 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:16-214246 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:16-214453 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:16-214667 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:16-214893 util-scheduler-8620 DEBUG Adding task: 3792 / 0x59ee8a0
Jul 07 20:56:16-215074 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:16-215277 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:16-215453 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:16-215628 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:16-215892 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:16-216088 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:16-216266 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:16-216466 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:16-216730 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:16-216930 util-scheduler-8620 DEBUG Adding task: 3793 / 0x52cbfb8
Jul 07 20:56:16-217214 util-scheduler-8620 DEBUG Checking readiness of task: 3790 / 0x46620a0
Jul 07 20:56:16-217410 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-217600 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-217790 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-217980 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-218171 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-218360 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-218550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-218739 util-scheduler-8620 DEBUG Running task: 3792 / 0x59ee8a0
Jul 07 20:56:16-218947 util-scheduler-8620 DEBUG Adding task: 3794 / 0x59ee8a0
Jul 07 20:56:16-219170 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:16-219374 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:16-219583 util-scheduler-8620 DEBUG Adding task: 3795 / 0x46620a0
Jul 07 20:56:16-219827 util-scheduler-8620 DEBUG Checking readiness of task: 3795 / 0x46620a0
Jul 07 20:56:16-220021 util-scheduler-8620 DEBUG Checking readiness of task: 3790 / 0x46620a0
Jul 07 20:56:16-220212 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-220402 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-220592 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-220782 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-220972 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-221161 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-221369 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-221561 util-scheduler-8620 DEBUG Running task: 3795 / 0x46620a0
Jul 07 20:56:16-221746 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:16-221924 util-8620 DEBUG process_notify is running
Jul 07 20:56:16-222100 util-8620 DEBUG client_notify is running
Jul 07 20:56:16-222278 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:16-222474 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:16-222664 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:16-222916 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:16-223164 util-scheduler-8620 DEBUG Checking readiness of task: 3790 / 0x46620a0
Jul 07 20:56:16-223356 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-223546 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-223736 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-223926 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-224116 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-224304 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-224493 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-224684 util-scheduler-8620 DEBUG Running task: 3790 / 0x46620a0
Jul 07 20:56:16-225088 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:16-225356 util-scheduler-8620 DEBUG Adding task: 3796 / 0x4662248
Jul 07 20:56:16-225604 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-225795 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-225986 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-226176 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-226366 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-226555 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-226744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-226933 util-scheduler-8620 DEBUG Running task: 3796 / 0x4662248
Jul 07 20:56:16-227123 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:16-227319 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:16-227536 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:16-227734 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:16-227932 util-scheduler-8620 DEBUG Adding task: 3797 / 0x46620a0
Jul 07 20:56:16-228117 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:16-228321 util-scheduler-8620 DEBUG Adding task: 3798 / 0x46620a0
Jul 07 20:56:16-228561 util-scheduler-8620 DEBUG Checking readiness of task: 3798 / 0x46620a0
Jul 07 20:56:16-228754 util-scheduler-8620 DEBUG Checking readiness of task: 3797 / 0x46620a0
Jul 07 20:56:16-228946 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:16-229136 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:16-229346 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:16-229537 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:16-229728 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:16-230403 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:16-230617 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:16-230819 util-scheduler-8620 DEBUG Running task: 3797 / 0x46620a0
Jul 07 20:56:16-231007 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:16-231190 util-8620 DEBUG process_notify is running
Jul 07 20:56:16-231367 util-8620 DEBUG client_notify is running
Jul 07 20:56:16-231560 util-scheduler-8620 DEBUG Canceling task: 3794 / 0x59ee8a0
Jul 07 20:56:16-231814 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:16-232038 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:16-232329 cadet-p2p-8620 DEBUG Checking 0x51e6cb0 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:16-232566 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:16-232744 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:16-232937 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:16-233275 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:16-233474 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:16-233655 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:16-233844 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:16-234032 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:16-234210 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:16-234394 util-scheduler-8620 DEBUG Canceling task: 3791 / 0x59e8808
Jul 07 20:56:16-234626 util-scheduler-8620 DEBUG Adding task: 3799 / 0x59e8808
Jul 07 20:56:16-234879 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:16-235049 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:16-235229 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:16-235429 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:16-235639 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:16-235815 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:16-236015 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:16-236245 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:16-236429 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:16-236610 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:16-236802 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:16-237072 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:21-222089 util-scheduler-8620 DEBUG Checking readiness of task: 3798 / 0x46620a0
Jul 07 20:56:21-222469 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-224071 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-224432 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-224629 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-224822 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-225012 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-225232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-225430 util-scheduler-8620 DEBUG Running task: 3793 / 0x52cbfb8
Jul 07 20:56:21-225668 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:21-225929 cadet-tun-8620 DEBUG  kx started 8 m ago
Jul 07 20:56:21-226137 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:21-226337 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:21-226539 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:21-226775 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:21-226955 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:21-227178 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:21-227468 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:21-227664 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:21-227903 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:21-228111 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:21-228428 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:21-228628 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:21-228853 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:21-229036 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:21-229237 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:21-229447 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:21-229665 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:21-229889 util-scheduler-8620 DEBUG Adding task: 3800 / 0x59ee8a0
Jul 07 20:56:21-230070 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:21-230273 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:21-230449 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:21-230623 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:21-230861 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:21-231056 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:21-231233 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:21-231432 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:21-231675 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:21-231872 util-scheduler-8620 DEBUG Adding task: 3801 / 0x52cbfb8
Jul 07 20:56:21-232138 util-scheduler-8620 DEBUG Checking readiness of task: 3798 / 0x46620a0
Jul 07 20:56:21-232331 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-232557 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-232748 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-232937 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-233127 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-233345 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-233534 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-233724 util-scheduler-8620 DEBUG Running task: 3800 / 0x59ee8a0
Jul 07 20:56:21-233932 util-scheduler-8620 DEBUG Adding task: 3802 / 0x59ee8a0
Jul 07 20:56:21-234154 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:21-234357 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:21-234566 util-scheduler-8620 DEBUG Adding task: 3803 / 0x46620a0
Jul 07 20:56:21-234811 util-scheduler-8620 DEBUG Checking readiness of task: 3803 / 0x46620a0
Jul 07 20:56:21-235004 util-scheduler-8620 DEBUG Checking readiness of task: 3798 / 0x46620a0
Jul 07 20:56:21-235195 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-235384 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-235574 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-235764 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-235957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-236146 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-236335 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-236525 util-scheduler-8620 DEBUG Running task: 3803 / 0x46620a0
Jul 07 20:56:21-236710 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:21-236888 util-8620 DEBUG process_notify is running
Jul 07 20:56:21-237060 util-8620 DEBUG client_notify is running
Jul 07 20:56:21-237263 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:21-237460 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:21-237651 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:21-237909 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:21-238157 util-scheduler-8620 DEBUG Checking readiness of task: 3798 / 0x46620a0
Jul 07 20:56:21-238350 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-238540 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-238730 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-238919 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-239109 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-239298 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-239486 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-239676 util-scheduler-8620 DEBUG Running task: 3798 / 0x46620a0
Jul 07 20:56:21-240083 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:21-240313 util-scheduler-8620 DEBUG Adding task: 3804 / 0x4662248
Jul 07 20:56:21-240560 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-240752 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-240943 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-241132 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-241350 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-241539 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-241741 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-241992 util-scheduler-8620 DEBUG Running task: 3804 / 0x4662248
Jul 07 20:56:21-242195 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:21-242398 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:21-242657 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:21-242867 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:21-243077 util-scheduler-8620 DEBUG Adding task: 3805 / 0x46620a0
Jul 07 20:56:21-243266 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:21-243470 util-scheduler-8620 DEBUG Adding task: 3806 / 0x46620a0
Jul 07 20:56:21-243738 util-scheduler-8620 DEBUG Checking readiness of task: 3806 / 0x46620a0
Jul 07 20:56:21-243932 util-scheduler-8620 DEBUG Checking readiness of task: 3805 / 0x46620a0
Jul 07 20:56:21-244124 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:21-244314 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:21-244505 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:21-244694 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:21-244883 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:21-245072 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:21-245330 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:21-245537 util-scheduler-8620 DEBUG Running task: 3805 / 0x46620a0
Jul 07 20:56:21-245724 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:21-245901 util-8620 DEBUG process_notify is running
Jul 07 20:56:21-246070 util-8620 DEBUG client_notify is running
Jul 07 20:56:21-246260 util-scheduler-8620 DEBUG Canceling task: 3802 / 0x59ee8a0
Jul 07 20:56:21-246490 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:21-246707 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:21-246939 cadet-p2p-8620 DEBUG Checking 0x51e8e18 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:21-247173 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:21-247350 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:21-247537 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:21-247818 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:21-248013 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:21-248190 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:21-248377 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:21-248566 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:21-248746 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:21-248930 util-scheduler-8620 DEBUG Canceling task: 3799 / 0x59e8808
Jul 07 20:56:21-249142 util-scheduler-8620 DEBUG Adding task: 3807 / 0x59e8808
Jul 07 20:56:21-249413 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:21-249585 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:21-249767 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:21-249967 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:21-250142 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:21-250315 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:21-250514 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:21-250718 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:21-250901 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:21-251078 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:21-251267 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:21-251515 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:26-237020 util-scheduler-8620 DEBUG Checking readiness of task: 3806 / 0x46620a0
Jul 07 20:56:26-237440 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-238040 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-238485 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-238686 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-238879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-239075 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-239267 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-239462 util-scheduler-8620 DEBUG Running task: 3801 / 0x52cbfb8
Jul 07 20:56:26-239703 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:26-239961 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:26-240170 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:26-240437 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:26-240720 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:26-240958 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:26-241139 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:26-241391 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:26-241683 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:26-241881 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:26-242122 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:26-242331 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:26-242650 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:26-242851 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:26-243077 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:26-243261 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:26-243437 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:26-243645 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:26-243861 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:26-244091 util-scheduler-8620 DEBUG Adding task: 3808 / 0x59ee8a0
Jul 07 20:56:26-244275 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:26-244480 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:26-244656 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:26-244832 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:26-245071 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:26-245288 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:26-245466 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:26-245665 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:26-245909 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:26-246107 util-scheduler-8620 DEBUG Adding task: 3809 / 0x52cbfb8
Jul 07 20:56:26-246373 util-scheduler-8620 DEBUG Checking readiness of task: 3806 / 0x46620a0
Jul 07 20:56:26-246565 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-246755 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-246945 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-247136 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-247326 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-247516 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-247705 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-247897 util-scheduler-8620 DEBUG Running task: 3808 / 0x59ee8a0
Jul 07 20:56:26-248140 util-scheduler-8620 DEBUG Adding task: 3810 / 0x59ee8a0
Jul 07 20:56:26-248363 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:26-248566 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:26-248773 util-scheduler-8620 DEBUG Adding task: 3811 / 0x46620a0
Jul 07 20:56:26-249016 util-scheduler-8620 DEBUG Checking readiness of task: 3811 / 0x46620a0
Jul 07 20:56:26-249230 util-scheduler-8620 DEBUG Checking readiness of task: 3806 / 0x46620a0
Jul 07 20:56:26-249422 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-249611 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-249801 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-249991 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-250196 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-250386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-250576 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-250769 util-scheduler-8620 DEBUG Running task: 3811 / 0x46620a0
Jul 07 20:56:26-250955 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:26-251135 util-8620 DEBUG process_notify is running
Jul 07 20:56:26-251324 util-8620 DEBUG client_notify is running
Jul 07 20:56:26-251505 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:26-251701 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:26-251892 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:26-252150 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:26-252399 util-scheduler-8620 DEBUG Checking readiness of task: 3806 / 0x46620a0
Jul 07 20:56:26-252592 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-252783 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-252974 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-253164 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-253377 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-253567 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-253757 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-253947 util-scheduler-8620 DEBUG Running task: 3806 / 0x46620a0
Jul 07 20:56:26-254357 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:26-254589 util-scheduler-8620 DEBUG Adding task: 3812 / 0x4662248
Jul 07 20:56:26-254837 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-255030 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-255221 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-255412 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-255603 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-255792 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-255981 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-256170 util-scheduler-8620 DEBUG Running task: 3812 / 0x4662248
Jul 07 20:56:26-256361 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:26-256557 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:26-256774 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:26-256971 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:26-257171 util-scheduler-8620 DEBUG Adding task: 3813 / 0x46620a0
Jul 07 20:56:26-257392 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:26-257598 util-scheduler-8620 DEBUG Adding task: 3814 / 0x46620a0
Jul 07 20:56:26-257839 util-scheduler-8620 DEBUG Checking readiness of task: 3814 / 0x46620a0
Jul 07 20:56:26-258031 util-scheduler-8620 DEBUG Checking readiness of task: 3813 / 0x46620a0
Jul 07 20:56:26-258223 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:26-258413 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:26-258602 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:26-258792 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:26-258982 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:26-259170 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:26-259359 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:26-259548 util-scheduler-8620 DEBUG Running task: 3813 / 0x46620a0
Jul 07 20:56:26-259732 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:26-259906 util-8620 DEBUG process_notify is running
Jul 07 20:56:26-260075 util-8620 DEBUG client_notify is running
Jul 07 20:56:26-260260 util-scheduler-8620 DEBUG Canceling task: 3810 / 0x59ee8a0
Jul 07 20:56:26-260483 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:26-260697 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:26-260929 cadet-p2p-8620 DEBUG Checking 0x5217f40 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:26-261161 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:26-261360 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:26-261548 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:26-261830 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:26-262024 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:26-262203 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:26-262390 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:26-262579 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:26-262757 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:26-262940 util-scheduler-8620 DEBUG Canceling task: 3807 / 0x59e8808
Jul 07 20:56:26-263150 util-scheduler-8620 DEBUG Adding task: 3815 / 0x59e8808
Jul 07 20:56:26-263393 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:26-263563 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:26-263743 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:26-263942 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:26-264120 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:26-264295 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:26-264493 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:26-264697 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:26-264880 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:26-265057 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:26-265265 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:26-265513 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:31-251254 util-scheduler-8620 DEBUG Checking readiness of task: 3814 / 0x46620a0
Jul 07 20:56:31-251642 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-252267 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-252470 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-252734 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-252947 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-253173 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-253390 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-253584 util-scheduler-8620 DEBUG Running task: 3809 / 0x52cbfb8
Jul 07 20:56:31-253824 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:31-254081 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:31-254288 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:31-254490 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:31-254691 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:31-254926 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:31-255137 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:31-255362 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:31-255652 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:31-255849 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:31-256088 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:31-256296 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:31-256613 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:31-256815 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:31-257040 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:31-257240 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:31-257431 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:31-257639 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:31-257853 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:31-258079 util-scheduler-8620 DEBUG Adding task: 3816 / 0x59ee8a0
Jul 07 20:56:31-258259 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:31-258463 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:31-258639 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:31-258814 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:31-259052 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:31-259247 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:31-259425 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:31-259624 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:31-259867 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:31-260064 util-scheduler-8620 DEBUG Adding task: 3817 / 0x52cbfb8
Jul 07 20:56:31-260324 util-scheduler-8620 DEBUG Checking readiness of task: 3814 / 0x46620a0
Jul 07 20:56:31-260517 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-260707 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-260897 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-261087 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-261297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-261487 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-261676 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-261865 util-scheduler-8620 DEBUG Running task: 3816 / 0x59ee8a0
Jul 07 20:56:31-262073 util-scheduler-8620 DEBUG Adding task: 3818 / 0x59ee8a0
Jul 07 20:56:31-262294 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:31-262497 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:31-262704 util-scheduler-8620 DEBUG Adding task: 3819 / 0x46620a0
Jul 07 20:56:31-262948 util-scheduler-8620 DEBUG Checking readiness of task: 3819 / 0x46620a0
Jul 07 20:56:31-263141 util-scheduler-8620 DEBUG Checking readiness of task: 3814 / 0x46620a0
Jul 07 20:56:31-263332 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-263522 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-263730 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-263921 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-264111 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-264299 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-264488 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-264680 util-scheduler-8620 DEBUG Running task: 3819 / 0x46620a0
Jul 07 20:56:31-264864 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:31-265043 util-8620 DEBUG process_notify is running
Jul 07 20:56:31-265234 util-8620 DEBUG client_notify is running
Jul 07 20:56:31-265419 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:31-265613 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:31-265804 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:31-266061 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:31-266311 util-scheduler-8620 DEBUG Checking readiness of task: 3814 / 0x46620a0
Jul 07 20:56:31-266503 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-266694 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-266884 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-267073 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-267263 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-267453 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-267641 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-267831 util-scheduler-8620 DEBUG Running task: 3814 / 0x46620a0
Jul 07 20:56:31-268235 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:31-268466 util-scheduler-8620 DEBUG Adding task: 3820 / 0x4662248
Jul 07 20:56:31-268713 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-268905 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-269095 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-269306 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-269496 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-269685 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-269872 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-270061 util-scheduler-8620 DEBUG Running task: 3820 / 0x4662248
Jul 07 20:56:31-270251 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:31-270446 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:31-270663 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:31-270861 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:31-271059 util-scheduler-8620 DEBUG Adding task: 3821 / 0x46620a0
Jul 07 20:56:31-271244 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:31-271448 util-scheduler-8620 DEBUG Adding task: 3822 / 0x46620a0
Jul 07 20:56:31-271689 util-scheduler-8620 DEBUG Checking readiness of task: 3822 / 0x46620a0
Jul 07 20:56:31-271881 util-scheduler-8620 DEBUG Checking readiness of task: 3821 / 0x46620a0
Jul 07 20:56:31-272072 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:31-272262 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:31-272451 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:31-272657 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:31-272848 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:31-273038 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:31-273245 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:31-273438 util-scheduler-8620 DEBUG Running task: 3821 / 0x46620a0
Jul 07 20:56:31-273622 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:31-273797 util-8620 DEBUG process_notify is running
Jul 07 20:56:31-273966 util-8620 DEBUG client_notify is running
Jul 07 20:56:31-274151 util-scheduler-8620 DEBUG Canceling task: 3818 / 0x59ee8a0
Jul 07 20:56:31-274373 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:31-274589 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:31-274819 cadet-p2p-8620 DEBUG Checking 0x60995d8 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:31-275052 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:31-275230 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:31-275420 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:31-275702 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:31-275897 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:31-276075 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:31-276263 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:31-276451 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:31-276630 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:31-276813 util-scheduler-8620 DEBUG Canceling task: 3815 / 0x59e8808
Jul 07 20:56:31-277023 util-scheduler-8620 DEBUG Adding task: 3823 / 0x59e8808
Jul 07 20:56:31-277286 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:31-277458 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:31-277639 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:31-277838 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:31-278012 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:31-278186 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:31-278385 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:31-278588 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:31-278782 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:31-278959 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:31-279148 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:31-279393 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:36-265233 util-scheduler-8620 DEBUG Checking readiness of task: 3822 / 0x46620a0
Jul 07 20:56:36-265620 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-266247 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-266449 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-266702 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-266910 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-267101 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-267291 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-267485 util-scheduler-8620 DEBUG Running task: 3817 / 0x52cbfb8
Jul 07 20:56:36-267725 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:36-267981 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:36-268189 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:36-268389 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:36-268591 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:36-268826 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:36-269030 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:36-269275 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:36-269568 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:36-269764 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:36-270001 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:36-270209 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:36-270525 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:36-270726 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:36-270951 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:36-271134 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:36-271309 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:36-271517 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:36-271731 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:36-271955 util-scheduler-8620 DEBUG Adding task: 3824 / 0x59ee8a0
Jul 07 20:56:36-272135 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:36-272338 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:36-272514 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:36-272688 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:36-272926 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:36-273120 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:36-273320 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:36-273519 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:36-273761 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:36-273959 util-scheduler-8620 DEBUG Adding task: 3825 / 0x52cbfb8
Jul 07 20:56:36-274220 util-scheduler-8620 DEBUG Checking readiness of task: 3822 / 0x46620a0
Jul 07 20:56:36-274412 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-274602 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-274792 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-274982 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-275172 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-275361 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-275550 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-275739 util-scheduler-8620 DEBUG Running task: 3824 / 0x59ee8a0
Jul 07 20:56:36-275947 util-scheduler-8620 DEBUG Adding task: 3826 / 0x59ee8a0
Jul 07 20:56:36-276226 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:36-276498 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:36-276714 util-scheduler-8620 DEBUG Adding task: 3827 / 0x46620a0
Jul 07 20:56:36-276961 util-scheduler-8620 DEBUG Checking readiness of task: 3827 / 0x46620a0
Jul 07 20:56:36-277154 util-scheduler-8620 DEBUG Checking readiness of task: 3822 / 0x46620a0
Jul 07 20:56:36-277366 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-277557 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-277748 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-277938 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-278127 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-278317 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-278506 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-278698 util-scheduler-8620 DEBUG Running task: 3827 / 0x46620a0
Jul 07 20:56:36-278883 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:36-279080 util-8620 DEBUG process_notify is running
Jul 07 20:56:36-279253 util-8620 DEBUG client_notify is running
Jul 07 20:56:36-279432 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:36-279628 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:36-279819 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:36-280071 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:36-280319 util-scheduler-8620 DEBUG Checking readiness of task: 3822 / 0x46620a0
Jul 07 20:56:36-280512 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-280703 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-280894 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-281085 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-281297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-281487 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-281676 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-281866 util-scheduler-8620 DEBUG Running task: 3822 / 0x46620a0
Jul 07 20:56:36-282270 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:36-282500 util-scheduler-8620 DEBUG Adding task: 3828 / 0x4662248
Jul 07 20:56:36-282747 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-282939 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-283129 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-283320 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-283512 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-283703 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-283893 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-284083 util-scheduler-8620 DEBUG Running task: 3828 / 0x4662248
Jul 07 20:56:36-284273 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:36-284468 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:36-284685 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:36-284882 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:36-285080 util-scheduler-8620 DEBUG Adding task: 3829 / 0x46620a0
Jul 07 20:56:36-285285 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:36-285489 util-scheduler-8620 DEBUG Adding task: 3830 / 0x46620a0
Jul 07 20:56:36-285731 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:36-285923 util-scheduler-8620 DEBUG Checking readiness of task: 3829 / 0x46620a0
Jul 07 20:56:36-286115 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:36-286305 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:36-286509 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:36-286704 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:36-286895 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:36-287085 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:36-287274 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:36-287465 util-scheduler-8620 DEBUG Running task: 3829 / 0x46620a0
Jul 07 20:56:36-287649 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:36-287824 util-8620 DEBUG process_notify is running
Jul 07 20:56:36-287993 util-8620 DEBUG client_notify is running
Jul 07 20:56:36-288197 util-scheduler-8620 DEBUG Canceling task: 3826 / 0x59ee8a0
Jul 07 20:56:36-288421 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:36-288638 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:36-288869 cadet-p2p-8620 DEBUG Checking 0x519e3c8 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:36-289103 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:36-289301 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:36-289489 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:36-289772 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:36-289966 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:36-290145 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:36-290332 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:36-290520 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:36-290699 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:36-290882 util-scheduler-8620 DEBUG Canceling task: 3823 / 0x59e8808
Jul 07 20:56:36-291092 util-scheduler-8620 DEBUG Adding task: 3831 / 0x59e8808
Jul 07 20:56:36-291335 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:36-291505 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:36-291687 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:36-291886 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:36-292060 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:36-292234 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:36-292433 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:36-292636 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:36-292819 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:36-292997 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:36-293186 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:36-293450 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:39-042290 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:39-042670 util-scheduler-8620 DEBUG Checking readiness of task: 3197 / 0x465ee60
Jul 07 20:56:39-042871 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:39-043067 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:39-043262 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:39-043456 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:39-043649 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:39-043841 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:39-044040 util-scheduler-8620 DEBUG Running task: 3197 / 0x465ee60
Jul 07 20:56:39-044464 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:56:39-044723 util-scheduler-8620 DEBUG Adding task: 3832 / 0x465f008
Jul 07 20:56:39-045004 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:39-045237 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:39-045434 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:39-045628 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:39-045827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:39-046022 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:39-046214 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:39-046406 util-scheduler-8620 DEBUG Running task: 3832 / 0x465f008
Jul 07 20:56:39-046602 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:56:39-046879 nse-api-8620 DEBUG Received information about peer `Z2YH' from peerinfo database
Jul 07 20:56:39-047071 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:56:39-047285 util-scheduler-8620 DEBUG Adding task: 3833 / 0x465f008
Jul 07 20:56:39-047529 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:39-047725 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:39-047918 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:39-048111 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:39-048303 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:39-048494 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:39-048684 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:39-048876 util-scheduler-8620 DEBUG Running task: 3833 / 0x465f008
Jul 07 20:56:39-049068 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:56:39-049317 nse-api-8620 DEBUG Received information about peer `Z2YH' from peerinfo database
Jul 07 20:56:39-049595 cadet-hll-8620 DEBUG  hello for Z2YH (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:56:39-050182 cadet-p2p-8620 DEBUG set hello for Z2YH
Jul 07 20:56:39-050370 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:56:39-050564 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:39-050780 util-scheduler-8620 DEBUG Adding task: 3834 / 0x465ee60
Jul 07 20:56:41-276349 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-276730 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:41-277538 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-277985 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-278183 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-278375 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-278568 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-278759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-278953 util-scheduler-8620 DEBUG Running task: 3825 / 0x52cbfb8
Jul 07 20:56:41-279193 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:41-279453 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:41-279660 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:41-279861 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:41-280064 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:41-280300 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:41-280482 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:41-280703 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:41-280994 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:41-281221 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:41-281463 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:41-281672 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:41-281990 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:41-282192 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:41-282417 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:41-282600 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:41-282776 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:41-282982 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:41-283199 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:41-283438 util-scheduler-8620 DEBUG Adding task: 3835 / 0x59ee8a0
Jul 07 20:56:41-283618 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:41-283857 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:41-284034 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:41-284209 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:41-284446 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:41-284642 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:41-284819 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:41-285016 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:41-285282 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:41-285482 util-scheduler-8620 DEBUG Adding task: 3836 / 0x52cbfb8
Jul 07 20:56:41-285751 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-285944 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:41-286133 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-286323 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-286511 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-286701 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-286890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-287078 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-287267 util-scheduler-8620 DEBUG Running task: 3835 / 0x59ee8a0
Jul 07 20:56:41-287477 util-scheduler-8620 DEBUG Adding task: 3837 / 0x59ee8a0
Jul 07 20:56:41-287700 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:41-287905 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:41-288113 util-scheduler-8620 DEBUG Adding task: 3838 / 0x46620a0
Jul 07 20:56:41-288358 util-scheduler-8620 DEBUG Checking readiness of task: 3838 / 0x46620a0
Jul 07 20:56:41-288551 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-288741 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:41-288931 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-289120 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-289330 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-289520 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-289708 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-289897 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-290088 util-scheduler-8620 DEBUG Running task: 3838 / 0x46620a0
Jul 07 20:56:41-290272 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:41-290450 util-8620 DEBUG process_notify is running
Jul 07 20:56:41-290622 util-8620 DEBUG client_notify is running
Jul 07 20:56:41-290801 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:41-290996 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:41-291187 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:41-291444 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:41-291770 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-292038 util-scheduler-8620 DEBUG Checking readiness of task: 3830 / 0x46620a0
Jul 07 20:56:41-292233 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-292424 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-292614 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-292803 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-292992 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-293180 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-293411 util-scheduler-8620 DEBUG Running task: 3830 / 0x46620a0
Jul 07 20:56:41-293823 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:41-294053 util-scheduler-8620 DEBUG Adding task: 3839 / 0x4662248
Jul 07 20:56:41-294303 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-294495 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-294685 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-294874 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-295063 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-295252 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-295440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-295629 util-scheduler-8620 DEBUG Running task: 3839 / 0x4662248
Jul 07 20:56:41-295818 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:41-296012 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:41-296229 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:41-296427 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:41-296626 util-scheduler-8620 DEBUG Adding task: 3840 / 0x46620a0
Jul 07 20:56:41-296810 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:41-297014 util-scheduler-8620 DEBUG Adding task: 3841 / 0x46620a0
Jul 07 20:56:41-297273 util-scheduler-8620 DEBUG Checking readiness of task: 3841 / 0x46620a0
Jul 07 20:56:41-297468 util-scheduler-8620 DEBUG Checking readiness of task: 3840 / 0x46620a0
Jul 07 20:56:41-297659 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:41-297848 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:41-298037 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:41-298228 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:41-298418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:41-298605 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:41-298794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:41-298984 util-scheduler-8620 DEBUG Running task: 3840 / 0x46620a0
Jul 07 20:56:41-299168 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:41-299343 util-8620 DEBUG process_notify is running
Jul 07 20:56:41-299511 util-8620 DEBUG client_notify is running
Jul 07 20:56:41-299697 util-scheduler-8620 DEBUG Canceling task: 3837 / 0x59ee8a0
Jul 07 20:56:41-299922 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:41-300137 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:41-300368 cadet-p2p-8620 DEBUG Checking 0x609c158 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:41-300602 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:41-300779 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:41-300966 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:41-301270 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:41-301466 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:41-301645 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:41-301833 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:41-302021 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:41-302198 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:41-302381 util-scheduler-8620 DEBUG Canceling task: 3831 / 0x59e8808
Jul 07 20:56:41-302593 util-scheduler-8620 DEBUG Adding task: 3842 / 0x59e8808
Jul 07 20:56:41-302836 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:41-303022 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:41-303205 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:41-303405 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:41-303580 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:41-303754 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:41-303952 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:41-304156 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:41-304339 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:41-304517 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:41-304716 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:41-304964 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:46-290631 util-scheduler-8620 DEBUG Checking readiness of task: 3841 / 0x46620a0
Jul 07 20:56:46-291031 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-291660 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-291860 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-292121 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-292333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-292524 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-292714 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-292907 util-scheduler-8620 DEBUG Running task: 3836 / 0x52cbfb8
Jul 07 20:56:46-293147 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:46-293428 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:46-293636 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:46-293836 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:46-294039 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:46-294274 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:46-294456 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:46-294678 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:46-294969 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:46-295166 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:46-295404 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:46-295613 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:46-295930 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:46-296132 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:46-296356 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:46-296539 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:46-296715 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:46-296921 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:46-297136 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:46-297382 util-scheduler-8620 DEBUG Adding task: 3843 / 0x59ee8a0
Jul 07 20:56:46-297562 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:46-297766 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:46-297942 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:46-298117 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:46-298355 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:46-298551 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:46-298731 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:46-298930 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:46-299174 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:46-299371 util-scheduler-8620 DEBUG Adding task: 3844 / 0x52cbfb8
Jul 07 20:56:46-299664 util-scheduler-8620 DEBUG Checking readiness of task: 3841 / 0x46620a0
Jul 07 20:56:46-299858 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-300049 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-300239 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-300429 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-300618 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-300807 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-300996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-301184 util-scheduler-8620 DEBUG Running task: 3843 / 0x59ee8a0
Jul 07 20:56:46-301413 util-scheduler-8620 DEBUG Adding task: 3845 / 0x59ee8a0
Jul 07 20:56:46-301635 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:46-301839 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:46-302049 util-scheduler-8620 DEBUG Adding task: 3846 / 0x46620a0
Jul 07 20:56:46-302292 util-scheduler-8620 DEBUG Checking readiness of task: 3846 / 0x46620a0
Jul 07 20:56:46-302486 util-scheduler-8620 DEBUG Checking readiness of task: 3841 / 0x46620a0
Jul 07 20:56:46-302676 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-302865 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-303057 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-303247 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-303436 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-303625 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-303814 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-304006 util-scheduler-8620 DEBUG Running task: 3846 / 0x46620a0
Jul 07 20:56:46-304191 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:46-304369 util-8620 DEBUG process_notify is running
Jul 07 20:56:46-304541 util-8620 DEBUG client_notify is running
Jul 07 20:56:46-304721 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:46-304916 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:46-305108 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:46-305385 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:46-305633 util-scheduler-8620 DEBUG Checking readiness of task: 3841 / 0x46620a0
Jul 07 20:56:46-305826 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-306015 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-306205 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-306394 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-306583 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-306772 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-306960 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-307150 util-scheduler-8620 DEBUG Running task: 3841 / 0x46620a0
Jul 07 20:56:46-307557 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:46-307787 util-scheduler-8620 DEBUG Adding task: 3847 / 0x4662248
Jul 07 20:56:46-308034 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-308226 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-308417 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-308607 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-308817 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-309007 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-309216 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-309408 util-scheduler-8620 DEBUG Running task: 3847 / 0x4662248
Jul 07 20:56:46-309598 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:46-309794 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:46-310010 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:46-310207 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:46-310405 util-scheduler-8620 DEBUG Adding task: 3848 / 0x46620a0
Jul 07 20:56:46-310590 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:46-310795 util-scheduler-8620 DEBUG Adding task: 3849 / 0x46620a0
Jul 07 20:56:46-311036 util-scheduler-8620 DEBUG Checking readiness of task: 3849 / 0x46620a0
Jul 07 20:56:46-311228 util-scheduler-8620 DEBUG Checking readiness of task: 3848 / 0x46620a0
Jul 07 20:56:46-311419 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:46-311609 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:46-311800 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:46-311990 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:46-312193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:46-312383 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:46-312571 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:46-312762 util-scheduler-8620 DEBUG Running task: 3848 / 0x46620a0
Jul 07 20:56:46-312946 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:46-313121 util-8620 DEBUG process_notify is running
Jul 07 20:56:46-313309 util-8620 DEBUG client_notify is running
Jul 07 20:56:46-313495 util-scheduler-8620 DEBUG Canceling task: 3845 / 0x59ee8a0
Jul 07 20:56:46-313718 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:46-313933 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:46-314163 cadet-p2p-8620 DEBUG Checking 0x609f500 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:46-314397 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:46-314574 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:46-314761 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:46-315044 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:46-315238 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:46-315416 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:46-315604 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:46-315793 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:46-315971 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:46-316154 util-scheduler-8620 DEBUG Canceling task: 3842 / 0x59e8808
Jul 07 20:56:46-316362 util-scheduler-8620 DEBUG Adding task: 3850 / 0x59e8808
Jul 07 20:56:46-316605 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:46-316775 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:46-316955 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:46-317176 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:46-317371 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:46-317572 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:46-317787 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:46-317992 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:46-318176 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:46-318354 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:46-318560 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:46-318828 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:51-304517 util-scheduler-8620 DEBUG Checking readiness of task: 3849 / 0x46620a0
Jul 07 20:56:51-304907 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-305557 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-305757 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-306019 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-306234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-306425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-306615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-306808 util-scheduler-8620 DEBUG Running task: 3844 / 0x52cbfb8
Jul 07 20:56:51-307047 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:51-307304 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:51-307512 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:51-307712 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:51-307913 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:51-308151 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:51-308331 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:51-308553 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:51-308844 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:51-309041 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:51-309302 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:51-309512 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:51-309828 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:51-310032 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:51-310257 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:51-310441 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:51-310616 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:51-310822 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:51-311035 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:51-311259 util-scheduler-8620 DEBUG Adding task: 3851 / 0x59ee8a0
Jul 07 20:56:51-311439 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:51-311643 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:51-311818 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:51-311993 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:51-312231 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:51-312426 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:51-312604 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:51-312803 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:51-313046 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:51-313261 util-scheduler-8620 DEBUG Adding task: 3852 / 0x52cbfb8
Jul 07 20:56:51-313522 util-scheduler-8620 DEBUG Checking readiness of task: 3849 / 0x46620a0
Jul 07 20:56:51-313715 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-313905 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-314095 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-314285 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-314475 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-314664 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-314893 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-315084 util-scheduler-8620 DEBUG Running task: 3851 / 0x59ee8a0
Jul 07 20:56:51-315293 util-scheduler-8620 DEBUG Adding task: 3853 / 0x59ee8a0
Jul 07 20:56:51-315515 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:51-315718 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:51-315927 util-scheduler-8620 DEBUG Adding task: 3854 / 0x46620a0
Jul 07 20:56:51-316171 util-scheduler-8620 DEBUG Checking readiness of task: 3854 / 0x46620a0
Jul 07 20:56:51-316364 util-scheduler-8620 DEBUG Checking readiness of task: 3849 / 0x46620a0
Jul 07 20:56:51-316554 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-316745 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-316957 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-317148 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-317359 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-317549 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-317739 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-317931 util-scheduler-8620 DEBUG Running task: 3854 / 0x46620a0
Jul 07 20:56:51-318115 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:51-318293 util-8620 DEBUG process_notify is running
Jul 07 20:56:51-318466 util-8620 DEBUG client_notify is running
Jul 07 20:56:51-318646 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:51-318841 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:51-319032 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:51-319290 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:51-319552 util-scheduler-8620 DEBUG Checking readiness of task: 3849 / 0x46620a0
Jul 07 20:56:51-319744 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-319941 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-320131 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-320321 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-320511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-320700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-320962 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-321254 util-scheduler-8620 DEBUG Running task: 3849 / 0x46620a0
Jul 07 20:56:51-321664 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:51-321895 util-scheduler-8620 DEBUG Adding task: 3855 / 0x4662248
Jul 07 20:56:51-322144 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-322335 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-322525 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-322715 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-322904 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-323092 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-323280 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-323469 util-scheduler-8620 DEBUG Running task: 3855 / 0x4662248
Jul 07 20:56:51-323659 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:51-323855 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:51-324072 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:51-324286 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:51-324485 util-scheduler-8620 DEBUG Adding task: 3856 / 0x46620a0
Jul 07 20:56:51-324670 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:51-324874 util-scheduler-8620 DEBUG Adding task: 3857 / 0x46620a0
Jul 07 20:56:51-325114 util-scheduler-8620 DEBUG Checking readiness of task: 3857 / 0x46620a0
Jul 07 20:56:51-325328 util-scheduler-8620 DEBUG Checking readiness of task: 3856 / 0x46620a0
Jul 07 20:56:51-325520 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:51-325710 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:51-325900 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:51-326090 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:51-326280 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:51-326469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:51-326657 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:51-326847 util-scheduler-8620 DEBUG Running task: 3856 / 0x46620a0
Jul 07 20:56:51-327031 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:51-327206 util-8620 DEBUG process_notify is running
Jul 07 20:56:51-327374 util-8620 DEBUG client_notify is running
Jul 07 20:56:51-327559 util-scheduler-8620 DEBUG Canceling task: 3853 / 0x59ee8a0
Jul 07 20:56:51-327781 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:51-327998 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:51-328230 cadet-p2p-8620 DEBUG Checking 0x60a0898 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:51-328463 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:51-328641 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:51-328828 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:51-329109 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:51-329325 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:51-329504 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:51-329691 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:51-329882 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:51-330061 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:51-330243 util-scheduler-8620 DEBUG Canceling task: 3850 / 0x59e8808
Jul 07 20:56:51-330454 util-scheduler-8620 DEBUG Adding task: 3858 / 0x59e8808
Jul 07 20:56:51-330696 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:51-330866 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:51-331046 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:51-331244 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:51-331418 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:51-331591 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:51-331789 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:51-331994 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:51-332177 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:51-332354 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:51-332543 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:51-332780 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:56-314159 util-scheduler-8620 DEBUG Checking readiness of task: 3857 / 0x46620a0
Jul 07 20:56:56-314553 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-315687 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-315890 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-316086 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-316313 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-316505 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-316695 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-316888 util-scheduler-8620 DEBUG Running task: 3852 / 0x52cbfb8
Jul 07 20:56:56-317126 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:56:56-317421 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:56:56-317630 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:56:56-317831 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:56:56-318036 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:56:56-318272 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:56:56-318452 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:56:56-318674 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:56:56-318968 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:56:56-319164 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:56:56-319402 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:56:56-319610 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:56:56-319926 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:56:56-320125 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:56:56-320351 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:56:56-320535 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:56:56-320711 cadet-con-8620 DEBUG  sendable
Jul 07 20:56:56-320918 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:56:56-321132 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:56:56-321386 util-scheduler-8620 DEBUG Adding task: 3859 / 0x59ee8a0
Jul 07 20:56:56-321567 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:56:56-321771 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:56-321949 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:56:56-322124 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:56:56-322362 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:56:56-322557 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:56:56-322734 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:56:56-322932 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:56-323403 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:56:56-323603 util-scheduler-8620 DEBUG Adding task: 3860 / 0x52cbfb8
Jul 07 20:56:56-323864 util-scheduler-8620 DEBUG Checking readiness of task: 3857 / 0x46620a0
Jul 07 20:56:56-324056 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-324246 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-324436 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-324628 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-324818 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-325006 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-325220 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-325413 util-scheduler-8620 DEBUG Running task: 3859 / 0x59ee8a0
Jul 07 20:56:56-325622 util-scheduler-8620 DEBUG Adding task: 3861 / 0x59ee8a0
Jul 07 20:56:56-325845 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:56:56-326048 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:56-326257 util-scheduler-8620 DEBUG Adding task: 3862 / 0x46620a0
Jul 07 20:56:56-326501 util-scheduler-8620 DEBUG Checking readiness of task: 3862 / 0x46620a0
Jul 07 20:56:56-326695 util-scheduler-8620 DEBUG Checking readiness of task: 3857 / 0x46620a0
Jul 07 20:56:56-326905 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-327096 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-327286 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-327476 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-327672 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-327862 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-328050 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-328241 util-scheduler-8620 DEBUG Running task: 3862 / 0x46620a0
Jul 07 20:56:56-328427 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:56-328605 util-8620 DEBUG process_notify is running
Jul 07 20:56:56-328778 util-8620 DEBUG client_notify is running
Jul 07 20:56:56-328956 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:56:56-329152 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:56-329371 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:56:56-329627 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:56-329877 util-scheduler-8620 DEBUG Checking readiness of task: 3857 / 0x46620a0
Jul 07 20:56:56-330070 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-330260 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-330450 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-330640 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-330829 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-331021 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-331209 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-331399 util-scheduler-8620 DEBUG Running task: 3857 / 0x46620a0
Jul 07 20:56:56-331806 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:56:56-332040 util-scheduler-8620 DEBUG Adding task: 3863 / 0x4662248
Jul 07 20:56:56-332287 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-332478 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-332667 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-332856 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-333046 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-333262 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-333452 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-333641 util-scheduler-8620 DEBUG Running task: 3863 / 0x4662248
Jul 07 20:56:56-333832 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:56:56-334028 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:56:56-334245 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:56:56-334442 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:56:56-334640 util-scheduler-8620 DEBUG Adding task: 3864 / 0x46620a0
Jul 07 20:56:56-334824 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:56-335027 util-scheduler-8620 DEBUG Adding task: 3865 / 0x46620a0
Jul 07 20:56:56-335267 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:56:56-335459 util-scheduler-8620 DEBUG Checking readiness of task: 3864 / 0x46620a0
Jul 07 20:56:56-335651 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:56-335856 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:56-336047 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:56-336238 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:56-336427 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:56-336616 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:56-336804 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:56-336994 util-scheduler-8620 DEBUG Running task: 3864 / 0x46620a0
Jul 07 20:56:56-337177 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:56:56-337379 util-8620 DEBUG process_notify is running
Jul 07 20:56:56-337549 util-8620 DEBUG client_notify is running
Jul 07 20:56:56-337734 util-scheduler-8620 DEBUG Canceling task: 3861 / 0x59ee8a0
Jul 07 20:56:56-337958 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:56:56-338175 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:56:56-338406 cadet-p2p-8620 DEBUG Checking 0x51a4c08 towards 2FDYFV0X (->V8XX)
Jul 07 20:56:56-338638 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:56:56-338816 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:56:56-339002 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:56:56-339283 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:56:56-339478 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:56:56-339657 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:56:56-339845 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:56:56-340032 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:56:56-340209 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:56:56-340391 util-scheduler-8620 DEBUG Canceling task: 3858 / 0x59e8808
Jul 07 20:56:56-340601 util-scheduler-8620 DEBUG Adding task: 3866 / 0x59e8808
Jul 07 20:56:56-340843 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:56:56-341013 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:56:56-341218 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:56:56-341420 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:56:56-341595 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:56:56-341769 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:56:56-341970 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:56:56-342175 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:56:56-342357 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:56:56-342535 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:56:56-342722 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:56:56-342969 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:56:57-332644 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:56:57-332941 util-scheduler-8620 DEBUG Checking readiness of task: 3834 / 0x465ee60
Jul 07 20:56:57-333140 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:57-333363 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:57-333557 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:57-333749 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:57-333941 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:57-334144 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:57-334340 util-scheduler-8620 DEBUG Running task: 3834 / 0x465ee60
Jul 07 20:56:57-334757 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:56:57-335002 util-scheduler-8620 DEBUG Adding task: 3867 / 0x465f008
Jul 07 20:56:57-335300 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:56:57-335497 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:57-335688 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:57-335880 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:57-336070 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:57-336261 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:57-336450 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:57-336640 util-scheduler-8620 DEBUG Running task: 3867 / 0x465f008
Jul 07 20:56:57-336831 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:56:57-337064 nse-api-8620 DEBUG Received information about peer `Z0PW' from peerinfo database
Jul 07 20:56:57-337279 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:56:57-337493 util-scheduler-8620 DEBUG Adding task: 3868 / 0x465f008
Jul 07 20:56:57-337728 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:56:57-337920 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:56:57-338111 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:56:57-338301 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:56:57-338492 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:56:57-338681 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:56:57-338870 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:56:57-339059 util-scheduler-8620 DEBUG Running task: 3868 / 0x465f008
Jul 07 20:56:57-339249 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:56:57-339465 nse-api-8620 DEBUG Received information about peer `Z0PW' from peerinfo database
Jul 07 20:56:57-339734 cadet-hll-8620 DEBUG  hello for Z0PW (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:56:57-339997 cadet-p2p-8620 DEBUG set hello for Z0PW
Jul 07 20:56:57-340173 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:56:57-340360 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:56:57-340565 util-scheduler-8620 DEBUG Adding task: 3869 / 0x465ee60
Jul 07 20:57:01-327752 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-328127 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:57:01-328807 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-329294 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-329496 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-329691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-329883 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-330074 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-330269 util-scheduler-8620 DEBUG Running task: 3860 / 0x52cbfb8
Jul 07 20:57:01-330527 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:01-330786 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:57:01-330994 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:01-331195 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:01-331414 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:01-331650 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:01-331831 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:01-332053 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:01-332344 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:01-332560 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:01-332799 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:01-333007 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:01-333382 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:01-333603 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:01-333829 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:01-334012 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:01-334189 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:01-334396 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:01-334629 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:01-334856 util-scheduler-8620 DEBUG Adding task: 3870 / 0x59ee8a0
Jul 07 20:57:01-335037 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:01-335241 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:01-335418 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:01-335593 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:01-335849 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:01-336047 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:01-336225 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:01-336425 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:01-336668 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:01-336884 util-scheduler-8620 DEBUG Adding task: 3871 / 0x52cbfb8
Jul 07 20:57:01-337151 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-337365 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:57:01-337556 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-337747 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-337953 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-338144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-338333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-338521 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-338711 util-scheduler-8620 DEBUG Running task: 3870 / 0x59ee8a0
Jul 07 20:57:01-338936 util-scheduler-8620 DEBUG Adding task: 3872 / 0x59ee8a0
Jul 07 20:57:01-339161 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:01-339365 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:01-339573 util-scheduler-8620 DEBUG Adding task: 3873 / 0x46620a0
Jul 07 20:57:01-339818 util-scheduler-8620 DEBUG Checking readiness of task: 3873 / 0x46620a0
Jul 07 20:57:01-340029 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-340219 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:57:01-340410 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-340600 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-340791 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-340998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-341206 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-341398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-341591 util-scheduler-8620 DEBUG Running task: 3873 / 0x46620a0
Jul 07 20:57:01-341776 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:01-341956 util-8620 DEBUG process_notify is running
Jul 07 20:57:01-342146 util-8620 DEBUG client_notify is running
Jul 07 20:57:01-342326 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:01-342523 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:01-342715 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:01-342992 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:01-343261 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-343454 util-scheduler-8620 DEBUG Checking readiness of task: 3865 / 0x46620a0
Jul 07 20:57:01-343659 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-343850 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-344041 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-344247 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-344438 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-344626 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-344817 util-scheduler-8620 DEBUG Running task: 3865 / 0x46620a0
Jul 07 20:57:01-345261 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:01-345495 util-scheduler-8620 DEBUG Adding task: 3874 / 0x4662248
Jul 07 20:57:01-345745 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-345940 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-346131 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-346337 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-346528 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-346718 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-346907 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-347096 util-scheduler-8620 DEBUG Running task: 3874 / 0x4662248
Jul 07 20:57:01-347287 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:01-347499 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:01-347717 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:01-347914 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:01-348113 util-scheduler-8620 DEBUG Adding task: 3875 / 0x46620a0
Jul 07 20:57:01-348298 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:01-348519 util-scheduler-8620 DEBUG Adding task: 3876 / 0x46620a0
Jul 07 20:57:01-348761 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:01-348954 util-scheduler-8620 DEBUG Checking readiness of task: 3875 / 0x46620a0
Jul 07 20:57:01-349145 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:01-349357 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:01-349564 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:01-349755 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:01-349946 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:01-350135 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:01-350323 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:01-350514 util-scheduler-8620 DEBUG Running task: 3875 / 0x46620a0
Jul 07 20:57:01-350715 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:01-350891 util-8620 DEBUG process_notify is running
Jul 07 20:57:01-351061 util-8620 DEBUG client_notify is running
Jul 07 20:57:01-351247 util-scheduler-8620 DEBUG Canceling task: 3872 / 0x59ee8a0
Jul 07 20:57:01-351470 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:01-351707 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:01-351941 cadet-p2p-8620 DEBUG Checking 0x60a4d50 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:01-352175 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:01-352354 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:01-352557 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:01-352865 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:01-353061 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:01-353260 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:01-353450 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:01-353639 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:01-353842 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:01-354027 util-scheduler-8620 DEBUG Canceling task: 3866 / 0x59e8808
Jul 07 20:57:01-354238 util-scheduler-8620 DEBUG Adding task: 3877 / 0x59e8808
Jul 07 20:57:01-354481 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:01-354652 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:01-354834 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:01-355053 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:01-355227 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:01-355400 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:01-355600 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:01-355804 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:01-356007 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:01-356188 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:01-356377 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:01-356623 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:02-671359 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-671705 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-671902 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-672096 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-672288 util-scheduler-8620 DEBUG Checking readiness of task: 2893 / 0x4665be0
Jul 07 20:57:02-672483 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-672675 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-672865 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-673079 util-scheduler-8620 DEBUG Running task: 2893 / 0x4665be0
Jul 07 20:57:02-673529 util-8620 DEBUG receive_ready read 747/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665be0)!
Jul 07 20:57:02-673787 util-scheduler-8620 DEBUG Adding task: 3878 / 0x4665d88
Jul 07 20:57:02-674061 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-674255 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-674446 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-674636 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-674827 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-675016 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-675206 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-675396 util-scheduler-8620 DEBUG Running task: 3878 / 0x4665d88
Jul 07 20:57:02-675587 util-8620 DEBUG Received message of type 145 and size 747 from dht service.
Jul 07 20:57:02-675788 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:02-676002 util-scheduler-8620 DEBUG Adding task: 3879 / 0x4665be0
Jul 07 20:57:02-676212 dht-api-8620 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46642c0
Jul 07 20:57:02-676425 dht-api-8620 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 20:57:02-678059 cadet-dht-8620 DEBUG    GET has 1 hops.
Jul 07 20:57:02-678293 cadet-dht-8620 DEBUG    Adding from GET: KNAS.
Jul 07 20:57:02-678513 cadet-dht-8620 DEBUG    PUT has 4 hops.
Jul 07 20:57:02-678721 cadet-dht-8620 DEBUG    Adding from PUT: STRN.
Jul 07 20:57:02-678943 cadet-dht-8620 DEBUG    Adding from PUT: VYGR.
Jul 07 20:57:02-679961 cadet-dht-8620 DEBUG    Adding from PUT: GN10.
Jul 07 20:57:02-680181 cadet-dht-8620 DEBUG    Adding from PUT: V8XX.
Jul 07 20:57:02-680390 cadet-dht-8620 DEBUG    (first of GET: KNAS)
Jul 07 20:57:02-680591 cadet-dht-8620 DEBUG    (first of PUT: V8XX)
Jul 07 20:57:02-680767 cadet-dht-8620 DEBUG    In total: 2 hops
Jul 07 20:57:02-680972 cadet-dht-8620 DEBUG        1: GN10
Jul 07 20:57:02-681176 cadet-dht-8620 DEBUG        4: V8XX
Jul 07 20:57:02-681507 cadet-dht-8620 INFO Got path from DHT:  GN10 V8XX
Jul 07 20:57:02-681728 cadet-dht-8620 DEBUG Got HELLO for V8XX
Jul 07 20:57:02-681960 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:57:02-682140 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:57:02-682379 cadet-p2p-8620 DEBUG set hello for V8XX
Jul 07 20:57:02-682896 cadet-p2p-8620 DEBUG  merge into 0x51a9ba0 (491 bytes)
Jul 07 20:57:02-683163 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:57:02-683358 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:57:02-683577 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:57:02-683783 util-scheduler-8620 DEBUG Adding task: 3880 / 0x46624e8
Jul 07 20:57:02-684041 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:02-684235 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-684425 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-684615 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-684805 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-684995 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-685183 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-685393 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-685583 util-scheduler-8620 DEBUG Running task: 3880 / 0x46624e8
Jul 07 20:57:02-685766 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:57:02-685963 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:57:02-686169 util-scheduler-8620 DEBUG Adding task: 3881 / 0x4663d68
Jul 07 20:57:02-686414 util-scheduler-8620 DEBUG Checking readiness of task: 3881 / 0x4663d68
Jul 07 20:57:02-686606 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:02-686797 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-686987 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-687176 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-687366 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-687556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-687745 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-687934 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-688125 util-scheduler-8620 DEBUG Running task: 3881 / 0x4663d68
Jul 07 20:57:02-688311 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:57:02-688491 util-8620 DEBUG process_notify is running
Jul 07 20:57:02-688665 util-8620 DEBUG client_notify is running
Jul 07 20:57:02-688842 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:57:02-689052 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:57:02-689283 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:57:02-689481 util-scheduler-8620 DEBUG Adding task: 3882 / 0x46624e8
Jul 07 20:57:02-689680 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:57:02-689881 util-scheduler-8620 DEBUG Canceling task: 3882 / 0x46624e8
Jul 07 20:57:02-690119 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:57:02-690316 util-scheduler-8620 DEBUG Adding task: 3883 / 0x46624e8
Jul 07 20:57:02-690499 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:57:02-690695 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:57:02-690960 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:57:02-691210 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:02-691401 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-691590 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-691780 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-691970 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-692160 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-692348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-692537 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-692727 util-scheduler-8620 DEBUG Running task: 3883 / 0x46624e8
Jul 07 20:57:02-692907 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:57:02-693096 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:57:02-693315 util-scheduler-8620 DEBUG Adding task: 3884 / 0x4663d68
Jul 07 20:57:02-693554 util-scheduler-8620 DEBUG Checking readiness of task: 3884 / 0x4663d68
Jul 07 20:57:02-693747 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:02-693938 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:02-694127 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:02-694317 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:02-694507 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:02-694697 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:02-694886 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:02-695074 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:02-695291 util-scheduler-8620 DEBUG Running task: 3884 / 0x4663d68
Jul 07 20:57:02-695476 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:57:02-695651 util-8620 DEBUG process_notify is running
Jul 07 20:57:02-695820 util-8620 DEBUG client_notify is running
Jul 07 20:57:02-696025 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:57:02-696252 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:57:02-696455 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:57:02-696656 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:57:02-696905 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:57:06-338563 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-338944 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:06-339962 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-340173 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-340425 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-340640 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-340832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-341025 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-341242 util-scheduler-8620 DEBUG Running task: 3871 / 0x52cbfb8
Jul 07 20:57:06-341507 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:06-341767 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:57:06-341974 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:06-342173 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:06-342374 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:06-342611 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:06-342791 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:06-343012 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:06-343304 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:06-343501 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:06-343739 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:06-343947 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:06-344263 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:06-344467 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:06-344691 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:06-344874 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:06-345051 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:06-345277 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:06-345508 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:06-345734 util-scheduler-8620 DEBUG Adding task: 3885 / 0x59ee8a0
Jul 07 20:57:06-345915 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:06-346119 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:06-346295 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:06-346470 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:06-346709 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:06-346903 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:06-347082 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:06-347280 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:06-347524 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:06-347721 util-scheduler-8620 DEBUG Adding task: 3886 / 0x52cbfb8
Jul 07 20:57:06-347979 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-348170 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:06-348361 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-348552 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-348742 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-348932 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-349122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-349332 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-349522 util-scheduler-8620 DEBUG Running task: 3885 / 0x59ee8a0
Jul 07 20:57:06-349730 util-scheduler-8620 DEBUG Adding task: 3887 / 0x59ee8a0
Jul 07 20:57:06-349951 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:06-350154 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:06-350364 util-scheduler-8620 DEBUG Adding task: 3888 / 0x46620a0
Jul 07 20:57:06-350609 util-scheduler-8620 DEBUG Checking readiness of task: 3888 / 0x46620a0
Jul 07 20:57:06-350804 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-350995 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:06-351185 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-351376 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-351565 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-351774 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-351965 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-352154 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-352348 util-scheduler-8620 DEBUG Running task: 3888 / 0x46620a0
Jul 07 20:57:06-352534 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:06-352713 util-8620 DEBUG process_notify is running
Jul 07 20:57:06-352885 util-8620 DEBUG client_notify is running
Jul 07 20:57:06-353065 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:06-353280 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:06-353472 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:06-353728 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:06-353976 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-354169 util-scheduler-8620 DEBUG Checking readiness of task: 3876 / 0x46620a0
Jul 07 20:57:06-354364 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-354554 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-354744 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-354935 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-355125 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-355314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-355504 util-scheduler-8620 DEBUG Running task: 3876 / 0x46620a0
Jul 07 20:57:06-355909 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:06-356141 util-scheduler-8620 DEBUG Adding task: 3889 / 0x4662248
Jul 07 20:57:06-356389 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-356581 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-356772 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-356961 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-357153 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-357363 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-357553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-357743 util-scheduler-8620 DEBUG Running task: 3889 / 0x4662248
Jul 07 20:57:06-357933 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:06-358130 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:06-358346 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:06-358543 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:06-358741 util-scheduler-8620 DEBUG Adding task: 3890 / 0x46620a0
Jul 07 20:57:06-358926 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:06-359131 util-scheduler-8620 DEBUG Adding task: 3891 / 0x46620a0
Jul 07 20:57:06-359371 util-scheduler-8620 DEBUG Checking readiness of task: 3891 / 0x46620a0
Jul 07 20:57:06-359563 util-scheduler-8620 DEBUG Checking readiness of task: 3890 / 0x46620a0
Jul 07 20:57:06-359754 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:06-359943 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:06-360132 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:06-360322 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:06-360513 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:06-360702 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:06-360907 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:06-361099 util-scheduler-8620 DEBUG Running task: 3890 / 0x46620a0
Jul 07 20:57:06-361303 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:06-361479 util-8620 DEBUG process_notify is running
Jul 07 20:57:06-361649 util-8620 DEBUG client_notify is running
Jul 07 20:57:06-361835 util-scheduler-8620 DEBUG Canceling task: 3887 / 0x59ee8a0
Jul 07 20:57:06-362059 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:06-362275 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:06-362506 cadet-p2p-8620 DEBUG Checking 0x51ab760 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:06-362740 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:06-362918 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:06-363106 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:06-363389 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:06-363583 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:06-363763 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:06-363952 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:06-364171 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:06-364353 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:06-364537 util-scheduler-8620 DEBUG Canceling task: 3877 / 0x59e8808
Jul 07 20:57:06-364747 util-scheduler-8620 DEBUG Adding task: 3892 / 0x59e8808
Jul 07 20:57:06-364990 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:06-365163 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:06-365367 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:06-365567 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:06-365742 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:06-365915 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:06-366114 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:06-366319 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:06-366502 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:06-366680 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:06-366881 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:06-367125 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:11-352865 util-scheduler-8620 DEBUG Checking readiness of task: 3891 / 0x46620a0
Jul 07 20:57:11-353273 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-353993 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-354200 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-354396 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-354589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-354780 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-354969 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-355163 util-scheduler-8620 DEBUG Running task: 3886 / 0x52cbfb8
Jul 07 20:57:11-355401 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:11-355661 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:57:11-355867 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:11-356070 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:11-356272 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:11-356507 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:11-356688 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:11-356909 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:11-357225 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:11-357450 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:11-357691 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:11-357899 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:11-358216 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:11-358418 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:11-358644 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:11-358826 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:11-359002 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:11-359209 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:11-359423 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:11-359648 util-scheduler-8620 DEBUG Adding task: 3893 / 0x59ee8a0
Jul 07 20:57:11-359827 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:11-360031 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:11-360208 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:11-360382 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:11-360619 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:11-360814 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:11-360991 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:11-361211 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:11-361457 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:11-361655 util-scheduler-8620 DEBUG Adding task: 3894 / 0x52cbfb8
Jul 07 20:57:11-361912 util-scheduler-8620 DEBUG Checking readiness of task: 3891 / 0x46620a0
Jul 07 20:57:11-362104 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-362294 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-362483 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-362672 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-362863 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-363052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-363240 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-363429 util-scheduler-8620 DEBUG Running task: 3893 / 0x59ee8a0
Jul 07 20:57:11-363637 util-scheduler-8620 DEBUG Adding task: 3895 / 0x59ee8a0
Jul 07 20:57:11-363859 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:11-364063 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:11-364271 util-scheduler-8620 DEBUG Adding task: 3896 / 0x46620a0
Jul 07 20:57:11-364516 util-scheduler-8620 DEBUG Checking readiness of task: 3896 / 0x46620a0
Jul 07 20:57:11-364710 util-scheduler-8620 DEBUG Checking readiness of task: 3891 / 0x46620a0
Jul 07 20:57:11-364901 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-365091 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-365304 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-365495 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-365689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-365878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-366067 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-366259 util-scheduler-8620 DEBUG Running task: 3896 / 0x46620a0
Jul 07 20:57:11-366444 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:11-366622 util-8620 DEBUG process_notify is running
Jul 07 20:57:11-366795 util-8620 DEBUG client_notify is running
Jul 07 20:57:11-366974 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:11-367184 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:11-367376 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:11-367631 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:11-367880 util-scheduler-8620 DEBUG Checking readiness of task: 3891 / 0x46620a0
Jul 07 20:57:11-368072 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-368263 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-368454 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-368643 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-368832 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-369021 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-369231 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-369424 util-scheduler-8620 DEBUG Running task: 3891 / 0x46620a0
Jul 07 20:57:11-369828 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:11-370059 util-scheduler-8620 DEBUG Adding task: 3897 / 0x4662248
Jul 07 20:57:11-370306 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-370498 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-370748 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-371007 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-371202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-371393 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-371581 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-371770 util-scheduler-8620 DEBUG Running task: 3897 / 0x4662248
Jul 07 20:57:11-371960 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:11-372156 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:11-372374 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:11-372571 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:11-372770 util-scheduler-8620 DEBUG Adding task: 3898 / 0x46620a0
Jul 07 20:57:11-372954 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:11-373157 util-scheduler-8620 DEBUG Adding task: 3899 / 0x46620a0
Jul 07 20:57:11-373423 util-scheduler-8620 DEBUG Checking readiness of task: 3899 / 0x46620a0
Jul 07 20:57:11-373616 util-scheduler-8620 DEBUG Checking readiness of task: 3898 / 0x46620a0
Jul 07 20:57:11-373807 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:11-373997 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:11-374186 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:11-374388 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:11-374578 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:11-374767 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:11-374956 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:11-375147 util-scheduler-8620 DEBUG Running task: 3898 / 0x46620a0
Jul 07 20:57:11-375331 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:11-375506 util-8620 DEBUG process_notify is running
Jul 07 20:57:11-375678 util-8620 DEBUG client_notify is running
Jul 07 20:57:11-375863 util-scheduler-8620 DEBUG Canceling task: 3895 / 0x59ee8a0
Jul 07 20:57:11-376085 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:11-376302 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:11-376551 cadet-p2p-8620 DEBUG Checking 0x5286458 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:11-376785 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:11-376962 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:11-377149 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:11-377453 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:11-377648 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:11-377828 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:11-378015 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:11-378202 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:11-378380 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:11-378564 util-scheduler-8620 DEBUG Canceling task: 3892 / 0x59e8808
Jul 07 20:57:11-378776 util-scheduler-8620 DEBUG Adding task: 3900 / 0x59e8808
Jul 07 20:57:11-379019 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:11-379189 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:11-379369 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:11-379568 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:11-379742 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:11-379916 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:11-380112 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:11-380317 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:11-380500 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:11-380677 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:11-380866 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:11-381112 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:16-366798 util-scheduler-8620 DEBUG Checking readiness of task: 3899 / 0x46620a0
Jul 07 20:57:16-367180 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-367942 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-368383 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-368584 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-368796 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-368988 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-369178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-369397 util-scheduler-8620 DEBUG Running task: 3894 / 0x52cbfb8
Jul 07 20:57:16-369636 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:16-369915 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:57:16-370123 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:16-370341 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:16-370543 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:16-370779 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:16-370976 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:16-371199 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:16-371492 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:16-371690 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:16-371928 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:16-372155 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:16-372475 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:16-372676 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:16-372901 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:16-373101 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:16-373340 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:16-373550 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:16-373764 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:16-373991 util-scheduler-8620 DEBUG Adding task: 3901 / 0x59ee8a0
Jul 07 20:57:16-374193 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:16-374397 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:16-374575 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:16-374751 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:16-374989 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:16-375209 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:16-375388 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:16-375587 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:16-375832 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:16-376029 util-scheduler-8620 DEBUG Adding task: 3902 / 0x52cbfb8
Jul 07 20:57:16-376311 util-scheduler-8620 DEBUG Checking readiness of task: 3899 / 0x46620a0
Jul 07 20:57:16-376506 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-376697 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-376887 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-377078 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-377289 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-377496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-377685 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-377874 util-scheduler-8620 DEBUG Running task: 3901 / 0x59ee8a0
Jul 07 20:57:16-378082 util-scheduler-8620 DEBUG Adding task: 3903 / 0x59ee8a0
Jul 07 20:57:16-378305 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:16-378526 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:16-378735 util-scheduler-8620 DEBUG Adding task: 3904 / 0x46620a0
Jul 07 20:57:16-378981 util-scheduler-8620 DEBUG Checking readiness of task: 3904 / 0x46620a0
Jul 07 20:57:16-379195 util-scheduler-8620 DEBUG Checking readiness of task: 3899 / 0x46620a0
Jul 07 20:57:16-379386 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-379593 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-379805 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-379997 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-380189 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-380378 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-380582 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-380775 util-scheduler-8620 DEBUG Running task: 3904 / 0x46620a0
Jul 07 20:57:16-380960 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:16-381139 util-8620 DEBUG process_notify is running
Jul 07 20:57:16-381333 util-8620 DEBUG client_notify is running
Jul 07 20:57:16-381514 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:16-381726 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:16-381919 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:16-382190 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:16-382441 util-scheduler-8620 DEBUG Checking readiness of task: 3899 / 0x46620a0
Jul 07 20:57:16-382634 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-382825 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-383014 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-383238 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-383428 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-383617 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-383823 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-384013 util-scheduler-8620 DEBUG Running task: 3899 / 0x46620a0
Jul 07 20:57:16-384420 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:16-384650 util-scheduler-8620 DEBUG Adding task: 3905 / 0x4662248
Jul 07 20:57:16-384914 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-385106 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-385316 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-385506 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-385695 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-385909 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-386099 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-386287 util-scheduler-8620 DEBUG Running task: 3905 / 0x4662248
Jul 07 20:57:16-386477 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:16-386672 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:16-386890 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:16-387107 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:16-387306 util-scheduler-8620 DEBUG Adding task: 3906 / 0x46620a0
Jul 07 20:57:16-387491 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:16-387696 util-scheduler-8620 DEBUG Adding task: 3907 / 0x46620a0
Jul 07 20:57:16-387936 util-scheduler-8620 DEBUG Checking readiness of task: 3907 / 0x46620a0
Jul 07 20:57:16-388145 util-scheduler-8620 DEBUG Checking readiness of task: 3906 / 0x46620a0
Jul 07 20:57:16-388336 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:16-388526 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:16-388716 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:16-388905 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:16-389110 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:16-389320 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:16-389511 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:16-389701 util-scheduler-8620 DEBUG Running task: 3906 / 0x46620a0
Jul 07 20:57:16-389887 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:16-390063 util-8620 DEBUG process_notify is running
Jul 07 20:57:16-390249 util-8620 DEBUG client_notify is running
Jul 07 20:57:16-390435 util-scheduler-8620 DEBUG Canceling task: 3903 / 0x59ee8a0
Jul 07 20:57:16-390659 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:16-390875 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:16-391106 cadet-p2p-8620 DEBUG Checking 0x609fb08 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:16-391356 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:16-391535 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:16-391723 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:16-392007 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:16-392201 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:16-392396 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:16-392583 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:16-392788 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:16-392967 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:16-393152 util-scheduler-8620 DEBUG Canceling task: 3900 / 0x59e8808
Jul 07 20:57:16-393406 util-scheduler-8620 DEBUG Adding task: 3908 / 0x59e8808
Jul 07 20:57:16-393652 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:16-393822 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:16-394004 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:16-394203 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:16-394394 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:16-394570 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:16-394768 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:16-394974 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:16-395157 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:16-395334 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:16-395538 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:16-395786 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:21-381171 util-scheduler-8620 DEBUG Checking readiness of task: 3907 / 0x46620a0
Jul 07 20:57:21-381584 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-382256 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-382457 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-382718 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-382931 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-383121 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-383311 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-383504 util-scheduler-8620 DEBUG Running task: 3902 / 0x52cbfb8
Jul 07 20:57:21-383743 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:21-384001 cadet-tun-8620 DEBUG  kx started 9 m ago
Jul 07 20:57:21-384207 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:21-384406 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:21-384608 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:21-384843 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:21-385024 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:21-385267 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:21-385559 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:21-385756 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:21-385993 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:21-386201 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:21-386521 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:21-386722 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:21-386947 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:21-387130 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:21-387305 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:21-387512 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:21-387726 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:21-387950 util-scheduler-8620 DEBUG Adding task: 3909 / 0x59ee8a0
Jul 07 20:57:21-388130 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:21-388333 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:21-388509 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:21-388683 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:21-388920 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:21-389151 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:21-389350 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:21-389562 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:21-389807 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:21-390006 util-scheduler-8620 DEBUG Adding task: 3910 / 0x52cbfb8
Jul 07 20:57:21-390265 util-scheduler-8620 DEBUG Checking readiness of task: 3907 / 0x46620a0
Jul 07 20:57:21-390457 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-390647 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-390837 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-391028 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-391218 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-391405 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-391594 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-391783 util-scheduler-8620 DEBUG Running task: 3909 / 0x59ee8a0
Jul 07 20:57:21-391990 util-scheduler-8620 DEBUG Adding task: 3911 / 0x59ee8a0
Jul 07 20:57:21-392210 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:21-392413 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:21-392619 util-scheduler-8620 DEBUG Adding task: 3912 / 0x46620a0
Jul 07 20:57:21-392864 util-scheduler-8620 DEBUG Checking readiness of task: 3912 / 0x46620a0
Jul 07 20:57:21-393058 util-scheduler-8620 DEBUG Checking readiness of task: 3907 / 0x46620a0
Jul 07 20:57:21-393267 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-393458 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-393647 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-393838 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-394027 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-394215 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-394403 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-394595 util-scheduler-8620 DEBUG Running task: 3912 / 0x46620a0
Jul 07 20:57:21-394780 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:21-394959 util-8620 DEBUG process_notify is running
Jul 07 20:57:21-395131 util-8620 DEBUG client_notify is running
Jul 07 20:57:21-395310 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:21-395503 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:21-395695 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:21-395953 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:21-396201 util-scheduler-8620 DEBUG Checking readiness of task: 3907 / 0x46620a0
Jul 07 20:57:21-396395 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-396585 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-396774 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-396963 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-397152 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-397365 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-397554 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-397745 util-scheduler-8620 DEBUG Running task: 3907 / 0x46620a0
Jul 07 20:57:21-398151 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:21-398396 util-scheduler-8620 DEBUG Adding task: 3913 / 0x4662248
Jul 07 20:57:21-398644 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-398837 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-399028 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-399218 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-399407 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-399596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-399785 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-399974 util-scheduler-8620 DEBUG Running task: 3913 / 0x4662248
Jul 07 20:57:21-400165 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:21-400360 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:21-400577 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:21-400774 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:21-400972 util-scheduler-8620 DEBUG Adding task: 3914 / 0x46620a0
Jul 07 20:57:21-401161 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:21-401385 util-scheduler-8620 DEBUG Adding task: 3915 / 0x46620a0
Jul 07 20:57:21-401626 util-scheduler-8620 DEBUG Checking readiness of task: 3915 / 0x46620a0
Jul 07 20:57:21-401819 util-scheduler-8620 DEBUG Checking readiness of task: 3914 / 0x46620a0
Jul 07 20:57:21-402012 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:21-402201 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:21-402390 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:21-402578 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:21-402768 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:21-402957 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:21-403145 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:21-403334 util-scheduler-8620 DEBUG Running task: 3914 / 0x46620a0
Jul 07 20:57:21-403519 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:21-403693 util-8620 DEBUG process_notify is running
Jul 07 20:57:21-403861 util-8620 DEBUG client_notify is running
Jul 07 20:57:21-404047 util-scheduler-8620 DEBUG Canceling task: 3911 / 0x59ee8a0
Jul 07 20:57:21-404271 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:21-404485 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:21-404716 cadet-p2p-8620 DEBUG Checking 0x60ac9a8 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:21-404949 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:21-405127 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:21-405333 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:21-405616 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:21-405811 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:21-405990 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:21-406176 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:21-406364 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:21-406542 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:21-406724 util-scheduler-8620 DEBUG Canceling task: 3908 / 0x59e8808
Jul 07 20:57:21-406933 util-scheduler-8620 DEBUG Adding task: 3916 / 0x59e8808
Jul 07 20:57:21-407175 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:21-407345 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:21-407525 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:21-407724 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:21-407899 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:21-408090 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:21-408289 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:21-408494 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:21-408678 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:21-408856 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:21-409044 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:21-409308 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:26-393403 util-scheduler-8620 DEBUG Checking readiness of task: 3915 / 0x46620a0
Jul 07 20:57:26-393797 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-394558 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-394997 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-395201 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-395395 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-395599 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-395789 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-395983 util-scheduler-8620 DEBUG Running task: 3910 / 0x52cbfb8
Jul 07 20:57:26-396221 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:26-396480 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:26-396686 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:26-396886 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:26-397088 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:26-397350 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:26-397531 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:26-397752 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:26-398043 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:26-398240 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:26-398478 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:26-398685 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:26-399004 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:26-399204 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:26-399429 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:26-399612 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:26-399787 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:26-399995 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:26-400210 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:26-400436 util-scheduler-8620 DEBUG Adding task: 3917 / 0x59ee8a0
Jul 07 20:57:26-400616 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:26-400819 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:26-400994 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:26-401170 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:26-401432 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:26-401629 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:26-401807 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:26-402006 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:26-402254 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:26-402522 util-scheduler-8620 DEBUG Adding task: 3918 / 0x52cbfb8
Jul 07 20:57:26-402864 util-scheduler-8620 DEBUG Checking readiness of task: 3915 / 0x46620a0
Jul 07 20:57:26-403059 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-403250 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-403473 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-403665 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-403855 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-404044 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-404232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-404421 util-scheduler-8620 DEBUG Running task: 3917 / 0x59ee8a0
Jul 07 20:57:26-404630 util-scheduler-8620 DEBUG Adding task: 3919 / 0x59ee8a0
Jul 07 20:57:26-404855 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:26-405058 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:26-405288 util-scheduler-8620 DEBUG Adding task: 3920 / 0x46620a0
Jul 07 20:57:26-405533 util-scheduler-8620 DEBUG Checking readiness of task: 3920 / 0x46620a0
Jul 07 20:57:26-405727 util-scheduler-8620 DEBUG Checking readiness of task: 3915 / 0x46620a0
Jul 07 20:57:26-405917 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-406108 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-406297 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-406487 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-406678 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-406867 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-407055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-407246 util-scheduler-8620 DEBUG Running task: 3920 / 0x46620a0
Jul 07 20:57:26-407431 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:26-407609 util-8620 DEBUG process_notify is running
Jul 07 20:57:26-407783 util-8620 DEBUG client_notify is running
Jul 07 20:57:26-407962 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:26-408157 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:26-408350 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:26-408606 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:26-408854 util-scheduler-8620 DEBUG Checking readiness of task: 3915 / 0x46620a0
Jul 07 20:57:26-409047 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-409257 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-409448 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-409637 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-409826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-410015 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-410203 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-410393 util-scheduler-8620 DEBUG Running task: 3915 / 0x46620a0
Jul 07 20:57:26-410797 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:26-411026 util-scheduler-8620 DEBUG Adding task: 3921 / 0x4662248
Jul 07 20:57:26-411275 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-411469 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-411660 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-411850 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-412040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-412232 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-412436 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-412627 util-scheduler-8620 DEBUG Running task: 3921 / 0x4662248
Jul 07 20:57:26-412816 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:26-413010 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:26-413246 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:26-413446 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:26-413644 util-scheduler-8620 DEBUG Adding task: 3922 / 0x46620a0
Jul 07 20:57:26-413830 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:26-414033 util-scheduler-8620 DEBUG Adding task: 3923 / 0x46620a0
Jul 07 20:57:26-414275 util-scheduler-8620 DEBUG Checking readiness of task: 3923 / 0x46620a0
Jul 07 20:57:26-414467 util-scheduler-8620 DEBUG Checking readiness of task: 3922 / 0x46620a0
Jul 07 20:57:26-414659 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:26-414848 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:26-415038 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:26-415228 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:26-415418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:26-415607 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:26-415795 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:26-415985 util-scheduler-8620 DEBUG Running task: 3922 / 0x46620a0
Jul 07 20:57:26-416169 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:26-416343 util-8620 DEBUG process_notify is running
Jul 07 20:57:26-416512 util-8620 DEBUG client_notify is running
Jul 07 20:57:26-416697 util-scheduler-8620 DEBUG Canceling task: 3919 / 0x59ee8a0
Jul 07 20:57:26-416920 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:26-417146 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:26-417398 cadet-p2p-8620 DEBUG Checking 0x60b0008 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:26-417632 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:26-417810 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:26-417997 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:26-418281 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:26-418476 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:26-418654 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:26-418843 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:26-419031 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:26-419210 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:26-419394 util-scheduler-8620 DEBUG Canceling task: 3916 / 0x59e8808
Jul 07 20:57:26-419604 util-scheduler-8620 DEBUG Adding task: 3924 / 0x59e8808
Jul 07 20:57:26-419846 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:26-420017 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:26-420197 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:26-420396 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:26-420571 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:26-420744 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:26-420941 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:26-421147 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:26-421350 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:26-421528 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:26-421717 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:26-421962 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:31-407670 util-scheduler-8620 DEBUG Checking readiness of task: 3923 / 0x46620a0
Jul 07 20:57:31-408066 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-409106 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-409501 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-409698 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-409893 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-410083 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-410275 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-410468 util-scheduler-8620 DEBUG Running task: 3918 / 0x52cbfb8
Jul 07 20:57:31-410711 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:31-410971 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:31-411179 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:31-411380 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:31-411582 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:31-411818 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:31-411999 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:31-412221 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:31-412512 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:31-412709 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:31-412947 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:31-413156 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:31-413500 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:31-413701 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:31-413927 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:31-414111 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:31-414287 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:31-414492 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:31-414706 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:31-414932 util-scheduler-8620 DEBUG Adding task: 3925 / 0x59ee8a0
Jul 07 20:57:31-415112 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:31-415314 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:31-415492 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:31-415666 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:31-415905 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:31-416101 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:31-416280 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:31-416478 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:31-416722 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:31-416919 util-scheduler-8620 DEBUG Adding task: 3926 / 0x52cbfb8
Jul 07 20:57:31-417185 util-scheduler-8620 DEBUG Checking readiness of task: 3923 / 0x46620a0
Jul 07 20:57:31-417406 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-417596 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-417786 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-417976 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-418166 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-418354 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-418543 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-418732 util-scheduler-8620 DEBUG Running task: 3925 / 0x59ee8a0
Jul 07 20:57:31-418942 util-scheduler-8620 DEBUG Adding task: 3927 / 0x59ee8a0
Jul 07 20:57:31-419196 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:31-419400 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:31-419609 util-scheduler-8620 DEBUG Adding task: 3928 / 0x46620a0
Jul 07 20:57:31-419853 util-scheduler-8620 DEBUG Checking readiness of task: 3928 / 0x46620a0
Jul 07 20:57:31-420048 util-scheduler-8620 DEBUG Checking readiness of task: 3923 / 0x46620a0
Jul 07 20:57:31-420239 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-420429 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-420619 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-420812 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-421002 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-421213 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-421405 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-421596 util-scheduler-8620 DEBUG Running task: 3928 / 0x46620a0
Jul 07 20:57:31-421781 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:31-421958 util-8620 DEBUG process_notify is running
Jul 07 20:57:31-422131 util-8620 DEBUG client_notify is running
Jul 07 20:57:31-422310 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:31-422506 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:31-422697 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:31-422953 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:31-423203 util-scheduler-8620 DEBUG Checking readiness of task: 3923 / 0x46620a0
Jul 07 20:57:31-423396 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-423587 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-423778 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-423968 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-424158 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-424346 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-424534 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-424736 util-scheduler-8620 DEBUG Running task: 3923 / 0x46620a0
Jul 07 20:57:31-425141 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:31-425397 util-scheduler-8620 DEBUG Adding task: 3929 / 0x4662248
Jul 07 20:57:31-425645 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-425838 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-426028 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-426218 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-426408 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-426597 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-426787 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-426977 util-scheduler-8620 DEBUG Running task: 3929 / 0x4662248
Jul 07 20:57:31-427166 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:31-427362 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:31-427578 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:31-427776 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:31-427974 util-scheduler-8620 DEBUG Adding task: 3930 / 0x46620a0
Jul 07 20:57:31-428159 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:31-428379 util-scheduler-8620 DEBUG Adding task: 3931 / 0x46620a0
Jul 07 20:57:31-428621 util-scheduler-8620 DEBUG Checking readiness of task: 3931 / 0x46620a0
Jul 07 20:57:31-428813 util-scheduler-8620 DEBUG Checking readiness of task: 3930 / 0x46620a0
Jul 07 20:57:31-429004 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:31-429218 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:31-429410 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:31-429600 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:31-429789 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:31-429977 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:31-430165 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:31-430356 util-scheduler-8620 DEBUG Running task: 3930 / 0x46620a0
Jul 07 20:57:31-430538 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:31-430716 util-8620 DEBUG process_notify is running
Jul 07 20:57:31-430885 util-8620 DEBUG client_notify is running
Jul 07 20:57:31-431071 util-scheduler-8620 DEBUG Canceling task: 3927 / 0x59ee8a0
Jul 07 20:57:31-431294 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:31-431510 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:31-431742 cadet-p2p-8620 DEBUG Checking 0x60b4158 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:31-431975 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:31-432153 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:31-432339 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:31-432624 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:31-432819 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:31-432996 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:31-433185 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:31-433399 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:31-433617 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:31-433800 util-scheduler-8620 DEBUG Canceling task: 3924 / 0x59e8808
Jul 07 20:57:31-434012 util-scheduler-8620 DEBUG Adding task: 3932 / 0x59e8808
Jul 07 20:57:31-434255 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:31-434427 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:31-434607 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:31-434807 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:31-434982 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:31-435156 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:31-435355 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:31-435561 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:31-435744 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:31-435922 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:31-436111 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:31-436360 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:36-422070 util-scheduler-8620 DEBUG Checking readiness of task: 3931 / 0x46620a0
Jul 07 20:57:36-422465 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-423032 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-423473 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-423673 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-423869 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-424061 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-424281 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-424476 util-scheduler-8620 DEBUG Running task: 3926 / 0x52cbfb8
Jul 07 20:57:36-424717 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:36-424979 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:36-425211 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:36-425416 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:36-425620 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:36-425856 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:36-426038 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:36-426259 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:36-426551 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:36-426749 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:36-426988 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:36-427196 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:36-427515 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:36-427716 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:36-427942 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:36-428126 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:36-428301 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:36-428508 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:36-428724 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:36-428949 util-scheduler-8620 DEBUG Adding task: 3933 / 0x59ee8a0
Jul 07 20:57:36-429129 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:36-429354 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:36-429532 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:36-429707 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:36-429945 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:36-430141 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:36-430318 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:36-430516 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:36-430761 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:36-430960 util-scheduler-8620 DEBUG Adding task: 3934 / 0x52cbfb8
Jul 07 20:57:36-431227 util-scheduler-8620 DEBUG Checking readiness of task: 3931 / 0x46620a0
Jul 07 20:57:36-431422 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-431615 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-431804 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-431995 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-432184 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-432386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-432575 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-432765 util-scheduler-8620 DEBUG Running task: 3933 / 0x59ee8a0
Jul 07 20:57:36-432973 util-scheduler-8620 DEBUG Adding task: 3935 / 0x59ee8a0
Jul 07 20:57:36-433213 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:36-433419 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:36-433628 util-scheduler-8620 DEBUG Adding task: 3936 / 0x46620a0
Jul 07 20:57:36-433909 util-scheduler-8620 DEBUG Checking readiness of task: 3936 / 0x46620a0
Jul 07 20:57:36-434103 util-scheduler-8620 DEBUG Checking readiness of task: 3931 / 0x46620a0
Jul 07 20:57:36-434292 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-434482 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-434672 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-434879 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-435069 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-435258 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-435446 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-435637 util-scheduler-8620 DEBUG Running task: 3936 / 0x46620a0
Jul 07 20:57:36-435823 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:36-436002 util-8620 DEBUG process_notify is running
Jul 07 20:57:36-436174 util-8620 DEBUG client_notify is running
Jul 07 20:57:36-436352 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:36-436547 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:36-436738 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:36-436996 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:36-437263 util-scheduler-8620 DEBUG Checking readiness of task: 3931 / 0x46620a0
Jul 07 20:57:36-437459 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-437649 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-437838 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-438028 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-438217 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-438405 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-438593 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-438783 util-scheduler-8620 DEBUG Running task: 3931 / 0x46620a0
Jul 07 20:57:36-439188 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:36-439417 util-scheduler-8620 DEBUG Adding task: 3937 / 0x4662248
Jul 07 20:57:36-439664 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-439856 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-440046 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-440237 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-440428 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-440617 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-440806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-441007 util-scheduler-8620 DEBUG Running task: 3937 / 0x4662248
Jul 07 20:57:36-441219 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:36-441416 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:36-441636 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:36-441834 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:36-442033 util-scheduler-8620 DEBUG Adding task: 3938 / 0x46620a0
Jul 07 20:57:36-442219 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:36-442424 util-scheduler-8620 DEBUG Adding task: 3939 / 0x46620a0
Jul 07 20:57:36-442665 util-scheduler-8620 DEBUG Checking readiness of task: 3939 / 0x46620a0
Jul 07 20:57:36-442856 util-scheduler-8620 DEBUG Checking readiness of task: 3938 / 0x46620a0
Jul 07 20:57:36-443048 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:36-443238 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:36-443427 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:36-443616 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:36-443821 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:36-444012 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:36-444200 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:36-444390 util-scheduler-8620 DEBUG Running task: 3938 / 0x46620a0
Jul 07 20:57:36-444574 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:36-444748 util-8620 DEBUG process_notify is running
Jul 07 20:57:36-444917 util-8620 DEBUG client_notify is running
Jul 07 20:57:36-445102 util-scheduler-8620 DEBUG Canceling task: 3935 / 0x59ee8a0
Jul 07 20:57:36-445346 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:36-445562 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:36-445795 cadet-p2p-8620 DEBUG Checking 0x60b7aa8 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:36-446029 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:36-446208 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:36-446395 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:36-446676 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:36-446871 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:36-447050 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:36-447239 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:36-447426 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:36-447604 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:36-447788 util-scheduler-8620 DEBUG Canceling task: 3932 / 0x59e8808
Jul 07 20:57:36-447998 util-scheduler-8620 DEBUG Adding task: 3940 / 0x59e8808
Jul 07 20:57:36-448240 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:36-448412 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:36-448593 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:36-448793 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:36-448968 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:36-449142 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:36-449360 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:36-449610 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:36-449797 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:36-449976 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:36-450167 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:36-450413 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:41-436134 util-scheduler-8620 DEBUG Checking readiness of task: 3939 / 0x46620a0
Jul 07 20:57:41-436523 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-437853 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-438194 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-438392 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-438585 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-438777 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-438968 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-439162 util-scheduler-8620 DEBUG Running task: 3934 / 0x52cbfb8
Jul 07 20:57:41-439402 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:41-439661 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:41-439868 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:41-440071 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:41-440274 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:41-440510 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:41-440707 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:41-440929 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:41-441291 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:41-441492 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:41-441730 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:41-441939 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:41-442258 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:41-442458 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:41-442684 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:41-442867 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:41-443042 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:41-443249 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:41-443464 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:41-443688 util-scheduler-8620 DEBUG Adding task: 3941 / 0x59ee8a0
Jul 07 20:57:41-443869 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:41-444072 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:41-444248 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:41-444423 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:41-444661 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:41-444856 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:41-445034 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:41-445257 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:41-445504 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:41-445702 util-scheduler-8620 DEBUG Adding task: 3942 / 0x52cbfb8
Jul 07 20:57:41-445966 util-scheduler-8620 DEBUG Checking readiness of task: 3939 / 0x46620a0
Jul 07 20:57:41-446161 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-446351 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-446541 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-446730 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-446920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-447109 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-447298 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-447487 util-scheduler-8620 DEBUG Running task: 3941 / 0x59ee8a0
Jul 07 20:57:41-447695 util-scheduler-8620 DEBUG Adding task: 3943 / 0x59ee8a0
Jul 07 20:57:41-447914 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:41-448116 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:41-448324 util-scheduler-8620 DEBUG Adding task: 3944 / 0x46620a0
Jul 07 20:57:41-448568 util-scheduler-8620 DEBUG Checking readiness of task: 3944 / 0x46620a0
Jul 07 20:57:41-448761 util-scheduler-8620 DEBUG Checking readiness of task: 3939 / 0x46620a0
Jul 07 20:57:41-448952 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-449141 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-449358 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-449548 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-449738 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-449926 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-450116 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-450307 util-scheduler-8620 DEBUG Running task: 3944 / 0x46620a0
Jul 07 20:57:41-450492 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:41-450670 util-8620 DEBUG process_notify is running
Jul 07 20:57:41-450858 util-8620 DEBUG client_notify is running
Jul 07 20:57:41-451037 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:41-451232 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:41-451424 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:41-451681 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:41-451930 util-scheduler-8620 DEBUG Checking readiness of task: 3939 / 0x46620a0
Jul 07 20:57:41-452124 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-452314 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-452504 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-452694 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-452884 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-453073 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-453288 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-453481 util-scheduler-8620 DEBUG Running task: 3939 / 0x46620a0
Jul 07 20:57:41-453887 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:41-454118 util-scheduler-8620 DEBUG Adding task: 3945 / 0x4662248
Jul 07 20:57:41-454366 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-454559 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-454749 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-454940 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-455129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-455318 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-455505 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-455695 util-scheduler-8620 DEBUG Running task: 3945 / 0x4662248
Jul 07 20:57:41-455885 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:41-456080 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:41-456295 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:41-456493 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:41-456690 util-scheduler-8620 DEBUG Adding task: 3946 / 0x46620a0
Jul 07 20:57:41-456876 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:41-457079 util-scheduler-8620 DEBUG Adding task: 3947 / 0x46620a0
Jul 07 20:57:41-457346 util-scheduler-8620 DEBUG Checking readiness of task: 3947 / 0x46620a0
Jul 07 20:57:41-457538 util-scheduler-8620 DEBUG Checking readiness of task: 3946 / 0x46620a0
Jul 07 20:57:41-457730 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:41-457919 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:41-458110 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:41-458299 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:41-458489 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:41-458678 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:41-458866 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:41-459056 util-scheduler-8620 DEBUG Running task: 3946 / 0x46620a0
Jul 07 20:57:41-459239 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:41-459413 util-8620 DEBUG process_notify is running
Jul 07 20:57:41-459581 util-8620 DEBUG client_notify is running
Jul 07 20:57:41-459767 util-scheduler-8620 DEBUG Canceling task: 3943 / 0x59ee8a0
Jul 07 20:57:41-460006 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:41-460223 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:41-460453 cadet-p2p-8620 DEBUG Checking 0x60bb2b0 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:41-460686 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:41-460863 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:41-461050 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:41-461358 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:41-461555 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:41-461735 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:41-461933 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:41-462122 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:41-462301 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:41-462483 util-scheduler-8620 DEBUG Canceling task: 3940 / 0x59e8808
Jul 07 20:57:41-462695 util-scheduler-8620 DEBUG Adding task: 3948 / 0x59e8808
Jul 07 20:57:41-462937 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:41-463107 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:41-463291 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:41-463491 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:41-463666 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:41-463839 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:41-464038 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:41-464243 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:41-464426 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:41-464604 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:41-464792 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:41-465039 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:46-450843 util-scheduler-8620 DEBUG Checking readiness of task: 3947 / 0x46620a0
Jul 07 20:57:46-451224 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-452138 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-452345 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-452595 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-452804 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-452996 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-453187 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-453402 util-scheduler-8620 DEBUG Running task: 3942 / 0x52cbfb8
Jul 07 20:57:46-453640 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:46-453897 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:46-454105 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:46-454308 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:46-454512 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:46-454748 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:46-454928 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:46-455150 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:46-455439 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:46-455636 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:46-455873 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:46-456097 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:46-456420 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:46-456623 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:46-456850 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:46-457061 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:46-457259 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:46-457468 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:46-457684 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:46-457912 util-scheduler-8620 DEBUG Adding task: 3949 / 0x59ee8a0
Jul 07 20:57:46-458092 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:46-458295 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:46-458472 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:46-458647 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:46-458885 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:46-459081 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:46-459258 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:46-459457 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:46-459700 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:46-459897 util-scheduler-8620 DEBUG Adding task: 3950 / 0x52cbfb8
Jul 07 20:57:46-460155 util-scheduler-8620 DEBUG Checking readiness of task: 3947 / 0x46620a0
Jul 07 20:57:46-460350 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-460541 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-460733 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-460923 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-461113 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-461323 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-461513 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-461703 util-scheduler-8620 DEBUG Running task: 3949 / 0x59ee8a0
Jul 07 20:57:46-461932 util-scheduler-8620 DEBUG Adding task: 3951 / 0x59ee8a0
Jul 07 20:57:46-462154 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:46-462357 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:46-462566 util-scheduler-8620 DEBUG Adding task: 3952 / 0x46620a0
Jul 07 20:57:46-462810 util-scheduler-8620 DEBUG Checking readiness of task: 3952 / 0x46620a0
Jul 07 20:57:46-463005 util-scheduler-8620 DEBUG Checking readiness of task: 3947 / 0x46620a0
Jul 07 20:57:46-463195 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-463385 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-463576 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-463766 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-463956 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-464145 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-464335 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-464530 util-scheduler-8620 DEBUG Running task: 3952 / 0x46620a0
Jul 07 20:57:46-464716 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:46-464894 util-8620 DEBUG process_notify is running
Jul 07 20:57:46-465067 util-8620 DEBUG client_notify is running
Jul 07 20:57:46-465265 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:46-465462 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:46-465653 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:46-465907 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:46-466154 util-scheduler-8620 DEBUG Checking readiness of task: 3947 / 0x46620a0
Jul 07 20:57:46-466348 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-466555 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-466747 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-466936 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-467126 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-467315 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-467504 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-467695 util-scheduler-8620 DEBUG Running task: 3947 / 0x46620a0
Jul 07 20:57:46-468103 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:46-468334 util-scheduler-8620 DEBUG Adding task: 3953 / 0x4662248
Jul 07 20:57:46-468584 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-468778 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-468969 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-469160 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-469371 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-469561 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-469763 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-469954 util-scheduler-8620 DEBUG Running task: 3953 / 0x4662248
Jul 07 20:57:46-470144 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:46-470340 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:46-470558 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:46-470757 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:46-470955 util-scheduler-8620 DEBUG Adding task: 3954 / 0x46620a0
Jul 07 20:57:46-471140 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:46-471342 util-scheduler-8620 DEBUG Adding task: 3955 / 0x46620a0
Jul 07 20:57:46-471582 util-scheduler-8620 DEBUG Checking readiness of task: 3955 / 0x46620a0
Jul 07 20:57:46-471775 util-scheduler-8620 DEBUG Checking readiness of task: 3954 / 0x46620a0
Jul 07 20:57:46-471966 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:46-472156 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:46-472346 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:46-472535 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:46-472724 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:46-472913 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:46-473102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:46-473311 util-scheduler-8620 DEBUG Running task: 3954 / 0x46620a0
Jul 07 20:57:46-473494 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:46-473669 util-8620 DEBUG process_notify is running
Jul 07 20:57:46-473837 util-8620 DEBUG client_notify is running
Jul 07 20:57:46-474023 util-scheduler-8620 DEBUG Canceling task: 3951 / 0x59ee8a0
Jul 07 20:57:46-474245 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:46-474463 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:46-474694 cadet-p2p-8620 DEBUG Checking 0x60be700 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:46-474927 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:46-475106 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:46-475292 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:46-475575 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:46-475771 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:46-475966 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:46-476154 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:46-476342 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:46-476521 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:46-476703 util-scheduler-8620 DEBUG Canceling task: 3948 / 0x59e8808
Jul 07 20:57:46-476915 util-scheduler-8620 DEBUG Adding task: 3956 / 0x59e8808
Jul 07 20:57:46-477158 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:46-477351 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:46-477532 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:46-477732 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:46-477907 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:46-478080 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:46-478278 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:46-478484 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:46-478667 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:46-478845 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:46-479033 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:46-479276 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:51-465030 util-scheduler-8620 DEBUG Checking readiness of task: 3955 / 0x46620a0
Jul 07 20:57:51-465424 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-466038 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-466251 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-466484 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-466691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-466881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-467072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-467265 util-scheduler-8620 DEBUG Running task: 3950 / 0x52cbfb8
Jul 07 20:57:51-467499 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:51-467754 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:51-467960 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:51-468161 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:51-468363 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:51-468597 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:51-468777 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:51-468998 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:51-469313 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:51-469512 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:51-469749 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:51-469957 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:51-470275 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:51-470475 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:51-470700 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:51-470883 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:51-471059 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:51-471264 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:51-471477 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:51-471699 util-scheduler-8620 DEBUG Adding task: 3957 / 0x59ee8a0
Jul 07 20:57:51-471880 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:51-472083 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:51-472258 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:51-472457 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:51-472695 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:51-472892 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:51-473069 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:51-473287 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:51-473530 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:51-473728 util-scheduler-8620 DEBUG Adding task: 3958 / 0x52cbfb8
Jul 07 20:57:51-473983 util-scheduler-8620 DEBUG Checking readiness of task: 3955 / 0x46620a0
Jul 07 20:57:51-474176 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-474365 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-474555 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-474744 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-474934 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-475122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-475311 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-475499 util-scheduler-8620 DEBUG Running task: 3957 / 0x59ee8a0
Jul 07 20:57:51-475708 util-scheduler-8620 DEBUG Adding task: 3959 / 0x59ee8a0
Jul 07 20:57:51-475930 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:51-476134 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:51-476341 util-scheduler-8620 DEBUG Adding task: 3960 / 0x46620a0
Jul 07 20:57:51-476584 util-scheduler-8620 DEBUG Checking readiness of task: 3960 / 0x46620a0
Jul 07 20:57:51-476777 util-scheduler-8620 DEBUG Checking readiness of task: 3955 / 0x46620a0
Jul 07 20:57:51-476981 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-477171 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-477380 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-477571 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-477760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-477948 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-478137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-478328 util-scheduler-8620 DEBUG Running task: 3960 / 0x46620a0
Jul 07 20:57:51-478513 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:51-478690 util-8620 DEBUG process_notify is running
Jul 07 20:57:51-478862 util-8620 DEBUG client_notify is running
Jul 07 20:57:51-479040 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:51-479236 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:51-479425 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:51-479678 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:51-479927 util-scheduler-8620 DEBUG Checking readiness of task: 3955 / 0x46620a0
Jul 07 20:57:51-480120 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-480310 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-480500 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-480690 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-480880 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-481068 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-481277 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-481468 util-scheduler-8620 DEBUG Running task: 3955 / 0x46620a0
Jul 07 20:57:51-481886 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:51-482115 util-scheduler-8620 DEBUG Adding task: 3961 / 0x4662248
Jul 07 20:57:51-482363 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-482556 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-482746 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-482936 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-483125 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-483313 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-483501 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-483690 util-scheduler-8620 DEBUG Running task: 3961 / 0x4662248
Jul 07 20:57:51-483879 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:51-484073 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:51-484289 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:51-484487 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:51-484683 util-scheduler-8620 DEBUG Adding task: 3962 / 0x46620a0
Jul 07 20:57:51-484868 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:51-485071 util-scheduler-8620 DEBUG Adding task: 3963 / 0x46620a0
Jul 07 20:57:51-485331 util-scheduler-8620 DEBUG Checking readiness of task: 3963 / 0x46620a0
Jul 07 20:57:51-485525 util-scheduler-8620 DEBUG Checking readiness of task: 3962 / 0x46620a0
Jul 07 20:57:51-485720 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:51-485909 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:51-486099 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:51-486289 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:51-486479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:51-486666 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:51-486854 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:51-487044 util-scheduler-8620 DEBUG Running task: 3962 / 0x46620a0
Jul 07 20:57:51-487230 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:51-487404 util-8620 DEBUG process_notify is running
Jul 07 20:57:51-487573 util-8620 DEBUG client_notify is running
Jul 07 20:57:51-487756 util-scheduler-8620 DEBUG Canceling task: 3959 / 0x59ee8a0
Jul 07 20:57:51-487977 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:51-488193 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:51-488424 cadet-p2p-8620 DEBUG Checking 0x60c2010 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:51-488656 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:51-488834 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:51-489019 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:51-489320 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:51-489516 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:51-489695 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:51-489882 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:51-490070 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:51-490249 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:51-490431 util-scheduler-8620 DEBUG Canceling task: 3956 / 0x59e8808
Jul 07 20:57:51-490641 util-scheduler-8620 DEBUG Adding task: 3964 / 0x59e8808
Jul 07 20:57:51-490883 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:51-491053 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:51-491234 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:51-491433 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:51-491621 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:51-491795 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:51-491992 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:51-492196 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:51-492379 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:51-492557 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:51-492744 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:51-492987 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:56-478860 util-scheduler-8620 DEBUG Checking readiness of task: 3963 / 0x46620a0
Jul 07 20:57:56-479228 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-479792 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-479989 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-480235 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-480444 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-480634 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-480823 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-481015 util-scheduler-8620 DEBUG Running task: 3958 / 0x52cbfb8
Jul 07 20:57:56-481269 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:57:56-481526 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:57:56-481731 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:57:56-481931 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:57:56-482132 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:57:56-482364 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:57:56-482544 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:57:56-482766 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:57:56-483053 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:57:56-483251 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:57:56-483486 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:57:56-483694 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:57:56-484010 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:57:56-484225 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:57:56-484449 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:57:56-484633 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:57:56-484807 cadet-con-8620 DEBUG  sendable
Jul 07 20:57:56-485013 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:57:56-485246 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:57:56-485472 util-scheduler-8620 DEBUG Adding task: 3965 / 0x59ee8a0
Jul 07 20:57:56-485653 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:57:56-485856 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:56-486033 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:57:56-486208 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:57:56-486445 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:57:56-486641 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:57:56-486819 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:57:56-487019 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:56-487261 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:57:56-487458 util-scheduler-8620 DEBUG Adding task: 3966 / 0x52cbfb8
Jul 07 20:57:56-487712 util-scheduler-8620 DEBUG Checking readiness of task: 3963 / 0x46620a0
Jul 07 20:57:56-487905 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-488129 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-488320 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-488512 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-488702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-488911 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-489109 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-489319 util-scheduler-8620 DEBUG Running task: 3965 / 0x59ee8a0
Jul 07 20:57:56-489528 util-scheduler-8620 DEBUG Adding task: 3967 / 0x59ee8a0
Jul 07 20:57:56-489749 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:57:56-489953 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:56-490161 util-scheduler-8620 DEBUG Adding task: 3968 / 0x46620a0
Jul 07 20:57:56-490405 util-scheduler-8620 DEBUG Checking readiness of task: 3968 / 0x46620a0
Jul 07 20:57:56-490600 util-scheduler-8620 DEBUG Checking readiness of task: 3963 / 0x46620a0
Jul 07 20:57:56-490790 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-490980 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-491169 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-491359 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-491548 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-491737 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-491924 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-492114 util-scheduler-8620 DEBUG Running task: 3968 / 0x46620a0
Jul 07 20:57:56-492298 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:56-492475 util-8620 DEBUG process_notify is running
Jul 07 20:57:56-492646 util-8620 DEBUG client_notify is running
Jul 07 20:57:56-492825 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:57:56-493021 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:56-493231 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:57:56-493485 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:57:56-493732 util-scheduler-8620 DEBUG Checking readiness of task: 3963 / 0x46620a0
Jul 07 20:57:56-493925 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-494115 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-494305 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-494495 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-494686 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-494875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-495063 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-495254 util-scheduler-8620 DEBUG Running task: 3963 / 0x46620a0
Jul 07 20:57:56-495659 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:57:56-495888 util-scheduler-8620 DEBUG Adding task: 3969 / 0x4662248
Jul 07 20:57:56-496134 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-496326 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-496517 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-496707 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-496899 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-497105 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-497314 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-497504 util-scheduler-8620 DEBUG Running task: 3969 / 0x4662248
Jul 07 20:57:56-497695 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:57:56-497890 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:57:56-498105 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:57:56-498301 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:57:56-498498 util-scheduler-8620 DEBUG Adding task: 3970 / 0x46620a0
Jul 07 20:57:56-498684 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:57:56-498887 util-scheduler-8620 DEBUG Adding task: 3971 / 0x46620a0
Jul 07 20:57:56-499127 util-scheduler-8620 DEBUG Checking readiness of task: 3971 / 0x46620a0
Jul 07 20:57:56-499321 util-scheduler-8620 DEBUG Checking readiness of task: 3970 / 0x46620a0
Jul 07 20:57:56-499512 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:57:56-499701 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:57:56-499891 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:57:56-500080 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:57:56-500270 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:57:56-500459 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:57:56-500647 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:57:56-500838 util-scheduler-8620 DEBUG Running task: 3970 / 0x46620a0
Jul 07 20:57:56-501021 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:57:56-501227 util-8620 DEBUG process_notify is running
Jul 07 20:57:56-501400 util-8620 DEBUG client_notify is running
Jul 07 20:57:56-501585 util-scheduler-8620 DEBUG Canceling task: 3967 / 0x59ee8a0
Jul 07 20:57:56-501808 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:57:56-502024 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:57:56-502255 cadet-p2p-8620 DEBUG Checking 0x60c5510 towards 2FDYFV0X (->V8XX)
Jul 07 20:57:56-502489 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:57:56-502668 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:57:56-502853 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:57:56-503137 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:57:56-503348 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:57:56-503529 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:57:56-503716 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:57:56-503906 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:57:56-504085 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:57:56-504267 util-scheduler-8620 DEBUG Canceling task: 3964 / 0x59e8808
Jul 07 20:57:56-504478 util-scheduler-8620 DEBUG Adding task: 3972 / 0x59e8808
Jul 07 20:57:56-504721 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:57:56-504891 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:57:56-505071 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:57:56-505293 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:57:56-505479 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:57:56-505653 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:57:56-505851 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:57:56-506057 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:57:56-506239 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:57:56-506417 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:57:56-506606 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:57:56-506851 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:01-492596 util-scheduler-8620 DEBUG Checking readiness of task: 3971 / 0x46620a0
Jul 07 20:58:01-492958 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-493557 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-493756 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-494003 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-494211 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-494401 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-494592 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-494785 util-scheduler-8620 DEBUG Running task: 3966 / 0x52cbfb8
Jul 07 20:58:01-495019 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:01-495272 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:58:01-495477 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:01-495678 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:01-495879 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:01-496113 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:01-496294 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:01-496515 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:01-496802 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:01-496999 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:01-497256 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:01-497466 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:01-497780 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:01-497981 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:01-498208 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:01-498391 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:01-498567 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:01-498772 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:01-498985 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:01-499207 util-scheduler-8620 DEBUG Adding task: 3973 / 0x59ee8a0
Jul 07 20:58:01-499387 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:01-499590 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:01-499767 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:01-499942 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:01-500178 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:01-500374 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:01-500551 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:01-500749 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:01-500992 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:01-501210 util-scheduler-8620 DEBUG Adding task: 3974 / 0x52cbfb8
Jul 07 20:58:01-501477 util-scheduler-8620 DEBUG Checking readiness of task: 3971 / 0x46620a0
Jul 07 20:58:01-501671 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-501860 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-502051 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-502240 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-502430 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-502620 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-502809 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-502998 util-scheduler-8620 DEBUG Running task: 3973 / 0x59ee8a0
Jul 07 20:58:01-503230 util-scheduler-8620 DEBUG Adding task: 3975 / 0x59ee8a0
Jul 07 20:58:01-503453 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:01-503657 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:01-503864 util-scheduler-8620 DEBUG Adding task: 3976 / 0x46620a0
Jul 07 20:58:01-504107 util-scheduler-8620 DEBUG Checking readiness of task: 3976 / 0x46620a0
Jul 07 20:58:01-504302 util-scheduler-8620 DEBUG Checking readiness of task: 3971 / 0x46620a0
Jul 07 20:58:01-504493 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-504683 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-504873 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-505061 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-505272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-505461 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-505650 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-505841 util-scheduler-8620 DEBUG Running task: 3976 / 0x46620a0
Jul 07 20:58:01-506026 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:01-506204 util-8620 DEBUG process_notify is running
Jul 07 20:58:01-506376 util-8620 DEBUG client_notify is running
Jul 07 20:58:01-506555 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:01-506750 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:01-506942 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:01-507194 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:01-507442 util-scheduler-8620 DEBUG Checking readiness of task: 3971 / 0x46620a0
Jul 07 20:58:01-507635 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-507825 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-508015 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-508208 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-508398 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-508585 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-508774 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-508964 util-scheduler-8620 DEBUG Running task: 3971 / 0x46620a0
Jul 07 20:58:01-509385 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:01-509615 util-scheduler-8620 DEBUG Adding task: 3977 / 0x4662248
Jul 07 20:58:01-509863 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-510055 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-510245 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-510435 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-510624 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-510812 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-511000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-511190 util-scheduler-8620 DEBUG Running task: 3977 / 0x4662248
Jul 07 20:58:01-511379 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:01-511575 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:01-511791 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:01-511987 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:01-512200 util-scheduler-8620 DEBUG Adding task: 3978 / 0x46620a0
Jul 07 20:58:01-512385 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:01-512587 util-scheduler-8620 DEBUG Adding task: 3979 / 0x46620a0
Jul 07 20:58:01-512842 util-scheduler-8620 DEBUG Checking readiness of task: 3979 / 0x46620a0
Jul 07 20:58:01-513034 util-scheduler-8620 DEBUG Checking readiness of task: 3978 / 0x46620a0
Jul 07 20:58:01-513245 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:01-513437 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:01-513628 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:01-513817 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:01-514009 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:01-514198 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:01-514387 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:01-514578 util-scheduler-8620 DEBUG Running task: 3978 / 0x46620a0
Jul 07 20:58:01-514761 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:01-514936 util-8620 DEBUG process_notify is running
Jul 07 20:58:01-515104 util-8620 DEBUG client_notify is running
Jul 07 20:58:01-515290 util-scheduler-8620 DEBUG Canceling task: 3975 / 0x59ee8a0
Jul 07 20:58:01-515512 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:01-515728 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:01-515959 cadet-p2p-8620 DEBUG Checking 0x60c8d88 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:01-516193 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:01-516371 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:01-516558 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:01-516842 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:01-517037 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:01-517234 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:01-517424 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:01-517612 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:01-517789 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:01-517973 util-scheduler-8620 DEBUG Canceling task: 3972 / 0x59e8808
Jul 07 20:58:01-518187 util-scheduler-8620 DEBUG Adding task: 3980 / 0x59e8808
Jul 07 20:58:01-518430 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:01-518600 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:01-518780 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:01-518980 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:01-519155 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:01-519329 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:01-519527 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:01-519734 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:01-519917 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:01-520095 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:01-520284 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:01-520527 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:06-506325 util-scheduler-8620 DEBUG Checking readiness of task: 3979 / 0x46620a0
Jul 07 20:58:06-506696 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-507161 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-507358 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-507605 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-507813 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-508030 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-508222 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-508417 util-scheduler-8620 DEBUG Running task: 3974 / 0x52cbfb8
Jul 07 20:58:06-508652 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:06-508909 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:58:06-509116 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:06-509338 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:06-509543 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:06-509778 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:06-509959 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:06-510182 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:06-510471 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:06-510668 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:06-510906 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:06-511116 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:06-511433 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:06-511634 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:06-511859 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:06-512044 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:06-512220 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:06-512427 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:06-512641 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:06-512866 util-scheduler-8620 DEBUG Adding task: 3981 / 0x59ee8a0
Jul 07 20:58:06-513048 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:06-513270 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:06-513448 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:06-513625 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:06-513863 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:06-514060 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:06-514237 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:06-514436 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:06-514679 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:06-514877 util-scheduler-8620 DEBUG Adding task: 3982 / 0x52cbfb8
Jul 07 20:58:06-515134 util-scheduler-8620 DEBUG Checking readiness of task: 3979 / 0x46620a0
Jul 07 20:58:06-515328 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-515519 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-515710 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-515900 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-516092 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-516283 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-516472 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-516663 util-scheduler-8620 DEBUG Running task: 3981 / 0x59ee8a0
Jul 07 20:58:06-516871 util-scheduler-8620 DEBUG Adding task: 3983 / 0x59ee8a0
Jul 07 20:58:06-517092 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:06-517315 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:06-517522 util-scheduler-8620 DEBUG Adding task: 3984 / 0x46620a0
Jul 07 20:58:06-517767 util-scheduler-8620 DEBUG Checking readiness of task: 3984 / 0x46620a0
Jul 07 20:58:06-517962 util-scheduler-8620 DEBUG Checking readiness of task: 3979 / 0x46620a0
Jul 07 20:58:06-518154 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-518361 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-518553 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-518744 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-518935 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-519124 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-519318 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-519509 util-scheduler-8620 DEBUG Running task: 3984 / 0x46620a0
Jul 07 20:58:06-519693 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:06-519886 util-8620 DEBUG process_notify is running
Jul 07 20:58:06-520060 util-8620 DEBUG client_notify is running
Jul 07 20:58:06-520239 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:06-520436 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:06-520628 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:06-520882 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:06-521130 util-scheduler-8620 DEBUG Checking readiness of task: 3979 / 0x46620a0
Jul 07 20:58:06-521345 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-521537 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-521728 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-521919 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-522108 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-522343 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-522537 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-522739 util-scheduler-8620 DEBUG Running task: 3979 / 0x46620a0
Jul 07 20:58:06-523143 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:06-523375 util-scheduler-8620 DEBUG Adding task: 3985 / 0x4662248
Jul 07 20:58:06-523627 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-523820 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-524012 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-524204 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-524394 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-524585 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-524774 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-524965 util-scheduler-8620 DEBUG Running task: 3985 / 0x4662248
Jul 07 20:58:06-525156 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:06-525373 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:06-525591 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:06-525789 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:06-525989 util-scheduler-8620 DEBUG Adding task: 3986 / 0x46620a0
Jul 07 20:58:06-526174 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:06-526378 util-scheduler-8620 DEBUG Adding task: 3987 / 0x46620a0
Jul 07 20:58:06-526618 util-scheduler-8620 DEBUG Checking readiness of task: 3987 / 0x46620a0
Jul 07 20:58:06-526812 util-scheduler-8620 DEBUG Checking readiness of task: 3986 / 0x46620a0
Jul 07 20:58:06-527003 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:06-527194 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:06-527385 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:06-527593 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:06-527784 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:06-527973 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:06-528163 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:06-528354 util-scheduler-8620 DEBUG Running task: 3986 / 0x46620a0
Jul 07 20:58:06-528539 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:06-528715 util-8620 DEBUG process_notify is running
Jul 07 20:58:06-528885 util-8620 DEBUG client_notify is running
Jul 07 20:58:06-529070 util-scheduler-8620 DEBUG Canceling task: 3983 / 0x59ee8a0
Jul 07 20:58:06-529316 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:06-529534 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:06-529767 cadet-p2p-8620 DEBUG Checking 0x60cb9d0 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:06-530001 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:06-530180 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:06-530368 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:06-530654 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:06-530850 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:06-531029 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:06-531218 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:06-531406 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:06-531585 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:06-531768 util-scheduler-8620 DEBUG Canceling task: 3980 / 0x59e8808
Jul 07 20:58:06-531980 util-scheduler-8620 DEBUG Adding task: 3988 / 0x59e8808
Jul 07 20:58:06-532225 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:06-532396 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:06-532577 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:06-532777 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:06-532954 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:06-533128 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:06-533349 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:06-533554 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:06-533739 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:06-533916 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:06-534106 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:06-534352 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:11-520024 util-scheduler-8620 DEBUG Checking readiness of task: 3987 / 0x46620a0
Jul 07 20:58:11-520419 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-521047 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-521288 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-521522 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-521718 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-521908 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-522101 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-522295 util-scheduler-8620 DEBUG Running task: 3982 / 0x52cbfb8
Jul 07 20:58:11-522535 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:11-522793 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:58:11-523000 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:11-523200 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:11-523402 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:11-523637 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:11-523846 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:11-524069 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:11-524363 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:11-524560 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:11-524797 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:11-525005 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:11-525345 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:11-525549 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:11-525775 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:11-525960 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:11-526136 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:11-526342 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:11-526557 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:11-526782 util-scheduler-8620 DEBUG Adding task: 3989 / 0x59ee8a0
Jul 07 20:58:11-526963 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:11-527178 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:11-527355 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:11-527530 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:11-527767 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:11-527963 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:11-528141 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:11-528338 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:11-528582 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:11-528779 util-scheduler-8620 DEBUG Adding task: 3990 / 0x52cbfb8
Jul 07 20:58:11-529039 util-scheduler-8620 DEBUG Checking readiness of task: 3987 / 0x46620a0
Jul 07 20:58:11-529251 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-529443 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-529633 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-529824 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-530013 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-530201 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-530389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-530581 util-scheduler-8620 DEBUG Running task: 3989 / 0x59ee8a0
Jul 07 20:58:11-530790 util-scheduler-8620 DEBUG Adding task: 3991 / 0x59ee8a0
Jul 07 20:58:11-531011 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:11-531213 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:11-531421 util-scheduler-8620 DEBUG Adding task: 3992 / 0x46620a0
Jul 07 20:58:11-531665 util-scheduler-8620 DEBUG Checking readiness of task: 3992 / 0x46620a0
Jul 07 20:58:11-531859 util-scheduler-8620 DEBUG Checking readiness of task: 3987 / 0x46620a0
Jul 07 20:58:11-532050 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-532239 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-532430 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-532620 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-532809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-532998 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-533186 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-533396 util-scheduler-8620 DEBUG Running task: 3992 / 0x46620a0
Jul 07 20:58:11-533581 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:11-533775 util-8620 DEBUG process_notify is running
Jul 07 20:58:11-533948 util-8620 DEBUG client_notify is running
Jul 07 20:58:11-534128 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:11-534322 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:11-534514 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:11-534771 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:11-535020 util-scheduler-8620 DEBUG Checking readiness of task: 3987 / 0x46620a0
Jul 07 20:58:11-535214 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-535405 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-535595 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-535784 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-535974 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-536162 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-536351 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-536540 util-scheduler-8620 DEBUG Running task: 3987 / 0x46620a0
Jul 07 20:58:11-536966 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:11-537217 util-scheduler-8620 DEBUG Adding task: 3993 / 0x4662248
Jul 07 20:58:11-537467 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-537660 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-537850 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-538041 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-538231 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-538420 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-538609 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-538798 util-scheduler-8620 DEBUG Running task: 3993 / 0x4662248
Jul 07 20:58:11-538987 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:11-539183 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:11-539399 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:11-539596 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:11-539794 util-scheduler-8620 DEBUG Adding task: 3994 / 0x46620a0
Jul 07 20:58:11-539979 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:11-540184 util-scheduler-8620 DEBUG Adding task: 3995 / 0x46620a0
Jul 07 20:58:11-540424 util-scheduler-8620 DEBUG Checking readiness of task: 3995 / 0x46620a0
Jul 07 20:58:11-540620 util-scheduler-8620 DEBUG Checking readiness of task: 3994 / 0x46620a0
Jul 07 20:58:11-540812 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:11-541001 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:11-541208 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:11-541400 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:11-541589 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:11-541778 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:11-541965 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:11-542156 util-scheduler-8620 DEBUG Running task: 3994 / 0x46620a0
Jul 07 20:58:11-542339 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:11-542515 util-8620 DEBUG process_notify is running
Jul 07 20:58:11-542683 util-8620 DEBUG client_notify is running
Jul 07 20:58:11-542884 util-scheduler-8620 DEBUG Canceling task: 3991 / 0x59ee8a0
Jul 07 20:58:11-543109 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:11-543325 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:11-543557 cadet-p2p-8620 DEBUG Checking 0x60cfc90 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:11-543791 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:11-543969 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:11-544156 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:11-544440 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:11-544635 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:11-544813 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:11-545001 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:11-545207 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:11-545389 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:11-545572 util-scheduler-8620 DEBUG Canceling task: 3988 / 0x59e8808
Jul 07 20:58:11-545784 util-scheduler-8620 DEBUG Adding task: 3996 / 0x59e8808
Jul 07 20:58:11-546026 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:11-546197 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:11-546377 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:11-546577 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:11-546751 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:11-546924 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:11-547121 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:11-547325 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:11-547508 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:11-547686 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:11-547874 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:11-548118 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:16-533925 util-scheduler-8620 DEBUG Checking readiness of task: 3995 / 0x46620a0
Jul 07 20:58:16-534283 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-534891 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-535088 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-535333 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-535541 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-535731 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-535921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-536114 util-scheduler-8620 DEBUG Running task: 3990 / 0x52cbfb8
Jul 07 20:58:16-536347 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:16-536602 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:58:16-536809 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:16-537009 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:16-537232 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:16-537468 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:16-537649 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:16-537870 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:16-538159 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:16-538356 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:16-538592 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:16-538799 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:16-539113 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:16-539345 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:16-539571 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:16-539754 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:16-539930 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:16-540135 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:16-540348 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:16-540571 util-scheduler-8620 DEBUG Adding task: 3997 / 0x59ee8a0
Jul 07 20:58:16-540752 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:16-540956 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:16-541133 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:16-541329 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:16-541567 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:16-541766 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:16-541943 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:16-542142 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:16-542385 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:16-542583 util-scheduler-8620 DEBUG Adding task: 3998 / 0x52cbfb8
Jul 07 20:58:16-542838 util-scheduler-8620 DEBUG Checking readiness of task: 3995 / 0x46620a0
Jul 07 20:58:16-543031 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-543221 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-543411 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-543599 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-543789 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-543977 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-544166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-544354 util-scheduler-8620 DEBUG Running task: 3997 / 0x59ee8a0
Jul 07 20:58:16-544562 util-scheduler-8620 DEBUG Adding task: 3999 / 0x59ee8a0
Jul 07 20:58:16-544782 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:16-545003 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:16-545230 util-scheduler-8620 DEBUG Adding task: 4000 / 0x46620a0
Jul 07 20:58:16-545474 util-scheduler-8620 DEBUG Checking readiness of task: 4000 / 0x46620a0
Jul 07 20:58:16-545668 util-scheduler-8620 DEBUG Checking readiness of task: 3995 / 0x46620a0
Jul 07 20:58:16-545859 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-546049 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-546240 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-546429 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-546619 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-546807 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-546996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-547187 util-scheduler-8620 DEBUG Running task: 4000 / 0x46620a0
Jul 07 20:58:16-547371 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:16-547549 util-8620 DEBUG process_notify is running
Jul 07 20:58:16-547721 util-8620 DEBUG client_notify is running
Jul 07 20:58:16-547900 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:16-548095 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:16-548286 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:16-548540 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:16-548788 util-scheduler-8620 DEBUG Checking readiness of task: 3995 / 0x46620a0
Jul 07 20:58:16-548997 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-549207 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-549413 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-549603 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-549808 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-549998 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-550186 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-550376 util-scheduler-8620 DEBUG Running task: 3995 / 0x46620a0
Jul 07 20:58:16-550778 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:16-551008 util-scheduler-8620 DEBUG Adding task: 4001 / 0x4662248
Jul 07 20:58:16-551255 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-551447 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-551637 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-551831 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-552020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-552209 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-552397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-552586 util-scheduler-8620 DEBUG Running task: 4001 / 0x4662248
Jul 07 20:58:16-552776 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:16-552971 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:16-553206 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:16-553404 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:16-553603 util-scheduler-8620 DEBUG Adding task: 4002 / 0x46620a0
Jul 07 20:58:16-553787 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:16-553990 util-scheduler-8620 DEBUG Adding task: 4003 / 0x46620a0
Jul 07 20:58:16-554230 util-scheduler-8620 DEBUG Checking readiness of task: 4003 / 0x46620a0
Jul 07 20:58:16-554423 util-scheduler-8620 DEBUG Checking readiness of task: 4002 / 0x46620a0
Jul 07 20:58:16-554614 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:16-554804 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:16-554994 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:16-555182 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:16-555373 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:16-555561 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:16-555760 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:16-555951 util-scheduler-8620 DEBUG Running task: 4002 / 0x46620a0
Jul 07 20:58:16-556134 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:16-556307 util-8620 DEBUG process_notify is running
Jul 07 20:58:16-556477 util-8620 DEBUG client_notify is running
Jul 07 20:58:16-556661 util-scheduler-8620 DEBUG Canceling task: 3999 / 0x59ee8a0
Jul 07 20:58:16-556884 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:16-557100 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:16-557351 cadet-p2p-8620 DEBUG Checking 0x60d34b0 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:16-557584 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:16-557762 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:16-557950 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:16-558231 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:16-558442 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:16-558621 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:16-558809 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:16-558997 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:16-559176 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:16-559359 util-scheduler-8620 DEBUG Canceling task: 3996 / 0x59e8808
Jul 07 20:58:16-559570 util-scheduler-8620 DEBUG Adding task: 4004 / 0x59e8808
Jul 07 20:58:16-559813 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:16-559984 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:16-560165 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:16-560365 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:16-560540 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:16-560714 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:16-560912 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:16-561116 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:16-561319 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:16-561498 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:16-561686 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:16-561933 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:21-547150 util-scheduler-8620 DEBUG Checking readiness of task: 4003 / 0x46620a0
Jul 07 20:58:21-547549 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-547747 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-548903 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-549100 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-549324 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-549518 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-549709 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-549903 util-scheduler-8620 DEBUG Running task: 3998 / 0x52cbfb8
Jul 07 20:58:21-550143 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:21-550404 cadet-tun-8620 DEBUG  kx started 10 m ago
Jul 07 20:58:21-550612 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:21-550813 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:21-551015 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:21-551250 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:21-551431 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:21-551653 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:21-551944 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:21-552142 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:21-552377 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:21-552585 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:21-552904 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:21-553105 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:21-553358 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:21-553543 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:21-553718 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:21-553925 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:21-554140 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:21-554365 util-scheduler-8620 DEBUG Adding task: 4005 / 0x59ee8a0
Jul 07 20:58:21-554546 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:21-554787 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:21-554965 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:21-555140 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:21-555378 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:21-555575 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:21-555752 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:21-555949 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:21-556193 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:21-556392 util-scheduler-8620 DEBUG Adding task: 4006 / 0x52cbfb8
Jul 07 20:58:21-556652 util-scheduler-8620 DEBUG Checking readiness of task: 4003 / 0x46620a0
Jul 07 20:58:21-556845 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-557035 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-557249 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-557441 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-557632 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-557820 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-558009 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-558198 util-scheduler-8620 DEBUG Running task: 4005 / 0x59ee8a0
Jul 07 20:58:21-558406 util-scheduler-8620 DEBUG Adding task: 4007 / 0x59ee8a0
Jul 07 20:58:21-558629 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:21-558832 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:21-559041 util-scheduler-8620 DEBUG Adding task: 4008 / 0x46620a0
Jul 07 20:58:21-559284 util-scheduler-8620 DEBUG Checking readiness of task: 4008 / 0x46620a0
Jul 07 20:58:21-559479 util-scheduler-8620 DEBUG Checking readiness of task: 4003 / 0x46620a0
Jul 07 20:58:21-559668 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-559858 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-560048 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-560237 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-560427 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-560616 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-560806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-560997 util-scheduler-8620 DEBUG Running task: 4008 / 0x46620a0
Jul 07 20:58:21-561181 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:21-561391 util-8620 DEBUG process_notify is running
Jul 07 20:58:21-561563 util-8620 DEBUG client_notify is running
Jul 07 20:58:21-561743 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:21-561938 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:21-562129 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:21-562387 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:21-562635 util-scheduler-8620 DEBUG Checking readiness of task: 4003 / 0x46620a0
Jul 07 20:58:21-562829 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-563033 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-563223 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-563413 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-563602 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-563791 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-563979 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-564185 util-scheduler-8620 DEBUG Running task: 4003 / 0x46620a0
Jul 07 20:58:21-564597 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:21-564826 util-scheduler-8620 DEBUG Adding task: 4009 / 0x4662248
Jul 07 20:58:21-565074 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-565291 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-565483 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-565674 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-565864 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-566052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-566241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-566433 util-scheduler-8620 DEBUG Running task: 4009 / 0x4662248
Jul 07 20:58:21-566624 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:21-566820 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:21-567037 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:21-567234 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:21-567433 util-scheduler-8620 DEBUG Adding task: 4010 / 0x46620a0
Jul 07 20:58:21-567619 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:21-567822 util-scheduler-8620 DEBUG Adding task: 4011 / 0x46620a0
Jul 07 20:58:21-568063 util-scheduler-8620 DEBUG Checking readiness of task: 4011 / 0x46620a0
Jul 07 20:58:21-568254 util-scheduler-8620 DEBUG Checking readiness of task: 4010 / 0x46620a0
Jul 07 20:58:21-568446 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:21-568636 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:21-568825 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:21-569015 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:21-569228 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:21-569421 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:21-569609 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:21-569800 util-scheduler-8620 DEBUG Running task: 4010 / 0x46620a0
Jul 07 20:58:21-569983 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:21-570156 util-8620 DEBUG process_notify is running
Jul 07 20:58:21-570326 util-8620 DEBUG client_notify is running
Jul 07 20:58:21-570513 util-scheduler-8620 DEBUG Canceling task: 4007 / 0x59ee8a0
Jul 07 20:58:21-570734 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:21-570951 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:21-571182 cadet-p2p-8620 DEBUG Checking 0x60d69d8 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:21-571415 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:21-571702 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:21-571891 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:21-572176 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:21-572372 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:21-572551 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:21-572739 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:21-572927 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:21-573105 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:21-573318 util-scheduler-8620 DEBUG Canceling task: 4004 / 0x59e8808
Jul 07 20:58:21-573532 util-scheduler-8620 DEBUG Adding task: 4012 / 0x59e8808
Jul 07 20:58:21-573775 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:21-573964 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:21-574146 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:21-574347 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:21-574523 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:21-574697 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:21-574896 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:21-575100 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:21-575284 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:21-575462 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:21-575651 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:21-575899 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:26-561536 util-scheduler-8620 DEBUG Checking readiness of task: 4011 / 0x46620a0
Jul 07 20:58:26-561924 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-562698 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-563146 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-563349 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-563544 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-563736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-563926 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-564120 util-scheduler-8620 DEBUG Running task: 4006 / 0x52cbfb8
Jul 07 20:58:26-564360 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:26-564620 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:26-564827 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:26-565031 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:26-565258 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:26-565499 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:26-565680 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:26-565902 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:26-566194 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:26-566392 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:26-566629 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:26-566839 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:26-567157 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:26-567358 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:26-567585 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:26-567768 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:26-567944 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:26-568150 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:26-568365 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:26-568591 util-scheduler-8620 DEBUG Adding task: 4013 / 0x59ee8a0
Jul 07 20:58:26-568771 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:26-568974 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:26-569151 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:26-569348 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:26-569587 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:26-569785 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:26-569962 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:26-570161 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:26-570404 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:26-570602 util-scheduler-8620 DEBUG Adding task: 4014 / 0x52cbfb8
Jul 07 20:58:26-570915 util-scheduler-8620 DEBUG Checking readiness of task: 4011 / 0x46620a0
Jul 07 20:58:26-571110 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-571301 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-571491 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-571681 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-571870 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-572059 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-572248 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-572437 util-scheduler-8620 DEBUG Running task: 4013 / 0x59ee8a0
Jul 07 20:58:26-572645 util-scheduler-8620 DEBUG Adding task: 4015 / 0x59ee8a0
Jul 07 20:58:26-572866 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:26-573069 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:26-573301 util-scheduler-8620 DEBUG Adding task: 4016 / 0x46620a0
Jul 07 20:58:26-573546 util-scheduler-8620 DEBUG Checking readiness of task: 4016 / 0x46620a0
Jul 07 20:58:26-573741 util-scheduler-8620 DEBUG Checking readiness of task: 4011 / 0x46620a0
Jul 07 20:58:26-573931 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-574121 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-574310 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-574500 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-574689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-574879 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-575070 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-575261 util-scheduler-8620 DEBUG Running task: 4016 / 0x46620a0
Jul 07 20:58:26-575446 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:26-575623 util-8620 DEBUG process_notify is running
Jul 07 20:58:26-575796 util-8620 DEBUG client_notify is running
Jul 07 20:58:26-575974 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:26-576169 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:26-576360 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:26-576617 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:26-576865 util-scheduler-8620 DEBUG Checking readiness of task: 4011 / 0x46620a0
Jul 07 20:58:26-577059 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-577272 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-577463 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-577654 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-577844 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-578034 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-578222 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-578412 util-scheduler-8620 DEBUG Running task: 4011 / 0x46620a0
Jul 07 20:58:26-578821 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:26-579051 util-scheduler-8620 DEBUG Adding task: 4017 / 0x4662248
Jul 07 20:58:26-579298 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-579492 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-579682 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-579873 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-580079 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-580269 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-580458 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-580716 util-scheduler-8620 DEBUG Running task: 4017 / 0x4662248
Jul 07 20:58:26-580985 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:26-581186 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:26-581426 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:26-581624 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:26-581822 util-scheduler-8620 DEBUG Adding task: 4018 / 0x46620a0
Jul 07 20:58:26-582007 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:26-582211 util-scheduler-8620 DEBUG Adding task: 4019 / 0x46620a0
Jul 07 20:58:26-582452 util-scheduler-8620 DEBUG Checking readiness of task: 4019 / 0x46620a0
Jul 07 20:58:26-582644 util-scheduler-8620 DEBUG Checking readiness of task: 4018 / 0x46620a0
Jul 07 20:58:26-582835 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:26-583024 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:26-583214 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:26-583403 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:26-583593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:26-583784 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:26-583973 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:26-584163 util-scheduler-8620 DEBUG Running task: 4018 / 0x46620a0
Jul 07 20:58:26-584346 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:26-584521 util-8620 DEBUG process_notify is running
Jul 07 20:58:26-584690 util-8620 DEBUG client_notify is running
Jul 07 20:58:26-584875 util-scheduler-8620 DEBUG Canceling task: 4015 / 0x59ee8a0
Jul 07 20:58:26-585101 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:26-585337 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:26-585569 cadet-p2p-8620 DEBUG Checking 0x60d9ee0 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:26-585804 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:26-585982 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:26-586169 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:26-586453 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:26-586649 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:26-586828 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:26-587016 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:26-587204 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:26-587384 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:26-587568 util-scheduler-8620 DEBUG Canceling task: 4012 / 0x59e8808
Jul 07 20:58:26-587779 util-scheduler-8620 DEBUG Adding task: 4020 / 0x59e8808
Jul 07 20:58:26-588022 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:26-588194 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:26-588375 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:26-588574 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:26-588749 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:26-588923 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:26-589122 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:26-589348 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:26-589532 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:26-589712 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:26-589917 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:26-590165 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:31-573372 util-scheduler-8620 DEBUG Checking readiness of task: 4019 / 0x46620a0
Jul 07 20:58:31-573759 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-574386 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-574626 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-574856 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-575069 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-575260 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-575450 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-575644 util-scheduler-8620 DEBUG Running task: 4014 / 0x52cbfb8
Jul 07 20:58:31-575893 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:31-576154 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:31-576360 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:31-576563 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:31-576766 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:31-577001 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:31-577182 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:31-577427 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:31-577717 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:31-577914 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:31-578151 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:31-578358 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:31-578675 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:31-578876 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:31-579100 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:31-579285 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:31-579460 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:31-579667 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:31-579881 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:31-580105 util-scheduler-8620 DEBUG Adding task: 4021 / 0x59ee8a0
Jul 07 20:58:31-580285 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:31-580488 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:31-580665 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:31-580840 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:31-581077 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:31-581293 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:31-581471 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:31-581670 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:31-581912 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:31-582108 util-scheduler-8620 DEBUG Adding task: 4022 / 0x52cbfb8
Jul 07 20:58:31-582366 util-scheduler-8620 DEBUG Checking readiness of task: 4019 / 0x46620a0
Jul 07 20:58:31-582559 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-582750 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-582940 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-583130 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-583319 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-583508 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-583728 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-583919 util-scheduler-8620 DEBUG Running task: 4021 / 0x59ee8a0
Jul 07 20:58:31-584126 util-scheduler-8620 DEBUG Adding task: 4023 / 0x59ee8a0
Jul 07 20:58:31-584348 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:31-584552 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:31-584759 util-scheduler-8620 DEBUG Adding task: 4024 / 0x46620a0
Jul 07 20:58:31-585002 util-scheduler-8620 DEBUG Checking readiness of task: 4024 / 0x46620a0
Jul 07 20:58:31-585216 util-scheduler-8620 DEBUG Checking readiness of task: 4019 / 0x46620a0
Jul 07 20:58:31-585408 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-585599 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-585788 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-585982 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-586172 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-586361 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-586549 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-586741 util-scheduler-8620 DEBUG Running task: 4024 / 0x46620a0
Jul 07 20:58:31-586925 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:31-587103 util-8620 DEBUG process_notify is running
Jul 07 20:58:31-587275 util-8620 DEBUG client_notify is running
Jul 07 20:58:31-587455 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:31-587649 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:31-587840 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:31-588096 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:31-588343 util-scheduler-8620 DEBUG Checking readiness of task: 4019 / 0x46620a0
Jul 07 20:58:31-588537 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-588727 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-588917 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-589107 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-589316 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-589506 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-589694 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-589884 util-scheduler-8620 DEBUG Running task: 4019 / 0x46620a0
Jul 07 20:58:31-590288 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:31-590518 util-scheduler-8620 DEBUG Adding task: 4025 / 0x4662248
Jul 07 20:58:31-590765 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-590958 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-591149 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-591338 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-591528 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-591717 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-591906 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-592095 util-scheduler-8620 DEBUG Running task: 4025 / 0x4662248
Jul 07 20:58:31-592283 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:31-592478 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:31-592693 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:31-592905 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:31-593103 util-scheduler-8620 DEBUG Adding task: 4026 / 0x46620a0
Jul 07 20:58:31-593308 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:31-593513 util-scheduler-8620 DEBUG Adding task: 4027 / 0x46620a0
Jul 07 20:58:31-593753 util-scheduler-8620 DEBUG Checking readiness of task: 4027 / 0x46620a0
Jul 07 20:58:31-593946 util-scheduler-8620 DEBUG Checking readiness of task: 4026 / 0x46620a0
Jul 07 20:58:31-594137 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:31-594327 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:31-594520 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:31-594709 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:31-594898 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:31-595085 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:31-595273 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:31-595464 util-scheduler-8620 DEBUG Running task: 4026 / 0x46620a0
Jul 07 20:58:31-595647 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:31-595821 util-8620 DEBUG process_notify is running
Jul 07 20:58:31-595991 util-8620 DEBUG client_notify is running
Jul 07 20:58:31-596177 util-scheduler-8620 DEBUG Canceling task: 4023 / 0x59ee8a0
Jul 07 20:58:31-596399 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:31-596614 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:31-596845 cadet-p2p-8620 DEBUG Checking 0x60dd898 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:31-597089 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:31-597288 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:31-597475 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:31-597757 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:31-597952 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:31-598131 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:31-598318 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:31-598505 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:31-598683 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:31-598867 util-scheduler-8620 DEBUG Canceling task: 4020 / 0x59e8808
Jul 07 20:58:31-599078 util-scheduler-8620 DEBUG Adding task: 4028 / 0x59e8808
Jul 07 20:58:31-599320 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:31-599490 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:31-599671 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:31-599870 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:31-600045 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:31-600219 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:31-600487 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:31-600774 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:31-600960 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:31-601138 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:31-601349 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:31-601597 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:36-587248 util-scheduler-8620 DEBUG Checking readiness of task: 4027 / 0x46620a0
Jul 07 20:58:36-587628 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-588283 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-588514 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-588751 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-588998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-589209 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-589402 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-589595 util-scheduler-8620 DEBUG Running task: 4022 / 0x52cbfb8
Jul 07 20:58:36-589830 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:36-590086 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:36-590293 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:36-590493 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:36-590695 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:36-590929 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:36-591110 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:36-591330 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:36-591619 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:36-591817 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:36-592055 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:36-592262 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:36-592579 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:36-592779 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:36-593004 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:36-593207 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:36-593385 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:36-593592 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:36-593807 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:36-594032 util-scheduler-8620 DEBUG Adding task: 4029 / 0x59ee8a0
Jul 07 20:58:36-594212 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:36-594415 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:36-594592 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:36-594767 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:36-595005 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:36-595202 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:36-595380 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:36-595579 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:36-595821 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:36-596018 util-scheduler-8620 DEBUG Adding task: 4030 / 0x52cbfb8
Jul 07 20:58:36-596274 util-scheduler-8620 DEBUG Checking readiness of task: 4027 / 0x46620a0
Jul 07 20:58:36-596467 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-596657 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-596847 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-597037 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-597249 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-597440 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-597629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-597819 util-scheduler-8620 DEBUG Running task: 4029 / 0x59ee8a0
Jul 07 20:58:36-598026 util-scheduler-8620 DEBUG Adding task: 4031 / 0x59ee8a0
Jul 07 20:58:36-598246 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:36-598448 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:36-598654 util-scheduler-8620 DEBUG Adding task: 4032 / 0x46620a0
Jul 07 20:58:36-598931 util-scheduler-8620 DEBUG Checking readiness of task: 4032 / 0x46620a0
Jul 07 20:58:36-599125 util-scheduler-8620 DEBUG Checking readiness of task: 4027 / 0x46620a0
Jul 07 20:58:36-599338 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-599529 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-599719 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-599909 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-600099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-600288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-600477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-600668 util-scheduler-8620 DEBUG Running task: 4032 / 0x46620a0
Jul 07 20:58:36-600853 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:36-601031 util-8620 DEBUG process_notify is running
Jul 07 20:58:36-601224 util-8620 DEBUG client_notify is running
Jul 07 20:58:36-601404 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:36-601600 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:36-601792 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:36-602077 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:36-602326 util-scheduler-8620 DEBUG Checking readiness of task: 4027 / 0x46620a0
Jul 07 20:58:36-602520 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-602711 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-602900 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-603091 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-603280 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-603469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-603658 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-603848 util-scheduler-8620 DEBUG Running task: 4027 / 0x46620a0
Jul 07 20:58:36-604251 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:36-604481 util-scheduler-8620 DEBUG Adding task: 4033 / 0x4662248
Jul 07 20:58:36-604740 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-604934 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-605127 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-605340 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-605531 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-605719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-605909 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-606098 util-scheduler-8620 DEBUG Running task: 4033 / 0x4662248
Jul 07 20:58:36-606288 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:36-606483 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:36-606700 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:36-606897 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:36-607099 util-scheduler-8620 DEBUG Adding task: 4034 / 0x46620a0
Jul 07 20:58:36-607284 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:36-607487 util-scheduler-8620 DEBUG Adding task: 4035 / 0x46620a0
Jul 07 20:58:36-607727 util-scheduler-8620 DEBUG Checking readiness of task: 4035 / 0x46620a0
Jul 07 20:58:36-607919 util-scheduler-8620 DEBUG Checking readiness of task: 4034 / 0x46620a0
Jul 07 20:58:36-608110 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:36-608317 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:36-608508 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:36-608698 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:36-608888 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:36-609076 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:36-609285 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:36-609475 util-scheduler-8620 DEBUG Running task: 4034 / 0x46620a0
Jul 07 20:58:36-609659 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:36-609835 util-8620 DEBUG process_notify is running
Jul 07 20:58:36-610003 util-8620 DEBUG client_notify is running
Jul 07 20:58:36-610187 util-scheduler-8620 DEBUG Canceling task: 4031 / 0x59ee8a0
Jul 07 20:58:36-610410 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:36-610626 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:36-610858 cadet-p2p-8620 DEBUG Checking 0x60d6048 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:36-611091 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:36-611269 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:36-611456 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:36-611738 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:36-611933 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:36-612111 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:36-612298 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:36-612486 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:36-612665 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:36-612849 util-scheduler-8620 DEBUG Canceling task: 4028 / 0x59e8808
Jul 07 20:58:36-613060 util-scheduler-8620 DEBUG Adding task: 4036 / 0x59e8808
Jul 07 20:58:36-613322 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:36-613494 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:36-613674 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:36-613875 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:36-614049 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:36-614223 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:36-614420 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:36-614624 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:36-614808 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:36-614985 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:36-615174 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:36-615420 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:41-601155 util-scheduler-8620 DEBUG Checking readiness of task: 4035 / 0x46620a0
Jul 07 20:58:41-601547 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-602036 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-602239 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-602502 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-602713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-602904 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-603094 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-603287 util-scheduler-8620 DEBUG Running task: 4030 / 0x52cbfb8
Jul 07 20:58:41-603519 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:41-603778 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:41-603984 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:41-604183 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:41-604414 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:41-604647 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:41-604828 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:41-605048 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:41-605359 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:41-605557 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:41-605794 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:41-606001 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:41-606317 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:41-606518 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:41-606744 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:41-606927 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:41-607103 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:41-607307 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:41-607521 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:41-607744 util-scheduler-8620 DEBUG Adding task: 4037 / 0x59ee8a0
Jul 07 20:58:41-607925 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:41-608128 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:41-608306 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:41-608480 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:41-608718 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:41-608914 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:41-609091 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:41-609310 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:41-609553 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:41-609750 util-scheduler-8620 DEBUG Adding task: 4038 / 0x52cbfb8
Jul 07 20:58:41-610004 util-scheduler-8620 DEBUG Checking readiness of task: 4035 / 0x46620a0
Jul 07 20:58:41-610197 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-610387 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-610578 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-610768 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-610957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-611146 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-611336 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-611525 util-scheduler-8620 DEBUG Running task: 4037 / 0x59ee8a0
Jul 07 20:58:41-611746 util-scheduler-8620 DEBUG Adding task: 4039 / 0x59ee8a0
Jul 07 20:58:41-611965 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:41-612167 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:41-612374 util-scheduler-8620 DEBUG Adding task: 4040 / 0x46620a0
Jul 07 20:58:41-612618 util-scheduler-8620 DEBUG Checking readiness of task: 4040 / 0x46620a0
Jul 07 20:58:41-612811 util-scheduler-8620 DEBUG Checking readiness of task: 4035 / 0x46620a0
Jul 07 20:58:41-613001 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-613208 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-613399 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-613589 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-613779 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-613967 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-614156 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-614363 util-scheduler-8620 DEBUG Running task: 4040 / 0x46620a0
Jul 07 20:58:41-614549 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:41-614726 util-8620 DEBUG process_notify is running
Jul 07 20:58:41-614898 util-8620 DEBUG client_notify is running
Jul 07 20:58:41-615075 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:41-615269 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:41-615460 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:41-615717 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:41-615966 util-scheduler-8620 DEBUG Checking readiness of task: 4035 / 0x46620a0
Jul 07 20:58:41-616160 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-616351 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-616540 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-616730 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-616920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-617108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-617319 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-617509 util-scheduler-8620 DEBUG Running task: 4035 / 0x46620a0
Jul 07 20:58:41-617914 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:41-618141 util-scheduler-8620 DEBUG Adding task: 4041 / 0x4662248
Jul 07 20:58:41-618391 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-618584 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-618775 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-618965 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-619156 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-619346 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-619535 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-619725 util-scheduler-8620 DEBUG Running task: 4041 / 0x4662248
Jul 07 20:58:41-619915 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:41-620110 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:41-620325 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:41-620521 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:41-620718 util-scheduler-8620 DEBUG Adding task: 4042 / 0x46620a0
Jul 07 20:58:41-620901 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:41-621127 util-scheduler-8620 DEBUG Adding task: 4043 / 0x46620a0
Jul 07 20:58:41-621391 util-scheduler-8620 DEBUG Checking readiness of task: 4043 / 0x46620a0
Jul 07 20:58:41-621585 util-scheduler-8620 DEBUG Checking readiness of task: 4042 / 0x46620a0
Jul 07 20:58:41-621777 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:41-621967 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:41-622158 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:41-622348 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:41-622538 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:41-622726 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:41-622914 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:41-623105 util-scheduler-8620 DEBUG Running task: 4042 / 0x46620a0
Jul 07 20:58:41-623289 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:41-623479 util-8620 DEBUG process_notify is running
Jul 07 20:58:41-623649 util-8620 DEBUG client_notify is running
Jul 07 20:58:41-623833 util-scheduler-8620 DEBUG Canceling task: 4039 / 0x59ee8a0
Jul 07 20:58:41-624055 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:41-624270 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:41-624501 cadet-p2p-8620 DEBUG Checking 0x60e4300 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:41-624734 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:41-624913 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:41-625098 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:41-625401 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:41-625594 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:41-625773 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:41-625959 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:41-626147 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:41-626325 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:41-626508 util-scheduler-8620 DEBUG Canceling task: 4036 / 0x59e8808
Jul 07 20:58:41-626719 util-scheduler-8620 DEBUG Adding task: 4044 / 0x59e8808
Jul 07 20:58:41-626961 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:41-627131 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:41-627312 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:41-627512 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:41-627686 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:41-627860 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:41-628058 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:41-628267 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:41-628451 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:41-628629 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:41-628817 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:41-629063 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:46-614887 util-scheduler-8620 DEBUG Checking readiness of task: 4043 / 0x46620a0
Jul 07 20:58:46-615263 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-616538 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-616908 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-617104 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-617333 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-617525 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-617715 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-617909 util-scheduler-8620 DEBUG Running task: 4038 / 0x52cbfb8
Jul 07 20:58:46-618147 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:46-618407 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:46-618614 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:46-618815 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:46-619017 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:46-619256 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:46-619438 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:46-619658 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:46-619964 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:46-620163 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:46-620401 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:46-620609 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:46-620965 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:46-621169 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:46-621423 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:46-621608 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:46-621784 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:46-621991 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:46-622206 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:46-622432 util-scheduler-8620 DEBUG Adding task: 4045 / 0x59ee8a0
Jul 07 20:58:46-622612 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:46-622816 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:46-622992 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:46-623166 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:46-623405 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:46-623601 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:46-623778 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:46-623977 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:46-624221 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:46-624418 util-scheduler-8620 DEBUG Adding task: 4046 / 0x52cbfb8
Jul 07 20:58:46-624683 util-scheduler-8620 DEBUG Checking readiness of task: 4043 / 0x46620a0
Jul 07 20:58:46-624876 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-625067 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-625283 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-625474 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-625663 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-625852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-626040 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-626229 util-scheduler-8620 DEBUG Running task: 4045 / 0x59ee8a0
Jul 07 20:58:46-626437 util-scheduler-8620 DEBUG Adding task: 4047 / 0x59ee8a0
Jul 07 20:58:46-626659 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:46-626862 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:46-627070 util-scheduler-8620 DEBUG Adding task: 4048 / 0x46620a0
Jul 07 20:58:46-627317 util-scheduler-8620 DEBUG Checking readiness of task: 4048 / 0x46620a0
Jul 07 20:58:46-627511 util-scheduler-8620 DEBUG Checking readiness of task: 4043 / 0x46620a0
Jul 07 20:58:46-627702 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-627891 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-628081 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-628271 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-628461 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-628649 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-628838 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-629028 util-scheduler-8620 DEBUG Running task: 4048 / 0x46620a0
Jul 07 20:58:46-629213 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:46-629421 util-8620 DEBUG process_notify is running
Jul 07 20:58:46-629594 util-8620 DEBUG client_notify is running
Jul 07 20:58:46-629774 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:46-629969 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:46-630161 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:46-630418 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:46-630685 util-scheduler-8620 DEBUG Checking readiness of task: 4043 / 0x46620a0
Jul 07 20:58:46-630880 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-631070 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-631260 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-631451 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-631640 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-631828 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-632017 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-632207 util-scheduler-8620 DEBUG Running task: 4043 / 0x46620a0
Jul 07 20:58:46-632617 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:46-632944 util-scheduler-8620 DEBUG Adding task: 4049 / 0x4662248
Jul 07 20:58:46-633220 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-633416 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-633606 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-633796 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-633987 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-634175 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-634364 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-634553 util-scheduler-8620 DEBUG Running task: 4049 / 0x4662248
Jul 07 20:58:46-634744 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:46-634939 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:46-635157 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:46-635354 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:46-635551 util-scheduler-8620 DEBUG Adding task: 4050 / 0x46620a0
Jul 07 20:58:46-635735 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:46-635938 util-scheduler-8620 DEBUG Adding task: 4051 / 0x46620a0
Jul 07 20:58:46-636178 util-scheduler-8620 DEBUG Checking readiness of task: 4051 / 0x46620a0
Jul 07 20:58:46-636370 util-scheduler-8620 DEBUG Checking readiness of task: 4050 / 0x46620a0
Jul 07 20:58:46-636562 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:46-636752 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:46-636942 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:46-637132 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:46-637348 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:46-637538 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:46-637725 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:46-637916 util-scheduler-8620 DEBUG Running task: 4050 / 0x46620a0
Jul 07 20:58:46-638099 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:46-638273 util-8620 DEBUG process_notify is running
Jul 07 20:58:46-638441 util-8620 DEBUG client_notify is running
Jul 07 20:58:46-638625 util-scheduler-8620 DEBUG Canceling task: 4047 / 0x59ee8a0
Jul 07 20:58:46-638848 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:46-639065 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:46-639299 cadet-p2p-8620 DEBUG Checking 0x60e7a08 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:46-639533 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:46-639711 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:46-639915 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:46-640201 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:46-640397 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:46-640576 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:46-640764 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:46-640952 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:46-641131 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:46-641352 util-scheduler-8620 DEBUG Canceling task: 4044 / 0x59e8808
Jul 07 20:58:46-641563 util-scheduler-8620 DEBUG Adding task: 4052 / 0x59e8808
Jul 07 20:58:46-641807 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:46-641977 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:46-642159 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:46-642359 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:46-642534 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:46-642707 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:46-642906 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:46-643111 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:46-643294 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:46-643472 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:46-643660 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:46-643907 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:51-629568 util-scheduler-8620 DEBUG Checking readiness of task: 4051 / 0x46620a0
Jul 07 20:58:51-629966 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-630700 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-631133 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-631336 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-631530 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-631722 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-631913 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-632110 util-scheduler-8620 DEBUG Running task: 4046 / 0x52cbfb8
Jul 07 20:58:51-632348 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:51-632606 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:51-632813 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:51-633014 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:51-633239 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:51-633479 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:51-633661 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:51-633883 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:51-634174 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:51-634372 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:51-634610 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:51-634819 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:51-635138 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:51-635339 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:51-635565 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:51-635749 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:51-635926 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:51-636131 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:51-636346 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:51-636571 util-scheduler-8620 DEBUG Adding task: 4053 / 0x59ee8a0
Jul 07 20:58:51-636790 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:51-636995 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:51-637172 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:51-637368 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:51-637607 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:51-637803 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:51-637980 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:51-638179 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:51-638421 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:51-638619 util-scheduler-8620 DEBUG Adding task: 4054 / 0x52cbfb8
Jul 07 20:58:51-638883 util-scheduler-8620 DEBUG Checking readiness of task: 4051 / 0x46620a0
Jul 07 20:58:51-639077 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-639267 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-639455 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-639645 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-639835 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-640023 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-640212 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-640402 util-scheduler-8620 DEBUG Running task: 4053 / 0x59ee8a0
Jul 07 20:58:51-640609 util-scheduler-8620 DEBUG Adding task: 4055 / 0x59ee8a0
Jul 07 20:58:51-640833 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:51-641036 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:51-641262 util-scheduler-8620 DEBUG Adding task: 4056 / 0x46620a0
Jul 07 20:58:51-641508 util-scheduler-8620 DEBUG Checking readiness of task: 4056 / 0x46620a0
Jul 07 20:58:51-641702 util-scheduler-8620 DEBUG Checking readiness of task: 4051 / 0x46620a0
Jul 07 20:58:51-641892 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-642082 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-642271 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-642461 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-642649 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-642839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-643027 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-643218 util-scheduler-8620 DEBUG Running task: 4056 / 0x46620a0
Jul 07 20:58:51-643403 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:51-643581 util-8620 DEBUG process_notify is running
Jul 07 20:58:51-643755 util-8620 DEBUG client_notify is running
Jul 07 20:58:51-643933 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:51-644128 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:51-644319 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:51-644575 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:51-644822 util-scheduler-8620 DEBUG Checking readiness of task: 4051 / 0x46620a0
Jul 07 20:58:51-645016 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-645229 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-645421 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-645610 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-645799 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-646004 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-646193 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-646383 util-scheduler-8620 DEBUG Running task: 4051 / 0x46620a0
Jul 07 20:58:51-646792 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:51-647021 util-scheduler-8620 DEBUG Adding task: 4057 / 0x4662248
Jul 07 20:58:51-647268 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-647460 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-647652 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-647842 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-648031 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-648220 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-648409 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-648598 util-scheduler-8620 DEBUG Running task: 4057 / 0x4662248
Jul 07 20:58:51-648789 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:51-648997 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:51-649232 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:51-649430 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:51-649627 util-scheduler-8620 DEBUG Adding task: 4058 / 0x46620a0
Jul 07 20:58:51-649812 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:51-650015 util-scheduler-8620 DEBUG Adding task: 4059 / 0x46620a0
Jul 07 20:58:51-650275 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:51-650469 util-scheduler-8620 DEBUG Checking readiness of task: 4058 / 0x46620a0
Jul 07 20:58:51-650660 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:51-650853 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:51-651043 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:51-651233 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:51-651422 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:51-651610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:51-651798 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:51-651988 util-scheduler-8620 DEBUG Running task: 4058 / 0x46620a0
Jul 07 20:58:51-652172 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:51-652346 util-8620 DEBUG process_notify is running
Jul 07 20:58:51-652515 util-8620 DEBUG client_notify is running
Jul 07 20:58:51-652699 util-scheduler-8620 DEBUG Canceling task: 4055 / 0x59ee8a0
Jul 07 20:58:51-652922 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:51-653138 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:51-653389 cadet-p2p-8620 DEBUG Checking 0x60eb2c0 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:51-653623 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:51-653800 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:51-653987 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:51-654268 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:51-654463 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:51-654641 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:51-654829 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:51-655017 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:51-655196 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:51-655378 util-scheduler-8620 DEBUG Canceling task: 4052 / 0x59e8808
Jul 07 20:58:51-655590 util-scheduler-8620 DEBUG Adding task: 4060 / 0x59e8808
Jul 07 20:58:51-655847 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:51-656019 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:51-656199 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:51-656399 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:51-656574 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:51-656748 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:51-656947 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:51-657152 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:51-657355 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:51-657532 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:51-657723 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:51-657969 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:56-040542 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-040938 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-041140 util-scheduler-8620 DEBUG Checking readiness of task: 3869 / 0x465ee60
Jul 07 20:58:56-041376 util-scheduler-8620 DEBUG Checking readiness of task: 3074 / 0x4663d68
Jul 07 20:58:56-041573 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-041776 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-041968 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-042163 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-042362 util-scheduler-8620 DEBUG Running task: 3074 / 0x4663d68
Jul 07 20:58:56-042793 util-8620 DEBUG receive_ready read 1614/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:58:56-043125 util-scheduler-8620 DEBUG Adding task: 4061 / 0x4663f10
Jul 07 20:58:56-043344 util-scheduler-8620 DEBUG Running task: 3869 / 0x465ee60
Jul 07 20:58:56-043753 util-8620 DEBUG receive_ready read 1734/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:58:56-043988 util-scheduler-8620 DEBUG Adding task: 4062 / 0x465f008
Jul 07 20:58:56-044258 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-044454 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-044648 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-044841 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-045036 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-045258 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-045454 util-scheduler-8620 DEBUG Running task: 4062 / 0x465f008
Jul 07 20:58:56-045650 util-8620 DEBUG Received message of type 332 and size 578 from peerinfo service.
Jul 07 20:58:56-045905 nse-api-8620 DEBUG Received information about peer `GN10' from peerinfo database
Jul 07 20:58:56-046209 cadet-hll-8620 DEBUG  hello for GN10 (538 bytes), expires on Tue Jul 08 08:58:56 2014
Jul 07 20:58:56-046462 cadet-p2p-8620 DEBUG set hello for GN10
Jul 07 20:58:56-047132 cadet-p2p-8620 DEBUG  merge into 0x60e6868 (538 bytes)
Jul 07 20:58:56-047530 cadet-hll-8620 DEBUG  updated mine to 0x60e6868
Jul 07 20:58:56-047754 util-scheduler-8620 DEBUG Adding task: 4063 / 0x465f008
Jul 07 20:58:56-047956 util-scheduler-8620 DEBUG Running task: 4061 / 0x4663f10
Jul 07 20:58:56-048149 util-8620 DEBUG Received message of type 17 and size 538 from transport service.
Jul 07 20:58:56-048384 util-scheduler-8620 DEBUG Adding task: 4064 / 0x4663f10
Jul 07 20:58:56-048713 transport-api-8620 DEBUG Receiving (my own) `HELLO' message, I am `GN10'.
Jul 07 20:58:56-049425 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-049658 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-049856 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-050051 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-050243 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-050436 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-050628 util-scheduler-8620 DEBUG Running task: 4064 / 0x4663f10
Jul 07 20:58:56-050821 util-8620 DEBUG Received message of type 17 and size 538 from transport service.
Jul 07 20:58:56-051046 util-scheduler-8620 DEBUG Adding task: 4065 / 0x4663f10
Jul 07 20:58:56-051261 transport-api-8620 DEBUG Receiving (my own) `HELLO' message, I am `GN10'.
Jul 07 20:58:56-051485 util-scheduler-8620 DEBUG Running task: 4063 / 0x465f008
Jul 07 20:58:56-051679 util-8620 DEBUG Received message of type 332 and size 578 from peerinfo service.
Jul 07 20:58:56-051905 nse-api-8620 DEBUG Received information about peer `GN10' from peerinfo database
Jul 07 20:58:56-052186 cadet-hll-8620 DEBUG  hello for GN10 (538 bytes), expires on Tue Jul 08 08:58:56 2014
Jul 07 20:58:56-052406 cadet-p2p-8620 DEBUG set hello for GN10
Jul 07 20:58:56-053052 cadet-p2p-8620 DEBUG  merge into 0x60dc8e8 (538 bytes)
Jul 07 20:58:56-053301 cadet-hll-8620 DEBUG  updated mine to 0x60dc8e8
Jul 07 20:58:56-053515 util-scheduler-8620 DEBUG Adding task: 4066 / 0x465f008
Jul 07 20:58:56-053753 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-053948 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-054142 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-054335 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-054525 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-054717 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-054908 util-scheduler-8620 DEBUG Running task: 4066 / 0x465f008
Jul 07 20:58:56-055103 util-8620 DEBUG Received message of type 332 and size 578 from peerinfo service.
Jul 07 20:58:56-055323 nse-api-8620 DEBUG Received information about peer `GN10' from peerinfo database
Jul 07 20:58:56-055604 cadet-hll-8620 DEBUG  hello for GN10 (538 bytes), expires on Tue Jul 08 08:58:56 2014
Jul 07 20:58:56-055820 cadet-p2p-8620 DEBUG set hello for GN10
Jul 07 20:58:56-056450 cadet-p2p-8620 DEBUG  merge into 0x60cdc68 (538 bytes)
Jul 07 20:58:56-056671 cadet-hll-8620 DEBUG  updated mine to 0x60cdc68
Jul 07 20:58:56-056859 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:56-057073 util-scheduler-8620 DEBUG Adding task: 4067 / 0x465ee60
Jul 07 20:58:56-057293 util-scheduler-8620 DEBUG Running task: 4065 / 0x4663f10
Jul 07 20:58:56-057487 util-8620 DEBUG Received message of type 17 and size 538 from transport service.
Jul 07 20:58:56-057680 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:56-057878 util-scheduler-8620 DEBUG Adding task: 4068 / 0x4663d68
Jul 07 20:58:56-058092 transport-api-8620 DEBUG Receiving (my own) `HELLO' message, I am `GN10'.
Jul 07 20:58:56-639303 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-639565 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-640385 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-641029 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-641253 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-641451 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-641644 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-641836 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-642034 util-scheduler-8620 DEBUG Running task: 4054 / 0x52cbfb8
Jul 07 20:58:56-642300 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:58:56-642560 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:58:56-642769 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:58:56-642971 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:58:56-643176 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:58:56-643413 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:58:56-643594 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:58:56-643816 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:58:56-644108 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:58:56-644307 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:58:56-644544 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:58:56-644753 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:58:56-645071 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:58:56-645294 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:58:56-645520 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:58:56-645706 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:58:56-645882 cadet-con-8620 DEBUG  sendable
Jul 07 20:58:56-646089 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:58:56-646304 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:58:56-646531 util-scheduler-8620 DEBUG Adding task: 4069 / 0x59ee8a0
Jul 07 20:58:56-646712 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:58:56-646916 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:56-647092 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:58:56-647268 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:58:56-647509 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:58:56-647704 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:58:56-647883 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:58:56-648081 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:56-648325 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:58:56-648523 util-scheduler-8620 DEBUG Adding task: 4070 / 0x52cbfb8
Jul 07 20:58:56-648788 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-648981 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-649171 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-649382 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-649572 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-649762 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-649950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-650141 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-650329 util-scheduler-8620 DEBUG Running task: 4069 / 0x59ee8a0
Jul 07 20:58:56-650537 util-scheduler-8620 DEBUG Adding task: 4071 / 0x59ee8a0
Jul 07 20:58:56-650759 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:58:56-650962 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:56-651170 util-scheduler-8620 DEBUG Adding task: 4072 / 0x46620a0
Jul 07 20:58:56-651434 util-scheduler-8620 DEBUG Checking readiness of task: 4072 / 0x46620a0
Jul 07 20:58:56-651631 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-651821 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-652014 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-652204 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-652394 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-652600 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-652790 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-652979 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-653170 util-scheduler-8620 DEBUG Running task: 4072 / 0x46620a0
Jul 07 20:58:56-653376 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:56-653555 util-8620 DEBUG process_notify is running
Jul 07 20:58:56-653729 util-8620 DEBUG client_notify is running
Jul 07 20:58:56-653908 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:58:56-654103 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:56-654294 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:58:56-654564 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:58:56-654813 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-655006 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-655197 util-scheduler-8620 DEBUG Checking readiness of task: 4059 / 0x46620a0
Jul 07 20:58:56-655388 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-655578 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-655768 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-655957 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-656145 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-656334 util-scheduler-8620 DEBUG Running task: 4059 / 0x46620a0
Jul 07 20:58:56-656743 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:58:56-656974 util-scheduler-8620 DEBUG Adding task: 4073 / 0x4662248
Jul 07 20:58:56-657241 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-657434 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-657625 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-657814 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-658003 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-658191 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-658379 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-658568 util-scheduler-8620 DEBUG Running task: 4073 / 0x4662248
Jul 07 20:58:56-658758 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:58:56-658953 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:58:56-659168 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:58:56-659364 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:58:56-659562 util-scheduler-8620 DEBUG Adding task: 4074 / 0x46620a0
Jul 07 20:58:56-659747 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:58:56-659950 util-scheduler-8620 DEBUG Adding task: 4075 / 0x46620a0
Jul 07 20:58:56-660192 util-scheduler-8620 DEBUG Checking readiness of task: 4075 / 0x46620a0
Jul 07 20:58:56-660386 util-scheduler-8620 DEBUG Checking readiness of task: 4074 / 0x46620a0
Jul 07 20:58:56-660577 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:58:56-660768 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:58:56-660956 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:58:56-661146 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:58:56-661356 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:58:56-661545 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:58:56-661750 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:58:56-661942 util-scheduler-8620 DEBUG Running task: 4074 / 0x46620a0
Jul 07 20:58:56-662128 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:58:56-662303 util-8620 DEBUG process_notify is running
Jul 07 20:58:56-662472 util-8620 DEBUG client_notify is running
Jul 07 20:58:56-662657 util-scheduler-8620 DEBUG Canceling task: 4071 / 0x59ee8a0
Jul 07 20:58:56-662882 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:58:56-663097 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:58:56-663328 cadet-p2p-8620 DEBUG Checking 0x60eded0 towards 2FDYFV0X (->V8XX)
Jul 07 20:58:56-663561 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:58:56-663739 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:58:56-663926 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:58:56-664208 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:58:56-664403 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:58:56-664582 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:58:56-664770 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:58:56-664958 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:58:56-665136 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:58:56-665339 util-scheduler-8620 DEBUG Canceling task: 4060 / 0x59e8808
Jul 07 20:58:56-665551 util-scheduler-8620 DEBUG Adding task: 4076 / 0x59e8808
Jul 07 20:58:56-665793 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:58:56-665963 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:58:56-666143 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:58:56-666343 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:58:56-666518 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:58:56-666691 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:58:56-666888 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:58:56-667092 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:58:56-667275 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:58:56-667453 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:58:56-667641 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:58:56-667887 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:01-652215 util-scheduler-8620 DEBUG Checking readiness of task: 4075 / 0x46620a0
Jul 07 20:59:01-652589 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-653374 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-653818 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-654019 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-654216 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-654407 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-654598 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-654791 util-scheduler-8620 DEBUG Running task: 4070 / 0x52cbfb8
Jul 07 20:59:01-655032 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:01-655291 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:59:01-655498 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:01-655699 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:01-655903 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:01-656140 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:01-656322 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:01-656543 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:01-656835 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:01-657065 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:01-657327 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:01-657537 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:01-657857 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:01-658060 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:01-658286 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:01-658470 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:01-658646 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:01-658853 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:01-659068 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:01-659292 util-scheduler-8620 DEBUG Adding task: 4077 / 0x59ee8a0
Jul 07 20:59:01-659472 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:01-659675 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:01-659852 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:01-660029 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:01-660266 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:01-660464 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:01-660642 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:01-660853 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:01-661096 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:01-661314 util-scheduler-8620 DEBUG Adding task: 4078 / 0x52cbfb8
Jul 07 20:59:01-661579 util-scheduler-8620 DEBUG Checking readiness of task: 4075 / 0x46620a0
Jul 07 20:59:01-661772 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-661963 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-662154 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-662344 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-662534 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-662723 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-662912 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-663102 util-scheduler-8620 DEBUG Running task: 4077 / 0x59ee8a0
Jul 07 20:59:01-663315 util-scheduler-8620 DEBUG Adding task: 4079 / 0x59ee8a0
Jul 07 20:59:01-663536 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:01-663739 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:01-663946 util-scheduler-8620 DEBUG Adding task: 4080 / 0x46620a0
Jul 07 20:59:01-664190 util-scheduler-8620 DEBUG Checking readiness of task: 4080 / 0x46620a0
Jul 07 20:59:01-664385 util-scheduler-8620 DEBUG Checking readiness of task: 4075 / 0x46620a0
Jul 07 20:59:01-664575 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-664765 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-664955 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-665146 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-665356 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-665546 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-665734 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-665926 util-scheduler-8620 DEBUG Running task: 4080 / 0x46620a0
Jul 07 20:59:01-666111 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:01-666290 util-8620 DEBUG process_notify is running
Jul 07 20:59:01-666462 util-8620 DEBUG client_notify is running
Jul 07 20:59:01-666642 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:01-666853 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:01-667045 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:01-667305 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:01-667554 util-scheduler-8620 DEBUG Checking readiness of task: 4075 / 0x46620a0
Jul 07 20:59:01-667749 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-667940 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-668129 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-668320 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-668511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-668700 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-668889 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-669080 util-scheduler-8620 DEBUG Running task: 4075 / 0x46620a0
Jul 07 20:59:01-669507 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:01-669737 util-scheduler-8620 DEBUG Adding task: 4081 / 0x4662248
Jul 07 20:59:01-669984 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-670177 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-670368 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-670559 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-670749 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-670939 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-671129 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-671318 util-scheduler-8620 DEBUG Running task: 4081 / 0x4662248
Jul 07 20:59:01-671509 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:01-671704 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:01-671921 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:01-672118 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:01-672316 util-scheduler-8620 DEBUG Adding task: 4082 / 0x46620a0
Jul 07 20:59:01-672501 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:01-672703 util-scheduler-8620 DEBUG Adding task: 4083 / 0x46620a0
Jul 07 20:59:01-672943 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:01-673136 util-scheduler-8620 DEBUG Checking readiness of task: 4082 / 0x46620a0
Jul 07 20:59:01-673348 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:01-673539 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:01-673728 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:01-673919 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:01-674109 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:01-674297 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:01-674485 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:01-674676 util-scheduler-8620 DEBUG Running task: 4082 / 0x46620a0
Jul 07 20:59:01-674859 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:01-675033 util-8620 DEBUG process_notify is running
Jul 07 20:59:01-675202 util-8620 DEBUG client_notify is running
Jul 07 20:59:01-675387 util-scheduler-8620 DEBUG Canceling task: 4079 / 0x59ee8a0
Jul 07 20:59:01-675610 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:01-675826 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:01-676073 cadet-p2p-8620 DEBUG Checking 0x60f6e70 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:01-676308 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:01-676486 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:01-676672 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:01-676956 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:01-677151 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:01-677350 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:01-677538 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:01-677728 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:01-677907 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:01-678091 util-scheduler-8620 DEBUG Canceling task: 4076 / 0x59e8808
Jul 07 20:59:01-678303 util-scheduler-8620 DEBUG Adding task: 4084 / 0x59e8808
Jul 07 20:59:01-678547 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:01-678717 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:01-678898 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:01-679099 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:01-679273 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:01-679446 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:01-679644 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:01-679849 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:01-680031 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:01-680209 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:01-680397 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:01-680644 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:03-545416 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:03-545773 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:03-545969 util-scheduler-8620 DEBUG Checking readiness of task: 4067 / 0x465ee60
Jul 07 20:59:03-546166 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:03-546359 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:03-546550 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:03-546755 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:03-546946 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:03-547141 util-scheduler-8620 DEBUG Running task: 4067 / 0x465ee60
Jul 07 20:59:03-547562 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 20:59:03-547814 util-scheduler-8620 DEBUG Adding task: 4085 / 0x465f008
Jul 07 20:59:03-548093 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:03-548286 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:03-548477 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:03-548669 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:03-548860 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:03-549050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:03-549392 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:03-549589 util-scheduler-8620 DEBUG Running task: 4085 / 0x465f008
Jul 07 20:59:03-549784 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 20:59:03-550024 nse-api-8620 DEBUG Received information about peer `ZHQ4' from peerinfo database
Jul 07 20:59:03-550212 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 20:59:03-550427 util-scheduler-8620 DEBUG Adding task: 4086 / 0x465f008
Jul 07 20:59:03-550730 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:03-550926 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:03-551118 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:03-551310 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:03-551502 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:03-551692 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:03-551882 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:03-552072 util-scheduler-8620 DEBUG Running task: 4086 / 0x465f008
Jul 07 20:59:03-552262 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 20:59:03-552480 nse-api-8620 DEBUG Received information about peer `ZHQ4' from peerinfo database
Jul 07 20:59:03-552753 cadet-hll-8620 DEBUG  hello for ZHQ4 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 20:59:03-553019 cadet-p2p-8620 DEBUG set hello for ZHQ4
Jul 07 20:59:03-553225 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 20:59:03-553419 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:03-553629 util-scheduler-8620 DEBUG Adding task: 4087 / 0x465ee60
Jul 07 20:59:06-664587 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-664972 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:06-666464 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-666824 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-667025 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-667218 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-667409 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-667601 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-667795 util-scheduler-8620 DEBUG Running task: 4078 / 0x52cbfb8
Jul 07 20:59:06-668034 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:06-668294 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:59:06-668501 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:06-668702 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:06-668905 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:06-669141 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:06-669355 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:06-669577 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:06-669869 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:06-670067 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:06-670304 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:06-670513 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:06-670834 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:06-671036 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:06-671261 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:06-671445 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:06-671621 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:06-671828 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:06-672045 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:06-672271 util-scheduler-8620 DEBUG Adding task: 4088 / 0x59ee8a0
Jul 07 20:59:06-672452 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:06-672656 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:06-672832 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:06-673007 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:06-673307 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:06-673505 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:06-673684 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:06-673883 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:06-674128 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:06-674329 util-scheduler-8620 DEBUG Adding task: 4089 / 0x52cbfb8
Jul 07 20:59:06-674594 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-674787 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:06-674977 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-675166 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-675357 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-675547 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-675736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-675925 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-676116 util-scheduler-8620 DEBUG Running task: 4088 / 0x59ee8a0
Jul 07 20:59:06-676324 util-scheduler-8620 DEBUG Adding task: 4090 / 0x59ee8a0
Jul 07 20:59:06-676546 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:06-676751 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:06-676960 util-scheduler-8620 DEBUG Adding task: 4091 / 0x46620a0
Jul 07 20:59:06-677230 util-scheduler-8620 DEBUG Checking readiness of task: 4091 / 0x46620a0
Jul 07 20:59:06-677428 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-677618 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:06-677809 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-677998 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-678189 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-678378 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-678627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-678817 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-679010 util-scheduler-8620 DEBUG Running task: 4091 / 0x46620a0
Jul 07 20:59:06-679195 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:06-679374 util-8620 DEBUG process_notify is running
Jul 07 20:59:06-679548 util-8620 DEBUG client_notify is running
Jul 07 20:59:06-679727 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:06-679923 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:06-680115 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:06-680373 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:06-680624 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-680828 util-scheduler-8620 DEBUG Checking readiness of task: 4083 / 0x46620a0
Jul 07 20:59:06-681020 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-681236 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-681428 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-681618 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-681807 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-681996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-682186 util-scheduler-8620 DEBUG Running task: 4083 / 0x46620a0
Jul 07 20:59:06-682594 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:06-682842 util-scheduler-8620 DEBUG Adding task: 4092 / 0x4662248
Jul 07 20:59:06-683091 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-683284 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-683476 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-683665 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-683855 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-684045 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-684234 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-684427 util-scheduler-8620 DEBUG Running task: 4092 / 0x4662248
Jul 07 20:59:06-684618 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:06-684815 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:06-685031 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:06-685252 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:06-685454 util-scheduler-8620 DEBUG Adding task: 4093 / 0x46620a0
Jul 07 20:59:06-685639 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:06-685843 util-scheduler-8620 DEBUG Adding task: 4094 / 0x46620a0
Jul 07 20:59:06-686085 util-scheduler-8620 DEBUG Checking readiness of task: 4094 / 0x46620a0
Jul 07 20:59:06-686278 util-scheduler-8620 DEBUG Checking readiness of task: 4093 / 0x46620a0
Jul 07 20:59:06-686469 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:06-686659 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:06-686849 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:06-687039 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:06-687229 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:06-687417 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:06-687605 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:06-687795 util-scheduler-8620 DEBUG Running task: 4093 / 0x46620a0
Jul 07 20:59:06-688001 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:06-688176 util-8620 DEBUG process_notify is running
Jul 07 20:59:06-688348 util-8620 DEBUG client_notify is running
Jul 07 20:59:06-688534 util-scheduler-8620 DEBUG Canceling task: 4090 / 0x59ee8a0
Jul 07 20:59:06-688759 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:06-688975 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:06-689233 cadet-p2p-8620 DEBUG Checking 0x60fb190 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:06-689470 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:06-689651 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:06-689838 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:06-690125 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:06-690320 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:06-690500 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:06-690688 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:06-690876 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:06-691056 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:06-691239 util-scheduler-8620 DEBUG Canceling task: 4084 / 0x59e8808
Jul 07 20:59:06-691452 util-scheduler-8620 DEBUG Adding task: 4095 / 0x59e8808
Jul 07 20:59:06-691696 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:06-691866 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:06-692048 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:06-692250 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:06-692425 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:06-692615 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:06-692816 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:06-693021 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:06-693230 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:06-693411 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:06-693602 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:06-693850 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:11-679473 util-scheduler-8620 DEBUG Checking readiness of task: 4094 / 0x46620a0
Jul 07 20:59:11-679853 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-680843 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-681052 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-681352 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-681548 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-681742 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-681933 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-682125 util-scheduler-8620 DEBUG Running task: 4089 / 0x52cbfb8
Jul 07 20:59:11-682363 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:11-682623 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:59:11-682830 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:11-683033 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:11-683236 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:11-683471 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:11-683651 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:11-683873 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:11-684166 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:11-684425 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:11-684738 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:11-684949 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:11-685291 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:11-685495 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:11-685721 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:11-685907 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:11-686084 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:11-686290 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:11-686505 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:11-686732 util-scheduler-8620 DEBUG Adding task: 4096 / 0x59ee8a0
Jul 07 20:59:11-686913 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:11-687115 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:11-687292 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:11-687468 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:11-687706 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:11-687902 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:11-688108 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:11-688308 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:11-688552 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:11-688762 util-scheduler-8620 DEBUG Adding task: 4097 / 0x52cbfb8
Jul 07 20:59:11-689021 util-scheduler-8620 DEBUG Checking readiness of task: 4094 / 0x46620a0
Jul 07 20:59:11-689236 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-689429 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-689649 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-689840 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-690030 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-690219 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-690407 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-690597 util-scheduler-8620 DEBUG Running task: 4096 / 0x59ee8a0
Jul 07 20:59:11-690804 util-scheduler-8620 DEBUG Adding task: 4098 / 0x59ee8a0
Jul 07 20:59:11-691026 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:11-691229 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:11-691437 util-scheduler-8620 DEBUG Adding task: 4099 / 0x46620a0
Jul 07 20:59:11-691680 util-scheduler-8620 DEBUG Checking readiness of task: 4099 / 0x46620a0
Jul 07 20:59:11-691876 util-scheduler-8620 DEBUG Checking readiness of task: 4094 / 0x46620a0
Jul 07 20:59:11-692067 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-692271 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-692462 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-692652 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-692841 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-693029 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-693236 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-693430 util-scheduler-8620 DEBUG Running task: 4099 / 0x46620a0
Jul 07 20:59:11-693614 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:11-693793 util-8620 DEBUG process_notify is running
Jul 07 20:59:11-693967 util-8620 DEBUG client_notify is running
Jul 07 20:59:11-694147 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:11-694342 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:11-694533 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:11-694787 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:11-695036 util-scheduler-8620 DEBUG Checking readiness of task: 4094 / 0x46620a0
Jul 07 20:59:11-695229 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-695420 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-695610 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-695799 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-695992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-696218 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-696410 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-696601 util-scheduler-8620 DEBUG Running task: 4094 / 0x46620a0
Jul 07 20:59:11-697008 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:11-697256 util-scheduler-8620 DEBUG Adding task: 4100 / 0x4662248
Jul 07 20:59:11-697505 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-697700 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-697890 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-698082 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-698271 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-698461 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-698668 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-698858 util-scheduler-8620 DEBUG Running task: 4100 / 0x4662248
Jul 07 20:59:11-699049 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:11-699245 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:11-699462 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:11-699659 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:11-699857 util-scheduler-8620 DEBUG Adding task: 4101 / 0x46620a0
Jul 07 20:59:11-700042 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:11-700245 util-scheduler-8620 DEBUG Adding task: 4102 / 0x46620a0
Jul 07 20:59:11-700485 util-scheduler-8620 DEBUG Checking readiness of task: 4102 / 0x46620a0
Jul 07 20:59:11-700678 util-scheduler-8620 DEBUG Checking readiness of task: 4101 / 0x46620a0
Jul 07 20:59:11-700869 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:11-701059 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:11-701269 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:11-701459 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:11-701648 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:11-701838 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:11-702028 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:11-702218 util-scheduler-8620 DEBUG Running task: 4101 / 0x46620a0
Jul 07 20:59:11-702400 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:11-702575 util-8620 DEBUG process_notify is running
Jul 07 20:59:11-702743 util-8620 DEBUG client_notify is running
Jul 07 20:59:11-702929 util-scheduler-8620 DEBUG Canceling task: 4098 / 0x59ee8a0
Jul 07 20:59:11-703152 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:11-703392 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:11-703625 cadet-p2p-8620 DEBUG Checking 0x60fe908 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:11-703859 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:11-704036 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:11-704222 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:11-704506 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:11-704700 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:11-704879 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:11-705067 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:11-705278 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:11-705457 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:11-705640 util-scheduler-8620 DEBUG Canceling task: 4095 / 0x59e8808
Jul 07 20:59:11-705855 util-scheduler-8620 DEBUG Adding task: 4103 / 0x59e8808
Jul 07 20:59:11-706100 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:11-706269 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:11-706450 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:11-706652 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:11-706829 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:11-707003 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:11-707202 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:11-707408 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:11-707593 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:11-707771 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:11-707961 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:11-708207 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:16-693904 util-scheduler-8620 DEBUG Checking readiness of task: 4102 / 0x46620a0
Jul 07 20:59:16-694285 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-694746 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-694973 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-695211 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-695407 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-695599 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-695790 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-695998 util-scheduler-8620 DEBUG Running task: 4097 / 0x52cbfb8
Jul 07 20:59:16-696235 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:16-696492 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:59:16-696700 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:16-696902 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:16-697109 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:16-697363 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:16-697545 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:16-697767 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:16-698058 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:16-698255 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:16-698493 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:16-698701 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:16-699020 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:16-699221 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:16-699446 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:16-699631 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:16-699807 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:16-700012 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:16-700229 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:16-700453 util-scheduler-8620 DEBUG Adding task: 4104 / 0x59ee8a0
Jul 07 20:59:16-700634 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:16-700836 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:16-701012 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:16-701209 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:16-701451 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:16-701647 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:16-701839 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:16-702053 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:16-702295 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:16-702493 util-scheduler-8620 DEBUG Adding task: 4105 / 0x52cbfb8
Jul 07 20:59:16-702751 util-scheduler-8620 DEBUG Checking readiness of task: 4102 / 0x46620a0
Jul 07 20:59:16-702944 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-703134 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-703324 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-703513 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-703703 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-703891 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-704079 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-704268 util-scheduler-8620 DEBUG Running task: 4104 / 0x59ee8a0
Jul 07 20:59:16-704475 util-scheduler-8620 DEBUG Adding task: 4106 / 0x59ee8a0
Jul 07 20:59:16-704719 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:16-704923 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:16-705132 util-scheduler-8620 DEBUG Adding task: 4107 / 0x46620a0
Jul 07 20:59:16-705399 util-scheduler-8620 DEBUG Checking readiness of task: 4107 / 0x46620a0
Jul 07 20:59:16-705594 util-scheduler-8620 DEBUG Checking readiness of task: 4102 / 0x46620a0
Jul 07 20:59:16-705783 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-705973 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-706162 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-706353 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-706542 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-706731 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-706919 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-707113 util-scheduler-8620 DEBUG Running task: 4107 / 0x46620a0
Jul 07 20:59:16-707297 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:16-707475 util-8620 DEBUG process_notify is running
Jul 07 20:59:16-707647 util-8620 DEBUG client_notify is running
Jul 07 20:59:16-707826 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:16-708019 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:16-708210 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:16-708464 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:16-708711 util-scheduler-8620 DEBUG Checking readiness of task: 4102 / 0x46620a0
Jul 07 20:59:16-708905 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-709095 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-709305 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-709496 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-709685 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-709875 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-710063 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-710253 util-scheduler-8620 DEBUG Running task: 4102 / 0x46620a0
Jul 07 20:59:16-710656 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:16-710886 util-scheduler-8620 DEBUG Adding task: 4108 / 0x4662248
Jul 07 20:59:16-711133 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-711325 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-711516 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-711705 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-711895 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-712084 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-712273 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-712461 util-scheduler-8620 DEBUG Running task: 4108 / 0x4662248
Jul 07 20:59:16-712651 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:16-712846 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:16-713062 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:16-713292 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:16-713491 util-scheduler-8620 DEBUG Adding task: 4109 / 0x46620a0
Jul 07 20:59:16-713691 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:16-713896 util-scheduler-8620 DEBUG Adding task: 4110 / 0x46620a0
Jul 07 20:59:16-714136 util-scheduler-8620 DEBUG Checking readiness of task: 4110 / 0x46620a0
Jul 07 20:59:16-714329 util-scheduler-8620 DEBUG Checking readiness of task: 4109 / 0x46620a0
Jul 07 20:59:16-714520 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:16-714711 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:16-714900 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:16-715091 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:16-715280 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:16-715469 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:16-715656 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:16-715847 util-scheduler-8620 DEBUG Running task: 4109 / 0x46620a0
Jul 07 20:59:16-716030 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:16-716205 util-8620 DEBUG process_notify is running
Jul 07 20:59:16-716374 util-8620 DEBUG client_notify is running
Jul 07 20:59:16-716560 util-scheduler-8620 DEBUG Canceling task: 4106 / 0x59ee8a0
Jul 07 20:59:16-716781 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:16-716996 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:16-717296 cadet-p2p-8620 DEBUG Checking 0x6101530 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:16-717533 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:16-717711 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:16-717898 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:16-718182 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:16-718377 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:16-718555 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:16-718743 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:16-718933 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:16-719112 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:16-719295 util-scheduler-8620 DEBUG Canceling task: 4103 / 0x59e8808
Jul 07 20:59:16-719509 util-scheduler-8620 DEBUG Adding task: 4111 / 0x59e8808
Jul 07 20:59:16-719752 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:16-719923 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:16-720104 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:16-720303 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:16-720478 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:16-720652 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:16-720851 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:16-721055 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:16-721257 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:16-721436 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:16-721627 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:16-721871 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:21-707646 util-scheduler-8620 DEBUG Checking readiness of task: 4110 / 0x46620a0
Jul 07 20:59:21-708045 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-708665 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-708867 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-709130 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-709364 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-709556 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-709781 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-709976 util-scheduler-8620 DEBUG Running task: 4105 / 0x52cbfb8
Jul 07 20:59:21-710216 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:21-710474 cadet-tun-8620 DEBUG  kx started 11 m ago
Jul 07 20:59:21-710681 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:21-710881 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:21-711084 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:21-711320 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:21-711501 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:21-711721 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:21-712013 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:21-712211 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:21-712448 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:21-712657 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:21-712975 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:21-713176 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:21-713439 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:21-713624 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:21-713800 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:21-714006 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:21-714223 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:21-714448 util-scheduler-8620 DEBUG Adding task: 4112 / 0x59ee8a0
Jul 07 20:59:21-714629 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:21-714832 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:21-715010 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:21-715184 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:21-715422 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:21-715618 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:21-715796 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:21-715994 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:21-716239 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:21-716436 util-scheduler-8620 DEBUG Adding task: 4113 / 0x52cbfb8
Jul 07 20:59:21-716696 util-scheduler-8620 DEBUG Checking readiness of task: 4110 / 0x46620a0
Jul 07 20:59:21-716890 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-717080 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-717289 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-717480 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-717670 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-717859 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-718051 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-718240 util-scheduler-8620 DEBUG Running task: 4112 / 0x59ee8a0
Jul 07 20:59:21-718448 util-scheduler-8620 DEBUG Adding task: 4114 / 0x59ee8a0
Jul 07 20:59:21-718671 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:21-718875 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:21-719083 util-scheduler-8620 DEBUG Adding task: 4115 / 0x46620a0
Jul 07 20:59:21-719442 util-scheduler-8620 DEBUG Checking readiness of task: 4115 / 0x46620a0
Jul 07 20:59:21-719639 util-scheduler-8620 DEBUG Checking readiness of task: 4110 / 0x46620a0
Jul 07 20:59:21-719830 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-720019 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-720229 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-720419 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-720610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-720798 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-720988 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-721179 util-scheduler-8620 DEBUG Running task: 4115 / 0x46620a0
Jul 07 20:59:21-721386 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:21-721564 util-8620 DEBUG process_notify is running
Jul 07 20:59:21-721737 util-8620 DEBUG client_notify is running
Jul 07 20:59:21-721916 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:21-722112 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:21-722303 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:21-722561 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:21-722809 util-scheduler-8620 DEBUG Checking readiness of task: 4110 / 0x46620a0
Jul 07 20:59:21-723002 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-723194 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-723383 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-723572 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-723762 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-723950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-724139 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-724329 util-scheduler-8620 DEBUG Running task: 4110 / 0x46620a0
Jul 07 20:59:21-724735 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:21-724977 util-scheduler-8620 DEBUG Adding task: 4116 / 0x4662248
Jul 07 20:59:21-725244 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-725438 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-725628 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-725817 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-726007 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-726196 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-726385 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-726574 util-scheduler-8620 DEBUG Running task: 4116 / 0x4662248
Jul 07 20:59:21-726763 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:21-726959 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:21-727175 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:21-727372 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:21-727570 util-scheduler-8620 DEBUG Adding task: 4117 / 0x46620a0
Jul 07 20:59:21-727754 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:21-727960 util-scheduler-8620 DEBUG Adding task: 4118 / 0x46620a0
Jul 07 20:59:21-728204 util-scheduler-8620 DEBUG Checking readiness of task: 4118 / 0x46620a0
Jul 07 20:59:21-728396 util-scheduler-8620 DEBUG Checking readiness of task: 4117 / 0x46620a0
Jul 07 20:59:21-728586 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:21-728776 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:21-728965 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:21-729154 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:21-729391 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:21-729582 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:21-729771 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:21-729961 util-scheduler-8620 DEBUG Running task: 4117 / 0x46620a0
Jul 07 20:59:21-730145 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:21-730321 util-8620 DEBUG process_notify is running
Jul 07 20:59:21-730490 util-8620 DEBUG client_notify is running
Jul 07 20:59:21-730675 util-scheduler-8620 DEBUG Canceling task: 4114 / 0x59ee8a0
Jul 07 20:59:21-730900 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:21-731115 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:21-731349 cadet-p2p-8620 DEBUG Checking 0x61059e8 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:21-731583 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:21-731762 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:21-731949 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:21-732233 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:21-732428 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:21-732607 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:21-732794 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:21-732983 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:21-733161 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:21-733365 util-scheduler-8620 DEBUG Canceling task: 4111 / 0x59e8808
Jul 07 20:59:21-733578 util-scheduler-8620 DEBUG Adding task: 4119 / 0x59e8808
Jul 07 20:59:21-733822 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:21-733992 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:21-734173 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:21-734373 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:21-734548 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:21-734721 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:21-734920 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:21-735126 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:21-735308 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:21-735485 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:21-735673 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:21-735920 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:25-310392 util-scheduler-8620 DEBUG Checking readiness of task: 4118 / 0x46620a0
Jul 07 20:59:25-310777 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-310975 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-311169 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-311361 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-311554 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-311744 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-311933 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-312129 util-scheduler-8620 DEBUG Running task: 4118 / 0x46620a0
Jul 07 20:59:25-312555 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:25-312812 util-scheduler-8620 DEBUG Adding task: 4120 / 0x4662248
Jul 07 20:59:25-313091 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-313316 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-313510 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-313733 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-313927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-314117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-314307 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-314497 util-scheduler-8620 DEBUG Running task: 4120 / 0x4662248
Jul 07 20:59:25-314689 util-8620 DEBUG Received message of type 70 and size 120 from core service.
Jul 07 20:59:25-314890 core-api-8620 DEBUG Processing message of type 70 and size 120 from core service
Jul 07 20:59:25-315123 core-api-8620 DEBUG Received message of type 280 and size 84 from peer `KNAS'
Jul 07 20:59:25-315392 cadet-con-8620 INFO <-- {         ENCRYPTED} on connection M9KEP6HP from KNAS
Jul 07 20:59:25-315637 cadet-con-8620 DEBUG   connection M9KEP6HP (->P00P)
Jul 07 20:59:25-315866 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:25-316074 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:59:25-316272 cadet-con-8620 DEBUG  PID 0 (expected 0+)
Jul 07 20:59:25-316453 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:25-316643 util-scheduler-8620 DEBUG Canceling task: 3610 / 0x53a5de0
Jul 07 20:59:25-316868 util-scheduler-8620 DEBUG Adding task: 4121 / 0x53a5de0
Jul 07 20:59:25-317048 cadet-con-8620 DEBUG   message for us!
Jul 07 20:59:25-317330 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:25-317548 util-scheduler-8620 DEBUG Adding task: 4122 / 0x4d5e5d8
Jul 07 20:59:25-317733 cadet-tun-8620 DEBUG   decrypt start
Jul 07 20:59:25-317902 cadet-tun-8620 DEBUG   decrypt iv
Jul 07 20:59:25-321532 cadet-tun-8620 DEBUG   decrypt iv done
Jul 07 20:59:25-322424 cadet-tun-8620 DEBUG   decrypt end
Jul 07 20:59:25-322639 cadet-tun-8620 INFO   HMAC with key X5GG98S2
Jul 07 20:59:25-325978 cadet-tun-8620 INFO <=== {         KEEPALIVE} on P00P
Jul 07 20:59:25-326823 cadet-con-8620 DEBUG GMC send FWD ACK on M9KEP6HP (->P00P)
Jul 07 20:59:25-327011 cadet-con-8620 DEBUG   getting from all channels
Jul 07 20:59:25-327189 cadet-con-8620 DEBUG   buffer available: 64
Jul 07 20:59:25-327363 cadet-con-8620 DEBUG   sending on connection
Jul 07 20:59:25-327586 cadet-con-8620 DEBUG connection send FWD ack on M9KEP6HP (->P00P)
Jul 07 20:59:25-327767 cadet-con-8620 DEBUG  ACK 64
Jul 07 20:59:25-327946 cadet-con-8620 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 20:59:25-328217 cadet-con-8620 INFO --> {               ACK} ( 64) on connection M9KEP6HP (->P00P) (40 bytes)
Jul 07 20:59:25-328409 cadet-con-8620 DEBUG  ack 64
Jul 07 20:59:25-328589 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 0
Jul 07 20:59:25-328825 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:25-329036 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:59:25-329359 cadet-p2p-8620 INFO que {               ACK} ( 64) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 40)
Jul 07 20:59:25-329559 cadet-p2p-8620 DEBUG priority 100
Jul 07 20:59:25-329784 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:59:25-329967 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:25-330142 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:25-330348 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 40 bytes
Jul 07 20:59:25-330564 core-api-8620 DEBUG Asking core for transmission of 40 bytes to `KNAS'
Jul 07 20:59:25-330787 util-scheduler-8620 DEBUG Adding task: 4123 / 0x4d5c9e8
Jul 07 20:59:25-330968 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:25-331173 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:59:25-331349 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:25-331525 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:59:25-331762 cadet-p2p-8620 DEBUG QQQ  - {               ACK} BCK on M9KEP6HP (->P00P)
Jul 07 20:59:25-331948 cadet-p2p-8620 DEBUG QQQ    payload , 64
Jul 07 20:59:25-332123 cadet-p2p-8620 DEBUG QQQ    size: 40 bytes
Jul 07 20:59:25-332345 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:59:25-332531 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:25-332742 util-scheduler-8620 DEBUG Adding task: 4124 / 0x46620a0
Jul 07 20:59:25-333013 util-scheduler-8620 DEBUG Checking readiness of task: 4124 / 0x46620a0
Jul 07 20:59:25-333234 util-scheduler-8620 DEBUG Checking readiness of task: 4122 / 0x4d5e5d8
Jul 07 20:59:25-333428 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-333619 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-333809 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-333998 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-334189 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-334378 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-334566 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-334759 util-scheduler-8620 DEBUG Running task: 4122 / 0x4d5e5d8
Jul 07 20:59:25-334945 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:25-335123 util-8620 DEBUG process_notify is running
Jul 07 20:59:25-335298 util-8620 DEBUG client_notify is running
Jul 07 20:59:25-335543 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:25-335750 util-scheduler-8620 DEBUG Adding task: 4125 / 0x4d5e5d8
Jul 07 20:59:25-335953 util-8620 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 20:59:25-336216 util-8620 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:25-336415 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:59:25-336613 util-scheduler-8620 DEBUG Running task: 4123 / 0x4d5c9e8
Jul 07 20:59:25-336820 util-scheduler-8620 DEBUG Adding task: 4126 / 0x4d5c9e8
Jul 07 20:59:25-337042 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:59:25-337260 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:25-337458 util-scheduler-8620 DEBUG Adding task: 4127 / 0x46620a0
Jul 07 20:59:25-337701 util-scheduler-8620 DEBUG Checking readiness of task: 4127 / 0x46620a0
Jul 07 20:59:25-337895 util-scheduler-8620 DEBUG Checking readiness of task: 4125 / 0x4d5e5d8
Jul 07 20:59:25-338085 util-scheduler-8620 DEBUG Checking readiness of task: 4124 / 0x46620a0
Jul 07 20:59:25-338275 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-338465 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-338657 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-338848 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-339040 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-339229 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-339417 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-339608 util-scheduler-8620 DEBUG Running task: 4125 / 0x4d5e5d8
Jul 07 20:59:25-339795 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:25-339970 util-8620 DEBUG process_notify is running
Jul 07 20:59:25-340140 util-8620 DEBUG client_notify is running
Jul 07 20:59:25-340350 util-8620 DEBUG Transmitting message of type 168 and size 44 to statistics service.
Jul 07 20:59:25-340597 util-8620 DEBUG Connection transmitted 44/44 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:25-340808 util-scheduler-8620 DEBUG Running task: 4127 / 0x46620a0
Jul 07 20:59:25-340991 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:25-341166 util-8620 DEBUG process_notify is running
Jul 07 20:59:25-341358 util-8620 DEBUG client_notify is running
Jul 07 20:59:25-341536 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:25-341747 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:25-341938 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:25-342177 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:25-342425 util-scheduler-8620 DEBUG Checking readiness of task: 4124 / 0x46620a0
Jul 07 20:59:25-342619 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-342812 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-343002 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-343192 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-343381 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-343570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-343759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-343949 util-scheduler-8620 DEBUG Running task: 4124 / 0x46620a0
Jul 07 20:59:25-344349 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:25-344580 util-scheduler-8620 DEBUG Adding task: 4128 / 0x4662248
Jul 07 20:59:25-344827 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-345020 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-345233 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-345424 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-345614 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-345803 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-345992 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-346181 util-scheduler-8620 DEBUG Running task: 4128 / 0x4662248
Jul 07 20:59:25-346372 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:25-346566 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:25-346781 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:59:25-346978 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:25-347176 util-scheduler-8620 DEBUG Adding task: 4129 / 0x46620a0
Jul 07 20:59:25-347373 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:25-347571 util-scheduler-8620 DEBUG Adding task: 4130 / 0x46620a0
Jul 07 20:59:25-347809 util-scheduler-8620 DEBUG Checking readiness of task: 4130 / 0x46620a0
Jul 07 20:59:25-348002 util-scheduler-8620 DEBUG Checking readiness of task: 4129 / 0x46620a0
Jul 07 20:59:25-348192 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:25-348382 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:25-348572 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:25-348762 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:25-348955 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:25-349144 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:25-349355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:25-349546 util-scheduler-8620 DEBUG Running task: 4129 / 0x46620a0
Jul 07 20:59:25-349730 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:25-349905 util-8620 DEBUG process_notify is running
Jul 07 20:59:25-350073 util-8620 DEBUG client_notify is running
Jul 07 20:59:25-350258 util-scheduler-8620 DEBUG Canceling task: 4126 / 0x4d5c9e8
Jul 07 20:59:25-350480 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 40 bytes.
Jul 07 20:59:25-350712 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:59:25-350946 cadet-p2p-8620 DEBUG Checking 0x6122ff0 towards M9KEP6HP (->P00P)
Jul 07 20:59:25-351180 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:59:25-351359 cadet-p2p-8620 DEBUG   size 40 ok
Jul 07 20:59:25-351545 cadet-p2p-8620 DEBUG   raw {               ACK}
Jul 07 20:59:25-351813 cadet-p2p-8620 INFO snd {               ACK} ( 64) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 40)
Jul 07 20:59:25-352007 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:25-352187 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:25-352374 cadet-con-8620 DEBUG  sent BCK {               ACK}
Jul 07 20:59:25-352547 cadet-con-8620 DEBUG  calling cont
Jul 07 20:59:25-352729 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:59:25-352903 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:25-353083 cadet-p2p-8620 DEBUG   return 40
Jul 07 20:59:25-353304 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:59:25-353479 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:25-353653 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:25-353849 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:59:25-354053 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 40 bytes.
Jul 07 20:59:25-354237 core-api-8620 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 20:59:25-354414 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:25-354602 util-8620 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 20:59:25-354844 util-8620 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:26-717922 util-scheduler-8620 DEBUG Checking readiness of task: 4130 / 0x46620a0
Jul 07 20:59:26-718235 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-718723 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-718960 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-719186 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-719393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-719584 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-719774 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-719970 util-scheduler-8620 DEBUG Running task: 4113 / 0x52cbfb8
Jul 07 20:59:26-720196 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:26-720451 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:26-720660 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:26-720861 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:26-721063 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:26-721353 cadet-tun-8620 DEBUG   connection 2FDYFV0X (->V8XX): 3
Jul 07 20:59:26-721536 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:26-721757 cadet-tun-8620 DEBUG  selected: connection 2FDYFV0X (->V8XX)
Jul 07 20:59:26-722044 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (196 bytes)
Jul 07 20:59:26-722241 cadet-con-8620 DEBUG   C_P+ 0x59e8808 0
Jul 07 20:59:26-722479 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:26-722690 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:26-723005 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD towards V8XX (size 196)
Jul 07 20:59:26-723206 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:26-723431 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 2FDYFV0X (->V8XX)
Jul 07 20:59:26-723614 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:26-723790 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:26-723996 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:26-724209 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:26-724454 util-scheduler-8620 DEBUG Adding task: 4131 / 0x59ee8a0
Jul 07 20:59:26-724636 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:26-724839 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:26-725018 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:26-725211 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x59ee8cc
Jul 07 20:59:26-725451 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 2FDYFV0X (->V8XX)
Jul 07 20:59:26-725647 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:26-725824 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:26-726021 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:26-726264 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:26-726461 util-scheduler-8620 DEBUG Adding task: 4132 / 0x52cbfb8
Jul 07 20:59:26-726713 util-scheduler-8620 DEBUG Checking readiness of task: 4130 / 0x46620a0
Jul 07 20:59:26-726906 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-727097 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-727311 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-727501 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-727690 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-727880 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-728068 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-728258 util-scheduler-8620 DEBUG Running task: 4131 / 0x59ee8a0
Jul 07 20:59:26-728466 util-scheduler-8620 DEBUG Adding task: 4133 / 0x59ee8a0
Jul 07 20:59:26-728685 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:26-728886 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:26-729094 util-scheduler-8620 DEBUG Adding task: 4134 / 0x46620a0
Jul 07 20:59:26-729356 util-scheduler-8620 DEBUG Checking readiness of task: 4134 / 0x46620a0
Jul 07 20:59:26-729551 util-scheduler-8620 DEBUG Checking readiness of task: 4130 / 0x46620a0
Jul 07 20:59:26-729741 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-729934 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-730124 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-730314 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-730503 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-730693 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-730882 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-731073 util-scheduler-8620 DEBUG Running task: 4134 / 0x46620a0
Jul 07 20:59:26-731258 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:26-731435 util-8620 DEBUG process_notify is running
Jul 07 20:59:26-731607 util-8620 DEBUG client_notify is running
Jul 07 20:59:26-731798 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:26-731992 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:26-732183 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:26-732434 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:26-732681 util-scheduler-8620 DEBUG Checking readiness of task: 4130 / 0x46620a0
Jul 07 20:59:26-732873 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-733063 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-733292 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-733483 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-733673 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-733877 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-734066 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-734256 util-scheduler-8620 DEBUG Running task: 4130 / 0x46620a0
Jul 07 20:59:26-734658 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:26-734885 util-scheduler-8620 DEBUG Adding task: 4135 / 0x4662248
Jul 07 20:59:26-735131 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-735324 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-735513 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-735703 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-735893 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-736082 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-736270 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-736458 util-scheduler-8620 DEBUG Running task: 4135 / 0x4662248
Jul 07 20:59:26-736646 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:26-736841 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:26-737056 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:26-737273 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:26-737471 util-scheduler-8620 DEBUG Adding task: 4136 / 0x46620a0
Jul 07 20:59:26-737655 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:26-737857 util-scheduler-8620 DEBUG Adding task: 4137 / 0x46620a0
Jul 07 20:59:26-738098 util-scheduler-8620 DEBUG Checking readiness of task: 4137 / 0x46620a0
Jul 07 20:59:26-738290 util-scheduler-8620 DEBUG Checking readiness of task: 4136 / 0x46620a0
Jul 07 20:59:26-738481 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-738671 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-738859 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-739049 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-739238 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-739427 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-739615 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-739805 util-scheduler-8620 DEBUG Running task: 4136 / 0x46620a0
Jul 07 20:59:26-739992 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:26-740166 util-8620 DEBUG process_notify is running
Jul 07 20:59:26-740337 util-8620 DEBUG client_notify is running
Jul 07 20:59:26-740521 util-scheduler-8620 DEBUG Canceling task: 4133 / 0x59ee8a0
Jul 07 20:59:26-740742 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:26-740956 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:26-741185 cadet-p2p-8620 DEBUG Checking 0x61274d8 towards 2FDYFV0X (->V8XX)
Jul 07 20:59:26-741439 cadet-p2p-8620 DEBUG   on connection 2FDYFV0X (->V8XX) FWD
Jul 07 20:59:26-741615 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:26-741800 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:26-742081 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 2FDYFV0X (->V8XX) (0x59e8808) FWD (size 196)
Jul 07 20:59:26-742274 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:26-742451 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:26-742637 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:26-742824 cadet-con-8620 DEBUG  C_P- 0x59e8808 1
Jul 07 20:59:26-743001 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:26-743184 util-scheduler-8620 DEBUG Canceling task: 4119 / 0x59e8808
Jul 07 20:59:26-743410 util-scheduler-8620 DEBUG Adding task: 4138 / 0x59e8808
Jul 07 20:59:26-743672 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:26-743843 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:26-744022 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:26-744220 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:26-744394 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:26-744567 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:26-744765 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:26-744968 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:26-745150 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:26-745347 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:26-745536 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:26-745779 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:26-872067 util-scheduler-8620 DEBUG Checking readiness of task: 4137 / 0x46620a0
Jul 07 20:59:26-872279 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-872474 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-872667 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-872858 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-873089 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-873298 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-873489 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-873681 util-scheduler-8620 DEBUG Running task: 3623 / 0x53a5de0
Jul 07 20:59:26-873922 cadet-con-8620 DEBUG BCK keepalive for M9KEP6HP (->P00P)
Jul 07 20:59:26-874315 cadet-con-8620 INFO keepalive BCK for connection M9KEP6HP (->P00P)
Jul 07 20:59:26-874694 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:26-874912 util-scheduler-8620 DEBUG Adding task: 4139 / 0x4d5e5d8
Jul 07 20:59:26-875130 cadet-tun-8620 DEBUG GMT Send on Tunnel P00P
Jul 07 20:59:26-875334 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:59:26-875515 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:59:26-875698 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:59:26-875877 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:59:26-876055 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:26-876278 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:26-876513 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:26-876751 cadet-tun-8620 DEBUG TTT  - M9KEP6HP (->P00P) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:26-876936 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:26-877261 cadet-tun-8620 DEBUG   t_encrypt start
Jul 07 20:59:26-877436 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:59:26-877622 cadet-tun-8620 INFO   ENC with key 1BR3R993
Jul 07 20:59:26-881066 cadet-tun-8620 DEBUG   t_encrypt IV derived
Jul 07 20:59:26-882334 cadet-tun-8620 DEBUG   t_encrypt end
Jul 07 20:59:26-882575 cadet-tun-8620 DEBUG   no KX: using current key
Jul 07 20:59:26-882766 cadet-tun-8620 INFO   HMAC with key 1BR3R993
Jul 07 20:59:26-885490 cadet-tun-8620 DEBUG type {         KEEPALIVE}
Jul 07 20:59:26-885812 cadet-con-8620 INFO --> {         ENCRYPTED} ({         KEEPALIVE} 0) on connection M9KEP6HP (->P00P) (84 bytes)
Jul 07 20:59:26-886017 cadet-con-8620 DEBUG   Q_N+ 0x53a5e18 0
Jul 07 20:59:26-886197 cadet-con-8620 DEBUG last pid sent 4294967295
Jul 07 20:59:26-886373 cadet-con-8620 DEBUG      ack recv 0
Jul 07 20:59:26-886552 cadet-con-8620 DEBUG   C_P+ 0x53a5de0 0
Jul 07 20:59:26-886788 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:26-886996 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:59:26-887307 cadet-p2p-8620 INFO que {         ENCRYPTED} ({         KEEPALIVE} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK towards P00P (size 84)
Jul 07 20:59:26-887530 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:26-887758 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:59:26-887942 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:26-888117 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:26-888333 cadet-p2p-8620 DEBUG calling core tmt rdy towards KNAS for 84 bytes
Jul 07 20:59:26-888551 core-api-8620 DEBUG Asking core for transmission of 84 bytes to `KNAS'
Jul 07 20:59:26-888776 util-scheduler-8620 DEBUG Adding task: 4140 / 0x4d5c9e8
Jul 07 20:59:26-888956 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:26-889162 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:59:26-889362 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:26-889540 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x4d5ca14
Jul 07 20:59:26-889777 cadet-p2p-8620 DEBUG QQQ  - {         ENCRYPTED} BCK on M9KEP6HP (->P00P)
Jul 07 20:59:26-889976 cadet-p2p-8620 DEBUG QQQ    payload {         KEEPALIVE}, 0
Jul 07 20:59:26-890155 cadet-p2p-8620 DEBUG QQQ    size: 84 bytes
Jul 07 20:59:26-890357 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:59:26-890615 util-scheduler-8620 DEBUG Checking readiness of task: 4139 / 0x4d5e5d8
Jul 07 20:59:26-890811 util-scheduler-8620 DEBUG Checking readiness of task: 4137 / 0x46620a0
Jul 07 20:59:26-891002 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-891192 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-891381 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-891570 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-891760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-891949 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-892137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-892328 util-scheduler-8620 DEBUG Running task: 4139 / 0x4d5e5d8
Jul 07 20:59:26-892513 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:26-892690 util-8620 DEBUG process_notify is running
Jul 07 20:59:26-892861 util-8620 DEBUG client_notify is running
Jul 07 20:59:26-893085 util-8620 DEBUG Transmitting message of type 168 and size 40 to statistics service.
Jul 07 20:59:26-893358 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:26-893569 util-scheduler-8620 DEBUG Running task: 4140 / 0x4d5c9e8
Jul 07 20:59:26-893777 util-scheduler-8620 DEBUG Adding task: 4141 / 0x4d5c9e8
Jul 07 20:59:26-893998 core-api-8620 DEBUG Adding SEND REQUEST for peer `KNAS' to message queue
Jul 07 20:59:26-894196 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:26-894400 util-scheduler-8620 DEBUG Adding task: 4142 / 0x46620a0
Jul 07 20:59:26-894641 util-scheduler-8620 DEBUG Checking readiness of task: 4142 / 0x46620a0
Jul 07 20:59:26-894835 util-scheduler-8620 DEBUG Checking readiness of task: 4137 / 0x46620a0
Jul 07 20:59:26-895025 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-895215 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-895405 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-895594 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-895784 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-895972 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-896161 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-896350 util-scheduler-8620 DEBUG Running task: 4142 / 0x46620a0
Jul 07 20:59:26-896533 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:26-896707 util-8620 DEBUG process_notify is running
Jul 07 20:59:26-896892 util-8620 DEBUG client_notify is running
Jul 07 20:59:26-897072 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:26-897286 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:26-897475 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:26-897715 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:26-897962 util-scheduler-8620 DEBUG Checking readiness of task: 4137 / 0x46620a0
Jul 07 20:59:26-898156 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-898346 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-898536 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-898725 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-898914 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-899103 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-899291 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-899481 util-scheduler-8620 DEBUG Running task: 4137 / 0x46620a0
Jul 07 20:59:26-899883 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:26-900112 util-scheduler-8620 DEBUG Adding task: 4143 / 0x4662248
Jul 07 20:59:26-900358 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-900550 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-900740 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-900931 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-901120 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-901331 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-901520 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-901711 util-scheduler-8620 DEBUG Running task: 4143 / 0x4662248
Jul 07 20:59:26-901900 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:26-902096 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:26-902310 core-api-8620 DEBUG Received notification about transmission readiness to `KNAS'.
Jul 07 20:59:26-902506 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:26-902702 util-scheduler-8620 DEBUG Adding task: 4144 / 0x46620a0
Jul 07 20:59:26-902887 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:26-903090 util-scheduler-8620 DEBUG Adding task: 4145 / 0x46620a0
Jul 07 20:59:26-903330 util-scheduler-8620 DEBUG Checking readiness of task: 4145 / 0x46620a0
Jul 07 20:59:26-903522 util-scheduler-8620 DEBUG Checking readiness of task: 4144 / 0x46620a0
Jul 07 20:59:26-903712 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:26-903902 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:26-904091 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:26-904281 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:26-904470 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:26-904658 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:26-904847 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:26-905049 util-scheduler-8620 DEBUG Running task: 4144 / 0x46620a0
Jul 07 20:59:26-905251 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:26-905427 util-8620 DEBUG process_notify is running
Jul 07 20:59:26-905596 util-8620 DEBUG client_notify is running
Jul 07 20:59:26-905779 util-scheduler-8620 DEBUG Canceling task: 4141 / 0x4d5c9e8
Jul 07 20:59:26-906051 core-api-8620 DEBUG Transmitting SEND request to `KNAS' with 84 bytes.
Jul 07 20:59:26-906266 cadet-p2p-8620 DEBUG Queue send towards KNAS (max 196)
Jul 07 20:59:26-906498 cadet-p2p-8620 DEBUG Checking 0x612e9d0 towards M9KEP6HP (->P00P)
Jul 07 20:59:26-906731 cadet-con-8620 DEBUG  checking sendability of BCK traffic on M9KEP6HP (->P00P)
Jul 07 20:59:26-906914 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:26-907089 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:26-907308 cadet-p2p-8620 DEBUG   on connection M9KEP6HP (->P00P) BCK
Jul 07 20:59:26-907486 cadet-p2p-8620 DEBUG   size 84 ok
Jul 07 20:59:26-907661 cadet-p2p-8620 DEBUG   payload ID 0
Jul 07 20:59:26-907942 cadet-p2p-8620 INFO snd {         ENCRYPTED} ({         KEEPALIVE} 0) on connection M9KEP6HP (->P00P) (0x53a5de0) BCK (size 84)
Jul 07 20:59:26-908136 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:26-908315 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:26-908501 cadet-con-8620 DEBUG  sent BCK {         ENCRYPTED}
Jul 07 20:59:26-908688 cadet-con-8620 DEBUG  C_P- 0x53a5de0 1
Jul 07 20:59:26-908916 cadet-con-8620 DEBUG GMC send BCK ACK on M9KEP6HP (->P00P)
Jul 07 20:59:26-909091 cadet-con-8620 DEBUG   getting from one connection
Jul 07 20:59:26-909285 cadet-con-8620 DEBUG   buffer available: 10
Jul 07 20:59:26-909457 cadet-con-8620 DEBUG   sending on channels...
Jul 07 20:59:26-909654 cadet-tun-8620 DEBUG GCT_unchoke_channels on P00P
Jul 07 20:59:26-909829 cadet-tun-8620 DEBUG  head: (nil)
Jul 07 20:59:26-910030 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS P00P
Jul 07 20:59:26-910209 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 20:59:26-910389 cadet-tun-8620 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 20:59:26-910567 cadet-tun-8620 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 20:59:26-910742 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:26-910910 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:26-911076 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:26-911306 cadet-tun-8620 DEBUG TTT  - M9KEP6HP (->P00P) [3] buf: 11/10 (qn 0/1)
Jul 07 20:59:26-911492 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:26-911668 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:59:26-911869 util-scheduler-8620 DEBUG Adding task: 4146 / 0x53a5de0
Jul 07 20:59:26-912115 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:26-912293 cadet-con-8620 DEBUG !  Q_N- 0x53a5e18 1
Jul 07 20:59:26-912470 cadet-con-8620 DEBUG !   accounting pid 0
Jul 07 20:59:26-912641 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:26-912822 cadet-p2p-8620 DEBUG   return 84
Jul 07 20:59:26-913020 cadet-p2p-8620 DEBUG QQQ Message queue towards KNAS
Jul 07 20:59:26-913214 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:26-913390 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:26-913590 cadet-p2p-8620 DEBUG QQQ End queue towards KNAS
Jul 07 20:59:26-913793 core-api-8620 DEBUG Transmitting SEND request to `KNAS' yielded 84 bytes.
Jul 07 20:59:26-913975 core-api-8620 DEBUG Produced SEND message to core with 84 bytes payload
Jul 07 20:59:26-914152 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:26-914340 util-8620 DEBUG Transmitting message of type 76 and size 140 to core service.
Jul 07 20:59:26-914583 util-8620 DEBUG Connection transmitted 140/140 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:27-043208 util-scheduler-8620 DEBUG Checking readiness of task: 4145 / 0x46620a0
Jul 07 20:59:27-043431 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:27-043630 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:27-043824 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:27-044017 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:27-044210 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:27-044401 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:27-044613 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:27-044808 util-scheduler-8620 DEBUG Running task: 4145 / 0x46620a0
Jul 07 20:59:27-045237 util-8620 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:27-045471 util-scheduler-8620 DEBUG Adding task: 4147 / 0x4662248
Jul 07 20:59:27-045724 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:27-045919 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:27-046112 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:27-046304 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:27-046496 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:27-046687 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:27-046879 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:27-047069 util-scheduler-8620 DEBUG Running task: 4147 / 0x4662248
Jul 07 20:59:27-047260 util-8620 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 20:59:27-047454 core-api-8620 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 20:59:27-047674 core-api-8620 DEBUG Received message of type 268 and size 40 from peer `KNAS'
Jul 07 20:59:27-047928 cadet-con-8620 INFO <-- {               ACK} on connection M9KEP6HP from KNAS
Jul 07 20:59:27-048180 cadet-con-8620 DEBUG  get next hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:27-048393 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:59:27-048634 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:27-048842 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:59:27-049026 cadet-con-8620 DEBUG   BCK ACK
Jul 07 20:59:27-049225 cadet-con-8620 DEBUG   ACK 100 (was 0)
Jul 07 20:59:27-049458 cadet-con-8620 DEBUG connection_unlock_queue BCK on M9KEP6HP (->P00P)
Jul 07 20:59:27-049690 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 20:59:27-049898 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 20:59:27-050083 cadet-p2p-8620 DEBUG   queue empty!
Jul 07 20:59:27-050260 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:27-050465 util-scheduler-8620 DEBUG Adding task: 4148 / 0x46620a0
Jul 07 20:59:30-921425 util-scheduler-8620 DEBUG Checking readiness of task: 4148 / 0x46620a0
Jul 07 20:59:30-921793 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:30-921992 util-scheduler-8620 DEBUG Checking readiness of task: 4068 / 0x4663d68
Jul 07 20:59:30-922191 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:30-922385 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:30-922578 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:30-922769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:30-922961 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:30-923158 util-scheduler-8620 DEBUG Running task: 4068 / 0x4663d68
Jul 07 20:59:30-923582 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:59:30-923839 util-scheduler-8620 DEBUG Adding task: 4149 / 0x4663f10
Jul 07 20:59:30-924120 util-scheduler-8620 DEBUG Checking readiness of task: 4148 / 0x46620a0
Jul 07 20:59:30-924318 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:30-924512 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:30-924704 util-scheduler-8620 DEBUG Checking readiness of task: 2985 / 0x4d5c418
Jul 07 20:59:30-924897 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:30-925092 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:30-925860 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:30-926118 util-scheduler-8620 DEBUG Running task: 2985 / 0x4d5c418
Jul 07 20:59:30-926530 util-8620 DEBUG receive_ready read 48/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:59:30-926747 util-8620 DEBUG Server receives 48 bytes from `<unbound UNIX client>'.
Jul 07 20:59:30-926948 util-8620 DEBUG Server-mst receives 48 bytes with 0 bytes already in private buffer
Jul 07 20:59:30-927231 util-8620 DEBUG Server-mst has 48 bytes left in inbound buffer
Jul 07 20:59:30-927425 util-8620 DEBUG Tokenizer gives server message of type 274 from client
Jul 07 20:59:30-927623 util-8620 DEBUG Server schedules transmission of 48-byte message of type 274 to client.
Jul 07 20:59:30-927865 util-scheduler-8620 DEBUG Adding task: 4150 / 0x4d5c578
Jul 07 20:59:30-928321 cadet-loc-8620 DEBUG Got a DESTROY CHANNEL from client!
Jul 07 20:59:30-928679 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:59:30-928963 cadet-loc-8620 DEBUG   for channel 80000004
Jul 07 20:59:30-929302 cadet-chn-8620 DEBUG  Client 0 is owner.
Jul 07 20:59:30-929626 cadet-chn-8620 INFO ===> {   CHANNEL_DESTROY} FWD on channel V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:59:30-929855 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:59:30-930063 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:30-930252 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:30-930448 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4132
Jul 07 20:59:30-930636 cadet-tun-8620 DEBUG TTT  tq_head 0x59f45c0, tq_tail 0x59f45c0
Jul 07 20:59:30-930820 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:30-930994 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:30-931231 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:59:30-931416 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:30-931654 cadet-tun-8620 DEBUG TTT  - 2FDYFV0X (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:30-931840 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:30-932043 cadet-tun-8620 DEBUG queue data on Tunnel V8XX
Jul 07 20:59:30-932242 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:30-932420 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:30-932603 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4132
Jul 07 20:59:30-932784 cadet-tun-8620 DEBUG TTT  tq_head 0x59f45c0, tq_tail 0x59f45c0
Jul 07 20:59:30-932962 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:30-933131 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:30-933376 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:59:30-933548 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:30-933777 cadet-tun-8620 DEBUG TTT  - 2FDYFV0X (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:30-933961 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:30-934177 cadet-chn-8620 DEBUG destroying channel V8XX:1073741824
Jul 07 20:59:30-934388 cadet-chn-8620 DEBUG Channel V8XX:40000000 (0x5845ae0)
Jul 07 20:59:30-934576 cadet-chn-8620 DEBUG   root (nil)/0x5845d90
Jul 07 20:59:30-934755 cadet-chn-8620 DEBUG   dest (nil)/(nil)
Jul 07 20:59:30-934966 cadet-chn-8620 DEBUG channel message sent callback {    CHANNEL_CREATE}
Jul 07 20:59:30-935160 cadet-chn-8620 DEBUG !!! SENT {    CHANNEL_CREATE}
Jul 07 20:59:30-935358 cadet-tun-8620 DEBUG Removing channel 0x5845ae0 from tunnel 0x52cbfb8
Jul 07 20:59:30-935589 cadet-tun-8620 DEBUG  found! V8XX:19 gid:40000000 (80000004 / 0)
Jul 07 20:59:30-935873 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:30-936099 util-scheduler-8620 DEBUG Adding task: 4151 / 0x4d5e5d8
Jul 07 20:59:30-936317 cadet-tun-8620 DEBUG Tunnel V8XX destroy if empty
Jul 07 20:59:30-936518 cadet-tun-8620 DEBUG Tunnel V8XX empty: destroying scheduled
Jul 07 20:59:30-936723 util-scheduler-8620 DEBUG Adding task: 4152 / 0x52cbfb8
Jul 07 20:59:30-936929 cadet-tun-8620 DEBUG Scheduled destroy of 0x52cbfb8 as 1038
Jul 07 20:59:30-937126 util-scheduler-8620 DEBUG Canceling task: 4150 / 0x4d5c578
Jul 07 20:59:30-937380 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:59:30-937565 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:59:30-937774 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:59:30-937981 util-scheduler-8620 DEBUG Adding task: 4153 / 0x4d5c418
Jul 07 20:59:30-938182 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:59:30-938415 util-scheduler-8620 DEBUG Running task: 4148 / 0x46620a0
Jul 07 20:59:30-938838 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:30-939071 util-scheduler-8620 DEBUG Adding task: 4154 / 0x4662248
Jul 07 20:59:30-939280 util-scheduler-8620 DEBUG Running task: 4149 / 0x4663f10
Jul 07 20:59:30-939474 util-8620 DEBUG Received message of type 362 and size 40 from transport service.
Jul 07 20:59:30-939668 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:30-939872 util-scheduler-8620 DEBUG Adding task: 4155 / 0x4663d68
Jul 07 20:59:30-940253 transport-api-8620 DEBUG Receiving `DISCONNECT' message for `V8XX'.
Jul 07 20:59:30-940563 util-scheduler-8620 DEBUG Checking readiness of task: 4155 / 0x4663d68
Jul 07 20:59:30-940762 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:30-940955 util-scheduler-8620 DEBUG Checking readiness of task: 4151 / 0x4d5e5d8
Jul 07 20:59:30-941148 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:30-941373 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:30-941564 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:30-941754 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:30-941942 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:30-942134 util-scheduler-8620 DEBUG Running task: 4151 / 0x4d5e5d8
Jul 07 20:59:30-942321 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:30-942498 util-8620 DEBUG process_notify is running
Jul 07 20:59:30-942672 util-8620 DEBUG client_notify is running
Jul 07 20:59:30-942901 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:59:30-943261 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:30-943475 util-scheduler-8620 DEBUG Running task: 4154 / 0x4662248
Jul 07 20:59:30-943664 util-8620 DEBUG Received message of type 68 and size 40 from core service.
Jul 07 20:59:30-943861 core-api-8620 DEBUG Processing message of type 68 and size 40 from core service
Jul 07 20:59:30-944074 core-api-8620 DEBUG Received notification about disconnect from `V8XX'.
Jul 07 20:59:30-944319 cadet-p2p-8620 INFO DISCONNECTED GN10 <= V8XX
Jul 07 20:59:30-944581 cadet-p2p-8620 DEBUG   notifying 2FDYFV0X (->V8XX) due to V8XX
Jul 07 20:59:30-944831 cadet-con-8620 DEBUG  notify broken on 2FDYFV0X (->V8XX) due to V8XX disconnect
Jul 07 20:59:30-945066 cadet-con-8620 DEBUG  get prev hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:30-945299 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:59:30-945535 cadet-con-8620 DEBUG destroying connection 2FDYFV0X (->V8XX)
Jul 07 20:59:30-945715 cadet-con-8620 DEBUG  fc's f: 0x59e880c, b: 0x59e8840
Jul 07 20:59:30-945898 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:59:30-946125 cadet-con-8620 DEBUG  *** Cancel FWD queues for connection 2FDYFV0X (->V8XX)
Jul 07 20:59:30-946357 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:30-946563 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:30-946801 cadet-con-8620 DEBUG  *** Cancel BCK queues for connection 2FDYFV0X (->V8XX)
Jul 07 20:59:30-947033 cadet-con-8620 DEBUG  get prev hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:30-947238 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:59:30-947473 cadet-con-8620 DEBUG  get next hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:30-947682 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:30-947937 cadet-p2p-8620 DEBUG removing connection 2FDYFV0X (->V8XX)
Jul 07 20:59:30-948141 cadet-p2p-8620 DEBUG from peer V8XX
Jul 07 20:59:30-948342 cadet-p2p-8620 DEBUG peer V8XX ok, has 1 connections.
Jul 07 20:59:30-948587 cadet-con-8620 DEBUG  get prev hop 2FDYFV0X (->V8XX) [0/2]
Jul 07 20:59:30-948791 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:59:30-949036 cadet-p2p-8620 DEBUG removing connection 2FDYFV0X (->V8XX)
Jul 07 20:59:30-949256 cadet-p2p-8620 DEBUG from peer GN10
Jul 07 20:59:30-949455 cadet-p2p-8620 DEBUG peer GN10 ok, has 2 connections.
Jul 07 20:59:30-949648 cadet-con-8620 DEBUG  fc tasks f: 0, b: 0
Jul 07 20:59:30-949897 cadet-tun-8620 DEBUG Removing connection 2FDYFV0X (->V8XX) from tunnel V8XX
Jul 07 20:59:30-950119 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_READY => CADET_TUNNEL_WAITING
Jul 07 20:59:30-950322 util-scheduler-8620 DEBUG Canceling task: 4138 / 0x59e8808
Jul 07 20:59:30-950523 util-scheduler-8620 DEBUG Canceling task: 2998 / 0x59e8808
Jul 07 20:59:30-950813 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:30-951025 util-scheduler-8620 DEBUG Adding task: 4156 / 0x4d5e5d8
Jul 07 20:59:30-951325 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:30-951533 util-scheduler-8620 DEBUG Adding task: 4157 / 0x46620a0
Jul 07 20:59:30-951801 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:30-951997 util-scheduler-8620 DEBUG Checking readiness of task: 4156 / 0x4d5e5d8
Jul 07 20:59:30-952192 util-scheduler-8620 DEBUG Checking readiness of task: 4155 / 0x4663d68
Jul 07 20:59:30-952381 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:30-952571 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:30-952762 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:30-952951 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:30-953140 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:30-953353 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:30-953547 util-scheduler-8620 DEBUG Running task: 4156 / 0x4d5e5d8
Jul 07 20:59:30-953735 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:30-953911 util-8620 DEBUG process_notify is running
Jul 07 20:59:30-954082 util-8620 DEBUG client_notify is running
Jul 07 20:59:30-954322 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:30-954540 util-scheduler-8620 DEBUG Adding task: 4158 / 0x4d5e5d8
Jul 07 20:59:30-954749 util-8620 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 20:59:30-955126 util-8620 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:30-955339 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x4d5e5d8).
Jul 07 20:59:30-955621 util-scheduler-8620 DEBUG Checking readiness of task: 4158 / 0x4d5e5d8
Jul 07 20:59:30-955825 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:30-956023 util-scheduler-8620 DEBUG Checking readiness of task: 4155 / 0x4663d68
Jul 07 20:59:30-956220 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:30-956416 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:30-956613 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:30-956810 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:30-957006 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:30-957239 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:30-957445 util-scheduler-8620 DEBUG Running task: 4158 / 0x4d5e5d8
Jul 07 20:59:30-957637 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:30-957824 util-8620 DEBUG process_notify is running
Jul 07 20:59:30-958001 util-8620 DEBUG client_notify is running
Jul 07 20:59:30-958285 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:59:30-958544 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:31-727381 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:31-727736 util-scheduler-8620 DEBUG Checking readiness of task: 4155 / 0x4663d68
Jul 07 20:59:31-727944 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:31-728138 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:31-728331 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:31-728525 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:31-728715 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:31-728905 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:31-729097 util-scheduler-8620 DEBUG Running task: 4132 / 0x52cbfb8
Jul 07 20:59:31-729360 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:31-729618 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:31-729828 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:31-730029 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:31-731061 cadet-tun-8620 WARNING 


Jul 07 20:59:31-732197 cadet-8620 ERROR Assertion failed at gnunet-service-cadet_tunnel.c:1272.
Jul 07 20:59:31-733830 cadet-tun-8620 WARNING sending {      KX_EPHEMERAL}
Jul 07 20:59:31-734432 cadet-tun-8620 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:31-734624 cadet-tun-8620 WARNING TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:31-734812 cadet-tun-8620 WARNING TTT  kx_ctx 0x5789e78, rekey_task 0
Jul 07 20:59:31-734997 cadet-tun-8620 WARNING TTT  tq_head 0x613da50, tq_tail 0x613da50
Jul 07 20:59:31-735178 cadet-tun-8620 WARNING TTT  destroy 4152
Jul 07 20:59:31-735350 cadet-tun-8620 WARNING TTT  channels:
Jul 07 20:59:31-735518 cadet-tun-8620 WARNING TTT  connections:
Jul 07 20:59:31-735686 cadet-tun-8620 WARNING TTT DEBUG TUNNEL END
Jul 07 20:59:31-737317 cadet-p2p-8620 WARNING PPP DEBUG PEER V8XX
Jul 07 20:59:31-738585 cadet-p2p-8620 WARNING PPP last contact Mon Jul 07 20:59:30 2014
Jul 07 20:59:31-739751 cadet-p2p-8620 WARNING PPP core transmit handle (nil)
Jul 07 20:59:31-740775 cadet-p2p-8620 WARNING PPP DHT GET handle 0x59e53b0
Jul 07 20:59:31-741900 cadet-p2p-8620 WARNING PPP # connections over link to peer: 0
Jul 07 20:59:31-742437 cadet-p2p-8620 WARNING QQQ Message queue towards V8XX
Jul 07 20:59:31-742622 cadet-p2p-8620 WARNING QQQ  queue length: 0
Jul 07 20:59:31-742802 cadet-p2p-8620 WARNING QQQ  core tmt rdy: (nil)
Jul 07 20:59:31-743005 cadet-p2p-8620 WARNING QQQ End queue towards V8XX
Jul 07 20:59:31-743955 cadet-p2p-8620 WARNING PPP DEBUG END
Jul 07 20:59:31-745095 cadet-tun-8620 WARNING 


Jul 07 20:59:31-745611 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:31-745827 util-scheduler-8620 DEBUG Adding task: 4159 / 0x52cbfb8
Jul 07 20:59:35-551650 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:35-552032 util-scheduler-8620 DEBUG Checking readiness of task: 4155 / 0x4663d68
Jul 07 20:59:35-552230 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:35-552427 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:35-552619 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:35-552810 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:35-553001 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:35-553213 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:35-553504 util-scheduler-8620 DEBUG Running task: 4155 / 0x4663d68
Jul 07 20:59:35-554035 util-8620 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:59:35-554329 util-scheduler-8620 DEBUG Adding task: 4160 / 0x4663f10
Jul 07 20:59:35-554611 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:35-554804 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:35-554995 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:35-555186 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:35-555375 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:35-555564 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:35-555752 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:35-555941 util-scheduler-8620 DEBUG Running task: 4160 / 0x4663f10
Jul 07 20:59:35-556134 util-8620 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 20:59:35-556359 util-scheduler-8620 DEBUG Adding task: 4161 / 0x4663f10
Jul 07 20:59:35-556585 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX'.
Jul 07 20:59:35-556796 transport-api-8620 DEBUG Creating entry for neighbour `V8XX'.
Jul 07 20:59:35-556992 util-bandwidth-8620 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 20:59:35-557185 util-bandwidth-8620 DEBUG Tracker 0x6143b38 initialized with 1024 Bps and max carry 5
Jul 07 20:59:35-557450 util-scheduler-8620 DEBUG Adding task: 4162 / 0x6143b38
Jul 07 20:59:35-557677 transport-api-8620 DEBUG Receiving `CONNECT' message for `V8XX' with quota 10509
Jul 07 20:59:35-557870 util-bandwidth-8620 DEBUG Tracker 0x6143b38 bandwidth changed to 10509 Bps
Jul 07 20:59:35-558107 util-bandwidth-8620 DEBUG Tracker 0x6143b38 updated, have 1024 Bps, last update was 883 µs ago
Jul 07 20:59:35-558320 util-scheduler-8620 DEBUG Canceling task: 4162 / 0x6143b38
Jul 07 20:59:35-558534 util-scheduler-8620 DEBUG Adding task: 4163 / 0x6143b38
Jul 07 20:59:35-558771 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:35-558963 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:35-559154 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:35-559345 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:35-559534 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:35-559723 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:35-559911 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:35-560101 util-scheduler-8620 DEBUG Running task: 4161 / 0x4663f10
Jul 07 20:59:35-560289 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:59:35-560478 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:35-560691 util-scheduler-8620 DEBUG Adding task: 4164 / 0x4663d68
Jul 07 20:59:35-560878 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:59:35-561093 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 10509
Jul 07 20:59:35-561305 util-bandwidth-8620 DEBUG Tracker 0x6143b38 bandwidth changed to 10509 Bps
Jul 07 20:59:35-561533 util-bandwidth-8620 DEBUG Tracker 0x6143b38 updated, have 10509 Bps, last update was 3433 µs ago
Jul 07 20:59:35-561738 util-scheduler-8620 DEBUG Canceling task: 4163 / 0x6143b38
Jul 07 20:59:35-561950 util-scheduler-8620 DEBUG Adding task: 4165 / 0x6143b38
Jul 07 20:59:36-067154 util-scheduler-8620 DEBUG Checking readiness of task: 4164 / 0x4663d68
Jul 07 20:59:36-067408 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:36-067607 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:36-067801 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:36-067994 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:36-068187 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:36-068379 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:36-068593 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:36-068788 util-scheduler-8620 DEBUG Running task: 4164 / 0x4663d68
Jul 07 20:59:36-069322 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 20:59:36-069566 util-scheduler-8620 DEBUG Adding task: 4166 / 0x4663f10
Jul 07 20:59:36-069827 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:36-070023 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:36-070214 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:36-070407 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:36-070598 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:36-070790 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:36-070980 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:36-071170 util-scheduler-8620 DEBUG Running task: 4166 / 0x4663f10
Jul 07 20:59:36-071362 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 20:59:36-071556 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:36-071763 util-scheduler-8620 DEBUG Adding task: 4167 / 0x4663d68
Jul 07 20:59:36-071949 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 20:59:36-072166 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 10509
Jul 07 20:59:36-072358 util-bandwidth-8620 DEBUG Tracker 0x6143b38 bandwidth changed to 10509 Bps
Jul 07 20:59:36-072601 util-bandwidth-8620 DEBUG Tracker 0x6143b38 updated, have 10509 Bps, last update was 511 ms ago
Jul 07 20:59:36-072814 util-scheduler-8620 DEBUG Canceling task: 4165 / 0x6143b38
Jul 07 20:59:36-073029 util-scheduler-8620 DEBUG Adding task: 4168 / 0x6143b38
Jul 07 20:59:36-746594 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:36-746860 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:36-747349 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:36-747583 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:36-747822 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:36-748016 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:36-748206 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:36-748395 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:36-748587 util-scheduler-8620 DEBUG Running task: 4159 / 0x52cbfb8
Jul 07 20:59:36-748807 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:36-749063 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:36-749325 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:36-749528 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:36-749875 cadet-tun-8620 WARNING 


Jul 07 20:59:36-750150 cadet-8620 ERROR Assertion failed at gnunet-service-cadet_tunnel.c:1272.
Jul 07 20:59:36-750446 cadet-tun-8620 WARNING sending {      KX_EPHEMERAL}
Jul 07 20:59:36-750655 cadet-tun-8620 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:36-750840 cadet-tun-8620 WARNING TTT  cstate CADET_TUNNEL_WAITING, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:36-751025 cadet-tun-8620 WARNING TTT  kx_ctx 0x5789e78, rekey_task 0
Jul 07 20:59:36-751209 cadet-tun-8620 WARNING TTT  tq_head 0x613da50, tq_tail 0x613da50
Jul 07 20:59:36-751389 cadet-tun-8620 WARNING TTT  destroy 4152
Jul 07 20:59:36-751557 cadet-tun-8620 WARNING TTT  channels:
Jul 07 20:59:36-751724 cadet-tun-8620 WARNING TTT  connections:
Jul 07 20:59:36-751892 cadet-tun-8620 WARNING TTT DEBUG TUNNEL END
Jul 07 20:59:36-752259 cadet-p2p-8620 WARNING PPP DEBUG PEER V8XX
Jul 07 20:59:36-752649 cadet-p2p-8620 WARNING PPP last contact Mon Jul 07 20:59:30 2014
Jul 07 20:59:36-752982 cadet-p2p-8620 WARNING PPP core transmit handle (nil)
Jul 07 20:59:36-753382 cadet-p2p-8620 WARNING PPP DHT GET handle 0x59e53b0
Jul 07 20:59:36-753722 cadet-p2p-8620 WARNING PPP # connections over link to peer: 0
Jul 07 20:59:36-753935 cadet-p2p-8620 WARNING QQQ Message queue towards V8XX
Jul 07 20:59:36-754113 cadet-p2p-8620 WARNING QQQ  queue length: 0
Jul 07 20:59:36-754288 cadet-p2p-8620 WARNING QQQ  core tmt rdy: (nil)
Jul 07 20:59:36-754489 cadet-p2p-8620 WARNING QQQ End queue towards V8XX
Jul 07 20:59:36-754818 cadet-p2p-8620 WARNING PPP DEBUG END
Jul 07 20:59:36-755081 cadet-tun-8620 WARNING 


Jul 07 20:59:36-755323 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:36-755528 util-scheduler-8620 DEBUG Adding task: 4169 / 0x52cbfb8
Jul 07 20:59:40-312989 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-313368 util-scheduler-8620 DEBUG Checking readiness of task: 4157 / 0x46620a0
Jul 07 20:59:40-313567 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-313761 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-313954 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-314145 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-314336 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-314526 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-314722 util-scheduler-8620 DEBUG Running task: 4157 / 0x46620a0
Jul 07 20:59:40-315144 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:40-315396 util-scheduler-8620 DEBUG Adding task: 4170 / 0x4662248
Jul 07 20:59:40-315669 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-315863 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-316056 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-316246 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-316438 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-316627 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-316830 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-317020 util-scheduler-8620 DEBUG Running task: 4170 / 0x4662248
Jul 07 20:59:40-317239 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 20:59:40-317674 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 20:59:40-317902 core-api-8620 DEBUG Received notification about connection from `V8XX'.
Jul 07 20:59:40-318177 cadet-p2p-8620 INFO CONNECTED GN10 <= V8XX
Jul 07 20:59:40-318464 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:40-318681 util-scheduler-8620 DEBUG Adding task: 4171 / 0x4d5e5d8
Jul 07 20:59:40-318904 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:59:40-319086 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:59:40-319263 cadet-p2p-8620 DEBUG   added last
Jul 07 20:59:40-319485 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:59:40-319750 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:59:40-319947 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:59:40-320164 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:40-320366 util-scheduler-8620 DEBUG Adding task: 4172 / 0x46624e8
Jul 07 20:59:40-320550 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:59:40-320858 cadet-p2p-8620 DEBUG   path to use:  GN10 V8XX
Jul 07 20:59:40-321322 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:40-321536 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:40-321778 cadet-con-8620 DEBUG  get prev hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:40-321987 cadet-con-8620 DEBUG   ID: GN10 (1)
Jul 07 20:59:40-322222 cadet-con-8620 DEBUG register neighbors for connection 0V7ADHDH (->V8XX)
Jul 07 20:59:40-322412 cadet-8620 DEBUG PATH:
Jul 07 20:59:40-322595 cadet-8620 DEBUG   GN10
Jul 07 20:59:40-322782 cadet-8620 DEBUG   V8XX
Jul 07 20:59:40-322936 cadet-8620 DEBUG END
Jul 07 20:59:40-323106 cadet-con-8620 DEBUG own pos 0
Jul 07 20:59:40-323331 cadet-con-8620 DEBUG putting connection 0V7ADHDH (->V8XX) to next peer 0x4d64970
Jul 07 20:59:40-323541 cadet-con-8620 DEBUG next peer 0x4d64970 V8XX
Jul 07 20:59:40-323772 cadet-con-8620 DEBUG putting connection 0V7ADHDH (->V8XX) to prev peer 0x4d5be88
Jul 07 20:59:40-323980 cadet-con-8620 DEBUG prev peer 0x4d5be88 GN10
Jul 07 20:59:40-324208 cadet-p2p-8620 DEBUG adding connection 0V7ADHDH (->V8XX)
Jul 07 20:59:40-324409 cadet-p2p-8620 DEBUG to peer V8XX
Jul 07 20:59:40-324611 cadet-p2p-8620 DEBUG peer V8XX ok, has 0 connections.
Jul 07 20:59:40-324803 cadet-p2p-8620 DEBUG  now has 1 connections.
Jul 07 20:59:40-324977 cadet-p2p-8620 DEBUG result 1
Jul 07 20:59:40-325221 cadet-p2p-8620 DEBUG adding connection 0V7ADHDH (->V8XX)
Jul 07 20:59:40-326162 cadet-p2p-8620 DEBUG to peer GN10
Jul 07 20:59:40-326641 cadet-p2p-8620 DEBUG peer GN10 ok, has 1 connections.
Jul 07 20:59:40-326890 cadet-p2p-8620 DEBUG  now has 2 connections.
Jul 07 20:59:40-327118 cadet-p2p-8620 DEBUG result 1
Jul 07 20:59:40-327343 cadet-tun-8620 DEBUG add connection 0V7ADHDH (->V8XX)
Jul 07 20:59:40-327545 cadet-tun-8620 DEBUG  to tunnel V8XX
Jul 07 20:59:40-328562 util-scheduler-8620 DEBUG Adding task: 4173 / 0x52cbfb8
Jul 07 20:59:40-328829 cadet-con-8620 INFO ===> { CONNECTION_CREATE} on connection 0V7ADHDH (->V8XX)  (100 bytes)
Jul 07 20:59:40-329310 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0 (create)
Jul 07 20:59:40-329661 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:40-329871 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:40-330175 cadet-p2p-8620 INFO que { CONNECTION_CREATE} ( 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 100)
Jul 07 20:59:40-330539 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:40-331452 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:40-331642 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:40-331820 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:40-332029 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 20:59:40-332249 core-api-8620 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 20:59:40-332464 util-scheduler-8620 DEBUG Adding task: 4174 / 0x6146380
Jul 07 20:59:40-332645 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:40-332854 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:40-333032 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:40-333233 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:40-333476 cadet-p2p-8620 DEBUG QQQ  - { CONNECTION_CREATE} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:40-333664 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:59:40-333841 cadet-p2p-8620 DEBUG QQQ    size: 100 bytes
Jul 07 20:59:40-334043 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:40-334281 cadet-con-8620 DEBUG Connection 0V7ADHDH (->V8XX) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 20:59:40-334474 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:40-334684 util-scheduler-8620 DEBUG Adding task: 4175 / 0x46620a0
Jul 07 20:59:40-334947 util-scheduler-8620 DEBUG Checking readiness of task: 4175 / 0x46620a0
Jul 07 20:59:40-335142 util-scheduler-8620 DEBUG Checking readiness of task: 4171 / 0x4d5e5d8
Jul 07 20:59:40-335335 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-335526 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-335717 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-335909 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-336099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-336307 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-336498 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-336691 util-scheduler-8620 DEBUG Running task: 4171 / 0x4d5e5d8
Jul 07 20:59:40-336877 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:40-337058 util-8620 DEBUG process_notify is running
Jul 07 20:59:40-337256 util-8620 DEBUG client_notify is running
Jul 07 20:59:40-337486 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 20:59:40-337790 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:40-338004 util-scheduler-8620 DEBUG Running task: 4174 / 0x6146380
Jul 07 20:59:40-338214 util-scheduler-8620 DEBUG Adding task: 4176 / 0x6146380
Jul 07 20:59:40-338439 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:40-338642 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:40-338844 util-scheduler-8620 DEBUG Adding task: 4177 / 0x46620a0
Jul 07 20:59:40-339043 util-scheduler-8620 DEBUG Running task: 4173 / 0x52cbfb8
Jul 07 20:59:40-339244 util-scheduler-8620 DEBUG Running task: 4172 / 0x46624e8
Jul 07 20:59:40-339430 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:59:40-339622 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:59:40-339902 util-scheduler-8620 DEBUG Adding task: 4178 / 0x4663d68
Jul 07 20:59:40-340148 util-scheduler-8620 DEBUG Checking readiness of task: 4178 / 0x4663d68
Jul 07 20:59:40-340345 util-scheduler-8620 DEBUG Checking readiness of task: 4177 / 0x46620a0
Jul 07 20:59:40-340537 util-scheduler-8620 DEBUG Checking readiness of task: 4175 / 0x46620a0
Jul 07 20:59:40-340728 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-340919 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-341110 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-341328 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-341520 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-341709 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-341898 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-342102 util-scheduler-8620 DEBUG Running task: 4177 / 0x46620a0
Jul 07 20:59:40-342286 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:40-342462 util-8620 DEBUG process_notify is running
Jul 07 20:59:40-342632 util-8620 DEBUG client_notify is running
Jul 07 20:59:40-342813 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:40-343009 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:40-343201 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:40-343597 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:40-343811 util-scheduler-8620 DEBUG Running task: 4178 / 0x4663d68
Jul 07 20:59:40-343997 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:59:40-344174 util-8620 DEBUG process_notify is running
Jul 07 20:59:40-344345 util-8620 DEBUG client_notify is running
Jul 07 20:59:40-344522 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:59:40-344740 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:59:40-344955 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:40-345155 util-scheduler-8620 DEBUG Adding task: 4179 / 0x46624e8
Jul 07 20:59:40-345382 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:59:40-345586 util-scheduler-8620 DEBUG Canceling task: 4179 / 0x46624e8
Jul 07 20:59:40-345809 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:40-346007 util-scheduler-8620 DEBUG Adding task: 4180 / 0x46624e8
Jul 07 20:59:40-346209 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:59:40-346403 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:59:40-346845 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:59:40-347101 util-scheduler-8620 DEBUG Checking readiness of task: 4175 / 0x46620a0
Jul 07 20:59:40-347298 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-347490 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-347680 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-347872 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-348063 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-348253 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-348444 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-348635 util-scheduler-8620 DEBUG Running task: 4175 / 0x46620a0
Jul 07 20:59:40-349038 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:40-349291 util-scheduler-8620 DEBUG Adding task: 4181 / 0x4662248
Jul 07 20:59:40-349501 util-scheduler-8620 DEBUG Running task: 4180 / 0x46624e8
Jul 07 20:59:40-349685 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:59:40-349875 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:59:40-350074 util-scheduler-8620 DEBUG Adding task: 4182 / 0x4663d68
Jul 07 20:59:40-350313 util-scheduler-8620 DEBUG Checking readiness of task: 4182 / 0x4663d68
Jul 07 20:59:40-350508 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-350699 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-350890 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-351080 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-351272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-351463 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-351653 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-351846 util-scheduler-8620 DEBUG Running task: 4182 / 0x4663d68
Jul 07 20:59:40-352030 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:59:40-352206 util-8620 DEBUG process_notify is running
Jul 07 20:59:40-352376 util-8620 DEBUG client_notify is running
Jul 07 20:59:40-352582 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:59:40-352787 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:59:40-352982 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:59:40-353178 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:59:40-353606 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:59:40-353956 util-scheduler-8620 DEBUG Running task: 4181 / 0x4662248
Jul 07 20:59:40-354286 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:40-354619 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:40-354976 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:40-355318 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:40-355652 util-scheduler-8620 DEBUG Adding task: 4183 / 0x46620a0
Jul 07 20:59:40-355974 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:40-356312 util-scheduler-8620 DEBUG Adding task: 4184 / 0x46620a0
Jul 07 20:59:40-356697 util-scheduler-8620 DEBUG Checking readiness of task: 4184 / 0x46620a0
Jul 07 20:59:40-357050 util-scheduler-8620 DEBUG Checking readiness of task: 4183 / 0x46620a0
Jul 07 20:59:40-357316 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:40-357511 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:40-357703 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:40-357894 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:40-358085 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:40-358275 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:40-358467 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:40-358659 util-scheduler-8620 DEBUG Running task: 4183 / 0x46620a0
Jul 07 20:59:40-358843 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:40-359018 util-8620 DEBUG process_notify is running
Jul 07 20:59:40-359188 util-8620 DEBUG client_notify is running
Jul 07 20:59:40-359372 util-scheduler-8620 DEBUG Canceling task: 4176 / 0x6146380
Jul 07 20:59:40-359594 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 20:59:40-359812 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:40-360045 cadet-p2p-8620 DEBUG Checking 0x6148768 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:40-360279 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:40-360458 cadet-p2p-8620 DEBUG   size 100 ok
Jul 07 20:59:40-360629 cadet-p2p-8620 DEBUG   path create
Jul 07 20:59:40-360798 cadet-p2p-8620 DEBUG Sending CONNECTION CREATE...
Jul 07 20:59:40-360979 cadet-p2p-8620 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 20:59:40-361267 cadet-p2p-8620 INFO snd { CONNECTION_CREATE} ( 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 100)
Jul 07 20:59:40-361462 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:40-361644 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:40-361832 cadet-con-8620 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 20:59:40-362014 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 20:59:40-362224 util-scheduler-8620 DEBUG Adding task: 4185 / 0x6146c10
Jul 07 20:59:40-362462 cadet-con-8620 DEBUG next keepalive in 1 s
Jul 07 20:59:40-362636 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:40-362820 cadet-p2p-8620 DEBUG   return 100
Jul 07 20:59:40-363021 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:40-363196 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:40-363370 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:40-363568 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:40-363773 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 20:59:40-363957 core-api-8620 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 20:59:40-364136 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:40-364324 util-8620 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 20:59:40-364559 util-8620 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:41-182644 util-scheduler-8620 DEBUG Checking readiness of task: 4184 / 0x46620a0
Jul 07 20:59:41-183002 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-183211 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:41-183404 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-183596 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-183786 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-183976 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-184166 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-184361 util-scheduler-8620 DEBUG Running task: 4184 / 0x46620a0
Jul 07 20:59:41-184782 util-8620 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:41-185059 util-scheduler-8620 DEBUG Adding task: 4186 / 0x4662248
Jul 07 20:59:41-185362 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-185556 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:41-185748 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-185940 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-186131 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-186321 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-186512 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-186703 util-scheduler-8620 DEBUG Running task: 4186 / 0x4662248
Jul 07 20:59:41-186895 util-8620 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 20:59:41-187094 core-api-8620 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 20:59:41-187324 core-api-8620 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 20:59:41-187589 cadet-con-8620 INFO <-- {    CONNECTION_ACK} on connection 0V7ADHDH from V8XX
Jul 07 20:59:41-187805 cadet-con-8620 DEBUG   via peer V8XX
Jul 07 20:59:41-188048 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:41-188282 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:41-188468 cadet-con-8620 DEBUG   SYNACK
Jul 07 20:59:41-188701 cadet-con-8620 DEBUG Connection 0V7ADHDH (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 20:59:41-188890 cadet-con-8620 DEBUG Connection BCK reset timeout
Jul 07 20:59:41-189100 util-scheduler-8620 DEBUG Adding task: 4187 / 0x6146c10
Jul 07 20:59:41-189371 cadet-p2p-8620 DEBUG adding path [2] to peer V8XX
Jul 07 20:59:41-189552 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 20:59:41-189743 cadet-con-8620 DEBUG   Connection (SYN)ACK for us!
Jul 07 20:59:41-189917 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:41-190108 util-scheduler-8620 DEBUG Canceling task: 4185 / 0x6146c10
Jul 07 20:59:41-190322 util-scheduler-8620 DEBUG Adding task: 4188 / 0x6146c10
Jul 07 20:59:41-190561 cadet-con-8620 DEBUG next keepalive in 2 s
Jul 07 20:59:41-190795 cadet-con-8620 DEBUG Connection 0V7ADHDH (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 20:59:41-191035 cadet-con-8620 INFO ===> {           BCK ACK} on connection 0V7ADHDH (->V8XX)
Jul 07 20:59:41-191271 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:41-191477 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:41-191773 cadet-p2p-8620 INFO que {    CONNECTION_ACK} ( 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 36)
Jul 07 20:59:41-191971 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:41-192196 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:41-192380 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:41-192556 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:41-192761 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 20:59:41-192980 core-api-8620 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 20:59:41-193215 util-scheduler-8620 DEBUG Adding task: 4189 / 0x6146380
Jul 07 20:59:41-193397 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:41-193603 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:41-193779 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:41-193954 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:41-194193 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:41-194377 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:59:41-194554 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:59:41-194753 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:41-194964 cadet-tun-8620 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 20:59:41-195174 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:41-195386 util-scheduler-8620 DEBUG Adding task: 4190 / 0x46620a0
Jul 07 20:59:41-195633 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-195827 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-196019 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:41-196210 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-196409 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-196603 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-196809 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-197006 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-197229 util-scheduler-8620 DEBUG Running task: 4189 / 0x6146380
Jul 07 20:59:41-197451 util-scheduler-8620 DEBUG Adding task: 4191 / 0x6146380
Jul 07 20:59:41-197681 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:41-197884 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:41-198086 util-scheduler-8620 DEBUG Adding task: 4192 / 0x46620a0
Jul 07 20:59:41-198336 util-scheduler-8620 DEBUG Checking readiness of task: 4192 / 0x46620a0
Jul 07 20:59:41-198535 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-198727 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-198919 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:41-199110 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-199303 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-199494 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-199684 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-199871 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-200062 util-scheduler-8620 DEBUG Running task: 4192 / 0x46620a0
Jul 07 20:59:41-200246 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:41-200424 util-8620 DEBUG process_notify is running
Jul 07 20:59:41-200595 util-8620 DEBUG client_notify is running
Jul 07 20:59:41-200773 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:41-200970 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:41-201160 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:41-201507 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:41-319055 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-319409 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-319608 util-scheduler-8620 DEBUG Checking readiness of task: 4153 / 0x4d5c418
Jul 07 20:59:41-319804 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-319998 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-320193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-320386 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-320574 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-320769 util-scheduler-8620 DEBUG Running task: 4153 / 0x4d5c418
Jul 07 20:59:41-321162 util-8620 DEBUG receive_ready read 48/65535 bytes from `<unbound UNIX client>' (0x4d5c418)!
Jul 07 20:59:41-321411 util-8620 DEBUG Server receives 48 bytes from `<unbound UNIX client>'.
Jul 07 20:59:41-321607 util-8620 DEBUG Server-mst receives 48 bytes with 0 bytes already in private buffer
Jul 07 20:59:41-321794 util-8620 DEBUG Server-mst has 48 bytes left in inbound buffer
Jul 07 20:59:41-321997 util-8620 DEBUG Tokenizer gives server message of type 273 from client
Jul 07 20:59:41-322188 util-8620 DEBUG Server schedules transmission of 48-byte message of type 273 to client.
Jul 07 20:59:41-322429 util-scheduler-8620 DEBUG Adding task: 4193 / 0x4d5c578
Jul 07 20:59:41-322609 cadet-loc-8620 DEBUG 
Jul 07 20:59:41-322778 cadet-loc-8620 DEBUG new channel requested
Jul 07 20:59:41-322953 cadet-loc-8620 DEBUG   by client 0
Jul 07 20:59:41-323171 cadet-chn-8620 DEBUG   towards V8XX:19
Jul 07 20:59:41-323399 cadet-p2p-8620 DEBUG peer_connect towards V8XX
Jul 07 20:59:41-323669 transport-api-8620 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 20:59:41-323860 transport-api-8620 DEBUG Control transmit of 491 bytes requested
Jul 07 20:59:41-324082 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:41-324281 util-scheduler-8620 DEBUG Adding task: 4194 / 0x46624e8
Jul 07 20:59:41-324463 cadet-p2p-8620 DEBUG   some path exists
Jul 07 20:59:41-324809 cadet-p2p-8620 DEBUG   but is NULL, all paths are in use
Jul 07 20:59:41-325086 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:41-325327 util-scheduler-8620 DEBUG Adding task: 4195 / 0x4d5e5d8
Jul 07 20:59:41-325542 cadet-tun-8620 DEBUG Adding channel 0x6149888 to tunnel 0x52cbfb8
Jul 07 20:59:41-325738 cadet-tun-8620 DEBUG  adding 0x6149af8 to (nil)
Jul 07 20:59:41-326108 util-scheduler-8620 DEBUG Canceling task: 4152 / 0x52cbfb8
Jul 07 20:59:41-327132 cadet-tun-8620 DEBUG  undo destroy!
Jul 07 20:59:41-327564 cadet-chn-8620 DEBUG CREATED CHANNEL V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:41-327827 cadet-chn-8620 INFO ===> {    CHANNEL_CREATE} FWD on channel V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:41-328049 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:59:41-328251 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:41-328434 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:41-328619 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4169
Jul 07 20:59:41-328803 cadet-tun-8620 DEBUG TTT  tq_head 0x613da50, tq_tail 0x613da50
Jul 07 20:59:41-328982 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:41-329153 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:41-329397 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:41-329572 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:41-329812 cadet-tun-8620 DEBUG TTT  - 0V7ADHDH (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:41-329999 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:41-330199 cadet-tun-8620 DEBUG queue data on Tunnel V8XX
Jul 07 20:59:41-330398 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:41-330575 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:41-330757 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4169
Jul 07 20:59:41-330938 cadet-tun-8620 DEBUG TTT  tq_head 0x613da50, tq_tail 0x613da50
Jul 07 20:59:41-331116 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:41-331284 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:41-331497 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:41-331670 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:41-331896 cadet-tun-8620 DEBUG TTT  - 0V7ADHDH (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:41-332081 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:41-332289 util-scheduler-8620 DEBUG Canceling task: 4193 / 0x4d5c578
Jul 07 20:59:41-332481 util-8620 DEBUG GNUNET_SERVER_receive_done called while still in processing loop
Jul 07 20:59:41-332663 util-8620 DEBUG Server-mst leaves 0 bytes in private buffer
Jul 07 20:59:41-332869 util-8620 DEBUG Server re-enters receive loop, timeout: forever.
Jul 07 20:59:41-333074 util-scheduler-8620 DEBUG Adding task: 4196 / 0x4d5c418
Jul 07 20:59:41-333299 util-8620 DEBUG Server leaves instant processing loop: ret = 1, server = 0x45515e0, shutdown = 0, suspended = 0
Jul 07 20:59:41-333588 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-333805 util-scheduler-8620 DEBUG Checking readiness of task: 4195 / 0x4d5e5d8
Jul 07 20:59:41-334001 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-334191 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-334381 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-334570 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-334759 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-334947 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-335136 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-335328 util-scheduler-8620 DEBUG Running task: 4195 / 0x4d5e5d8
Jul 07 20:59:41-335513 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:41-335690 util-8620 DEBUG process_notify is running
Jul 07 20:59:41-335861 util-8620 DEBUG client_notify is running
Jul 07 20:59:41-336087 util-8620 DEBUG Transmitting message of type 168 and size 33 to statistics service.
Jul 07 20:59:41-336346 util-8620 DEBUG Connection transmitted 33/33 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:41-336557 util-scheduler-8620 DEBUG Running task: 4194 / 0x46624e8
Jul 07 20:59:41-336742 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:59:41-336932 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:59:41-337132 util-scheduler-8620 DEBUG Adding task: 4197 / 0x4663d68
Jul 07 20:59:41-337397 util-scheduler-8620 DEBUG Checking readiness of task: 4197 / 0x4663d68
Jul 07 20:59:41-337592 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-337782 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-337972 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-338161 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-338352 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-338541 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-338729 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-338916 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-339107 util-scheduler-8620 DEBUG Running task: 4197 / 0x4663d68
Jul 07 20:59:41-339289 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:59:41-339464 util-8620 DEBUG process_notify is running
Jul 07 20:59:41-339632 util-8620 DEBUG client_notify is running
Jul 07 20:59:41-339807 transport-api-8620 DEBUG Transmitting `HELLO' request.
Jul 07 20:59:41-340019 transport-api-8620 DEBUG Control transmit of 40 bytes requested
Jul 07 20:59:41-340231 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:41-340431 util-scheduler-8620 DEBUG Adding task: 4198 / 0x46624e8
Jul 07 20:59:41-340632 transport-api-8620 DEBUG Added 491 bytes of control message at 0
Jul 07 20:59:41-340830 util-scheduler-8620 DEBUG Canceling task: 4198 / 0x46624e8
Jul 07 20:59:41-341050 transport-api-8620 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 20:59:41-341268 util-scheduler-8620 DEBUG Adding task: 4199 / 0x46624e8
Jul 07 20:59:41-341453 transport-api-8620 DEBUG Transmitting 491 bytes to transport service
Jul 07 20:59:41-341646 util-8620 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 20:59:41-341893 util-8620 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:59:41-342144 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-342337 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-342527 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-342734 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-342924 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-343114 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-343303 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-343491 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-343679 util-scheduler-8620 DEBUG Running task: 4199 / 0x46624e8
Jul 07 20:59:41-343859 transport-api-8620 DEBUG Calling notify_transmit_ready
Jul 07 20:59:41-344051 util-8620 DEBUG Scheduling transmission (0x4663d68).
Jul 07 20:59:41-344248 util-scheduler-8620 DEBUG Adding task: 4200 / 0x4663d68
Jul 07 20:59:41-344485 util-scheduler-8620 DEBUG Checking readiness of task: 4200 / 0x4663d68
Jul 07 20:59:41-344679 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-344869 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-345070 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-345284 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-345475 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-345664 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-345852 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-346041 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-346231 util-scheduler-8620 DEBUG Running task: 4200 / 0x4663d68
Jul 07 20:59:41-346414 util-8620 DEBUG transmit_ready running (0x4663d68).
Jul 07 20:59:41-346587 util-8620 DEBUG process_notify is running
Jul 07 20:59:41-346756 util-8620 DEBUG client_notify is running
Jul 07 20:59:41-346962 transport-api-8620 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 20:59:41-347160 transport-api-8620 DEBUG Added 40 bytes of control message at 0
Jul 07 20:59:41-347351 transport-api-8620 DEBUG Transmitting 40 bytes to transport service
Jul 07 20:59:41-347544 util-8620 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 20:59:41-347785 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)
Jul 07 20:59:41-756080 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-756436 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-756631 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-756823 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-757014 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-757229 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-757420 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-757610 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-757802 util-scheduler-8620 DEBUG Running task: 4169 / 0x52cbfb8
Jul 07 20:59:41-758037 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:41-758294 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:41-758502 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:41-758701 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:41-758903 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:41-759137 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 20:59:41-759317 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:41-759536 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 20:59:41-759828 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 20:59:41-760024 cadet-con-8620 DEBUG   C_P+ 0x6146c10 1
Jul 07 20:59:41-760260 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:41-760493 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:41-760812 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 20:59:41-761011 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:41-761259 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:41-761446 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:41-761625 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:41-761830 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 20:59:41-762037 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:41-762214 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 20:59:41-762390 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:41-762631 cadet-p2p-8620 DEBUG QQQ  - {    CONNECTION_ACK} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:41-762816 cadet-p2p-8620 DEBUG QQQ    payload , 0
Jul 07 20:59:41-762993 cadet-p2p-8620 DEBUG QQQ    size: 36 bytes
Jul 07 20:59:41-763226 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:41-763420 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:41-763598 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:41-763796 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:41-764048 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:41-764255 util-scheduler-8620 DEBUG Adding task: 4201 / 0x52cbfb8
Jul 07 20:59:41-794509 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:41-794840 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:41-795037 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:41-795230 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:41-795430 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:41-795623 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:41-795812 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:41-796005 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:41-796198 util-scheduler-8620 DEBUG Running task: 4168 / 0x6143b38
Jul 07 20:59:43-191889 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-192264 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:43-192461 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-192652 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-192846 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-193037 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-193246 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-193440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-193633 util-scheduler-8620 DEBUG Running task: 4188 / 0x6146c10
Jul 07 20:59:43-193904 cadet-con-8620 DEBUG FWD keepalive for 0V7ADHDH (->V8XX)
Jul 07 20:59:43-194137 cadet-con-8620 INFO keepalive FWD for connection 0V7ADHDH (->V8XX)
Jul 07 20:59:43-194420 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 20:59:43-194638 util-scheduler-8620 DEBUG Adding task: 4202 / 0x4d5e5d8
Jul 07 20:59:43-194853 cadet-tun-8620 DEBUG GMT Send on Tunnel V8XX
Jul 07 20:59:43-195054 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:43-195237 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:43-195420 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4201
Jul 07 20:59:43-195602 cadet-tun-8620 DEBUG TTT  tq_head 0x613da50, tq_tail 0x614f300
Jul 07 20:59:43-195844 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:43-196053 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:43-196688 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:43-197088 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:43-197538 cadet-tun-8620 DEBUG TTT  - 0V7ADHDH (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:43-197767 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:43-197976 cadet-tun-8620 DEBUG queue data on Tunnel V8XX
Jul 07 20:59:43-198180 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 20:59:43-198362 cadet-tun-8620 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_SENT
Jul 07 20:59:43-198547 cadet-tun-8620 DEBUG TTT  kx_ctx 0x5789e78, rekey_task 4201
Jul 07 20:59:43-198731 cadet-tun-8620 DEBUG TTT  tq_head 0x613da50, tq_tail 0x614f300
Jul 07 20:59:43-198910 cadet-tun-8620 DEBUG TTT  destroy 0
Jul 07 20:59:43-199080 cadet-tun-8620 DEBUG TTT  channels:
Jul 07 20:59:43-199295 cadet-tun-8620 DEBUG TTT  - V8XX:19 gid:40000001 (80000005 / 0)
Jul 07 20:59:43-199468 cadet-tun-8620 DEBUG TTT  connections:
Jul 07 20:59:43-199697 cadet-tun-8620 DEBUG TTT  - 0V7ADHDH (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 20:59:43-199882 cadet-tun-8620 DEBUG TTT DEBUG TUNNEL END
Jul 07 20:59:43-200179 util-scheduler-8620 DEBUG Checking readiness of task: 4202 / 0x4d5e5d8
Jul 07 20:59:43-200379 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-200570 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:43-200761 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-200950 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-201154 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-201370 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-201560 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-201749 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-201943 util-scheduler-8620 DEBUG Running task: 4202 / 0x4d5e5d8
Jul 07 20:59:43-202129 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 20:59:43-202309 util-8620 DEBUG process_notify is running
Jul 07 20:59:43-202481 util-8620 DEBUG client_notify is running
Jul 07 20:59:43-202714 util-8620 DEBUG Transmitting message of type 168 and size 40 to statistics service.
Jul 07 20:59:43-203091 util-8620 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 20:59:43-972995 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-973390 util-scheduler-8620 DEBUG Checking readiness of task: 4190 / 0x46620a0
Jul 07 20:59:43-973594 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-973786 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-973980 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-974173 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-974368 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-974566 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-974761 util-scheduler-8620 DEBUG Running task: 4190 / 0x46620a0
Jul 07 20:59:43-975183 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:43-975441 util-scheduler-8620 DEBUG Adding task: 4203 / 0x4662248
Jul 07 20:59:43-975721 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-975914 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-976105 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-976295 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-976485 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-976674 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-976863 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-977082 util-scheduler-8620 DEBUG Running task: 4203 / 0x4662248
Jul 07 20:59:43-977298 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:43-977499 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:43-977731 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:43-977936 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:43-978143 util-scheduler-8620 DEBUG Adding task: 4204 / 0x46620a0
Jul 07 20:59:43-978332 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:43-978538 util-scheduler-8620 DEBUG Adding task: 4205 / 0x46620a0
Jul 07 20:59:43-978782 util-scheduler-8620 DEBUG Checking readiness of task: 4205 / 0x46620a0
Jul 07 20:59:43-978973 util-scheduler-8620 DEBUG Checking readiness of task: 4204 / 0x46620a0
Jul 07 20:59:43-979164 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-979353 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-979542 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-979731 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-979920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-980108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-980296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-980487 util-scheduler-8620 DEBUG Running task: 4204 / 0x46620a0
Jul 07 20:59:43-980670 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:43-980848 util-8620 DEBUG process_notify is running
Jul 07 20:59:43-981021 util-8620 DEBUG client_notify is running
Jul 07 20:59:43-981234 util-scheduler-8620 DEBUG Canceling task: 4191 / 0x6146380
Jul 07 20:59:43-981465 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 20:59:43-981690 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:43-981930 cadet-p2p-8620 DEBUG Checking 0x614d548 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:43-982228 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:43-982455 cadet-p2p-8620 DEBUG   size 36 ok
Jul 07 20:59:43-982666 cadet-p2p-8620 DEBUG   path ack
Jul 07 20:59:43-982880 cadet-p2p-8620 DEBUG Sending CONNECTION ACK...
Jul 07 20:59:43-983128 cadet-p2p-8620 DEBUG CONNECTION ACK sent!
Jul 07 20:59:43-983432 cadet-p2p-8620 INFO snd {    CONNECTION_ACK} ( 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 36)
Jul 07 20:59:43-983631 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:43-983811 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:43-983999 cadet-con-8620 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 20:59:43-984182 cadet-con-8620 DEBUG  C_P- 0x6146c10 2
Jul 07 20:59:43-984369 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:43-984592 cadet-p2p-8620 DEBUG Checking 0x6151648 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:43-984830 cadet-p2p-8620 DEBUG Checking 0x6151648 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:43-985009 cadet-p2p-8620 DEBUG   more data!
Jul 07 20:59:43-985237 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:43-985458 util-scheduler-8620 DEBUG Adding task: 4206 / 0x6146380
Jul 07 20:59:43-985637 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:43-985813 cadet-p2p-8620 DEBUG   return 36
Jul 07 20:59:43-986010 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:43-986184 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:43-986358 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:43-986596 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:43-986790 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:43-986967 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:43-987164 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:43-987390 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 20:59:43-987573 core-api-8620 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 20:59:43-987776 util-scheduler-8620 DEBUG Adding task: 4207 / 0x6146380
Jul 07 20:59:43-987995 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:43-988191 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:43-988392 util-scheduler-8620 DEBUG Adding task: 4208 / 0x46620a0
Jul 07 20:59:43-988591 util-8620 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 20:59:43-989346 util-8620 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:43-989547 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 20:59:43-989801 util-scheduler-8620 DEBUG Checking readiness of task: 4208 / 0x46620a0
Jul 07 20:59:43-989996 util-scheduler-8620 DEBUG Checking readiness of task: 4205 / 0x46620a0
Jul 07 20:59:43-990187 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-990376 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-990565 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-990755 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-990943 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-991133 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-991321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-991511 util-scheduler-8620 DEBUG Running task: 4208 / 0x46620a0
Jul 07 20:59:43-991694 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:43-991872 util-8620 DEBUG process_notify is running
Jul 07 20:59:43-992042 util-8620 DEBUG client_notify is running
Jul 07 20:59:43-992221 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:43-992415 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:43-992605 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:43-992885 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:43-993091 util-scheduler-8620 DEBUG Running task: 4206 / 0x6146380
Jul 07 20:59:43-993316 util-scheduler-8620 DEBUG Canceling task: 4207 / 0x6146380
Jul 07 20:59:43-993531 util-scheduler-8620 DEBUG Adding task: 4209 / 0x6146380
Jul 07 20:59:43-993749 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:43-993944 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:43-994147 util-scheduler-8620 DEBUG Adding task: 4210 / 0x46620a0
Jul 07 20:59:43-994390 util-scheduler-8620 DEBUG Checking readiness of task: 4210 / 0x46620a0
Jul 07 20:59:43-994583 util-scheduler-8620 DEBUG Checking readiness of task: 4205 / 0x46620a0
Jul 07 20:59:43-994774 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:43-994964 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:43-995156 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:43-995349 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:43-995543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:43-995735 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:43-995925 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:43-996116 util-scheduler-8620 DEBUG Running task: 4210 / 0x46620a0
Jul 07 20:59:43-996299 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:43-996473 util-8620 DEBUG process_notify is running
Jul 07 20:59:43-996641 util-8620 DEBUG client_notify is running
Jul 07 20:59:43-996818 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:43-997029 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:43-997240 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:43-997526 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:44-103186 util-scheduler-8620 DEBUG Checking readiness of task: 4205 / 0x46620a0
Jul 07 20:59:44-103503 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:44-103700 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:44-103893 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:44-104084 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:44-104276 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:44-104466 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:44-104659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:44-104852 util-scheduler-8620 DEBUG Running task: 4205 / 0x46620a0
Jul 07 20:59:44-105285 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:44-105525 util-scheduler-8620 DEBUG Adding task: 4211 / 0x4662248
Jul 07 20:59:44-105785 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:44-105978 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:44-106168 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:44-106357 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:44-106547 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:44-106736 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:44-106924 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:44-107113 util-scheduler-8620 DEBUG Running task: 4211 / 0x4662248
Jul 07 20:59:44-107302 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:44-107500 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:44-107720 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:44-107922 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:44-108123 util-scheduler-8620 DEBUG Adding task: 4212 / 0x46620a0
Jul 07 20:59:44-108309 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:44-108511 util-scheduler-8620 DEBUG Adding task: 4213 / 0x46620a0
Jul 07 20:59:44-108753 util-scheduler-8620 DEBUG Checking readiness of task: 4213 / 0x46620a0
Jul 07 20:59:44-108946 util-scheduler-8620 DEBUG Checking readiness of task: 4212 / 0x46620a0
Jul 07 20:59:44-109138 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:44-109350 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:44-109540 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:44-109731 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:44-109920 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:44-110108 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:44-110296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:44-110488 util-scheduler-8620 DEBUG Running task: 4212 / 0x46620a0
Jul 07 20:59:44-110672 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:44-110848 util-8620 DEBUG process_notify is running
Jul 07 20:59:44-111017 util-8620 DEBUG client_notify is running
Jul 07 20:59:44-111201 util-scheduler-8620 DEBUG Canceling task: 4209 / 0x6146380
Jul 07 20:59:44-111424 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:44-111641 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:44-111898 cadet-p2p-8620 DEBUG Checking 0x6151648 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:44-112131 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:44-112309 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:44-112497 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:44-112781 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 20:59:44-112975 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:44-113155 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:44-113365 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:44-113554 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 20:59:44-113731 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:44-113932 util-scheduler-8620 DEBUG Adding task: 4214 / 0x6146c10
Jul 07 20:59:44-114183 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:44-114354 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:44-114532 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:44-114734 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:44-114909 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:44-115083 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:44-115281 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:44-115484 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:44-115667 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:44-115845 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:44-116033 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:44-116280 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:46-767042 util-scheduler-8620 DEBUG Checking readiness of task: 4213 / 0x46620a0
Jul 07 20:59:46-767390 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:46-767586 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:46-767777 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:46-767969 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:46-768159 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:46-768348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:46-768538 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:46-768730 util-scheduler-8620 DEBUG Running task: 4201 / 0x52cbfb8
Jul 07 20:59:46-768964 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:46-769243 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:46-769450 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:46-769651 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:46-769853 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:46-770087 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 20:59:46-770268 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:46-770489 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 20:59:46-770779 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 20:59:46-770990 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 20:59:46-771227 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:46-771435 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:46-771755 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 20:59:46-771955 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:46-772179 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:46-772362 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:46-772538 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:46-772768 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:46-772984 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:46-773235 util-scheduler-8620 DEBUG Adding task: 4215 / 0x6146380
Jul 07 20:59:46-773419 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:46-773624 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:46-773800 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:46-773975 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:46-774212 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:46-774408 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:46-774585 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:46-774784 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:46-775028 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:46-775225 util-scheduler-8620 DEBUG Adding task: 4216 / 0x52cbfb8
Jul 07 20:59:46-775483 util-scheduler-8620 DEBUG Checking readiness of task: 4213 / 0x46620a0
Jul 07 20:59:46-775676 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:46-775866 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:46-776055 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:46-776245 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:46-776434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:46-776624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:46-776811 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:46-777001 util-scheduler-8620 DEBUG Running task: 4215 / 0x6146380
Jul 07 20:59:46-777231 util-scheduler-8620 DEBUG Adding task: 4217 / 0x6146380
Jul 07 20:59:46-777455 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:46-777657 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:46-777864 util-scheduler-8620 DEBUG Adding task: 4218 / 0x46620a0
Jul 07 20:59:46-778108 util-scheduler-8620 DEBUG Checking readiness of task: 4218 / 0x46620a0
Jul 07 20:59:46-778302 util-scheduler-8620 DEBUG Checking readiness of task: 4213 / 0x46620a0
Jul 07 20:59:46-778493 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:46-778683 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:46-778873 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:46-779062 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:46-779252 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:46-779441 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:46-779629 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:46-779821 util-scheduler-8620 DEBUG Running task: 4218 / 0x46620a0
Jul 07 20:59:46-780004 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:46-780182 util-8620 DEBUG process_notify is running
Jul 07 20:59:46-780354 util-8620 DEBUG client_notify is running
Jul 07 20:59:46-780533 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:46-780729 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:46-780919 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:46-781171 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:48-083421 util-scheduler-8620 DEBUG Checking readiness of task: 4213 / 0x46620a0
Jul 07 20:59:48-083776 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:48-083975 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:48-084176 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:48-084407 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:48-084620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:48-084813 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:48-085004 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:48-085227 util-scheduler-8620 DEBUG Running task: 4213 / 0x46620a0
Jul 07 20:59:48-085651 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:48-085902 util-scheduler-8620 DEBUG Adding task: 4219 / 0x4662248
Jul 07 20:59:48-086175 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:48-086371 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:48-086564 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:48-086756 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:48-086949 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:48-087141 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:48-087332 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:48-087523 util-scheduler-8620 DEBUG Running task: 4219 / 0x4662248
Jul 07 20:59:48-087715 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:48-087915 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:48-088147 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:48-088354 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:48-088560 util-scheduler-8620 DEBUG Adding task: 4220 / 0x46620a0
Jul 07 20:59:48-088755 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:48-088970 util-scheduler-8620 DEBUG Adding task: 4221 / 0x46620a0
Jul 07 20:59:48-089239 util-scheduler-8620 DEBUG Checking readiness of task: 4221 / 0x46620a0
Jul 07 20:59:48-089436 util-scheduler-8620 DEBUG Checking readiness of task: 4220 / 0x46620a0
Jul 07 20:59:48-089629 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:48-089820 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:48-090042 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:48-092215 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:48-092427 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:48-092622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:48-092814 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:48-093011 util-scheduler-8620 DEBUG Running task: 4220 / 0x46620a0
Jul 07 20:59:48-093220 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:48-093405 util-8620 DEBUG process_notify is running
Jul 07 20:59:48-093579 util-8620 DEBUG client_notify is running
Jul 07 20:59:48-093773 util-scheduler-8620 DEBUG Canceling task: 4217 / 0x6146380
Jul 07 20:59:48-094012 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:48-094236 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:48-094476 cadet-p2p-8620 DEBUG Checking 0x6156f80 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:48-094716 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:48-094896 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:48-095088 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:48-095376 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 20:59:48-095574 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:48-095755 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:48-095945 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:48-096135 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 20:59:48-096340 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:48-096748 util-scheduler-8620 DEBUG Canceling task: 4214 / 0x6146c10
Jul 07 20:59:48-096971 util-scheduler-8620 DEBUG Adding task: 4222 / 0x6146c10
Jul 07 20:59:48-097246 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:48-097421 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:48-097604 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:48-097809 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:48-097986 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:48-098162 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:48-098363 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:48-098570 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:48-098756 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:48-098940 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:48-099133 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:48-099387 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:51-779078 util-scheduler-8620 DEBUG Checking readiness of task: 4221 / 0x46620a0
Jul 07 20:59:51-779460 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-779656 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-779849 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-780041 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-780233 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-780423 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-780613 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-780810 util-scheduler-8620 DEBUG Running task: 4216 / 0x52cbfb8
Jul 07 20:59:51-781048 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:51-781337 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:51-781547 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:51-781747 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:51-781949 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:51-782186 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 20:59:51-782367 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:51-782588 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 20:59:51-782879 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 20:59:51-783077 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 20:59:51-783315 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:51-783525 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:51-783844 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 20:59:51-784045 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:51-784269 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:51-784453 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:51-784629 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:51-784835 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:51-785052 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:51-785299 util-scheduler-8620 DEBUG Adding task: 4223 / 0x6146380
Jul 07 20:59:51-785481 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:51-785684 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:51-785861 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:51-786036 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:51-786274 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:51-786500 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:51-786679 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:51-786878 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:51-787122 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:51-787319 util-scheduler-8620 DEBUG Adding task: 4224 / 0x52cbfb8
Jul 07 20:59:51-787579 util-scheduler-8620 DEBUG Checking readiness of task: 4221 / 0x46620a0
Jul 07 20:59:51-787771 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-787962 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-788151 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-788340 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-788530 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-788719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-788909 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-789103 util-scheduler-8620 DEBUG Running task: 4223 / 0x6146380
Jul 07 20:59:51-789333 util-scheduler-8620 DEBUG Adding task: 4225 / 0x6146380
Jul 07 20:59:51-789556 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:51-789759 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:51-789967 util-scheduler-8620 DEBUG Adding task: 4226 / 0x46620a0
Jul 07 20:59:51-790211 util-scheduler-8620 DEBUG Checking readiness of task: 4226 / 0x46620a0
Jul 07 20:59:51-790405 util-scheduler-8620 DEBUG Checking readiness of task: 4221 / 0x46620a0
Jul 07 20:59:51-790595 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-790784 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-790975 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-791165 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-791445 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-791636 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-791826 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-792016 util-scheduler-8620 DEBUG Running task: 4226 / 0x46620a0
Jul 07 20:59:51-792201 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:51-792380 util-8620 DEBUG process_notify is running
Jul 07 20:59:51-792552 util-8620 DEBUG client_notify is running
Jul 07 20:59:51-792731 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:51-792926 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:51-793117 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:51-793396 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:51-963187 util-scheduler-8620 DEBUG Checking readiness of task: 4221 / 0x46620a0
Jul 07 20:59:51-963574 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-963772 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-963966 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-964159 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-964357 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-964550 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-964740 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-964935 util-scheduler-8620 DEBUG Running task: 4221 / 0x46620a0
Jul 07 20:59:51-967689 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:51-967995 util-scheduler-8620 DEBUG Adding task: 4227 / 0x4662248
Jul 07 20:59:51-968290 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-968488 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-968681 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-968873 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-969068 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-969289 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-969480 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-969671 util-scheduler-8620 DEBUG Running task: 4227 / 0x4662248
Jul 07 20:59:51-969863 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:51-970073 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:51-970300 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:51-970501 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:51-970704 util-scheduler-8620 DEBUG Adding task: 4228 / 0x46620a0
Jul 07 20:59:51-970892 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:51-971098 util-scheduler-8620 DEBUG Adding task: 4229 / 0x46620a0
Jul 07 20:59:51-971344 util-scheduler-8620 DEBUG Checking readiness of task: 4229 / 0x46620a0
Jul 07 20:59:51-971537 util-scheduler-8620 DEBUG Checking readiness of task: 4228 / 0x46620a0
Jul 07 20:59:51-971729 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:51-971930 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:51-972122 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:51-972312 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:51-972505 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:51-972693 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:51-972883 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:51-973073 util-scheduler-8620 DEBUG Running task: 4228 / 0x46620a0
Jul 07 20:59:51-973749 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:51-974216 util-8620 DEBUG process_notify is running
Jul 07 20:59:51-974391 util-8620 DEBUG client_notify is running
Jul 07 20:59:51-974581 util-scheduler-8620 DEBUG Canceling task: 4225 / 0x6146380
Jul 07 20:59:51-974810 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:51-975030 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:51-975266 cadet-p2p-8620 DEBUG Checking 0x6159aa8 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:51-975501 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:51-975721 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:51-975967 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:51-976363 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 20:59:51-976562 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:51-976742 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:51-976932 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:51-977121 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 20:59:51-977325 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:51-977509 util-scheduler-8620 DEBUG Canceling task: 4222 / 0x6146c10
Jul 07 20:59:51-977722 util-scheduler-8620 DEBUG Adding task: 4230 / 0x6146c10
Jul 07 20:59:51-977970 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:51-978140 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:51-978320 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:51-978521 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:51-978695 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:51-978870 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:51-979089 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:51-979295 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:51-979478 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:51-979658 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:51-979847 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:51-980098 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:56-792293 util-scheduler-8620 DEBUG Checking readiness of task: 4229 / 0x46620a0
Jul 07 20:59:56-792673 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:56-792871 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:56-793064 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:56-793279 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:56-793471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:56-793661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:56-793851 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:56-794044 util-scheduler-8620 DEBUG Running task: 4224 / 0x52cbfb8
Jul 07 20:59:56-794281 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 20:59:56-794538 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 20:59:56-794745 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 20:59:56-794946 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 20:59:56-795148 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 20:59:56-795383 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 20:59:56-795565 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 20:59:56-795786 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 20:59:56-796076 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 20:59:56-796275 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 20:59:56-796513 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 20:59:56-796723 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 20:59:56-797042 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 20:59:56-797264 cadet-p2p-8620 DEBUG priority 0
Jul 07 20:59:56-797490 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 20:59:56-797673 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 20:59:56-797848 cadet-con-8620 DEBUG  sendable
Jul 07 20:59:56-798055 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 20:59:56-798270 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 20:59:56-798494 util-scheduler-8620 DEBUG Adding task: 4231 / 0x6146380
Jul 07 20:59:56-798674 core-api-8620 DEBUG Transmission request added to queue
Jul 07 20:59:56-798877 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:56-799054 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 20:59:56-799229 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 20:59:56-799467 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 20:59:56-799663 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 20:59:56-799840 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 20:59:56-800039 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:56-800283 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 20:59:56-800480 util-scheduler-8620 DEBUG Adding task: 4232 / 0x52cbfb8
Jul 07 20:59:56-800737 util-scheduler-8620 DEBUG Checking readiness of task: 4229 / 0x46620a0
Jul 07 20:59:56-800930 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:56-801120 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:56-801332 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:56-801561 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:56-801754 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:56-801942 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:56-802132 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:56-802321 util-scheduler-8620 DEBUG Running task: 4231 / 0x6146380
Jul 07 20:59:56-802530 util-scheduler-8620 DEBUG Adding task: 4233 / 0x6146380
Jul 07 20:59:56-802752 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 20:59:56-802957 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:56-803165 util-scheduler-8620 DEBUG Adding task: 4234 / 0x46620a0
Jul 07 20:59:56-803408 util-scheduler-8620 DEBUG Checking readiness of task: 4234 / 0x46620a0
Jul 07 20:59:56-803603 util-scheduler-8620 DEBUG Checking readiness of task: 4229 / 0x46620a0
Jul 07 20:59:56-803793 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:56-803982 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:56-804171 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:56-804375 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:56-804564 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:56-804753 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:56-804942 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:56-805134 util-scheduler-8620 DEBUG Running task: 4234 / 0x46620a0
Jul 07 20:59:56-805339 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:56-805519 util-8620 DEBUG process_notify is running
Jul 07 20:59:56-805692 util-8620 DEBUG client_notify is running
Jul 07 20:59:56-805872 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 20:59:56-806066 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:56-806258 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 20:59:56-806517 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 20:59:57-556958 util-scheduler-8620 DEBUG Checking readiness of task: 4229 / 0x46620a0
Jul 07 20:59:57-557364 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:57-557562 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:57-557755 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:57-557947 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:57-558139 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:57-558332 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:57-558529 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:57-558725 util-scheduler-8620 DEBUG Running task: 4229 / 0x46620a0
Jul 07 20:59:57-559146 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 20:59:57-559401 util-scheduler-8620 DEBUG Adding task: 4235 / 0x4662248
Jul 07 20:59:57-559684 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:57-559878 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:57-560068 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:57-560258 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:57-560448 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:57-560638 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:57-560827 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:57-561050 util-scheduler-8620 DEBUG Running task: 4235 / 0x4662248
Jul 07 20:59:57-561270 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 20:59:57-561472 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 20:59:57-561705 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 20:59:57-561913 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 20:59:57-562120 util-scheduler-8620 DEBUG Adding task: 4236 / 0x46620a0
Jul 07 20:59:57-562307 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 20:59:57-562514 util-scheduler-8620 DEBUG Adding task: 4237 / 0x46620a0
Jul 07 20:59:57-562758 util-scheduler-8620 DEBUG Checking readiness of task: 4237 / 0x46620a0
Jul 07 20:59:57-562951 util-scheduler-8620 DEBUG Checking readiness of task: 4236 / 0x46620a0
Jul 07 20:59:57-563142 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 20:59:57-563333 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 20:59:57-563523 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 20:59:57-563712 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 20:59:57-563902 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 20:59:57-564089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 20:59:57-564279 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 20:59:57-564470 util-scheduler-8620 DEBUG Running task: 4236 / 0x46620a0
Jul 07 20:59:57-564656 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 20:59:57-564834 util-8620 DEBUG process_notify is running
Jul 07 20:59:57-565006 util-8620 DEBUG client_notify is running
Jul 07 20:59:57-565218 util-scheduler-8620 DEBUG Canceling task: 4233 / 0x6146380
Jul 07 20:59:57-565450 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 20:59:57-565672 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 20:59:57-565912 cadet-p2p-8620 DEBUG Checking 0x615c720 towards 0V7ADHDH (->V8XX)
Jul 07 20:59:57-566146 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 20:59:57-566324 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 20:59:57-566515 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 20:59:57-566799 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 20:59:57-566994 cadet-p2p-8620 DEBUG  calling callback
Jul 07 20:59:57-567173 cadet-con-8620 DEBUG connection message_sent
Jul 07 20:59:57-567360 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 20:59:57-567549 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 20:59:57-567726 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 20:59:57-567909 util-scheduler-8620 DEBUG Canceling task: 4230 / 0x6146c10
Jul 07 20:59:57-568121 util-scheduler-8620 DEBUG Adding task: 4238 / 0x6146c10
Jul 07 20:59:57-568371 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 20:59:57-568545 cadet-con-8620 DEBUG !  message sent!
Jul 07 20:59:57-568726 cadet-p2p-8620 DEBUG   return 196
Jul 07 20:59:57-568927 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 20:59:57-569103 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 20:59:57-569305 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 20:59:57-569504 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 20:59:57-569709 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 20:59:57-569893 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 20:59:57-570071 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 20:59:57-570263 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 20:59:57-570514 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:01-804869 util-scheduler-8620 DEBUG Checking readiness of task: 4237 / 0x46620a0
Jul 07 21:00:01-805298 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:01-805496 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:01-805690 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:01-805882 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:01-806073 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:01-806264 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:01-806454 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:01-806648 util-scheduler-8620 DEBUG Running task: 4232 / 0x52cbfb8
Jul 07 21:00:01-806884 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:01-807141 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 21:00:01-807349 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:01-807551 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:01-807755 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:01-807990 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:01-808171 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:01-808392 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:01-808683 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:01-808883 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:01-809121 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:01-809358 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:01-809683 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:01-809894 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:01-810120 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:01-810304 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:01-810493 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:01-810699 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:01-810915 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:01-811141 util-scheduler-8620 DEBUG Adding task: 4239 / 0x6146380
Jul 07 21:00:01-811321 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:01-811526 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:01-811704 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:01-811879 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:01-812116 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:01-812312 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:01-812489 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:01-812688 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:01-812931 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:01-813129 util-scheduler-8620 DEBUG Adding task: 4240 / 0x52cbfb8
Jul 07 21:00:01-813432 util-scheduler-8620 DEBUG Checking readiness of task: 4237 / 0x46620a0
Jul 07 21:00:01-813627 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:01-813818 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:01-814008 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:01-814199 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:01-814389 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:01-814578 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:01-814769 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:01-814958 util-scheduler-8620 DEBUG Running task: 4239 / 0x6146380
Jul 07 21:00:01-815168 util-scheduler-8620 DEBUG Adding task: 4241 / 0x6146380
Jul 07 21:00:01-815389 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:01-815612 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:01-815821 util-scheduler-8620 DEBUG Adding task: 4242 / 0x46620a0
Jul 07 21:00:01-816065 util-scheduler-8620 DEBUG Checking readiness of task: 4242 / 0x46620a0
Jul 07 21:00:01-816260 util-scheduler-8620 DEBUG Checking readiness of task: 4237 / 0x46620a0
Jul 07 21:00:01-816451 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:01-816640 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:01-816831 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:01-817020 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:01-817236 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:01-817428 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:01-817618 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:01-817809 util-scheduler-8620 DEBUG Running task: 4242 / 0x46620a0
Jul 07 21:00:01-817994 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:01-818172 util-8620 DEBUG process_notify is running
Jul 07 21:00:01-818345 util-8620 DEBUG client_notify is running
Jul 07 21:00:01-818525 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:01-818721 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:01-818913 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:01-819168 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:06-664031 util-scheduler-8620 DEBUG Checking readiness of task: 4237 / 0x46620a0
Jul 07 21:00:06-664429 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-666556 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-666764 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-666959 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-667161 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-667353 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-667543 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-667741 util-scheduler-8620 DEBUG Running task: 4237 / 0x46620a0
Jul 07 21:00:06-668168 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:06-668424 util-scheduler-8620 DEBUG Adding task: 4243 / 0x4662248
Jul 07 21:00:06-668706 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-668900 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-669095 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-669315 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-669506 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-669696 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-669885 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-670075 util-scheduler-8620 DEBUG Running task: 4243 / 0x4662248
Jul 07 21:00:06-670266 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:06-670467 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:06-670700 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:06-670907 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:06-671114 util-scheduler-8620 DEBUG Adding task: 4244 / 0x46620a0
Jul 07 21:00:06-671303 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:06-671508 util-scheduler-8620 DEBUG Adding task: 4245 / 0x46620a0
Jul 07 21:00:06-671780 util-scheduler-8620 DEBUG Checking readiness of task: 4245 / 0x46620a0
Jul 07 21:00:06-671974 util-scheduler-8620 DEBUG Checking readiness of task: 4244 / 0x46620a0
Jul 07 21:00:06-672166 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-672357 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-672547 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-672738 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-672927 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-673117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-673330 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-673524 util-scheduler-8620 DEBUG Running task: 4244 / 0x46620a0
Jul 07 21:00:06-673709 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:06-673889 util-8620 DEBUG process_notify is running
Jul 07 21:00:06-674061 util-8620 DEBUG client_notify is running
Jul 07 21:00:06-674249 util-scheduler-8620 DEBUG Canceling task: 4241 / 0x6146380
Jul 07 21:00:06-674475 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:06-674696 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:06-674937 cadet-p2p-8620 DEBUG Checking 0x615f4a8 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:06-675171 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:06-675350 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:06-675540 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:06-675826 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:06-676022 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:06-676202 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:06-676390 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:06-676579 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:06-676758 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:06-676941 util-scheduler-8620 DEBUG Canceling task: 4238 / 0x6146c10
Jul 07 21:00:06-677154 util-scheduler-8620 DEBUG Adding task: 4246 / 0x6146c10
Jul 07 21:00:06-677429 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:06-677601 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:06-677783 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:06-677983 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:06-678160 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:06-678334 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:06-678534 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:06-678752 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:06-678937 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:06-679120 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:06-679311 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:06-679562 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:06-813364 util-scheduler-8620 DEBUG Checking readiness of task: 4245 / 0x46620a0
Jul 07 21:00:06-813625 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-813818 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-814010 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-814201 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-814393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-814583 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-814773 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-814989 util-scheduler-8620 DEBUG Running task: 4240 / 0x52cbfb8
Jul 07 21:00:06-815212 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:06-815460 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 21:00:06-815666 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:06-815865 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:06-816067 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:06-816298 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:06-816478 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:06-816698 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:06-816981 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:06-817178 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:06-817442 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:06-817651 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:06-817964 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:06-818164 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:06-818388 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:06-818571 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:06-818747 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:06-818952 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:06-819168 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:06-819387 util-scheduler-8620 DEBUG Adding task: 4247 / 0x6146380
Jul 07 21:00:06-819567 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:06-819770 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:06-819949 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:06-820123 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:06-820360 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:06-820556 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:06-820733 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:06-820931 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:06-821172 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:06-821398 util-scheduler-8620 DEBUG Adding task: 4248 / 0x52cbfb8
Jul 07 21:00:06-821644 util-scheduler-8620 DEBUG Checking readiness of task: 4245 / 0x46620a0
Jul 07 21:00:06-821837 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-822029 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-822218 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-822409 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-822598 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-822786 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-822974 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-823164 util-scheduler-8620 DEBUG Running task: 4247 / 0x6146380
Jul 07 21:00:06-823372 util-scheduler-8620 DEBUG Adding task: 4249 / 0x6146380
Jul 07 21:00:06-823592 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:06-823793 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:06-824000 util-scheduler-8620 DEBUG Adding task: 4250 / 0x46620a0
Jul 07 21:00:06-824242 util-scheduler-8620 DEBUG Checking readiness of task: 4250 / 0x46620a0
Jul 07 21:00:06-824436 util-scheduler-8620 DEBUG Checking readiness of task: 4245 / 0x46620a0
Jul 07 21:00:06-824627 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-824816 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-825005 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-825238 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-825431 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-825620 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-825809 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-826000 util-scheduler-8620 DEBUG Running task: 4250 / 0x46620a0
Jul 07 21:00:06-826183 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:06-826361 util-8620 DEBUG process_notify is running
Jul 07 21:00:06-826534 util-8620 DEBUG client_notify is running
Jul 07 21:00:06-826711 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:06-826905 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:06-827096 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:06-827345 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:06-921770 util-scheduler-8620 DEBUG Checking readiness of task: 4245 / 0x46620a0
Jul 07 21:00:06-922160 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-922358 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-922551 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-922744 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-922937 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-923128 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-923318 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-923515 util-scheduler-8620 DEBUG Running task: 4245 / 0x46620a0
Jul 07 21:00:06-923940 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:06-924197 util-scheduler-8620 DEBUG Adding task: 4251 / 0x4662248
Jul 07 21:00:06-924477 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-924673 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-924864 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-925055 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-925271 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-925461 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-925651 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-925841 util-scheduler-8620 DEBUG Running task: 4251 / 0x4662248
Jul 07 21:00:06-926034 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:06-926234 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:06-926467 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:06-926674 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:06-926881 util-scheduler-8620 DEBUG Adding task: 4252 / 0x46620a0
Jul 07 21:00:06-927070 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:06-927276 util-scheduler-8620 DEBUG Adding task: 4253 / 0x46620a0
Jul 07 21:00:06-927520 util-scheduler-8620 DEBUG Checking readiness of task: 4253 / 0x46620a0
Jul 07 21:00:06-927713 util-scheduler-8620 DEBUG Checking readiness of task: 4252 / 0x46620a0
Jul 07 21:00:06-927906 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:06-928108 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:06-928298 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:06-928488 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:06-928678 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:06-928900 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:06-929093 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:06-929305 util-scheduler-8620 DEBUG Running task: 4252 / 0x46620a0
Jul 07 21:00:06-929492 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:06-929671 util-8620 DEBUG process_notify is running
Jul 07 21:00:06-929844 util-8620 DEBUG client_notify is running
Jul 07 21:00:06-930032 util-scheduler-8620 DEBUG Canceling task: 4249 / 0x6146380
Jul 07 21:00:06-930259 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:06-930481 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:06-930721 cadet-p2p-8620 DEBUG Checking 0x61620c0 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:06-930957 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:06-931135 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:06-931325 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:06-931610 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:06-931806 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:06-931985 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:06-932173 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:06-932362 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:06-932540 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:06-932723 util-scheduler-8620 DEBUG Canceling task: 4246 / 0x6146c10
Jul 07 21:00:06-932936 util-scheduler-8620 DEBUG Adding task: 4254 / 0x6146c10
Jul 07 21:00:06-933187 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:06-933379 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:06-933560 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:06-933762 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:06-933938 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:06-934113 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:06-934311 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:06-934517 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:06-934701 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:06-934880 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:06-935071 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:06-935323 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:11-826447 util-scheduler-8620 DEBUG Checking readiness of task: 4253 / 0x46620a0
Jul 07 21:00:11-826818 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:11-827015 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:11-827208 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:11-827401 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:11-827593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:11-827784 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:11-827973 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:11-828166 util-scheduler-8620 DEBUG Running task: 4248 / 0x52cbfb8
Jul 07 21:00:11-828404 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:11-828661 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 21:00:11-828869 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:11-829071 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:11-829297 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:11-829534 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:11-829716 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:11-829938 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:11-830228 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:11-830471 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:11-830724 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:11-830935 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:11-831254 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:11-831455 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:11-831680 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:11-831864 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:11-832040 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:11-832247 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:11-832462 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:11-832686 util-scheduler-8620 DEBUG Adding task: 4255 / 0x6146380
Jul 07 21:00:11-832865 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:11-833070 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:11-833271 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:11-833447 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:11-833684 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:11-833880 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:11-834058 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:11-834256 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:11-834500 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:11-834698 util-scheduler-8620 DEBUG Adding task: 4256 / 0x52cbfb8
Jul 07 21:00:11-834956 util-scheduler-8620 DEBUG Checking readiness of task: 4253 / 0x46620a0
Jul 07 21:00:11-835151 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:11-835341 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:11-835531 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:11-835722 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:11-835912 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:11-836101 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:11-836289 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:11-836479 util-scheduler-8620 DEBUG Running task: 4255 / 0x6146380
Jul 07 21:00:11-836687 util-scheduler-8620 DEBUG Adding task: 4257 / 0x6146380
Jul 07 21:00:11-836909 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:11-837113 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:11-837339 util-scheduler-8620 DEBUG Adding task: 4258 / 0x46620a0
Jul 07 21:00:11-837583 util-scheduler-8620 DEBUG Checking readiness of task: 4258 / 0x46620a0
Jul 07 21:00:11-837777 util-scheduler-8620 DEBUG Checking readiness of task: 4253 / 0x46620a0
Jul 07 21:00:11-837968 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:11-838158 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:11-838348 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:11-838537 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:11-838727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:11-838915 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:11-839105 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:11-839295 util-scheduler-8620 DEBUG Running task: 4258 / 0x46620a0
Jul 07 21:00:11-839482 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:11-839660 util-8620 DEBUG process_notify is running
Jul 07 21:00:11-839833 util-8620 DEBUG client_notify is running
Jul 07 21:00:11-840028 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:11-840238 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:11-840432 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:11-840688 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:12-973916 util-scheduler-8620 DEBUG Checking readiness of task: 4253 / 0x46620a0
Jul 07 21:00:12-974225 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:12-974422 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:12-974615 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:12-974807 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:12-974998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:12-975190 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:12-975403 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:12-975596 util-scheduler-8620 DEBUG Running task: 4253 / 0x46620a0
Jul 07 21:00:12-976021 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:12-976268 util-scheduler-8620 DEBUG Adding task: 4259 / 0x4662248
Jul 07 21:00:12-976534 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:12-976728 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:12-976920 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:12-977111 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:12-977332 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:12-977523 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:12-977715 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:12-977904 util-scheduler-8620 DEBUG Running task: 4259 / 0x4662248
Jul 07 21:00:12-978096 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:12-978293 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:12-978520 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:12-978723 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:12-978926 util-scheduler-8620 DEBUG Adding task: 4260 / 0x46620a0
Jul 07 21:00:12-979113 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:12-979318 util-scheduler-8620 DEBUG Adding task: 4261 / 0x46620a0
Jul 07 21:00:12-979562 util-scheduler-8620 DEBUG Checking readiness of task: 4261 / 0x46620a0
Jul 07 21:00:12-979755 util-scheduler-8620 DEBUG Checking readiness of task: 4260 / 0x46620a0
Jul 07 21:00:12-979946 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:12-980137 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:12-980328 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:12-980518 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:12-980711 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:12-980899 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:12-981089 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:12-981306 util-scheduler-8620 DEBUG Running task: 4260 / 0x46620a0
Jul 07 21:00:12-981492 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:12-981670 util-8620 DEBUG process_notify is running
Jul 07 21:00:12-981842 util-8620 DEBUG client_notify is running
Jul 07 21:00:12-982029 util-scheduler-8620 DEBUG Canceling task: 4257 / 0x6146380
Jul 07 21:00:12-982253 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:12-982496 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:12-982738 cadet-p2p-8620 DEBUG Checking 0x6164c98 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:12-982973 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:12-983151 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:12-983341 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:12-983626 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:12-983822 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:12-984002 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:12-984190 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:12-984377 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:12-984556 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:12-984739 util-scheduler-8620 DEBUG Canceling task: 4254 / 0x6146c10
Jul 07 21:00:12-984950 util-scheduler-8620 DEBUG Adding task: 4262 / 0x6146c10
Jul 07 21:00:12-985219 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:12-985392 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:12-985572 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:12-985773 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:12-985949 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:12-986123 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:12-986322 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:12-986527 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:12-986711 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:12-986890 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:12-987134 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:12-987383 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:16-838710 util-scheduler-8620 DEBUG Checking readiness of task: 4261 / 0x46620a0
Jul 07 21:00:16-839092 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:16-839749 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:16-839950 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:16-840210 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:16-840426 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:16-840619 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:16-840810 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:16-841003 util-scheduler-8620 DEBUG Running task: 4256 / 0x52cbfb8
Jul 07 21:00:16-841262 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:16-841521 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 21:00:16-841731 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:16-841932 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:16-842135 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:16-842370 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:16-842551 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:16-842772 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:16-843062 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:16-843260 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:16-843498 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:16-843706 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:16-844023 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:16-844224 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:16-844449 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:16-844633 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:16-844840 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:16-845050 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:16-845286 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:16-845512 util-scheduler-8620 DEBUG Adding task: 4263 / 0x6146380
Jul 07 21:00:16-845692 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:16-845896 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:16-846074 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:16-846249 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:16-846500 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:16-846696 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:16-846873 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:16-847073 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:16-847317 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:16-847515 util-scheduler-8620 DEBUG Adding task: 4264 / 0x52cbfb8
Jul 07 21:00:16-847773 util-scheduler-8620 DEBUG Checking readiness of task: 4261 / 0x46620a0
Jul 07 21:00:16-847966 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:16-848157 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:16-848347 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:16-848538 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:16-848728 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:16-848918 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:16-849106 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:16-849317 util-scheduler-8620 DEBUG Running task: 4263 / 0x6146380
Jul 07 21:00:16-849526 util-scheduler-8620 DEBUG Adding task: 4265 / 0x6146380
Jul 07 21:00:16-849749 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:16-849952 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:16-850159 util-scheduler-8620 DEBUG Adding task: 4266 / 0x46620a0
Jul 07 21:00:16-850402 util-scheduler-8620 DEBUG Checking readiness of task: 4266 / 0x46620a0
Jul 07 21:00:16-850596 util-scheduler-8620 DEBUG Checking readiness of task: 4261 / 0x46620a0
Jul 07 21:00:16-850786 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:16-850976 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:16-851166 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:16-851357 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:16-851547 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:16-851740 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:16-851928 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:16-852121 util-scheduler-8620 DEBUG Running task: 4266 / 0x46620a0
Jul 07 21:00:16-852305 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:16-852485 util-8620 DEBUG process_notify is running
Jul 07 21:00:16-852657 util-8620 DEBUG client_notify is running
Jul 07 21:00:16-852838 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:16-853033 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:16-853241 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:16-853502 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:17-099748 util-scheduler-8620 DEBUG Checking readiness of task: 4261 / 0x46620a0
Jul 07 21:00:17-100132 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:17-100329 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:17-100552 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:17-100745 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:17-100938 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:17-101130 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:17-101352 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:17-101548 util-scheduler-8620 DEBUG Running task: 4261 / 0x46620a0
Jul 07 21:00:17-101976 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:17-102233 util-scheduler-8620 DEBUG Adding task: 4267 / 0x4662248
Jul 07 21:00:17-102513 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:17-102706 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:17-102897 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:17-103088 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:17-103281 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:17-103470 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:17-103659 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:17-103848 util-scheduler-8620 DEBUG Running task: 4267 / 0x4662248
Jul 07 21:00:17-104039 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:17-104239 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:17-104471 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:17-104679 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:17-104886 util-scheduler-8620 DEBUG Adding task: 4268 / 0x46620a0
Jul 07 21:00:17-105073 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:17-105307 util-scheduler-8620 DEBUG Adding task: 4269 / 0x46620a0
Jul 07 21:00:17-105551 util-scheduler-8620 DEBUG Checking readiness of task: 4269 / 0x46620a0
Jul 07 21:00:17-105745 util-scheduler-8620 DEBUG Checking readiness of task: 4268 / 0x46620a0
Jul 07 21:00:17-105937 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:17-106127 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:17-106318 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:17-106508 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:17-106698 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:17-106886 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:17-107076 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:17-107267 util-scheduler-8620 DEBUG Running task: 4268 / 0x46620a0
Jul 07 21:00:17-107453 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:17-107632 util-8620 DEBUG process_notify is running
Jul 07 21:00:17-107804 util-8620 DEBUG client_notify is running
Jul 07 21:00:17-107993 util-scheduler-8620 DEBUG Canceling task: 4265 / 0x6146380
Jul 07 21:00:17-108218 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:17-108440 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:17-108679 cadet-p2p-8620 DEBUG Checking 0x6110f70 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:17-108913 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:17-109092 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:17-109308 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:17-109593 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:17-109789 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:17-109970 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:17-110175 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:17-110364 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:17-110542 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:17-110725 util-scheduler-8620 DEBUG Canceling task: 4262 / 0x6146c10
Jul 07 21:00:17-110938 util-scheduler-8620 DEBUG Adding task: 4270 / 0x6146c10
Jul 07 21:00:17-111189 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:17-111360 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:17-111541 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:17-111745 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:17-111920 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:17-112094 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:17-112292 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:17-112497 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:17-112681 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:17-112860 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:17-113051 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:17-113327 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:21-852415 util-scheduler-8620 DEBUG Checking readiness of task: 4269 / 0x46620a0
Jul 07 21:00:21-852801 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:21-853612 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:21-854074 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:21-854277 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:21-854471 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:21-854661 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:21-854853 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:21-855047 util-scheduler-8620 DEBUG Running task: 4264 / 0x52cbfb8
Jul 07 21:00:21-855288 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:21-855548 cadet-tun-8620 DEBUG  kx started 12 m ago
Jul 07 21:00:21-855756 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:21-855959 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:21-856161 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:21-856397 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:21-856579 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:21-856800 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:21-857092 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:21-857316 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:21-857555 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:21-857765 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:21-858082 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:21-858284 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:21-858509 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:21-858693 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:21-858869 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:21-859076 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:21-859291 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:21-859516 util-scheduler-8620 DEBUG Adding task: 4271 / 0x6146380
Jul 07 21:00:21-859696 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:21-859900 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:21-860078 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:21-860253 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:21-860548 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:21-860757 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:21-860936 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:21-861134 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:21-861402 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:21-861601 util-scheduler-8620 DEBUG Adding task: 4272 / 0x52cbfb8
Jul 07 21:00:21-861866 util-scheduler-8620 DEBUG Checking readiness of task: 4269 / 0x46620a0
Jul 07 21:00:21-862061 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:21-862252 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:21-862442 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:21-862633 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:21-862826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:21-863015 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:21-863203 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:21-863393 util-scheduler-8620 DEBUG Running task: 4271 / 0x6146380
Jul 07 21:00:21-863602 util-scheduler-8620 DEBUG Adding task: 4273 / 0x6146380
Jul 07 21:00:21-863825 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:21-864029 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:21-864237 util-scheduler-8620 DEBUG Adding task: 4274 / 0x46620a0
Jul 07 21:00:21-864481 util-scheduler-8620 DEBUG Checking readiness of task: 4274 / 0x46620a0
Jul 07 21:00:21-864675 util-scheduler-8620 DEBUG Checking readiness of task: 4269 / 0x46620a0
Jul 07 21:00:21-864865 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:21-865055 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:21-865265 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:21-865456 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:21-865646 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:21-865834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:21-866024 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:21-866216 util-scheduler-8620 DEBUG Running task: 4274 / 0x46620a0
Jul 07 21:00:21-866402 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:21-866580 util-8620 DEBUG process_notify is running
Jul 07 21:00:21-866753 util-8620 DEBUG client_notify is running
Jul 07 21:00:21-866933 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:21-867128 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:21-867320 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:21-867578 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:25-498871 util-scheduler-8620 DEBUG Checking readiness of task: 4269 / 0x46620a0
Jul 07 21:00:25-499234 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:25-499430 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:25-499623 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:25-499815 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:25-500008 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:25-500198 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:25-500389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:25-500584 util-scheduler-8620 DEBUG Running task: 4269 / 0x46620a0
Jul 07 21:00:25-501005 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:25-501316 util-scheduler-8620 DEBUG Adding task: 4275 / 0x4662248
Jul 07 21:00:25-501599 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:25-501792 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:25-501983 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:25-502174 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:25-502364 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:25-502554 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:25-502742 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:25-502934 util-scheduler-8620 DEBUG Running task: 4275 / 0x4662248
Jul 07 21:00:25-503125 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:25-503324 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:25-503555 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:25-503765 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:25-503972 util-scheduler-8620 DEBUG Adding task: 4276 / 0x46620a0
Jul 07 21:00:25-504159 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:25-504365 util-scheduler-8620 DEBUG Adding task: 4277 / 0x46620a0
Jul 07 21:00:25-504608 util-scheduler-8620 DEBUG Checking readiness of task: 4277 / 0x46620a0
Jul 07 21:00:25-504801 util-scheduler-8620 DEBUG Checking readiness of task: 4276 / 0x46620a0
Jul 07 21:00:25-504993 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:25-505183 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:25-505400 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:25-505590 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:25-505779 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:25-505967 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:25-506157 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:25-506348 util-scheduler-8620 DEBUG Running task: 4276 / 0x46620a0
Jul 07 21:00:25-506533 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:25-506725 util-8620 DEBUG process_notify is running
Jul 07 21:00:25-506897 util-8620 DEBUG client_notify is running
Jul 07 21:00:25-507086 util-scheduler-8620 DEBUG Canceling task: 4273 / 0x6146380
Jul 07 21:00:25-507311 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:25-507532 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:25-507772 cadet-p2p-8620 DEBUG Checking 0x616a6a0 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:25-508006 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:25-508184 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:25-508375 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:25-508658 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:25-508853 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:25-509032 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:25-509246 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:25-509437 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:25-509616 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:25-509799 util-scheduler-8620 DEBUG Canceling task: 4270 / 0x6146c10
Jul 07 21:00:25-510011 util-scheduler-8620 DEBUG Adding task: 4278 / 0x6146c10
Jul 07 21:00:25-510260 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:25-510431 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:25-510612 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:25-510812 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:25-511006 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:25-511181 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:25-511381 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:25-511586 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:25-511769 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:25-511948 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:25-512139 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:25-512390 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:26-861804 util-scheduler-8620 DEBUG Checking readiness of task: 4277 / 0x46620a0
Jul 07 21:00:26-862194 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:26-862840 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:26-863041 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:26-863303 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:26-863515 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:26-863706 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:26-863897 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:26-864091 util-scheduler-8620 DEBUG Running task: 4272 / 0x52cbfb8
Jul 07 21:00:26-864331 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:26-864589 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:26-864796 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:26-864997 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:26-865224 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:26-865462 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:26-865643 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:26-865865 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:26-866156 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:26-866354 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:26-866591 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:26-866878 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:26-867281 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:26-867484 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:26-867709 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:26-867892 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:26-868068 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:26-868274 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:26-868492 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:26-868716 util-scheduler-8620 DEBUG Adding task: 4279 / 0x6146380
Jul 07 21:00:26-868896 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:26-869100 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:26-869301 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:26-869476 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:26-869715 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:26-869912 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:26-870090 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:26-870287 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:26-870533 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:26-870730 util-scheduler-8620 DEBUG Adding task: 4280 / 0x52cbfb8
Jul 07 21:00:26-870986 util-scheduler-8620 DEBUG Checking readiness of task: 4277 / 0x46620a0
Jul 07 21:00:26-871181 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:26-871405 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:26-871597 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:26-871788 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:26-871978 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:26-872167 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:26-872355 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:26-872546 util-scheduler-8620 DEBUG Running task: 4279 / 0x6146380
Jul 07 21:00:26-872755 util-scheduler-8620 DEBUG Adding task: 4281 / 0x6146380
Jul 07 21:00:26-872977 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:26-873181 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:26-873410 util-scheduler-8620 DEBUG Adding task: 4282 / 0x46620a0
Jul 07 21:00:26-873653 util-scheduler-8620 DEBUG Checking readiness of task: 4282 / 0x46620a0
Jul 07 21:00:26-873849 util-scheduler-8620 DEBUG Checking readiness of task: 4277 / 0x46620a0
Jul 07 21:00:26-874039 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:26-874233 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:26-874422 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:26-874611 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:26-874801 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:26-874989 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:26-875178 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:26-875370 util-scheduler-8620 DEBUG Running task: 4282 / 0x46620a0
Jul 07 21:00:26-875554 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:26-875733 util-8620 DEBUG process_notify is running
Jul 07 21:00:26-875906 util-8620 DEBUG client_notify is running
Jul 07 21:00:26-876085 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:26-876281 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:26-876472 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:26-876730 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:30-478660 util-scheduler-8620 DEBUG Checking readiness of task: 4277 / 0x46620a0
Jul 07 21:00:30-479043 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:30-479241 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:30-479434 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:30-479642 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:30-479847 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:30-480038 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:30-480228 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:30-480424 util-scheduler-8620 DEBUG Running task: 4277 / 0x46620a0
Jul 07 21:00:30-480846 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:30-481100 util-scheduler-8620 DEBUG Adding task: 4283 / 0x4662248
Jul 07 21:00:30-481405 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:30-481599 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:30-481790 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:30-481980 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:30-482170 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:30-482360 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:30-482581 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:30-482771 util-scheduler-8620 DEBUG Running task: 4283 / 0x4662248
Jul 07 21:00:30-482964 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:30-483163 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:30-483395 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:30-483603 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:30-483809 util-scheduler-8620 DEBUG Adding task: 4284 / 0x46620a0
Jul 07 21:00:30-483996 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:30-484203 util-scheduler-8620 DEBUG Adding task: 4285 / 0x46620a0
Jul 07 21:00:30-484447 util-scheduler-8620 DEBUG Checking readiness of task: 4285 / 0x46620a0
Jul 07 21:00:30-484639 util-scheduler-8620 DEBUG Checking readiness of task: 4284 / 0x46620a0
Jul 07 21:00:30-484830 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:30-485024 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:30-485498 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:30-485699 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:30-485891 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:30-486081 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:30-486270 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:30-486463 util-scheduler-8620 DEBUG Running task: 4284 / 0x46620a0
Jul 07 21:00:30-486725 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:30-486907 util-8620 DEBUG process_notify is running
Jul 07 21:00:30-487080 util-8620 DEBUG client_notify is running
Jul 07 21:00:30-487269 util-scheduler-8620 DEBUG Canceling task: 4281 / 0x6146380
Jul 07 21:00:30-487497 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:30-487718 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:30-487958 cadet-p2p-8620 DEBUG Checking 0x616d288 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:30-488193 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:30-488371 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:30-488562 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:30-488849 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:30-489045 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:30-489244 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:30-489434 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:30-489623 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:30-489802 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:30-489987 util-scheduler-8620 DEBUG Canceling task: 4278 / 0x6146c10
Jul 07 21:00:30-490201 util-scheduler-8620 DEBUG Adding task: 4286 / 0x6146c10
Jul 07 21:00:30-490452 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:30-490624 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:30-490806 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:30-491007 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:30-491566 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:30-491747 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:30-491950 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:30-492156 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:30-492340 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:30-492519 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:30-492711 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:30-493479 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:31-872277 util-scheduler-8620 DEBUG Checking readiness of task: 4285 / 0x46620a0
Jul 07 21:00:31-872665 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:31-872867 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:31-873063 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:31-873284 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:31-873479 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:31-873669 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:31-873858 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:31-874050 util-scheduler-8620 DEBUG Running task: 4280 / 0x52cbfb8
Jul 07 21:00:31-874288 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:31-874545 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:31-874752 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:31-874953 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:31-875156 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:31-875391 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:31-875571 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:31-875791 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:31-876082 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:31-876279 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:31-876515 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:31-876724 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:31-877043 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:31-877264 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:31-877490 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:31-877673 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:31-877848 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:31-878054 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:31-878268 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:31-878492 util-scheduler-8620 DEBUG Adding task: 4287 / 0x6146380
Jul 07 21:00:31-878673 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:31-878877 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:31-879054 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:31-879228 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:31-879465 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:31-879661 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:31-879838 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:31-880035 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:31-880279 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:31-880476 util-scheduler-8620 DEBUG Adding task: 4288 / 0x52cbfb8
Jul 07 21:00:31-880732 util-scheduler-8620 DEBUG Checking readiness of task: 4285 / 0x46620a0
Jul 07 21:00:31-880924 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:31-881127 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:31-882159 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:31-882387 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:31-882580 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:31-882769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:31-882958 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:31-883147 util-scheduler-8620 DEBUG Running task: 4287 / 0x6146380
Jul 07 21:00:31-883382 util-scheduler-8620 DEBUG Adding task: 4289 / 0x6146380
Jul 07 21:00:31-883609 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:31-883818 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:31-884030 util-scheduler-8620 DEBUG Adding task: 4290 / 0x46620a0
Jul 07 21:00:31-884282 util-scheduler-8620 DEBUG Checking readiness of task: 4290 / 0x46620a0
Jul 07 21:00:31-884479 util-scheduler-8620 DEBUG Checking readiness of task: 4285 / 0x46620a0
Jul 07 21:00:31-884671 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:31-884862 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:31-885052 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:31-885270 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:31-885463 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:31-885655 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:31-885846 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:31-886041 util-scheduler-8620 DEBUG Running task: 4290 / 0x46620a0
Jul 07 21:00:31-886228 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:31-886406 util-8620 DEBUG process_notify is running
Jul 07 21:00:31-886580 util-8620 DEBUG client_notify is running
Jul 07 21:00:31-886758 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:31-886957 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:31-887146 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:31-887453 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:34-641081 util-scheduler-8620 DEBUG Checking readiness of task: 4285 / 0x46620a0
Jul 07 21:00:34-641488 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:34-641686 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:34-641879 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:34-642072 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:34-642266 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:34-642461 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:34-642651 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:34-642846 util-scheduler-8620 DEBUG Running task: 4285 / 0x46620a0
Jul 07 21:00:34-643268 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:34-643525 util-scheduler-8620 DEBUG Adding task: 4291 / 0x4662248
Jul 07 21:00:34-643804 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:34-643998 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:34-644189 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:34-644380 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:34-644570 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:34-644761 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:34-644950 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:34-645140 util-scheduler-8620 DEBUG Running task: 4291 / 0x4662248
Jul 07 21:00:34-645354 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:34-645556 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:34-645789 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:34-645999 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:34-646206 util-scheduler-8620 DEBUG Adding task: 4292 / 0x46620a0
Jul 07 21:00:34-646425 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:34-646631 util-scheduler-8620 DEBUG Adding task: 4293 / 0x46620a0
Jul 07 21:00:34-646875 util-scheduler-8620 DEBUG Checking readiness of task: 4293 / 0x46620a0
Jul 07 21:00:34-647068 util-scheduler-8620 DEBUG Checking readiness of task: 4292 / 0x46620a0
Jul 07 21:00:34-647260 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:34-647450 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:34-647639 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:34-647830 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:34-648020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:34-648209 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:34-648398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:34-648589 util-scheduler-8620 DEBUG Running task: 4292 / 0x46620a0
Jul 07 21:00:34-648774 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:34-648952 util-8620 DEBUG process_notify is running
Jul 07 21:00:34-649126 util-8620 DEBUG client_notify is running
Jul 07 21:00:34-649336 util-scheduler-8620 DEBUG Canceling task: 4289 / 0x6146380
Jul 07 21:00:34-649563 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:34-649785 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:34-650024 cadet-p2p-8620 DEBUG Checking 0x616fed0 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:34-650259 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:34-650437 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:34-650627 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:34-650911 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:34-651107 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:34-651287 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:34-651474 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:34-651663 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:34-651841 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:34-652024 util-scheduler-8620 DEBUG Canceling task: 4286 / 0x6146c10
Jul 07 21:00:34-652236 util-scheduler-8620 DEBUG Adding task: 4294 / 0x6146c10
Jul 07 21:00:34-652487 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:34-652658 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:34-652840 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:34-653042 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:34-653240 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:34-653418 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:34-653618 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:34-653823 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:34-654007 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:34-654186 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:34-654376 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:34-654624 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:36-882841 util-scheduler-8620 DEBUG Checking readiness of task: 4293 / 0x46620a0
Jul 07 21:00:36-883170 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:36-884187 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:36-884433 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:36-884670 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:36-884864 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:36-885112 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:36-885372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:36-885568 util-scheduler-8620 DEBUG Running task: 4288 / 0x52cbfb8
Jul 07 21:00:36-885800 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:36-886056 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:36-886263 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:36-886478 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:36-886682 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:36-886916 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:36-887097 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:36-887318 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:36-887607 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:36-887804 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:36-888042 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:36-888249 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:36-888564 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:36-888765 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:36-888990 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:36-889174 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:36-889376 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:36-889584 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:36-889798 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:36-890022 util-scheduler-8620 DEBUG Adding task: 4295 / 0x6146380
Jul 07 21:00:36-890203 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:36-890407 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:36-890585 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:36-890760 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:36-890997 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:36-891194 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:36-891372 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:36-891570 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:36-891813 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:36-892011 util-scheduler-8620 DEBUG Adding task: 4296 / 0x52cbfb8
Jul 07 21:00:36-892267 util-scheduler-8620 DEBUG Checking readiness of task: 4293 / 0x46620a0
Jul 07 21:00:36-892461 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:36-892652 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:36-892843 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:36-893078 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:36-893308 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:36-893499 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:36-893688 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:36-893879 util-scheduler-8620 DEBUG Running task: 4295 / 0x6146380
Jul 07 21:00:36-894088 util-scheduler-8620 DEBUG Adding task: 4297 / 0x6146380
Jul 07 21:00:36-894312 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:36-894513 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:36-894721 util-scheduler-8620 DEBUG Adding task: 4298 / 0x46620a0
Jul 07 21:00:36-894965 util-scheduler-8620 DEBUG Checking readiness of task: 4298 / 0x46620a0
Jul 07 21:00:36-895159 util-scheduler-8620 DEBUG Checking readiness of task: 4293 / 0x46620a0
Jul 07 21:00:36-895350 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:36-895540 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:36-895748 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:36-895940 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:36-896129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:36-896319 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:36-896508 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:36-896700 util-scheduler-8620 DEBUG Running task: 4298 / 0x46620a0
Jul 07 21:00:36-896885 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:36-897064 util-8620 DEBUG process_notify is running
Jul 07 21:00:36-897256 util-8620 DEBUG client_notify is running
Jul 07 21:00:36-897436 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:36-897632 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:36-897823 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:36-898074 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:38-292708 util-scheduler-8620 DEBUG Checking readiness of task: 4293 / 0x46620a0
Jul 07 21:00:38-293016 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:38-293245 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:38-293440 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:38-293633 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:38-293826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:38-294019 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:38-294223 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:38-294544 util-scheduler-8620 DEBUG Running task: 4293 / 0x46620a0
Jul 07 21:00:38-294969 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:38-295216 util-scheduler-8620 DEBUG Adding task: 4299 / 0x4662248
Jul 07 21:00:38-295483 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:38-295677 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:38-295923 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:38-296121 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:38-296315 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:38-296506 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:38-296699 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:38-296890 util-scheduler-8620 DEBUG Running task: 4299 / 0x4662248
Jul 07 21:00:38-297083 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:38-297304 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:38-297532 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:38-297736 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:38-297940 util-scheduler-8620 DEBUG Adding task: 4300 / 0x46620a0
Jul 07 21:00:38-298126 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:38-298332 util-scheduler-8620 DEBUG Adding task: 4301 / 0x46620a0
Jul 07 21:00:38-298576 util-scheduler-8620 DEBUG Checking readiness of task: 4301 / 0x46620a0
Jul 07 21:00:38-298770 util-scheduler-8620 DEBUG Checking readiness of task: 4300 / 0x46620a0
Jul 07 21:00:38-298964 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:38-299155 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:38-299346 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:38-299539 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:38-299753 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:38-299945 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:38-300135 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:38-300328 util-scheduler-8620 DEBUG Running task: 4300 / 0x46620a0
Jul 07 21:00:38-300517 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:38-300694 util-8620 DEBUG process_notify is running
Jul 07 21:00:38-300868 util-8620 DEBUG client_notify is running
Jul 07 21:00:38-301055 util-scheduler-8620 DEBUG Canceling task: 4297 / 0x6146380
Jul 07 21:00:38-301301 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:38-301522 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:38-301759 cadet-p2p-8620 DEBUG Checking 0x6172b78 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:38-301994 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:38-302174 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:38-302363 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:38-302662 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:38-302859 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:38-303039 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:38-303227 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:38-303416 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:38-303596 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:38-303781 util-scheduler-8620 DEBUG Canceling task: 4294 / 0x6146c10
Jul 07 21:00:38-303994 util-scheduler-8620 DEBUG Adding task: 4302 / 0x6146c10
Jul 07 21:00:38-304243 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:38-304415 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:38-304596 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:38-304798 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:38-304975 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:38-305151 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:38-305373 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:38-305579 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:38-305764 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:38-305944 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:38-306134 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:38-306895 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:41-895740 util-scheduler-8620 DEBUG Checking readiness of task: 4301 / 0x46620a0
Jul 07 21:00:41-896088 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:41-896672 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:41-896875 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:41-897124 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:41-897354 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:41-897545 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:41-897735 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:41-897929 util-scheduler-8620 DEBUG Running task: 4296 / 0x52cbfb8
Jul 07 21:00:41-898160 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:41-898417 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:41-898624 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:41-898825 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:41-899027 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:41-899263 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:41-899443 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:41-899687 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:41-899976 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:41-900173 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:41-900411 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:41-900618 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:41-900933 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:41-901134 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:41-901381 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:41-901567 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:41-901743 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:41-901947 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:41-902161 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:41-902386 util-scheduler-8620 DEBUG Adding task: 4303 / 0x6146380
Jul 07 21:00:41-902566 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:41-902770 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:41-902948 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:41-903123 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:41-903360 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:41-903556 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:41-903733 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:41-903932 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:41-904175 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:41-904372 util-scheduler-8620 DEBUG Adding task: 4304 / 0x52cbfb8
Jul 07 21:00:41-904627 util-scheduler-8620 DEBUG Checking readiness of task: 4301 / 0x46620a0
Jul 07 21:00:41-904821 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:41-905011 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:41-905222 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:41-905413 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:41-905605 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:41-905794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:41-905984 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:41-906173 util-scheduler-8620 DEBUG Running task: 4303 / 0x6146380
Jul 07 21:00:41-906382 util-scheduler-8620 DEBUG Adding task: 4305 / 0x6146380
Jul 07 21:00:41-906603 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:41-906806 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:41-907013 util-scheduler-8620 DEBUG Adding task: 4306 / 0x46620a0
Jul 07 21:00:41-907256 util-scheduler-8620 DEBUG Checking readiness of task: 4306 / 0x46620a0
Jul 07 21:00:41-907451 util-scheduler-8620 DEBUG Checking readiness of task: 4301 / 0x46620a0
Jul 07 21:00:41-907640 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:41-907831 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:41-908020 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:41-908210 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:41-908400 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:41-908591 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:41-908780 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:41-908971 util-scheduler-8620 DEBUG Running task: 4306 / 0x46620a0
Jul 07 21:00:41-909157 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:41-909373 util-8620 DEBUG process_notify is running
Jul 07 21:00:41-909548 util-8620 DEBUG client_notify is running
Jul 07 21:00:41-909726 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:41-909922 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:41-910112 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:41-910366 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:42-152818 util-scheduler-8620 DEBUG Checking readiness of task: 4301 / 0x46620a0
Jul 07 21:00:42-153041 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:42-153258 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:42-153450 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:42-153642 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:42-153833 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:42-154025 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:42-154230 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:42-154424 util-scheduler-8620 DEBUG Running task: 4301 / 0x46620a0
Jul 07 21:00:42-154831 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:42-155067 util-scheduler-8620 DEBUG Adding task: 4307 / 0x4662248
Jul 07 21:00:42-155322 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:42-155515 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:42-155718 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:42-155908 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:42-156098 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:42-156286 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:42-156477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:42-156666 util-scheduler-8620 DEBUG Running task: 4307 / 0x4662248
Jul 07 21:00:42-156858 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:42-157054 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:42-157294 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:42-157494 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:42-157695 util-scheduler-8620 DEBUG Adding task: 4308 / 0x46620a0
Jul 07 21:00:42-157879 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:42-158083 util-scheduler-8620 DEBUG Adding task: 4309 / 0x46620a0
Jul 07 21:00:42-158324 util-scheduler-8620 DEBUG Checking readiness of task: 4309 / 0x46620a0
Jul 07 21:00:42-158516 util-scheduler-8620 DEBUG Checking readiness of task: 4308 / 0x46620a0
Jul 07 21:00:42-158708 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:42-158898 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:42-159088 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:42-159277 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:42-159467 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:42-159656 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:42-159845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:42-160036 util-scheduler-8620 DEBUG Running task: 4308 / 0x46620a0
Jul 07 21:00:42-160219 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:42-160397 util-8620 DEBUG process_notify is running
Jul 07 21:00:42-160566 util-8620 DEBUG client_notify is running
Jul 07 21:00:42-160752 util-scheduler-8620 DEBUG Canceling task: 4305 / 0x6146380
Jul 07 21:00:42-160994 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:42-161231 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:42-161466 cadet-p2p-8620 DEBUG Checking 0x6175760 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:42-161701 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:42-161879 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:42-162066 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:42-162350 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:42-162543 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:42-162721 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:42-162908 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:42-163096 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:42-163273 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:42-163456 util-scheduler-8620 DEBUG Canceling task: 4302 / 0x6146c10
Jul 07 21:00:42-163666 util-scheduler-8620 DEBUG Adding task: 4310 / 0x6146c10
Jul 07 21:00:42-163911 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:42-164081 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:42-164262 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:42-164461 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:42-164637 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:42-164810 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:42-165007 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:42-165231 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:42-165417 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:42-165595 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:42-165784 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:42-166029 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:46-905376 util-scheduler-8620 DEBUG Checking readiness of task: 4309 / 0x46620a0
Jul 07 21:00:46-905758 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:46-905954 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:46-906150 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:46-906342 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:46-906533 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:46-906723 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:46-906913 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:46-907105 util-scheduler-8620 DEBUG Running task: 4304 / 0x52cbfb8
Jul 07 21:00:46-907343 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:46-907600 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:46-907806 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:46-908010 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:46-908214 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:46-908457 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:46-908641 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:46-908868 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:46-909165 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:46-909395 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:46-909638 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:46-909849 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:46-910169 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:46-910369 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:46-910624 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:46-910808 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:46-910984 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:46-911189 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:46-911402 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:46-911630 util-scheduler-8620 DEBUG Adding task: 4311 / 0x6146380
Jul 07 21:00:46-911812 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:46-912015 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:46-912190 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:46-912365 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:46-912602 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:46-912796 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:46-912975 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:46-913173 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:46-914127 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:46-914357 util-scheduler-8620 DEBUG Adding task: 4312 / 0x52cbfb8
Jul 07 21:00:46-914621 util-scheduler-8620 DEBUG Checking readiness of task: 4309 / 0x46620a0
Jul 07 21:00:46-914816 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:46-915007 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:46-915195 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:46-915385 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:46-915573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:46-915762 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:46-915950 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:46-916140 util-scheduler-8620 DEBUG Running task: 4311 / 0x6146380
Jul 07 21:00:46-916348 util-scheduler-8620 DEBUG Adding task: 4313 / 0x6146380
Jul 07 21:00:46-916570 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:46-916786 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:46-916993 util-scheduler-8620 DEBUG Adding task: 4314 / 0x46620a0
Jul 07 21:00:46-917254 util-scheduler-8620 DEBUG Checking readiness of task: 4314 / 0x46620a0
Jul 07 21:00:46-917450 util-scheduler-8620 DEBUG Checking readiness of task: 4309 / 0x46620a0
Jul 07 21:00:46-917640 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:46-917830 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:46-918019 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:46-918209 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:46-918397 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:46-918587 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:46-918775 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:46-918966 util-scheduler-8620 DEBUG Running task: 4314 / 0x46620a0
Jul 07 21:00:46-919151 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:46-919329 util-8620 DEBUG process_notify is running
Jul 07 21:00:46-919503 util-8620 DEBUG client_notify is running
Jul 07 21:00:46-919682 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:46-919877 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:46-920068 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:46-920381 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:49-251811 util-scheduler-8620 DEBUG Checking readiness of task: 4309 / 0x46620a0
Jul 07 21:00:49-252200 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:49-252397 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:49-252591 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:49-252782 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:49-252976 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:49-253175 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:49-253393 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:49-253589 util-scheduler-8620 DEBUG Running task: 4309 / 0x46620a0
Jul 07 21:00:49-254011 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:49-254266 util-scheduler-8620 DEBUG Adding task: 4315 / 0x4662248
Jul 07 21:00:49-254541 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:49-254735 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:49-254926 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:49-255117 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:49-255308 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:49-255497 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:49-255687 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:49-255876 util-scheduler-8620 DEBUG Running task: 4315 / 0x4662248
Jul 07 21:00:49-256068 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:49-256267 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:49-256498 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:49-256705 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:49-256910 util-scheduler-8620 DEBUG Adding task: 4316 / 0x46620a0
Jul 07 21:00:49-257098 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:49-257328 util-scheduler-8620 DEBUG Adding task: 4317 / 0x46620a0
Jul 07 21:00:49-257571 util-scheduler-8620 DEBUG Checking readiness of task: 4317 / 0x46620a0
Jul 07 21:00:49-257764 util-scheduler-8620 DEBUG Checking readiness of task: 4316 / 0x46620a0
Jul 07 21:00:49-257956 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:49-258146 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:49-258338 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:49-258527 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:49-258718 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:49-258906 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:49-259096 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:49-259287 util-scheduler-8620 DEBUG Running task: 4316 / 0x46620a0
Jul 07 21:00:49-259473 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:49-259651 util-8620 DEBUG process_notify is running
Jul 07 21:00:49-259824 util-8620 DEBUG client_notify is running
Jul 07 21:00:49-260011 util-scheduler-8620 DEBUG Canceling task: 4313 / 0x6146380
Jul 07 21:00:49-260236 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:49-260457 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:49-260697 cadet-p2p-8620 DEBUG Checking 0x6178390 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:49-260932 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:49-261110 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:49-261323 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:49-261608 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:49-261823 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:49-262003 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:49-262191 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:49-262381 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:49-262559 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:49-262742 util-scheduler-8620 DEBUG Canceling task: 4310 / 0x6146c10
Jul 07 21:00:49-262953 util-scheduler-8620 DEBUG Adding task: 4318 / 0x6146c10
Jul 07 21:00:49-263203 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:49-263374 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:49-263555 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:49-263760 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:49-263936 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:49-264110 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:49-264308 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:49-264513 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:49-264696 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:49-264875 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:49-265066 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:49-265338 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:51-917170 util-scheduler-8620 DEBUG Checking readiness of task: 4317 / 0x46620a0
Jul 07 21:00:51-917578 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:51-918256 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:51-918704 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:51-918907 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:51-919101 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:51-919293 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:51-919484 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:51-919694 util-scheduler-8620 DEBUG Running task: 4312 / 0x52cbfb8
Jul 07 21:00:51-919935 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:51-920193 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:51-920403 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:51-920605 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:51-920808 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:51-921045 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:51-921265 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:51-921489 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:51-921781 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:51-921978 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:51-922229 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:51-922437 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:51-922756 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:51-922957 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:51-923182 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:51-923366 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:51-923542 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:51-923748 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:51-923964 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:51-924191 util-scheduler-8620 DEBUG Adding task: 4319 / 0x6146380
Jul 07 21:00:51-924375 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:51-924578 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:51-924790 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:51-924967 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:51-925225 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:51-925423 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:51-925601 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:51-925799 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:51-926045 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:51-926243 util-scheduler-8620 DEBUG Adding task: 4320 / 0x52cbfb8
Jul 07 21:00:51-926509 util-scheduler-8620 DEBUG Checking readiness of task: 4317 / 0x46620a0
Jul 07 21:00:51-926703 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:51-926893 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:51-927083 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:51-927272 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:51-927462 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:51-927651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:51-927838 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:51-928028 util-scheduler-8620 DEBUG Running task: 4319 / 0x6146380
Jul 07 21:00:51-928235 util-scheduler-8620 DEBUG Adding task: 4321 / 0x6146380
Jul 07 21:00:51-928458 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:51-928661 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:51-928870 util-scheduler-8620 DEBUG Adding task: 4322 / 0x46620a0
Jul 07 21:00:51-929115 util-scheduler-8620 DEBUG Checking readiness of task: 4322 / 0x46620a0
Jul 07 21:00:51-929330 util-scheduler-8620 DEBUG Checking readiness of task: 4317 / 0x46620a0
Jul 07 21:00:51-929521 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:51-929710 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:51-929901 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:51-930091 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:51-930280 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:51-930489 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:51-930681 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:51-930874 util-scheduler-8620 DEBUG Running task: 4322 / 0x46620a0
Jul 07 21:00:51-931060 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:51-931240 util-8620 DEBUG process_notify is running
Jul 07 21:00:51-931414 util-8620 DEBUG client_notify is running
Jul 07 21:00:51-931594 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:51-931791 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:51-931981 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:51-932239 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:54-599134 util-scheduler-8620 DEBUG Checking readiness of task: 4317 / 0x46620a0
Jul 07 21:00:54-599520 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:54-599717 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:54-599909 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:54-600102 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:54-600294 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:54-600487 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:54-600690 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:54-600886 util-scheduler-8620 DEBUG Running task: 4317 / 0x46620a0
Jul 07 21:00:54-601369 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:00:54-601631 util-scheduler-8620 DEBUG Adding task: 4323 / 0x4662248
Jul 07 21:00:54-601912 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:54-602108 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:54-602301 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:54-602493 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:54-602687 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:54-602878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:54-603069 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:54-603260 util-scheduler-8620 DEBUG Running task: 4323 / 0x4662248
Jul 07 21:00:54-603453 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:00:54-603654 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:00:54-603888 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:00:54-604096 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:54-604304 util-scheduler-8620 DEBUG Adding task: 4324 / 0x46620a0
Jul 07 21:00:54-604493 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:00:54-604700 util-scheduler-8620 DEBUG Adding task: 4325 / 0x46620a0
Jul 07 21:00:54-604948 util-scheduler-8620 DEBUG Checking readiness of task: 4325 / 0x46620a0
Jul 07 21:00:54-605143 util-scheduler-8620 DEBUG Checking readiness of task: 4324 / 0x46620a0
Jul 07 21:00:54-605363 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:54-605555 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:54-605746 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:54-605936 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:54-606128 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:54-606317 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:54-606507 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:54-606700 util-scheduler-8620 DEBUG Running task: 4324 / 0x46620a0
Jul 07 21:00:54-606884 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:54-607065 util-8620 DEBUG process_notify is running
Jul 07 21:00:54-607237 util-8620 DEBUG client_notify is running
Jul 07 21:00:54-607427 util-scheduler-8620 DEBUG Canceling task: 4321 / 0x6146380
Jul 07 21:00:54-607653 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:00:54-607875 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:00:54-608117 cadet-p2p-8620 DEBUG Checking 0x617b0a0 towards 0V7ADHDH (->V8XX)
Jul 07 21:00:54-608352 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:00:54-608531 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:00:54-608722 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:00:54-609008 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:00:54-609229 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:00:54-609414 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:00:54-609603 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:00:54-609793 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:00:54-609973 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:00:54-610158 util-scheduler-8620 DEBUG Canceling task: 4318 / 0x6146c10
Jul 07 21:00:54-610371 util-scheduler-8620 DEBUG Adding task: 4326 / 0x6146c10
Jul 07 21:00:54-610636 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:00:54-610809 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:00:54-611011 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:00:54-611219 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:54-611397 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:00:54-611573 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:00:54-611773 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:54-611979 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:00:54-612164 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:00:54-612344 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:54-612535 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:00:54-613382 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:00:56-928728 util-scheduler-8620 DEBUG Checking readiness of task: 4325 / 0x46620a0
Jul 07 21:00:56-929127 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:56-930072 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:56-930283 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:56-930478 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:56-930670 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:56-930862 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:56-931052 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:56-931246 util-scheduler-8620 DEBUG Running task: 4320 / 0x52cbfb8
Jul 07 21:00:56-931485 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:00:56-931747 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:00:56-931955 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:00:56-932155 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:00:56-932357 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:00:56-932593 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:00:56-932776 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:00:56-932997 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:00:56-933313 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:00:56-933511 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:00:56-933750 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:00:56-933958 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:00:56-934278 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:00:56-934480 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:00:56-934704 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:00:56-934887 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:00:56-935063 cadet-con-8620 DEBUG  sendable
Jul 07 21:00:56-935269 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:00:56-935484 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:00:56-935709 util-scheduler-8620 DEBUG Adding task: 4327 / 0x6146380
Jul 07 21:00:56-935890 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:00:56-936094 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:00:56-936272 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:00:56-936448 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:00:56-936686 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:00:56-936884 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:00:56-937061 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:00:56-937302 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:00:56-937548 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:00:56-937746 util-scheduler-8620 DEBUG Adding task: 4328 / 0x52cbfb8
Jul 07 21:00:56-938009 util-scheduler-8620 DEBUG Checking readiness of task: 4325 / 0x46620a0
Jul 07 21:00:56-938231 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:56-938423 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:56-938613 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:56-938804 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:56-938994 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:56-939184 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:56-939373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:56-939563 util-scheduler-8620 DEBUG Running task: 4327 / 0x6146380
Jul 07 21:00:56-939773 util-scheduler-8620 DEBUG Adding task: 4329 / 0x6146380
Jul 07 21:00:56-939996 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:00:56-940200 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:00:56-940408 util-scheduler-8620 DEBUG Adding task: 4330 / 0x46620a0
Jul 07 21:00:56-940653 util-scheduler-8620 DEBUG Checking readiness of task: 4330 / 0x46620a0
Jul 07 21:00:56-940847 util-scheduler-8620 DEBUG Checking readiness of task: 4325 / 0x46620a0
Jul 07 21:00:56-941038 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:00:56-941251 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:00:56-941443 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:00:56-941634 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:00:56-941826 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:00:56-942016 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:00:56-942205 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:00:56-942397 util-scheduler-8620 DEBUG Running task: 4330 / 0x46620a0
Jul 07 21:00:56-942581 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:00:56-942761 util-8620 DEBUG process_notify is running
Jul 07 21:00:56-942933 util-8620 DEBUG client_notify is running
Jul 07 21:00:56-943113 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:00:56-943307 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:00:56-943499 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:00:56-943826 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:00-410528 util-scheduler-8620 DEBUG Checking readiness of task: 4325 / 0x46620a0
Jul 07 21:01:00-410919 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:00-411117 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:00-411310 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:00-411502 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:00-411695 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:00-411886 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:00-412077 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:00-412272 util-scheduler-8620 DEBUG Running task: 4325 / 0x46620a0
Jul 07 21:01:00-412694 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:00-412951 util-scheduler-8620 DEBUG Adding task: 4331 / 0x4662248
Jul 07 21:01:00-413259 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:00-413455 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:00-413647 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:00-413837 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:00-414059 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:00-414248 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:00-414440 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:00-414629 util-scheduler-8620 DEBUG Running task: 4331 / 0x4662248
Jul 07 21:01:00-414820 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:00-415021 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:00-415253 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:00-415474 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:00-415682 util-scheduler-8620 DEBUG Adding task: 4332 / 0x46620a0
Jul 07 21:01:00-415872 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:00-416078 util-scheduler-8620 DEBUG Adding task: 4333 / 0x46620a0
Jul 07 21:01:00-416322 util-scheduler-8620 DEBUG Checking readiness of task: 4333 / 0x46620a0
Jul 07 21:01:00-416515 util-scheduler-8620 DEBUG Checking readiness of task: 4332 / 0x46620a0
Jul 07 21:01:00-416706 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:00-416897 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:00-417085 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:00-417305 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:00-417496 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:00-417688 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:00-417876 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:00-418068 util-scheduler-8620 DEBUG Running task: 4332 / 0x46620a0
Jul 07 21:01:00-418254 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:00-418433 util-8620 DEBUG process_notify is running
Jul 07 21:01:00-418606 util-8620 DEBUG client_notify is running
Jul 07 21:01:00-418793 util-scheduler-8620 DEBUG Canceling task: 4329 / 0x6146380
Jul 07 21:01:00-419153 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:00-420640 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:00-420889 cadet-p2p-8620 DEBUG Checking 0x617dcd8 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:00-421127 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:00-421337 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:00-421628 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:00-422013 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:00-422214 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:00-422396 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:00-422685 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:00-422971 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:00-423154 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:00-423440 util-scheduler-8620 DEBUG Canceling task: 4326 / 0x6146c10
Jul 07 21:01:00-423659 util-scheduler-8620 DEBUG Adding task: 4334 / 0x6146c10
Jul 07 21:01:00-424008 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:00-424277 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:00-424462 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:00-424763 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:00-424942 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:00-425239 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:00-425539 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:00-425750 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:00-426027 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:00-426209 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:00-426500 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:00-427359 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:01-939426 util-scheduler-8620 DEBUG Checking readiness of task: 4333 / 0x46620a0
Jul 07 21:01:01-939815 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:01-941030 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:01-941254 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:01-941448 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:01-941640 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:01-941832 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:01-942023 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:01-942220 util-scheduler-8620 DEBUG Running task: 4328 / 0x52cbfb8
Jul 07 21:01:01-942459 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:01-942716 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:01:01-942924 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:01-943124 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:01-943327 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:01-943564 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:01-943745 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:01-943965 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:01-944258 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:01-944456 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:01-944694 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:01-944904 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:01-945248 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:01-945453 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:01-945678 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:01-945862 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:01-946038 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:01-946244 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:01-946463 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:01-946689 util-scheduler-8620 DEBUG Adding task: 4335 / 0x6146380
Jul 07 21:01:01-946869 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:01-947073 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:01-947251 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:01-947426 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:01-947663 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:01-947860 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:01-948037 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:01-948237 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:01-948483 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:01-948681 util-scheduler-8620 DEBUG Adding task: 4336 / 0x52cbfb8
Jul 07 21:01:01-948939 util-scheduler-8620 DEBUG Checking readiness of task: 4333 / 0x46620a0
Jul 07 21:01:01-949133 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:01-949372 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:01-949563 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:01-949752 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:01-949944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:01-950132 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:01-950322 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:01-950537 util-scheduler-8620 DEBUG Running task: 4335 / 0x6146380
Jul 07 21:01:01-950748 util-scheduler-8620 DEBUG Adding task: 4337 / 0x6146380
Jul 07 21:01:01-950972 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:01-951176 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:01-951386 util-scheduler-8620 DEBUG Adding task: 4338 / 0x46620a0
Jul 07 21:01:01-951631 util-scheduler-8620 DEBUG Checking readiness of task: 4338 / 0x46620a0
Jul 07 21:01:01-951827 util-scheduler-8620 DEBUG Checking readiness of task: 4333 / 0x46620a0
Jul 07 21:01:01-952018 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:01-952208 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:01-952398 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:01-952587 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:01-952778 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:01-952979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:01-953168 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:01-953385 util-scheduler-8620 DEBUG Running task: 4338 / 0x46620a0
Jul 07 21:01:01-953571 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:01-953749 util-8620 DEBUG process_notify is running
Jul 07 21:01:01-953923 util-8620 DEBUG client_notify is running
Jul 07 21:01:01-954102 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:01-954298 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:01-954489 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:01-954814 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:05-260024 util-scheduler-8620 DEBUG Checking readiness of task: 4333 / 0x46620a0
Jul 07 21:01:05-260412 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:05-260610 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:05-260802 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:05-260995 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:05-261187 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:05-261416 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:05-261606 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:05-261802 util-scheduler-8620 DEBUG Running task: 4333 / 0x46620a0
Jul 07 21:01:05-262223 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:05-262481 util-scheduler-8620 DEBUG Adding task: 4339 / 0x4662248
Jul 07 21:01:05-262760 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:05-262955 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:05-263146 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:05-263338 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:05-263531 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:05-263721 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:05-263914 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:05-264105 util-scheduler-8620 DEBUG Running task: 4339 / 0x4662248
Jul 07 21:01:05-264296 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:05-264497 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:05-264731 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:05-264969 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:05-265178 util-scheduler-8620 DEBUG Adding task: 4340 / 0x46620a0
Jul 07 21:01:05-265395 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:05-265603 util-scheduler-8620 DEBUG Adding task: 4341 / 0x46620a0
Jul 07 21:01:05-265851 util-scheduler-8620 DEBUG Checking readiness of task: 4341 / 0x46620a0
Jul 07 21:01:05-266045 util-scheduler-8620 DEBUG Checking readiness of task: 4340 / 0x46620a0
Jul 07 21:01:05-266240 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:05-266431 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:05-266622 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:05-266813 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:05-267005 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:05-267199 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:05-267389 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:05-267583 util-scheduler-8620 DEBUG Running task: 4340 / 0x46620a0
Jul 07 21:01:05-267769 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:05-267949 util-8620 DEBUG process_notify is running
Jul 07 21:01:05-268123 util-8620 DEBUG client_notify is running
Jul 07 21:01:05-268313 util-scheduler-8620 DEBUG Canceling task: 4337 / 0x6146380
Jul 07 21:01:05-268541 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:05-268764 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:05-269006 cadet-p2p-8620 DEBUG Checking 0x6180968 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:05-269313 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:05-269495 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:05-269687 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:05-269974 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:05-270170 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:05-270353 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:05-270542 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:05-270733 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:05-270912 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:05-271097 util-scheduler-8620 DEBUG Canceling task: 4334 / 0x6146c10
Jul 07 21:01:05-271311 util-scheduler-8620 DEBUG Adding task: 4342 / 0x6146c10
Jul 07 21:01:05-271563 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:05-271734 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:05-271917 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:05-272119 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:05-272296 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:05-272472 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:05-272673 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:05-272879 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:05-273063 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:05-273267 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:05-273459 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:05-273701 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:06-950520 util-scheduler-8620 DEBUG Checking readiness of task: 4341 / 0x46620a0
Jul 07 21:01:06-950902 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:06-951099 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:06-951292 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:06-951485 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:06-951707 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:06-951899 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:06-952089 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:06-952283 util-scheduler-8620 DEBUG Running task: 4336 / 0x52cbfb8
Jul 07 21:01:06-952523 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:06-952781 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:01:06-952988 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:06-953215 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:06-953421 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:06-953658 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:06-953839 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:06-954060 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:06-954353 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:06-954550 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:06-954787 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:06-954995 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:06-955313 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:06-955515 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:06-955740 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:06-955924 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:06-956100 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:06-956317 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:06-956532 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:06-956757 util-scheduler-8620 DEBUG Adding task: 4343 / 0x6146380
Jul 07 21:01:06-956938 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:06-957141 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:06-958700 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:06-958915 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:06-959163 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:06-959362 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:06-959540 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:06-959739 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:06-959987 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:06-960188 util-scheduler-8620 DEBUG Adding task: 4344 / 0x52cbfb8
Jul 07 21:01:06-960451 util-scheduler-8620 DEBUG Checking readiness of task: 4341 / 0x46620a0
Jul 07 21:01:06-960646 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:06-960836 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:06-961026 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:06-961238 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:06-961429 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:06-961618 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:06-961806 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:06-961996 util-scheduler-8620 DEBUG Running task: 4343 / 0x6146380
Jul 07 21:01:06-962207 util-scheduler-8620 DEBUG Adding task: 4345 / 0x6146380
Jul 07 21:01:06-962429 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:06-962634 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:06-962843 util-scheduler-8620 DEBUG Adding task: 4346 / 0x46620a0
Jul 07 21:01:06-963088 util-scheduler-8620 DEBUG Checking readiness of task: 4346 / 0x46620a0
Jul 07 21:01:06-963282 util-scheduler-8620 DEBUG Checking readiness of task: 4341 / 0x46620a0
Jul 07 21:01:06-963473 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:06-963684 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:06-963875 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:06-964065 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:06-964256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:06-964444 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:06-964632 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:06-964824 util-scheduler-8620 DEBUG Running task: 4346 / 0x46620a0
Jul 07 21:01:06-965009 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:06-965211 util-8620 DEBUG process_notify is running
Jul 07 21:01:06-965388 util-8620 DEBUG client_notify is running
Jul 07 21:01:06-965567 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:06-965765 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:06-965956 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:06-966278 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:09-824692 util-scheduler-8620 DEBUG Checking readiness of task: 4341 / 0x46620a0
Jul 07 21:01:09-825074 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:09-825308 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:09-825509 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:09-825712 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:09-825905 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:09-826095 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:09-826286 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:09-826482 util-scheduler-8620 DEBUG Running task: 4341 / 0x46620a0
Jul 07 21:01:09-826903 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:09-827159 util-scheduler-8620 DEBUG Adding task: 4347 / 0x4662248
Jul 07 21:01:09-827436 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:09-827633 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:09-827824 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:09-828015 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:09-828208 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:09-828398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:09-828591 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:09-828783 util-scheduler-8620 DEBUG Running task: 4347 / 0x4662248
Jul 07 21:01:09-828974 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:09-830187 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:09-830427 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:09-830843 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:09-831260 util-scheduler-8620 DEBUG Adding task: 4348 / 0x46620a0
Jul 07 21:01:09-831452 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:09-831659 util-scheduler-8620 DEBUG Adding task: 4349 / 0x46620a0
Jul 07 21:01:09-831911 util-scheduler-8620 DEBUG Checking readiness of task: 4349 / 0x46620a0
Jul 07 21:01:09-832105 util-scheduler-8620 DEBUG Checking readiness of task: 4348 / 0x46620a0
Jul 07 21:01:09-832299 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:09-832491 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:09-832713 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:09-832904 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:09-833096 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:09-833311 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:09-833503 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:09-833694 util-scheduler-8620 DEBUG Running task: 4348 / 0x46620a0
Jul 07 21:01:09-833882 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:09-834060 util-8620 DEBUG process_notify is running
Jul 07 21:01:09-834233 util-8620 DEBUG client_notify is running
Jul 07 21:01:09-834422 util-scheduler-8620 DEBUG Canceling task: 4345 / 0x6146380
Jul 07 21:01:09-834649 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:09-834871 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:09-835113 cadet-p2p-8620 DEBUG Checking 0x61835c8 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:09-835348 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:09-835527 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:09-835718 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:09-836004 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:09-836201 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:09-836382 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:09-836571 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:09-836761 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:09-836940 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:09-837124 util-scheduler-8620 DEBUG Canceling task: 4342 / 0x6146c10
Jul 07 21:01:09-844788 util-scheduler-8620 DEBUG Adding task: 4350 / 0x6146c10
Jul 07 21:01:09-845119 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:09-845325 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:09-845518 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:09-845736 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:09-845915 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:09-846092 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:09-846294 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:09-846503 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:09-846690 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:09-846886 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:09-847079 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:09-847807 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:11-962478 util-scheduler-8620 DEBUG Checking readiness of task: 4349 / 0x46620a0
Jul 07 21:01:11-962865 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:11-963847 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:11-964064 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:11-964273 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:11-964477 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:11-964673 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:11-964862 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:11-965057 util-scheduler-8620 DEBUG Running task: 4344 / 0x52cbfb8
Jul 07 21:01:11-965319 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:11-965579 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:01:11-965785 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:11-965987 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:11-966189 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:11-966452 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:11-966633 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:11-966855 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:11-967152 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:11-967349 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:11-967587 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:11-967796 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:11-968116 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:11-968317 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:11-968542 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:11-968727 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:11-968903 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:11-969111 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:11-969346 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:11-969573 util-scheduler-8620 DEBUG Adding task: 4351 / 0x6146380
Jul 07 21:01:11-969753 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:11-969957 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:11-970134 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:11-970310 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:11-970549 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:11-970744 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:11-970922 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:11-971120 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:11-971365 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:11-971562 util-scheduler-8620 DEBUG Adding task: 4352 / 0x52cbfb8
Jul 07 21:01:11-971822 util-scheduler-8620 DEBUG Checking readiness of task: 4349 / 0x46620a0
Jul 07 21:01:11-972016 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:11-972206 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:11-972395 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:11-972585 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:11-972775 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:11-972963 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:11-973152 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:11-973364 util-scheduler-8620 DEBUG Running task: 4351 / 0x6146380
Jul 07 21:01:11-973574 util-scheduler-8620 DEBUG Adding task: 4353 / 0x6146380
Jul 07 21:01:11-973796 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:11-974000 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:11-974209 util-scheduler-8620 DEBUG Adding task: 4354 / 0x46620a0
Jul 07 21:01:11-974452 util-scheduler-8620 DEBUG Checking readiness of task: 4354 / 0x46620a0
Jul 07 21:01:11-974648 util-scheduler-8620 DEBUG Checking readiness of task: 4349 / 0x46620a0
Jul 07 21:01:11-974839 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:11-975029 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:11-975221 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:11-975412 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:11-975604 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:11-975794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:11-975982 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:11-976174 util-scheduler-8620 DEBUG Running task: 4354 / 0x46620a0
Jul 07 21:01:11-976379 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:11-976560 util-8620 DEBUG process_notify is running
Jul 07 21:01:11-976732 util-8620 DEBUG client_notify is running
Jul 07 21:01:11-976914 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:11-977110 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:11-977321 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:11-977575 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:14-373673 util-scheduler-8620 DEBUG Checking readiness of task: 4349 / 0x46620a0
Jul 07 21:01:14-373996 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:14-374194 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:14-374387 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:14-374581 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:14-374776 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:14-374965 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:14-375155 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:14-375348 util-scheduler-8620 DEBUG Running task: 4349 / 0x46620a0
Jul 07 21:01:14-375766 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:14-376014 util-scheduler-8620 DEBUG Adding task: 4355 / 0x4662248
Jul 07 21:01:14-376286 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:14-376481 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:14-376674 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:14-376864 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:14-377056 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:14-377272 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:14-377462 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:14-377652 util-scheduler-8620 DEBUG Running task: 4355 / 0x4662248
Jul 07 21:01:14-377845 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:14-378043 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:14-378273 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:14-378478 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:14-378682 util-scheduler-8620 DEBUG Adding task: 4356 / 0x46620a0
Jul 07 21:01:14-378873 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:14-379085 util-scheduler-8620 DEBUG Adding task: 4357 / 0x46620a0
Jul 07 21:01:14-379331 util-scheduler-8620 DEBUG Checking readiness of task: 4357 / 0x46620a0
Jul 07 21:01:14-379524 util-scheduler-8620 DEBUG Checking readiness of task: 4356 / 0x46620a0
Jul 07 21:01:14-379716 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:14-379906 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:14-380110 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:14-380414 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:14-380704 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:14-380993 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:14-381767 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:14-382062 util-scheduler-8620 DEBUG Running task: 4356 / 0x46620a0
Jul 07 21:01:14-382433 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:14-382707 util-8620 DEBUG process_notify is running
Jul 07 21:01:14-383002 util-8620 DEBUG client_notify is running
Jul 07 21:01:14-383376 util-scheduler-8620 DEBUG Canceling task: 4353 / 0x6146380
Jul 07 21:01:14-383708 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:14-384113 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:14-384539 cadet-p2p-8620 DEBUG Checking 0x6186250 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:14-384961 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:14-385258 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:14-385455 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:14-385747 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:14-385946 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:14-386227 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:14-386510 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:14-386705 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:14-386888 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:14-387075 util-scheduler-8620 DEBUG Canceling task: 4350 / 0x6146c10
Jul 07 21:01:14-387293 util-scheduler-8620 DEBUG Adding task: 4358 / 0x6146c10
Jul 07 21:01:14-387677 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:14-387853 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:14-388036 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:14-388240 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:14-388467 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:14-388645 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:14-388845 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:14-389103 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:14-389580 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:14-390028 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:14-390313 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:14-390558 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:16-974318 util-scheduler-8620 DEBUG Checking readiness of task: 4357 / 0x46620a0
Jul 07 21:01:16-974708 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:16-975289 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:16-975520 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:16-975757 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:16-975952 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:16-976144 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:16-976334 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:16-976527 util-scheduler-8620 DEBUG Running task: 4352 / 0x52cbfb8
Jul 07 21:01:16-976766 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:16-977025 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:01:16-977253 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:16-977457 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:16-977661 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:16-977898 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:16-978079 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:16-978301 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:16-978592 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:16-978791 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:16-979030 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:16-979237 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:16-979556 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:16-979786 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:16-980012 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:16-980196 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:16-980372 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:16-980579 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:16-980795 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:16-981021 util-scheduler-8620 DEBUG Adding task: 4359 / 0x6146380
Jul 07 21:01:16-981221 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:16-981427 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:16-981606 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:16-981781 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:16-982019 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:16-982215 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:16-982392 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:16-982591 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:16-982835 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:16-983033 util-scheduler-8620 DEBUG Adding task: 4360 / 0x52cbfb8
Jul 07 21:01:16-983293 util-scheduler-8620 DEBUG Checking readiness of task: 4357 / 0x46620a0
Jul 07 21:01:16-983486 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:16-983677 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:16-983867 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:16-984057 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:16-984248 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:16-984436 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:16-984626 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:16-984816 util-scheduler-8620 DEBUG Running task: 4359 / 0x6146380
Jul 07 21:01:16-985025 util-scheduler-8620 DEBUG Adding task: 4361 / 0x6146380
Jul 07 21:01:16-985266 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:16-985473 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:16-985682 util-scheduler-8620 DEBUG Adding task: 4362 / 0x46620a0
Jul 07 21:01:16-985927 util-scheduler-8620 DEBUG Checking readiness of task: 4362 / 0x46620a0
Jul 07 21:01:16-986122 util-scheduler-8620 DEBUG Checking readiness of task: 4357 / 0x46620a0
Jul 07 21:01:16-986312 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:16-986502 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:16-986692 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:16-986882 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:16-987072 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:16-987262 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:16-987450 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:16-987643 util-scheduler-8620 DEBUG Running task: 4362 / 0x46620a0
Jul 07 21:01:16-987827 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:16-988006 util-8620 DEBUG process_notify is running
Jul 07 21:01:16-988179 util-8620 DEBUG client_notify is running
Jul 07 21:01:16-988358 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:16-988553 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:16-988759 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:16-989014 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:18-980795 util-scheduler-8620 DEBUG Checking readiness of task: 4357 / 0x46620a0
Jul 07 21:01:18-981165 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:18-981388 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:18-981582 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:18-981774 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:18-981965 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:18-982157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:18-982346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:18-982542 util-scheduler-8620 DEBUG Running task: 4357 / 0x46620a0
Jul 07 21:01:18-982962 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:18-983214 util-scheduler-8620 DEBUG Adding task: 4363 / 0x4662248
Jul 07 21:01:18-983491 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:18-983685 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:18-983875 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:18-984066 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:18-984256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:18-984446 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:18-984635 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:18-984826 util-scheduler-8620 DEBUG Running task: 4363 / 0x4662248
Jul 07 21:01:18-985017 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:18-987423 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:18-987676 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:18-987886 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:18-988096 util-scheduler-8620 DEBUG Adding task: 4364 / 0x46620a0
Jul 07 21:01:18-988283 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:18-988491 util-scheduler-8620 DEBUG Adding task: 4365 / 0x46620a0
Jul 07 21:01:18-988738 util-scheduler-8620 DEBUG Checking readiness of task: 4365 / 0x46620a0
Jul 07 21:01:18-988934 util-scheduler-8620 DEBUG Checking readiness of task: 4364 / 0x46620a0
Jul 07 21:01:18-989128 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:18-989345 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:18-989535 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:18-989725 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:18-989915 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:18-990104 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:18-990296 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:18-990488 util-scheduler-8620 DEBUG Running task: 4364 / 0x46620a0
Jul 07 21:01:18-990674 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:18-990853 util-8620 DEBUG process_notify is running
Jul 07 21:01:18-991025 util-8620 DEBUG client_notify is running
Jul 07 21:01:18-991214 util-scheduler-8620 DEBUG Canceling task: 4361 / 0x6146380
Jul 07 21:01:18-991439 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:18-991660 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:18-991901 cadet-p2p-8620 DEBUG Checking 0x6188e58 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:18-992135 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:18-992313 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:18-992504 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:18-992817 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:18-993014 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:18-993217 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:18-993407 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:18-993596 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:18-993774 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:18-993957 util-scheduler-8620 DEBUG Canceling task: 4358 / 0x6146c10
Jul 07 21:01:18-994170 util-scheduler-8620 DEBUG Adding task: 4366 / 0x6146c10
Jul 07 21:01:18-994421 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:18-994592 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:18-994773 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:18-994973 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:18-995148 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:18-995323 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:18-995522 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:18-995728 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:18-995911 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:18-996090 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:18-996281 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:18-997135 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:21-986190 util-scheduler-8620 DEBUG Checking readiness of task: 4365 / 0x46620a0
Jul 07 21:01:21-986584 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:21-987107 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:21-987311 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:21-987577 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:21-987791 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:21-987983 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:21-988173 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:21-988367 util-scheduler-8620 DEBUG Running task: 4360 / 0x52cbfb8
Jul 07 21:01:21-988607 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:21-988865 cadet-tun-8620 DEBUG  kx started 13 m ago
Jul 07 21:01:21-989073 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:21-989315 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:21-989520 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:21-989757 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:21-989939 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:21-990160 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:21-990453 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:21-990650 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:21-990888 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:21-991098 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:21-991417 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:21-991619 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:21-991845 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:21-992028 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:21-992205 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:21-992411 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:21-992628 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:21-992854 util-scheduler-8620 DEBUG Adding task: 4367 / 0x6146380
Jul 07 21:01:21-993070 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:21-993297 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:21-993478 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:21-993653 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:21-993892 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:21-994102 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:21-994281 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:21-994479 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:21-994725 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:21-994923 util-scheduler-8620 DEBUG Adding task: 4368 / 0x52cbfb8
Jul 07 21:01:21-995182 util-scheduler-8620 DEBUG Checking readiness of task: 4365 / 0x46620a0
Jul 07 21:01:21-995378 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:21-995569 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:21-995758 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:21-995948 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:21-996138 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:21-996327 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:21-996515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:21-996704 util-scheduler-8620 DEBUG Running task: 4367 / 0x6146380
Jul 07 21:01:21-996912 util-scheduler-8620 DEBUG Adding task: 4369 / 0x6146380
Jul 07 21:01:21-997135 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:21-997362 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:21-997571 util-scheduler-8620 DEBUG Adding task: 4370 / 0x46620a0
Jul 07 21:01:21-997815 util-scheduler-8620 DEBUG Checking readiness of task: 4370 / 0x46620a0
Jul 07 21:01:21-998010 util-scheduler-8620 DEBUG Checking readiness of task: 4365 / 0x46620a0
Jul 07 21:01:21-998201 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:21-998390 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:21-998581 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:21-998771 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:21-998961 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:21-999149 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:21-999339 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:21-999530 util-scheduler-8620 DEBUG Running task: 4370 / 0x46620a0
Jul 07 21:01:21-999715 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:21-999893 util-8620 DEBUG process_notify is running
Jul 07 21:01:22-000066 util-8620 DEBUG client_notify is running
Jul 07 21:01:22-000249 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:22-000446 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:22-000641 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:22-000900 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:23-618590 util-scheduler-8620 DEBUG Checking readiness of task: 4365 / 0x46620a0
Jul 07 21:01:23-618985 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:23-619183 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:23-619376 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:23-619573 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:23-619764 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:23-619954 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:23-620185 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:23-620382 util-scheduler-8620 DEBUG Running task: 4365 / 0x46620a0
Jul 07 21:01:23-620806 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:23-621061 util-scheduler-8620 DEBUG Adding task: 4371 / 0x4662248
Jul 07 21:01:23-621375 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:23-621569 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:23-621761 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:23-621951 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:23-622144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:23-622333 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:23-622522 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:23-622711 util-scheduler-8620 DEBUG Running task: 4371 / 0x4662248
Jul 07 21:01:23-622903 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:23-623104 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:23-623336 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:23-623544 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:23-623751 util-scheduler-8620 DEBUG Adding task: 4372 / 0x46620a0
Jul 07 21:01:23-623937 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:23-624143 util-scheduler-8620 DEBUG Adding task: 4373 / 0x46620a0
Jul 07 21:01:23-624387 util-scheduler-8620 DEBUG Checking readiness of task: 4373 / 0x46620a0
Jul 07 21:01:23-624579 util-scheduler-8620 DEBUG Checking readiness of task: 4372 / 0x46620a0
Jul 07 21:01:23-624770 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:23-624961 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:23-625151 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:23-625368 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:23-625559 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:23-625751 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:23-625938 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:23-626131 util-scheduler-8620 DEBUG Running task: 4372 / 0x46620a0
Jul 07 21:01:23-626315 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:23-626495 util-8620 DEBUG process_notify is running
Jul 07 21:01:23-626666 util-8620 DEBUG client_notify is running
Jul 07 21:01:23-626856 util-scheduler-8620 DEBUG Canceling task: 4369 / 0x6146380
Jul 07 21:01:23-627080 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:23-627302 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:23-627543 cadet-p2p-8620 DEBUG Checking 0x618bb10 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:23-627778 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:23-627956 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:23-628146 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:23-628431 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:23-628627 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:23-628807 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:23-628995 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:23-629184 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:23-629390 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:23-629574 util-scheduler-8620 DEBUG Canceling task: 4366 / 0x6146c10
Jul 07 21:01:23-629785 util-scheduler-8620 DEBUG Adding task: 4374 / 0x6146c10
Jul 07 21:01:23-630054 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:23-630226 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:23-630408 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:23-630610 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:23-630785 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:23-630960 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:23-631160 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:23-631368 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:23-631552 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:23-631731 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:23-631923 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:23-632175 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:26-997372 util-scheduler-8620 DEBUG Checking readiness of task: 4373 / 0x46620a0
Jul 07 21:01:26-997770 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:26-998957 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:26-999168 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:26-999364 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:26-999570 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:26-999760 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:26-999950 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-000143 util-scheduler-8620 DEBUG Running task: 4368 / 0x52cbfb8
Jul 07 21:01:27-000386 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:27-000645 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:27-000854 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:27-001056 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:27-001284 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:27-001523 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:27-001705 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:27-001927 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:27-002219 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:27-002418 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:27-002657 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:27-002867 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:27-003192 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:27-003400 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:27-003630 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:27-003818 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:27-003997 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:27-004211 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:27-004433 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:27-004669 util-scheduler-8620 DEBUG Adding task: 4375 / 0x6146380
Jul 07 21:01:27-004855 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:27-005064 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:27-005295 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:27-005474 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:27-005716 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:27-005915 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:27-006094 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:27-006294 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:27-006542 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:27-006772 util-scheduler-8620 DEBUG Adding task: 4376 / 0x52cbfb8
Jul 07 21:01:27-007037 util-scheduler-8620 DEBUG Checking readiness of task: 4373 / 0x46620a0
Jul 07 21:01:27-007233 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:27-007425 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:27-007616 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:27-007808 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:27-007998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:27-008189 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:27-008379 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-008570 util-scheduler-8620 DEBUG Running task: 4375 / 0x6146380
Jul 07 21:01:27-008781 util-scheduler-8620 DEBUG Adding task: 4377 / 0x6146380
Jul 07 21:01:27-009004 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:27-009231 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:27-009446 util-scheduler-8620 DEBUG Adding task: 4378 / 0x46620a0
Jul 07 21:01:27-009692 util-scheduler-8620 DEBUG Checking readiness of task: 4378 / 0x46620a0
Jul 07 21:01:27-009887 util-scheduler-8620 DEBUG Checking readiness of task: 4373 / 0x46620a0
Jul 07 21:01:27-010079 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:27-010271 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:27-010462 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:27-010653 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:27-010843 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:27-011035 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:27-011224 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-011418 util-scheduler-8620 DEBUG Running task: 4378 / 0x46620a0
Jul 07 21:01:27-011603 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:27-011784 util-8620 DEBUG process_notify is running
Jul 07 21:01:27-011959 util-8620 DEBUG client_notify is running
Jul 07 21:01:27-012141 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:27-012338 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:27-012532 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:27-012853 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:27-013105 util-scheduler-8620 DEBUG Checking readiness of task: 4373 / 0x46620a0
Jul 07 21:01:27-013320 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:27-013513 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:27-013705 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:27-013896 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:27-014087 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:27-014277 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:27-014467 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-014658 util-scheduler-8620 DEBUG Running task: 4373 / 0x46620a0
Jul 07 21:01:27-015064 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:27-015295 util-scheduler-8620 DEBUG Adding task: 4379 / 0x4662248
Jul 07 21:01:27-015601 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:27-015802 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:27-015996 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:27-016206 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:27-016401 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:27-016596 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:27-016788 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-016984 util-scheduler-8620 DEBUG Running task: 4379 / 0x4662248
Jul 07 21:01:27-017179 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:27-017401 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:27-017623 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:27-017824 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:27-018027 util-scheduler-8620 DEBUG Adding task: 4380 / 0x46620a0
Jul 07 21:01:27-018213 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:27-018420 util-scheduler-8620 DEBUG Adding task: 4381 / 0x46620a0
Jul 07 21:01:27-018665 util-scheduler-8620 DEBUG Checking readiness of task: 4381 / 0x46620a0
Jul 07 21:01:27-018859 util-scheduler-8620 DEBUG Checking readiness of task: 4380 / 0x46620a0
Jul 07 21:01:27-019053 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:27-019244 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:27-019439 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:27-019631 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:27-019821 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:27-020011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:27-020202 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:27-020394 util-scheduler-8620 DEBUG Running task: 4380 / 0x46620a0
Jul 07 21:01:27-020580 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:27-020757 util-8620 DEBUG process_notify is running
Jul 07 21:01:27-020929 util-8620 DEBUG client_notify is running
Jul 07 21:01:27-021126 util-scheduler-8620 DEBUG Canceling task: 4377 / 0x6146380
Jul 07 21:01:27-021373 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:27-021592 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:27-021828 cadet-p2p-8620 DEBUG Checking 0x618e7e0 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:27-022063 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:27-022243 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:27-022432 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:27-022716 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:27-022914 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:27-023093 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:27-023283 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:27-023472 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:27-023651 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:27-023835 util-scheduler-8620 DEBUG Canceling task: 4374 / 0x6146c10
Jul 07 21:01:27-024049 util-scheduler-8620 DEBUG Adding task: 4382 / 0x6146c10
Jul 07 21:01:27-024294 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:27-024467 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:27-024648 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:27-024929 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:27-025105 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:27-025301 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:27-025501 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:27-025707 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:27-025893 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:27-026092 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:27-026285 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:27-027910 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:32-011917 util-scheduler-8620 DEBUG Checking readiness of task: 4381 / 0x46620a0
Jul 07 21:01:32-012320 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-012525 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-012723 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-012921 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-013118 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-013340 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-013536 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-013732 util-scheduler-8620 DEBUG Running task: 4376 / 0x52cbfb8
Jul 07 21:01:32-013975 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:32-014235 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:32-014445 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:32-014648 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:32-014852 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:32-015090 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:32-015273 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:32-015494 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:32-015786 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:32-015986 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:32-016225 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:32-016436 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:32-016757 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:32-016960 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:32-017187 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:32-017394 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:32-017572 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:32-017780 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:32-017999 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:32-018550 util-scheduler-8620 DEBUG Adding task: 4383 / 0x6146380
Jul 07 21:01:32-019170 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:32-019483 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:32-019666 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:32-019898 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:32-020291 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:32-020497 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:32-020768 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:32-020970 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:32-021245 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:32-021453 util-scheduler-8620 DEBUG Adding task: 4384 / 0x52cbfb8
Jul 07 21:01:32-021722 util-scheduler-8620 DEBUG Checking readiness of task: 4381 / 0x46620a0
Jul 07 21:01:32-021917 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-022108 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-022300 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-022491 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-022683 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-022873 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-023094 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-023289 util-scheduler-8620 DEBUG Running task: 4383 / 0x6146380
Jul 07 21:01:32-023500 util-scheduler-8620 DEBUG Adding task: 4385 / 0x6146380
Jul 07 21:01:32-023724 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:32-023930 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:32-024141 util-scheduler-8620 DEBUG Adding task: 4386 / 0x46620a0
Jul 07 21:01:32-024386 util-scheduler-8620 DEBUG Checking readiness of task: 4386 / 0x46620a0
Jul 07 21:01:32-024582 util-scheduler-8620 DEBUG Checking readiness of task: 4381 / 0x46620a0
Jul 07 21:01:32-024774 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-024965 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-025157 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-025369 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-025561 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-025752 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-025943 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-026136 util-scheduler-8620 DEBUG Running task: 4386 / 0x46620a0
Jul 07 21:01:32-026323 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:32-026504 util-8620 DEBUG process_notify is running
Jul 07 21:01:32-026679 util-8620 DEBUG client_notify is running
Jul 07 21:01:32-026863 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:32-027068 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:32-027265 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:32-027581 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:32-055683 util-scheduler-8620 DEBUG Checking readiness of task: 4381 / 0x46620a0
Jul 07 21:01:32-055925 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-056120 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-056313 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-056580 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-056775 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-056981 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-057173 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-057390 util-scheduler-8620 DEBUG Running task: 4381 / 0x46620a0
Jul 07 21:01:32-057801 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:32-058043 util-scheduler-8620 DEBUG Adding task: 4387 / 0x4662248
Jul 07 21:01:32-058302 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-058498 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-058691 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-058882 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-059075 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-059266 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-059456 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-059647 util-scheduler-8620 DEBUG Running task: 4387 / 0x4662248
Jul 07 21:01:32-059839 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:32-060039 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:32-060289 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:32-060493 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:32-060697 util-scheduler-8620 DEBUG Adding task: 4388 / 0x46620a0
Jul 07 21:01:32-060885 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:32-061092 util-scheduler-8620 DEBUG Adding task: 4389 / 0x46620a0
Jul 07 21:01:32-061356 util-scheduler-8620 DEBUG Checking readiness of task: 4389 / 0x46620a0
Jul 07 21:01:32-061551 util-scheduler-8620 DEBUG Checking readiness of task: 4388 / 0x46620a0
Jul 07 21:01:32-061745 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:32-061936 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:32-062127 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:32-062318 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:32-062511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:32-062704 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:32-062896 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:32-063096 util-scheduler-8620 DEBUG Running task: 4388 / 0x46620a0
Jul 07 21:01:32-063286 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:32-063470 util-8620 DEBUG process_notify is running
Jul 07 21:01:32-063646 util-8620 DEBUG client_notify is running
Jul 07 21:01:32-063839 util-scheduler-8620 DEBUG Canceling task: 4385 / 0x6146380
Jul 07 21:01:32-064072 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:32-064294 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:32-064532 cadet-p2p-8620 DEBUG Checking 0x6191210 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:32-064768 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:32-064947 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:32-065137 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:32-065445 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:32-065642 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:32-065822 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:32-066012 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:32-066202 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:32-066382 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:32-066568 util-scheduler-8620 DEBUG Canceling task: 4382 / 0x6146c10
Jul 07 21:01:32-066782 util-scheduler-8620 DEBUG Adding task: 4390 / 0x6146c10
Jul 07 21:01:32-067031 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:32-067203 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:32-067385 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:32-067587 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:32-067765 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:32-067941 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:32-068140 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:32-068346 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:32-068531 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:32-068712 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:32-068905 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:32-069782 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:37-026570 util-scheduler-8620 DEBUG Checking readiness of task: 4389 / 0x46620a0
Jul 07 21:01:37-026966 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:37-027164 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:37-027359 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:37-027583 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:37-027777 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:37-027969 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:37-028161 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:37-028370 util-scheduler-8620 DEBUG Running task: 4384 / 0x52cbfb8
Jul 07 21:01:37-028611 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:37-028872 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:37-029084 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:37-030210 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:37-030461 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:37-030706 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:37-030894 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:37-031141 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:37-031439 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:37-031639 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:37-031879 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:37-032089 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:37-032408 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:37-032611 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:37-032836 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:37-033021 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:37-033220 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:37-033431 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:37-033648 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:37-033878 util-scheduler-8620 DEBUG Adding task: 4391 / 0x6146380
Jul 07 21:01:37-034060 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:37-034265 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:37-034445 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:37-034622 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:37-034863 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:37-035060 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:37-035240 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:37-035440 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:37-035688 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:37-035887 util-scheduler-8620 DEBUG Adding task: 4392 / 0x52cbfb8
Jul 07 21:01:37-036155 util-scheduler-8620 DEBUG Checking readiness of task: 4389 / 0x46620a0
Jul 07 21:01:37-036350 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:37-036542 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:37-036747 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:37-036938 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:37-037129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:37-037341 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:37-037531 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:37-037723 util-scheduler-8620 DEBUG Running task: 4391 / 0x6146380
Jul 07 21:01:37-037933 util-scheduler-8620 DEBUG Adding task: 4393 / 0x6146380
Jul 07 21:01:37-038158 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:37-038362 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:37-038571 util-scheduler-8620 DEBUG Adding task: 4394 / 0x46620a0
Jul 07 21:01:37-038817 util-scheduler-8620 DEBUG Checking readiness of task: 4394 / 0x46620a0
Jul 07 21:01:37-039036 util-scheduler-8620 DEBUG Checking readiness of task: 4389 / 0x46620a0
Jul 07 21:01:37-039230 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:37-039421 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:37-039612 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:37-039805 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:37-039996 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:37-040188 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:37-040378 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:37-040572 util-scheduler-8620 DEBUG Running task: 4394 / 0x46620a0
Jul 07 21:01:37-040759 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:37-040939 util-8620 DEBUG process_notify is running
Jul 07 21:01:37-041114 util-8620 DEBUG client_notify is running
Jul 07 21:01:37-041316 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:37-041519 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:37-041716 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:37-042027 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:39-635799 util-scheduler-8620 DEBUG Checking readiness of task: 4389 / 0x46620a0
Jul 07 21:01:39-636194 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:39-636395 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:39-636605 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:39-636797 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:39-636990 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:39-637181 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:39-637397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:39-637593 util-scheduler-8620 DEBUG Running task: 4389 / 0x46620a0
Jul 07 21:01:39-638018 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:39-638273 util-scheduler-8620 DEBUG Adding task: 4395 / 0x4662248
Jul 07 21:01:39-638554 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:39-638747 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:39-638937 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:39-639127 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:39-639316 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:39-639507 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:39-639695 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:39-639884 util-scheduler-8620 DEBUG Running task: 4395 / 0x4662248
Jul 07 21:01:39-640074 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:39-640273 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:39-640505 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:39-640713 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:39-640920 util-scheduler-8620 DEBUG Adding task: 4396 / 0x46620a0
Jul 07 21:01:39-641108 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:39-641335 util-scheduler-8620 DEBUG Adding task: 4397 / 0x46620a0
Jul 07 21:01:39-641578 util-scheduler-8620 DEBUG Checking readiness of task: 4397 / 0x46620a0
Jul 07 21:01:39-641771 util-scheduler-8620 DEBUG Checking readiness of task: 4396 / 0x46620a0
Jul 07 21:01:39-641962 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:39-642184 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:39-642374 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:39-642564 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:39-642753 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:39-642941 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:39-643129 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:39-643322 util-scheduler-8620 DEBUG Running task: 4396 / 0x46620a0
Jul 07 21:01:39-643508 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:39-643685 util-8620 DEBUG process_notify is running
Jul 07 21:01:39-643857 util-8620 DEBUG client_notify is running
Jul 07 21:01:39-644044 util-scheduler-8620 DEBUG Canceling task: 4393 / 0x6146380
Jul 07 21:01:39-644270 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:39-644491 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:39-644730 cadet-p2p-8620 DEBUG Checking 0x61940e0 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:39-644963 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:39-645141 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:39-645354 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:39-645639 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:39-645834 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:39-646013 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:39-646201 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:39-646389 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:39-646567 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:39-646751 util-scheduler-8620 DEBUG Canceling task: 4390 / 0x6146c10
Jul 07 21:01:39-646961 util-scheduler-8620 DEBUG Adding task: 4398 / 0x6146c10
Jul 07 21:01:39-647211 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:39-647382 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:39-647561 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:39-647764 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:39-647943 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:39-648121 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:39-648323 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:39-648531 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:39-648716 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:39-648897 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:39-649088 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:39-649863 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:42-038451 util-scheduler-8620 DEBUG Checking readiness of task: 4397 / 0x46620a0
Jul 07 21:01:42-038852 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:42-039595 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:42-039960 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:42-040161 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:42-040356 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:42-040552 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:42-040745 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:42-040941 util-scheduler-8620 DEBUG Running task: 4392 / 0x52cbfb8
Jul 07 21:01:42-041182 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:42-041474 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:42-041685 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:42-041943 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:42-042150 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:42-042388 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:42-042571 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:42-042795 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:42-043090 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:42-043293 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:42-043532 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:42-043742 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:42-044063 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:42-044267 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:42-044494 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:42-044681 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:42-044858 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:42-045067 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:42-045315 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:42-045544 util-scheduler-8620 DEBUG Adding task: 4399 / 0x6146380
Jul 07 21:01:42-045726 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:42-045933 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:42-046111 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:42-046288 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:42-046529 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:42-046727 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:42-046907 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:42-047107 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:42-047354 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:42-047554 util-scheduler-8620 DEBUG Adding task: 4400 / 0x52cbfb8
Jul 07 21:01:42-047822 util-scheduler-8620 DEBUG Checking readiness of task: 4397 / 0x46620a0
Jul 07 21:01:42-048018 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:42-048210 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:42-048403 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:42-048594 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:42-048787 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:42-048978 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:42-049169 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:42-049388 util-scheduler-8620 DEBUG Running task: 4399 / 0x6146380
Jul 07 21:01:42-049598 util-scheduler-8620 DEBUG Adding task: 4401 / 0x6146380
Jul 07 21:01:42-049822 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:42-050029 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:42-050239 util-scheduler-8620 DEBUG Adding task: 4402 / 0x46620a0
Jul 07 21:01:42-050485 util-scheduler-8620 DEBUG Checking readiness of task: 4402 / 0x46620a0
Jul 07 21:01:42-050682 util-scheduler-8620 DEBUG Checking readiness of task: 4397 / 0x46620a0
Jul 07 21:01:42-050876 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:42-051067 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:42-051260 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:42-051452 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:42-051644 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:42-051835 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:42-052044 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:42-052239 util-scheduler-8620 DEBUG Running task: 4402 / 0x46620a0
Jul 07 21:01:42-052425 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:42-052607 util-8620 DEBUG process_notify is running
Jul 07 21:01:42-052782 util-8620 DEBUG client_notify is running
Jul 07 21:01:42-052964 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:42-053163 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:42-053386 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:42-053645 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:44-454155 util-scheduler-8620 DEBUG Checking readiness of task: 4397 / 0x46620a0
Jul 07 21:01:44-454544 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:44-454742 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:44-454935 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:44-455129 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:44-455321 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:44-455513 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:44-455703 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:44-455936 util-scheduler-8620 DEBUG Running task: 4397 / 0x46620a0
Jul 07 21:01:44-456360 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:44-456615 util-scheduler-8620 DEBUG Adding task: 4403 / 0x4662248
Jul 07 21:01:44-456893 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:44-457087 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:44-457307 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:44-457498 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:44-457689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:44-457878 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:44-458068 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:44-458257 util-scheduler-8620 DEBUG Running task: 4403 / 0x4662248
Jul 07 21:01:44-458449 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:44-458648 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:44-458881 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:44-459088 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:44-459295 util-scheduler-8620 DEBUG Adding task: 4404 / 0x46620a0
Jul 07 21:01:44-459482 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:44-459689 util-scheduler-8620 DEBUG Adding task: 4405 / 0x46620a0
Jul 07 21:01:44-459934 util-scheduler-8620 DEBUG Checking readiness of task: 4405 / 0x46620a0
Jul 07 21:01:44-460126 util-scheduler-8620 DEBUG Checking readiness of task: 4404 / 0x46620a0
Jul 07 21:01:44-460318 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:44-460508 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:44-460698 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:44-460889 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:44-461078 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:44-461292 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:44-461481 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:44-461673 util-scheduler-8620 DEBUG Running task: 4404 / 0x46620a0
Jul 07 21:01:44-461890 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:44-462070 util-8620 DEBUG process_notify is running
Jul 07 21:01:44-462243 util-8620 DEBUG client_notify is running
Jul 07 21:01:44-462433 util-scheduler-8620 DEBUG Canceling task: 4401 / 0x6146380
Jul 07 21:01:44-462658 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:44-462880 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:44-463123 cadet-p2p-8620 DEBUG Checking 0x6196c80 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:44-463358 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:44-463535 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:44-463739 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:44-464027 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:44-464224 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:44-464405 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:44-464593 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:44-464782 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:44-464960 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:44-465143 util-scheduler-8620 DEBUG Canceling task: 4398 / 0x6146c10
Jul 07 21:01:44-465381 util-scheduler-8620 DEBUG Adding task: 4406 / 0x6146c10
Jul 07 21:01:44-465632 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:44-465803 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:44-465985 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:44-466186 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:44-466361 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:44-466536 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:44-466734 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:44-466939 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:44-467122 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:44-467302 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:44-467492 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:44-468278 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:47-050300 util-scheduler-8620 DEBUG Checking readiness of task: 4405 / 0x46620a0
Jul 07 21:01:47-050694 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:47-051638 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:47-051848 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:47-052099 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:47-052311 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:47-052504 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:47-052697 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:47-052892 util-scheduler-8620 DEBUG Running task: 4400 / 0x52cbfb8
Jul 07 21:01:47-053134 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:47-053417 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:47-053627 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:47-053832 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:47-054038 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:47-054277 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:47-054460 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:47-054682 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:47-054974 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:47-055174 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:47-055436 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:47-055674 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:47-055996 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:47-056200 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:47-056427 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:47-056613 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:47-056791 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:47-057001 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:47-057237 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:47-057468 util-scheduler-8620 DEBUG Adding task: 4407 / 0x6146380
Jul 07 21:01:47-057651 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:47-057857 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:47-058036 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:47-058213 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:47-058455 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:47-058653 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:47-058833 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:47-059034 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:47-059280 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:47-059480 util-scheduler-8620 DEBUG Adding task: 4408 / 0x52cbfb8
Jul 07 21:01:47-059742 util-scheduler-8620 DEBUG Checking readiness of task: 4405 / 0x46620a0
Jul 07 21:01:47-059937 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:47-060130 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:47-060321 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:47-060513 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:47-060704 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:47-060896 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:47-061087 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:47-061297 util-scheduler-8620 DEBUG Running task: 4407 / 0x6146380
Jul 07 21:01:47-061510 util-scheduler-8620 DEBUG Adding task: 4409 / 0x6146380
Jul 07 21:01:47-061734 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:47-061941 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:47-062151 util-scheduler-8620 DEBUG Adding task: 4410 / 0x46620a0
Jul 07 21:01:47-062398 util-scheduler-8620 DEBUG Checking readiness of task: 4410 / 0x46620a0
Jul 07 21:01:47-062593 util-scheduler-8620 DEBUG Checking readiness of task: 4405 / 0x46620a0
Jul 07 21:01:47-062787 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:47-062979 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:47-063173 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:47-063364 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:47-063556 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:47-063747 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:47-063939 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:47-064134 util-scheduler-8620 DEBUG Running task: 4410 / 0x46620a0
Jul 07 21:01:47-064320 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:47-064502 util-8620 DEBUG process_notify is running
Jul 07 21:01:47-064676 util-8620 DEBUG client_notify is running
Jul 07 21:01:47-064858 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:47-065055 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:47-065270 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:47-065549 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:49-937535 util-scheduler-8620 DEBUG Checking readiness of task: 4405 / 0x46620a0
Jul 07 21:01:49-937913 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:49-938116 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:49-938324 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:49-938516 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:49-938709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:49-938898 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:49-939088 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:49-939286 util-scheduler-8620 DEBUG Running task: 4405 / 0x46620a0
Jul 07 21:01:49-939706 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:49-939962 util-scheduler-8620 DEBUG Adding task: 4411 / 0x4662248
Jul 07 21:01:49-940239 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:49-940435 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:49-940640 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:49-940831 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:49-941021 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:49-941238 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:49-941431 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:49-941620 util-scheduler-8620 DEBUG Running task: 4411 / 0x4662248
Jul 07 21:01:49-941813 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:49-942010 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:49-942240 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:49-942448 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:49-942654 util-scheduler-8620 DEBUG Adding task: 4412 / 0x46620a0
Jul 07 21:01:49-942841 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:49-943048 util-scheduler-8620 DEBUG Adding task: 4413 / 0x46620a0
Jul 07 21:01:49-943292 util-scheduler-8620 DEBUG Checking readiness of task: 4413 / 0x46620a0
Jul 07 21:01:49-943485 util-scheduler-8620 DEBUG Checking readiness of task: 4412 / 0x46620a0
Jul 07 21:01:49-943677 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:49-943867 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:49-944059 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:49-944250 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:49-944439 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:49-944628 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:49-944818 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:49-945009 util-scheduler-8620 DEBUG Running task: 4412 / 0x46620a0
Jul 07 21:01:49-945214 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:49-945393 util-8620 DEBUG process_notify is running
Jul 07 21:01:49-945567 util-8620 DEBUG client_notify is running
Jul 07 21:01:49-945754 util-scheduler-8620 DEBUG Canceling task: 4409 / 0x6146380
Jul 07 21:01:49-945981 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:49-946202 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:49-946441 cadet-p2p-8620 DEBUG Checking 0x6199868 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:49-946676 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:49-946882 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:49-947074 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:49-947359 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:49-947555 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:49-947736 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:49-947924 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:49-948115 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:49-948293 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:49-948477 util-scheduler-8620 DEBUG Canceling task: 4406 / 0x6146c10
Jul 07 21:01:49-948690 util-scheduler-8620 DEBUG Adding task: 4414 / 0x6146c10
Jul 07 21:01:49-948940 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:49-949111 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:49-949312 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:49-949513 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:49-949689 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:49-949863 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:49-950061 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:49-950267 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:49-950451 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:49-950629 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:49-950820 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:49-951068 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:52-061749 util-scheduler-8620 DEBUG Checking readiness of task: 4413 / 0x46620a0
Jul 07 21:01:52-062147 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:52-063307 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:52-063519 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:52-063714 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:52-063907 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:52-064100 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:52-064292 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:52-064487 util-scheduler-8620 DEBUG Running task: 4408 / 0x52cbfb8
Jul 07 21:01:52-064726 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:52-064985 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:52-065242 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:52-065449 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:52-065654 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:52-065892 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:52-066075 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:52-066298 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:52-066590 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:52-066789 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:52-067035 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:52-067247 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:52-067569 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:52-067773 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:52-068002 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:52-068190 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:52-068372 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:52-068591 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:52-068813 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:52-069077 util-scheduler-8620 DEBUG Adding task: 4415 / 0x6146380
Jul 07 21:01:52-069287 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:52-069497 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:52-069677 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:52-069855 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:52-070095 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:52-070294 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:52-070473 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:52-070673 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:52-070920 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:52-071121 util-scheduler-8620 DEBUG Adding task: 4416 / 0x52cbfb8
Jul 07 21:01:52-071383 util-scheduler-8620 DEBUG Checking readiness of task: 4413 / 0x46620a0
Jul 07 21:01:52-071579 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:52-071771 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:52-071963 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:52-072154 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:52-072346 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:52-072535 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:52-072725 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:52-072918 util-scheduler-8620 DEBUG Running task: 4415 / 0x6146380
Jul 07 21:01:52-073127 util-scheduler-8620 DEBUG Adding task: 4417 / 0x6146380
Jul 07 21:01:52-073387 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:52-073593 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:52-073804 util-scheduler-8620 DEBUG Adding task: 4418 / 0x46620a0
Jul 07 21:01:52-074049 util-scheduler-8620 DEBUG Checking readiness of task: 4418 / 0x46620a0
Jul 07 21:01:52-074247 util-scheduler-8620 DEBUG Checking readiness of task: 4413 / 0x46620a0
Jul 07 21:01:52-074439 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:52-074629 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:52-074821 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:52-075012 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:52-075204 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:52-075394 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:52-075585 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:52-075777 util-scheduler-8620 DEBUG Running task: 4418 / 0x46620a0
Jul 07 21:01:52-075965 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:52-076144 util-8620 DEBUG process_notify is running
Jul 07 21:01:52-076320 util-8620 DEBUG client_notify is running
Jul 07 21:01:52-076499 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:52-076699 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:52-076890 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:52-077221 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:53-227572 util-scheduler-8620 DEBUG Checking readiness of task: 4413 / 0x46620a0
Jul 07 21:01:53-227949 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:53-228151 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:53-228343 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:53-228535 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:53-228727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:53-228970 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:53-229163 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:53-229386 util-scheduler-8620 DEBUG Running task: 4413 / 0x46620a0
Jul 07 21:01:53-229813 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:53-230070 util-scheduler-8620 DEBUG Adding task: 4419 / 0x4662248
Jul 07 21:01:53-230346 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:53-230543 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:53-230736 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:53-230926 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:53-231118 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:53-231307 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:53-231496 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:53-231685 util-scheduler-8620 DEBUG Running task: 4419 / 0x4662248
Jul 07 21:01:53-231878 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:53-232076 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:53-232309 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:53-232515 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:53-232719 util-scheduler-8620 DEBUG Adding task: 4420 / 0x46620a0
Jul 07 21:01:53-232907 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:53-233113 util-scheduler-8620 DEBUG Adding task: 4421 / 0x46620a0
Jul 07 21:01:53-233381 util-scheduler-8620 DEBUG Checking readiness of task: 4421 / 0x46620a0
Jul 07 21:01:53-233576 util-scheduler-8620 DEBUG Checking readiness of task: 4420 / 0x46620a0
Jul 07 21:01:53-233771 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:53-233963 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:53-234450 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:53-234646 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:53-234836 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:53-235027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:53-235216 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:53-235409 util-scheduler-8620 DEBUG Running task: 4420 / 0x46620a0
Jul 07 21:01:53-235594 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:53-235772 util-8620 DEBUG process_notify is running
Jul 07 21:01:53-235947 util-8620 DEBUG client_notify is running
Jul 07 21:01:53-236135 util-scheduler-8620 DEBUG Canceling task: 4417 / 0x6146380
Jul 07 21:01:53-236366 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:53-236588 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:53-236829 cadet-p2p-8620 DEBUG Checking 0x619c630 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:53-237064 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:53-237274 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:53-237465 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:53-237752 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:53-237948 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:53-238128 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:53-238316 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:53-238505 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:53-238683 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:53-238867 util-scheduler-8620 DEBUG Canceling task: 4414 / 0x6146c10
Jul 07 21:01:53-239102 util-scheduler-8620 DEBUG Adding task: 4422 / 0x6146c10
Jul 07 21:01:53-239354 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:53-239525 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:53-239706 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:53-239908 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:53-240083 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:53-240259 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:53-240457 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:53-240663 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:53-240847 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:53-241026 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:53-241238 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:53-241490 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:57-074113 util-scheduler-8620 DEBUG Checking readiness of task: 4421 / 0x46620a0
Jul 07 21:01:57-074512 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-075694 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-076063 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-076264 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-076459 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-076652 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-076845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-077042 util-scheduler-8620 DEBUG Running task: 4416 / 0x52cbfb8
Jul 07 21:01:57-077315 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:01:57-077578 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:01:57-077788 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:01:57-077991 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:01:57-078198 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:01:57-078436 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:01:57-078620 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:01:57-078843 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:01:57-079137 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:01:57-079349 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:01:57-079590 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:01:57-079801 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:01:57-080121 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:01:57-080325 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:01:57-080552 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:01:57-080739 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:01:57-080917 cadet-con-8620 DEBUG  sendable
Jul 07 21:01:57-081128 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:01:57-081374 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:01:57-081604 util-scheduler-8620 DEBUG Adding task: 4423 / 0x6146380
Jul 07 21:01:57-081786 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:01:57-081992 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:57-082176 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:01:57-082354 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:01:57-082595 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:01:57-082793 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:01:57-082974 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:01:57-083211 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:57-083460 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:01:57-083661 util-scheduler-8620 DEBUG Adding task: 4424 / 0x52cbfb8
Jul 07 21:01:57-083929 util-scheduler-8620 DEBUG Checking readiness of task: 4421 / 0x46620a0
Jul 07 21:01:57-084127 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-084320 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-084512 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-084704 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-084897 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-085088 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-085305 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-085499 util-scheduler-8620 DEBUG Running task: 4423 / 0x6146380
Jul 07 21:01:57-085710 util-scheduler-8620 DEBUG Adding task: 4425 / 0x6146380
Jul 07 21:01:57-085936 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:01:57-086142 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:57-086352 util-scheduler-8620 DEBUG Adding task: 4426 / 0x46620a0
Jul 07 21:01:57-086598 util-scheduler-8620 DEBUG Checking readiness of task: 4426 / 0x46620a0
Jul 07 21:01:57-086795 util-scheduler-8620 DEBUG Checking readiness of task: 4421 / 0x46620a0
Jul 07 21:01:57-086988 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-087180 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-087372 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-087564 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-087755 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-087947 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-088137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-088332 util-scheduler-8620 DEBUG Running task: 4426 / 0x46620a0
Jul 07 21:01:57-088519 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:57-088701 util-8620 DEBUG process_notify is running
Jul 07 21:01:57-088877 util-8620 DEBUG client_notify is running
Jul 07 21:01:57-089058 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:01:57-089282 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:57-089477 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:01:57-089737 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:01:57-882350 util-scheduler-8620 DEBUG Checking readiness of task: 4421 / 0x46620a0
Jul 07 21:01:57-882707 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-882904 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-883097 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-883289 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-883481 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-883673 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-883873 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-884069 util-scheduler-8620 DEBUG Running task: 4421 / 0x46620a0
Jul 07 21:01:57-884495 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:01:57-884753 util-scheduler-8620 DEBUG Adding task: 4427 / 0x4662248
Jul 07 21:01:57-885033 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-885247 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-885471 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-885663 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-885854 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-886044 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-886232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-886423 util-scheduler-8620 DEBUG Running task: 4427 / 0x4662248
Jul 07 21:01:57-886614 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:01:57-886815 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:01:57-887049 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:01:57-887259 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:01:57-887466 util-scheduler-8620 DEBUG Adding task: 4428 / 0x46620a0
Jul 07 21:01:57-887655 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:01:57-887861 util-scheduler-8620 DEBUG Adding task: 4429 / 0x46620a0
Jul 07 21:01:57-888106 util-scheduler-8620 DEBUG Checking readiness of task: 4429 / 0x46620a0
Jul 07 21:01:57-888298 util-scheduler-8620 DEBUG Checking readiness of task: 4428 / 0x46620a0
Jul 07 21:01:57-888490 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:01:57-888726 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:01:57-888918 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:01:57-889111 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:01:57-889335 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:01:57-889527 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:01:57-889717 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:01:57-889909 util-scheduler-8620 DEBUG Running task: 4428 / 0x46620a0
Jul 07 21:01:57-890096 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:01:57-890275 util-8620 DEBUG process_notify is running
Jul 07 21:01:57-890447 util-8620 DEBUG client_notify is running
Jul 07 21:01:57-890635 util-scheduler-8620 DEBUG Canceling task: 4425 / 0x6146380
Jul 07 21:01:57-890863 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:01:57-891084 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:01:57-891324 cadet-p2p-8620 DEBUG Checking 0x619f2b8 towards 0V7ADHDH (->V8XX)
Jul 07 21:01:57-891558 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:01:57-891737 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:01:57-891928 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:01:57-892214 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:01:57-892409 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:01:57-892588 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:01:57-892776 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:01:57-892965 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:01:57-893143 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:01:57-893348 util-scheduler-8620 DEBUG Canceling task: 4422 / 0x6146c10
Jul 07 21:01:57-893573 util-scheduler-8620 DEBUG Adding task: 4430 / 0x6146c10
Jul 07 21:01:57-893826 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:01:57-893997 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:01:57-894178 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:01:57-894378 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:01:57-894553 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:01:57-894727 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:01:57-894925 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:01:57-895130 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:01:57-895331 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:01:57-895512 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:01:57-895703 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:01:57-895956 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:02-088012 util-scheduler-8620 DEBUG Checking readiness of task: 4429 / 0x46620a0
Jul 07 21:02:02-088397 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:02-088916 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:02-089144 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:02-089396 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:02-089593 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:02-089787 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:02-089995 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:02-090192 util-scheduler-8620 DEBUG Running task: 4424 / 0x52cbfb8
Jul 07 21:02:02-090431 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:02-090690 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:02:02-090901 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:02-091105 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:02-091309 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:02-091545 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:02-091729 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:02-091951 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:02-092243 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:02-092445 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:02-092686 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:02-092898 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:02-093241 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:02-093447 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:02-093674 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:02-093875 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:02-094065 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:02-094285 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:02-094506 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:02-094733 util-scheduler-8620 DEBUG Adding task: 4431 / 0x6146380
Jul 07 21:02:02-094917 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:02-095122 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:02-095358 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:02-095623 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:02-095870 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:02-096073 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:02-096255 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:02-096458 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:02-096709 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:02-096912 util-scheduler-8620 DEBUG Adding task: 4432 / 0x52cbfb8
Jul 07 21:02:02-097175 util-scheduler-8620 DEBUG Checking readiness of task: 4429 / 0x46620a0
Jul 07 21:02:02-097393 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:02-097586 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:02-097778 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:02-097971 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:02-098193 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:02-098388 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:02-098579 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:02-098772 util-scheduler-8620 DEBUG Running task: 4431 / 0x6146380
Jul 07 21:02:02-098983 util-scheduler-8620 DEBUG Adding task: 4433 / 0x6146380
Jul 07 21:02:02-099209 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:02-099414 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:02-099626 util-scheduler-8620 DEBUG Adding task: 4434 / 0x46620a0
Jul 07 21:02:02-099870 util-scheduler-8620 DEBUG Checking readiness of task: 4434 / 0x46620a0
Jul 07 21:02:02-100068 util-scheduler-8620 DEBUG Checking readiness of task: 4429 / 0x46620a0
Jul 07 21:02:02-100259 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:02-100450 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:02-100639 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:02-100830 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:02-101020 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:02-101229 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:02-101419 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:02-101613 util-scheduler-8620 DEBUG Running task: 4434 / 0x46620a0
Jul 07 21:02:02-101797 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:02-101976 util-8620 DEBUG process_notify is running
Jul 07 21:02:02-102150 util-8620 DEBUG client_notify is running
Jul 07 21:02:02-102329 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:02-102543 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:02-102736 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:02-102990 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:06-811348 util-scheduler-8620 DEBUG Checking readiness of task: 4429 / 0x46620a0
Jul 07 21:02:06-811717 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:06-811918 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:06-812111 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:06-812303 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:06-812497 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:06-812689 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:06-812879 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:06-813075 util-scheduler-8620 DEBUG Running task: 4429 / 0x46620a0
Jul 07 21:02:06-813534 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:06-813789 util-scheduler-8620 DEBUG Adding task: 4435 / 0x4662248
Jul 07 21:02:06-814067 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:06-814261 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:06-814453 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:06-814644 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:06-814834 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:06-815024 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:06-815213 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:06-815403 util-scheduler-8620 DEBUG Running task: 4435 / 0x4662248
Jul 07 21:02:06-815595 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:06-815832 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:06-816065 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:06-816271 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:06-816477 util-scheduler-8620 DEBUG Adding task: 4436 / 0x46620a0
Jul 07 21:02:06-816665 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:06-816871 util-scheduler-8620 DEBUG Adding task: 4437 / 0x46620a0
Jul 07 21:02:06-817115 util-scheduler-8620 DEBUG Checking readiness of task: 4437 / 0x46620a0
Jul 07 21:02:06-817333 util-scheduler-8620 DEBUG Checking readiness of task: 4436 / 0x46620a0
Jul 07 21:02:06-817526 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:06-817716 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:06-817907 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:06-818097 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:06-818288 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:06-818480 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:06-818669 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:06-818861 util-scheduler-8620 DEBUG Running task: 4436 / 0x46620a0
Jul 07 21:02:06-819046 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:06-819224 util-8620 DEBUG process_notify is running
Jul 07 21:02:06-819396 util-8620 DEBUG client_notify is running
Jul 07 21:02:06-819583 util-scheduler-8620 DEBUG Canceling task: 4433 / 0x6146380
Jul 07 21:02:06-819809 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:06-820030 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:06-820268 cadet-p2p-8620 DEBUG Checking 0x61a1ef8 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:06-820503 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:06-820682 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:06-820872 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:06-821155 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:06-821375 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:06-821556 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:06-821744 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:06-821936 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:06-822115 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:06-822299 util-scheduler-8620 DEBUG Canceling task: 4430 / 0x6146c10
Jul 07 21:02:06-822510 util-scheduler-8620 DEBUG Adding task: 4438 / 0x6146c10
Jul 07 21:02:06-822760 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:06-822931 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:06-823112 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:06-823312 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:06-823488 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:06-823662 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:06-823862 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:06-824067 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:06-824250 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:06-824429 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:06-824619 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:06-824868 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:07-097271 util-scheduler-8620 DEBUG Checking readiness of task: 4437 / 0x46620a0
Jul 07 21:02:07-097543 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-098115 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-098425 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-098624 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-098820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-099011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-099203 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-099396 util-scheduler-8620 DEBUG Running task: 4432 / 0x52cbfb8
Jul 07 21:02:07-099617 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:07-099867 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:02:07-100075 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:07-100277 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:07-100478 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:07-100709 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:07-100889 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:07-101109 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:07-101414 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:07-101611 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:07-101849 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:07-102060 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:07-102374 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:07-102575 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:07-102799 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:07-102983 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:07-103158 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:07-103364 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:07-103578 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:07-103797 util-scheduler-8620 DEBUG Adding task: 4439 / 0x6146380
Jul 07 21:02:07-103976 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:07-104179 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:07-104356 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:07-104529 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:07-104766 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:07-104962 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:07-105139 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:07-105360 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:07-105602 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:07-105800 util-scheduler-8620 DEBUG Adding task: 4440 / 0x52cbfb8
Jul 07 21:02:07-106045 util-scheduler-8620 DEBUG Checking readiness of task: 4437 / 0x46620a0
Jul 07 21:02:07-106237 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-106428 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-106618 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-106807 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-106997 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-107187 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-107375 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-107565 util-scheduler-8620 DEBUG Running task: 4439 / 0x6146380
Jul 07 21:02:07-107771 util-scheduler-8620 DEBUG Adding task: 4441 / 0x6146380
Jul 07 21:02:07-107992 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:07-108191 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:07-108396 util-scheduler-8620 DEBUG Adding task: 4442 / 0x46620a0
Jul 07 21:02:07-108653 util-scheduler-8620 DEBUG Checking readiness of task: 4442 / 0x46620a0
Jul 07 21:02:07-108847 util-scheduler-8620 DEBUG Checking readiness of task: 4437 / 0x46620a0
Jul 07 21:02:07-109038 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-109248 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-109440 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-109641 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-109832 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-110020 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-110209 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-110400 util-scheduler-8620 DEBUG Running task: 4442 / 0x46620a0
Jul 07 21:02:07-110583 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:07-110761 util-8620 DEBUG process_notify is running
Jul 07 21:02:07-110933 util-8620 DEBUG client_notify is running
Jul 07 21:02:07-111111 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:07-111303 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:07-111493 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:07-111740 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:07-115954 util-scheduler-8620 DEBUG Checking readiness of task: 4437 / 0x46620a0
Jul 07 21:02:07-116161 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-116356 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-116548 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-116741 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-116932 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-117122 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-117397 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-117591 util-scheduler-8620 DEBUG Running task: 4437 / 0x46620a0
Jul 07 21:02:07-117998 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:07-118227 util-scheduler-8620 DEBUG Adding task: 4443 / 0x4662248
Jul 07 21:02:07-118475 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-118670 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-118862 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-119053 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-119243 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-119436 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-119625 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-119815 util-scheduler-8620 DEBUG Running task: 4443 / 0x4662248
Jul 07 21:02:07-120004 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:07-120201 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:07-120415 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:07-120612 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:07-120810 util-scheduler-8620 DEBUG Adding task: 4444 / 0x46620a0
Jul 07 21:02:07-120994 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:07-121217 util-scheduler-8620 DEBUG Adding task: 4445 / 0x46620a0
Jul 07 21:02:07-121459 util-scheduler-8620 DEBUG Checking readiness of task: 4445 / 0x46620a0
Jul 07 21:02:07-121668 util-scheduler-8620 DEBUG Checking readiness of task: 4444 / 0x46620a0
Jul 07 21:02:07-121861 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:07-122052 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:07-122242 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:07-122432 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:07-122622 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:07-122812 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:07-123001 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:07-123192 util-scheduler-8620 DEBUG Running task: 4444 / 0x46620a0
Jul 07 21:02:07-123376 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:07-123552 util-8620 DEBUG process_notify is running
Jul 07 21:02:07-123721 util-8620 DEBUG client_notify is running
Jul 07 21:02:07-123905 util-scheduler-8620 DEBUG Canceling task: 4441 / 0x6146380
Jul 07 21:02:07-124127 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:07-124343 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:07-124573 cadet-p2p-8620 DEBUG Checking 0x61a4b80 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:07-124805 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:07-124983 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:07-125169 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:07-125469 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:07-125663 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:07-125840 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:07-126027 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:07-126214 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:07-126391 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:07-126572 util-scheduler-8620 DEBUG Canceling task: 4438 / 0x6146c10
Jul 07 21:02:07-126783 util-scheduler-8620 DEBUG Adding task: 4446 / 0x6146c10
Jul 07 21:02:07-127024 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:07-127194 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:07-127373 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:07-127572 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:07-127747 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:07-127920 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:07-128117 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:07-128321 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:07-128504 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:07-128681 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:07-128869 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:07-129112 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:12-110949 util-scheduler-8620 DEBUG Checking readiness of task: 4445 / 0x46620a0
Jul 07 21:02:12-111347 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:12-112001 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:12-112205 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:12-112469 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:12-112682 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:12-112873 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:12-113063 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:12-113279 util-scheduler-8620 DEBUG Running task: 4440 / 0x52cbfb8
Jul 07 21:02:12-113520 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:12-113814 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:02:12-114022 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:12-114224 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:12-114427 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:12-114663 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:12-114845 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:12-115066 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:12-115358 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:12-115557 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:12-115794 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:12-116006 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:12-116326 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:12-116528 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:12-116752 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:12-116936 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:12-117126 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:12-117354 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:12-117571 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:12-117796 util-scheduler-8620 DEBUG Adding task: 4447 / 0x6146380
Jul 07 21:02:12-117977 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:12-118181 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:12-118359 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:12-118534 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:12-118772 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:12-118969 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:12-119147 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:12-119344 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:12-119589 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:12-119787 util-scheduler-8620 DEBUG Adding task: 4448 / 0x52cbfb8
Jul 07 21:02:12-120046 util-scheduler-8620 DEBUG Checking readiness of task: 4445 / 0x46620a0
Jul 07 21:02:12-120241 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:12-120431 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:12-120621 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:12-120810 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:12-121000 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:12-121207 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:12-121398 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:12-121589 util-scheduler-8620 DEBUG Running task: 4447 / 0x6146380
Jul 07 21:02:12-121797 util-scheduler-8620 DEBUG Adding task: 4449 / 0x6146380
Jul 07 21:02:12-122019 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:12-122223 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:12-122432 util-scheduler-8620 DEBUG Adding task: 4450 / 0x46620a0
Jul 07 21:02:12-122675 util-scheduler-8620 DEBUG Checking readiness of task: 4450 / 0x46620a0
Jul 07 21:02:12-122870 util-scheduler-8620 DEBUG Checking readiness of task: 4445 / 0x46620a0
Jul 07 21:02:12-123059 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:12-123249 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:12-123439 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:12-123628 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:12-123818 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:12-124025 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:12-124215 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:12-124407 util-scheduler-8620 DEBUG Running task: 4450 / 0x46620a0
Jul 07 21:02:12-124593 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:12-124771 util-8620 DEBUG process_notify is running
Jul 07 21:02:12-124944 util-8620 DEBUG client_notify is running
Jul 07 21:02:12-125123 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:12-125341 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:12-125533 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:12-125792 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:14-895719 util-scheduler-8620 DEBUG Checking readiness of task: 4445 / 0x46620a0
Jul 07 21:02:14-896099 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:14-896297 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:14-896490 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:14-896685 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:14-896877 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:14-897070 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:14-897300 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:14-897497 util-scheduler-8620 DEBUG Running task: 4445 / 0x46620a0
Jul 07 21:02:14-897921 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:14-898176 util-scheduler-8620 DEBUG Adding task: 4451 / 0x4662248
Jul 07 21:02:14-898456 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:14-898649 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:14-898841 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:14-899031 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:14-899222 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:14-899413 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:14-899602 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:14-899795 util-scheduler-8620 DEBUG Running task: 4451 / 0x4662248
Jul 07 21:02:14-899987 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:14-900186 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:14-900418 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:14-900625 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:14-900831 util-scheduler-8620 DEBUG Adding task: 4452 / 0x46620a0
Jul 07 21:02:14-901020 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:14-901248 util-scheduler-8620 DEBUG Adding task: 4453 / 0x46620a0
Jul 07 21:02:14-901498 util-scheduler-8620 DEBUG Checking readiness of task: 4453 / 0x46620a0
Jul 07 21:02:14-901691 util-scheduler-8620 DEBUG Checking readiness of task: 4452 / 0x46620a0
Jul 07 21:02:14-901883 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:14-902073 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:14-902263 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:14-902454 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:14-902643 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:14-902834 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:14-903051 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:14-903246 util-scheduler-8620 DEBUG Running task: 4452 / 0x46620a0
Jul 07 21:02:14-903430 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:14-903610 util-8620 DEBUG process_notify is running
Jul 07 21:02:14-903782 util-8620 DEBUG client_notify is running
Jul 07 21:02:14-903970 util-scheduler-8620 DEBUG Canceling task: 4449 / 0x6146380
Jul 07 21:02:14-904197 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:14-904418 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:14-904658 cadet-p2p-8620 DEBUG Checking 0x61a7788 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:14-904893 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:14-905072 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:14-905283 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:14-905569 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:14-905765 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:14-905944 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:14-906133 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:14-906322 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:14-906500 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:14-906686 util-scheduler-8620 DEBUG Canceling task: 4446 / 0x6146c10
Jul 07 21:02:14-906900 util-scheduler-8620 DEBUG Adding task: 4454 / 0x6146c10
Jul 07 21:02:14-907151 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:14-907321 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:14-907502 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:14-907704 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:14-907880 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:14-908055 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:14-908253 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:14-908470 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:14-908654 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:14-908832 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:14-909022 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:14-909293 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:17-121380 util-scheduler-8620 DEBUG Checking readiness of task: 4453 / 0x46620a0
Jul 07 21:02:17-121764 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:17-121960 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:17-122152 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:17-122345 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:17-122536 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:17-122725 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:17-122914 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:17-123106 util-scheduler-8620 DEBUG Running task: 4448 / 0x52cbfb8
Jul 07 21:02:17-123343 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:17-123599 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:02:17-123805 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:17-124006 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:17-124208 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:17-124444 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:17-124627 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:17-124847 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:17-125137 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:17-125357 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:17-125622 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:17-125832 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:17-126149 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:17-126350 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:17-126573 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:17-126756 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:17-126930 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:17-127137 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:17-127350 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:17-127575 util-scheduler-8620 DEBUG Adding task: 4455 / 0x6146380
Jul 07 21:02:17-127755 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:17-127958 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:17-128134 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:17-128308 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:17-128546 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:17-128741 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:17-128918 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:17-129118 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:17-130159 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:17-130408 util-scheduler-8620 DEBUG Adding task: 4456 / 0x52cbfb8
Jul 07 21:02:17-130675 util-scheduler-8620 DEBUG Checking readiness of task: 4453 / 0x46620a0
Jul 07 21:02:17-130878 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:17-131070 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:17-131264 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:17-131456 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:17-131647 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:17-131839 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:17-132028 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:17-132218 util-scheduler-8620 DEBUG Running task: 4455 / 0x6146380
Jul 07 21:02:17-132428 util-scheduler-8620 DEBUG Adding task: 4457 / 0x6146380
Jul 07 21:02:17-132656 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:17-132859 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:17-133067 util-scheduler-8620 DEBUG Adding task: 4458 / 0x46620a0
Jul 07 21:02:17-133341 util-scheduler-8620 DEBUG Checking readiness of task: 4458 / 0x46620a0
Jul 07 21:02:17-133537 util-scheduler-8620 DEBUG Checking readiness of task: 4453 / 0x46620a0
Jul 07 21:02:17-133726 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:17-133914 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:17-134103 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:17-134293 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:17-134484 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:17-134672 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:17-134859 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:17-135050 util-scheduler-8620 DEBUG Running task: 4458 / 0x46620a0
Jul 07 21:02:17-135233 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:17-135413 util-8620 DEBUG process_notify is running
Jul 07 21:02:17-135584 util-8620 DEBUG client_notify is running
Jul 07 21:02:17-135763 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:17-135959 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:17-136174 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:17-136482 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:19-768002 util-scheduler-8620 DEBUG Checking readiness of task: 4453 / 0x46620a0
Jul 07 21:02:19-768390 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:19-768587 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:19-768779 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:19-768971 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:19-769162 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:19-769394 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:19-769585 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:19-769780 util-scheduler-8620 DEBUG Running task: 4453 / 0x46620a0
Jul 07 21:02:19-770201 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:19-770459 util-scheduler-8620 DEBUG Adding task: 4459 / 0x4662248
Jul 07 21:02:19-770740 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:19-770933 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:19-771124 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:19-771314 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:19-771505 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:19-771693 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:19-771883 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:19-772073 util-scheduler-8620 DEBUG Running task: 4459 / 0x4662248
Jul 07 21:02:19-772266 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:19-772467 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:19-772700 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:19-772909 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:19-773115 util-scheduler-8620 DEBUG Adding task: 4460 / 0x46620a0
Jul 07 21:02:19-773330 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:19-773538 util-scheduler-8620 DEBUG Adding task: 4461 / 0x46620a0
Jul 07 21:02:19-773780 util-scheduler-8620 DEBUG Checking readiness of task: 4461 / 0x46620a0
Jul 07 21:02:19-773974 util-scheduler-8620 DEBUG Checking readiness of task: 4460 / 0x46620a0
Jul 07 21:02:19-774166 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:19-774369 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:19-774562 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:19-774752 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:19-774943 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:19-775131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:19-775321 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:19-775512 util-scheduler-8620 DEBUG Running task: 4460 / 0x46620a0
Jul 07 21:02:19-775697 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:19-775876 util-8620 DEBUG process_notify is running
Jul 07 21:02:19-776048 util-8620 DEBUG client_notify is running
Jul 07 21:02:19-776235 util-scheduler-8620 DEBUG Canceling task: 4457 / 0x6146380
Jul 07 21:02:19-776461 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:19-776682 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:19-776923 cadet-p2p-8620 DEBUG Checking 0x61aa378 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:19-777187 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:19-777412 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:19-777604 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:19-777889 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:19-778085 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:19-778265 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:19-778453 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:19-778642 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:19-778821 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:19-779004 util-scheduler-8620 DEBUG Canceling task: 4454 / 0x6146c10
Jul 07 21:02:19-779217 util-scheduler-8620 DEBUG Adding task: 4462 / 0x6146c10
Jul 07 21:02:19-779469 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:19-779641 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:19-779824 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:19-780026 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:19-780203 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:19-780377 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:19-780576 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:19-780782 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:19-780965 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:19-781144 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:19-781363 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:19-781616 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:22-132920 util-scheduler-8620 DEBUG Checking readiness of task: 4461 / 0x46620a0
Jul 07 21:02:22-133333 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:22-133904 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:22-134137 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:22-134359 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:22-134568 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:22-134759 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:22-134950 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:22-135143 util-scheduler-8620 DEBUG Running task: 4456 / 0x52cbfb8
Jul 07 21:02:22-135380 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:22-135639 cadet-tun-8620 DEBUG  kx started 14 m ago
Jul 07 21:02:22-135847 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:22-136050 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:22-136253 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:22-136488 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:22-136668 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:22-136890 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:22-137181 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:22-137417 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:22-137655 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:22-137863 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:22-138182 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:22-138383 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:22-138609 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:22-138792 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:22-138968 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:22-139175 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:22-139414 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:22-139639 util-scheduler-8620 DEBUG Adding task: 4463 / 0x6146380
Jul 07 21:02:22-139820 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:22-140023 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:22-140201 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:22-140376 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:22-140613 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:22-140808 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:22-140986 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:22-141184 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:22-141450 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:22-141647 util-scheduler-8620 DEBUG Adding task: 4464 / 0x52cbfb8
Jul 07 21:02:22-141907 util-scheduler-8620 DEBUG Checking readiness of task: 4461 / 0x46620a0
Jul 07 21:02:22-142100 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:22-142290 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:22-142479 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:22-142669 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:22-142859 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:22-143050 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:22-143239 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:22-143428 util-scheduler-8620 DEBUG Running task: 4463 / 0x6146380
Jul 07 21:02:22-143637 util-scheduler-8620 DEBUG Adding task: 4465 / 0x6146380
Jul 07 21:02:22-143859 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:22-144062 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:22-144271 util-scheduler-8620 DEBUG Adding task: 4466 / 0x46620a0
Jul 07 21:02:22-144513 util-scheduler-8620 DEBUG Checking readiness of task: 4466 / 0x46620a0
Jul 07 21:02:22-144707 util-scheduler-8620 DEBUG Checking readiness of task: 4461 / 0x46620a0
Jul 07 21:02:22-144898 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:22-145088 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:22-145298 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:22-145488 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:22-145678 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:22-145866 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:22-146055 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:22-146267 util-scheduler-8620 DEBUG Running task: 4466 / 0x46620a0
Jul 07 21:02:22-146452 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:22-146631 util-8620 DEBUG process_notify is running
Jul 07 21:02:22-146804 util-8620 DEBUG client_notify is running
Jul 07 21:02:22-146983 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:22-147192 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:22-147383 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:22-147637 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:24-317029 util-scheduler-8620 DEBUG Checking readiness of task: 4461 / 0x46620a0
Jul 07 21:02:24-317406 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:24-317603 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:24-317796 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:24-318014 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:24-318207 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:24-318398 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:24-318589 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:24-318784 util-scheduler-8620 DEBUG Running task: 4461 / 0x46620a0
Jul 07 21:02:24-319201 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:24-319455 util-scheduler-8620 DEBUG Adding task: 4467 / 0x4662248
Jul 07 21:02:24-319726 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:24-319919 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:24-320111 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:24-320300 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:24-320493 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:24-320682 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:24-320871 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:24-321062 util-scheduler-8620 DEBUG Running task: 4467 / 0x4662248
Jul 07 21:02:24-321281 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:24-321482 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:24-321712 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:24-321919 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:24-322123 util-scheduler-8620 DEBUG Adding task: 4468 / 0x46620a0
Jul 07 21:02:24-322309 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:24-322515 util-scheduler-8620 DEBUG Adding task: 4469 / 0x46620a0
Jul 07 21:02:24-322756 util-scheduler-8620 DEBUG Checking readiness of task: 4469 / 0x46620a0
Jul 07 21:02:24-322950 util-scheduler-8620 DEBUG Checking readiness of task: 4468 / 0x46620a0
Jul 07 21:02:24-323141 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:24-323331 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:24-323520 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:24-323709 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:24-323900 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:24-324089 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:24-324276 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:24-324468 util-scheduler-8620 DEBUG Running task: 4468 / 0x46620a0
Jul 07 21:02:24-324653 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:24-324830 util-8620 DEBUG process_notify is running
Jul 07 21:02:24-325002 util-8620 DEBUG client_notify is running
Jul 07 21:02:24-325212 util-scheduler-8620 DEBUG Canceling task: 4465 / 0x6146380
Jul 07 21:02:24-325442 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:24-325662 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:24-325900 cadet-p2p-8620 DEBUG Checking 0x61ad030 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:24-326133 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:24-326314 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:24-326503 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:24-326787 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:24-327003 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:24-327182 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:24-327370 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:24-327558 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:24-327753 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:24-327938 util-scheduler-8620 DEBUG Canceling task: 4462 / 0x6146c10
Jul 07 21:02:24-328149 util-scheduler-8620 DEBUG Adding task: 4470 / 0x6146c10
Jul 07 21:02:24-328398 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:24-328569 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:24-328750 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:24-328950 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:24-329127 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:24-329328 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:24-329528 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:24-329733 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:24-329916 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:24-330095 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:24-330285 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:24-330536 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:27-144613 util-scheduler-8620 DEBUG Checking readiness of task: 4469 / 0x46620a0
Jul 07 21:02:27-144968 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:27-145778 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:27-146220 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:27-146422 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:27-146614 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:27-146806 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:27-146996 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:27-147190 util-scheduler-8620 DEBUG Running task: 4464 / 0x52cbfb8
Jul 07 21:02:27-147429 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:27-147690 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:27-147897 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:27-148099 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:27-148303 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:27-148539 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:27-148720 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:27-148941 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:27-149258 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:27-149461 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:27-149698 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:27-149910 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:27-150228 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:27-150429 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:27-150655 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:27-150838 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:27-151014 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:27-151220 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:27-151434 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:27-151661 util-scheduler-8620 DEBUG Adding task: 4471 / 0x6146380
Jul 07 21:02:27-151841 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:27-152046 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:27-152222 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:27-152398 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:27-152647 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:27-152844 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:27-153057 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:27-153278 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:27-153526 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:27-153723 util-scheduler-8620 DEBUG Adding task: 4472 / 0x52cbfb8
Jul 07 21:02:27-153991 util-scheduler-8620 DEBUG Checking readiness of task: 4469 / 0x46620a0
Jul 07 21:02:27-154185 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:27-154375 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:27-154565 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:27-154755 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:27-154944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:27-155134 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:27-155322 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:27-155512 util-scheduler-8620 DEBUG Running task: 4471 / 0x6146380
Jul 07 21:02:27-155721 util-scheduler-8620 DEBUG Adding task: 4473 / 0x6146380
Jul 07 21:02:27-155944 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:27-156149 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:27-156357 util-scheduler-8620 DEBUG Adding task: 4474 / 0x46620a0
Jul 07 21:02:27-156601 util-scheduler-8620 DEBUG Checking readiness of task: 4474 / 0x46620a0
Jul 07 21:02:27-156796 util-scheduler-8620 DEBUG Checking readiness of task: 4469 / 0x46620a0
Jul 07 21:02:27-156985 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:27-157176 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:27-157387 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:27-157577 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:27-157767 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:27-157955 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:27-158145 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:27-158336 util-scheduler-8620 DEBUG Running task: 4474 / 0x46620a0
Jul 07 21:02:27-158521 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:27-158700 util-8620 DEBUG process_notify is running
Jul 07 21:02:27-158873 util-8620 DEBUG client_notify is running
Jul 07 21:02:27-159051 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:27-159247 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:27-159439 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:27-159697 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:28-464489 util-scheduler-8620 DEBUG Checking readiness of task: 4469 / 0x46620a0
Jul 07 21:02:28-464874 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:28-465071 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:28-465291 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:28-465484 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:28-465679 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:28-465881 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:28-466071 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:28-466267 util-scheduler-8620 DEBUG Running task: 4469 / 0x46620a0
Jul 07 21:02:28-466689 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:28-466948 util-scheduler-8620 DEBUG Adding task: 4475 / 0x4662248
Jul 07 21:02:28-467260 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:28-467455 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:28-467645 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:28-467835 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:28-468025 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:28-468215 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:28-468403 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:28-468594 util-scheduler-8620 DEBUG Running task: 4475 / 0x4662248
Jul 07 21:02:28-468785 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:28-468985 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:28-469237 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:28-469447 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:28-469655 util-scheduler-8620 DEBUG Adding task: 4476 / 0x46620a0
Jul 07 21:02:28-469842 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:28-470048 util-scheduler-8620 DEBUG Adding task: 4477 / 0x46620a0
Jul 07 21:02:28-470292 util-scheduler-8620 DEBUG Checking readiness of task: 4477 / 0x46620a0
Jul 07 21:02:28-470484 util-scheduler-8620 DEBUG Checking readiness of task: 4476 / 0x46620a0
Jul 07 21:02:28-470676 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:28-470866 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:28-471056 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:28-471245 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:28-471436 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:28-471626 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:28-471814 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:28-472006 util-scheduler-8620 DEBUG Running task: 4476 / 0x46620a0
Jul 07 21:02:28-472191 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:28-472370 util-8620 DEBUG process_notify is running
Jul 07 21:02:28-472542 util-8620 DEBUG client_notify is running
Jul 07 21:02:28-472730 util-scheduler-8620 DEBUG Canceling task: 4473 / 0x6146380
Jul 07 21:02:28-472974 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:28-473216 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:28-473458 cadet-p2p-8620 DEBUG Checking 0x61afd50 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:28-473693 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:28-473872 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:28-474061 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:28-474345 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:28-474541 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:28-474725 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:28-474913 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:28-475101 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:28-475279 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:28-475462 util-scheduler-8620 DEBUG Canceling task: 4470 / 0x6146c10
Jul 07 21:02:28-475675 util-scheduler-8620 DEBUG Adding task: 4478 / 0x6146c10
Jul 07 21:02:28-475926 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:28-476097 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:28-476278 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:28-476478 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:28-476654 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:28-476828 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:28-477027 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:28-477265 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:28-477451 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:28-477631 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:28-477822 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:28-478073 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:32-157557 util-scheduler-8620 DEBUG Checking readiness of task: 4477 / 0x46620a0
Jul 07 21:02:32-157935 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:32-158423 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:32-158659 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:32-158893 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:32-159089 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:32-159279 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:32-159469 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:32-159662 util-scheduler-8620 DEBUG Running task: 4472 / 0x52cbfb8
Jul 07 21:02:32-159898 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:32-160154 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:32-160363 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:32-160566 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:32-160769 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:32-161004 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:32-161185 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:32-161431 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:32-161722 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:32-161920 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:32-162157 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:32-162367 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:32-162684 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:32-162885 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:32-163110 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:32-163293 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:32-163469 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:32-163675 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:32-163893 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:32-164117 util-scheduler-8620 DEBUG Adding task: 4479 / 0x6146380
Jul 07 21:02:32-164297 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:32-164501 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:32-164678 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:32-164852 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:32-165090 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:32-165306 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:32-165485 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:32-165683 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:32-165928 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:32-166126 util-scheduler-8620 DEBUG Adding task: 4480 / 0x52cbfb8
Jul 07 21:02:32-166383 util-scheduler-8620 DEBUG Checking readiness of task: 4477 / 0x46620a0
Jul 07 21:02:32-166577 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:32-166766 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:32-166955 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:32-167171 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:32-167362 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:32-167551 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:32-167740 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:32-167930 util-scheduler-8620 DEBUG Running task: 4479 / 0x6146380
Jul 07 21:02:32-168137 util-scheduler-8620 DEBUG Adding task: 4481 / 0x6146380
Jul 07 21:02:32-168361 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:32-168564 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:32-168772 util-scheduler-8620 DEBUG Adding task: 4482 / 0x46620a0
Jul 07 21:02:32-169016 util-scheduler-8620 DEBUG Checking readiness of task: 4482 / 0x46620a0
Jul 07 21:02:32-169230 util-scheduler-8620 DEBUG Checking readiness of task: 4477 / 0x46620a0
Jul 07 21:02:32-169422 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:32-169613 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:32-169802 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:32-169992 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:32-170183 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:32-170371 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:32-170561 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:32-170752 util-scheduler-8620 DEBUG Running task: 4482 / 0x46620a0
Jul 07 21:02:32-170938 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:32-171116 util-8620 DEBUG process_notify is running
Jul 07 21:02:32-171290 util-8620 DEBUG client_notify is running
Jul 07 21:02:32-171468 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:32-171663 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:32-171854 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:32-172109 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:33-288815 util-scheduler-8620 DEBUG Checking readiness of task: 4477 / 0x46620a0
Jul 07 21:02:33-289125 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:33-289347 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:33-289541 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:33-289733 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:33-289925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:33-290118 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:33-290317 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:33-290511 util-scheduler-8620 DEBUG Running task: 4477 / 0x46620a0
Jul 07 21:02:33-290925 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:33-291168 util-scheduler-8620 DEBUG Adding task: 4483 / 0x4662248
Jul 07 21:02:33-291433 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:33-291625 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:33-291817 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:33-292007 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:33-292197 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:33-292388 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:33-292577 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:33-292791 util-scheduler-8620 DEBUG Running task: 4483 / 0x4662248
Jul 07 21:02:33-292982 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:33-293181 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:33-293427 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:33-293631 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:33-293833 util-scheduler-8620 DEBUG Adding task: 4484 / 0x46620a0
Jul 07 21:02:33-294018 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:33-294224 util-scheduler-8620 DEBUG Adding task: 4485 / 0x46620a0
Jul 07 21:02:33-294466 util-scheduler-8620 DEBUG Checking readiness of task: 4485 / 0x46620a0
Jul 07 21:02:33-294658 util-scheduler-8620 DEBUG Checking readiness of task: 4484 / 0x46620a0
Jul 07 21:02:33-294850 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:33-295040 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:33-295230 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:33-295419 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:33-295610 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:33-295800 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:33-295990 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:33-296181 util-scheduler-8620 DEBUG Running task: 4484 / 0x46620a0
Jul 07 21:02:33-296367 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:33-296555 util-8620 DEBUG process_notify is running
Jul 07 21:02:33-296725 util-8620 DEBUG client_notify is running
Jul 07 21:02:33-296912 util-scheduler-8620 DEBUG Canceling task: 4481 / 0x6146380
Jul 07 21:02:33-297137 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:33-297377 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:33-297612 cadet-p2p-8620 DEBUG Checking 0x61b2930 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:33-297845 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:33-298024 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:33-298212 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:33-298495 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:33-298690 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:33-298870 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:33-299058 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:33-299245 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:33-299423 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:33-299605 util-scheduler-8620 DEBUG Canceling task: 4478 / 0x6146c10
Jul 07 21:02:33-299816 util-scheduler-8620 DEBUG Adding task: 4486 / 0x6146c10
Jul 07 21:02:33-300063 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:33-300234 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:33-300414 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:33-300614 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:33-300790 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:33-300965 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:33-301163 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:33-301387 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:33-301569 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:33-301748 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:33-301938 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:33-302186 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:37-170146 util-scheduler-8620 DEBUG Checking readiness of task: 4485 / 0x46620a0
Jul 07 21:02:37-170585 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:37-170817 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:37-171014 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:37-171289 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:37-171501 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:37-171693 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:37-171884 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:37-172077 util-scheduler-8620 DEBUG Running task: 4480 / 0x52cbfb8
Jul 07 21:02:37-172314 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:37-172572 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:37-172778 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:37-172980 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:37-173184 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:37-173444 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:37-173626 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:37-173846 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:37-174137 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:37-174335 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:37-174572 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:37-174781 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:37-175098 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:37-175298 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:37-175521 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:37-175705 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:37-175880 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:37-176086 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:37-176300 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:37-176523 util-scheduler-8620 DEBUG Adding task: 4487 / 0x6146380
Jul 07 21:02:37-176706 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:37-176910 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:37-177087 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:37-177300 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:37-177540 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:37-177736 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:37-177914 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:37-178111 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:37-178355 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:37-178552 util-scheduler-8620 DEBUG Adding task: 4488 / 0x52cbfb8
Jul 07 21:02:37-178809 util-scheduler-8620 DEBUG Checking readiness of task: 4485 / 0x46620a0
Jul 07 21:02:37-179002 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:37-179192 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:37-179381 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:37-179570 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:37-179760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:37-179950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:37-180138 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:37-180328 util-scheduler-8620 DEBUG Running task: 4487 / 0x6146380
Jul 07 21:02:37-180535 util-scheduler-8620 DEBUG Adding task: 4489 / 0x6146380
Jul 07 21:02:37-180756 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:37-180976 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:37-181185 util-scheduler-8620 DEBUG Adding task: 4490 / 0x46620a0
Jul 07 21:02:37-181448 util-scheduler-8620 DEBUG Checking readiness of task: 4490 / 0x46620a0
Jul 07 21:02:37-181644 util-scheduler-8620 DEBUG Checking readiness of task: 4485 / 0x46620a0
Jul 07 21:02:37-181834 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:37-182024 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:37-182215 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:37-182404 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:37-182594 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:37-182782 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:37-182971 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:37-183162 util-scheduler-8620 DEBUG Running task: 4490 / 0x46620a0
Jul 07 21:02:37-183347 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:37-183525 util-8620 DEBUG process_notify is running
Jul 07 21:02:37-183697 util-8620 DEBUG client_notify is running
Jul 07 21:02:37-183875 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:37-184071 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:37-184261 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:37-184514 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:39-979103 util-scheduler-8620 DEBUG Checking readiness of task: 4485 / 0x46620a0
Jul 07 21:02:39-979448 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:39-979646 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:39-979837 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:39-980029 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:39-980234 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:39-980425 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:39-980624 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:39-980819 util-scheduler-8620 DEBUG Running task: 4485 / 0x46620a0
Jul 07 21:02:39-981261 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:39-981513 util-scheduler-8620 DEBUG Adding task: 4491 / 0x4662248
Jul 07 21:02:39-981783 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:39-981977 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:39-982169 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:39-982359 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:39-982551 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:39-982740 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:39-982929 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:39-983118 util-scheduler-8620 DEBUG Running task: 4491 / 0x4662248
Jul 07 21:02:39-983310 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:39-983507 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:39-983734 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:39-983939 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:39-984142 util-scheduler-8620 DEBUG Adding task: 4492 / 0x46620a0
Jul 07 21:02:39-984330 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:39-984535 util-scheduler-8620 DEBUG Adding task: 4493 / 0x46620a0
Jul 07 21:02:39-984804 util-scheduler-8620 DEBUG Checking readiness of task: 4493 / 0x46620a0
Jul 07 21:02:39-984996 util-scheduler-8620 DEBUG Checking readiness of task: 4492 / 0x46620a0
Jul 07 21:02:39-985209 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:39-985402 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:39-985592 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:39-985781 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:39-985972 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:39-986161 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:39-986349 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:39-986542 util-scheduler-8620 DEBUG Running task: 4492 / 0x46620a0
Jul 07 21:02:39-986727 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:39-986905 util-8620 DEBUG process_notify is running
Jul 07 21:02:39-987075 util-8620 DEBUG client_notify is running
Jul 07 21:02:39-987262 util-scheduler-8620 DEBUG Canceling task: 4489 / 0x6146380
Jul 07 21:02:39-987490 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:39-987709 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:39-987946 cadet-p2p-8620 DEBUG Checking 0x61b5560 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:39-988179 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:39-988357 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:39-988546 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:39-988830 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:39-989025 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:39-989223 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:39-989413 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:39-989601 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:39-989779 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:39-989962 util-scheduler-8620 DEBUG Canceling task: 4486 / 0x6146c10
Jul 07 21:02:39-990177 util-scheduler-8620 DEBUG Adding task: 4494 / 0x6146c10
Jul 07 21:02:39-990427 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:39-990597 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:39-990778 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:39-990978 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:39-991154 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:39-991327 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:39-991525 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:39-991730 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:39-991913 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:39-992091 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:39-992281 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:39-992533 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:42-180893 util-scheduler-8620 DEBUG Checking readiness of task: 4493 / 0x46620a0
Jul 07 21:02:42-181286 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:42-182045 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:42-182416 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:42-182615 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:42-182809 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:42-183000 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:42-183190 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:42-183433 util-scheduler-8620 DEBUG Running task: 4488 / 0x52cbfb8
Jul 07 21:02:42-183675 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:42-183934 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:42-184144 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:42-184345 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:42-184548 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:42-184785 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:42-184966 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:42-185187 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:42-185513 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:42-185713 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:42-185950 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:42-186158 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:42-186479 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:42-186680 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:42-186905 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:42-187089 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:42-187265 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:42-187471 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:42-187686 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:42-187912 util-scheduler-8620 DEBUG Adding task: 4495 / 0x6146380
Jul 07 21:02:42-188092 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:42-188297 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:42-188474 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:42-188649 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:42-188886 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:42-189083 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:42-189288 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:42-189489 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:42-189734 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:42-189932 util-scheduler-8620 DEBUG Adding task: 4496 / 0x52cbfb8
Jul 07 21:02:42-190200 util-scheduler-8620 DEBUG Checking readiness of task: 4493 / 0x46620a0
Jul 07 21:02:42-190393 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:42-190597 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:42-190788 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:42-190978 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:42-191168 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:42-191356 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:42-191544 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:42-191734 util-scheduler-8620 DEBUG Running task: 4495 / 0x6146380
Jul 07 21:02:42-191942 util-scheduler-8620 DEBUG Adding task: 4497 / 0x6146380
Jul 07 21:02:42-192165 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:42-192369 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:42-192577 util-scheduler-8620 DEBUG Adding task: 4498 / 0x46620a0
Jul 07 21:02:42-192823 util-scheduler-8620 DEBUG Checking readiness of task: 4498 / 0x46620a0
Jul 07 21:02:42-193017 util-scheduler-8620 DEBUG Checking readiness of task: 4493 / 0x46620a0
Jul 07 21:02:42-193233 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:42-193426 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:42-193615 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:42-193806 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:42-194017 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:42-194211 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:42-194401 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:42-194593 util-scheduler-8620 DEBUG Running task: 4498 / 0x46620a0
Jul 07 21:02:42-194778 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:42-194958 util-8620 DEBUG process_notify is running
Jul 07 21:02:42-195131 util-8620 DEBUG client_notify is running
Jul 07 21:02:42-195311 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:42-195506 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:42-195698 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:42-195955 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:44-192266 util-scheduler-8620 DEBUG Checking readiness of task: 4493 / 0x46620a0
Jul 07 21:02:44-192622 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:44-192818 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:44-193010 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:44-193235 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:44-193430 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:44-193622 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:44-193816 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:44-194011 util-scheduler-8620 DEBUG Running task: 4493 / 0x46620a0
Jul 07 21:02:44-194432 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:44-194687 util-scheduler-8620 DEBUG Adding task: 4499 / 0x4662248
Jul 07 21:02:44-194960 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:44-195156 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:44-195347 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:44-195538 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:44-195727 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:44-195917 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:44-196106 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:44-196295 util-scheduler-8620 DEBUG Running task: 4499 / 0x4662248
Jul 07 21:02:44-196487 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:44-196686 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:44-196916 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:44-197123 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:44-197358 util-scheduler-8620 DEBUG Adding task: 4500 / 0x46620a0
Jul 07 21:02:44-197546 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:44-197752 util-scheduler-8620 DEBUG Adding task: 4501 / 0x46620a0
Jul 07 21:02:44-197996 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:44-198188 util-scheduler-8620 DEBUG Checking readiness of task: 4500 / 0x46620a0
Jul 07 21:02:44-198381 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:44-198570 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:44-198759 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:44-198949 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:44-199139 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:44-199359 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:44-199547 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:44-199739 util-scheduler-8620 DEBUG Running task: 4500 / 0x46620a0
Jul 07 21:02:44-199923 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:44-200101 util-8620 DEBUG process_notify is running
Jul 07 21:02:44-200272 util-8620 DEBUG client_notify is running
Jul 07 21:02:44-200461 util-scheduler-8620 DEBUG Canceling task: 4497 / 0x6146380
Jul 07 21:02:44-200685 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:44-200906 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:44-201144 cadet-p2p-8620 DEBUG Checking 0x61b8200 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:44-201408 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:44-201587 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:44-201776 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:44-202061 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:44-202257 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:44-202436 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:44-202623 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:44-202811 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:44-202989 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:44-203172 util-scheduler-8620 DEBUG Canceling task: 4494 / 0x6146c10
Jul 07 21:02:44-203384 util-scheduler-8620 DEBUG Adding task: 4502 / 0x6146c10
Jul 07 21:02:44-203633 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:44-203803 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:44-203984 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:44-204184 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:44-204359 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:44-204533 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:44-204735 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:44-204940 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:44-205124 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:44-205330 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:44-205520 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:44-205772 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:45-991789 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:45-992156 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:45-992353 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:45-992547 util-scheduler-8620 DEBUG Checking readiness of task: 4087 / 0x465ee60
Jul 07 21:02:45-992744 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:45-992936 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:45-993127 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:45-993359 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:45-993555 util-scheduler-8620 DEBUG Running task: 4087 / 0x465ee60
Jul 07 21:02:45-993976 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 21:02:45-994228 util-scheduler-8620 DEBUG Adding task: 4503 / 0x465f008
Jul 07 21:02:45-994512 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:45-994705 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:45-994896 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:45-995086 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:45-995306 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:45-995496 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:45-995686 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:45-995875 util-scheduler-8620 DEBUG Running task: 4503 / 0x465f008
Jul 07 21:02:45-996066 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 21:02:45-996304 nse-api-8620 DEBUG Received information about peer `F151' from peerinfo database
Jul 07 21:02:45-996491 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 21:02:45-996702 util-scheduler-8620 DEBUG Adding task: 4504 / 0x465f008
Jul 07 21:02:45-996939 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:45-997133 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:45-997354 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:45-997545 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:45-997737 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:45-997926 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:45-998115 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:45-998305 util-scheduler-8620 DEBUG Running task: 4504 / 0x465f008
Jul 07 21:02:45-998495 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:02:45-998712 nse-api-8620 DEBUG Received information about peer `F151' from peerinfo database
Jul 07 21:02:45-998986 cadet-hll-8620 DEBUG  hello for F151 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:02:45-999255 cadet-p2p-8620 DEBUG set hello for F151
Jul 07 21:02:45-999433 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 21:02:45-999621 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:45-999831 util-scheduler-8620 DEBUG Adding task: 4505 / 0x465ee60
Jul 07 21:02:47-191296 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:47-191682 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:47-191881 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:47-192073 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:47-192268 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:47-192460 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:47-192651 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:47-192842 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:47-193035 util-scheduler-8620 DEBUG Running task: 4496 / 0x52cbfb8
Jul 07 21:02:47-193302 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:47-193562 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:47-193770 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:47-193971 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:47-194174 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:47-194411 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:47-194592 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:47-194813 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:47-195105 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:47-195302 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:47-195540 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:47-195748 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:47-196067 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:47-196324 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:47-196563 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:47-196782 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:47-196961 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:47-197170 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:47-198493 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:47-198752 util-scheduler-8620 DEBUG Adding task: 4506 / 0x6146380
Jul 07 21:02:47-198935 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:47-199141 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:47-199319 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:47-199499 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:47-199738 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:47-199936 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:47-200114 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:47-200312 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:47-200558 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:47-200756 util-scheduler-8620 DEBUG Adding task: 4507 / 0x52cbfb8
Jul 07 21:02:47-201017 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:47-201236 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:47-201428 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:47-201618 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:47-201808 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:47-201998 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:47-202186 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:47-202376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:47-202565 util-scheduler-8620 DEBUG Running task: 4506 / 0x6146380
Jul 07 21:02:47-202775 util-scheduler-8620 DEBUG Adding task: 4508 / 0x6146380
Jul 07 21:02:47-202998 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:47-203204 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:47-203412 util-scheduler-8620 DEBUG Adding task: 4509 / 0x46620a0
Jul 07 21:02:47-203656 util-scheduler-8620 DEBUG Checking readiness of task: 4509 / 0x46620a0
Jul 07 21:02:47-203850 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:47-204041 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:47-204231 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:47-204422 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:47-204612 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:47-204801 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:47-204990 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:47-205180 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:47-205396 util-scheduler-8620 DEBUG Running task: 4509 / 0x46620a0
Jul 07 21:02:47-205582 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:47-205761 util-8620 DEBUG process_notify is running
Jul 07 21:02:47-205934 util-8620 DEBUG client_notify is running
Jul 07 21:02:47-206114 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:47-206310 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:47-206502 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:47-206814 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:48-423909 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:48-424293 util-scheduler-8620 DEBUG Checking readiness of task: 4501 / 0x46620a0
Jul 07 21:02:48-424492 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:48-424721 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:48-424914 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:48-425107 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:48-425336 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:48-425539 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:48-425734 util-scheduler-8620 DEBUG Running task: 4501 / 0x46620a0
Jul 07 21:02:48-426158 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:48-426413 util-scheduler-8620 DEBUG Adding task: 4510 / 0x4662248
Jul 07 21:02:48-426691 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:48-426886 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:48-427077 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:48-427268 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:48-427460 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:48-427649 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:48-427838 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:48-428026 util-scheduler-8620 DEBUG Running task: 4510 / 0x4662248
Jul 07 21:02:48-428217 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:48-428418 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:48-428649 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:48-428857 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:48-429063 util-scheduler-8620 DEBUG Adding task: 4511 / 0x46620a0
Jul 07 21:02:48-429278 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:48-429485 util-scheduler-8620 DEBUG Adding task: 4512 / 0x46620a0
Jul 07 21:02:48-429730 util-scheduler-8620 DEBUG Checking readiness of task: 4512 / 0x46620a0
Jul 07 21:02:48-429923 util-scheduler-8620 DEBUG Checking readiness of task: 4511 / 0x46620a0
Jul 07 21:02:48-430114 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:48-430305 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:48-430496 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:48-430685 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:48-430875 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:48-431064 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:48-431253 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:48-431446 util-scheduler-8620 DEBUG Running task: 4511 / 0x46620a0
Jul 07 21:02:48-431631 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:48-431810 util-8620 DEBUG process_notify is running
Jul 07 21:02:48-431982 util-8620 DEBUG client_notify is running
Jul 07 21:02:48-432171 util-scheduler-8620 DEBUG Canceling task: 4508 / 0x6146380
Jul 07 21:02:48-432397 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:48-432619 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:48-432859 cadet-p2p-8620 DEBUG Checking 0x61bb848 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:48-433094 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:48-433298 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:48-433490 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:48-433775 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:48-433971 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:48-434169 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:48-434358 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:48-434548 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:48-434727 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:48-434910 util-scheduler-8620 DEBUG Canceling task: 4502 / 0x6146c10
Jul 07 21:02:48-435122 util-scheduler-8620 DEBUG Adding task: 4513 / 0x6146c10
Jul 07 21:02:48-435373 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:48-435545 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:48-435727 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:48-435933 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:48-436108 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:48-436281 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:48-436481 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:48-436686 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:48-436870 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:48-437050 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:48-437266 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:48-437520 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:52-202744 util-scheduler-8620 DEBUG Checking readiness of task: 4512 / 0x46620a0
Jul 07 21:02:52-203133 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-203957 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-204337 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-204535 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-204729 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-204919 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-205110 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-205338 util-scheduler-8620 DEBUG Running task: 4507 / 0x52cbfb8
Jul 07 21:02:52-205579 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:52-205837 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:52-206045 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:52-206247 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:52-206452 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:52-206688 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:52-206870 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:52-207094 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:52-207386 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:52-207583 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:52-207820 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:52-208028 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:52-208346 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:52-208547 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:52-208771 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:52-208955 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:52-209130 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:52-209366 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:52-209582 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:52-209815 util-scheduler-8620 DEBUG Adding task: 4514 / 0x6146380
Jul 07 21:02:52-209998 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:52-210202 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:52-210380 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:52-210554 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:52-210826 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:52-211022 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:52-211200 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:52-211398 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:52-211643 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:52-211842 util-scheduler-8620 DEBUG Adding task: 4515 / 0x52cbfb8
Jul 07 21:02:52-212109 util-scheduler-8620 DEBUG Checking readiness of task: 4512 / 0x46620a0
Jul 07 21:02:52-212304 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-212496 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-212692 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-212882 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-213084 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-213302 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-213492 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-213682 util-scheduler-8620 DEBUG Running task: 4514 / 0x6146380
Jul 07 21:02:52-213891 util-scheduler-8620 DEBUG Adding task: 4516 / 0x6146380
Jul 07 21:02:52-214113 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:52-214318 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:52-214526 util-scheduler-8620 DEBUG Adding task: 4517 / 0x46620a0
Jul 07 21:02:52-214771 util-scheduler-8620 DEBUG Checking readiness of task: 4517 / 0x46620a0
Jul 07 21:02:52-214965 util-scheduler-8620 DEBUG Checking readiness of task: 4512 / 0x46620a0
Jul 07 21:02:52-215155 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-215345 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-215534 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-215725 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-215915 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-216104 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-216292 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-216484 util-scheduler-8620 DEBUG Running task: 4517 / 0x46620a0
Jul 07 21:02:52-216668 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:52-216848 util-8620 DEBUG process_notify is running
Jul 07 21:02:52-217024 util-8620 DEBUG client_notify is running
Jul 07 21:02:52-217229 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:52-217426 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:52-217619 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:52-217876 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:52-218123 util-scheduler-8620 DEBUG Checking readiness of task: 4512 / 0x46620a0
Jul 07 21:02:52-218316 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-218506 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-218696 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-218885 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-219074 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-219263 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-219451 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-219640 util-scheduler-8620 DEBUG Running task: 4512 / 0x46620a0
Jul 07 21:02:52-220045 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:02:52-220292 util-scheduler-8620 DEBUG Adding task: 4518 / 0x4662248
Jul 07 21:02:52-220540 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-220733 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-220923 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-221114 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-221330 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-221519 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-221708 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-221897 util-scheduler-8620 DEBUG Running task: 4518 / 0x4662248
Jul 07 21:02:52-222086 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:02:52-222282 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:02:52-222499 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:02:52-222697 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:52-222896 util-scheduler-8620 DEBUG Adding task: 4519 / 0x46620a0
Jul 07 21:02:52-223081 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:02:52-223285 util-scheduler-8620 DEBUG Adding task: 4520 / 0x46620a0
Jul 07 21:02:52-223526 util-scheduler-8620 DEBUG Checking readiness of task: 4520 / 0x46620a0
Jul 07 21:02:52-223719 util-scheduler-8620 DEBUG Checking readiness of task: 4519 / 0x46620a0
Jul 07 21:02:52-223910 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:52-224099 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:52-224289 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:52-224478 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:52-224668 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:52-224856 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:52-225045 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:52-225261 util-scheduler-8620 DEBUG Running task: 4519 / 0x46620a0
Jul 07 21:02:52-225446 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:52-225621 util-8620 DEBUG process_notify is running
Jul 07 21:02:52-225791 util-8620 DEBUG client_notify is running
Jul 07 21:02:52-225976 util-scheduler-8620 DEBUG Canceling task: 4516 / 0x6146380
Jul 07 21:02:52-226201 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:02:52-226418 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:02:52-226649 cadet-p2p-8620 DEBUG Checking 0x61be498 towards 0V7ADHDH (->V8XX)
Jul 07 21:02:52-226882 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:02:52-227066 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:02:52-227252 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:02:52-227535 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:02:52-227730 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:02:52-227910 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:02:52-228097 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:02:52-228285 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:02:52-228463 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:02:52-228647 util-scheduler-8620 DEBUG Canceling task: 4513 / 0x6146c10
Jul 07 21:02:52-228858 util-scheduler-8620 DEBUG Adding task: 4521 / 0x6146c10
Jul 07 21:02:52-229101 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:02:52-229298 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:02:52-229480 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:02:52-229682 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:52-229876 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:02:52-230051 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:02:52-230250 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:52-230454 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:02:52-230639 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:02:52-230817 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:52-231005 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:02:52-231253 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:02:57-216992 util-scheduler-8620 DEBUG Checking readiness of task: 4520 / 0x46620a0
Jul 07 21:02:57-217420 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:57-218238 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:57-218436 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:57-218629 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:57-218821 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:57-219011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:57-219200 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:57-219393 util-scheduler-8620 DEBUG Running task: 4515 / 0x52cbfb8
Jul 07 21:02:57-219631 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:02:57-219889 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:02:57-220096 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:02:57-220295 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:02:57-220496 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:02:57-220745 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:02:57-220926 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:02:57-221150 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:02:57-221471 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:02:57-221671 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:02:57-221914 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:02:57-222123 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:02:57-222449 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:02:57-222655 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:02:57-222886 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:02:57-223072 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:02:57-223250 cadet-con-8620 DEBUG  sendable
Jul 07 21:02:57-223461 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:02:57-223676 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:02:57-223905 util-scheduler-8620 DEBUG Adding task: 4522 / 0x6146380
Jul 07 21:02:57-224085 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:02:57-224289 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:02:57-224466 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:02:57-224641 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:02:57-224878 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:02:57-225073 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:02:57-225290 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:02:57-225490 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:02:57-225736 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:02:57-225934 util-scheduler-8620 DEBUG Adding task: 4523 / 0x52cbfb8
Jul 07 21:02:57-226195 util-scheduler-8620 DEBUG Checking readiness of task: 4520 / 0x46620a0
Jul 07 21:02:57-226390 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:57-226616 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:57-226808 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:57-226996 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:57-227185 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:57-227373 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:57-227560 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:57-227751 util-scheduler-8620 DEBUG Running task: 4522 / 0x6146380
Jul 07 21:02:57-227959 util-scheduler-8620 DEBUG Adding task: 4524 / 0x6146380
Jul 07 21:02:57-228182 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:02:57-228386 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:02:57-228595 util-scheduler-8620 DEBUG Adding task: 4525 / 0x46620a0
Jul 07 21:02:57-228839 util-scheduler-8620 DEBUG Checking readiness of task: 4525 / 0x46620a0
Jul 07 21:02:57-229033 util-scheduler-8620 DEBUG Checking readiness of task: 4520 / 0x46620a0
Jul 07 21:02:57-229243 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:02:57-229434 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:02:57-229624 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:02:57-229812 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:02:57-230002 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:02:57-230189 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:02:57-230378 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:02:57-230569 util-scheduler-8620 DEBUG Running task: 4525 / 0x46620a0
Jul 07 21:02:57-230754 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:02:57-230933 util-8620 DEBUG process_notify is running
Jul 07 21:02:57-231105 util-8620 DEBUG client_notify is running
Jul 07 21:02:57-231285 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:02:57-231479 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:02:57-231670 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:02:57-231982 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:00-776580 util-scheduler-8620 DEBUG Checking readiness of task: 4520 / 0x46620a0
Jul 07 21:03:00-776952 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:00-777149 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:00-777365 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:00-777568 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:00-777760 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:00-777950 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:00-778140 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:00-778334 util-scheduler-8620 DEBUG Running task: 4520 / 0x46620a0
Jul 07 21:03:00-778754 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:00-779008 util-scheduler-8620 DEBUG Adding task: 4526 / 0x4662248
Jul 07 21:03:00-779285 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:00-779477 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:00-779667 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:00-779857 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:00-780047 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:00-780265 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:00-780455 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:00-780645 util-scheduler-8620 DEBUG Running task: 4526 / 0x4662248
Jul 07 21:03:00-780835 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:00-781035 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:00-781957 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:00-782195 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:00-782409 util-scheduler-8620 DEBUG Adding task: 4527 / 0x46620a0
Jul 07 21:03:00-782683 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:00-782893 util-scheduler-8620 DEBUG Adding task: 4528 / 0x46620a0
Jul 07 21:03:00-783160 util-scheduler-8620 DEBUG Checking readiness of task: 4528 / 0x46620a0
Jul 07 21:03:00-783360 util-scheduler-8620 DEBUG Checking readiness of task: 4527 / 0x46620a0
Jul 07 21:03:00-783558 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:00-783751 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:00-784010 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:00-784203 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:00-784393 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:00-784582 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:00-784769 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:00-784962 util-scheduler-8620 DEBUG Running task: 4527 / 0x46620a0
Jul 07 21:03:00-785147 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:00-785347 util-8620 DEBUG process_notify is running
Jul 07 21:03:00-785519 util-8620 DEBUG client_notify is running
Jul 07 21:03:00-785708 util-scheduler-8620 DEBUG Canceling task: 4524 / 0x6146380
Jul 07 21:03:00-785937 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:00-786157 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:00-786397 cadet-p2p-8620 DEBUG Checking 0x61c1130 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:00-786630 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:00-786808 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:00-786998 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:00-787284 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:00-787493 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:00-787673 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:00-787860 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:00-788049 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:00-788226 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:00-788408 util-scheduler-8620 DEBUG Canceling task: 4521 / 0x6146c10
Jul 07 21:03:00-788622 util-scheduler-8620 DEBUG Adding task: 4529 / 0x6146c10
Jul 07 21:03:00-788871 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:00-789041 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:00-789241 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:00-789442 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:00-789619 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:00-789792 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:00-789991 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:00-790195 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:00-790378 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:00-790557 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:00-790745 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:00-791522 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:02-227543 util-scheduler-8620 DEBUG Checking readiness of task: 4528 / 0x46620a0
Jul 07 21:03:02-227939 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:02-228694 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:02-229154 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:02-229379 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:02-229573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:02-229764 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:02-229955 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:02-230149 util-scheduler-8620 DEBUG Running task: 4523 / 0x52cbfb8
Jul 07 21:03:02-230387 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:02-230645 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:03:02-230852 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:02-231054 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:02-231256 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:02-231491 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:02-231672 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:02-231893 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:02-232185 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:02-232383 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:02-232621 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:02-232829 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:02-233148 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:02-233370 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:02-233595 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:02-233779 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:02-233955 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:02-234163 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:02-234448 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:02-234754 util-scheduler-8620 DEBUG Adding task: 4530 / 0x6146380
Jul 07 21:03:02-234937 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:02-235141 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:02-235318 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:02-235494 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:02-235734 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:02-235932 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:02-236109 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:02-236308 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:02-236552 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:02-236750 util-scheduler-8620 DEBUG Adding task: 4531 / 0x52cbfb8
Jul 07 21:03:02-237015 util-scheduler-8620 DEBUG Checking readiness of task: 4528 / 0x46620a0
Jul 07 21:03:02-237231 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:02-237424 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:02-237614 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:02-237805 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:02-237995 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:02-238184 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:02-238373 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:02-238561 util-scheduler-8620 DEBUG Running task: 4530 / 0x6146380
Jul 07 21:03:02-238808 util-scheduler-8620 DEBUG Adding task: 4532 / 0x6146380
Jul 07 21:03:02-239033 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:02-239238 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:02-239446 util-scheduler-8620 DEBUG Adding task: 4533 / 0x46620a0
Jul 07 21:03:02-239690 util-scheduler-8620 DEBUG Checking readiness of task: 4533 / 0x46620a0
Jul 07 21:03:02-239885 util-scheduler-8620 DEBUG Checking readiness of task: 4528 / 0x46620a0
Jul 07 21:03:02-240077 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:02-240268 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:02-240459 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:02-240649 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:02-240839 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:02-241027 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:02-241236 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:02-241430 util-scheduler-8620 DEBUG Running task: 4533 / 0x46620a0
Jul 07 21:03:02-241614 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:02-241793 util-8620 DEBUG process_notify is running
Jul 07 21:03:02-241966 util-8620 DEBUG client_notify is running
Jul 07 21:03:02-242146 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:02-242341 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:02-242533 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:02-242788 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:03-961983 util-scheduler-8620 DEBUG Checking readiness of task: 4528 / 0x46620a0
Jul 07 21:03:03-962354 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:03-962552 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:03-962744 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:03-962938 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:03-963130 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:03-963325 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:03-963515 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:03-963711 util-scheduler-8620 DEBUG Running task: 4528 / 0x46620a0
Jul 07 21:03:03-964136 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:03-964393 util-scheduler-8620 DEBUG Adding task: 4534 / 0x4662248
Jul 07 21:03:03-964672 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:03-964866 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:03-965058 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:03-965284 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:03-965489 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:03-965679 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:03-965872 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:03-966063 util-scheduler-8620 DEBUG Running task: 4534 / 0x4662248
Jul 07 21:03:03-966253 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:03-966454 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:03-966688 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:03-966896 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:03-967103 util-scheduler-8620 DEBUG Adding task: 4535 / 0x46620a0
Jul 07 21:03:03-967321 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:03-967529 util-scheduler-8620 DEBUG Adding task: 4536 / 0x46620a0
Jul 07 21:03:03-967775 util-scheduler-8620 DEBUG Checking readiness of task: 4536 / 0x46620a0
Jul 07 21:03:03-967967 util-scheduler-8620 DEBUG Checking readiness of task: 4535 / 0x46620a0
Jul 07 21:03:03-968160 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:03-968351 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:03-968541 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:03-968731 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:03-968922 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:03-969110 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:03-969327 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:03-969520 util-scheduler-8620 DEBUG Running task: 4535 / 0x46620a0
Jul 07 21:03:03-969706 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:03-969885 util-8620 DEBUG process_notify is running
Jul 07 21:03:03-970057 util-8620 DEBUG client_notify is running
Jul 07 21:03:03-970246 util-scheduler-8620 DEBUG Canceling task: 4532 / 0x6146380
Jul 07 21:03:03-970471 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:03-970692 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:03-970932 cadet-p2p-8620 DEBUG Checking 0x61c3dc0 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:03-971167 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:03-971345 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:03-971536 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:03-971823 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:03-972019 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:03-972200 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:03-972387 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:03-972576 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:03-972755 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:03-972939 util-scheduler-8620 DEBUG Canceling task: 4529 / 0x6146c10
Jul 07 21:03:03-973151 util-scheduler-8620 DEBUG Adding task: 4537 / 0x6146c10
Jul 07 21:03:03-973432 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:03-973604 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:03-973785 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:03-973987 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:03-974162 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:03-974338 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:03-974536 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:03-974742 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:03-974925 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:03-975105 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:03-975296 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:03-975548 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:07-240174 util-scheduler-8620 DEBUG Checking readiness of task: 4536 / 0x46620a0
Jul 07 21:03:07-240560 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-240760 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-241368 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-241605 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-241842 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-242060 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-242252 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-242446 util-scheduler-8620 DEBUG Running task: 4531 / 0x52cbfb8
Jul 07 21:03:07-242682 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:07-242938 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:03:07-243145 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:07-243347 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:07-243549 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:07-243785 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:07-243965 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:07-244223 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:07-244514 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:07-244713 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:07-244950 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:07-245181 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:07-245548 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:07-245750 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:07-245975 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:07-246158 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:07-246334 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:07-246558 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:07-246776 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:07-247000 util-scheduler-8620 DEBUG Adding task: 4538 / 0x6146380
Jul 07 21:03:07-247180 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:07-247384 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:07-247582 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:07-247757 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:07-247995 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:07-248193 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:07-248371 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:07-248587 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:07-248833 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:07-249032 util-scheduler-8620 DEBUG Adding task: 4539 / 0x52cbfb8
Jul 07 21:03:07-249310 util-scheduler-8620 DEBUG Checking readiness of task: 4536 / 0x46620a0
Jul 07 21:03:07-249504 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-249722 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-249913 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-250104 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-250295 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-250486 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-250690 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-250881 util-scheduler-8620 DEBUG Running task: 4538 / 0x6146380
Jul 07 21:03:07-251091 util-scheduler-8620 DEBUG Adding task: 4540 / 0x6146380
Jul 07 21:03:07-251313 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:07-251516 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:07-251724 util-scheduler-8620 DEBUG Adding task: 4541 / 0x46620a0
Jul 07 21:03:07-251998 util-scheduler-8620 DEBUG Checking readiness of task: 4541 / 0x46620a0
Jul 07 21:03:07-252193 util-scheduler-8620 DEBUG Checking readiness of task: 4536 / 0x46620a0
Jul 07 21:03:07-252384 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-252573 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-252779 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-252989 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-253208 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-253401 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-253592 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-253783 util-scheduler-8620 DEBUG Running task: 4541 / 0x46620a0
Jul 07 21:03:07-253986 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:07-254165 util-8620 DEBUG process_notify is running
Jul 07 21:03:07-254338 util-8620 DEBUG client_notify is running
Jul 07 21:03:07-254517 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:07-254712 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:07-254904 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:07-255176 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:07-255428 util-scheduler-8620 DEBUG Checking readiness of task: 4536 / 0x46620a0
Jul 07 21:03:07-255622 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-255813 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-256003 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-256211 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-256401 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-256590 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-256782 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-256973 util-scheduler-8620 DEBUG Running task: 4536 / 0x46620a0
Jul 07 21:03:07-257414 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:07-257646 util-scheduler-8620 DEBUG Adding task: 4542 / 0x4662248
Jul 07 21:03:07-257895 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-258088 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-258297 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-258488 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-258677 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-258867 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-259056 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-259260 util-scheduler-8620 DEBUG Running task: 4542 / 0x4662248
Jul 07 21:03:07-259451 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:07-259648 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:07-259866 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:07-260065 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:07-260264 util-scheduler-8620 DEBUG Adding task: 4543 / 0x46620a0
Jul 07 21:03:07-260466 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:07-260673 util-scheduler-8620 DEBUG Adding task: 4544 / 0x46620a0
Jul 07 21:03:07-260913 util-scheduler-8620 DEBUG Checking readiness of task: 4544 / 0x46620a0
Jul 07 21:03:07-261107 util-scheduler-8620 DEBUG Checking readiness of task: 4543 / 0x46620a0
Jul 07 21:03:07-261319 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:07-261529 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:07-261719 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:07-261927 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:07-262118 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:07-262307 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:07-262514 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:07-262705 util-scheduler-8620 DEBUG Running task: 4543 / 0x46620a0
Jul 07 21:03:07-262891 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:07-263066 util-8620 DEBUG process_notify is running
Jul 07 21:03:07-263236 util-8620 DEBUG client_notify is running
Jul 07 21:03:07-263421 util-scheduler-8620 DEBUG Canceling task: 4540 / 0x6146380
Jul 07 21:03:07-263664 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:07-263881 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:07-264113 cadet-p2p-8620 DEBUG Checking 0x61c6a50 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:07-264347 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:07-264543 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:07-264732 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:07-265016 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:07-265230 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:07-265411 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:07-265618 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:07-265807 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:07-265986 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:07-266170 util-scheduler-8620 DEBUG Canceling task: 4537 / 0x6146c10
Jul 07 21:03:07-266381 util-scheduler-8620 DEBUG Adding task: 4545 / 0x6146c10
Jul 07 21:03:07-266624 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:07-266832 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:07-267015 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:07-267215 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:07-267390 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:07-267564 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:07-267778 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:07-267984 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:07-268168 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:07-268346 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:07-268534 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:07-268778 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:11-036540 util-scheduler-8620 DEBUG Checking readiness of task: 4544 / 0x46620a0
Jul 07 21:03:11-036925 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:11-037124 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:11-037356 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:11-037553 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:11-037748 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:11-037944 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:11-038137 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:11-038336 util-scheduler-8620 DEBUG Running task: 4544 / 0x46620a0
Jul 07 21:03:11-038762 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:11-039021 util-scheduler-8620 DEBUG Adding task: 4546 / 0x4662248
Jul 07 21:03:11-039303 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:11-039500 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:11-039728 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:11-039923 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:11-040117 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:11-040309 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:11-040502 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:11-040695 util-scheduler-8620 DEBUG Running task: 4546 / 0x4662248
Jul 07 21:03:11-040888 util-8620 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:03:11-041092 core-api-8620 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:03:11-041346 core-api-8620 DEBUG Received notification about connection from `TZQE'.
Jul 07 21:03:11-041634 cadet-p2p-8620 INFO CONNECTED GN10 <= TZQE
Jul 07 21:03:11-041927 util-8620 DEBUG Scheduling transmission (0x4d5e5d8).
Jul 07 21:03:11-042148 util-scheduler-8620 DEBUG Adding task: 4547 / 0x4d5e5d8
Jul 07 21:03:11-042371 cadet-p2p-8620 DEBUG adding path [2] to peer TZQE
Jul 07 21:03:11-042558 cadet-p2p-8620 DEBUG  final length: 2
Jul 07 21:03:11-042735 cadet-p2p-8620 DEBUG   added last
Jul 07 21:03:11-042929 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:11-043138 util-scheduler-8620 DEBUG Adding task: 4548 / 0x46620a0
Jul 07 21:03:11-043394 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:11-043591 util-scheduler-8620 DEBUG Checking readiness of task: 4547 / 0x4d5e5d8
Jul 07 21:03:11-043788 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:11-043981 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:11-044175 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:11-044367 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:11-044561 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:11-044753 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:11-044945 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:11-045141 util-scheduler-8620 DEBUG Running task: 4547 / 0x4d5e5d8
Jul 07 21:03:11-045586 util-8620 DEBUG transmit_ready running (0x4d5e5d8).
Jul 07 21:03:11-045771 util-8620 DEBUG process_notify is running
Jul 07 21:03:11-045950 util-8620 DEBUG client_notify is running
Jul 07 21:03:11-046181 util-8620 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:03:11-046482 util-8620 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d5e5d8)
Jul 07 21:03:12-249431 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-249814 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-252593 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-252821 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:12-253124 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-253358 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-253552 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-253744 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-253939 util-scheduler-8620 DEBUG Running task: 4539 / 0x52cbfb8
Jul 07 21:03:12-254182 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:12-254442 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:03:12-254652 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:12-254857 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:12-255067 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:12-255305 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:12-255489 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:12-255739 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:12-256036 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:12-256236 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:12-256475 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:12-256686 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:12-257006 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:12-257229 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:12-257459 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:12-257643 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:12-257821 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:12-258031 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:12-258248 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:12-258475 util-scheduler-8620 DEBUG Adding task: 4549 / 0x6146380
Jul 07 21:03:12-258657 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:12-258864 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:12-259042 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:12-259218 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:12-259457 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:12-259654 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:12-259834 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:12-260033 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:12-260283 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:12-260488 util-scheduler-8620 DEBUG Adding task: 4550 / 0x52cbfb8
Jul 07 21:03:12-260764 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-260959 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-261151 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-262027 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:12-262373 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-262713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-263051 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-263391 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-263733 util-scheduler-8620 DEBUG Running task: 4549 / 0x6146380
Jul 07 21:03:12-264094 util-scheduler-8620 DEBUG Adding task: 4551 / 0x6146380
Jul 07 21:03:12-264470 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:12-264822 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:12-265183 util-scheduler-8620 DEBUG Adding task: 4552 / 0x46620a0
Jul 07 21:03:12-265601 util-scheduler-8620 DEBUG Checking readiness of task: 4552 / 0x46620a0
Jul 07 21:03:12-265946 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-266286 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-266628 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-266972 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:12-267274 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-267620 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-267918 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-268206 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-268548 util-scheduler-8620 DEBUG Running task: 4552 / 0x46620a0
Jul 07 21:03:12-268883 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:12-269233 util-8620 DEBUG process_notify is running
Jul 07 21:03:12-269573 util-8620 DEBUG client_notify is running
Jul 07 21:03:12-269903 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:12-270250 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:12-270549 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:12-271072 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:12-369618 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-369867 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-370062 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-370255 util-scheduler-8620 DEBUG Checking readiness of task: 4167 / 0x4663d68
Jul 07 21:03:12-370448 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-370639 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-370829 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-371018 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-371210 util-scheduler-8620 DEBUG Running task: 4167 / 0x4663d68
Jul 07 21:03:12-371624 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663d68)!
Jul 07 21:03:12-371878 util-scheduler-8620 DEBUG Adding task: 4553 / 0x4663f10
Jul 07 21:03:12-372138 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-372332 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-372524 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-372713 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-372905 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-373094 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-373304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-373495 util-scheduler-8620 DEBUG Running task: 4553 / 0x4663f10
Jul 07 21:03:12-373687 util-8620 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:03:12-373883 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:12-374094 util-scheduler-8620 DEBUG Adding task: 4554 / 0x4663d68
Jul 07 21:03:12-374282 transport-api-8620 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:03:12-374504 transport-api-8620 DEBUG Receiving `SET_QUOTA' message for `TZQE' with quota 10356
Jul 07 21:03:12-374698 util-bandwidth-8620 DEBUG Tracker 0x4d73060 bandwidth changed to 10356 Bps
Jul 07 21:03:12-374967 util-bandwidth-8620 DEBUG Tracker 0x4d73060 updated, have 9216 Bps, last update was 13 m ago
Jul 07 21:03:12-375188 util-scheduler-8620 DEBUG Adding task: 4555 / 0x4d73060
Jul 07 21:03:12-375425 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:12-375619 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-375810 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-375999 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-376190 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-376380 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-376570 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-376759 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-376948 util-scheduler-8620 DEBUG Running task: 4555 / 0x4d73060
Jul 07 21:03:12-671936 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:12-672236 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-672436 util-scheduler-8620 DEBUG Checking readiness of task: 4505 / 0x465ee60
Jul 07 21:03:12-672668 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-672867 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-673058 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-673287 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-673480 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-673674 util-scheduler-8620 DEBUG Running task: 4505 / 0x465ee60
Jul 07 21:03:12-674090 util-8620 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 21:03:12-674338 util-scheduler-8620 DEBUG Adding task: 4556 / 0x465f008
Jul 07 21:03:12-674608 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:12-674802 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-674993 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-675183 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-675374 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-675563 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-675755 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-675945 util-scheduler-8620 DEBUG Running task: 4556 / 0x465f008
Jul 07 21:03:12-676137 util-8620 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 21:03:12-676371 nse-api-8620 DEBUG Received information about peer `YXNW' from peerinfo database
Jul 07 21:03:12-676559 cadet-hll-8620 DEBUG  hello with id 0xbed57888 and msg (nil)
Jul 07 21:03:12-676769 util-scheduler-8620 DEBUG Adding task: 4557 / 0x465f008
Jul 07 21:03:12-677004 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:12-677220 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:12-677413 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:12-677603 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:12-677793 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:12-677982 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:12-678172 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:12-678363 util-scheduler-8620 DEBUG Running task: 4557 / 0x465f008
Jul 07 21:03:12-678552 util-8620 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:03:12-678767 nse-api-8620 DEBUG Received information about peer `YXNW' from peerinfo database
Jul 07 21:03:12-679038 cadet-hll-8620 DEBUG  hello for YXNW (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:03:12-679299 cadet-p2p-8620 DEBUG set hello for YXNW
Jul 07 21:03:12-679476 cadet-p2p-8620 DEBUG  new (40 bytes)
Jul 07 21:03:12-679663 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:12-679870 util-scheduler-8620 DEBUG Adding task: 4558 / 0x465ee60
Jul 07 21:03:14-994700 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:14-995086 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:14-995284 util-scheduler-8620 DEBUG Checking readiness of task: 4548 / 0x46620a0
Jul 07 21:03:14-995480 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:14-995675 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:14-995896 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:14-996091 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:14-996290 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:14-996486 util-scheduler-8620 DEBUG Running task: 4548 / 0x46620a0
Jul 07 21:03:14-996904 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:14-997185 util-scheduler-8620 DEBUG Adding task: 4559 / 0x4662248
Jul 07 21:03:14-997499 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:14-997694 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:14-997887 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:14-998077 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:14-998268 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:14-998457 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:14-998649 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:14-998838 util-scheduler-8620 DEBUG Running task: 4559 / 0x4662248
Jul 07 21:03:14-999029 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:14-999228 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:14-999459 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:14-999668 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:14-999875 util-scheduler-8620 DEBUG Adding task: 4560 / 0x46620a0
Jul 07 21:03:15-000061 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:15-000271 util-scheduler-8620 DEBUG Adding task: 4561 / 0x46620a0
Jul 07 21:03:15-000517 util-scheduler-8620 DEBUG Checking readiness of task: 4561 / 0x46620a0
Jul 07 21:03:15-000713 util-scheduler-8620 DEBUG Checking readiness of task: 4560 / 0x46620a0
Jul 07 21:03:15-000906 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:15-001099 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:15-001314 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:15-001507 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:15-001699 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:15-001889 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:15-002081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:15-002275 util-scheduler-8620 DEBUG Running task: 4560 / 0x46620a0
Jul 07 21:03:15-002461 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:15-002643 util-8620 DEBUG process_notify is running
Jul 07 21:03:15-002817 util-8620 DEBUG client_notify is running
Jul 07 21:03:15-003008 util-scheduler-8620 DEBUG Canceling task: 4551 / 0x6146380
Jul 07 21:03:15-003234 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:15-003470 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:15-003711 cadet-p2p-8620 DEBUG Checking 0x61ca258 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:15-003947 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:15-004128 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:15-004320 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:15-004606 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:15-004803 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:15-004985 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:15-005174 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:15-005385 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:15-005566 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:15-005754 util-scheduler-8620 DEBUG Canceling task: 4545 / 0x6146c10
Jul 07 21:03:15-005968 util-scheduler-8620 DEBUG Adding task: 4562 / 0x6146c10
Jul 07 21:03:15-006220 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:15-006393 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:15-006576 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:15-006780 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:15-006974 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:15-007152 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:15-007353 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:15-007560 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:15-007745 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:15-007926 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:15-008120 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:15-008370 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:17-262893 util-scheduler-8620 DEBUG Checking readiness of task: 4561 / 0x46620a0
Jul 07 21:03:17-263257 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-266229 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-266441 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-266638 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-266835 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-267026 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-267217 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-267410 util-scheduler-8620 DEBUG Running task: 4550 / 0x52cbfb8
Jul 07 21:03:17-267647 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:17-268191 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:03:17-268407 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:17-268610 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:17-268814 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:17-269049 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:17-269256 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:17-269478 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:17-269771 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:17-269968 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:17-270206 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:17-270415 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:17-270732 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:17-270933 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:17-271158 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:17-271344 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:17-271521 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:17-271727 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:17-271946 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:17-272171 util-scheduler-8620 DEBUG Adding task: 4563 / 0x6146380
Jul 07 21:03:17-272350 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:17-272555 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:17-272732 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:17-272908 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:17-273145 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:17-273364 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:17-273542 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:17-273741 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:17-273985 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:17-274182 util-scheduler-8620 DEBUG Adding task: 4564 / 0x52cbfb8
Jul 07 21:03:17-274441 util-scheduler-8620 DEBUG Checking readiness of task: 4561 / 0x46620a0
Jul 07 21:03:17-274634 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-274850 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-275041 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-275231 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-275422 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-275610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-275798 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-275987 util-scheduler-8620 DEBUG Running task: 4563 / 0x6146380
Jul 07 21:03:17-276196 util-scheduler-8620 DEBUG Adding task: 4565 / 0x6146380
Jul 07 21:03:17-276418 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:17-276623 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:17-276835 util-scheduler-8620 DEBUG Adding task: 4566 / 0x46620a0
Jul 07 21:03:17-277079 util-scheduler-8620 DEBUG Checking readiness of task: 4566 / 0x46620a0
Jul 07 21:03:17-277296 util-scheduler-8620 DEBUG Checking readiness of task: 4561 / 0x46620a0
Jul 07 21:03:17-277487 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-277677 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-277867 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-278056 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-278245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-278433 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-278623 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-278813 util-scheduler-8620 DEBUG Running task: 4566 / 0x46620a0
Jul 07 21:03:17-278998 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:17-279176 util-8620 DEBUG process_notify is running
Jul 07 21:03:17-279349 util-8620 DEBUG client_notify is running
Jul 07 21:03:17-279528 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:17-279724 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:17-279914 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:17-280168 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:17-484960 util-scheduler-8620 DEBUG Checking readiness of task: 4561 / 0x46620a0
Jul 07 21:03:17-485184 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-485399 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-485592 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-485784 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-485975 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-486168 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-486368 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-486575 util-scheduler-8620 DEBUG Running task: 4561 / 0x46620a0
Jul 07 21:03:17-486982 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:17-487219 util-scheduler-8620 DEBUG Adding task: 4567 / 0x4662248
Jul 07 21:03:17-487472 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-487666 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-487857 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-488047 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-488238 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-488447 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-488637 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-488826 util-scheduler-8620 DEBUG Running task: 4567 / 0x4662248
Jul 07 21:03:17-489017 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:17-489214 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:17-489463 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:17-489665 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:17-489865 util-scheduler-8620 DEBUG Adding task: 4568 / 0x46620a0
Jul 07 21:03:17-490052 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:17-490257 util-scheduler-8620 DEBUG Adding task: 4569 / 0x46620a0
Jul 07 21:03:17-490500 util-scheduler-8620 DEBUG Checking readiness of task: 4569 / 0x46620a0
Jul 07 21:03:17-490694 util-scheduler-8620 DEBUG Checking readiness of task: 4568 / 0x46620a0
Jul 07 21:03:17-490886 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:17-491076 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:17-491268 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:17-491457 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:17-491647 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:17-491836 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:17-492026 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:17-492216 util-scheduler-8620 DEBUG Running task: 4568 / 0x46620a0
Jul 07 21:03:17-492400 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:17-492575 util-8620 DEBUG process_notify is running
Jul 07 21:03:17-492745 util-8620 DEBUG client_notify is running
Jul 07 21:03:17-492929 util-scheduler-8620 DEBUG Canceling task: 4565 / 0x6146380
Jul 07 21:03:17-493153 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:17-493392 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:17-493625 cadet-p2p-8620 DEBUG Checking 0x61ce0b8 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:17-493858 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:17-494036 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:17-494224 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:17-494507 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:17-494702 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:17-494882 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:17-495071 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:17-495260 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:17-495439 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:17-495623 util-scheduler-8620 DEBUG Canceling task: 4562 / 0x6146c10
Jul 07 21:03:17-495835 util-scheduler-8620 DEBUG Adding task: 4570 / 0x6146c10
Jul 07 21:03:17-496101 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:17-496272 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:17-496454 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:17-496654 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:17-496830 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:17-497004 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:17-497222 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:17-497430 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:17-497613 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:17-497793 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:17-497982 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:17-498227 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:22-279137 util-scheduler-8620 DEBUG Checking readiness of task: 4569 / 0x46620a0
Jul 07 21:03:22-279518 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:22-280030 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:22-280248 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:22-280497 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:22-280708 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:22-280900 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:22-281102 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:22-281337 util-scheduler-8620 DEBUG Running task: 4564 / 0x52cbfb8
Jul 07 21:03:22-281577 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:22-281835 cadet-tun-8620 DEBUG  kx started 15 m ago
Jul 07 21:03:22-282043 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:22-282263 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:22-282467 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:22-282703 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:22-282884 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:22-283105 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:22-283416 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:22-283615 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:22-283854 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:22-284062 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:22-284398 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:22-284601 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:22-284825 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:22-285026 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:22-285227 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:22-285455 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:22-285676 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:22-285902 util-scheduler-8620 DEBUG Adding task: 4571 / 0x6146380
Jul 07 21:03:22-286082 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:22-286286 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:22-286537 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:22-286716 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:22-286960 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:22-287157 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:22-287337 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:22-287538 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:22-288448 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:22-288671 util-scheduler-8620 DEBUG Adding task: 4572 / 0x52cbfb8
Jul 07 21:03:22-288936 util-scheduler-8620 DEBUG Checking readiness of task: 4569 / 0x46620a0
Jul 07 21:03:22-289132 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:22-289348 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:22-289540 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:22-289751 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:22-289944 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:22-290148 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:22-290338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:22-290533 util-scheduler-8620 DEBUG Running task: 4571 / 0x6146380
Jul 07 21:03:22-290789 util-scheduler-8620 DEBUG Adding task: 4573 / 0x6146380
Jul 07 21:03:22-291018 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:22-291222 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:22-291431 util-scheduler-8620 DEBUG Adding task: 4574 / 0x46620a0
Jul 07 21:03:22-291676 util-scheduler-8620 DEBUG Checking readiness of task: 4574 / 0x46620a0
Jul 07 21:03:22-291887 util-scheduler-8620 DEBUG Checking readiness of task: 4569 / 0x46620a0
Jul 07 21:03:22-292079 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:22-292269 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:22-292458 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:22-292649 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:22-292839 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:22-293044 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:22-293254 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:22-293448 util-scheduler-8620 DEBUG Running task: 4574 / 0x46620a0
Jul 07 21:03:22-293633 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:22-293811 util-8620 DEBUG process_notify is running
Jul 07 21:03:22-294000 util-8620 DEBUG client_notify is running
Jul 07 21:03:22-294179 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:22-294376 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:22-294567 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:22-294820 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:23-869975 util-scheduler-8620 DEBUG Checking readiness of task: 4569 / 0x46620a0
Jul 07 21:03:23-870326 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:23-870523 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:23-870716 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:23-870910 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:23-871103 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:23-871294 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:23-871484 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:23-871680 util-scheduler-8620 DEBUG Running task: 4569 / 0x46620a0
Jul 07 21:03:23-872103 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:23-872356 util-scheduler-8620 DEBUG Adding task: 4575 / 0x4662248
Jul 07 21:03:23-872631 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:23-872824 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:23-873014 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:23-873227 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:23-873418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:23-873608 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:23-873797 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:23-873989 util-scheduler-8620 DEBUG Running task: 4575 / 0x4662248
Jul 07 21:03:23-874181 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:23-874380 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:23-874610 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:23-874815 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:23-875047 util-scheduler-8620 DEBUG Adding task: 4576 / 0x46620a0
Jul 07 21:03:23-875235 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:23-875441 util-scheduler-8620 DEBUG Adding task: 4577 / 0x46620a0
Jul 07 21:03:23-875685 util-scheduler-8620 DEBUG Checking readiness of task: 4577 / 0x46620a0
Jul 07 21:03:23-875877 util-scheduler-8620 DEBUG Checking readiness of task: 4576 / 0x46620a0
Jul 07 21:03:23-876069 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:23-876259 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:23-876449 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:23-876641 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:23-876831 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:23-877022 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:23-877230 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:23-877425 util-scheduler-8620 DEBUG Running task: 4576 / 0x46620a0
Jul 07 21:03:23-877611 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:23-877788 util-8620 DEBUG process_notify is running
Jul 07 21:03:23-877961 util-8620 DEBUG client_notify is running
Jul 07 21:03:23-878149 util-scheduler-8620 DEBUG Canceling task: 4573 / 0x6146380
Jul 07 21:03:23-878374 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:23-878594 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:23-878833 cadet-p2p-8620 DEBUG Checking 0x61d0d30 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:23-879067 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:23-879245 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:23-879434 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:23-879719 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:23-879914 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:23-880094 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:23-880281 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:23-880470 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:23-880648 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:23-880835 util-scheduler-8620 DEBUG Canceling task: 4570 / 0x6146c10
Jul 07 21:03:23-881046 util-scheduler-8620 DEBUG Adding task: 4578 / 0x6146c10
Jul 07 21:03:23-881315 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:23-881488 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:23-881669 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:23-881870 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:23-882045 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:23-882219 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:23-882418 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:23-882622 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:23-882805 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:23-882984 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:23-883174 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:23-883422 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:27-289380 util-scheduler-8620 DEBUG Checking readiness of task: 4577 / 0x46620a0
Jul 07 21:03:27-289750 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-293134 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-293408 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-293606 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-293801 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-294017 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-294210 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-294404 util-scheduler-8620 DEBUG Running task: 4572 / 0x52cbfb8
Jul 07 21:03:27-294641 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:27-294900 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:27-295106 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:27-295307 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:27-295510 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:27-295745 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:27-295940 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:27-296160 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:27-296451 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:27-296651 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:27-296888 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:27-297097 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:27-297440 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:27-297641 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:27-297866 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:27-298049 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:27-298225 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:27-298431 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:27-298644 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:27-298871 util-scheduler-8620 DEBUG Adding task: 4579 / 0x6146380
Jul 07 21:03:27-299052 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:27-299255 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:27-299435 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:27-299610 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:27-299848 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:27-300044 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:27-300221 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:27-300420 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:27-300664 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:27-300861 util-scheduler-8620 DEBUG Adding task: 4580 / 0x52cbfb8
Jul 07 21:03:27-301121 util-scheduler-8620 DEBUG Checking readiness of task: 4577 / 0x46620a0
Jul 07 21:03:27-301339 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-301530 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-301719 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-301909 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-302099 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-302288 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-302477 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-302667 util-scheduler-8620 DEBUG Running task: 4579 / 0x6146380
Jul 07 21:03:27-302875 util-scheduler-8620 DEBUG Adding task: 4581 / 0x6146380
Jul 07 21:03:27-303098 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:27-303301 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:27-303510 util-scheduler-8620 DEBUG Adding task: 4582 / 0x46620a0
Jul 07 21:03:27-303754 util-scheduler-8620 DEBUG Checking readiness of task: 4582 / 0x46620a0
Jul 07 21:03:27-303949 util-scheduler-8620 DEBUG Checking readiness of task: 4577 / 0x46620a0
Jul 07 21:03:27-304140 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-304346 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-304536 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-304727 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-304916 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-305104 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-305315 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-305508 util-scheduler-8620 DEBUG Running task: 4582 / 0x46620a0
Jul 07 21:03:27-305693 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:27-305872 util-8620 DEBUG process_notify is running
Jul 07 21:03:27-306045 util-8620 DEBUG client_notify is running
Jul 07 21:03:27-306224 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:27-306420 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:27-306610 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:27-306864 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:27-421185 util-scheduler-8620 DEBUG Checking readiness of task: 4577 / 0x46620a0
Jul 07 21:03:27-421491 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-421687 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-421879 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-422070 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-422261 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-422451 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-422640 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-422832 util-scheduler-8620 DEBUG Running task: 4577 / 0x46620a0
Jul 07 21:03:27-423239 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:27-423476 util-scheduler-8620 DEBUG Adding task: 4583 / 0x4662248
Jul 07 21:03:27-423729 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-423923 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-424114 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-424304 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-424494 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-424683 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-424872 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-425061 util-scheduler-8620 DEBUG Running task: 4583 / 0x4662248
Jul 07 21:03:27-425275 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:27-425473 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:27-425695 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:27-425895 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:27-426094 util-scheduler-8620 DEBUG Adding task: 4584 / 0x46620a0
Jul 07 21:03:27-426282 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:27-426486 util-scheduler-8620 DEBUG Adding task: 4585 / 0x46620a0
Jul 07 21:03:27-426729 util-scheduler-8620 DEBUG Checking readiness of task: 4585 / 0x46620a0
Jul 07 21:03:27-426920 util-scheduler-8620 DEBUG Checking readiness of task: 4584 / 0x46620a0
Jul 07 21:03:27-427112 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:27-427301 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:27-427492 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:27-427704 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:27-427896 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:27-428086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:27-428275 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:27-428465 util-scheduler-8620 DEBUG Running task: 4584 / 0x46620a0
Jul 07 21:03:27-428650 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:27-428825 util-8620 DEBUG process_notify is running
Jul 07 21:03:27-428995 util-8620 DEBUG client_notify is running
Jul 07 21:03:27-429181 util-scheduler-8620 DEBUG Canceling task: 4581 / 0x6146380
Jul 07 21:03:27-429432 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:27-429650 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:27-429885 cadet-p2p-8620 DEBUG Checking 0x61d3760 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:27-430118 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:27-430296 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:27-430483 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:27-430766 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:27-430961 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:27-431363 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:27-431554 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:27-431743 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:27-431922 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:27-432105 util-scheduler-8620 DEBUG Canceling task: 4578 / 0x6146c10
Jul 07 21:03:27-432319 util-scheduler-8620 DEBUG Adding task: 4586 / 0x6146c10
Jul 07 21:03:27-432565 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:27-432736 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:27-432917 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:27-433118 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:27-433318 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:27-433493 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:27-433691 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:27-433896 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:27-434080 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:27-434258 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:27-434448 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:27-434697 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:32-305891 util-scheduler-8620 DEBUG Checking readiness of task: 4585 / 0x46620a0
Jul 07 21:03:32-306277 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:32-308847 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:32-309265 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:32-309463 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:32-309658 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:32-309848 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:32-310039 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:32-310232 util-scheduler-8620 DEBUG Running task: 4580 / 0x52cbfb8
Jul 07 21:03:32-310473 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:32-310732 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:32-310940 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:32-311141 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:32-311344 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:32-311582 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:32-311801 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:32-312025 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:32-312317 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:32-312515 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:32-312754 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:32-312964 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:32-313306 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:32-313510 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:32-313735 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:32-313919 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:32-314095 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:32-314302 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:32-314516 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:32-314741 util-scheduler-8620 DEBUG Adding task: 4587 / 0x6146380
Jul 07 21:03:32-314921 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:32-315126 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:32-315304 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:32-315479 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:32-315718 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:32-315913 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:32-316092 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:32-316291 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:32-316536 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:32-316735 util-scheduler-8620 DEBUG Adding task: 4588 / 0x52cbfb8
Jul 07 21:03:32-317001 util-scheduler-8620 DEBUG Checking readiness of task: 4585 / 0x46620a0
Jul 07 21:03:32-317215 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:32-317407 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:32-317598 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:32-317789 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:32-317978 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:32-318167 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:32-318356 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:32-318546 util-scheduler-8620 DEBUG Running task: 4587 / 0x6146380
Jul 07 21:03:32-318755 util-scheduler-8620 DEBUG Adding task: 4589 / 0x6146380
Jul 07 21:03:32-318983 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:32-319188 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:32-319396 util-scheduler-8620 DEBUG Adding task: 4590 / 0x46620a0
Jul 07 21:03:32-319642 util-scheduler-8620 DEBUG Checking readiness of task: 4590 / 0x46620a0
Jul 07 21:03:32-319836 util-scheduler-8620 DEBUG Checking readiness of task: 4585 / 0x46620a0
Jul 07 21:03:32-320027 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:32-320217 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:32-320407 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:32-320597 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:32-320787 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:32-320975 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:32-321164 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:32-321378 util-scheduler-8620 DEBUG Running task: 4590 / 0x46620a0
Jul 07 21:03:32-321564 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:32-321760 util-8620 DEBUG process_notify is running
Jul 07 21:03:32-321935 util-8620 DEBUG client_notify is running
Jul 07 21:03:32-322115 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:32-322311 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:32-322503 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:32-322762 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:33-646051 util-scheduler-8620 DEBUG Checking readiness of task: 4585 / 0x46620a0
Jul 07 21:03:33-646402 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:33-646599 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:33-646791 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:33-646983 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:33-647175 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:33-647366 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:33-647572 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:33-647767 util-scheduler-8620 DEBUG Running task: 4585 / 0x46620a0
Jul 07 21:03:33-648185 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:33-648435 util-scheduler-8620 DEBUG Adding task: 4591 / 0x4662248
Jul 07 21:03:33-648709 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:33-648903 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:33-649095 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:33-649319 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:33-649511 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:33-649718 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:33-649937 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:33-650130 util-scheduler-8620 DEBUG Running task: 4591 / 0x4662248
Jul 07 21:03:33-650322 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:33-650522 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:33-650752 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:33-650959 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:33-651166 util-scheduler-8620 DEBUG Adding task: 4592 / 0x46620a0
Jul 07 21:03:33-651353 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:33-651561 util-scheduler-8620 DEBUG Adding task: 4593 / 0x46620a0
Jul 07 21:03:33-651807 util-scheduler-8620 DEBUG Checking readiness of task: 4593 / 0x46620a0
Jul 07 21:03:33-652002 util-scheduler-8620 DEBUG Checking readiness of task: 4592 / 0x46620a0
Jul 07 21:03:33-652195 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:33-652387 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:33-652578 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:33-652769 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:33-652960 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:33-653149 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:33-653365 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:33-653558 util-scheduler-8620 DEBUG Running task: 4592 / 0x46620a0
Jul 07 21:03:33-653745 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:33-653923 util-8620 DEBUG process_notify is running
Jul 07 21:03:33-654096 util-8620 DEBUG client_notify is running
Jul 07 21:03:33-654311 util-scheduler-8620 DEBUG Canceling task: 4589 / 0x6146380
Jul 07 21:03:33-654541 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:33-654762 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:33-655001 cadet-p2p-8620 DEBUG Checking 0x61d64e8 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:33-655237 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:33-655415 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:33-655606 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:33-655892 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:33-656088 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:33-656269 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:33-656459 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:33-656648 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:33-656829 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:33-657013 util-scheduler-8620 DEBUG Canceling task: 4586 / 0x6146c10
Jul 07 21:03:33-657250 util-scheduler-8620 DEBUG Adding task: 4594 / 0x6146c10
Jul 07 21:03:33-657503 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:33-657675 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:33-657857 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:33-658059 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:33-658236 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:33-658411 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:33-658609 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:33-658816 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:33-659000 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:33-659179 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:33-659374 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:33-660225 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:37-317373 util-scheduler-8620 DEBUG Checking readiness of task: 4593 / 0x46620a0
Jul 07 21:03:37-317750 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-317950 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-318144 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-318337 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-318530 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-318721 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-318912 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-319106 util-scheduler-8620 DEBUG Running task: 4588 / 0x52cbfb8
Jul 07 21:03:37-319347 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:37-319610 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:37-319820 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:37-320022 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:37-320226 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:37-320465 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:37-320647 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:37-320869 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:37-321163 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:37-321387 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:37-321627 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:37-321838 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:37-322158 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:37-322391 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:37-322620 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:37-322805 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:37-322983 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:37-323190 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:37-323408 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:37-323636 util-scheduler-8620 DEBUG Adding task: 4595 / 0x6146380
Jul 07 21:03:37-323819 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:37-324024 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:37-324205 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:37-324382 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:37-324621 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:37-324820 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:37-324999 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:37-325726 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:37-326084 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:37-326413 util-scheduler-8620 DEBUG Adding task: 4596 / 0x52cbfb8
Jul 07 21:03:37-326747 util-scheduler-8620 DEBUG Checking readiness of task: 4593 / 0x46620a0
Jul 07 21:03:37-326942 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-327134 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-327324 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-327514 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-327706 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-327895 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-328084 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-328274 util-scheduler-8620 DEBUG Running task: 4595 / 0x6146380
Jul 07 21:03:37-328484 util-scheduler-8620 DEBUG Adding task: 4597 / 0x6146380
Jul 07 21:03:37-328707 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:37-328911 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:37-329120 util-scheduler-8620 DEBUG Adding task: 4598 / 0x46620a0
Jul 07 21:03:37-329394 util-scheduler-8620 DEBUG Checking readiness of task: 4598 / 0x46620a0
Jul 07 21:03:37-329603 util-scheduler-8620 DEBUG Checking readiness of task: 4593 / 0x46620a0
Jul 07 21:03:37-329794 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-329983 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-330173 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-330363 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-330552 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-330742 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-330931 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-331122 util-scheduler-8620 DEBUG Running task: 4598 / 0x46620a0
Jul 07 21:03:37-331308 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:37-331488 util-8620 DEBUG process_notify is running
Jul 07 21:03:37-331662 util-8620 DEBUG client_notify is running
Jul 07 21:03:37-331843 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:37-332041 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:37-332232 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:37-332485 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:37-332734 util-scheduler-8620 DEBUG Checking readiness of task: 4593 / 0x46620a0
Jul 07 21:03:37-332954 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-333145 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-333359 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-333550 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-333741 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-333930 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-334122 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-334313 util-scheduler-8620 DEBUG Running task: 4593 / 0x46620a0
Jul 07 21:03:37-334718 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:37-334949 util-scheduler-8620 DEBUG Adding task: 4599 / 0x4662248
Jul 07 21:03:37-335196 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-335390 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-335581 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-335771 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-335961 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-336151 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-336340 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-336528 util-scheduler-8620 DEBUG Running task: 4599 / 0x4662248
Jul 07 21:03:37-336718 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:37-336915 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:37-337131 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:37-337355 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:37-337554 util-scheduler-8620 DEBUG Adding task: 4600 / 0x46620a0
Jul 07 21:03:37-337740 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:37-337945 util-scheduler-8620 DEBUG Adding task: 4601 / 0x46620a0
Jul 07 21:03:37-338186 util-scheduler-8620 DEBUG Checking readiness of task: 4601 / 0x46620a0
Jul 07 21:03:37-338379 util-scheduler-8620 DEBUG Checking readiness of task: 4600 / 0x46620a0
Jul 07 21:03:37-338570 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:37-338759 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:37-338947 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:37-339138 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:37-339328 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:37-339517 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:37-339706 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:37-339896 util-scheduler-8620 DEBUG Running task: 4600 / 0x46620a0
Jul 07 21:03:37-340080 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:37-340255 util-8620 DEBUG process_notify is running
Jul 07 21:03:37-340424 util-8620 DEBUG client_notify is running
Jul 07 21:03:37-340609 util-scheduler-8620 DEBUG Canceling task: 4597 / 0x6146380
Jul 07 21:03:37-340833 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:37-341049 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:37-341304 cadet-p2p-8620 DEBUG Checking 0x61d9258 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:37-341538 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:37-341717 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:37-341903 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:37-342186 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:37-342396 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:37-342576 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:37-342762 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:37-342951 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:37-343129 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:37-343312 util-scheduler-8620 DEBUG Canceling task: 4594 / 0x6146c10
Jul 07 21:03:37-343522 util-scheduler-8620 DEBUG Adding task: 4602 / 0x6146c10
Jul 07 21:03:37-343765 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:37-343935 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:37-344120 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:37-344319 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:37-344494 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:37-344668 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:37-344865 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:37-345071 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:37-345277 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:37-345457 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:37-345645 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:37-345891 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:42-329381 util-scheduler-8620 DEBUG Checking readiness of task: 4601 / 0x46620a0
Jul 07 21:03:42-329756 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-330333 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-330569 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-330807 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-331001 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-331192 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-331382 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-331577 util-scheduler-8620 DEBUG Running task: 4596 / 0x52cbfb8
Jul 07 21:03:42-331815 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:42-332072 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:42-332279 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:42-332479 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:42-332682 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:42-332918 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:42-333102 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:42-333347 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:42-333640 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:42-333838 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:42-334076 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:42-334284 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:42-334615 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:42-334816 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:42-335040 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:42-335225 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:42-335400 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:42-335606 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:42-335821 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:42-336045 util-scheduler-8620 DEBUG Adding task: 4603 / 0x6146380
Jul 07 21:03:42-336226 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:42-336454 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:42-336632 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:42-336808 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:42-337046 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:42-337264 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:42-337443 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:42-337642 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:42-337888 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:42-338085 util-scheduler-8620 DEBUG Adding task: 4604 / 0x52cbfb8
Jul 07 21:03:42-338342 util-scheduler-8620 DEBUG Checking readiness of task: 4601 / 0x46620a0
Jul 07 21:03:42-338536 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-338726 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-338917 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-339106 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-339297 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-339504 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-339694 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-339901 util-scheduler-8620 DEBUG Running task: 4603 / 0x6146380
Jul 07 21:03:42-340112 util-scheduler-8620 DEBUG Adding task: 4605 / 0x6146380
Jul 07 21:03:42-340335 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:42-340539 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:42-340746 util-scheduler-8620 DEBUG Adding task: 4606 / 0x46620a0
Jul 07 21:03:42-340992 util-scheduler-8620 DEBUG Checking readiness of task: 4606 / 0x46620a0
Jul 07 21:03:42-341206 util-scheduler-8620 DEBUG Checking readiness of task: 4601 / 0x46620a0
Jul 07 21:03:42-341400 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-341590 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-341780 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-341970 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-342159 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-342348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-342536 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-342728 util-scheduler-8620 DEBUG Running task: 4606 / 0x46620a0
Jul 07 21:03:42-342912 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:42-343094 util-8620 DEBUG process_notify is running
Jul 07 21:03:42-343268 util-8620 DEBUG client_notify is running
Jul 07 21:03:42-343446 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:42-343643 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:42-343833 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:42-344087 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:42-344335 util-scheduler-8620 DEBUG Checking readiness of task: 4601 / 0x46620a0
Jul 07 21:03:42-344528 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-344718 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-344909 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-345099 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-345309 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-345498 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-345688 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-345895 util-scheduler-8620 DEBUG Running task: 4601 / 0x46620a0
Jul 07 21:03:42-346300 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:42-346531 util-scheduler-8620 DEBUG Adding task: 4607 / 0x4662248
Jul 07 21:03:42-346780 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-346972 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-347161 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-347351 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-347540 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-347728 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-347916 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-348106 util-scheduler-8620 DEBUG Running task: 4607 / 0x4662248
Jul 07 21:03:42-348295 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:42-348492 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:42-348709 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:42-348907 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:42-349105 util-scheduler-8620 DEBUG Adding task: 4608 / 0x46620a0
Jul 07 21:03:42-349310 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:42-349515 util-scheduler-8620 DEBUG Adding task: 4609 / 0x46620a0
Jul 07 21:03:42-349770 util-scheduler-8620 DEBUG Checking readiness of task: 4609 / 0x46620a0
Jul 07 21:03:42-349963 util-scheduler-8620 DEBUG Checking readiness of task: 4608 / 0x46620a0
Jul 07 21:03:42-350154 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:42-350343 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:42-350532 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:42-350723 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:42-350913 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:42-351102 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:42-351290 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:42-351481 util-scheduler-8620 DEBUG Running task: 4608 / 0x46620a0
Jul 07 21:03:42-351665 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:42-351840 util-8620 DEBUG process_notify is running
Jul 07 21:03:42-352010 util-8620 DEBUG client_notify is running
Jul 07 21:03:42-352194 util-scheduler-8620 DEBUG Canceling task: 4605 / 0x6146380
Jul 07 21:03:42-352418 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:42-352634 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:42-352865 cadet-p2p-8620 DEBUG Checking 0x61dbec8 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:42-353102 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:42-353301 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:42-353487 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:42-353769 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:42-353964 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:42-354142 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:42-354330 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:42-354517 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:42-354696 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:42-354879 util-scheduler-8620 DEBUG Canceling task: 4602 / 0x6146c10
Jul 07 21:03:42-355089 util-scheduler-8620 DEBUG Adding task: 4610 / 0x6146c10
Jul 07 21:03:42-355331 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:42-355503 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:42-355701 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:42-355912 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:42-356088 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:42-356262 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:42-356460 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:42-356665 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:42-356849 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:42-357026 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:42-357234 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:42-357480 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:47-343229 util-scheduler-8620 DEBUG Checking readiness of task: 4609 / 0x46620a0
Jul 07 21:03:47-343626 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-344579 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-344783 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-345030 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-345257 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-345449 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-345640 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-345834 util-scheduler-8620 DEBUG Running task: 4604 / 0x52cbfb8
Jul 07 21:03:47-346073 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:47-346331 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:47-346539 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:47-346741 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:47-346943 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:47-347180 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:47-347362 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:47-347582 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:47-347873 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:47-348070 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:47-348308 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:47-348515 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:47-348835 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:47-349037 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:47-349281 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:47-349467 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:47-349643 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:47-349849 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:47-350065 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:47-350290 util-scheduler-8620 DEBUG Adding task: 4611 / 0x6146380
Jul 07 21:03:47-350471 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:47-350675 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:47-350852 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:47-351028 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:47-351267 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:47-351463 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:47-351640 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:47-351839 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:47-352084 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:47-352281 util-scheduler-8620 DEBUG Adding task: 4612 / 0x52cbfb8
Jul 07 21:03:47-352568 util-scheduler-8620 DEBUG Checking readiness of task: 4609 / 0x46620a0
Jul 07 21:03:47-352762 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-352952 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-353142 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-353352 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-353544 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-353732 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-353921 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-354110 util-scheduler-8620 DEBUG Running task: 4611 / 0x6146380
Jul 07 21:03:47-354322 util-scheduler-8620 DEBUG Adding task: 4613 / 0x6146380
Jul 07 21:03:47-354544 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:47-354749 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:47-354976 util-scheduler-8620 DEBUG Adding task: 4614 / 0x46620a0
Jul 07 21:03:47-355223 util-scheduler-8620 DEBUG Checking readiness of task: 4614 / 0x46620a0
Jul 07 21:03:47-355419 util-scheduler-8620 DEBUG Checking readiness of task: 4609 / 0x46620a0
Jul 07 21:03:47-355611 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-355800 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-355990 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-356179 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-356369 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-356557 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-356747 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-356938 util-scheduler-8620 DEBUG Running task: 4614 / 0x46620a0
Jul 07 21:03:47-357122 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:47-357320 util-8620 DEBUG process_notify is running
Jul 07 21:03:47-357495 util-8620 DEBUG client_notify is running
Jul 07 21:03:47-357674 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:47-357871 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:47-358062 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:47-358315 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:47-358563 util-scheduler-8620 DEBUG Checking readiness of task: 4609 / 0x46620a0
Jul 07 21:03:47-358756 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-358948 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-359137 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-359328 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-359517 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-359706 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-359894 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-360084 util-scheduler-8620 DEBUG Running task: 4609 / 0x46620a0
Jul 07 21:03:47-360487 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:47-360718 util-scheduler-8620 DEBUG Adding task: 4615 / 0x4662248
Jul 07 21:03:47-360965 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-361158 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-361369 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-361558 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-361763 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-361953 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-362141 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-362331 util-scheduler-8620 DEBUG Running task: 4615 / 0x4662248
Jul 07 21:03:47-362521 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:47-362717 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:47-362934 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:47-363131 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:47-363329 util-scheduler-8620 DEBUG Adding task: 4616 / 0x46620a0
Jul 07 21:03:47-363515 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:47-363732 util-scheduler-8620 DEBUG Adding task: 4617 / 0x46620a0
Jul 07 21:03:47-363974 util-scheduler-8620 DEBUG Checking readiness of task: 4617 / 0x46620a0
Jul 07 21:03:47-364166 util-scheduler-8620 DEBUG Checking readiness of task: 4616 / 0x46620a0
Jul 07 21:03:47-364362 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:47-364552 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:47-364743 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:47-364932 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:47-365122 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:47-365332 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:47-365521 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:47-365713 util-scheduler-8620 DEBUG Running task: 4616 / 0x46620a0
Jul 07 21:03:47-365896 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:47-366072 util-8620 DEBUG process_notify is running
Jul 07 21:03:47-366241 util-8620 DEBUG client_notify is running
Jul 07 21:03:47-366427 util-scheduler-8620 DEBUG Canceling task: 4613 / 0x6146380
Jul 07 21:03:47-366651 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:47-366867 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:47-367099 cadet-p2p-8620 DEBUG Checking 0x61deb28 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:47-367333 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:47-367511 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:47-367698 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:47-367980 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:47-368176 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:47-368354 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:47-368542 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:47-368730 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:47-368909 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:47-369091 util-scheduler-8620 DEBUG Canceling task: 4610 / 0x6146c10
Jul 07 21:03:47-369321 util-scheduler-8620 DEBUG Adding task: 4618 / 0x6146c10
Jul 07 21:03:47-369564 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:47-369735 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:47-369915 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:47-370115 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:47-370291 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:47-370464 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:47-370661 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:47-370866 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:47-371049 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:47-371227 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:47-371432 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:47-371677 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:52-357366 util-scheduler-8620 DEBUG Checking readiness of task: 4617 / 0x46620a0
Jul 07 21:03:52-357752 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-359173 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-359381 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-359577 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-359770 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-359961 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-360151 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-360344 util-scheduler-8620 DEBUG Running task: 4612 / 0x52cbfb8
Jul 07 21:03:52-360583 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:52-360840 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:52-361046 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:52-361270 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:52-361476 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:52-361714 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:52-361896 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:52-362118 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:52-362410 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:52-362610 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:52-362849 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:52-363060 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:52-363381 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:52-363583 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:52-363809 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:52-363993 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:52-364171 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:52-364379 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:52-364595 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:52-364823 util-scheduler-8620 DEBUG Adding task: 4619 / 0x6146380
Jul 07 21:03:52-365005 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:52-365231 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:52-365411 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:52-365587 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:52-365827 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:52-366024 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:52-366202 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:52-366402 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:52-366649 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:52-366849 util-scheduler-8620 DEBUG Adding task: 4620 / 0x52cbfb8
Jul 07 21:03:52-367108 util-scheduler-8620 DEBUG Checking readiness of task: 4617 / 0x46620a0
Jul 07 21:03:52-367303 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-367495 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-367686 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-367880 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-368071 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-368261 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-368480 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-368673 util-scheduler-8620 DEBUG Running task: 4619 / 0x6146380
Jul 07 21:03:52-368883 util-scheduler-8620 DEBUG Adding task: 4621 / 0x6146380
Jul 07 21:03:52-369107 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:52-369333 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:52-369544 util-scheduler-8620 DEBUG Adding task: 4622 / 0x46620a0
Jul 07 21:03:52-369790 util-scheduler-8620 DEBUG Checking readiness of task: 4622 / 0x46620a0
Jul 07 21:03:52-369986 util-scheduler-8620 DEBUG Checking readiness of task: 4617 / 0x46620a0
Jul 07 21:03:52-370177 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-370369 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-370559 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-370749 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-370940 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-371131 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-371320 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-371513 util-scheduler-8620 DEBUG Running task: 4622 / 0x46620a0
Jul 07 21:03:52-371711 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:52-371890 util-8620 DEBUG process_notify is running
Jul 07 21:03:52-372064 util-8620 DEBUG client_notify is running
Jul 07 21:03:52-372243 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:52-372441 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:52-372633 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:52-372951 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:52-373225 util-scheduler-8620 DEBUG Checking readiness of task: 4617 / 0x46620a0
Jul 07 21:03:52-373422 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-373613 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-373805 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-373996 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-374187 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-374376 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-374565 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-374757 util-scheduler-8620 DEBUG Running task: 4617 / 0x46620a0
Jul 07 21:03:52-375166 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:03:52-375398 util-scheduler-8620 DEBUG Adding task: 4623 / 0x4662248
Jul 07 21:03:52-375647 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-375842 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-376033 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-376224 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-376413 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-376604 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-376794 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-376984 util-scheduler-8620 DEBUG Running task: 4623 / 0x4662248
Jul 07 21:03:52-377174 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:03:52-377394 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:03:52-377612 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:03:52-377832 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:52-378034 util-scheduler-8620 DEBUG Adding task: 4624 / 0x46620a0
Jul 07 21:03:52-378221 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:03:52-378426 util-scheduler-8620 DEBUG Adding task: 4625 / 0x46620a0
Jul 07 21:03:52-378672 util-scheduler-8620 DEBUG Checking readiness of task: 4625 / 0x46620a0
Jul 07 21:03:52-378866 util-scheduler-8620 DEBUG Checking readiness of task: 4624 / 0x46620a0
Jul 07 21:03:52-379059 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:52-379249 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:52-379440 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:52-379630 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:52-379820 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:52-380011 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:52-380200 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:52-380393 util-scheduler-8620 DEBUG Running task: 4624 / 0x46620a0
Jul 07 21:03:52-380577 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:52-380753 util-8620 DEBUG process_notify is running
Jul 07 21:03:52-380924 util-8620 DEBUG client_notify is running
Jul 07 21:03:52-381110 util-scheduler-8620 DEBUG Canceling task: 4621 / 0x6146380
Jul 07 21:03:52-381357 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:03:52-381575 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:03:52-381809 cadet-p2p-8620 DEBUG Checking 0x528d838 towards 0V7ADHDH (->V8XX)
Jul 07 21:03:52-382043 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:03:52-382222 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:03:52-382409 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:03:52-382695 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:03:52-382891 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:03:52-383070 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:03:52-383259 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:03:52-383449 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:03:52-383628 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:03:52-383812 util-scheduler-8620 DEBUG Canceling task: 4618 / 0x6146c10
Jul 07 21:03:52-384025 util-scheduler-8620 DEBUG Adding task: 4626 / 0x6146c10
Jul 07 21:03:52-384268 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:03:52-384440 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:03:52-384621 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:03:52-384823 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:52-384999 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:03:52-385173 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:03:52-385394 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:52-385600 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:03:52-385785 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:03:52-385964 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:52-386153 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:03:52-387527 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:03:57-369375 util-scheduler-8620 DEBUG Checking readiness of task: 4625 / 0x46620a0
Jul 07 21:03:57-369763 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:57-370338 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:57-370543 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:57-370741 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:57-370957 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:57-371149 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:57-371339 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:57-371532 util-scheduler-8620 DEBUG Running task: 4620 / 0x52cbfb8
Jul 07 21:03:57-371769 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:03:57-372026 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:03:57-372233 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:03:57-372433 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:03:57-372636 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:03:57-372871 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:03:57-373053 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:03:57-373295 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:03:57-373588 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:03:57-373785 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:03:57-374022 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:03:57-374230 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:03:57-374547 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:03:57-374748 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:03:57-374972 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:03:57-375156 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:03:57-375331 cadet-con-8620 DEBUG  sendable
Jul 07 21:03:57-375539 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:03:57-375775 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:03:57-376003 util-scheduler-8620 DEBUG Adding task: 4627 / 0x6146380
Jul 07 21:03:57-376198 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:03:57-376404 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:03:57-376581 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:03:57-376756 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:03:57-376995 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:03:57-377209 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:03:57-377389 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:03:57-377588 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:03:57-377831 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:03:57-378030 util-scheduler-8620 DEBUG Adding task: 4628 / 0x52cbfb8
Jul 07 21:03:57-378287 util-scheduler-8620 DEBUG Checking readiness of task: 4625 / 0x46620a0
Jul 07 21:03:57-378482 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:57-378672 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:57-378861 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:57-379055 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:57-379245 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:57-379433 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:57-379622 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:57-379812 util-scheduler-8620 DEBUG Running task: 4627 / 0x6146380
Jul 07 21:03:57-380020 util-scheduler-8620 DEBUG Adding task: 4629 / 0x6146380
Jul 07 21:03:57-380243 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:03:57-380447 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:03:57-380655 util-scheduler-8620 DEBUG Adding task: 4630 / 0x46620a0
Jul 07 21:03:57-380899 util-scheduler-8620 DEBUG Checking readiness of task: 4630 / 0x46620a0
Jul 07 21:03:57-381093 util-scheduler-8620 DEBUG Checking readiness of task: 4625 / 0x46620a0
Jul 07 21:03:57-381320 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:03:57-381512 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:03:57-381702 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:03:57-381891 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:03:57-382082 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:03:57-382270 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:03:57-382459 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:03:57-382650 util-scheduler-8620 DEBUG Running task: 4630 / 0x46620a0
Jul 07 21:03:57-382836 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:03:57-383013 util-8620 DEBUG process_notify is running
Jul 07 21:03:57-383187 util-8620 DEBUG client_notify is running
Jul 07 21:03:57-383366 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:03:57-383565 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:03:57-383757 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:03:57-384010 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:01-770426 util-scheduler-8620 DEBUG Checking readiness of task: 4625 / 0x46620a0
Jul 07 21:04:01-770821 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:01-771021 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:01-771216 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:01-771409 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:01-771603 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:01-771794 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:01-771986 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:01-772186 util-scheduler-8620 DEBUG Running task: 4625 / 0x46620a0
Jul 07 21:04:01-772610 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:01-772868 util-scheduler-8620 DEBUG Adding task: 4631 / 0x4662248
Jul 07 21:04:01-773148 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:01-773388 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:01-773580 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:01-773774 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:01-773964 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:01-774157 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:01-774346 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:01-774538 util-scheduler-8620 DEBUG Running task: 4631 / 0x4662248
Jul 07 21:04:01-774730 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:01-774931 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:01-775165 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:01-775374 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:01-775583 util-scheduler-8620 DEBUG Adding task: 4632 / 0x46620a0
Jul 07 21:04:01-775773 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:01-775979 util-scheduler-8620 DEBUG Adding task: 4633 / 0x46620a0
Jul 07 21:04:01-776228 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:01-776422 util-scheduler-8620 DEBUG Checking readiness of task: 4632 / 0x46620a0
Jul 07 21:04:01-776616 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:01-776807 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:01-777027 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:01-777239 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:01-777434 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:01-777624 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:01-777815 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:01-778010 util-scheduler-8620 DEBUG Running task: 4632 / 0x46620a0
Jul 07 21:04:01-778196 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:01-778377 util-8620 DEBUG process_notify is running
Jul 07 21:04:01-778549 util-8620 DEBUG client_notify is running
Jul 07 21:04:01-778739 util-scheduler-8620 DEBUG Canceling task: 4629 / 0x6146380
Jul 07 21:04:01-778969 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:01-779192 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:01-779433 cadet-p2p-8620 DEBUG Checking 0x61e4410 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:01-779668 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:01-779847 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:01-780038 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:01-780327 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:01-780524 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:01-780707 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:01-780896 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:01-781085 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:01-781287 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:01-781471 util-scheduler-8620 DEBUG Canceling task: 4626 / 0x6146c10
Jul 07 21:04:01-781687 util-scheduler-8620 DEBUG Adding task: 4634 / 0x6146c10
Jul 07 21:04:01-781939 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:01-782111 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:01-782292 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:01-782495 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:01-782673 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:01-782849 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:01-783052 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:01-783257 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:01-784269 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:01-784469 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:01-784667 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:01-784920 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:02-378767 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:02-379110 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:02-379691 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:02-379897 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:02-380094 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:02-380306 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:02-380499 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:02-380691 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:02-380887 util-scheduler-8620 DEBUG Running task: 4628 / 0x52cbfb8
Jul 07 21:04:02-381121 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:02-381401 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:04:02-381608 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:02-381808 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:02-382034 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:02-382270 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:02-382451 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:02-382672 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:02-382961 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:02-383161 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:02-383399 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:02-383608 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:02-383925 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:02-384126 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:02-384351 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:02-384535 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:02-384710 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:02-384917 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:02-385132 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:02-385381 util-scheduler-8620 DEBUG Adding task: 4635 / 0x6146380
Jul 07 21:04:02-385563 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:02-385767 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:02-385945 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:02-386120 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:02-386357 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:02-386555 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:02-386732 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:02-386930 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:02-387174 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:02-387371 util-scheduler-8620 DEBUG Adding task: 4636 / 0x52cbfb8
Jul 07 21:04:02-387626 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:02-387820 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:02-388011 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:02-388201 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:02-388390 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:02-388581 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:02-388769 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:02-388958 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:02-389147 util-scheduler-8620 DEBUG Running task: 4635 / 0x6146380
Jul 07 21:04:02-389379 util-scheduler-8620 DEBUG Adding task: 4637 / 0x6146380
Jul 07 21:04:02-389601 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:02-389804 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:02-390012 util-scheduler-8620 DEBUG Adding task: 4638 / 0x46620a0
Jul 07 21:04:02-390259 util-scheduler-8620 DEBUG Checking readiness of task: 4638 / 0x46620a0
Jul 07 21:04:02-390454 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:02-390644 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:02-390834 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:02-391025 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:02-391215 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:02-391404 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:02-391593 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:02-391783 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:02-391990 util-scheduler-8620 DEBUG Running task: 4638 / 0x46620a0
Jul 07 21:04:02-392176 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:02-392355 util-8620 DEBUG process_notify is running
Jul 07 21:04:02-392528 util-8620 DEBUG client_notify is running
Jul 07 21:04:02-392708 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:02-392904 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:02-393094 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:02-393369 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:07-392544 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:07-392938 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:07-393712 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:07-394145 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:07-394349 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:07-394543 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:07-394734 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:07-394944 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:07-395141 util-scheduler-8620 DEBUG Running task: 4636 / 0x52cbfb8
Jul 07 21:04:07-395379 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:07-395640 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:04:07-395848 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:07-396049 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:07-396254 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:07-396490 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:07-396671 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:07-396891 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:07-397184 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:07-397410 cadet-con-8620 DEBUG   C_P+ 0x6146c10 1
Jul 07 21:04:07-397647 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:07-397855 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:07-398172 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:07-398373 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:07-398599 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:07-398782 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:07-398960 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:07-399164 cadet-p2p-8620 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:04:07-399368 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:07-399545 cadet-p2p-8620 DEBUG QQQ  queue length: 2
Jul 07 21:04:07-399719 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:07-399956 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:07-400165 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:07-400343 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:07-400576 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:07-400769 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:07-400944 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:07-401142 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:07-401405 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:07-401610 util-scheduler-8620 DEBUG Adding task: 4639 / 0x52cbfb8
Jul 07 21:04:07-749661 util-scheduler-8620 DEBUG Checking readiness of task: 4633 / 0x46620a0
Jul 07 21:04:07-749954 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:07-750186 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:07-750381 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:07-750573 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:07-750764 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:07-750955 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:07-751144 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:07-751337 util-scheduler-8620 DEBUG Running task: 4633 / 0x46620a0
Jul 07 21:04:07-751753 util-8620 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:07-752002 util-scheduler-8620 DEBUG Adding task: 4640 / 0x4662248
Jul 07 21:04:07-752266 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:07-752460 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:07-752652 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:07-752843 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:07-753034 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:07-753249 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:07-753441 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:07-753632 util-scheduler-8620 DEBUG Running task: 4640 / 0x4662248
Jul 07 21:04:07-753826 util-8620 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:04:07-754026 core-api-8620 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:04:07-754250 core-api-8620 DEBUG Received message of type 258 and size 100 from peer `KNAS'
Jul 07 21:04:07-754887 cadet-con-8620 INFO <-- { CONNECTION_BROKEN} on connection M9KEP6HP from KNAS
Jul 07 21:04:07-756025 cadet-con-8620 DEBUG   regarding STRN
Jul 07 21:04:07-757142 cadet-con-8620 DEBUG   regarding P00P
Jul 07 21:04:07-757917 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 21:04:07-758135 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 21:04:07-759006 cadet-con-8620 DEBUG  get prev hop M9KEP6HP (->P00P) [3/4]
Jul 07 21:04:07-759226 cadet-con-8620 DEBUG   ID: KNAS (2)
Jul 07 21:04:07-760529 util-scheduler-8620 DEBUG Adding task: 4641 / 0x5ad0060
Jul 07 21:04:07-762454 cadet-p2p-8620 DEBUG Link 7-3 broken
Jul 07 21:04:07-764741 cadet-p2p-8620 DEBUG Connection pop on M9KEP6HP (->P00P)
Jul 07 21:04:07-765717 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:07-765940 util-scheduler-8620 DEBUG Adding task: 4642 / 0x46620a0
Jul 07 21:04:08-021699 util-scheduler-8620 DEBUG Checking readiness of task: 4642 / 0x46620a0
Jul 07 21:04:08-022072 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-022277 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-022472 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-022666 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-022861 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-023062 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-023254 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-023452 util-scheduler-8620 DEBUG Running task: 4642 / 0x46620a0
Jul 07 21:04:08-023879 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:08-024140 util-scheduler-8620 DEBUG Adding task: 4643 / 0x4662248
Jul 07 21:04:08-024422 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-024618 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-024811 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-025035 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-025256 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-025453 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-025644 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-025837 util-scheduler-8620 DEBUG Running task: 4643 / 0x4662248
Jul 07 21:04:08-026030 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:08-026233 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:08-026467 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:08-026676 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:08-026886 util-scheduler-8620 DEBUG Adding task: 4644 / 0x46620a0
Jul 07 21:04:08-027077 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:08-027285 util-scheduler-8620 DEBUG Adding task: 4645 / 0x46620a0
Jul 07 21:04:08-027531 util-scheduler-8620 DEBUG Checking readiness of task: 4645 / 0x46620a0
Jul 07 21:04:08-027727 util-scheduler-8620 DEBUG Checking readiness of task: 4644 / 0x46620a0
Jul 07 21:04:08-027922 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-028114 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-028306 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-028499 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-028691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-028882 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-029074 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-029294 util-scheduler-8620 DEBUG Running task: 4644 / 0x46620a0
Jul 07 21:04:08-029487 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:08-029671 util-8620 DEBUG process_notify is running
Jul 07 21:04:08-029847 util-8620 DEBUG client_notify is running
Jul 07 21:04:08-030040 util-scheduler-8620 DEBUG Canceling task: 4637 / 0x6146380
Jul 07 21:04:08-030275 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:08-030500 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:08-030744 cadet-p2p-8620 DEBUG Checking 0x61e7010 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:08-030982 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:08-031162 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:08-031355 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:08-031641 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:08-031839 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:08-032021 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:08-032211 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:08-032402 cadet-con-8620 DEBUG  C_P- 0x6146c10 2
Jul 07 21:04:08-032583 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:08-032769 util-scheduler-8620 DEBUG Canceling task: 4634 / 0x6146c10
Jul 07 21:04:08-032985 util-scheduler-8620 DEBUG Adding task: 4646 / 0x6146c10
Jul 07 21:04:08-033264 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:08-033439 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:08-033664 cadet-p2p-8620 DEBUG Checking 0x61e87b0 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:08-033906 cadet-p2p-8620 DEBUG Checking 0x61e87b0 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:08-034088 cadet-p2p-8620 DEBUG   more data!
Jul 07 21:04:08-034296 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:08-034525 util-scheduler-8620 DEBUG Adding task: 4647 / 0x6146380
Jul 07 21:04:08-034706 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:08-034885 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:08-035112 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:08-035290 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:08-035467 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:08-035707 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:08-035904 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:08-036084 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:08-036285 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:08-036493 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:08-036678 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:08-036881 util-scheduler-8620 DEBUG Adding task: 4648 / 0x6146380
Jul 07 21:04:08-037104 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:08-037328 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:08-037533 util-scheduler-8620 DEBUG Adding task: 4649 / 0x46620a0
Jul 07 21:04:08-037736 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:08-037994 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:08-038194 util-8620 DEBUG Re-scheduling transmit_ready (more to do) (0x46620a0).
Jul 07 21:04:08-038442 util-scheduler-8620 DEBUG Checking readiness of task: 4649 / 0x46620a0
Jul 07 21:04:08-038638 util-scheduler-8620 DEBUG Checking readiness of task: 4645 / 0x46620a0
Jul 07 21:04:08-038831 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-039029 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-039226 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-039419 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-039612 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-039804 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-040000 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-040194 util-scheduler-8620 DEBUG Running task: 4649 / 0x46620a0
Jul 07 21:04:08-040382 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:08-040560 util-8620 DEBUG process_notify is running
Jul 07 21:04:08-040735 util-8620 DEBUG client_notify is running
Jul 07 21:04:08-040914 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:08-041112 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:08-041330 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:08-041784 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:08-042165 util-scheduler-8620 DEBUG Running task: 4647 / 0x6146380
Jul 07 21:04:08-042683 util-scheduler-8620 DEBUG Canceling task: 4648 / 0x6146380
Jul 07 21:04:08-042903 util-scheduler-8620 DEBUG Adding task: 4650 / 0x6146380
Jul 07 21:04:08-043299 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:08-043498 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:08-043762 util-scheduler-8620 DEBUG Adding task: 4651 / 0x46620a0
Jul 07 21:04:08-044064 util-scheduler-8620 DEBUG Checking readiness of task: 4651 / 0x46620a0
Jul 07 21:04:08-044417 util-scheduler-8620 DEBUG Checking readiness of task: 4645 / 0x46620a0
Jul 07 21:04:08-044614 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-044809 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-045002 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-045222 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-045418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-045628 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-045819 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-046013 util-scheduler-8620 DEBUG Running task: 4651 / 0x46620a0
Jul 07 21:04:08-046199 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:08-046377 util-8620 DEBUG process_notify is running
Jul 07 21:04:08-046554 util-8620 DEBUG client_notify is running
Jul 07 21:04:08-046733 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:08-046931 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:08-047123 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:08-047369 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:08-152780 util-scheduler-8620 DEBUG Checking readiness of task: 4645 / 0x46620a0
Jul 07 21:04:08-153041 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-153265 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-153459 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-153653 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-153844 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-154035 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-154226 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-154419 util-scheduler-8620 DEBUG Running task: 4645 / 0x46620a0
Jul 07 21:04:08-154826 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:08-155064 util-scheduler-8620 DEBUG Adding task: 4652 / 0x4662248
Jul 07 21:04:08-155324 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-155518 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-155709 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-155900 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-156090 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-156281 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-156470 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-156661 util-scheduler-8620 DEBUG Running task: 4652 / 0x4662248
Jul 07 21:04:08-156850 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:08-157047 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:08-157295 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:08-157500 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:08-157703 util-scheduler-8620 DEBUG Adding task: 4653 / 0x46620a0
Jul 07 21:04:08-157889 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:08-158094 util-scheduler-8620 DEBUG Adding task: 4654 / 0x46620a0
Jul 07 21:04:08-158337 util-scheduler-8620 DEBUG Checking readiness of task: 4654 / 0x46620a0
Jul 07 21:04:08-158532 util-scheduler-8620 DEBUG Checking readiness of task: 4653 / 0x46620a0
Jul 07 21:04:08-158725 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:08-158917 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:08-159108 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:08-159298 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:08-159490 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:08-159679 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:08-159870 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:08-160091 util-scheduler-8620 DEBUG Running task: 4653 / 0x46620a0
Jul 07 21:04:08-160279 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:08-160457 util-8620 DEBUG process_notify is running
Jul 07 21:04:08-160629 util-8620 DEBUG client_notify is running
Jul 07 21:04:08-160814 util-scheduler-8620 DEBUG Canceling task: 4650 / 0x6146380
Jul 07 21:04:08-161038 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:08-161281 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:08-161520 cadet-p2p-8620 DEBUG Checking 0x61e87b0 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:08-161754 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:08-161932 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:08-162121 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:08-162415 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:08-162611 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:08-162791 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:08-162979 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:08-163167 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:08-163345 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:08-163531 util-scheduler-8620 DEBUG Canceling task: 4646 / 0x6146c10
Jul 07 21:04:08-163743 util-scheduler-8620 DEBUG Adding task: 4655 / 0x6146c10
Jul 07 21:04:08-163989 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:08-164160 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:08-164340 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:08-164541 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:08-164718 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:08-164893 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:08-165093 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:08-165323 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:08-165507 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:08-165686 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:08-165876 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:08-166115 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:12-401840 util-scheduler-8620 DEBUG Checking readiness of task: 4654 / 0x46620a0
Jul 07 21:04:12-402234 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:12-403195 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:12-403394 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:12-403641 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:12-403850 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:12-404041 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:12-404232 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:12-404425 util-scheduler-8620 DEBUG Running task: 4639 / 0x52cbfb8
Jul 07 21:04:12-404664 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:12-404922 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:04:12-405130 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:12-405354 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:12-405556 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:12-405794 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:12-405975 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:12-406194 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:12-406486 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:12-406685 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:12-406948 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:12-407157 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:12-407476 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:12-407678 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:12-407903 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:12-408087 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:12-408263 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:12-408470 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:12-408685 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:12-408912 util-scheduler-8620 DEBUG Adding task: 4656 / 0x6146380
Jul 07 21:04:12-409092 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:12-409317 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:12-409495 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:12-409670 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:12-409907 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:12-410104 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:12-410281 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:12-410480 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:12-410726 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:12-410924 util-scheduler-8620 DEBUG Adding task: 4657 / 0x52cbfb8
Jul 07 21:04:12-411184 util-scheduler-8620 DEBUG Checking readiness of task: 4654 / 0x46620a0
Jul 07 21:04:12-411376 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:12-411566 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:12-411756 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:12-411946 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:12-412158 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:12-412363 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:12-412553 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:12-412757 util-scheduler-8620 DEBUG Running task: 4656 / 0x6146380
Jul 07 21:04:12-412980 util-scheduler-8620 DEBUG Adding task: 4658 / 0x6146380
Jul 07 21:04:12-413222 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:12-413427 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:12-413636 util-scheduler-8620 DEBUG Adding task: 4659 / 0x46620a0
Jul 07 21:04:12-413879 util-scheduler-8620 DEBUG Checking readiness of task: 4659 / 0x46620a0
Jul 07 21:04:12-414074 util-scheduler-8620 DEBUG Checking readiness of task: 4654 / 0x46620a0
Jul 07 21:04:12-414264 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:12-414453 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:12-414642 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:12-414831 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:12-415021 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:12-415209 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:12-415399 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:12-415589 util-scheduler-8620 DEBUG Running task: 4659 / 0x46620a0
Jul 07 21:04:12-415775 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:12-415953 util-8620 DEBUG process_notify is running
Jul 07 21:04:12-416126 util-8620 DEBUG client_notify is running
Jul 07 21:04:12-416305 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:12-416500 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:12-416707 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:12-416963 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:14-722144 util-scheduler-8620 DEBUG Checking readiness of task: 4654 / 0x46620a0
Jul 07 21:04:14-722515 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:14-722713 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:14-722905 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:14-723098 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:14-723291 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:14-723485 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:14-723683 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:14-723879 util-scheduler-8620 DEBUG Running task: 4654 / 0x46620a0
Jul 07 21:04:14-724299 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:14-724552 util-scheduler-8620 DEBUG Adding task: 4660 / 0x4662248
Jul 07 21:04:14-724826 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:14-725020 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:14-725282 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:14-725491 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:14-725719 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:14-725918 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:14-726108 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:14-726298 util-scheduler-8620 DEBUG Running task: 4660 / 0x4662248
Jul 07 21:04:14-726489 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:14-726689 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:14-726921 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:14-727128 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:14-727334 util-scheduler-8620 DEBUG Adding task: 4661 / 0x46620a0
Jul 07 21:04:14-727523 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:14-727728 util-scheduler-8620 DEBUG Adding task: 4662 / 0x46620a0
Jul 07 21:04:14-727975 util-scheduler-8620 DEBUG Checking readiness of task: 4662 / 0x46620a0
Jul 07 21:04:14-728168 util-scheduler-8620 DEBUG Checking readiness of task: 4661 / 0x46620a0
Jul 07 21:04:14-728360 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:14-728550 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:14-728740 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:14-728929 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:14-729119 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:14-729331 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:14-729520 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:14-729712 util-scheduler-8620 DEBUG Running task: 4661 / 0x46620a0
Jul 07 21:04:14-729896 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:14-730075 util-8620 DEBUG process_notify is running
Jul 07 21:04:14-730247 util-8620 DEBUG client_notify is running
Jul 07 21:04:14-730437 util-scheduler-8620 DEBUG Canceling task: 4658 / 0x6146380
Jul 07 21:04:14-730662 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:14-730883 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:14-731125 cadet-p2p-8620 DEBUG Checking 0x61edcc0 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:14-731408 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:14-731590 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:14-731781 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:14-732078 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:14-732276 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:14-732458 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:14-732647 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:14-732837 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:14-733017 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:14-733242 util-scheduler-8620 DEBUG Canceling task: 4655 / 0x6146c10
Jul 07 21:04:14-733459 util-scheduler-8620 DEBUG Adding task: 4663 / 0x6146c10
Jul 07 21:04:14-733741 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:14-733914 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:14-734104 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:14-734307 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:14-734483 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:14-734658 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:14-734857 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:14-735062 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:14-735246 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:14-735425 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:14-735614 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:14-735863 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:17-413764 util-scheduler-8620 DEBUG Checking readiness of task: 4662 / 0x46620a0
Jul 07 21:04:17-414142 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-415033 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-415233 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-415480 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-415689 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-415880 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-416072 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-416265 util-scheduler-8620 DEBUG Running task: 4657 / 0x52cbfb8
Jul 07 21:04:17-416503 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:17-416760 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:04:17-416967 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:17-417168 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:17-417394 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:17-417630 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:17-417811 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:17-418033 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:17-418323 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:17-418520 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:17-418756 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:17-418967 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:17-419283 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:17-419485 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:17-419709 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:17-419892 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:17-420068 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:17-420273 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:17-420514 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:17-420741 util-scheduler-8620 DEBUG Adding task: 4664 / 0x6146380
Jul 07 21:04:17-420922 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:17-421124 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:17-421324 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:17-421498 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:17-421738 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:17-421934 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:17-422110 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:17-422309 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:17-422552 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:17-422750 util-scheduler-8620 DEBUG Adding task: 4665 / 0x52cbfb8
Jul 07 21:04:17-423006 util-scheduler-8620 DEBUG Checking readiness of task: 4662 / 0x46620a0
Jul 07 21:04:17-423200 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-423391 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-423580 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-423771 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-423961 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-424150 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-424338 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-424528 util-scheduler-8620 DEBUG Running task: 4664 / 0x6146380
Jul 07 21:04:17-424736 util-scheduler-8620 DEBUG Adding task: 4666 / 0x6146380
Jul 07 21:04:17-424957 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:17-425161 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:17-425403 util-scheduler-8620 DEBUG Adding task: 4667 / 0x46620a0
Jul 07 21:04:17-425648 util-scheduler-8620 DEBUG Checking readiness of task: 4667 / 0x46620a0
Jul 07 21:04:17-425842 util-scheduler-8620 DEBUG Checking readiness of task: 4662 / 0x46620a0
Jul 07 21:04:17-426032 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-426222 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-426411 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-426601 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-426790 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-426979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-427167 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-427359 util-scheduler-8620 DEBUG Running task: 4667 / 0x46620a0
Jul 07 21:04:17-427543 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:17-427723 util-8620 DEBUG process_notify is running
Jul 07 21:04:17-427895 util-8620 DEBUG client_notify is running
Jul 07 21:04:17-428073 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:17-428268 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:17-428459 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:17-428714 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:17-923282 util-scheduler-8620 DEBUG Checking readiness of task: 4662 / 0x46620a0
Jul 07 21:04:17-923593 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-923789 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-923982 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-924173 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-924392 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-924587 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-924786 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-924980 util-scheduler-8620 DEBUG Running task: 4662 / 0x46620a0
Jul 07 21:04:17-925420 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:17-925666 util-scheduler-8620 DEBUG Adding task: 4668 / 0x4662248
Jul 07 21:04:17-925935 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-926128 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-926319 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-926510 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-926700 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-926890 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-927080 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-927269 util-scheduler-8620 DEBUG Running task: 4668 / 0x4662248
Jul 07 21:04:17-927460 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:17-927658 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:17-927885 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:17-928088 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:17-928291 util-scheduler-8620 DEBUG Adding task: 4669 / 0x46620a0
Jul 07 21:04:17-928477 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:17-928683 util-scheduler-8620 DEBUG Adding task: 4670 / 0x46620a0
Jul 07 21:04:17-928925 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:17-929117 util-scheduler-8620 DEBUG Checking readiness of task: 4669 / 0x46620a0
Jul 07 21:04:17-929330 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:17-929520 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:17-929712 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:17-929901 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:17-930091 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:17-930279 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:17-930469 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:17-930659 util-scheduler-8620 DEBUG Running task: 4669 / 0x46620a0
Jul 07 21:04:17-930845 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:17-931022 util-8620 DEBUG process_notify is running
Jul 07 21:04:17-931194 util-8620 DEBUG client_notify is running
Jul 07 21:04:17-931380 util-scheduler-8620 DEBUG Canceling task: 4666 / 0x6146380
Jul 07 21:04:17-931605 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:17-931826 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:17-932062 cadet-p2p-8620 DEBUG Checking 0x61f0940 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:17-932296 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:17-932474 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:17-932663 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:17-932947 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:17-933143 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:17-933342 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:17-933531 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:17-933720 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:17-933898 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:17-934099 util-scheduler-8620 DEBUG Canceling task: 4663 / 0x6146c10
Jul 07 21:04:17-934313 util-scheduler-8620 DEBUG Adding task: 4671 / 0x6146c10
Jul 07 21:04:17-934561 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:17-934734 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:17-934914 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:17-935115 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:17-935291 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:17-935465 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:17-935662 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:17-935866 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:17-936050 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:17-936227 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:17-936417 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:17-936664 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:20-056679 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:20-057030 util-scheduler-8620 DEBUG Checking readiness of task: 4558 / 0x465ee60
Jul 07 21:04:20-057254 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:20-057451 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:20-057647 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:20-057840 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:20-058034 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:20-058226 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:20-058425 util-scheduler-8620 DEBUG Running task: 4558 / 0x465ee60
Jul 07 21:04:20-058851 util-8620 DEBUG receive_ready read 104/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 21:04:20-059110 util-scheduler-8620 DEBUG Adding task: 4672 / 0x465f008
Jul 07 21:04:20-059391 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:20-059588 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:20-059782 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:20-059976 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:20-060169 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:20-060360 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:20-060552 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:20-060744 util-scheduler-8620 DEBUG Running task: 4672 / 0x465f008
Jul 07 21:04:20-060945 util-8620 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:04:20-061220 nse-api-8620 DEBUG Received information about peer `QCZ4' from peerinfo database
Jul 07 21:04:20-061513 cadet-hll-8620 DEBUG  hello for QCZ4 (64 bytes), expires on Tue Jul 08 09:04:20 2014
Jul 07 21:04:20-061742 cadet-p2p-8620 DEBUG set hello for QCZ4
Jul 07 21:04:20-062031 cadet-p2p-8620 DEBUG  merge into 0x61f30f8 (64 bytes)
Jul 07 21:04:20-062231 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:20-062447 util-scheduler-8620 DEBUG Adding task: 4673 / 0x465ee60
Jul 07 21:04:22-425286 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:22-425656 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:22-426292 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:22-426497 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:22-426748 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:22-426956 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:22-427174 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:22-427364 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:22-427558 util-scheduler-8620 DEBUG Running task: 4665 / 0x52cbfb8
Jul 07 21:04:22-427794 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:22-428053 cadet-tun-8620 DEBUG  kx started 16 m ago
Jul 07 21:04:22-428260 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:22-428463 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:22-428666 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:22-428901 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:22-429081 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:22-429324 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:22-429615 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:22-429813 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:22-430050 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:22-430257 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:22-430574 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:22-430775 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:22-430999 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:22-431183 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:22-431358 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:22-431565 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:22-431781 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:22-432006 util-scheduler-8620 DEBUG Adding task: 4674 / 0x6146380
Jul 07 21:04:22-432186 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:22-432390 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:22-432567 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:22-432742 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:22-432982 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:22-433178 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:22-433376 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:22-433576 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:22-433820 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:22-434019 util-scheduler-8620 DEBUG Adding task: 4675 / 0x52cbfb8
Jul 07 21:04:22-434275 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:22-434468 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:22-434657 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:22-434847 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:22-435036 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:22-435226 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:22-435435 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:22-435625 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:22-435816 util-scheduler-8620 DEBUG Running task: 4674 / 0x6146380
Jul 07 21:04:22-436025 util-scheduler-8620 DEBUG Adding task: 4676 / 0x6146380
Jul 07 21:04:22-436248 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:22-436451 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:22-436659 util-scheduler-8620 DEBUG Adding task: 4677 / 0x46620a0
Jul 07 21:04:22-436904 util-scheduler-8620 DEBUG Checking readiness of task: 4677 / 0x46620a0
Jul 07 21:04:22-437097 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:22-437307 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:22-437517 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:22-437708 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:22-437898 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:22-438087 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:22-438277 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:22-438466 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:22-438658 util-scheduler-8620 DEBUG Running task: 4677 / 0x46620a0
Jul 07 21:04:22-438859 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:22-439039 util-8620 DEBUG process_notify is running
Jul 07 21:04:22-439213 util-8620 DEBUG client_notify is running
Jul 07 21:04:22-439392 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:22-439587 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:22-439779 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:22-440031 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:26-112734 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:26-113120 util-scheduler-8620 DEBUG Checking readiness of task: 4670 / 0x46620a0
Jul 07 21:04:26-113355 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:26-113562 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:26-113756 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:26-113952 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:26-114144 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:26-114336 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:26-114533 util-scheduler-8620 DEBUG Running task: 4670 / 0x46620a0
Jul 07 21:04:26-114956 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:26-115220 util-scheduler-8620 DEBUG Adding task: 4678 / 0x4662248
Jul 07 21:04:26-115501 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:26-115696 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:26-115888 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:26-116080 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:26-116272 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:26-116462 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:26-116652 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:26-116845 util-scheduler-8620 DEBUG Running task: 4678 / 0x4662248
Jul 07 21:04:26-117038 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:26-117259 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:26-117495 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:26-117704 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:26-117911 util-scheduler-8620 DEBUG Adding task: 4679 / 0x46620a0
Jul 07 21:04:26-118100 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:26-118308 util-scheduler-8620 DEBUG Adding task: 4680 / 0x46620a0
Jul 07 21:04:26-118555 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:26-118750 util-scheduler-8620 DEBUG Checking readiness of task: 4679 / 0x46620a0
Jul 07 21:04:26-118958 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:26-119149 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:26-119372 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:26-119564 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:26-119755 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:26-119944 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:26-120135 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:26-120328 util-scheduler-8620 DEBUG Running task: 4679 / 0x46620a0
Jul 07 21:04:26-120515 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:26-120694 util-8620 DEBUG process_notify is running
Jul 07 21:04:26-120868 util-8620 DEBUG client_notify is running
Jul 07 21:04:26-121057 util-scheduler-8620 DEBUG Canceling task: 4676 / 0x6146380
Jul 07 21:04:26-121305 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:26-121528 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:26-121768 cadet-p2p-8620 DEBUG Checking 0x61f3d48 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:26-122004 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:26-122183 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:26-122375 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:26-122662 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:26-122859 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:26-123040 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:26-123229 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:26-123420 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:26-123599 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:26-123784 util-scheduler-8620 DEBUG Canceling task: 4671 / 0x6146c10
Jul 07 21:04:26-124002 util-scheduler-8620 DEBUG Adding task: 4681 / 0x6146c10
Jul 07 21:04:26-124255 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:26-124428 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:26-124609 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:26-124812 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:26-124989 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:26-125165 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:26-125388 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:26-125595 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:26-125780 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:26-125960 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:26-126174 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:26-126418 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:26-912825 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:26-913228 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:26-913427 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:26-913620 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:26-913813 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:26-914007 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:26-914197 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:26-914387 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:26-914582 util-scheduler-8620 DEBUG Running task: 4146 / 0x53a5de0
Jul 07 21:04:26-914853 cadet-con-8620 DEBUG BCK keepalive for M9KEP6HP (->P00P)
Jul 07 21:04:27-434678 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:27-434997 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-435498 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-435948 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-436288 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-436485 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-436676 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-436866 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-437059 util-scheduler-8620 DEBUG Running task: 4675 / 0x52cbfb8
Jul 07 21:04:27-437324 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:27-437582 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:27-437788 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:27-437989 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:27-438194 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:27-438431 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:27-438612 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:27-438833 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:27-439124 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:27-439321 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:27-439558 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:27-439766 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:27-440082 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:27-440284 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:27-440508 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:27-440693 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:27-440869 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:27-441076 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:27-441320 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:27-441544 util-scheduler-8620 DEBUG Adding task: 4682 / 0x6146380
Jul 07 21:04:27-441724 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:27-441927 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:27-442103 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:27-442278 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:27-442515 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:27-442712 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:27-442889 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:27-443087 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:27-443332 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:27-443529 util-scheduler-8620 DEBUG Adding task: 4683 / 0x52cbfb8
Jul 07 21:04:27-443791 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:27-443984 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-444174 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-444364 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-444555 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-444744 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-444934 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-445123 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-445343 util-scheduler-8620 DEBUG Running task: 4682 / 0x6146380
Jul 07 21:04:27-445552 util-scheduler-8620 DEBUG Adding task: 4684 / 0x6146380
Jul 07 21:04:27-445775 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:27-445978 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:27-446185 util-scheduler-8620 DEBUG Adding task: 4685 / 0x46620a0
Jul 07 21:04:27-446458 util-scheduler-8620 DEBUG Checking readiness of task: 4685 / 0x46620a0
Jul 07 21:04:27-446653 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:27-446857 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-447048 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-447238 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-447428 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-447618 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-447807 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-447997 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-448188 util-scheduler-8620 DEBUG Running task: 4685 / 0x46620a0
Jul 07 21:04:27-448373 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:27-448551 util-8620 DEBUG process_notify is running
Jul 07 21:04:27-448725 util-8620 DEBUG client_notify is running
Jul 07 21:04:27-448904 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:27-449099 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:27-449316 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:27-449571 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:27-541805 util-scheduler-8620 DEBUG Checking readiness of task: 4680 / 0x46620a0
Jul 07 21:04:27-542022 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-542215 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-542407 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-542599 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-542789 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-542979 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-543170 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-543366 util-scheduler-8620 DEBUG Running task: 4680 / 0x46620a0
Jul 07 21:04:27-543772 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:27-544005 util-scheduler-8620 DEBUG Adding task: 4686 / 0x4662248
Jul 07 21:04:27-544258 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-544452 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-544642 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-544832 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-545022 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-545241 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-545436 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-545626 util-scheduler-8620 DEBUG Running task: 4686 / 0x4662248
Jul 07 21:04:27-545818 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:27-546014 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:27-546235 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:27-546433 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:27-546633 util-scheduler-8620 DEBUG Adding task: 4687 / 0x46620a0
Jul 07 21:04:27-546819 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:27-547022 util-scheduler-8620 DEBUG Adding task: 4688 / 0x46620a0
Jul 07 21:04:27-547264 util-scheduler-8620 DEBUG Checking readiness of task: 4688 / 0x46620a0
Jul 07 21:04:27-547456 util-scheduler-8620 DEBUG Checking readiness of task: 4687 / 0x46620a0
Jul 07 21:04:27-547665 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:27-547855 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:27-548044 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:27-548235 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:27-548424 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:27-548613 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:27-548801 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:27-549000 util-scheduler-8620 DEBUG Running task: 4687 / 0x46620a0
Jul 07 21:04:27-549184 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:27-549386 util-8620 DEBUG process_notify is running
Jul 07 21:04:27-549558 util-8620 DEBUG client_notify is running
Jul 07 21:04:27-549743 util-scheduler-8620 DEBUG Canceling task: 4684 / 0x6146380
Jul 07 21:04:27-549968 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:27-550185 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:27-550418 cadet-p2p-8620 DEBUG Checking 0x61f6e88 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:27-550652 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:27-550829 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:27-551016 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:27-551299 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:27-551493 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:27-551671 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:27-551859 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:27-552047 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:27-552225 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:27-552407 util-scheduler-8620 DEBUG Canceling task: 4681 / 0x6146c10
Jul 07 21:04:27-552618 util-scheduler-8620 DEBUG Adding task: 4689 / 0x6146c10
Jul 07 21:04:27-552862 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:27-553033 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:27-553238 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:27-553440 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:27-553616 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:27-553790 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:27-553988 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:27-554193 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:27-554376 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:27-554555 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:27-554744 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:27-554991 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:32-448584 util-scheduler-8620 DEBUG Checking readiness of task: 4688 / 0x46620a0
Jul 07 21:04:32-448982 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:32-449615 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:32-449837 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:32-450083 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:32-450279 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:32-450471 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:32-450661 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:32-450855 util-scheduler-8620 DEBUG Running task: 4683 / 0x52cbfb8
Jul 07 21:04:32-451096 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:32-451354 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:32-451585 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:32-451788 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:32-451991 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:32-452227 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:32-452408 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:32-452630 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:32-452921 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:32-453119 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:32-453383 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:32-453592 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:32-453910 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:32-454124 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:32-454347 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:32-454532 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:32-454707 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:32-454914 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:32-455129 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:32-455357 util-scheduler-8620 DEBUG Adding task: 4690 / 0x6146380
Jul 07 21:04:32-455537 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:32-455741 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:32-455918 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:32-456093 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:32-456332 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:32-456528 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:32-456705 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:32-456904 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:32-457150 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:32-457370 util-scheduler-8620 DEBUG Adding task: 4691 / 0x52cbfb8
Jul 07 21:04:32-457634 util-scheduler-8620 DEBUG Checking readiness of task: 4688 / 0x46620a0
Jul 07 21:04:32-457827 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:32-458018 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:32-458208 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:32-458398 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:32-458588 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:32-458778 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:32-458967 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:32-459157 util-scheduler-8620 DEBUG Running task: 4690 / 0x6146380
Jul 07 21:04:32-459365 util-scheduler-8620 DEBUG Adding task: 4692 / 0x6146380
Jul 07 21:04:32-459588 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:32-459792 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:32-460060 util-scheduler-8620 DEBUG Adding task: 4693 / 0x46620a0
Jul 07 21:04:32-460376 util-scheduler-8620 DEBUG Checking readiness of task: 4693 / 0x46620a0
Jul 07 21:04:32-460572 util-scheduler-8620 DEBUG Checking readiness of task: 4688 / 0x46620a0
Jul 07 21:04:32-460764 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:32-460954 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:32-461144 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:32-461358 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:32-461549 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:32-461756 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:32-461946 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:32-462139 util-scheduler-8620 DEBUG Running task: 4693 / 0x46620a0
Jul 07 21:04:32-462325 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:32-462505 util-8620 DEBUG process_notify is running
Jul 07 21:04:32-462680 util-8620 DEBUG client_notify is running
Jul 07 21:04:32-462859 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:32-463058 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:32-463250 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:32-463503 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:34-602833 util-scheduler-8620 DEBUG Checking readiness of task: 4688 / 0x46620a0
Jul 07 21:04:34-603216 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:34-603419 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:34-603613 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:34-603805 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:34-603997 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:34-604186 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:34-604376 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:34-604571 util-scheduler-8620 DEBUG Running task: 4688 / 0x46620a0
Jul 07 21:04:34-604992 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:34-605272 util-scheduler-8620 DEBUG Adding task: 4694 / 0x4662248
Jul 07 21:04:34-605552 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:34-605839 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:34-606035 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:34-606227 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:34-606418 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:34-606610 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:34-606800 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:34-606991 util-scheduler-8620 DEBUG Running task: 4694 / 0x4662248
Jul 07 21:04:34-607184 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:34-607384 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:34-607619 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:34-607827 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:34-608035 util-scheduler-8620 DEBUG Adding task: 4695 / 0x46620a0
Jul 07 21:04:34-608225 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:34-608431 util-scheduler-8620 DEBUG Adding task: 4696 / 0x46620a0
Jul 07 21:04:34-608679 util-scheduler-8620 DEBUG Checking readiness of task: 4696 / 0x46620a0
Jul 07 21:04:34-608873 util-scheduler-8620 DEBUG Checking readiness of task: 4695 / 0x46620a0
Jul 07 21:04:34-609068 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:34-609282 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:34-609473 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:34-609665 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:34-609857 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:34-610046 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:34-610237 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:34-610459 util-scheduler-8620 DEBUG Running task: 4695 / 0x46620a0
Jul 07 21:04:34-610648 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:34-610827 util-8620 DEBUG process_notify is running
Jul 07 21:04:34-611001 util-8620 DEBUG client_notify is running
Jul 07 21:04:34-611190 util-scheduler-8620 DEBUG Canceling task: 4692 / 0x6146380
Jul 07 21:04:34-611422 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:34-611644 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:34-611886 cadet-p2p-8620 DEBUG Checking 0x61f9c68 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:34-612122 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:34-612301 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:34-612492 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:34-612780 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:34-612977 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:34-613157 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:34-613369 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:34-613559 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:34-613738 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:34-613923 util-scheduler-8620 DEBUG Canceling task: 4689 / 0x6146c10
Jul 07 21:04:34-614137 util-scheduler-8620 DEBUG Adding task: 4697 / 0x6146c10
Jul 07 21:04:34-614389 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:34-614562 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:34-614744 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:34-614947 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:34-615125 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:34-615313 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:34-615513 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:34-615719 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:34-615907 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:34-616088 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:34-616279 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:34-616522 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:37-460376 util-scheduler-8620 DEBUG Checking readiness of task: 4696 / 0x46620a0
Jul 07 21:04:37-460755 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:37-461209 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:37-461461 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:37-461697 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:37-461892 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:37-462086 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:37-462293 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:37-462487 util-scheduler-8620 DEBUG Running task: 4691 / 0x52cbfb8
Jul 07 21:04:37-462725 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:37-462983 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:37-463191 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:37-463392 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:37-463595 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:37-463831 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:37-464012 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:37-464233 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:37-464523 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:37-464722 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:37-464988 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:37-465220 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:37-465541 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:37-465743 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:37-465968 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:37-466153 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:37-466329 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:37-466536 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:37-466751 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:37-466978 util-scheduler-8620 DEBUG Adding task: 4698 / 0x6146380
Jul 07 21:04:37-467159 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:37-467364 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:37-467541 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:37-467715 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:37-467954 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:37-468150 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:37-468328 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:37-468526 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:37-468769 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:37-468967 util-scheduler-8620 DEBUG Adding task: 4699 / 0x52cbfb8
Jul 07 21:04:37-469247 util-scheduler-8620 DEBUG Checking readiness of task: 4696 / 0x46620a0
Jul 07 21:04:37-469442 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:37-469633 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:37-469823 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:37-470013 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:37-470202 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:37-470392 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:37-470580 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:37-470770 util-scheduler-8620 DEBUG Running task: 4698 / 0x6146380
Jul 07 21:04:37-471014 util-scheduler-8620 DEBUG Adding task: 4700 / 0x6146380
Jul 07 21:04:37-471237 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:37-471440 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:37-471648 util-scheduler-8620 DEBUG Adding task: 4701 / 0x46620a0
Jul 07 21:04:37-471892 util-scheduler-8620 DEBUG Checking readiness of task: 4701 / 0x46620a0
Jul 07 21:04:37-472087 util-scheduler-8620 DEBUG Checking readiness of task: 4696 / 0x46620a0
Jul 07 21:04:37-472277 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:37-472467 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:37-472656 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:37-472846 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:37-473035 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:37-473242 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:37-473432 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:37-473623 util-scheduler-8620 DEBUG Running task: 4701 / 0x46620a0
Jul 07 21:04:37-473810 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:37-473988 util-8620 DEBUG process_notify is running
Jul 07 21:04:37-474161 util-8620 DEBUG client_notify is running
Jul 07 21:04:37-474340 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:37-474536 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:37-474743 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:37-474998 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:40-357378 util-scheduler-8620 DEBUG Checking readiness of task: 4696 / 0x46620a0
Jul 07 21:04:40-357781 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:40-357983 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:40-358183 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:40-358379 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:40-358573 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:40-358764 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:40-358954 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:40-359149 util-scheduler-8620 DEBUG Running task: 4696 / 0x46620a0
Jul 07 21:04:40-359575 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:40-359835 util-scheduler-8620 DEBUG Adding task: 4702 / 0x4662248
Jul 07 21:04:40-360115 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:40-360307 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:40-360497 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:40-360687 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:40-360879 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:40-361067 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:40-366822 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:40-367031 util-scheduler-8620 DEBUG Running task: 4702 / 0x4662248
Jul 07 21:04:40-367227 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:40-367428 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:40-367664 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:40-367871 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:40-368078 util-scheduler-8620 DEBUG Adding task: 4703 / 0x46620a0
Jul 07 21:04:40-368266 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:40-368472 util-scheduler-8620 DEBUG Adding task: 4704 / 0x46620a0
Jul 07 21:04:40-368734 util-scheduler-8620 DEBUG Checking readiness of task: 4704 / 0x46620a0
Jul 07 21:04:40-368926 util-scheduler-8620 DEBUG Checking readiness of task: 4703 / 0x46620a0
Jul 07 21:04:40-369118 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:40-369333 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:40-369527 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:40-369718 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:40-369919 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:40-370113 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:40-370308 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:40-370509 util-scheduler-8620 DEBUG Running task: 4703 / 0x46620a0
Jul 07 21:04:40-370699 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:40-370880 util-8620 DEBUG process_notify is running
Jul 07 21:04:40-371058 util-8620 DEBUG client_notify is running
Jul 07 21:04:40-371251 util-scheduler-8620 DEBUG Canceling task: 4700 / 0x6146380
Jul 07 21:04:40-371491 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:40-371718 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:40-372475 cadet-p2p-8620 DEBUG Checking 0x61fc870 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:40-372743 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:40-372923 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:40-373115 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:40-373430 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:40-373626 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:40-373806 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:40-373994 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:40-374183 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:40-374362 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:40-374549 util-scheduler-8620 DEBUG Canceling task: 4697 / 0x6146c10
Jul 07 21:04:40-374767 util-scheduler-8620 DEBUG Adding task: 4705 / 0x6146c10
Jul 07 21:04:40-375018 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:40-375189 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:40-375371 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:40-375572 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:40-375747 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:40-375921 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:40-376120 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:40-376325 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:40-376508 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:40-376687 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:40-376878 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:40-378053 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:42-469758 util-scheduler-8620 DEBUG Checking readiness of task: 4704 / 0x46620a0
Jul 07 21:04:42-470152 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:42-470761 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:42-470993 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:42-471232 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:42-471463 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:42-471654 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:42-471845 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:42-472037 util-scheduler-8620 DEBUG Running task: 4699 / 0x52cbfb8
Jul 07 21:04:42-472276 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:42-472534 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:42-472742 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:42-472942 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:42-473164 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:42-473423 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:42-473605 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:42-473827 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:42-474120 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:42-474334 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:42-474626 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:42-474910 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:42-475231 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:42-475432 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:42-475657 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:42-475841 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:42-476018 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:42-476225 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:42-476468 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:42-476697 util-scheduler-8620 DEBUG Adding task: 4706 / 0x6146380
Jul 07 21:04:42-476878 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:42-477082 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:42-477281 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:42-477456 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:42-477695 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:42-477892 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:42-478070 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:42-478269 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:42-478514 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:42-478711 util-scheduler-8620 DEBUG Adding task: 4707 / 0x52cbfb8
Jul 07 21:04:42-478972 util-scheduler-8620 DEBUG Checking readiness of task: 4704 / 0x46620a0
Jul 07 21:04:42-479166 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:42-479358 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:42-479547 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:42-479739 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:42-479928 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:42-480117 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:42-480308 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:42-480498 util-scheduler-8620 DEBUG Running task: 4706 / 0x6146380
Jul 07 21:04:42-480706 util-scheduler-8620 DEBUG Adding task: 4708 / 0x6146380
Jul 07 21:04:42-480928 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:42-481132 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:42-481362 util-scheduler-8620 DEBUG Adding task: 4709 / 0x46620a0
Jul 07 21:04:42-481608 util-scheduler-8620 DEBUG Checking readiness of task: 4709 / 0x46620a0
Jul 07 21:04:42-481801 util-scheduler-8620 DEBUG Checking readiness of task: 4704 / 0x46620a0
Jul 07 21:04:42-481991 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:42-482182 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:42-482372 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:42-482561 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:42-482752 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:42-482941 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:42-483130 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:42-483322 util-scheduler-8620 DEBUG Running task: 4709 / 0x46620a0
Jul 07 21:04:42-483507 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:42-483698 util-8620 DEBUG process_notify is running
Jul 07 21:04:42-483872 util-8620 DEBUG client_notify is running
Jul 07 21:04:42-484052 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:42-484248 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:42-484439 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:42-484743 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:43-122986 util-scheduler-8620 DEBUG Checking readiness of task: 4704 / 0x46620a0
Jul 07 21:04:43-123337 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:43-123534 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:43-123727 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:43-123919 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:43-124144 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:43-124346 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:43-124537 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:43-124733 util-scheduler-8620 DEBUG Running task: 4704 / 0x46620a0
Jul 07 21:04:43-125152 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:43-125431 util-scheduler-8620 DEBUG Adding task: 4710 / 0x4662248
Jul 07 21:04:43-125706 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:43-125903 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:43-126135 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:43-126329 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:43-126520 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:43-126710 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:43-126898 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:43-127088 util-scheduler-8620 DEBUG Running task: 4710 / 0x4662248
Jul 07 21:04:43-127279 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:43-127478 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:43-127708 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:43-127913 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:43-128118 util-scheduler-8620 DEBUG Adding task: 4711 / 0x46620a0
Jul 07 21:04:43-128305 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:43-128511 util-scheduler-8620 DEBUG Adding task: 4712 / 0x46620a0
Jul 07 21:04:43-128754 util-scheduler-8620 DEBUG Checking readiness of task: 4712 / 0x46620a0
Jul 07 21:04:43-128948 util-scheduler-8620 DEBUG Checking readiness of task: 4711 / 0x46620a0
Jul 07 21:04:43-129140 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:43-129353 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:43-129544 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:43-129734 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:43-129925 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:43-130114 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:43-130304 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:43-130497 util-scheduler-8620 DEBUG Running task: 4711 / 0x46620a0
Jul 07 21:04:43-130682 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:43-130859 util-8620 DEBUG process_notify is running
Jul 07 21:04:43-131031 util-8620 DEBUG client_notify is running
Jul 07 21:04:43-131219 util-scheduler-8620 DEBUG Canceling task: 4708 / 0x6146380
Jul 07 21:04:43-131444 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:43-131664 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:43-131951 cadet-p2p-8620 DEBUG Checking 0x61ff510 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:43-132227 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:43-132478 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:43-132671 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:43-132958 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:43-133154 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:43-133354 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:43-133543 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:43-133732 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:43-133911 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:43-134118 util-scheduler-8620 DEBUG Canceling task: 4705 / 0x6146c10
Jul 07 21:04:43-134332 util-scheduler-8620 DEBUG Adding task: 4713 / 0x6146c10
Jul 07 21:04:43-134582 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:43-134753 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:43-134934 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:43-135135 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:43-135312 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:43-135486 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:43-135685 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:43-135891 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:43-136075 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:43-136254 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:43-136444 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:43-136694 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:47-482386 util-scheduler-8620 DEBUG Checking readiness of task: 4712 / 0x46620a0
Jul 07 21:04:47-482774 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:47-483366 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:47-483599 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:47-483835 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:47-484030 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:47-484221 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:47-484411 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:47-484607 util-scheduler-8620 DEBUG Running task: 4707 / 0x52cbfb8
Jul 07 21:04:47-484846 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:47-485102 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:47-485331 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:47-485532 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:47-485736 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:47-485971 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:47-486152 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:47-486374 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:47-486665 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:47-486863 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:47-487100 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:47-487307 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:47-487625 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:47-487826 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:47-488051 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:47-488235 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:47-488410 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:47-488619 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:47-488833 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:47-489059 util-scheduler-8620 DEBUG Adding task: 4714 / 0x6146380
Jul 07 21:04:47-489261 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:47-489466 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:47-489656 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:47-489831 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:47-490088 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:47-490284 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:47-490488 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:47-490688 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:47-490933 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:47-491132 util-scheduler-8620 DEBUG Adding task: 4715 / 0x52cbfb8
Jul 07 21:04:47-491394 util-scheduler-8620 DEBUG Checking readiness of task: 4712 / 0x46620a0
Jul 07 21:04:47-491589 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:47-491779 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:47-491970 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:47-492159 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:47-492349 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:47-492538 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:47-492726 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:47-492916 util-scheduler-8620 DEBUG Running task: 4714 / 0x6146380
Jul 07 21:04:47-493123 util-scheduler-8620 DEBUG Adding task: 4716 / 0x6146380
Jul 07 21:04:47-493366 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:47-493568 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:47-493777 util-scheduler-8620 DEBUG Adding task: 4717 / 0x46620a0
Jul 07 21:04:47-494021 util-scheduler-8620 DEBUG Checking readiness of task: 4717 / 0x46620a0
Jul 07 21:04:47-494215 util-scheduler-8620 DEBUG Checking readiness of task: 4712 / 0x46620a0
Jul 07 21:04:47-494405 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:47-494595 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:47-494785 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:47-494974 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:47-495163 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:47-495352 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:47-495541 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:47-495734 util-scheduler-8620 DEBUG Running task: 4717 / 0x46620a0
Jul 07 21:04:47-495921 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:47-496100 util-8620 DEBUG process_notify is running
Jul 07 21:04:47-496274 util-8620 DEBUG client_notify is running
Jul 07 21:04:47-496454 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:47-496652 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:47-496844 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:47-497096 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:49-460140 util-scheduler-8620 DEBUG Checking readiness of task: 4712 / 0x46620a0
Jul 07 21:04:49-460519 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:49-460720 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:49-460922 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:49-461114 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:49-461329 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:49-461521 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:49-461719 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:49-461930 util-scheduler-8620 DEBUG Running task: 4712 / 0x46620a0
Jul 07 21:04:49-462349 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:49-462605 util-scheduler-8620 DEBUG Adding task: 4718 / 0x4662248
Jul 07 21:04:49-462888 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:49-463111 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:49-463332 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:49-463523 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:49-463713 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:49-463901 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:49-464092 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:49-464282 util-scheduler-8620 DEBUG Running task: 4718 / 0x4662248
Jul 07 21:04:49-464471 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:49-464671 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:49-464901 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:49-465107 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:49-465335 util-scheduler-8620 DEBUG Adding task: 4719 / 0x46620a0
Jul 07 21:04:49-465522 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:49-465729 util-scheduler-8620 DEBUG Adding task: 4720 / 0x46620a0
Jul 07 21:04:49-465972 util-scheduler-8620 DEBUG Checking readiness of task: 4720 / 0x46620a0
Jul 07 21:04:49-466165 util-scheduler-8620 DEBUG Checking readiness of task: 4719 / 0x46620a0
Jul 07 21:04:49-466356 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:49-466569 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:49-466772 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:49-466970 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:49-467159 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:49-467348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:49-467536 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:49-467727 util-scheduler-8620 DEBUG Running task: 4719 / 0x46620a0
Jul 07 21:04:49-467917 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:49-468102 util-8620 DEBUG process_notify is running
Jul 07 21:04:49-468275 util-8620 DEBUG client_notify is running
Jul 07 21:04:49-468465 util-scheduler-8620 DEBUG Canceling task: 4716 / 0x6146380
Jul 07 21:04:49-468695 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:49-468916 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:49-469157 cadet-p2p-8620 DEBUG Checking 0x62021b8 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:49-470058 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:49-470249 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:49-470446 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:49-470741 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:49-470940 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:49-471122 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:49-471313 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:49-471502 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:49-471682 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:49-471875 util-scheduler-8620 DEBUG Canceling task: 4713 / 0x6146c10
Jul 07 21:04:49-472134 util-scheduler-8620 DEBUG Adding task: 4721 / 0x6146c10
Jul 07 21:04:49-472389 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:49-472563 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:49-472744 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:49-472945 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:49-473404 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:49-473583 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:49-473784 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:49-474019 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:49-474210 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:49-474676 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:49-474875 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:49-475318 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:52-494325 util-scheduler-8620 DEBUG Checking readiness of task: 4720 / 0x46620a0
Jul 07 21:04:52-494732 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-495354 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-495555 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-495803 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-496017 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-496208 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-496399 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-496592 util-scheduler-8620 DEBUG Running task: 4715 / 0x52cbfb8
Jul 07 21:04:52-496832 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:52-497090 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:52-497320 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:52-497522 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:52-497725 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:52-497961 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:52-498141 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:52-498362 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:52-498655 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:52-498854 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:52-499091 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:52-499299 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:52-499618 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:52-499819 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:52-500043 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:52-500226 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:52-500401 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:52-500610 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:52-500824 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:52-501051 util-scheduler-8620 DEBUG Adding task: 4722 / 0x6146380
Jul 07 21:04:52-501265 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:52-501472 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:52-501650 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:52-501826 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:52-502064 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:52-502260 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:52-502437 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:52-502636 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:52-502899 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:52-503101 util-scheduler-8620 DEBUG Adding task: 4723 / 0x52cbfb8
Jul 07 21:04:52-503365 util-scheduler-8620 DEBUG Checking readiness of task: 4720 / 0x46620a0
Jul 07 21:04:52-503559 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-503751 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-503940 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-504158 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-504350 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-504538 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-504727 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-504916 util-scheduler-8620 DEBUG Running task: 4722 / 0x6146380
Jul 07 21:04:52-505126 util-scheduler-8620 DEBUG Adding task: 4724 / 0x6146380
Jul 07 21:04:52-505372 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:52-505576 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:52-505784 util-scheduler-8620 DEBUG Adding task: 4725 / 0x46620a0
Jul 07 21:04:52-506028 util-scheduler-8620 DEBUG Checking readiness of task: 4725 / 0x46620a0
Jul 07 21:04:52-506222 util-scheduler-8620 DEBUG Checking readiness of task: 4720 / 0x46620a0
Jul 07 21:04:52-506411 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-506601 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-506790 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-506980 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-507170 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-507358 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-507547 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-507738 util-scheduler-8620 DEBUG Running task: 4725 / 0x46620a0
Jul 07 21:04:52-507928 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:52-508106 util-8620 DEBUG process_notify is running
Jul 07 21:04:52-508282 util-8620 DEBUG client_notify is running
Jul 07 21:04:52-508461 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:52-508658 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:52-508850 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:52-509104 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:52-596538 util-scheduler-8620 DEBUG Checking readiness of task: 4720 / 0x46620a0
Jul 07 21:04:52-596776 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-596970 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-597161 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-597381 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-597572 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-597765 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-597962 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-598162 util-scheduler-8620 DEBUG Running task: 4720 / 0x46620a0
Jul 07 21:04:52-598575 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:52-598813 util-scheduler-8620 DEBUG Adding task: 4726 / 0x4662248
Jul 07 21:04:52-599069 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-599265 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-599457 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-599647 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-599837 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-600026 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-600218 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-600407 util-scheduler-8620 DEBUG Running task: 4726 / 0x4662248
Jul 07 21:04:52-600618 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:52-600819 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:52-601042 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:52-601263 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:52-601465 util-scheduler-8620 DEBUG Adding task: 4727 / 0x46620a0
Jul 07 21:04:52-601652 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:52-601858 util-scheduler-8620 DEBUG Adding task: 4728 / 0x46620a0
Jul 07 21:04:52-602100 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:52-602293 util-scheduler-8620 DEBUG Checking readiness of task: 4727 / 0x46620a0
Jul 07 21:04:52-602486 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:52-602675 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:52-602864 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:52-603053 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:52-603248 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:52-603437 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:52-603627 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:52-603830 util-scheduler-8620 DEBUG Running task: 4727 / 0x46620a0
Jul 07 21:04:52-604016 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:52-604193 util-8620 DEBUG process_notify is running
Jul 07 21:04:52-604366 util-8620 DEBUG client_notify is running
Jul 07 21:04:52-604553 util-scheduler-8620 DEBUG Canceling task: 4724 / 0x6146380
Jul 07 21:04:52-604782 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:52-605000 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:52-605254 cadet-p2p-8620 DEBUG Checking 0x5295748 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:52-605491 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:52-605670 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:52-605857 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:52-606142 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:52-606337 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:52-606518 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:52-606706 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:52-606895 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:52-607073 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:52-607256 util-scheduler-8620 DEBUG Canceling task: 4721 / 0x6146c10
Jul 07 21:04:52-607468 util-scheduler-8620 DEBUG Adding task: 4729 / 0x6146c10
Jul 07 21:04:52-607717 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:52-607888 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:52-608068 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:52-608268 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:52-608444 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:52-608619 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:52-608816 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:52-609021 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:52-609225 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:52-609405 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:52-609597 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:52-609835 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:57-506198 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:57-506583 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:57-506814 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:57-507594 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:57-508034 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:57-508235 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:57-508427 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:57-508617 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:57-508812 util-scheduler-8620 DEBUG Running task: 4723 / 0x52cbfb8
Jul 07 21:04:57-509052 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:04:57-509337 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:04:57-509546 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:04:57-509767 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:04:57-510036 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:04:57-510353 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:04:57-510537 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:04:57-510758 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:04:57-511050 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:04:57-511252 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:04:57-511491 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:04:57-511699 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:04:57-512022 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:04:57-512223 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:04:57-512449 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:04:57-512634 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:04:57-512810 cadet-con-8620 DEBUG  sendable
Jul 07 21:04:57-513018 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:04:57-513256 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:04:57-513484 util-scheduler-8620 DEBUG Adding task: 4730 / 0x6146380
Jul 07 21:04:57-513666 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:04:57-513872 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:57-514049 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:04:57-514225 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:04:57-514463 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:04:57-514661 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:04:57-514838 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:04:57-515036 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:57-515283 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:04:57-515481 util-scheduler-8620 DEBUG Adding task: 4731 / 0x52cbfb8
Jul 07 21:04:57-515747 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:57-515942 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:57-516133 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:57-516322 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:57-516512 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:57-516702 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:57-516892 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:57-517081 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:57-517290 util-scheduler-8620 DEBUG Running task: 4730 / 0x6146380
Jul 07 21:04:57-517500 util-scheduler-8620 DEBUG Adding task: 4732 / 0x6146380
Jul 07 21:04:57-517723 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:04:57-517927 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:57-518170 util-scheduler-8620 DEBUG Adding task: 4733 / 0x46620a0
Jul 07 21:04:57-518416 util-scheduler-8620 DEBUG Checking readiness of task: 4733 / 0x46620a0
Jul 07 21:04:57-518610 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:57-518801 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:57-518990 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:57-519181 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:57-519370 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:57-519562 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:57-519751 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:57-519940 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:57-520132 util-scheduler-8620 DEBUG Running task: 4733 / 0x46620a0
Jul 07 21:04:57-520318 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:57-520496 util-8620 DEBUG process_notify is running
Jul 07 21:04:57-520670 util-8620 DEBUG client_notify is running
Jul 07 21:04:57-520848 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:04:57-521045 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:57-521257 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:04:57-521516 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:04:58-776690 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:58-777037 util-scheduler-8620 DEBUG Checking readiness of task: 4673 / 0x465ee60
Jul 07 21:04:58-777268 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:58-777478 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:58-777670 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:58-777864 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:58-778054 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:58-778245 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:58-778441 util-scheduler-8620 DEBUG Running task: 4673 / 0x465ee60
Jul 07 21:04:58-778865 util-8620 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ee60)!
Jul 07 21:04:58-779126 util-scheduler-8620 DEBUG Adding task: 4734 / 0x465f008
Jul 07 21:04:58-779406 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:58-779599 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:58-779792 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:58-779984 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:58-780175 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:58-780365 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:58-780558 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:58-780759 util-scheduler-8620 DEBUG Running task: 4734 / 0x465f008
Jul 07 21:04:58-780954 util-8620 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:04:58-781223 nse-api-8620 DEBUG Received information about peer `WAKN' from peerinfo database
Jul 07 21:04:58-781526 cadet-hll-8620 DEBUG  hello for WAKN (90 bytes), expires on Tue Jul 08 09:04:58 2014
Jul 07 21:04:58-781755 cadet-p2p-8620 DEBUG set hello for WAKN
Jul 07 21:04:58-782055 cadet-p2p-8620 DEBUG  merge into 0x6208d18 (90 bytes)
Jul 07 21:04:58-782250 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:58-782464 util-scheduler-8620 DEBUG Adding task: 4735 / 0x465ee60
Jul 07 21:04:58-785549 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:04:58-785914 util-scheduler-8620 DEBUG Checking readiness of task: 4728 / 0x46620a0
Jul 07 21:04:58-786114 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:58-786306 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:58-786499 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:58-786691 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:58-786882 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:58-787073 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:58-787275 util-scheduler-8620 DEBUG Running task: 4728 / 0x46620a0
Jul 07 21:04:58-787701 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:04:58-788075 util-scheduler-8620 DEBUG Adding task: 4736 / 0x4662248
Jul 07 21:04:58-788360 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:04:58-788556 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:58-788747 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:58-788938 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:58-789129 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:58-789348 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:58-789537 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:58-789729 util-scheduler-8620 DEBUG Running task: 4736 / 0x4662248
Jul 07 21:04:58-789920 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:04:58-790121 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:04:58-790356 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:04:58-790563 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:04:58-790771 util-scheduler-8620 DEBUG Adding task: 4737 / 0x46620a0
Jul 07 21:04:58-790958 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:04:58-791164 util-scheduler-8620 DEBUG Adding task: 4738 / 0x46620a0
Jul 07 21:04:58-791408 util-scheduler-8620 DEBUG Checking readiness of task: 4738 / 0x46620a0
Jul 07 21:04:58-791605 util-scheduler-8620 DEBUG Checking readiness of task: 4737 / 0x46620a0
Jul 07 21:04:58-791797 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:04:58-791987 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:04:58-792179 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:04:58-792368 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:04:58-792557 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:04:58-792746 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:04:58-792936 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:04:58-793128 util-scheduler-8620 DEBUG Running task: 4737 / 0x46620a0
Jul 07 21:04:58-793340 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:04:58-793520 util-8620 DEBUG process_notify is running
Jul 07 21:04:58-793693 util-8620 DEBUG client_notify is running
Jul 07 21:04:58-793881 util-scheduler-8620 DEBUG Canceling task: 4732 / 0x6146380
Jul 07 21:04:58-794110 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:04:58-794333 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:04:58-794573 cadet-p2p-8620 DEBUG Checking 0x6207a80 towards 0V7ADHDH (->V8XX)
Jul 07 21:04:58-794809 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:04:58-794988 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:04:58-795179 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:04:58-795465 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:04:58-795691 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:04:58-795874 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:04:58-796063 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:04:58-796253 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:04:58-796431 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:04:58-796615 util-scheduler-8620 DEBUG Canceling task: 4729 / 0x6146c10
Jul 07 21:04:58-796828 util-scheduler-8620 DEBUG Adding task: 4739 / 0x6146c10
Jul 07 21:04:58-797078 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:04:58-797278 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:04:58-797462 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:04:58-797664 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:04:58-797841 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:04:58-798014 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:04:58-798213 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:04:58-798419 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:04:58-798602 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:04:58-798783 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:04:58-798973 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:04:58-799226 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:05:02-519356 util-scheduler-8620 DEBUG Checking readiness of task: 4738 / 0x46620a0
Jul 07 21:05:02-519737 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:02-520408 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:02-520612 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:02-520868 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:02-521083 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:02-521293 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:02-521486 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:02-521679 util-scheduler-8620 DEBUG Running task: 4731 / 0x52cbfb8
Jul 07 21:05:02-521915 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:05:02-522172 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:05:02-522380 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:05:02-522583 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:05:02-522785 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:05:02-523033 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:05:02-523214 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:05:02-523435 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:05:02-523725 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:05:02-523922 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:05:02-524159 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:05:02-524367 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:05:02-524689 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:05:02-524891 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:05:02-525141 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:05:02-525347 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:05:02-525523 cadet-con-8620 DEBUG  sendable
Jul 07 21:05:02-525732 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:05:02-525950 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:05:02-526174 util-scheduler-8620 DEBUG Adding task: 4740 / 0x6146380
Jul 07 21:05:02-526354 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:05:02-526583 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:05:02-526762 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:05:02-526938 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:05:02-527177 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:05:02-527374 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:05:02-527590 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:05:02-527841 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:05:02-528087 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:05:02-528286 util-scheduler-8620 DEBUG Adding task: 4741 / 0x52cbfb8
Jul 07 21:05:02-528544 util-scheduler-8620 DEBUG Checking readiness of task: 4738 / 0x46620a0
Jul 07 21:05:02-528739 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:02-528929 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:02-529118 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:02-529330 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:02-529521 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:02-529710 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:02-529900 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:02-530089 util-scheduler-8620 DEBUG Running task: 4740 / 0x6146380
Jul 07 21:05:02-530296 util-scheduler-8620 DEBUG Adding task: 4742 / 0x6146380
Jul 07 21:05:02-530520 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:05:02-530724 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:05:02-530933 util-scheduler-8620 DEBUG Adding task: 4743 / 0x46620a0
Jul 07 21:05:02-531178 util-scheduler-8620 DEBUG Checking readiness of task: 4743 / 0x46620a0
Jul 07 21:05:02-531371 util-scheduler-8620 DEBUG Checking readiness of task: 4738 / 0x46620a0
Jul 07 21:05:02-531562 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:02-531751 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:02-531942 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:02-532131 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:02-532322 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:02-532510 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:02-532700 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:02-532891 util-scheduler-8620 DEBUG Running task: 4743 / 0x46620a0
Jul 07 21:05:02-533077 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:05:02-533276 util-8620 DEBUG process_notify is running
Jul 07 21:05:02-533450 util-8620 DEBUG client_notify is running
Jul 07 21:05:02-533630 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:05:02-533826 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:05:02-534018 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:05:02-534274 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:05:03-116376 util-scheduler-8620 DEBUG Checking readiness of task: 4738 / 0x46620a0
Jul 07 21:05:03-116721 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:03-116918 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:03-117110 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:03-117329 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:03-117524 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:03-117719 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:03-117910 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:03-118132 util-scheduler-8620 DEBUG Running task: 4738 / 0x46620a0
Jul 07 21:05:03-118551 util-8620 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)!
Jul 07 21:05:03-118800 util-scheduler-8620 DEBUG Adding task: 4744 / 0x4662248
Jul 07 21:05:03-119072 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:03-119265 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:03-119456 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:03-119647 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:03-119837 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:03-120025 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:03-120218 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:03-120409 util-scheduler-8620 DEBUG Running task: 4744 / 0x4662248
Jul 07 21:05:03-120599 util-8620 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:05:03-120799 core-api-8620 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:05:03-121027 core-api-8620 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:05:03-121254 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:05:03-121463 util-scheduler-8620 DEBUG Adding task: 4745 / 0x46620a0
Jul 07 21:05:03-121651 util-8620 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:03-121859 util-scheduler-8620 DEBUG Adding task: 4746 / 0x46620a0
Jul 07 21:05:03-122101 util-scheduler-8620 DEBUG Checking readiness of task: 4746 / 0x46620a0
Jul 07 21:05:03-122296 util-scheduler-8620 DEBUG Checking readiness of task: 4745 / 0x46620a0
Jul 07 21:05:03-122490 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:03-122680 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:03-122871 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:03-123062 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:03-123251 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:03-123442 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:03-123630 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:03-123822 util-scheduler-8620 DEBUG Running task: 4745 / 0x46620a0
Jul 07 21:05:03-124006 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:05:03-124186 util-8620 DEBUG process_notify is running
Jul 07 21:05:03-124358 util-8620 DEBUG client_notify is running
Jul 07 21:05:03-124547 util-scheduler-8620 DEBUG Canceling task: 4742 / 0x6146380
Jul 07 21:05:03-124771 core-api-8620 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:05:03-124992 cadet-p2p-8620 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:05:03-125251 cadet-p2p-8620 DEBUG Checking 0x620ae60 towards 0V7ADHDH (->V8XX)
Jul 07 21:05:03-125489 cadet-p2p-8620 DEBUG   on connection 0V7ADHDH (->V8XX) FWD
Jul 07 21:05:03-125669 cadet-p2p-8620 DEBUG   size 196 ok
Jul 07 21:05:03-125859 cadet-p2p-8620 DEBUG   raw {                KX}
Jul 07 21:05:03-126142 cadet-p2p-8620 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD (size 196)
Jul 07 21:05:03-126338 cadet-p2p-8620 DEBUG  calling callback
Jul 07 21:05:03-126530 cadet-con-8620 DEBUG connection message_sent
Jul 07 21:05:03-126719 cadet-con-8620 DEBUG  sent FWD {                KX}
Jul 07 21:05:03-126907 cadet-con-8620 DEBUG  C_P- 0x6146c10 1
Jul 07 21:05:03-127086 cadet-con-8620 DEBUG Connection FWD reset timeout
Jul 07 21:05:03-127270 util-scheduler-8620 DEBUG Canceling task: 4739 / 0x6146c10
Jul 07 21:05:03-127482 util-scheduler-8620 DEBUG Adding task: 4747 / 0x6146c10
Jul 07 21:05:03-127730 cadet-con-8620 DEBUG next keepalive in 5 m
Jul 07 21:05:03-127921 cadet-con-8620 DEBUG !  message sent!
Jul 07 21:05:03-128103 cadet-p2p-8620 DEBUG   return 196
Jul 07 21:05:03-128303 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:05:03-128479 cadet-p2p-8620 DEBUG QQQ  queue length: 0
Jul 07 21:05:03-128653 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:05:03-128852 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:05:03-129057 core-api-8620 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:05:03-129263 core-api-8620 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:05:03-129442 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:05:03-129633 util-8620 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:05:03-129881 util-8620 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:05:07-532853 util-scheduler-8620 DEBUG Checking readiness of task: 4746 / 0x46620a0
Jul 07 21:05:07-533263 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:07-533809 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:07-534313 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:07-534515 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:07-534709 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:07-534899 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:07-535090 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:07-535284 util-scheduler-8620 DEBUG Running task: 4741 / 0x52cbfb8
Jul 07 21:05:07-535524 cadet-tun-8620 INFO Re-key Tunnel V8XX
Jul 07 21:05:07-535783 cadet-tun-8620 DEBUG  kx started 17 m ago
Jul 07 21:05:07-535990 cadet-tun-8620 INFO ===> EPHM for V8XX
Jul 07 21:05:07-536191 cadet-tun-8620 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:05:07-536394 cadet-tun-8620 DEBUG tunnel_get_connection V8XX
Jul 07 21:05:07-536630 cadet-tun-8620 DEBUG   connection 0V7ADHDH (->V8XX): 3
Jul 07 21:05:07-536812 cadet-tun-8620 DEBUG     q_n 0, 
Jul 07 21:05:07-537034 cadet-tun-8620 DEBUG  selected: connection 0V7ADHDH (->V8XX)
Jul 07 21:05:07-537360 cadet-con-8620 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (196 bytes)
Jul 07 21:05:07-537562 cadet-con-8620 DEBUG   C_P+ 0x6146c10 0
Jul 07 21:05:07-537800 cadet-con-8620 DEBUG  get next hop 0V7ADHDH (->V8XX) [0/2]
Jul 07 21:05:07-538008 cadet-con-8620 DEBUG   ID: V8XX (4)
Jul 07 21:05:07-538326 cadet-p2p-8620 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection 0V7ADHDH (->V8XX) (0x6146c10) FWD towards V8XX (size 196)
Jul 07 21:05:07-538528 cadet-p2p-8620 DEBUG priority 0
Jul 07 21:05:07-538752 cadet-con-8620 DEBUG  checking sendability of FWD traffic on 0V7ADHDH (->V8XX)
Jul 07 21:05:07-538936 cadet-con-8620 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:05:07-539112 cadet-con-8620 DEBUG  sendable
Jul 07 21:05:07-539319 cadet-p2p-8620 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:05:07-539535 core-api-8620 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:05:07-539761 util-scheduler-8620 DEBUG Adding task: 4748 / 0x6146380
Jul 07 21:05:07-539941 core-api-8620 DEBUG Transmission request added to queue
Jul 07 21:05:07-540147 cadet-p2p-8620 DEBUG QQQ Message queue towards V8XX
Jul 07 21:05:07-540325 cadet-p2p-8620 DEBUG QQQ  queue length: 1
Jul 07 21:05:07-540500 cadet-p2p-8620 DEBUG QQQ  core tmt rdy: 0x61463ac
Jul 07 21:05:07-540737 cadet-p2p-8620 DEBUG QQQ  - {                KX} FWD on 0V7ADHDH (->V8XX)
Jul 07 21:05:07-540935 cadet-p2p-8620 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:05:07-541113 cadet-p2p-8620 DEBUG QQQ    size: 196 bytes
Jul 07 21:05:07-541333 cadet-p2p-8620 DEBUG QQQ End queue towards V8XX
Jul 07 21:05:07-541579 cadet-tun-8620 DEBUG   next call in 5 s
Jul 07 21:05:07-541778 util-scheduler-8620 DEBUG Adding task: 4749 / 0x52cbfb8
Jul 07 21:05:07-542075 util-scheduler-8620 DEBUG Checking readiness of task: 4746 / 0x46620a0
Jul 07 21:05:07-542271 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:07-542463 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:07-542653 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:07-542843 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:07-543035 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:07-543224 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:07-543412 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:07-543601 util-scheduler-8620 DEBUG Running task: 4748 / 0x6146380
Jul 07 21:05:07-543811 util-scheduler-8620 DEBUG Adding task: 4750 / 0x6146380
Jul 07 21:05:07-544034 core-api-8620 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:05:07-544240 util-8620 DEBUG Scheduling transmission (0x46620a0).
Jul 07 21:05:07-544449 util-scheduler-8620 DEBUG Adding task: 4751 / 0x46620a0
Jul 07 21:05:07-544694 util-scheduler-8620 DEBUG Checking readiness of task: 4751 / 0x46620a0
Jul 07 21:05:07-544889 util-scheduler-8620 DEBUG Checking readiness of task: 4746 / 0x46620a0
Jul 07 21:05:07-545080 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:07-545290 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:07-545481 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:07-545671 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:07-545863 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:07-546052 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:07-546241 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:07-546433 util-scheduler-8620 DEBUG Running task: 4751 / 0x46620a0
Jul 07 21:05:07-546619 util-8620 DEBUG transmit_ready running (0x46620a0).
Jul 07 21:05:07-546799 util-8620 DEBUG process_notify is running
Jul 07 21:05:07-546972 util-8620 DEBUG client_notify is running
Jul 07 21:05:07-547151 core-api-8620 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:05:07-547352 core-api-8620 DEBUG Request queue empty, not processing queue
Jul 07 21:05:07-547544 util-8620 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:05:07-547801 util-8620 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x46620a0)
Jul 07 21:05:07-760871 util-scheduler-8620 DEBUG Checking readiness of task: 4746 / 0x46620a0
Jul 07 21:05:07-761217 util-scheduler-8620 DEBUG Checking readiness of task: 4735 / 0x465ee60
Jul 07 21:05:07-761416 util-scheduler-8620 DEBUG Checking readiness of task: 4554 / 0x4663d68
Jul 07 21:05:07-761608 util-scheduler-8620 DEBUG Checking readiness of task: 4196 / 0x4d5c418
Jul 07 21:05:07-761800 util-scheduler-8620 DEBUG Checking readiness of task: 3879 / 0x4665be0
Jul 07 21:05:07-761992 util-scheduler-8620 DEBUG Checking readiness of task: 41 / 0x4d66008
Jul 07 21:05:07-762182 util-scheduler-8620 DEBUG Checking readiness of task: 39 / 0x4d5ee10
Jul 07 21:05:07-762372 util-scheduler-8620 DEBUG Checking readiness of task: 37 / 0x45515e0
Jul 07 21:05:07-762564 util-scheduler-8620 DEBUG Running task: 4641 / 0x5ad0060
Jul 07 21:05:07-764635 cadet-8620 ERROR Assertion failed at gnunet-service-cadet_peer.c:1949.
Jul 07 21:05:09-482840 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 21:05:09-533314 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 21:05:09-543909 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/core.conf'
Jul 07 21:05:09-545958 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-558376 util-8627 DEBUG Config section `core'
Jul 07 21:05:09-563092 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-567297 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-569088 util-8627 DEBUG Config value BINARY="gnunet-service-core"
Jul 07 21:05:09-569578 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-569829 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-570085 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-core.sock"
Jul 07 21:05:09-570336 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-570591 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-572121 util-8627 DEBUG Config value USE_EPHEMERAL_KEYS="YES"
Jul 07 21:05:09-573381 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-575996 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 21:05:09-576370 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 21:05:09-576825 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/namestore.conf'
Jul 07 21:05:09-577262 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-577584 util-8627 DEBUG Config section `namestore'
Jul 07 21:05:09-577801 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-578680 util-8627 DEBUG Config value USER_SERVICE="YES"
Jul 07 21:05:09-578951 util-8627 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-namestore.sock"
Jul 07 21:05:09-579208 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-579455 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-579720 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-579970 util-8627 DEBUG Config value BINARY="gnunet-service-namestore"
Jul 07 21:05:09-580221 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-580470 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-580721 util-8627 DEBUG Config value DATABASE="sqlite"
Jul 07 21:05:09-580982 util-8627 DEBUG Config section `namestore-sqlite'
Jul 07 21:05:09-581217 util-8627 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/namestore/sqlite.db"
Jul 07 21:05:09-581502 util-8627 DEBUG Config section `namestore-postgres'
Jul 07 21:05:09-581718 util-8627 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 21:05:09-581982 util-8627 DEBUG Config value TEMPORARY_TABLE="NO"
Jul 07 21:05:09-582240 util-8627 DEBUG Config section `uri'
Jul 07 21:05:09-582449 util-8627 DEBUG Config value gns="gnunet-namestore"
Jul 07 21:05:09-582715 util-8627 DEBUG Config section `fcfsd'
Jul 07 21:05:09-582943 util-8627 DEBUG Config value BINARY="gnunet-namestore-fcfsd"
Jul 07 21:05:09-583194 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-583550 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-fcfsd.sock"
Jul 07 21:05:09-583840 util-8627 DEBUG Config value HTTPPORT="18080"
Jul 07 21:05:09-584249 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-584469 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 21:05:09-584667 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 21:05:09-584934 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/vpn.conf'
Jul 07 21:05:09-585118 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-585345 util-8627 DEBUG Config section `vpn'
Jul 07 21:05:09-585552 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-585815 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-586056 util-8627 DEBUG Config value BINARY="gnunet-service-vpn"
Jul 07 21:05:09-586297 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-586538 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-586790 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-vpn.sock"
Jul 07 21:05:09-587049 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-587310 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-587569 util-8627 DEBUG Config value IPV6ADDR="1234::1"
Jul 07 21:05:09-587811 util-8627 DEBUG Config value IPV6PREFIX="32"
Jul 07 21:05:09-588058 util-8627 DEBUG Config value IPV4ADDR="10.11.10.1"
Jul 07 21:05:09-588306 util-8627 DEBUG Config value IPV4MASK="255.255.0.0"
Jul 07 21:05:09-588555 util-8627 DEBUG Config value VIRTDNS="10.11.10.2"
Jul 07 21:05:09-588801 util-8627 DEBUG Config value VIRTDNS6="1234::17"
Jul 07 21:05:09-589050 util-8627 DEBUG Config value IFNAME="vpn-gnunet"
Jul 07 21:05:09-589303 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-589526 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 21:05:09-589723 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 21:05:09-590010 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/arm.conf'
Jul 07 21:05:09-590288 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-590508 util-8627 DEBUG Config section `arm'
Jul 07 21:05:09-590732 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-590985 util-8627 DEBUG Config value BINARY="gnunet-service-arm"
Jul 07 21:05:09-591226 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-591478 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-591741 util-8627 DEBUG Config value DEFAULTSERVICES="topology hostlist dht nse cadet fs revocation"
Jul 07 21:05:09-592016 util-8627 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-arm.sock"
Jul 07 21:05:09-592265 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-592508 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-593904 util-8627 DEBUG Config value GLOBAL_PREFIX=""
Jul 07 21:05:09-594648 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-594867 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 21:05:09-595065 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 21:05:09-595331 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/set.conf'
Jul 07 21:05:09-595515 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-595720 util-8627 DEBUG Config section `set'
Jul 07 21:05:09-595927 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-596192 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-596441 util-8627 DEBUG Config value BINARY="gnunet-service-set"
Jul 07 21:05:09-596682 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-596924 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-597176 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-set.sock"
Jul 07 21:05:09-597455 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-597700 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-597922 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-598133 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 21:05:09-598329 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 21:05:09-598594 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/cadet.conf'
Jul 07 21:05:09-598777 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-598983 util-8627 DEBUG Config section `cadet'
Jul 07 21:05:09-599190 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-599472 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-599716 util-8627 DEBUG Config value BINARY="gnunet-service-cadet"
Jul 07 21:05:09-599961 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-600205 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-600458 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock"
Jul 07 21:05:09-600708 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-600969 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-601254 util-8627 DEBUG Config value REFRESH_CONNECTION_TIME="5 min"
Jul 07 21:05:09-601505 util-8627 DEBUG Config value ID_ANNOUNCE_TIME="1 h"
Jul 07 21:05:09-601753 util-8627 DEBUG Config value CONNECT_TIMEOUT="30 s"
Jul 07 21:05:09-602046 util-8627 DEBUG Config value DEFAULT_TTL="64"
Jul 07 21:05:09-602303 util-8627 DEBUG Config value DHT_REPLICATION_LEVEL="3"
Jul 07 21:05:09-602555 util-8627 DEBUG Config value MAX_TUNNELS="1000"
Jul 07 21:05:09-602804 util-8627 DEBUG Config value MAX_CONNECTIONS="1000"
Jul 07 21:05:09-603055 util-8627 DEBUG Config value MAX_MSGS_QUEUE="10000"
Jul 07 21:05:09-603307 util-8627 DEBUG Config value MAX_PEERS="1000"
Jul 07 21:05:09-603562 util-8627 DEBUG Config value REKEY_PERIOD="12 h"
Jul 07 21:05:09-603783 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-603994 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 21:05:09-604191 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 21:05:09-604459 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/peerinfo.conf'
Jul 07 21:05:09-604643 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-604858 util-8627 DEBUG Config section `peerinfo'
Jul 07 21:05:09-605066 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-605366 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-605612 util-8627 DEBUG Config value BINARY="gnunet-service-peerinfo"
Jul 07 21:05:09-605858 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-606102 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-606359 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock"
Jul 07 21:05:09-606610 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-606856 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-607237 util-8627 DEBUG Config value HOSTS="$GNUNET_DATA_HOME/peerinfo/hosts/"
Jul 07 21:05:09-607536 util-8627 DEBUG Config value NO_IO="NO"
Jul 07 21:05:09-607808 util-8627 DEBUG Config value USE_INCLUDED_HELLOS="YES"
Jul 07 21:05:09-608072 util-8627 DEBUG Config section `uri'
Jul 07 21:05:09-608280 util-8627 DEBUG Config value hello="gnunet-peerinfo"
Jul 07 21:05:09-608529 util-8627 DEBUG Config value friend-hello="gnunet-peerinfo"
Jul 07 21:05:09-608748 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-608961 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 21:05:09-609159 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 21:05:09-609477 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/transport.conf'
Jul 07 21:05:09-609661 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-609869 util-8627 DEBUG Config section `transport'
Jul 07 21:05:09-610076 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-610345 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-610592 util-8627 DEBUG Config value BINARY="gnunet-service-transport"
Jul 07 21:05:09-610866 util-8627 DEBUG Config value NEIGHBOUR_LIMIT="50"
Jul 07 21:05:09-611113 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-611370 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-611619 util-8627 DEBUG Config value PLUGINS="tcp udp"
Jul 07 21:05:09-611874 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock"
Jul 07 21:05:09-612136 util-8627 DEBUG Config value BLACKLIST_FILE="$GNUNET_CONFIG_HOME/transport/blacklist"
Jul 07 21:05:09-612389 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-612638 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-613162 util-8627 DEBUG Config section `transport-unix'
Jul 07 21:05:09-613455 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-transport-plugin-unix.sock"
Jul 07 21:05:09-613754 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-614015 util-8627 DEBUG Config section `transport-tcp'
Jul 07 21:05:09-614241 util-8627 DEBUG Config value PORT="2086"
Jul 07 21:05:09-614513 util-8627 DEBUG Config value ADVERTISED_PORT="2086"
Jul 07 21:05:09-614761 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-615036 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-615303 util-8627 DEBUG Config value TIMEOUT="5 s"
Jul 07 21:05:09-615616 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-616782 util-8627 DEBUG Config section `transport-udp'
Jul 07 21:05:09-617016 util-8627 DEBUG Config value PORT="2086"
Jul 07 21:05:09-617327 util-8627 DEBUG Config value BROADCAST="YES"
Jul 07 21:05:09-617576 util-8627 DEBUG Config value BROADCAST_RECEIVE="YES"
Jul 07 21:05:09-617834 util-8627 DEBUG Config value BROADCAST_INTERVAL="30 s"
Jul 07 21:05:09-618093 util-8627 DEBUG Config value MAX_BPS="1000000"
Jul 07 21:05:09-618343 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-618626 util-8627 DEBUG Config section `transport-http_client'
Jul 07 21:05:09-618838 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-619130 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-619618 util-8627 DEBUG Config section `transport-http_server'
Jul 07 21:05:09-619856 util-8627 DEBUG Config value PORT="1080"
Jul 07 21:05:09-620165 util-8627 DEBUG Config value ADVERTISED_PORT="1080"
Jul 07 21:05:09-620418 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-620686 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-620968 util-8627 DEBUG Config section `transport-https_client'
Jul 07 21:05:09-621222 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-621551 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-622065 util-8627 DEBUG Config section `transport-https_server'
Jul 07 21:05:09-622386 util-8627 DEBUG Config value PORT="4433"
Jul 07 21:05:09-622727 util-8627 DEBUG Config value ADVERTISED_PORT="4433"
Jul 07 21:05:09-622981 util-8627 DEBUG Config value CRYPTO_INIT="NORMAL"
Jul 07 21:05:09-623238 util-8627 DEBUG Config value KEY_FILE="$GNUNET_DATA_HOME/transport/https.key"
Jul 07 21:05:09-623506 util-8627 DEBUG Config value CERT_FILE="$GNUNET_DATA_HOME/transport/https.cert"
Jul 07 21:05:09-623766 util-8627 DEBUG Config value MAX_CONNECTIONS="128"
Jul 07 21:05:09-624024 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-624292 util-8627 DEBUG Config section `transport-wlan'
Jul 07 21:05:09-624519 util-8627 DEBUG Config value INTERFACE="mon0"
Jul 07 21:05:09-624855 util-8627 DEBUG Config value TESTMODE="0"
Jul 07 21:05:09-625113 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-625404 util-8627 DEBUG Config section `transport-bluetooth'
Jul 07 21:05:09-625631 util-8627 DEBUG Config value INTERFACE="hci0"
Jul 07 21:05:09-625973 util-8627 DEBUG Config value TESTMODE="0"
Jul 07 21:05:09-626225 util-8627 DEBUG Config value TESTING_IGNORE_KEYS="ACCEPT_FROM;"
Jul 07 21:05:09-626449 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-626670 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 21:05:09-626866 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 21:05:09-627166 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/ats.conf'
Jul 07 21:05:09-627351 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-627557 util-8627 DEBUG Config section `ats'
Jul 07 21:05:09-627763 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-628053 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-628302 util-8627 DEBUG Config value BINARY="gnunet-service-ats"
Jul 07 21:05:09-628548 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-628788 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-629055 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-ats.sock"
Jul 07 21:05:09-629338 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-629603 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-629879 util-8627 DEBUG Config value MODE="PROPORTIONAL"
Jul 07 21:05:09-630151 util-8627 DEBUG Config value UNSPECIFIED_QUOTA_IN="64 KiB"
Jul 07 21:05:09-630402 util-8627 DEBUG Config value UNSPECIFIED_QUOTA_OUT="64 KiB"
Jul 07 21:05:09-630672 util-8627 DEBUG Config value LOOPBACK_QUOTA_IN="unlimited"
Jul 07 21:05:09-630920 util-8627 DEBUG Config value LOOPBACK_QUOTA_OUT="unlimited"
Jul 07 21:05:09-631186 util-8627 DEBUG Config value LAN_QUOTA_IN="unlimited"
Jul 07 21:05:09-631436 util-8627 DEBUG Config value LAN_QUOTA_OUT="unlimited"
Jul 07 21:05:09-631701 util-8627 DEBUG Config value WAN_QUOTA_IN="64 KiB"
Jul 07 21:05:09-631959 util-8627 DEBUG Config value WAN_QUOTA_OUT="64 KiB"
Jul 07 21:05:09-632224 util-8627 DEBUG Config value WLAN_QUOTA_IN="1 MiB"
Jul 07 21:05:09-632475 util-8627 DEBUG Config value WLAN_QUOTA_OUT="1 MiB"
Jul 07 21:05:09-632744 util-8627 DEBUG Config value BLUETOOTH_QUOTA_IN="128 KiB"
Jul 07 21:05:09-632998 util-8627 DEBUG Config value BLUETOOTH_QUOTA_OUT="128 KiB"
Jul 07 21:05:09-633388 util-8627 DEBUG Config value PROP_PROPORTIONALITY_FACTOR="2.00"
Jul 07 21:05:09-633683 util-8627 DEBUG Config value PROP_STABILITY_FACTOR="1.25"
Jul 07 21:05:09-634076 util-8627 DEBUG Config value MLP_MAX_MIP_GAP="0.025"
Jul 07 21:05:09-634348 util-8627 DEBUG Config value MLP_MAX_LP_MIP_GAP="0.025"
Jul 07 21:05:09-634860 util-8627 DEBUG Config value MLP_DUMP_PROBLEM_ON_FAIL="YES"
Jul 07 21:05:09-635137 util-8627 DEBUG Config value MLP_DUMP_SOLUTION_ON_FAIL="YES"
Jul 07 21:05:09-635426 util-8627 DEBUG Config value RIL_STEP_TIME_MIN="500 ms"
Jul 07 21:05:09-635692 util-8627 DEBUG Config value RIL_STEP_TIME_MAX="1000 ms"
Jul 07 21:05:09-635980 util-8627 DEBUG Config value RIL_ALGORITHM="Q-LEARNING"
Jul 07 21:05:09-636241 util-8627 DEBUG Config value RIL_DISCOUNT_BETA="0.7"
Jul 07 21:05:09-636510 util-8627 DEBUG Config value RIL_GRADIENT_STEP_SIZE="0.3"
Jul 07 21:05:09-636777 util-8627 DEBUG Config value RIL_TRACE_DECAY="0.2"
Jul 07 21:05:09-637044 util-8627 DEBUG Config value RIL_EXPLORE_RATIO="0.1"
Jul 07 21:05:09-637338 util-8627 DEBUG Config value RIL_GLOBAL_REWARD_SHARE="1"
Jul 07 21:05:09-637584 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-637799 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 21:05:09-638000 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 21:05:09-638326 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/exit.conf'
Jul 07 21:05:09-638511 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-638718 util-8627 DEBUG Config section `exit'
Jul 07 21:05:09-638926 util-8627 DEBUG Config value BINARY="gnunet-daemon-exit"
Jul 07 21:05:09-639244 util-8627 DEBUG Config value IPV6ADDR="2001:DB8::1"
Jul 07 21:05:09-639511 util-8627 DEBUG Config value IPV6PREFIX="64"
Jul 07 21:05:09-639822 util-8627 DEBUG Config value IPV4ADDR="169.254.86.1"
Jul 07 21:05:09-640093 util-8627 DEBUG Config value IPV4MASK="255.255.255.0"
Jul 07 21:05:09-640385 util-8627 DEBUG Config value EXIT_RANGE_IPV4_POLICY="0.0.0.0/0:!25;"
Jul 07 21:05:09-640677 util-8627 DEBUG Config value EXIT_RANGE_IPV6_POLICY="::/0:!25;"
Jul 07 21:05:09-640967 util-8627 DEBUG Config value TUN_IFNAME="exit-gnunet"
Jul 07 21:05:09-641370 util-8627 DEBUG Config value EXIT_IFNAME="eth0"
Jul 07 21:05:09-641656 util-8627 DEBUG Config value EXIT_IPV4="NO"
Jul 07 21:05:09-641933 util-8627 DEBUG Config value EXIT_IPV6="NO"
Jul 07 21:05:09-642316 util-8627 DEBUG Config value EXIT_DNS="NO"
Jul 07 21:05:09-642600 util-8627 DEBUG Config value DNS_RESOLVER="8.8.8.8"
Jul 07 21:05:09-642876 util-8627 DEBUG Config value ENABLE_IPV4="YES"
Jul 07 21:05:09-643153 util-8627 DEBUG Config value ENABLE_IPV6="YES"
Jul 07 21:05:09-643469 util-8627 DEBUG Config value MAX_CONNECTIONS="256"
Jul 07 21:05:09-643688 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-643904 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 21:05:09-644101 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 21:05:09-644402 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/testbed.conf'
Jul 07 21:05:09-644586 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-644792 util-8627 DEBUG Config section `testbed'
Jul 07 21:05:09-644999 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-645320 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-645566 util-8627 DEBUG Config value BINARY="gnunet-service-testbed"
Jul 07 21:05:09-645837 util-8627 DEBUG Config value OPERATION_TIMEOUT="30 s"
Jul 07 21:05:09-646235 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-646491 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-646758 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-testbed.sock"
Jul 07 21:05:09-647010 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-647257 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-647572 util-8627 DEBUG Config value MAX_PARALLEL_OPERATIONS="1000"
Jul 07 21:05:09-647826 util-8627 DEBUG Config value MAX_PARALLEL_TOPOLOGY_CONFIG_OPERATIONS="1"
Jul 07 21:05:09-648175 util-8627 DEBUG Config value OVERLAY_TOPOLOGY="NONE"
Jul 07 21:05:09-648669 util-8627 DEBUG Config value MAX_PARALLEL_SERVICE_CONNECTIONS="256"
Jul 07 21:05:09-648972 util-8627 DEBUG Config value CACHE_SIZE="30"
Jul 07 21:05:09-649299 util-8627 DEBUG Config value MAX_OPEN_FDS="512"
Jul 07 21:05:09-649611 util-8627 DEBUG Config value SETUP_TIMEOUT="5 m"
Jul 07 21:05:09-650124 util-8627 DEBUG Config value SHARED_SERVICES=""
Jul 07 21:05:09-650397 util-8627 DEBUG Config section `testbed-logger'
Jul 07 21:05:09-650605 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-650902 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-651151 util-8627 DEBUG Config value BINARY="gnunet-service-testbed-logger"
Jul 07 21:05:09-651420 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-gnunet-testbed-logger.sock"
Jul 07 21:05:09-651673 util-8627 DEBUG Config value DIR="/tmp"
Jul 07 21:05:09-651919 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-652170 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-652444 util-8627 DEBUG Config section `testbed-barrier'
Jul 07 21:05:09-652655 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-652959 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-653242 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-testbed-barrier.sock"
Jul 07 21:05:09-653500 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-653750 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-654068 util-8627 DEBUG Config section `testbed-underlay'
Jul 07 21:05:09-654277 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-654579 util-8627 DEBUG Config value BINARY="gnunet-daemon-testbed-underlay"
Jul 07 21:05:09-654884 util-8627 DEBUG Config section `latency-logger'
Jul 07 21:05:09-655093 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-655372 util-8627 DEBUG Config value BINARY="gnunet-daemon-latency-logger"
Jul 07 21:05:09-655625 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-655846 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 21:05:09-656044 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 21:05:09-656320 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/revocation.conf'
Jul 07 21:05:09-656506 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-656713 util-8627 DEBUG Config section `revocation'
Jul 07 21:05:09-656920 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-657277 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-657532 util-8627 DEBUG Config value BINARY="gnunet-service-revocation"
Jul 07 21:05:09-657780 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-658074 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-658335 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-revocation.unix"
Jul 07 21:05:09-658590 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-658838 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-659160 util-8627 DEBUG Config value WORKBITS="25"
Jul 07 21:05:09-659423 util-8627 DEBUG Config value DATABASE="$GNUNET_DATA_HOME/revocation.dat"
Jul 07 21:05:09-659646 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-659857 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 21:05:09-660054 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 21:05:09-660320 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/topology.conf'
Jul 07 21:05:09-660504 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-660711 util-8627 DEBUG Config section `topology'
Jul 07 21:05:09-660919 util-8627 DEBUG Config value MINIMUM-FRIENDS="0"
Jul 07 21:05:09-661241 util-8627 DEBUG Config value FRIENDS-ONLY="NO"
Jul 07 21:05:09-661490 util-8627 DEBUG Config value TARGET-CONNECTION-COUNT="16"
Jul 07 21:05:09-661741 util-8627 DEBUG Config value FRIENDS="$GNUNET_CONFIG_HOME/topology/friends.txt"
Jul 07 21:05:09-661994 util-8627 DEBUG Config value BINARY="gnunet-daemon-topology"
Jul 07 21:05:09-662219 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-662428 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 21:05:09-662624 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 21:05:09-662900 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/fs.conf'
Jul 07 21:05:09-663084 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-663288 util-8627 DEBUG Config section `fs'
Jul 07 21:05:09-663495 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-663784 util-8627 DEBUG Config value INDEXDB="$GNUNET_DATA_HOME/fs/idxinfo.lst"
Jul 07 21:05:09-664062 util-8627 DEBUG Config value RESPECT="$GNUNET_DATA_HOME/fs/credit/"
Jul 07 21:05:09-664320 util-8627 DEBUG Config value STATE_DIR="$GNUNET_DATA_HOME/fs/persistence/"
Jul 07 21:05:09-664569 util-8627 DEBUG Config value UPDATE_DIR="$GNUNET_DATA_HOME/fs/updates/"
Jul 07 21:05:09-664827 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-665070 util-8627 DEBUG Config value BINARY="gnunet-service-fs"
Jul 07 21:05:09-665349 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-665594 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-665867 util-8627 DEBUG Config value DELAY="YES"
Jul 07 21:05:09-666137 util-8627 DEBUG Config value CONTENT_CACHING="YES"
Jul 07 21:05:09-666443 util-8627 DEBUG Config value CONTENT_PUSHING="YES"
Jul 07 21:05:09-666709 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-fs.sock"
Jul 07 21:05:09-667004 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-667283 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-667581 util-8627 DEBUG Config value MAX_PENDING_REQUESTS="65536"
Jul 07 21:05:09-667875 util-8627 DEBUG Config value DATASTORE_QUEUE_SIZE="1024"
Jul 07 21:05:09-668196 util-8627 DEBUG Config value MIN_MIGRATION_DELAY="100 ms"
Jul 07 21:05:09-668478 util-8627 DEBUG Config value EXPECTED_NEIGHBOUR_COUNT="128"
Jul 07 21:05:09-668774 util-8627 DEBUG Config value DISABLE_ANON_TRANSFER="NO"
Jul 07 21:05:09-669138 util-8627 DEBUG Config value MAX_CADET_CLIENTS="128"
Jul 07 21:05:09-669439 util-8627 DEBUG Config section `gnunet-auto-share'
Jul 07 21:05:09-669649 util-8627 DEBUG Config value BINARY="gnunet-auto-share"
Jul 07 21:05:09-669995 util-8627 DEBUG Config value OPTIONS="$GNUNET_DATA_HOME/fs/share/"
Jul 07 21:05:09-670259 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-670477 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 21:05:09-670675 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 21:05:09-670940 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/datacache.conf'
Jul 07 21:05:09-671123 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-671331 util-8627 DEBUG Config section `datacache-postgres'
Jul 07 21:05:09-671544 util-8627 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 21:05:09-671802 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-672012 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 21:05:09-672208 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 21:05:09-672474 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/identity.conf'
Jul 07 21:05:09-672657 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-672864 util-8627 DEBUG Config section `identity'
Jul 07 21:05:09-673071 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-673383 util-8627 DEBUG Config value USER_SERVICE="YES"
Jul 07 21:05:09-673640 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-673894 util-8627 DEBUG Config value BINARY="gnunet-service-identity"
Jul 07 21:05:09-674140 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-674386 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-674645 util-8627 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-identity.unix"
Jul 07 21:05:09-674898 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-675146 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-675429 util-8627 DEBUG Config value EGODIR="$GNUNET_DATA_HOME/identity/egos/"
Jul 07 21:05:09-675720 util-8627 DEBUG Config value SUBSYSTEM_CFG="$GNUNET_CONFIG_HOME/identity/subsystem_defaults.conf"
Jul 07 21:05:09-675946 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-676623 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 21:05:09-676835 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 21:05:09-677108 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/dht.conf'
Jul 07 21:05:09-677323 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-677530 util-8627 DEBUG Config section `dht'
Jul 07 21:05:09-677737 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-678040 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-678281 util-8627 DEBUG Config value BINARY="gnunet-service-dht"
Jul 07 21:05:09-678522 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-678762 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-679005 util-8627 DEBUG Config value BUCKET_SIZE="4"
Jul 07 21:05:09-679252 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock"
Jul 07 21:05:09-679524 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-679768 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-680162 util-8627 DEBUG Config value CACHE_RESULTS="YES"
Jul 07 21:05:09-680434 util-8627 DEBUG Config value DISABLE_TRY_CONNECT="NO"
Jul 07 21:05:09-680699 util-8627 DEBUG Config section `dhtcache'
Jul 07 21:05:09-680906 util-8627 DEBUG Config value DATABASE="heap"
Jul 07 21:05:09-681226 util-8627 DEBUG Config value QUOTA="50 MB"
Jul 07 21:05:09-681517 util-8627 DEBUG Config value DISABLE_BF_RC="NO"
Jul 07 21:05:09-681735 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-681947 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 21:05:09-682144 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 21:05:09-682425 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/testing.conf'
Jul 07 21:05:09-682613 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-682832 util-8627 DEBUG Config section `TESTING'
Jul 07 21:05:09-683057 util-8627 DEBUG Config value CONNECT_TIMEOUT="30 s"
Jul 07 21:05:09-683383 util-8627 DEBUG Config value CONNECT_ATTEMPTS="3"
Jul 07 21:05:09-683648 util-8627 DEBUG Config value MAX_OUTSTANDING_CONNECTIONS="50"
Jul 07 21:05:09-683921 util-8627 DEBUG Config value DELETE_FILES="YES"
Jul 07 21:05:09-684147 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-684357 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 21:05:09-684562 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 21:05:09-684827 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/pt.conf'
Jul 07 21:05:09-685013 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-685244 util-8627 DEBUG Config section `pt'
Jul 07 21:05:09-685454 util-8627 DEBUG Config value BINARY="gnunet-daemon-pt"
Jul 07 21:05:09-685774 util-8627 DEBUG Config value TUNNEL_IPV4="NO"
Jul 07 21:05:09-686039 util-8627 DEBUG Config value TUNNEL_IPV6="NO"
Jul 07 21:05:09-686308 util-8627 DEBUG Config value TUNNEL_DNS="NO"
Jul 07 21:05:09-686534 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-686746 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 21:05:09-686944 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 21:05:09-687212 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/template.conf'
Jul 07 21:05:09-687396 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-687612 util-8627 DEBUG Config section `template'
Jul 07 21:05:09-687822 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-688131 util-8627 DEBUG Config value PORT="9999"
Jul 07 21:05:09-688372 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-688619 util-8627 DEBUG Config value BINARY="gnunet-service-template"
Jul 07 21:05:09-688866 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-689112 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-689418 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-template.sock"
Jul 07 21:05:09-689672 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-689921 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-690273 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-690486 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 21:05:09-690682 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 21:05:09-690962 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/util.conf'
Jul 07 21:05:09-691147 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-691354 util-8627 DEBUG Config section `PATHS'
Jul 07 21:05:09-691728 util-8627 DEBUG Config value GNUNET_HOME="${GNUNET_TEST_HOME:-${HOME:-${USERPROFILE}}}"
Jul 07 21:05:09-692127 util-8627 DEBUG Config value GNUNET_DATA_HOME="${XDG_DATA_HOME:-$GNUNET_HOME/.local/share}/gnunet/"
Jul 07 21:05:09-692426 util-8627 DEBUG Config value GNUNET_CONFIG_HOME="${XDG_CONFIG_HOME:-$GNUNET_HOME/.config}/gnunet/"
Jul 07 21:05:09-692720 util-8627 DEBUG Config value GNUNET_CACHE_HOME="${XDG_CACHE_HOME:-$GNUNET_HOME/.cache}/gnunet/"
Jul 07 21:05:09-693151 util-8627 DEBUG Config value GNUNET_RUNTIME_DIR="${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/"
Jul 07 21:05:09-693501 util-8627 DEBUG Config value GNUNET_USER_RUNTIME_DIR="${TMPDIR:-${TMP:-/tmp}}/gnunet-${USERHOME:-${USER:-user}}-runtime/"
Jul 07 21:05:09-693922 util-8627 DEBUG Config section `PEER'
Jul 07 21:05:09-694136 util-8627 DEBUG Config value PRIVATE_KEY="$GNUNET_DATA_HOME/private_key.ecc"
Jul 07 21:05:09-694475 util-8627 DEBUG Config section `TESTING'
Jul 07 21:05:09-694685 util-8627 DEBUG Config value SPEEDUP_INTERVAL="0 ms"
Jul 07 21:05:09-694937 util-8627 DEBUG Config value SPEEDUP_DELTA="0 ms"
Jul 07 21:05:09-695274 util-8627 DEBUG Config value USE_ABSTRACT_SOCKETS="NO"
Jul 07 21:05:09-695498 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-695714 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 21:05:09-695910 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 21:05:09-696184 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/nat.conf'
Jul 07 21:05:09-696369 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-696576 util-8627 DEBUG Config section `nat'
Jul 07 21:05:09-696798 util-8627 DEBUG Config value BEHIND_NAT="NO"
Jul 07 21:05:09-697133 util-8627 DEBUG Config value PUNCHED_NAT="NO"
Jul 07 21:05:09-697442 util-8627 DEBUG Config value ENABLE_UPNP="NO"
Jul 07 21:05:09-697714 util-8627 DEBUG Config value USE_LOCALADDR="YES"
Jul 07 21:05:09-697988 util-8627 DEBUG Config value USE_HOSTNAME="NO"
Jul 07 21:05:09-698356 util-8627 DEBUG Config value ENABLE_ICMP_CLIENT="NO"
Jul 07 21:05:09-698602 util-8627 DEBUG Config value ENABLE_ICMP_SERVER="NO"
Jul 07 21:05:09-698963 util-8627 DEBUG Config value DISABLEV6="NO"
Jul 07 21:05:09-699238 util-8627 DEBUG Config value RETURN_LOCAL_ADDRESSES="NO"
Jul 07 21:05:09-699528 util-8627 DEBUG Config value HOSTNAME_DNS_FREQUENCY="20 min"
Jul 07 21:05:09-699831 util-8627 DEBUG Config value IFC_SCAN_FREQUENCY="15 min"
Jul 07 21:05:09-700119 util-8627 DEBUG Config value DYNDNS_FREQUENCY="7 min"
Jul 07 21:05:09-700389 util-8627 DEBUG Config section `gnunet-nat-server'
Jul 07 21:05:09-700600 util-8627 DEBUG Config value HOSTNAME="gnunet.org"
Jul 07 21:05:09-700902 util-8627 DEBUG Config value PORT="5724"
Jul 07 21:05:09-701140 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-701405 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 21:05:09-701603 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 21:05:09-701876 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/hostlist.conf'
Jul 07 21:05:09-702061 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-702268 util-8627 DEBUG Config section `hostlist'
Jul 07 21:05:09-702479 util-8627 DEBUG Config value BINARY="gnunet-daemon-hostlist"
Jul 07 21:05:09-702804 util-8627 DEBUG Config value HTTPPORT="8080"
Jul 07 21:05:09-703156 util-8627 DEBUG Config value HOSTLISTFILE="$GNUNET_CONFIG_HOME/hostlist/learned.txt"
Jul 07 21:05:09-703501 util-8627 DEBUG Config value OPTIONS="-b"
Jul 07 21:05:09-703776 util-8627 DEBUG Config value SERVERS="http://v10.gnunet.org/hostlist"
Jul 07 21:05:09-704262 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-704476 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 21:05:09-704673 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 21:05:09-704937 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/regex.conf'
Jul 07 21:05:09-705122 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-705399 util-8627 DEBUG Config section `regex'
Jul 07 21:05:09-705608 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-705941 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-regex.sock"
Jul 07 21:05:09-706190 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-706433 util-8627 DEBUG Config value BINARY="gnunet-service-regex"
Jul 07 21:05:09-706678 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-706923 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-707140 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-707351 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 21:05:09-707562 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 21:05:09-707843 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/dns.conf'
Jul 07 21:05:09-708069 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-708276 util-8627 DEBUG Config section `dns'
Jul 07 21:05:09-708484 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-708786 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-709027 util-8627 DEBUG Config value BINARY="gnunet-service-dns"
Jul 07 21:05:09-709301 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-dns.sock"
Jul 07 21:05:09-709611 util-8627 DEBUG Config value UNIX_MATCH_UID="YES"
Jul 07 21:05:09-709856 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-710189 util-8627 DEBUG Config value IFNAME="gnunet-dns"
Jul 07 21:05:09-710492 util-8627 DEBUG Config value IPV6ADDR="2001:DB8::1"
Jul 07 21:05:09-710737 util-8627 DEBUG Config value IPV6PREFIX="126"
Jul 07 21:05:09-711009 util-8627 DEBUG Config value IPV4ADDR="169.254.1.1"
Jul 07 21:05:09-711258 util-8627 DEBUG Config value IPV4MASK="255.255.0.0"
Jul 07 21:05:09-711595 util-8627 DEBUG Config value DNS_EXIT="8.8.8.8"
Jul 07 21:05:09-711826 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-712039 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 21:05:09-712237 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 21:05:09-712518 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/gns.conf'
Jul 07 21:05:09-712705 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-712912 util-8627 DEBUG Config section `gns'
Jul 07 21:05:09-713119 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-713468 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-713710 util-8627 DEBUG Config value BINARY="gnunet-service-gns"
Jul 07 21:05:09-713959 util-8627 DEBUG Config value UNIXPATH="$GNUNET_USER_RUNTIME_DIR/gnunet-service-gns.sock"
Jul 07 21:05:09-714218 util-8627 DEBUG Config value USER_SERVICE="YES"
Jul 07 21:05:09-714502 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-714784 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-715066 util-8627 DEBUG Config value MAX_PARALLEL_BACKGROUND_QUERIES="1000"
Jul 07 21:05:09-715344 util-8627 DEBUG Config value ZONE_PUBLISH_TIME_WINDOW="4 h"
Jul 07 21:05:09-715666 util-8627 DEBUG Config section `gns-proxy'
Jul 07 21:05:09-715876 util-8627 DEBUG Config value BINARY="gnunet-gns-proxy"
Jul 07 21:05:09-716185 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-716429 util-8627 DEBUG Config value USER_SERVICE="YES"
Jul 07 21:05:09-716707 util-8627 DEBUG Config value PROXY_CACERT="$GNUNET_DATA_HOME/gns/gns_ca_cert.pem"
Jul 07 21:05:09-716975 util-8627 DEBUG Config value PROXY_UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-gns-proxy.sock"
Jul 07 21:05:09-717278 util-8627 DEBUG Config section `dns2gns'
Jul 07 21:05:09-717489 util-8627 DEBUG Config value BINARY="gnunet-dns2gns"
Jul 07 21:05:09-717798 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-718043 util-8627 DEBUG Config value USER_SERVICE="YES"
Jul 07 21:05:09-718315 util-8627 DEBUG Config value OPTIONS="-d 8.8.8.8"
Jul 07 21:05:09-718528 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-718753 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 21:05:09-718951 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 21:05:09-719218 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/namecache.conf'
Jul 07 21:05:09-719403 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-719610 util-8627 DEBUG Config section `namecache'
Jul 07 21:05:09-719818 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-720143 util-8627 DEBUG Config value USER_SERVICE="NO"
Jul 07 21:05:09-720410 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-namecache.sock"
Jul 07 21:05:09-720662 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-720909 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-721173 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-721464 util-8627 DEBUG Config value BINARY="gnunet-service-namecache"
Jul 07 21:05:09-721714 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-721964 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-722215 util-8627 DEBUG Config value DATABASE="sqlite"
Jul 07 21:05:09-722484 util-8627 DEBUG Config section `namecache-sqlite'
Jul 07 21:05:09-722698 util-8627 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/namecache/sqlite.db"
Jul 07 21:05:09-723040 util-8627 DEBUG Config section `namecache-postgres'
Jul 07 21:05:09-723254 util-8627 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 21:05:09-723590 util-8627 DEBUG Config value TEMPORARY_TABLE="NO"
Jul 07 21:05:09-723850 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-724064 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 21:05:09-724264 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 21:05:09-724533 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/statistics.conf'
Jul 07 21:05:09-724719 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-724927 util-8627 DEBUG Config section `statistics'
Jul 07 21:05:09-725135 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-725488 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-725746 util-8627 DEBUG Config value BINARY="gnunet-service-statistics"
Jul 07 21:05:09-725995 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-726242 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-726502 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock"
Jul 07 21:05:09-726757 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-727005 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-727263 util-8627 DEBUG Config value DATABASE="$GNUNET_DATA_HOME/statistics.dat"
Jul 07 21:05:09-727615 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-727827 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 21:05:09-728028 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 21:05:09-728309 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/nse.conf'
Jul 07 21:05:09-728494 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-728701 util-8627 DEBUG Config section `nse'
Jul 07 21:05:09-728908 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-729279 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-729523 util-8627 DEBUG Config value BINARY="gnunet-service-nse"
Jul 07 21:05:09-729764 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-730006 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-730268 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-nse.unix"
Jul 07 21:05:09-730516 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-730759 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-731012 util-8627 DEBUG Config value PROOFFILE="$GNUNET_DATA_HOME/nse/proof.dat"
Jul 07 21:05:09-731323 util-8627 DEBUG Config value HISTOGRAM_DIR="$GNUNET_CACHE_HOME/nse/histogram"
Jul 07 21:05:09-731662 util-8627 DEBUG Config value WORKDELAY="5 ms"
Jul 07 21:05:09-732010 util-8627 DEBUG Config value INTERVAL="1 h"
Jul 07 21:05:09-732343 util-8627 DEBUG Config value WORKBITS="22"
Jul 07 21:05:09-732573 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-732787 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 21:05:09-732999 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 21:05:09-733294 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/resolver.conf'
Jul 07 21:05:09-733479 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-733687 util-8627 DEBUG Config section `resolver'
Jul 07 21:05:09-733895 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-734224 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-734470 util-8627 DEBUG Config value BINARY="gnunet-service-resolver"
Jul 07 21:05:09-734716 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-734972 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-735230 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-resolver.sock"
Jul 07 21:05:09-735482 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-735728 util-8627 DEBUG Config value UNIX_MATCH_GID="NO"
Jul 07 21:05:09-736080 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-736296 util-8627 DEBUG Asked to parse config file `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 21:05:09-736494 util-8627 DEBUG Config file name expanded to `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 21:05:09-736766 util-8627 DEBUG Deserializing contents of file `/opt/gnunet/share/gnunet/config.d/datastore.conf'
Jul 07 21:05:09-736950 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-737169 util-8627 DEBUG Config section `datastore'
Jul 07 21:05:09-737418 util-8627 DEBUG Config value AUTOSTART="YES"
Jul 07 21:05:09-737758 util-8627 DEBUG Config value UNIXPATH="$GNUNET_RUNTIME_DIR/gnunet-service-datastore.sock"
Jul 07 21:05:09-738013 util-8627 DEBUG Config value UNIX_MATCH_UID="NO"
Jul 07 21:05:09-738259 util-8627 DEBUG Config value UNIX_MATCH_GID="YES"
Jul 07 21:05:09-738522 util-8627 DEBUG Config value HOSTNAME="localhost"
Jul 07 21:05:09-738772 util-8627 DEBUG Config value BINARY="gnunet-service-datastore"
Jul 07 21:05:09-739023 util-8627 DEBUG Config value ACCEPT_FROM="127.0.0.1;"
Jul 07 21:05:09-739272 util-8627 DEBUG Config value ACCEPT_FROM6="::1;"
Jul 07 21:05:09-739522 util-8627 DEBUG Config value QUOTA="5 GB"
Jul 07 21:05:09-739777 util-8627 DEBUG Config value BLOOMFILTER="$GNUNET_DATA_HOME/datastore/bloomfilter"
Jul 07 21:05:09-740041 util-8627 DEBUG Config value DATABASE="sqlite"
Jul 07 21:05:09-740319 util-8627 DEBUG Config section `datastore-sqlite'
Jul 07 21:05:09-740533 util-8627 DEBUG Config value FILENAME="$GNUNET_DATA_HOME/datastore/sqlite.db"
Jul 07 21:05:09-740877 util-8627 DEBUG Config section `datastore-postgres'
Jul 07 21:05:09-741091 util-8627 DEBUG Config value CONFIG="connect_timeout=10; dbname=gnunet"
Jul 07 21:05:09-741469 util-8627 DEBUG Config section `datastore-mysql'
Jul 07 21:05:09-741679 util-8627 DEBUG Config value DATABASE="gnunet"
Jul 07 21:05:09-742023 util-8627 DEBUG Config value CONFIG="~/.my.cnf"
Jul 07 21:05:09-742344 util-8627 DEBUG Config section `datastore-heap'
Jul 07 21:05:09-742556 util-8627 DEBUG Config value HASHMAPSIZE="1024"
Jul 07 21:05:09-742887 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-745932 util-8627 DEBUG Asked to parse config file `/home/gnunet/.config/gnunet.conf'
Jul 07 21:05:09-746147 util-8627 DEBUG Config file name expanded to `/home/gnunet/.config/gnunet.conf'
Jul 07 21:05:09-746430 util-8627 DEBUG Deserializing contents of file `/home/gnunet/.config/gnunet.conf'
Jul 07 21:05:09-746621 util-8627 DEBUG Deserializing config file
Jul 07 21:05:09-746831 util-8627 DEBUG Config section `arm'
Jul 07 21:05:09-747071 util-8627 DEBUG Config value DEFAULTSERVICES="topology hostlist dht nse fs revocation"
Jul 07 21:05:09-747378 util-8627 DEBUG Config section `transport'
Jul 07 21:05:09-747604 util-8627 DEBUG Config value PLUGINS="tcp udp http_server http_client https_server https_client"
Jul 07 21:05:09-747954 util-8627 DEBUG Config section `cadet'
Jul 07 21:05:09-748164 util-8627 DEBUG Config value PREFIX="valgrind"
Jul 07 21:05:09-748485 util-8627 DEBUG Config value OPTIONS="-L DEBUG -l /home/gnunet/cadet.log"
Jul 07 21:05:09-748824 util-8627 DEBUG Config value AUTOSTART="NO"
Jul 07 21:05:09-749125 util-8627 DEBUG Config section `nat'
Jul 07 21:05:09-749364 util-8627 DEBUG Config value DISABLEV6="YES"
Jul 07 21:05:09-749632 util-8627 DEBUG Config section `hostlist'
Jul 07 21:05:09-749861 util-8627 DEBUG Config value HTTPPORT="8080"
Jul 07 21:05:09-750195 util-8627 DEBUG Config value OPTIONS="-p"
Jul 07 21:05:09-750444 util-8627 DEBUG Config value SERVERS=""
Jul 07 21:05:09-750659 util-8627 DEBUG Finished deserializing config
Jul 07 21:05:09-773165 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `cadet'
Jul 07 21:05:09-775022 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `cadet'
Jul 07 21:05:09-777283 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock', $-expanding
Jul 07 21:05:09-780032 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-cadet.sock
Jul 07 21:05:09-782774 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-cadet.sock' with default (null)
Jul 07 21:05:09-783498 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:09-784275 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:09-786420 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:09-786616 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:09-788086 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:09-789740 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:09-790267 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:09-790468 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:09-790654 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:09-790997 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:09-791319 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:09-791500 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:09-792575 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:09-795291 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:09-801768 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:09-802333 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:09-802651 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:09-806117 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:09-807492 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock'
Jul 07 21:05:09-808668 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock', *nix-expanding
Jul 07 21:05:09-810278 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock'
Jul 07 21:05:09-820948 util-8627 DEBUG Asked to retrieve string `ACCEPT_FROM' in section `cadet'
Jul 07 21:05:09-832971 util-8627 DEBUG Asked to retrieve string `ACCEPT_FROM6' in section `cadet'
Jul 07 21:05:09-844645 util-8627 DEBUG Asked to retrieve filename `USERNAME' in section `cadet'
Jul 07 21:05:09-844842 util-8627 DEBUG Asked to retrieve string `USERNAME' in section `cadet'
Jul 07 21:05:09-845990 util-8627 DEBUG Failed to retrieve filename
Jul 07 21:05:09-847537 util-8627 DEBUG Service `cadet' runs with configuration from `/home/gnunet/.config/gnunet.conf'
Jul 07 21:05:09-859777 util-scheduler-8627 DEBUG Registering signal handlers
Jul 07 21:05:09-878337 util-scheduler-8627 DEBUG Adding continuation task: 1 / 0xbee5ea60
Jul 07 21:05:09-886388 util-scheduler-8627 DEBUG Adding task: 2 / (nil)
Jul 07 21:05:09-900792 util-scheduler-8627 DEBUG Checking readiness of task: 2 / (nil)
Jul 07 21:05:09-904834 util-scheduler-8627 DEBUG Running task: 2 / (nil)
Jul 07 21:05:09-906663 util-8627 DEBUG Not installing a handler because $GNUNET_OS_CONTROL_PIPE is empty
Jul 07 21:05:09-915729 util-scheduler-8627 DEBUG Running task: 1 / 0xbee5ea60
Jul 07 21:05:09-931532 util-8627 DEBUG Speed up disabled
Jul 07 21:05:09-934507 util-8627 DEBUG Asked to retrieve string `HOSTNAME' in section `resolver'
Jul 07 21:05:09-948023 util-8627 WARNING `bind' failed for `/tmp/gnunet-system-runtime//gnunet-service-cadet.sock': address already in use
Jul 07 21:05:09-952566 util-8627 ERROR `bind' failed at server.c:613 with error: Address already in use
Jul 07 21:05:09-961910 util-scheduler-8627 DEBUG Adding task: 3 / 0xbee5ea60
Jul 07 21:05:09-966374 util-8627 INFO Service `cadet' runs at /tmp/gnunet-system-runtime//gnunet-service-cadet.sock
Jul 07 21:05:09-969140 cadet-8627 DEBUG starting to run
Jul 07 21:05:09-973816 util-scheduler-8627 DEBUG Adding task: 4 / (nil)
Jul 07 21:05:09-974736 cadet-8627 INFO reading key
Jul 07 21:05:09-975676 util-8627 DEBUG Asked to retrieve filename `PRIVATE_KEY' in section `PEER'
Jul 07 21:05:09-975870 util-8627 DEBUG Asked to retrieve string `PRIVATE_KEY' in section `PEER'
Jul 07 21:05:09-976279 util-8627 DEBUG Retrieved filename `$GNUNET_DATA_HOME/private_key.ecc', $-expanding
Jul 07 21:05:09-976482 util-8627 DEBUG Asked to $-expand $GNUNET_DATA_HOME/private_key.ecc
Jul 07 21:05:09-976672 util-8627 DEBUG Split into `GNUNET_DATA_HOME' and `private_key.ecc' with default (null)
Jul 07 21:05:09-976859 util-8627 DEBUG Asked to retrieve string `GNUNET_DATA_HOME' in section `PATHS'
Jul 07 21:05:09-977102 util-8627 DEBUG Asked to $-expand ${XDG_DATA_HOME:-$GNUNET_HOME/.local/share}/gnunet/
Jul 07 21:05:09-977336 util-8627 DEBUG Split into `XDG_DATA_HOME' and `/gnunet/' with default $GNUNET_HOME/.local/share
Jul 07 21:05:09-977521 util-8627 DEBUG Asked to retrieve string `XDG_DATA_HOME' in section `PATHS'
Jul 07 21:05:09-977724 util-8627 DEBUG Filename for `XDG_DATA_HOME' is not in PATHS config section
Jul 07 21:05:09-977905 util-8627 DEBUG `XDG_DATA_HOME' is not an environment variable
Jul 07 21:05:09-978084 util-8627 DEBUG Asked to $-expand $GNUNET_HOME/.local/share
Jul 07 21:05:09-978264 util-8627 DEBUG Split into `GNUNET_HOME' and `.local/share' with default (null)
Jul 07 21:05:09-978446 util-8627 DEBUG Asked to retrieve string `GNUNET_HOME' in section `PATHS'
Jul 07 21:05:09-978683 util-8627 DEBUG Asked to $-expand ${GNUNET_TEST_HOME:-${HOME:-${USERPROFILE}}}
Jul 07 21:05:09-978890 util-8627 DEBUG Split into `GNUNET_TEST_HOME' and `' with default ${HOME:-${USERPROFILE}}
Jul 07 21:05:09-979076 util-8627 DEBUG Asked to retrieve string `GNUNET_TEST_HOME' in section `PATHS'
Jul 07 21:05:09-979298 util-8627 DEBUG Filename for `GNUNET_TEST_HOME' is not in PATHS config section
Jul 07 21:05:09-979486 util-8627 DEBUG `GNUNET_TEST_HOME' is not an environment variable
Jul 07 21:05:09-979662 util-8627 DEBUG Asked to $-expand ${HOME:-${USERPROFILE}}
Jul 07 21:05:09-979854 util-8627 DEBUG Split into `HOME' and `' with default ${USERPROFILE}
Jul 07 21:05:09-980034 util-8627 DEBUG Asked to retrieve string `HOME' in section `PATHS'
Jul 07 21:05:09-980235 util-8627 DEBUG Filename for `HOME' is not in PATHS config section
Jul 07 21:05:09-980669 util-8627 DEBUG Prefix is `/home/gnunet'
Jul 07 21:05:09-980879 util-8627 DEBUG Expanded to `/home/gnunet'
Jul 07 21:05:09-981066 util-8627 DEBUG Prefix is `/home/gnunet'
Jul 07 21:05:09-981299 util-8627 DEBUG Expanded to `/home/gnunet'
Jul 07 21:05:09-981492 util-8627 DEBUG Prefix is `/home/gnunet'
Jul 07 21:05:09-981697 util-8627 DEBUG Expanded to `/home/gnunet/.local/share'
Jul 07 21:05:09-981886 util-8627 DEBUG Prefix is `/home/gnunet/.local/share'
Jul 07 21:05:09-982087 util-8627 DEBUG Expanded to `/home/gnunet/.local/share/gnunet/'
Jul 07 21:05:09-982280 util-8627 DEBUG Prefix is `/home/gnunet/.local/share/gnunet/'
Jul 07 21:05:09-982488 util-8627 DEBUG Expanded to `/home/gnunet/.local/share/gnunet//private_key.ecc'
Jul 07 21:05:09-982868 util-8627 DEBUG Expanded to filename `/home/gnunet/.local/share/gnunet//private_key.ecc', *nix-expanding
Jul 07 21:05:09-983250 util-8627 DEBUG Filename result is `/home/gnunet/.local/share/gnunet//private_key.ecc'
Jul 07 21:05:10-840813 cadet-8627 INFO STARTING SERVICE (CADET) for peer [GN10]
Jul 07 21:05:10-842245 cadet-loc-8627 DEBUG init
Jul 07 21:05:10-845559 cadet-hll-8627 DEBUG init
Jul 07 21:05:10-847687 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-847884 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-848165 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:05:10-848370 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:05:10-848564 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:05:10-848752 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-849047 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-849281 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-849471 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-849674 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-849865 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-850039 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-850228 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-850408 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-850610 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-850788 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-850960 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-851247 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-851440 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-851645 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-851829 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-852025 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-852221 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-852429 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-852635 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:05:10-852854 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-854704 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-854897 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-855150 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:05:10-855346 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:05:10-855535 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:05:10-855722 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-855953 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-856151 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-856335 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-856535 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-856937 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-857111 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-857329 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-857510 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-857715 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-857893 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-858065 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-858233 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-858438 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-858634 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-858817 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-859023 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-859224 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-859431 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-859637 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:05:10-859841 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-867664 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' succeeded! (0x465d370)
Jul 07 21:05:10-869478 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'!
Jul 07 21:05:10-872351 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-872543 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-872799 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:05:10-872995 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:05:10-873185 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:05:10-873400 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-873631 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-873830 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-874013 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-874214 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-874392 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-874564 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-874752 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-874931 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-875132 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-875310 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-875481 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-875650 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-875831 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-876024 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-876206 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-876401 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-876593 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-876799 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-877023 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:05:10-877254 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-877495 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-877677 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:05:10-877925 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:05:10-878119 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:05:10-878309 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:05:10-878496 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-878725 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-878938 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-879121 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-879322 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-879500 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-879672 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-879858 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-880037 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-880241 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-880419 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-880591 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-880760 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-880940 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-881132 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-881342 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-881537 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-881729 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-881936 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-882141 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:05:10-882345 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:05:10-882850 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' succeeded! (0x465ed58)
Jul 07 21:05:10-883168 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'!
Jul 07 21:05:10-889634 util-8627 DEBUG Scheduling transmission (0x465ed58).
Jul 07 21:05:10-896914 util-scheduler-8627 DEBUG Adding task: 5 / 0x465ed58
Jul 07 21:05:10-899564 cadet-con-8627 DEBUG init
Jul 07 21:05:10-906890 cadet-p2p-8627 DEBUG init
Jul 07 21:05:10-912178 core-api-8627 DEBUG Connecting to CORE service
Jul 07 21:05:10-913332 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `core'
Jul 07 21:05:10-913525 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `core'
Jul 07 21:05:10-913782 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-core.sock', $-expanding
Jul 07 21:05:10-913976 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-core.sock
Jul 07 21:05:10-914164 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-core.sock' with default (null)
Jul 07 21:05:10-914351 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-914583 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-914782 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-914965 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-915167 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-915346 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-915518 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-915705 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-915884 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-916088 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-916276 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-916448 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-916617 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-916799 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-916994 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-917175 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-917407 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-917618 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-917825 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 21:05:10-918029 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-core.sock', *nix-expanding
Jul 07 21:05:10-918234 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 21:05:10-918478 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `core'
Jul 07 21:05:10-918659 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `core'
Jul 07 21:05:10-918906 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-core.sock', $-expanding
Jul 07 21:05:10-919097 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-core.sock
Jul 07 21:05:10-919283 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-core.sock' with default (null)
Jul 07 21:05:10-919469 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-919708 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-919905 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-920087 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-920291 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-920469 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-920641 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-920827 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-921007 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-921232 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-921412 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-921584 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-921753 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-921933 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-922125 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-922306 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-922501 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-922693 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-922896 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 21:05:10-923100 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-core.sock', *nix-expanding
Jul 07 21:05:10-923302 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-core.sock'
Jul 07 21:05:10-923655 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' succeeded! (0x4661f98)
Jul 07 21:05:10-923847 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-core.sock'!
Jul 07 21:05:10-925852 core-api-8627 INFO (Re)connecting to CORE service, monitoring messages of type 0
Jul 07 21:05:10-929614 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:05:10-930003 util-scheduler-8627 DEBUG Adding task: 6 / 0x4661f98
Jul 07 21:05:10-935222 transport-api-8627 DEBUG Connecting to transport service.
Jul 07 21:05:10-935827 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `transport'
Jul 07 21:05:10-936019 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `transport'
Jul 07 21:05:10-936299 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock', $-expanding
Jul 07 21:05:10-936496 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-transport.sock
Jul 07 21:05:10-936686 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-transport.sock' with default (null)
Jul 07 21:05:10-936872 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-937103 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-937343 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-937528 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-937730 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-937908 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-938081 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-938269 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-938452 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-938656 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-938834 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-939006 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-939175 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-939364 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-939559 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-939741 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-939937 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-940128 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-940335 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 21:05:10-940540 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-transport.sock', *nix-expanding
Jul 07 21:05:10-940747 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 21:05:10-941023 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `transport'
Jul 07 21:05:10-941229 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `transport'
Jul 07 21:05:10-941505 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-transport.sock', $-expanding
Jul 07 21:05:10-941700 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-transport.sock
Jul 07 21:05:10-941888 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-transport.sock' with default (null)
Jul 07 21:05:10-942074 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-942305 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-942502 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-942685 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-942891 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-943069 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-943241 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-943427 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-943607 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-943808 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-943984 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-944157 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-944325 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-944511 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-944704 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-944886 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-945081 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-945299 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-945506 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 21:05:10-945712 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-transport.sock', *nix-expanding
Jul 07 21:05:10-945918 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'
Jul 07 21:05:10-946280 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' succeeded! (0x4663c60)
Jul 07 21:05:10-946488 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-transport.sock'!
Jul 07 21:05:10-949423 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:05:10-954011 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:05:10-955165 util-scheduler-8627 DEBUG Adding task: 7 / 0x46623e0
Jul 07 21:05:10-957278 cadet-dht-8627 DEBUG init
Jul 07 21:05:10-965104 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `dht'
Jul 07 21:05:10-965335 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `dht'
Jul 07 21:05:10-965572 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock', $-expanding
Jul 07 21:05:10-965769 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-dht.sock
Jul 07 21:05:10-965959 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-dht.sock' with default (null)
Jul 07 21:05:10-966146 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-966378 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-966576 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-966760 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-966961 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-967140 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-967312 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-967499 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-967679 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-967881 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-968059 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-968230 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-968403 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-968585 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-968779 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-968960 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-969155 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-969372 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-969577 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 21:05:10-969780 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-dht.sock', *nix-expanding
Jul 07 21:05:10-969993 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 21:05:10-970215 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `dht'
Jul 07 21:05:10-970396 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `dht'
Jul 07 21:05:10-970625 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-dht.sock', $-expanding
Jul 07 21:05:10-970826 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-dht.sock
Jul 07 21:05:10-971013 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-dht.sock' with default (null)
Jul 07 21:05:10-971199 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:10-971430 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:10-971627 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:10-971809 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:10-972010 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:10-972187 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:10-972359 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:10-972546 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:10-972744 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:10-972949 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:10-973126 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:10-973324 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:10-973494 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:10-973675 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-973867 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:10-974048 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:10-974242 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-974435 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:10-974639 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 21:05:10-974843 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-dht.sock', *nix-expanding
Jul 07 21:05:10-975046 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'
Jul 07 21:05:10-975383 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' succeeded! (0x4665ad8)
Jul 07 21:05:10-975577 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-dht.sock'!
Jul 07 21:05:10-977579 util-scheduler-8627 DEBUG Adding task: 8 / (nil)
Jul 07 21:05:10-979153 cadet-tun-8627 DEBUG init
Jul 07 21:05:10-980580 util-scheduler-8627 DEBUG Adding task: 9 / (nil)
Jul 07 21:05:10-981936 cadet-8627 DEBUG Cadet service running
Jul 07 21:05:10-987919 util-scheduler-8627 DEBUG Checking readiness of task: 6 / 0x4661f98
Jul 07 21:05:10-989459 util-scheduler-8627 DEBUG Checking readiness of task: 5 / 0x465ed58
Jul 07 21:05:10-990432 util-scheduler-8627 DEBUG Running task: 5 / 0x465ed58
Jul 07 21:05:10-991828 util-8627 DEBUG transmit_ready running (0x465ed58).
Jul 07 21:05:10-995031 util-8627 DEBUG process_notify is running
Jul 07 21:05:10-997665 util-8627 DEBUG client_notify is running
Jul 07 21:05:11-001770 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:11-008300 util-scheduler-8627 DEBUG Adding task: 10 / 0x465ed58
Jul 07 21:05:11-011324 util-8627 DEBUG Transmitting message of type 334 and size 8 to peerinfo service.
Jul 07 21:05:11-015222 util-8627 DEBUG Connection transmitted 8/8 bytes to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)
Jul 07 21:05:11-015978 util-scheduler-8627 DEBUG Running task: 6 / 0x4661f98
Jul 07 21:05:11-016335 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:05:11-016629 util-8627 DEBUG process_notify is running
Jul 07 21:05:11-016969 util-8627 DEBUG client_notify is running
Jul 07 21:05:11-019139 core-api-8627 DEBUG Transmitting control message with 24 bytes of type 64 to core.
Jul 07 21:05:11-021843 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:11-022059 util-scheduler-8627 DEBUG Adding task: 11 / 0x4661f98
Jul 07 21:05:11-024000 core-api-8627 DEBUG Core connection down, not processing queue
Jul 07 21:05:11-024760 util-8627 DEBUG Transmitting message of type 64 and size 24 to core service.
Jul 07 21:05:11-025116 util-8627 DEBUG Connection transmitted 24/24 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:05:11-025358 util-scheduler-8627 DEBUG Running task: 9 / (nil)
Jul 07 21:05:13-042065 util-scheduler-8627 DEBUG Adding task: 12 / (nil)
Jul 07 21:05:13-042705 util-scheduler-8627 DEBUG Running task: 8 / (nil)
Jul 07 21:05:13-043885 cadet-dht-8627 DEBUG Announce ID
Jul 07 21:05:13-044890 cadet-hll-8627 DEBUG  mine is (nil)
Jul 07 21:05:13-045732 util-scheduler-8627 DEBUG Adding task: 13 / (nil)
Jul 07 21:05:13-046701 cadet-dht-8627 DEBUG   no hello, waiting!
Jul 07 21:05:13-047103 util-scheduler-8627 DEBUG Running task: 7 / 0x46623e0
Jul 07 21:05:13-049516 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:05:13-050627 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:05:13-050851 util-scheduler-8627 DEBUG Adding task: 14 / 0x4663c60
Jul 07 21:05:13-052320 util-scheduler-8627 DEBUG Checking readiness of task: 14 / 0x4663c60
Jul 07 21:05:13-052529 util-scheduler-8627 DEBUG Checking readiness of task: 11 / 0x4661f98
Jul 07 21:05:13-053115 util-scheduler-8627 DEBUG Checking readiness of task: 10 / 0x465ed58
Jul 07 21:05:13-053732 util-scheduler-8627 DEBUG Running task: 10 / 0x465ed58
Jul 07 21:05:13-058339 util-8627 DEBUG receive_ready read 3186/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:05:13-062389 util-scheduler-8627 DEBUG Adding task: 15 / 0x465ef00
Jul 07 21:05:13-063270 util-scheduler-8627 DEBUG Running task: 11 / 0x4661f98
Jul 07 21:05:13-063828 util-8627 DEBUG receive_ready read 240/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:05:13-064078 util-scheduler-8627 DEBUG Adding task: 16 / 0x4662140
Jul 07 21:05:13-064292 util-scheduler-8627 DEBUG Running task: 14 / 0x4663c60
Jul 07 21:05:13-064482 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:05:13-064676 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-064852 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-067934 transport-api-8627 DEBUG Transmitting `START' request.
Jul 07 21:05:13-070079 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:13-070305 util-scheduler-8627 DEBUG Adding task: 17 / 0x4663c60
Jul 07 21:05:13-071749 transport-api-8627 DEBUG Added 40 bytes of control message at 0
Jul 07 21:05:13-074683 transport-api-8627 DEBUG Transmitting 40 bytes to transport service
Jul 07 21:05:13-075163 util-8627 DEBUG Transmitting message of type 360 and size 40 to transport service.
Jul 07 21:05:13-075435 util-8627 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:05:13-075698 util-scheduler-8627 DEBUG Checking readiness of task: 17 / 0x4663c60
Jul 07 21:05:13-075897 util-scheduler-8627 DEBUG Running task: 17 / 0x4663c60
Jul 07 21:05:13-076307 util-8627 DEBUG receive_ready read 802/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:05:13-076552 util-scheduler-8627 DEBUG Adding task: 18 / 0x4663e08
Jul 07 21:05:13-076762 util-scheduler-8627 DEBUG Running task: 16 / 0x4662140
Jul 07 21:05:13-078831 util-8627 DEBUG Received message of type 65 and size 40 from core service.
Jul 07 21:05:13-084824 core-api-8627 DEBUG Processing message of type 65 and size 40 from core service
Jul 07 21:05:13-086959 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:05:13-089280 core-api-8627 DEBUG Connected to core service of peer `GN10'.
Jul 07 21:05:13-090538 cadet-p2p-8627 DEBUG Core init
Jul 07 21:05:13-105416 cadet-p2p-8627 INFO CONNECTED GN10 (self)
Jul 07 21:05:13-109945 cadet-p2p-8627 DEBUG adding path [1] to peer GN10
Jul 07 21:05:13-111281 cadet-p2p-8627 DEBUG  final length: 1
Jul 07 21:05:13-113471 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-114983 util-scheduler-8627 DEBUG Adding task: 19 / 0x4662140
Jul 07 21:05:13-115623 util-scheduler-8627 DEBUG Running task: 15 / 0x465ef00
Jul 07 21:05:13-115987 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:05:13-120258 nse-api-8627 DEBUG Received information about peer `4AE6' from peerinfo database
Jul 07 21:05:13-132742 cadet-hll-8627 DEBUG  hello for 4AE6 (64 bytes), expires on Mon Jul 07 22:33:30 2014
Jul 07 21:05:13-134711 cadet-p2p-8627 DEBUG set hello for 4AE6
Jul 07 21:05:13-136491 cadet-p2p-8627 DEBUG  new (64 bytes)
Jul 07 21:05:13-138194 util-scheduler-8627 DEBUG Adding task: 20 / 0x465ef00
Jul 07 21:05:13-139195 util-scheduler-8627 DEBUG Running task: 20 / 0x465ef00
Jul 07 21:05:13-139397 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-139733 nse-api-8627 DEBUG Received information about peer `4YCN' from peerinfo database
Jul 07 21:05:13-140156 cadet-hll-8627 DEBUG  hello for 4YCN (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-140545 cadet-p2p-8627 DEBUG set hello for 4YCN
Jul 07 21:05:13-140833 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-141063 util-scheduler-8627 DEBUG Adding task: 21 / 0x465ef00
Jul 07 21:05:13-141289 util-scheduler-8627 DEBUG Running task: 19 / 0x4662140
Jul 07 21:05:13-141480 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:05:13-141846 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:05:13-143315 core-api-8627 DEBUG Received notification about connection from `KNAS'.
Jul 07 21:05:13-146637 cadet-p2p-8627 INFO CONNECTED GN10 <= KNAS
Jul 07 21:05:13-155705 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `statistics'
Jul 07 21:05:13-155911 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `statistics'
Jul 07 21:05:13-156148 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock', $-expanding
Jul 07 21:05:13-156350 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock
Jul 07 21:05:13-156570 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-statistics.sock' with default (null)
Jul 07 21:05:13-156759 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:13-156996 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:13-157223 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:13-157410 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:13-157614 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:13-157795 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:13-157968 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:13-158158 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:13-158338 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:13-158540 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:13-158719 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:13-158891 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:13-159064 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:13-159249 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:13-159453 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:13-159647 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:13-159843 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:13-160038 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:13-160295 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 21:05:13-160506 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock', *nix-expanding
Jul 07 21:05:13-160723 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 21:05:13-160936 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `statistics'
Jul 07 21:05:13-161119 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `statistics'
Jul 07 21:05:13-161372 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock', $-expanding
Jul 07 21:05:13-161567 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-statistics.sock
Jul 07 21:05:13-161756 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-statistics.sock' with default (null)
Jul 07 21:05:13-161943 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:05:13-162174 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:05:13-162372 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:05:13-162554 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:05:13-162761 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:05:13-162950 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:05:13-163152 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:05:13-163341 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:05:13-163520 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:05:13-163721 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:05:13-163898 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:05:13-164069 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:05:13-164238 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:05:13-164418 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:13-164611 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:05:13-164793 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:05:13-164988 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:05:13-165179 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:05:13-165414 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 21:05:13-165622 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock', *nix-expanding
Jul 07 21:05:13-165829 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'
Jul 07 21:05:13-166213 util-8627 DEBUG Connection to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' succeeded! (0x4d50e20)
Jul 07 21:05:13-166412 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock'!
Jul 07 21:05:13-169690 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:05:13-169915 util-scheduler-8627 DEBUG Adding task: 22 / 0x4d50e20
Jul 07 21:05:13-170846 cadet-p2p-8627 DEBUG adding path [2] to peer KNAS
Jul 07 21:05:13-171409 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:05:13-171677 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-172071 util-scheduler-8627 DEBUG Adding task: 23 / 0x4662140
Jul 07 21:05:13-172277 util-scheduler-8627 DEBUG Running task: 18 / 0x4663e08
Jul 07 21:05:13-172472 util-8627 DEBUG Received message of type 17 and size 538 from transport service.
Jul 07 21:05:13-174177 util-scheduler-8627 DEBUG Adding task: 24 / 0x4663e08
Jul 07 21:05:13-177305 transport-api-8627 DEBUG Receiving (my own) `HELLO' message, I am `GN10'.
Jul 07 21:05:13-178902 util-scheduler-8627 DEBUG Checking readiness of task: 22 / 0x4d50e20
Jul 07 21:05:13-179118 util-scheduler-8627 DEBUG Running task: 22 / 0x4d50e20
Jul 07 21:05:13-179306 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:05:13-179494 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-179666 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-186166 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:05:13-186432 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:05:13-186647 util-scheduler-8627 DEBUG Running task: 24 / 0x4663e08
Jul 07 21:05:13-186841 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-187062 util-scheduler-8627 DEBUG Adding task: 25 / 0x4663e08
Jul 07 21:05:13-188633 transport-api-8627 DEBUG Receiving `CONNECT' message for `D3TJ'.
Jul 07 21:05:13-190390 transport-api-8627 DEBUG Creating entry for neighbour `D3TJ'.
Jul 07 21:05:13-193047 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-196166 util-bandwidth-8627 DEBUG Tracker 0x4d51d68 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-201383 util-scheduler-8627 DEBUG Adding task: 26 / 0x4d51d68
Jul 07 21:05:13-203870 transport-api-8627 DEBUG Receiving `CONNECT' message for `D3TJ' with quota 12173
Jul 07 21:05:13-205912 util-bandwidth-8627 DEBUG Tracker 0x4d51d68 bandwidth changed to 12173 Bps
Jul 07 21:05:13-212606 util-bandwidth-8627 DEBUG Tracker 0x4d51d68 updated, have 1024 Bps, last update was 11 ms ago
Jul 07 21:05:13-217100 util-scheduler-8627 DEBUG Canceling task: 26 / 0x4d51d68
Jul 07 21:05:13-218018 util-scheduler-8627 DEBUG Adding task: 27 / 0x4d51d68
Jul 07 21:05:13-218368 util-scheduler-8627 DEBUG Running task: 23 / 0x4662140
Jul 07 21:05:13-218566 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:05:13-218763 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:05:13-219082 core-api-8627 DEBUG Received notification about connection from `STRN'.
Jul 07 21:05:13-219517 cadet-p2p-8627 INFO CONNECTED GN10 <= STRN
Jul 07 21:05:13-220075 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:05:13-220292 util-scheduler-8627 DEBUG Adding task: 28 / 0x4d50e20
Jul 07 21:05:13-220509 cadet-p2p-8627 DEBUG adding path [2] to peer STRN
Jul 07 21:05:13-220689 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:05:13-220861 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-221070 util-scheduler-8627 DEBUG Adding task: 29 / 0x4662140
Jul 07 21:05:13-221295 util-scheduler-8627 DEBUG Running task: 21 / 0x465ef00
Jul 07 21:05:13-221487 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-221718 nse-api-8627 DEBUG Received information about peer `D3TJ' from peerinfo database
Jul 07 21:05:13-221986 cadet-hll-8627 DEBUG  hello for D3TJ (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-222217 cadet-p2p-8627 DEBUG set hello for D3TJ
Jul 07 21:05:13-222391 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-222600 util-scheduler-8627 DEBUG Adding task: 30 / 0x465ef00
Jul 07 21:05:13-222853 util-scheduler-8627 DEBUG Checking readiness of task: 28 / 0x4d50e20
Jul 07 21:05:13-223050 util-scheduler-8627 DEBUG Running task: 28 / 0x4d50e20
Jul 07 21:05:13-223234 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:05:13-223508 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-223684 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-224313 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:05:13-224573 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:05:13-224786 util-scheduler-8627 DEBUG Running task: 30 / 0x465ef00
Jul 07 21:05:13-224977 util-8627 DEBUG Received message of type 332 and size 420 from peerinfo service.
Jul 07 21:05:13-225236 nse-api-8627 DEBUG Received information about peer `DSTJ' from peerinfo database
Jul 07 21:05:13-226168 cadet-hll-8627 DEBUG  hello for DSTJ (380 bytes), expires on end of time
Jul 07 21:05:13-227418 cadet-p2p-8627 DEBUG set hello for DSTJ
Jul 07 21:05:13-227600 cadet-p2p-8627 DEBUG  new (380 bytes)
Jul 07 21:05:13-227817 util-scheduler-8627 DEBUG Adding task: 31 / 0x465ef00
Jul 07 21:05:13-228015 util-scheduler-8627 DEBUG Running task: 29 / 0x4662140
Jul 07 21:05:13-228204 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:05:13-228398 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:05:13-228606 core-api-8627 DEBUG Received notification about connection from `TZQE'.
Jul 07 21:05:13-228878 cadet-p2p-8627 INFO CONNECTED GN10 <= TZQE
Jul 07 21:05:13-229130 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:05:13-229366 util-scheduler-8627 DEBUG Adding task: 32 / 0x4d50e20
Jul 07 21:05:13-229578 cadet-p2p-8627 DEBUG adding path [2] to peer TZQE
Jul 07 21:05:13-229755 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:05:13-229924 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-230139 util-scheduler-8627 DEBUG Adding task: 33 / 0x4662140
Jul 07 21:05:13-230335 util-scheduler-8627 DEBUG Running task: 25 / 0x4663e08
Jul 07 21:05:13-230526 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-230740 util-scheduler-8627 DEBUG Adding task: 34 / 0x4663e08
Jul 07 21:05:13-231057 transport-api-8627 DEBUG Receiving `CONNECT' message for `KNAS'.
Jul 07 21:05:13-231420 transport-api-8627 DEBUG Creating entry for neighbour `KNAS'.
Jul 07 21:05:13-231778 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-232137 util-bandwidth-8627 DEBUG Tracker 0x4d54488 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-232377 util-scheduler-8627 DEBUG Adding task: 35 / 0x4d54488
Jul 07 21:05:13-232704 transport-api-8627 DEBUG Receiving `CONNECT' message for `KNAS' with quota 10913
Jul 07 21:05:13-233058 util-bandwidth-8627 DEBUG Tracker 0x4d54488 bandwidth changed to 10913 Bps
Jul 07 21:05:13-234110 util-bandwidth-8627 DEBUG Tracker 0x4d54488 updated, have 1024 Bps, last update was 1310 µs ago
Jul 07 21:05:13-234730 util-scheduler-8627 DEBUG Canceling task: 35 / 0x4d54488
Jul 07 21:05:13-234950 util-scheduler-8627 DEBUG Adding task: 36 / 0x4d54488
Jul 07 21:05:13-235188 util-scheduler-8627 DEBUG Checking readiness of task: 32 / 0x4d50e20
Jul 07 21:05:13-235382 util-scheduler-8627 DEBUG Running task: 32 / 0x4d50e20
Jul 07 21:05:13-235567 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:05:13-235742 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-235912 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-236127 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:05:13-236382 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:05:13-236592 util-scheduler-8627 DEBUG Running task: 34 / 0x4663e08
Jul 07 21:05:13-236784 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-236998 util-scheduler-8627 DEBUG Adding task: 37 / 0x4663e08
Jul 07 21:05:13-237236 transport-api-8627 DEBUG Receiving `CONNECT' message for `P00P'.
Jul 07 21:05:13-237444 transport-api-8627 DEBUG Creating entry for neighbour `P00P'.
Jul 07 21:05:13-237633 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-237822 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-238037 util-scheduler-8627 DEBUG Adding task: 38 / 0x4d54cd0
Jul 07 21:05:13-238255 transport-api-8627 DEBUG Receiving `CONNECT' message for `P00P' with quota 8117
Jul 07 21:05:13-238444 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 bandwidth changed to 8117 Bps
Jul 07 21:05:13-238677 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 updated, have 1024 Bps, last update was 814 µs ago
Jul 07 21:05:13-238884 util-scheduler-8627 DEBUG Canceling task: 38 / 0x4d54cd0
Jul 07 21:05:13-239120 util-scheduler-8627 DEBUG Adding task: 39 / 0x4d54cd0
Jul 07 21:05:13-239316 util-scheduler-8627 DEBUG Running task: 33 / 0x4662140
Jul 07 21:05:13-239503 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:05:13-239696 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:05:13-239902 core-api-8627 DEBUG Received notification about connection from `V8XX'.
Jul 07 21:05:13-240164 cadet-p2p-8627 INFO CONNECTED GN10 <= V8XX
Jul 07 21:05:13-240411 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:05:13-240619 util-scheduler-8627 DEBUG Adding task: 40 / 0x4d50e20
Jul 07 21:05:13-240831 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:05:13-241007 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:05:13-241177 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-241410 util-scheduler-8627 DEBUG Adding task: 41 / 0x4662140
Jul 07 21:05:13-241605 util-scheduler-8627 DEBUG Running task: 31 / 0x465ef00
Jul 07 21:05:13-241796 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:05:13-242021 nse-api-8627 DEBUG Received information about peer `KNAS' from peerinfo database
Jul 07 21:05:13-242439 cadet-hll-8627 DEBUG  hello for KNAS (64 bytes), expires on Tue Jul 08 08:48:16 2014
Jul 07 21:05:13-243097 cadet-p2p-8627 DEBUG set hello for KNAS
Jul 07 21:05:13-243278 cadet-p2p-8627 DEBUG  new (64 bytes)
Jul 07 21:05:13-243489 util-scheduler-8627 DEBUG Adding task: 42 / 0x465ef00
Jul 07 21:05:13-243727 util-scheduler-8627 DEBUG Checking readiness of task: 40 / 0x4d50e20
Jul 07 21:05:13-243922 util-scheduler-8627 DEBUG Running task: 40 / 0x4d50e20
Jul 07 21:05:13-244107 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:05:13-244297 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-244469 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-244679 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:05:13-244938 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:05:13-245147 util-scheduler-8627 DEBUG Running task: 42 / 0x465ef00
Jul 07 21:05:13-245365 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:05:13-245590 nse-api-8627 DEBUG Received information about peer `P00P' from peerinfo database
Jul 07 21:05:13-245852 cadet-hll-8627 DEBUG  hello for P00P (64 bytes), expires on Tue Jul 08 08:45:58 2014
Jul 07 21:05:13-246082 cadet-p2p-8627 DEBUG set hello for P00P
Jul 07 21:05:13-246254 cadet-p2p-8627 DEBUG  new (64 bytes)
Jul 07 21:05:13-246461 util-scheduler-8627 DEBUG Adding task: 43 / 0x465ef00
Jul 07 21:05:13-246656 util-scheduler-8627 DEBUG Running task: 41 / 0x4662140
Jul 07 21:05:13-246843 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:05:13-247140 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:05:13-247354 core-api-8627 DEBUG Received notification about connection from `D3TJ'.
Jul 07 21:05:13-247600 cadet-p2p-8627 INFO CONNECTED GN10 <= D3TJ
Jul 07 21:05:13-247845 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:05:13-248052 util-scheduler-8627 DEBUG Adding task: 44 / 0x4d50e20
Jul 07 21:05:13-248264 cadet-p2p-8627 DEBUG adding path [2] to peer D3TJ
Jul 07 21:05:13-248440 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:05:13-248610 cadet-p2p-8627 DEBUG   added last
Jul 07 21:05:13-248794 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:13-249003 util-scheduler-8627 DEBUG Adding task: 45 / 0x4661f98
Jul 07 21:05:13-249226 util-scheduler-8627 DEBUG Running task: 37 / 0x4663e08
Jul 07 21:05:13-249419 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-249633 util-scheduler-8627 DEBUG Adding task: 46 / 0x4663e08
Jul 07 21:05:13-249854 transport-api-8627 DEBUG Receiving `CONNECT' message for `STRN'.
Jul 07 21:05:13-250061 transport-api-8627 DEBUG Creating entry for neighbour `STRN'.
Jul 07 21:05:13-250249 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-250438 util-bandwidth-8627 DEBUG Tracker 0x4d57148 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-250654 util-scheduler-8627 DEBUG Adding task: 47 / 0x4d57148
Jul 07 21:05:13-250872 transport-api-8627 DEBUG Receiving `CONNECT' message for `STRN' with quota 8098
Jul 07 21:05:13-251060 util-bandwidth-8627 DEBUG Tracker 0x4d57148 bandwidth changed to 8098 Bps
Jul 07 21:05:13-251287 util-bandwidth-8627 DEBUG Tracker 0x4d57148 updated, have 1024 Bps, last update was 814 µs ago
Jul 07 21:05:13-251762 util-scheduler-8627 DEBUG Canceling task: 47 / 0x4d57148
Jul 07 21:05:13-251981 util-scheduler-8627 DEBUG Adding task: 48 / 0x4d57148
Jul 07 21:05:13-252219 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-252523 util-scheduler-8627 DEBUG Checking readiness of task: 44 / 0x4d50e20
Jul 07 21:05:13-252985 util-scheduler-8627 DEBUG Running task: 44 / 0x4d50e20
Jul 07 21:05:13-253177 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:05:13-253381 util-8627 DEBUG process_notify is running
Jul 07 21:05:13-253564 util-8627 DEBUG client_notify is running
Jul 07 21:05:13-253774 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:05:13-254023 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:05:13-254233 util-scheduler-8627 DEBUG Running task: 46 / 0x4663e08
Jul 07 21:05:13-254422 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-254636 util-scheduler-8627 DEBUG Adding task: 49 / 0x4663e08
Jul 07 21:05:13-254861 transport-api-8627 DEBUG Receiving `CONNECT' message for `TZQE'.
Jul 07 21:05:13-255069 transport-api-8627 DEBUG Creating entry for neighbour `TZQE'.
Jul 07 21:05:13-255256 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-255444 util-bandwidth-8627 DEBUG Tracker 0x4d579d0 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-255660 util-scheduler-8627 DEBUG Adding task: 50 / 0x4d579d0
Jul 07 21:05:13-255877 transport-api-8627 DEBUG Receiving `CONNECT' message for `TZQE' with quota 8873
Jul 07 21:05:13-256067 util-bandwidth-8627 DEBUG Tracker 0x4d579d0 bandwidth changed to 8873 Bps
Jul 07 21:05:13-256293 util-bandwidth-8627 DEBUG Tracker 0x4d579d0 updated, have 1024 Bps, last update was 815 µs ago
Jul 07 21:05:13-256497 util-scheduler-8627 DEBUG Canceling task: 50 / 0x4d579d0
Jul 07 21:05:13-256707 util-scheduler-8627 DEBUG Adding task: 51 / 0x4d579d0
Jul 07 21:05:13-256902 util-scheduler-8627 DEBUG Running task: 43 / 0x465ef00
Jul 07 21:05:13-257091 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:05:13-257358 nse-api-8627 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 21:05:13-257623 cadet-hll-8627 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 08:47:56 2014
Jul 07 21:05:13-257844 cadet-p2p-8627 DEBUG set hello for STRN
Jul 07 21:05:13-258016 cadet-p2p-8627 DEBUG  new (90 bytes)
Jul 07 21:05:13-258225 util-scheduler-8627 DEBUG Adding task: 52 / 0x465ef00
Jul 07 21:05:13-258457 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-258649 util-scheduler-8627 DEBUG Running task: 52 / 0x465ef00
Jul 07 21:05:13-258838 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-259063 nse-api-8627 DEBUG Received information about peer `Z0PW' from peerinfo database
Jul 07 21:05:13-259320 cadet-hll-8627 DEBUG  hello for Z0PW (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-259549 cadet-p2p-8627 DEBUG set hello for Z0PW
Jul 07 21:05:13-259722 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-259928 util-scheduler-8627 DEBUG Adding task: 53 / 0x465ef00
Jul 07 21:05:13-260123 util-scheduler-8627 DEBUG Running task: 49 / 0x4663e08
Jul 07 21:05:13-260313 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:05:13-260502 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:13-260702 util-scheduler-8627 DEBUG Adding task: 54 / 0x4663c60
Jul 07 21:05:13-260913 transport-api-8627 DEBUG Receiving `CONNECT' message for `V8XX'.
Jul 07 21:05:13-261118 transport-api-8627 DEBUG Creating entry for neighbour `V8XX'.
Jul 07 21:05:13-261332 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:05:13-261523 util-bandwidth-8627 DEBUG Tracker 0x4d58a00 initialized with 1024 Bps and max carry 5
Jul 07 21:05:13-261739 util-scheduler-8627 DEBUG Adding task: 55 / 0x4d58a00
Jul 07 21:05:13-261955 transport-api-8627 DEBUG Receiving `CONNECT' message for `V8XX' with quota 9260
Jul 07 21:05:13-262143 util-bandwidth-8627 DEBUG Tracker 0x4d58a00 bandwidth changed to 9260 Bps
Jul 07 21:05:13-262368 util-bandwidth-8627 DEBUG Tracker 0x4d58a00 updated, have 1024 Bps, last update was 812 µs ago
Jul 07 21:05:13-262574 util-scheduler-8627 DEBUG Canceling task: 55 / 0x4d58a00
Jul 07 21:05:13-262782 util-scheduler-8627 DEBUG Adding task: 56 / 0x4d58a00
Jul 07 21:05:13-263012 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-263201 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-263390 util-scheduler-8627 DEBUG Running task: 53 / 0x465ef00
Jul 07 21:05:13-263578 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-263799 nse-api-8627 DEBUG Received information about peer `Z2YH' from peerinfo database
Jul 07 21:05:13-264064 cadet-hll-8627 DEBUG  hello for Z2YH (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-264410 cadet-p2p-8627 DEBUG set hello for Z2YH
Jul 07 21:05:13-264603 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-264814 util-scheduler-8627 DEBUG Adding task: 57 / 0x465ef00
Jul 07 21:05:13-265053 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-265270 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-265461 util-scheduler-8627 DEBUG Running task: 57 / 0x465ef00
Jul 07 21:05:13-265651 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-265877 nse-api-8627 DEBUG Received information about peer `Z1WM' from peerinfo database
Jul 07 21:05:13-266134 cadet-hll-8627 DEBUG  hello for Z1WM (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-266605 cadet-p2p-8627 DEBUG set hello for Z1WM
Jul 07 21:05:13-266785 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-266994 util-scheduler-8627 DEBUG Adding task: 58 / 0x465ef00
Jul 07 21:05:13-267227 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-267418 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-267608 util-scheduler-8627 DEBUG Running task: 58 / 0x465ef00
Jul 07 21:05:13-267797 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-268020 nse-api-8627 DEBUG Received information about peer `F151' from peerinfo database
Jul 07 21:05:13-268277 cadet-hll-8627 DEBUG  hello for F151 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-268515 cadet-p2p-8627 DEBUG set hello for F151
Jul 07 21:05:13-268688 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-268899 util-scheduler-8627 DEBUG Adding task: 59 / 0x465ef00
Jul 07 21:05:13-269138 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-269361 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-269552 util-scheduler-8627 DEBUG Running task: 59 / 0x465ef00
Jul 07 21:05:13-269741 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-269964 nse-api-8627 DEBUG Received information about peer `FKFC' from peerinfo database
Jul 07 21:05:13-270231 cadet-hll-8627 DEBUG  hello for FKFC (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-270461 cadet-p2p-8627 DEBUG set hello for FKFC
Jul 07 21:05:13-270633 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-270839 util-scheduler-8627 DEBUG Adding task: 60 / 0x465ef00
Jul 07 21:05:13-271070 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-271260 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-271449 util-scheduler-8627 DEBUG Running task: 60 / 0x465ef00
Jul 07 21:05:13-271638 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-271859 nse-api-8627 DEBUG Received information about peer `FMX4' from peerinfo database
Jul 07 21:05:13-272114 cadet-hll-8627 DEBUG  hello for FMX4 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-272995 cadet-p2p-8627 DEBUG set hello for FMX4
Jul 07 21:05:13-273180 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-273430 util-scheduler-8627 DEBUG Adding task: 61 / 0x465ef00
Jul 07 21:05:13-273664 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-273856 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-274045 util-scheduler-8627 DEBUG Running task: 61 / 0x465ef00
Jul 07 21:05:13-274250 util-8627 DEBUG Received message of type 332 and size 578 from peerinfo service.
Jul 07 21:05:13-274484 nse-api-8627 DEBUG Received information about peer `GN10' from peerinfo database
Jul 07 21:05:13-274761 cadet-hll-8627 DEBUG  hello for GN10 (538 bytes), expires on Tue Jul 08 08:58:56 2014
Jul 07 21:05:13-274976 cadet-p2p-8627 DEBUG set hello for GN10
Jul 07 21:05:13-275148 cadet-p2p-8627 DEBUG  new (538 bytes)
Jul 07 21:05:13-277574 cadet-hll-8627 DEBUG  updated mine to 0x4d5b2e8
Jul 07 21:05:13-277791 util-scheduler-8627 DEBUG Adding task: 62 / 0x465ef00
Jul 07 21:05:13-278042 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-278235 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-278429 util-scheduler-8627 DEBUG Running task: 62 / 0x465ef00
Jul 07 21:05:13-278620 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:05:13-278841 nse-api-8627 DEBUG Received information about peer `QCZ4' from peerinfo database
Jul 07 21:05:13-279109 cadet-hll-8627 DEBUG  hello for QCZ4 (64 bytes), expires on Tue Jul 08 09:04:20 2014
Jul 07 21:05:13-279341 cadet-p2p-8627 DEBUG set hello for QCZ4
Jul 07 21:05:13-279519 cadet-p2p-8627 DEBUG  new (64 bytes)
Jul 07 21:05:13-279726 util-scheduler-8627 DEBUG Adding task: 63 / 0x465ef00
Jul 07 21:05:13-279956 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-280147 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-280337 util-scheduler-8627 DEBUG Running task: 63 / 0x465ef00
Jul 07 21:05:13-280528 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:05:13-280753 nse-api-8627 DEBUG Received information about peer `TZQE' from peerinfo database
Jul 07 21:05:13-281014 cadet-hll-8627 DEBUG  hello for TZQE (90 bytes), expires on Tue Jul 08 08:50:58 2014
Jul 07 21:05:13-281257 cadet-p2p-8627 DEBUG set hello for TZQE
Jul 07 21:05:13-281432 cadet-p2p-8627 DEBUG  new (90 bytes)
Jul 07 21:05:13-281648 util-scheduler-8627 DEBUG Adding task: 64 / 0x465ef00
Jul 07 21:05:13-281884 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-282074 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-282267 util-scheduler-8627 DEBUG Running task: 64 / 0x465ef00
Jul 07 21:05:13-282455 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-282673 nse-api-8627 DEBUG Received information about peer `ZHQ4' from peerinfo database
Jul 07 21:05:13-282933 cadet-hll-8627 DEBUG  hello for ZHQ4 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-283168 cadet-p2p-8627 DEBUG set hello for ZHQ4
Jul 07 21:05:13-283341 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-283547 util-scheduler-8627 DEBUG Adding task: 65 / 0x465ef00
Jul 07 21:05:13-283785 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-283976 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-284165 util-scheduler-8627 DEBUG Running task: 65 / 0x465ef00
Jul 07 21:05:13-284353 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-284570 nse-api-8627 DEBUG Received information about peer `F61H' from peerinfo database
Jul 07 21:05:13-284829 cadet-hll-8627 DEBUG  hello for F61H (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-285060 cadet-p2p-8627 DEBUG set hello for F61H
Jul 07 21:05:13-285258 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-285466 util-scheduler-8627 DEBUG Adding task: 66 / 0x465ef00
Jul 07 21:05:13-285696 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-285891 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-286081 util-scheduler-8627 DEBUG Running task: 66 / 0x465ef00
Jul 07 21:05:13-286270 util-8627 DEBUG Received message of type 332 and size 422 from peerinfo service.
Jul 07 21:05:13-286490 nse-api-8627 DEBUG Received information about peer `V8XX' from peerinfo database
Jul 07 21:05:13-286726 cadet-hll-8627 DEBUG  hello for V8XX (382 bytes), expires on end of time
Jul 07 21:05:13-286937 cadet-p2p-8627 DEBUG set hello for V8XX
Jul 07 21:05:13-287113 cadet-p2p-8627 DEBUG  new (382 bytes)
Jul 07 21:05:13-287332 util-scheduler-8627 DEBUG Adding task: 67 / 0x465ef00
Jul 07 21:05:13-287563 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-287753 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-287956 util-scheduler-8627 DEBUG Running task: 67 / 0x465ef00
Jul 07 21:05:13-288151 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:05:13-288374 nse-api-8627 DEBUG Received information about peer `WAKN' from peerinfo database
Jul 07 21:05:13-288640 cadet-hll-8627 DEBUG  hello for WAKN (90 bytes), expires on Tue Jul 08 09:04:58 2014
Jul 07 21:05:13-288872 cadet-p2p-8627 DEBUG set hello for WAKN
Jul 07 21:05:13-289047 cadet-p2p-8627 DEBUG  new (90 bytes)
Jul 07 21:05:13-289284 util-scheduler-8627 DEBUG Adding task: 68 / 0x465ef00
Jul 07 21:05:13-289516 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-289706 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-289895 util-scheduler-8627 DEBUG Running task: 68 / 0x465ef00
Jul 07 21:05:13-290084 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-290301 nse-api-8627 DEBUG Received information about peer `YXNW' from peerinfo database
Jul 07 21:05:13-290558 cadet-hll-8627 DEBUG  hello for YXNW (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-290788 cadet-p2p-8627 DEBUG set hello for YXNW
Jul 07 21:05:13-290961 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-291167 util-scheduler-8627 DEBUG Adding task: 69 / 0x465ef00
Jul 07 21:05:13-291402 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:13-291592 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:13-291781 util-scheduler-8627 DEBUG Running task: 69 / 0x465ef00
Jul 07 21:05:13-291970 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:05:13-292184 nse-api-8627 DEBUG Received information about peer `Z1SP' from peerinfo database
Jul 07 21:05:13-292443 cadet-hll-8627 DEBUG  hello for Z1SP (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:05:13-292678 cadet-p2p-8627 DEBUG set hello for Z1SP
Jul 07 21:05:13-292860 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:05:13-293043 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:13-293275 util-scheduler-8627 DEBUG Adding task: 70 / 0x465ed58
Jul 07 21:05:14-046637 util-scheduler-8627 DEBUG Checking readiness of task: 70 / 0x465ed58
Jul 07 21:05:14-046991 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:14-047188 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:14-047385 util-scheduler-8627 DEBUG Running task: 13 / (nil)
Jul 07 21:05:14-047793 cadet-dht-8627 DEBUG Announce ID
Jul 07 21:05:14-048131 cadet-hll-8627 DEBUG  mine is 0x4d5b2e8
Jul 07 21:05:14-050001 cadet-dht-8627 DEBUG Hello 0x4d5b2e8 size: 538
Jul 07 21:05:14-052870 util-scheduler-8627 DEBUG Adding task: 71 / 0x4d5e380
Jul 07 21:05:14-060097 util-8627 DEBUG Scheduling transmission (0x4665ad8).
Jul 07 21:05:14-060326 util-scheduler-8627 DEBUG Adding task: 72 / 0x4665ad8
Jul 07 21:05:14-061325 util-scheduler-8627 DEBUG Adding task: 73 / (nil)
Jul 07 21:05:14-061841 util-scheduler-8627 DEBUG Checking readiness of task: 72 / 0x4665ad8
Jul 07 21:05:14-062042 util-scheduler-8627 DEBUG Checking readiness of task: 70 / 0x465ed58
Jul 07 21:05:14-062237 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:14-062430 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:14-062625 util-scheduler-8627 DEBUG Running task: 72 / 0x4665ad8
Jul 07 21:05:14-062813 util-8627 DEBUG transmit_ready running (0x4665ad8).
Jul 07 21:05:14-063008 util-8627 DEBUG process_notify is running
Jul 07 21:05:14-063184 util-8627 DEBUG client_notify is running
Jul 07 21:05:14-067312 dht-api-8627 DEBUG Forwarded request of 634 bytes to DHT service
Jul 07 21:05:14-068492 dht-api-8627 DEBUG Starting to process replies from DHT
Jul 07 21:05:14-069417 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:14-069638 util-scheduler-8627 DEBUG Adding task: 74 / 0x4665ad8
Jul 07 21:05:14-070075 util-8627 DEBUG Transmitting message of type 142 and size 634 to dht service.
Jul 07 21:05:14-070379 util-8627 DEBUG Connection transmitted 634/634 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665ad8)
Jul 07 21:05:14-071181 util-scheduler-8627 DEBUG Checking readiness of task: 74 / 0x4665ad8
Jul 07 21:05:14-071589 util-scheduler-8627 DEBUG Checking readiness of task: 70 / 0x465ed58
Jul 07 21:05:14-071787 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:14-071980 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:14-072180 util-scheduler-8627 DEBUG Running task: 74 / 0x4665ad8
Jul 07 21:05:14-072611 util-8627 DEBUG receive_ready read 16/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665ad8)!
Jul 07 21:05:14-072889 util-scheduler-8627 DEBUG Adding task: 75 / 0x4665c80
Jul 07 21:05:14-073170 util-scheduler-8627 DEBUG Checking readiness of task: 70 / 0x465ed58
Jul 07 21:05:14-073391 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:14-073583 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:14-073775 util-scheduler-8627 DEBUG Running task: 75 / 0x4665c80
Jul 07 21:05:14-073968 util-8627 DEBUG Received message of type 155 and size 16 from dht service.
Jul 07 21:05:14-075214 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:14-075445 util-scheduler-8627 DEBUG Adding task: 76 / 0x4665ad8
Jul 07 21:05:14-077908 util-scheduler-8627 DEBUG Canceling task: 71 / 0x4d5e380
Jul 07 21:05:17-466471 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:17-466847 util-scheduler-8627 DEBUG Checking readiness of task: 70 / 0x465ed58
Jul 07 21:05:17-467054 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:17-467247 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:17-467445 util-scheduler-8627 DEBUG Running task: 70 / 0x465ed58
Jul 07 21:05:17-467872 util-8627 DEBUG receive_ready read 104/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:05:17-468475 util-scheduler-8627 DEBUG Adding task: 77 / 0x465ef00
Jul 07 21:05:17-468760 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:17-468954 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:17-469146 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:17-469372 util-scheduler-8627 DEBUG Running task: 77 / 0x465ef00
Jul 07 21:05:17-469566 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:05:17-469808 nse-api-8627 DEBUG Received information about peer `P00P' from peerinfo database
Jul 07 21:05:17-470094 cadet-hll-8627 DEBUG  hello for P00P (64 bytes), expires on Tue Jul 08 09:05:17 2014
Jul 07 21:05:17-470320 cadet-p2p-8627 DEBUG set hello for P00P
Jul 07 21:05:17-484756 cadet-p2p-8627 DEBUG  merge into 0x4d5fa50 (64 bytes)
Jul 07 21:05:17-485508 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:17-485734 util-scheduler-8627 DEBUG Adding task: 78 / 0x465ed58
Jul 07 21:05:18-594196 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:18-594540 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:18-595840 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:18-596270 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:18-596490 util-scheduler-8627 DEBUG Running task: 27 / 0x4d51d68
Jul 07 21:05:19-239962 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:19-240297 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:19-240492 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:19-240684 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:19-240877 util-scheduler-8627 DEBUG Running task: 36 / 0x4d54488
Jul 07 21:05:20-341047 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:20-341468 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:20-341665 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:20-341857 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:20-342051 util-scheduler-8627 DEBUG Running task: 56 / 0x4d58a00
Jul 07 21:05:20-642777 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:20-643020 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:20-643233 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:20-643475 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:20-643667 util-scheduler-8627 DEBUG Running task: 51 / 0x4d579d0
Jul 07 21:05:21-313463 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:21-313754 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:21-313948 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:21-314138 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:21-314331 util-scheduler-8627 DEBUG Running task: 39 / 0x4d54cd0
Jul 07 21:05:21-344593 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:21-344793 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:21-344985 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:21-345176 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:21-345385 util-scheduler-8627 DEBUG Running task: 48 / 0x4d57148
Jul 07 21:05:44-559035 util-scheduler-8627 DEBUG Checking readiness of task: 78 / 0x465ed58
Jul 07 21:05:44-559433 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:44-559630 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:44-559823 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:44-560021 util-scheduler-8627 DEBUG Running task: 78 / 0x465ed58
Jul 07 21:05:44-560448 util-8627 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:05:44-560708 util-scheduler-8627 DEBUG Adding task: 79 / 0x465ef00
Jul 07 21:05:44-560986 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:44-561178 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:44-561422 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:44-561613 util-scheduler-8627 DEBUG Running task: 79 / 0x465ef00
Jul 07 21:05:44-561806 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:05:44-562046 nse-api-8627 DEBUG Received information about peer `STRN' from peerinfo database
Jul 07 21:05:44-562336 cadet-hll-8627 DEBUG  hello for STRN (90 bytes), expires on Tue Jul 08 09:05:44 2014
Jul 07 21:05:44-562559 cadet-p2p-8627 DEBUG set hello for STRN
Jul 07 21:05:44-564088 cadet-p2p-8627 DEBUG  merge into 0x4d60908 (90 bytes)
Jul 07 21:05:44-564294 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:44-564512 util-scheduler-8627 DEBUG Adding task: 80 / 0x465ed58
Jul 07 21:05:44-685707 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:44-685979 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:44-686172 util-scheduler-8627 DEBUG Checking readiness of task: 54 / 0x4663c60
Jul 07 21:05:44-686366 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:44-686560 util-scheduler-8627 DEBUG Running task: 54 / 0x4663c60
Jul 07 21:05:44-686975 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:05:44-687216 util-scheduler-8627 DEBUG Adding task: 81 / 0x4663e08
Jul 07 21:05:44-687474 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:44-687701 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:44-687891 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:44-688080 util-scheduler-8627 DEBUG Running task: 81 / 0x4663e08
Jul 07 21:05:44-688271 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:05:44-688466 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:44-688669 util-scheduler-8627 DEBUG Adding task: 82 / 0x4663c60
Jul 07 21:05:44-689989 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:05:44-691964 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 8098
Jul 07 21:05:44-692431 util-bandwidth-8627 DEBUG Tracker 0x4d57148 bandwidth changed to 8098 Bps
Jul 07 21:05:44-694613 util-bandwidth-8627 DEBUG Tracker 0x4d57148 updated, have 8098 Bps, last update was 31 s ago
Jul 07 21:05:44-695250 util-scheduler-8627 DEBUG Adding task: 83 / 0x4d57148
Jul 07 21:05:44-695732 util-scheduler-8627 DEBUG Checking readiness of task: 82 / 0x4663c60
Jul 07 21:05:44-695930 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:44-696123 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:44-696330 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:44-696521 util-scheduler-8627 DEBUG Running task: 83 / 0x4d57148
Jul 07 21:05:56-250162 util-scheduler-8627 DEBUG Checking readiness of task: 82 / 0x4663c60
Jul 07 21:05:56-250556 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:56-250753 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:56-250945 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:56-251142 util-scheduler-8627 DEBUG Running task: 82 / 0x4663c60
Jul 07 21:05:56-251567 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:05:56-251824 util-scheduler-8627 DEBUG Adding task: 84 / 0x4663e08
Jul 07 21:05:56-252100 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:56-252292 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:56-252481 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:56-252671 util-scheduler-8627 DEBUG Running task: 84 / 0x4663e08
Jul 07 21:05:56-252863 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:05:56-253059 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:05:56-253301 util-scheduler-8627 DEBUG Adding task: 85 / 0x4663c60
Jul 07 21:05:56-253675 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:05:56-254018 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 8098
Jul 07 21:05:56-254216 util-bandwidth-8627 DEBUG Tracker 0x4d57148 bandwidth changed to 8098 Bps
Jul 07 21:05:56-254477 util-bandwidth-8627 DEBUG Tracker 0x4d57148 updated, have 8098 Bps, last update was 11 s ago
Jul 07 21:05:56-254698 util-scheduler-8627 DEBUG Adding task: 86 / 0x4d57148
Jul 07 21:05:56-254938 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:05:56-255129 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:05:56-255318 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:05:56-255507 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:05:56-255696 util-scheduler-8627 DEBUG Running task: 86 / 0x4d57148
Jul 07 21:06:19-249239 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:19-249616 util-scheduler-8627 DEBUG Checking readiness of task: 80 / 0x465ed58
Jul 07 21:06:19-249812 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:19-250003 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:06:19-250209 util-scheduler-8627 DEBUG Running task: 80 / 0x465ed58
Jul 07 21:06:19-250669 util-8627 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:06:19-250927 util-scheduler-8627 DEBUG Adding task: 87 / 0x465ef00
Jul 07 21:06:19-251204 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:19-251402 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:19-251597 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:06:19-251791 util-scheduler-8627 DEBUG Running task: 87 / 0x465ef00
Jul 07 21:06:19-251986 util-8627 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 21:06:19-252236 nse-api-8627 DEBUG Received information about peer `ZGV0' from peerinfo database
Jul 07 21:06:19-253386 cadet-hll-8627 DEBUG  hello with id 0xbee5e888 and msg (nil)
Jul 07 21:06:19-253871 util-scheduler-8627 DEBUG Adding task: 88 / 0x465ef00
Jul 07 21:06:19-254125 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:19-254319 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:19-254510 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:06:19-254700 util-scheduler-8627 DEBUG Running task: 88 / 0x465ef00
Jul 07 21:06:19-254891 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:06:19-255133 nse-api-8627 DEBUG Received information about peer `ZGV0' from peerinfo database
Jul 07 21:06:19-255404 cadet-hll-8627 DEBUG  hello for ZGV0 (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:06:19-255663 cadet-p2p-8627 DEBUG set hello for ZGV0
Jul 07 21:06:19-255839 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:06:19-256026 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:19-256239 util-scheduler-8627 DEBUG Adding task: 89 / 0x465ed58
Jul 07 21:06:47-470366 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-470760 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-470956 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-471147 util-scheduler-8627 DEBUG Checking readiness of task: 45 / 0x4661f98
Jul 07 21:06:47-471347 util-scheduler-8627 DEBUG Running task: 45 / 0x4661f98
Jul 07 21:06:47-471769 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:47-472026 util-scheduler-8627 DEBUG Adding task: 90 / 0x4662140
Jul 07 21:06:47-472302 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-472494 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-472683 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-472873 util-scheduler-8627 DEBUG Running task: 90 / 0x4662140
Jul 07 21:06:47-473064 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:06:47-473305 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:06:47-475249 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:06:47-478705 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:06:47-484860 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:06:47-486230 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:06:47-488865 cadet-con-8627 DEBUG   Creating path...
Jul 07 21:06:47-490494 cadet-con-8627 DEBUG   - 0: taking V8XX
Jul 07 21:06:47-491779 cadet-con-8627 DEBUG     storing at 0
Jul 07 21:06:47-492519 cadet-con-8627 DEBUG   - 1: taking GN10
Jul 07 21:06:47-493187 cadet-con-8627 DEBUG     storing at 1
Jul 07 21:06:47-494636 cadet-con-8627 DEBUG   Own position: 1
Jul 07 21:06:47-495577 cadet-con-8627 DEBUG   Creating connection
Jul 07 21:06:47-505833 cadet-con-8627 DEBUG  get next hop VF7F4W30 [1/2]
Jul 07 21:06:47-507296 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:06:47-509606 cadet-con-8627 DEBUG  get prev hop VF7F4W30 [1/2]
Jul 07 21:06:47-511119 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:06:47-512705 cadet-con-8627 DEBUG register neighbors for connection VF7F4W30
Jul 07 21:06:47-513833 cadet-8627 DEBUG PATH:
Jul 07 21:06:47-515183 cadet-8627 DEBUG   V8XX
Jul 07 21:06:47-515640 cadet-8627 DEBUG   GN10
Jul 07 21:06:47-516497 cadet-8627 DEBUG END
Jul 07 21:06:47-517641 cadet-con-8627 DEBUG own pos 1
Jul 07 21:06:47-518846 cadet-con-8627 DEBUG putting connection VF7F4W30 to next peer 0x4d4e270
Jul 07 21:06:47-520027 cadet-con-8627 DEBUG next peer 0x4d4e270 GN10
Jul 07 21:06:47-521252 cadet-con-8627 DEBUG putting connection VF7F4W30 to prev peer 0x4d55378
Jul 07 21:06:47-522429 cadet-con-8627 DEBUG prev peer 0x4d55378 V8XX
Jul 07 21:06:47-524621 cadet-p2p-8627 DEBUG adding connection VF7F4W30
Jul 07 21:06:47-525786 cadet-p2p-8627 DEBUG to peer GN10
Jul 07 21:06:47-527431 cadet-p2p-8627 DEBUG peer GN10 ok, has 0 connections.
Jul 07 21:06:47-529689 cadet-p2p-8627 DEBUG  now has 1 connections.
Jul 07 21:06:47-530630 cadet-p2p-8627 DEBUG result 1
Jul 07 21:06:47-531486 cadet-p2p-8627 DEBUG adding connection VF7F4W30
Jul 07 21:06:47-531847 cadet-p2p-8627 DEBUG to peer V8XX
Jul 07 21:06:47-532207 cadet-p2p-8627 DEBUG peer V8XX ok, has 0 connections.
Jul 07 21:06:47-532552 cadet-p2p-8627 DEBUG  now has 1 connections.
Jul 07 21:06:47-532886 cadet-p2p-8627 DEBUG result 1
Jul 07 21:06:47-535478 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:06:47-536684 util-scheduler-8627 DEBUG Adding task: 91 / 0x4d62e70
Jul 07 21:06:47-538752 cadet-con-8627 DEBUG Connection VF7F4W30 state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 21:06:47-541066 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:06:47-543316 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:06:47-543503 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:06:47-545033 cadet-p2p-8627 DEBUG   already known
Jul 07 21:06:47-552231 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:06:47-553525 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:06:47-555041 util-scheduler-8627 DEBUG Adding task: 92 / 0x4d63d80
Jul 07 21:06:47-557552 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_NEW => CADET_TUNNEL_WAITING
Jul 07 21:06:47-559903 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:06:47-560614 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:06:47-560980 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:06:47-564802 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:06:47-566041 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:06:47-567814 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:06:47-569003 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:06:47-570413 cadet-con-8627 DEBUG  sendable
Jul 07 21:06:47-573261 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:06:47-576973 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:06:47-579569 util-scheduler-8627 DEBUG Adding task: 93 / 0x4d55220
Jul 07 21:06:47-580740 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:06:47-582736 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:47-583777 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:06:47-584806 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:06:47-586963 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:06:47-588342 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:06:47-589349 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:06:47-590645 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:47-592220 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_SENT
Jul 07 21:06:47-592830 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:06:47-594175 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:47-594419 util-scheduler-8627 DEBUG Adding task: 94 / 0x4661f98
Jul 07 21:06:47-594684 util-scheduler-8627 DEBUG Checking readiness of task: 94 / 0x4661f98
Jul 07 21:06:47-594879 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-595070 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-595260 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-595452 util-scheduler-8627 DEBUG Running task: 93 / 0x4d55220
Jul 07 21:06:47-597425 util-scheduler-8627 DEBUG Adding task: 95 / 0x4d55220
Jul 07 21:06:47-601128 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:06:47-601679 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:47-601890 util-scheduler-8627 DEBUG Adding task: 96 / 0x4661f98
Jul 07 21:06:47-602092 util-scheduler-8627 DEBUG Running task: 92 / 0x4d63d80
Jul 07 21:06:47-603706 util-scheduler-8627 DEBUG Checking readiness of task: 96 / 0x4661f98
Jul 07 21:06:47-603906 util-scheduler-8627 DEBUG Checking readiness of task: 94 / 0x4661f98
Jul 07 21:06:47-604100 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-604291 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-604481 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-604673 util-scheduler-8627 DEBUG Running task: 96 / 0x4661f98
Jul 07 21:06:47-604859 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:47-605051 util-8627 DEBUG process_notify is running
Jul 07 21:06:47-605245 util-8627 DEBUG client_notify is running
Jul 07 21:06:47-605602 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:06:47-606248 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:47-606449 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:06:47-606715 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:06:47-606964 util-scheduler-8627 DEBUG Checking readiness of task: 94 / 0x4661f98
Jul 07 21:06:47-607157 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-607351 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-607540 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-607731 util-scheduler-8627 DEBUG Running task: 94 / 0x4661f98
Jul 07 21:06:47-608137 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:47-608390 util-scheduler-8627 DEBUG Adding task: 97 / 0x4662140
Jul 07 21:06:47-608636 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-608827 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-609016 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-609232 util-scheduler-8627 DEBUG Running task: 97 / 0x4662140
Jul 07 21:06:47-609425 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:06:47-609620 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:06:47-611374 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:06:47-612883 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:47-613091 util-scheduler-8627 DEBUG Adding task: 98 / 0x4661f98
Jul 07 21:06:47-613483 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:47-613690 util-scheduler-8627 DEBUG Adding task: 99 / 0x4661f98
Jul 07 21:06:47-613932 util-scheduler-8627 DEBUG Checking readiness of task: 99 / 0x4661f98
Jul 07 21:06:47-614125 util-scheduler-8627 DEBUG Checking readiness of task: 98 / 0x4661f98
Jul 07 21:06:47-614317 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:47-614506 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:47-614712 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:47-614904 util-scheduler-8627 DEBUG Running task: 98 / 0x4661f98
Jul 07 21:06:47-615088 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:47-615273 util-8627 DEBUG process_notify is running
Jul 07 21:06:47-615442 util-8627 DEBUG client_notify is running
Jul 07 21:06:47-616912 util-scheduler-8627 DEBUG Canceling task: 95 / 0x4d55220
Jul 07 21:06:47-618326 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:06:47-621353 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:06:47-622983 cadet-p2p-8627 DEBUG Checking 0x4d64628 towards VF7F4W30 (->V8XX)
Jul 07 21:06:47-625410 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:06:47-626469 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:06:47-627609 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:06:47-628813 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:06:47-630460 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:06:47-633091 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:06:47-635335 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:06:47-638805 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:06:47-640592 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:06:47-641846 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:06:47-644074 util-scheduler-8627 DEBUG Adding task: 100 / 0x4d62e70
Jul 07 21:06:47-645977 cadet-con-8627 DEBUG next keepalive in 1 s
Jul 07 21:06:47-647099 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:06:47-649372 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:06:47-650033 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:47-650368 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:06:47-650699 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:06:47-651129 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:47-652634 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:06:47-653812 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:06:47-654976 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:47-655402 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:06:47-655662 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:06:48-645180 util-scheduler-8627 DEBUG Checking readiness of task: 99 / 0x4661f98
Jul 07 21:06:48-645484 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:48-645678 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:48-645870 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:48-646062 util-scheduler-8627 DEBUG Running task: 100 / 0x4d62e70
Jul 07 21:06:48-647803 cadet-con-8627 DEBUG BCK keepalive for VF7F4W30 (->V8XX)
Jul 07 21:06:50-606366 util-scheduler-8627 DEBUG Checking readiness of task: 99 / 0x4661f98
Jul 07 21:06:50-606750 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-606946 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-607139 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-607336 util-scheduler-8627 DEBUG Running task: 99 / 0x4661f98
Jul 07 21:06:50-607762 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:50-608019 util-scheduler-8627 DEBUG Adding task: 101 / 0x4662140
Jul 07 21:06:50-608296 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-608488 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-608681 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-608870 util-scheduler-8627 DEBUG Running task: 101 / 0x4662140
Jul 07 21:06:50-609061 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:06:50-609332 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:06:50-609753 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:06:50-610071 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:06:50-610476 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:06:50-610777 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:06:50-612707 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:06:50-612941 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:06:50-613123 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:06:50-613431 cadet-p2p-8627 DEBUG   already known
Jul 07 21:06:50-613955 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:06:50-614313 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:06:50-615260 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:06:50-615504 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:06:50-615714 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:06:50-616169 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:06:50-616523 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:06:50-616909 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:06:50-617277 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:06:50-617621 cadet-con-8627 DEBUG  sendable
Jul 07 21:06:50-617928 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:06:50-618313 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:06:50-618538 util-scheduler-8627 DEBUG Adding task: 102 / 0x4d55220
Jul 07 21:06:50-618827 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:06:50-619042 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:50-619218 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:06:50-619394 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:06:50-619790 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:06:50-620140 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:06:50-620473 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:06:50-620682 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:50-620918 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:06:50-621171 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:06:50-621407 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:50-621622 util-scheduler-8627 DEBUG Adding task: 103 / 0x4661f98
Jul 07 21:06:50-621873 util-scheduler-8627 DEBUG Checking readiness of task: 103 / 0x4661f98
Jul 07 21:06:50-622066 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-622256 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-622445 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-622636 util-scheduler-8627 DEBUG Running task: 102 / 0x4d55220
Jul 07 21:06:50-622844 util-scheduler-8627 DEBUG Adding task: 104 / 0x4d55220
Jul 07 21:06:50-623179 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:06:50-623387 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:50-623591 util-scheduler-8627 DEBUG Adding task: 105 / 0x4661f98
Jul 07 21:06:50-623832 util-scheduler-8627 DEBUG Checking readiness of task: 105 / 0x4661f98
Jul 07 21:06:50-624026 util-scheduler-8627 DEBUG Checking readiness of task: 103 / 0x4661f98
Jul 07 21:06:50-624216 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-624405 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-624594 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-624786 util-scheduler-8627 DEBUG Running task: 105 / 0x4661f98
Jul 07 21:06:50-624990 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:50-625169 util-8627 DEBUG process_notify is running
Jul 07 21:06:50-625370 util-8627 DEBUG client_notify is running
Jul 07 21:06:50-625550 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:06:50-625747 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:50-625938 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:06:50-626193 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:06:50-626440 util-scheduler-8627 DEBUG Checking readiness of task: 103 / 0x4661f98
Jul 07 21:06:50-626631 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-626821 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-627010 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-627202 util-scheduler-8627 DEBUG Running task: 103 / 0x4661f98
Jul 07 21:06:50-627605 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:50-627831 util-scheduler-8627 DEBUG Adding task: 106 / 0x4662140
Jul 07 21:06:50-628074 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-628264 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-628453 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-628645 util-scheduler-8627 DEBUG Running task: 106 / 0x4662140
Jul 07 21:06:50-628834 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:06:50-629027 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:06:50-629404 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:06:50-629612 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:50-629811 util-scheduler-8627 DEBUG Adding task: 107 / 0x4661f98
Jul 07 21:06:50-629995 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:50-630194 util-scheduler-8627 DEBUG Adding task: 108 / 0x4661f98
Jul 07 21:06:50-630432 util-scheduler-8627 DEBUG Checking readiness of task: 108 / 0x4661f98
Jul 07 21:06:50-630634 util-scheduler-8627 DEBUG Checking readiness of task: 107 / 0x4661f98
Jul 07 21:06:50-630825 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:50-631014 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:50-631203 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:50-631393 util-scheduler-8627 DEBUG Running task: 107 / 0x4661f98
Jul 07 21:06:50-631577 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:50-631765 util-8627 DEBUG process_notify is running
Jul 07 21:06:50-631935 util-8627 DEBUG client_notify is running
Jul 07 21:06:50-632120 util-scheduler-8627 DEBUG Canceling task: 104 / 0x4d55220
Jul 07 21:06:50-632450 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:06:50-632826 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:06:50-633241 cadet-p2p-8627 DEBUG Checking 0x4d679f0 towards VF7F4W30 (->V8XX)
Jul 07 21:06:50-633571 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:06:50-633841 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:06:50-634105 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:06:50-634368 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:06:50-634633 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:06:50-634984 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:06:50-635333 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:06:50-635675 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:06:50-636020 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:06:50-636358 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:06:50-636828 util-scheduler-8627 DEBUG Adding task: 109 / 0x4d62e70
Jul 07 21:06:50-637254 cadet-con-8627 DEBUG next keepalive in 2 s
Jul 07 21:06:50-637584 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:06:50-637870 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:06:50-638077 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:50-638254 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:06:50-638430 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:06:50-638633 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:50-638942 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:06:50-639233 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:06:50-639418 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:50-639609 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:06:50-639857 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:06:52-638974 util-scheduler-8627 DEBUG Checking readiness of task: 108 / 0x4661f98
Jul 07 21:06:52-639344 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:52-639806 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:52-640038 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:52-640280 util-scheduler-8627 DEBUG Running task: 109 / 0x4d62e70
Jul 07 21:06:52-640787 cadet-con-8627 DEBUG BCK keepalive for VF7F4W30 (->V8XX)
Jul 07 21:06:58-057815 util-scheduler-8627 DEBUG Checking readiness of task: 108 / 0x4661f98
Jul 07 21:06:58-058206 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-058405 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-058599 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-058797 util-scheduler-8627 DEBUG Running task: 108 / 0x4661f98
Jul 07 21:06:58-059223 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:58-059505 util-scheduler-8627 DEBUG Adding task: 110 / 0x4662140
Jul 07 21:06:58-059784 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-059978 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-060170 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-060362 util-scheduler-8627 DEBUG Running task: 110 / 0x4662140
Jul 07 21:06:58-060556 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:06:58-060758 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:06:58-060990 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:06:58-061216 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:06:58-061525 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:06:58-061737 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:06:58-062003 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:06:58-062228 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:06:58-062410 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:06:58-062585 cadet-p2p-8627 DEBUG   already known
Jul 07 21:06:58-062828 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:06:58-063030 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:06:58-063259 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:06:58-063495 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:06:58-063705 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:06:58-064003 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:06:58-064201 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:06:58-064430 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:06:58-064649 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:06:58-064829 cadet-con-8627 DEBUG  sendable
Jul 07 21:06:58-065037 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:06:58-065279 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:06:58-065502 util-scheduler-8627 DEBUG Adding task: 111 / 0x4d55220
Jul 07 21:06:58-065684 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:06:58-065891 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:58-066068 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:06:58-066244 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:06:58-066497 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:06:58-066682 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:06:58-066860 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:06:58-067060 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:58-067295 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:06:58-067537 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:06:58-067744 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:58-067960 util-scheduler-8627 DEBUG Adding task: 112 / 0x4661f98
Jul 07 21:06:58-068207 util-scheduler-8627 DEBUG Checking readiness of task: 112 / 0x4661f98
Jul 07 21:06:58-068402 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-068594 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-068785 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-068977 util-scheduler-8627 DEBUG Running task: 111 / 0x4d55220
Jul 07 21:06:58-069187 util-scheduler-8627 DEBUG Adding task: 113 / 0x4d55220
Jul 07 21:06:58-069438 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:06:58-069643 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:58-069847 util-scheduler-8627 DEBUG Adding task: 114 / 0x4661f98
Jul 07 21:06:58-070089 util-scheduler-8627 DEBUG Checking readiness of task: 114 / 0x4661f98
Jul 07 21:06:58-070283 util-scheduler-8627 DEBUG Checking readiness of task: 112 / 0x4661f98
Jul 07 21:06:58-070475 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-070667 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-070859 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-071053 util-scheduler-8627 DEBUG Running task: 114 / 0x4661f98
Jul 07 21:06:58-071240 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:58-071420 util-8627 DEBUG process_notify is running
Jul 07 21:06:58-071595 util-8627 DEBUG client_notify is running
Jul 07 21:06:58-071776 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:06:58-071974 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:58-072167 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:06:58-072435 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:06:58-072684 util-scheduler-8627 DEBUG Checking readiness of task: 112 / 0x4661f98
Jul 07 21:06:58-072877 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-073069 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-073285 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-073479 util-scheduler-8627 DEBUG Running task: 112 / 0x4661f98
Jul 07 21:06:58-073882 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:06:58-074109 util-scheduler-8627 DEBUG Adding task: 115 / 0x4662140
Jul 07 21:06:58-074355 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-074563 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-074755 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-074946 util-scheduler-8627 DEBUG Running task: 115 / 0x4662140
Jul 07 21:06:58-075137 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:06:58-075332 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:06:58-075552 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:06:58-075765 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:06:58-075965 util-scheduler-8627 DEBUG Adding task: 116 / 0x4661f98
Jul 07 21:06:58-076149 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:06:58-076349 util-scheduler-8627 DEBUG Adding task: 117 / 0x4661f98
Jul 07 21:06:58-076587 util-scheduler-8627 DEBUG Checking readiness of task: 117 / 0x4661f98
Jul 07 21:06:58-076780 util-scheduler-8627 DEBUG Checking readiness of task: 116 / 0x4661f98
Jul 07 21:06:58-076972 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:06:58-077162 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:06:58-077379 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:06:58-077571 util-scheduler-8627 DEBUG Running task: 116 / 0x4661f98
Jul 07 21:06:58-077756 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:06:58-077932 util-8627 DEBUG process_notify is running
Jul 07 21:06:58-078103 util-8627 DEBUG client_notify is running
Jul 07 21:06:58-078288 util-scheduler-8627 DEBUG Canceling task: 113 / 0x4d55220
Jul 07 21:06:58-078512 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:06:58-078731 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:06:58-078963 cadet-p2p-8627 DEBUG Checking 0x4d6ac80 towards VF7F4W30 (->V8XX)
Jul 07 21:06:58-079197 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:06:58-079377 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:06:58-079548 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:06:58-079717 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:06:58-079889 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:06:58-080144 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:06:58-080338 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:06:58-080519 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:06:58-080708 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:06:58-080890 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:06:58-081099 util-scheduler-8627 DEBUG Adding task: 118 / 0x4d62e70
Jul 07 21:06:58-081367 cadet-con-8627 DEBUG next keepalive in 4 s
Jul 07 21:06:58-081539 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:06:58-081720 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:06:58-081919 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:06:58-082094 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:06:58-082269 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:06:58-082468 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:06:58-082673 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:06:58-082858 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:06:58-083037 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:06:58-083227 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:06:58-083474 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:02-085274 util-scheduler-8627 DEBUG Checking readiness of task: 117 / 0x4661f98
Jul 07 21:07:02-085637 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:02-085834 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:02-086028 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:02-086260 util-scheduler-8627 DEBUG Running task: 118 / 0x4d62e70
Jul 07 21:07:02-086555 cadet-con-8627 DEBUG BCK keepalive for VF7F4W30 (->V8XX)
Jul 07 21:07:10-719417 util-scheduler-8627 DEBUG Checking readiness of task: 117 / 0x4661f98
Jul 07 21:07:10-719834 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-720035 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-720240 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-720439 util-scheduler-8627 DEBUG Running task: 117 / 0x4661f98
Jul 07 21:07:10-720866 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:10-721122 util-scheduler-8627 DEBUG Adding task: 119 / 0x4662140
Jul 07 21:07:10-721434 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-721627 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-721817 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-722007 util-scheduler-8627 DEBUG Running task: 119 / 0x4662140
Jul 07 21:07:10-722199 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:07:10-722399 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:07:10-722629 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:07:10-722830 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:07:10-723070 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:07:10-723276 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:07:10-723491 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:07:10-723729 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:07:10-723909 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:07:10-724083 cadet-p2p-8627 DEBUG   already known
Jul 07 21:07:10-724324 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:07:10-724524 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:07:10-724751 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:07:10-724985 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:07:10-725216 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:07:10-725515 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:07:10-725711 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:07:10-725937 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:07:10-726119 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:07:10-726294 cadet-con-8627 DEBUG  sendable
Jul 07 21:07:10-726500 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:07:10-726736 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:07:10-726949 util-scheduler-8627 DEBUG Adding task: 120 / 0x4d55220
Jul 07 21:07:10-727128 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:07:10-727333 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:10-727508 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:07:10-727682 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:07:10-727919 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:07:10-728103 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:07:10-728279 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:07:10-728513 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:10-728772 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:07:10-729014 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:07:10-729283 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:10-729500 util-scheduler-8627 DEBUG Adding task: 121 / 0x4661f98
Jul 07 21:07:10-729777 util-scheduler-8627 DEBUG Checking readiness of task: 121 / 0x4661f98
Jul 07 21:07:10-729971 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-730160 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-730349 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-730541 util-scheduler-8627 DEBUG Running task: 120 / 0x4d55220
Jul 07 21:07:10-730749 util-scheduler-8627 DEBUG Adding task: 122 / 0x4d55220
Jul 07 21:07:10-730971 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:07:10-731174 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:10-731376 util-scheduler-8627 DEBUG Adding task: 123 / 0x4661f98
Jul 07 21:07:10-731616 util-scheduler-8627 DEBUG Checking readiness of task: 123 / 0x4661f98
Jul 07 21:07:10-731809 util-scheduler-8627 DEBUG Checking readiness of task: 121 / 0x4661f98
Jul 07 21:07:10-732000 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-732190 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-732380 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-732572 util-scheduler-8627 DEBUG Running task: 123 / 0x4661f98
Jul 07 21:07:10-732760 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:10-732938 util-8627 DEBUG process_notify is running
Jul 07 21:07:10-733111 util-8627 DEBUG client_notify is running
Jul 07 21:07:10-733336 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:07:10-733533 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:10-733724 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:07:10-733975 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:10-734222 util-scheduler-8627 DEBUG Checking readiness of task: 121 / 0x4661f98
Jul 07 21:07:10-734414 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-734603 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-734791 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-734980 util-scheduler-8627 DEBUG Running task: 121 / 0x4661f98
Jul 07 21:07:10-735381 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:10-735619 util-scheduler-8627 DEBUG Adding task: 124 / 0x4662140
Jul 07 21:07:10-735863 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-736053 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-736242 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-736430 util-scheduler-8627 DEBUG Running task: 124 / 0x4662140
Jul 07 21:07:10-736618 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:07:10-736811 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:07:10-737025 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:07:10-737243 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:10-737474 util-scheduler-8627 DEBUG Adding task: 125 / 0x4661f98
Jul 07 21:07:10-737669 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:10-737868 util-scheduler-8627 DEBUG Adding task: 126 / 0x4661f98
Jul 07 21:07:10-738105 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:10-738296 util-scheduler-8627 DEBUG Checking readiness of task: 125 / 0x4661f98
Jul 07 21:07:10-738486 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:10-738674 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:10-738863 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:10-739053 util-scheduler-8627 DEBUG Running task: 125 / 0x4661f98
Jul 07 21:07:10-739252 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:10-739427 util-8627 DEBUG process_notify is running
Jul 07 21:07:10-739596 util-8627 DEBUG client_notify is running
Jul 07 21:07:10-739780 util-scheduler-8627 DEBUG Canceling task: 122 / 0x4d55220
Jul 07 21:07:10-740002 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:07:10-740218 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:07:10-740449 cadet-p2p-8627 DEBUG Checking 0x4d6df10 towards VF7F4W30 (->V8XX)
Jul 07 21:07:10-740682 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:07:10-740860 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:07:10-741029 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:07:10-741218 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:07:10-741391 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:07:10-741649 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:07:10-741842 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:07:10-742021 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:07:10-742208 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:07:10-742388 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:07:10-742728 util-scheduler-8627 DEBUG Adding task: 127 / 0x4d62e70
Jul 07 21:07:10-742971 cadet-con-8627 DEBUG next keepalive in 8 s
Jul 07 21:07:10-743142 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:07:10-743322 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:07:10-743520 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:10-743693 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:07:10-743867 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:07:10-744065 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:10-744327 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:07:10-744513 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:07:10-744691 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:10-744880 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:07:10-745128 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:18-750892 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:18-751282 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:18-751478 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:18-751669 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:18-751863 util-scheduler-8627 DEBUG Running task: 127 / 0x4d62e70
Jul 07 21:07:18-752136 cadet-con-8627 DEBUG BCK keepalive for VF7F4W30 (->V8XX)
Jul 07 21:07:26-757453 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:26-757833 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:26-758028 util-scheduler-8627 DEBUG Checking readiness of task: 85 / 0x4663c60
Jul 07 21:07:26-758223 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:26-758421 util-scheduler-8627 DEBUG Running task: 85 / 0x4663c60
Jul 07 21:07:26-758846 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:07:26-759103 util-scheduler-8627 DEBUG Adding task: 128 / 0x4663e08
Jul 07 21:07:26-759380 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:26-759572 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:26-759765 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:26-759954 util-scheduler-8627 DEBUG Running task: 128 / 0x4663e08
Jul 07 21:07:26-760147 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:07:26-760345 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:26-760594 util-scheduler-8627 DEBUG Adding task: 129 / 0x4663c60
Jul 07 21:07:26-760783 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:07:26-761013 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `STRN' with quota 9216
Jul 07 21:07:26-761231 util-bandwidth-8627 DEBUG Tracker 0x4d57148 bandwidth changed to 9216 Bps
Jul 07 21:07:26-761500 util-bandwidth-8627 DEBUG Tracker 0x4d57148 updated, have 8098 Bps, last update was 90 s ago
Jul 07 21:07:26-761738 util-scheduler-8627 DEBUG Adding task: 130 / 0x4d57148
Jul 07 21:07:26-761976 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:26-762167 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:26-762356 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:26-762544 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:26-762734 util-scheduler-8627 DEBUG Running task: 130 / 0x4d57148
Jul 07 21:07:27-445753 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-446016 util-scheduler-8627 DEBUG Checking readiness of task: 126 / 0x4661f98
Jul 07 21:07:27-446211 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-446403 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-446597 util-scheduler-8627 DEBUG Running task: 126 / 0x4661f98
Jul 07 21:07:27-447007 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:27-447243 util-scheduler-8627 DEBUG Adding task: 131 / 0x4662140
Jul 07 21:07:27-447502 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-447694 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-447884 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-448073 util-scheduler-8627 DEBUG Running task: 131 / 0x4662140
Jul 07 21:07:27-448262 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:07:27-448460 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:07:27-448682 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:07:27-448880 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:07:27-449139 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:07:27-449373 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:07:27-449590 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:07:27-449813 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:07:27-449992 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:07:27-450165 cadet-p2p-8627 DEBUG   already known
Jul 07 21:07:27-450404 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:07:27-450605 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:07:27-450832 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:07:27-451066 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:07:27-451274 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:07:27-451568 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:07:27-451764 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:07:27-451990 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:07:27-452174 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:07:27-452350 cadet-con-8627 DEBUG  sendable
Jul 07 21:07:27-452556 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:07:27-452783 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:07:27-453003 util-scheduler-8627 DEBUG Adding task: 132 / 0x4d55220
Jul 07 21:07:27-453184 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:07:27-453411 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:27-453607 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:07:27-453782 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:07:27-454019 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:07:27-454204 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:07:27-454380 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:07:27-454578 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:27-454811 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:07:27-455052 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:07:27-455268 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:27-455475 util-scheduler-8627 DEBUG Adding task: 133 / 0x4661f98
Jul 07 21:07:27-455718 util-scheduler-8627 DEBUG Checking readiness of task: 133 / 0x4661f98
Jul 07 21:07:27-455910 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-456098 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-456287 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-456477 util-scheduler-8627 DEBUG Running task: 132 / 0x4d55220
Jul 07 21:07:27-456684 util-scheduler-8627 DEBUG Adding task: 134 / 0x4d55220
Jul 07 21:07:27-456905 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:07:27-457107 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:27-457329 util-scheduler-8627 DEBUG Adding task: 135 / 0x4661f98
Jul 07 21:07:27-457572 util-scheduler-8627 DEBUG Checking readiness of task: 135 / 0x4661f98
Jul 07 21:07:27-457764 util-scheduler-8627 DEBUG Checking readiness of task: 133 / 0x4661f98
Jul 07 21:07:27-457954 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-458143 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-458332 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-458524 util-scheduler-8627 DEBUG Running task: 135 / 0x4661f98
Jul 07 21:07:27-458709 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:27-458886 util-8627 DEBUG process_notify is running
Jul 07 21:07:27-459059 util-8627 DEBUG client_notify is running
Jul 07 21:07:27-459238 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:07:27-459433 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:27-459623 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:07:27-459871 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:27-460117 util-scheduler-8627 DEBUG Checking readiness of task: 133 / 0x4661f98
Jul 07 21:07:27-460308 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-460497 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-460685 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-460875 util-scheduler-8627 DEBUG Running task: 133 / 0x4661f98
Jul 07 21:07:27-461295 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:27-461520 util-scheduler-8627 DEBUG Adding task: 136 / 0x4662140
Jul 07 21:07:27-461764 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-461954 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-462142 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-462331 util-scheduler-8627 DEBUG Running task: 136 / 0x4662140
Jul 07 21:07:27-462519 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:07:27-462711 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:07:27-462925 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:07:27-463137 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:27-463335 util-scheduler-8627 DEBUG Adding task: 137 / 0x4661f98
Jul 07 21:07:27-463517 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:27-463714 util-scheduler-8627 DEBUG Adding task: 138 / 0x4661f98
Jul 07 21:07:27-463950 util-scheduler-8627 DEBUG Checking readiness of task: 138 / 0x4661f98
Jul 07 21:07:27-464141 util-scheduler-8627 DEBUG Checking readiness of task: 137 / 0x4661f98
Jul 07 21:07:27-464331 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:27-464520 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:27-464719 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:27-464909 util-scheduler-8627 DEBUG Running task: 137 / 0x4661f98
Jul 07 21:07:27-465092 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:27-465287 util-8627 DEBUG process_notify is running
Jul 07 21:07:27-465457 util-8627 DEBUG client_notify is running
Jul 07 21:07:27-465641 util-scheduler-8627 DEBUG Canceling task: 134 / 0x4d55220
Jul 07 21:07:27-465863 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:07:27-466092 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:07:27-466322 cadet-p2p-8627 DEBUG Checking 0x4d71940 towards VF7F4W30 (->V8XX)
Jul 07 21:07:27-466555 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:07:27-466733 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:07:27-466901 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:07:27-467069 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:07:27-467238 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:07:27-467496 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:07:27-467688 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:07:27-467867 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:07:27-468053 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:07:27-468233 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:07:27-468440 util-scheduler-8627 DEBUG Adding task: 139 / 0x4d62e70
Jul 07 21:07:27-468675 cadet-con-8627 DEBUG next keepalive in 16 s
Jul 07 21:07:27-468846 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:07:27-469025 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:07:27-469240 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:27-469415 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:07:27-469587 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:07:27-469785 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:27-469988 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:07:27-470171 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:07:27-470348 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:27-470535 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:07:27-470776 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:29-445141 util-scheduler-8627 DEBUG Checking readiness of task: 138 / 0x4661f98
Jul 07 21:07:29-445554 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:29-445766 util-scheduler-8627 DEBUG Checking readiness of task: 89 / 0x465ed58
Jul 07 21:07:29-445962 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:29-446159 util-scheduler-8627 DEBUG Running task: 89 / 0x465ed58
Jul 07 21:07:29-446584 util-8627 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:07:29-446842 util-scheduler-8627 DEBUG Adding task: 140 / 0x465ef00
Jul 07 21:07:29-447119 util-scheduler-8627 DEBUG Checking readiness of task: 138 / 0x4661f98
Jul 07 21:07:29-447310 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:29-447500 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:29-447713 util-scheduler-8627 DEBUG Running task: 140 / 0x465ef00
Jul 07 21:07:29-447907 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:07:29-448148 nse-api-8627 DEBUG Received information about peer `TZQE' from peerinfo database
Jul 07 21:07:29-448456 cadet-hll-8627 DEBUG  hello for TZQE (90 bytes), expires on Tue Jul 08 09:07:29 2014
Jul 07 21:07:29-448681 cadet-p2p-8627 DEBUG set hello for TZQE
Jul 07 21:07:29-448978 cadet-p2p-8627 DEBUG  merge into 0x4d74170 (90 bytes)
Jul 07 21:07:29-449173 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:29-452850 util-scheduler-8627 DEBUG Adding task: 141 / 0x465ed58
Jul 07 21:07:41-966192 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-966571 util-scheduler-8627 DEBUG Checking readiness of task: 138 / 0x4661f98
Jul 07 21:07:41-966769 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-966962 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-967159 util-scheduler-8627 DEBUG Running task: 138 / 0x4661f98
Jul 07 21:07:41-967582 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:41-967839 util-scheduler-8627 DEBUG Adding task: 142 / 0x4662140
Jul 07 21:07:41-968116 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-968308 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-968498 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-968688 util-scheduler-8627 DEBUG Running task: 142 / 0x4662140
Jul 07 21:07:41-968878 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:07:41-969079 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:07:41-969338 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:07:41-969539 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:07:41-969778 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:07:41-969985 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:07:41-970202 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:07:41-970422 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:07:41-970601 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:07:41-970773 cadet-p2p-8627 DEBUG   already known
Jul 07 21:07:41-971016 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:07:41-971216 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:07:41-971444 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:07:41-971679 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:07:41-971887 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:07:41-972180 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:07:41-972376 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:07:41-972623 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:07:41-972806 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:07:41-972981 cadet-con-8627 DEBUG  sendable
Jul 07 21:07:41-973187 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:07:41-973423 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:07:41-973639 util-scheduler-8627 DEBUG Adding task: 143 / 0x4d55220
Jul 07 21:07:41-973848 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:07:41-974051 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:41-974227 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:07:41-974401 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:07:41-974638 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:07:41-974822 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:07:41-975028 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:07:41-975228 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:41-975461 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:07:41-975702 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:07:41-975906 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:41-976121 util-scheduler-8627 DEBUG Adding task: 144 / 0x4661f98
Jul 07 21:07:41-976366 util-scheduler-8627 DEBUG Checking readiness of task: 144 / 0x4661f98
Jul 07 21:07:41-976557 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-976747 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-976936 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-977126 util-scheduler-8627 DEBUG Running task: 143 / 0x4d55220
Jul 07 21:07:41-977355 util-scheduler-8627 DEBUG Adding task: 145 / 0x4d55220
Jul 07 21:07:41-977578 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:07:41-977781 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:41-977982 util-scheduler-8627 DEBUG Adding task: 146 / 0x4661f98
Jul 07 21:07:41-978220 util-scheduler-8627 DEBUG Checking readiness of task: 146 / 0x4661f98
Jul 07 21:07:41-978413 util-scheduler-8627 DEBUG Checking readiness of task: 144 / 0x4661f98
Jul 07 21:07:41-978602 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-978804 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-978993 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-979184 util-scheduler-8627 DEBUG Running task: 146 / 0x4661f98
Jul 07 21:07:41-979369 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:41-979546 util-8627 DEBUG process_notify is running
Jul 07 21:07:41-979718 util-8627 DEBUG client_notify is running
Jul 07 21:07:41-979897 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:07:41-980093 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:41-980294 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:07:41-980543 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:07:41-980789 util-scheduler-8627 DEBUG Checking readiness of task: 144 / 0x4661f98
Jul 07 21:07:41-980985 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-981174 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-981384 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-981574 util-scheduler-8627 DEBUG Running task: 144 / 0x4661f98
Jul 07 21:07:41-981974 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:07:41-982199 util-scheduler-8627 DEBUG Adding task: 147 / 0x4662140
Jul 07 21:07:41-982443 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-982633 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-982822 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-983011 util-scheduler-8627 DEBUG Running task: 147 / 0x4662140
Jul 07 21:07:41-983199 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:07:41-983392 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:07:41-983606 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:07:41-983804 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:07:41-984000 util-scheduler-8627 DEBUG Adding task: 148 / 0x4661f98
Jul 07 21:07:41-984183 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:07:41-984380 util-scheduler-8627 DEBUG Adding task: 149 / 0x4661f98
Jul 07 21:07:41-984636 util-scheduler-8627 DEBUG Checking readiness of task: 149 / 0x4661f98
Jul 07 21:07:41-984828 util-scheduler-8627 DEBUG Checking readiness of task: 148 / 0x4661f98
Jul 07 21:07:41-985018 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:07:41-985228 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:07:41-985419 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:07:41-985610 util-scheduler-8627 DEBUG Running task: 148 / 0x4661f98
Jul 07 21:07:41-985793 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:07:41-985968 util-8627 DEBUG process_notify is running
Jul 07 21:07:41-986136 util-8627 DEBUG client_notify is running
Jul 07 21:07:41-986320 util-scheduler-8627 DEBUG Canceling task: 145 / 0x4d55220
Jul 07 21:07:41-986541 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:07:41-986758 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:07:41-986988 cadet-p2p-8627 DEBUG Checking 0x4d75140 towards VF7F4W30 (->V8XX)
Jul 07 21:07:41-987221 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:07:41-987398 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:07:41-987567 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:07:41-987734 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:07:41-987904 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:07:41-988158 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:07:41-988350 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:07:41-988529 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:07:41-988715 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:07:41-988895 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:07:41-989836 util-scheduler-8627 DEBUG Canceling task: 139 / 0x4d62e70
Jul 07 21:07:41-990282 util-scheduler-8627 DEBUG Adding task: 150 / 0x4d62e70
Jul 07 21:07:41-990529 cadet-con-8627 DEBUG next keepalive in 32 s
Jul 07 21:07:41-990715 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:07:41-990901 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:07:41-991101 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:07:41-991275 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:07:41-991449 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:07:41-991647 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:07:41-991851 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:07:41-992035 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:07:41-992213 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:07:41-992402 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:07:41-992649 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:08:14-022442 util-scheduler-8627 DEBUG Checking readiness of task: 149 / 0x4661f98
Jul 07 21:08:14-022845 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:14-023043 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:14-023238 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:14-023435 util-scheduler-8627 DEBUG Running task: 150 / 0x4d62e70
Jul 07 21:08:14-023709 cadet-con-8627 DEBUG BCK keepalive for VF7F4W30 (->V8XX)
Jul 07 21:08:40-165854 util-scheduler-8627 DEBUG Checking readiness of task: 149 / 0x4661f98
Jul 07 21:08:40-166240 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-166437 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-166629 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-166827 util-scheduler-8627 DEBUG Running task: 149 / 0x4661f98
Jul 07 21:08:40-167250 util-8627 DEBUG receive_ready read 136/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:08:40-167541 util-scheduler-8627 DEBUG Adding task: 151 / 0x4662140
Jul 07 21:08:40-167820 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-168012 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-168202 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-168392 util-scheduler-8627 DEBUG Running task: 151 / 0x4662140
Jul 07 21:08:40-168583 util-8627 DEBUG Received message of type 70 and size 136 from core service.
Jul 07 21:08:40-168783 core-api-8627 DEBUG Processing message of type 70 and size 136 from core service
Jul 07 21:08:40-169012 core-api-8627 DEBUG Received message of type 256 and size 100 from peer `V8XX'
Jul 07 21:08:40-169241 cadet-con-8627 DEBUG     path has 2 hops.
Jul 07 21:08:40-169485 cadet-con-8627 INFO <-- { CONNECTION_CREATE} on connection VF7F4W30 from V8XX
Jul 07 21:08:40-169693 cadet-con-8627 DEBUG     origin: V8XX
Jul 07 21:08:40-169912 cadet-con-8627 DEBUG   It's for us!
Jul 07 21:08:40-170704 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:08:40-170888 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:08:40-171062 cadet-p2p-8627 DEBUG   already known
Jul 07 21:08:40-171303 cadet-tun-8627 DEBUG add connection VF7F4W30 (->V8XX)
Jul 07 21:08:40-171504 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:08:40-171733 cadet-con-8627 INFO ===> {           FWD ACK} on connection VF7F4W30 (->V8XX)
Jul 07 21:08:40-171989 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:08:40-172197 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:08:40-172494 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 36)
Jul 07 21:08:40-172694 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:08:40-172921 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:08:40-173105 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:08:40-173308 cadet-con-8627 DEBUG  sendable
Jul 07 21:08:40-173516 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:08:40-173744 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:08:40-173961 util-scheduler-8627 DEBUG Adding task: 152 / 0x4d55220
Jul 07 21:08:40-174141 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:08:40-174346 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:08:40-174672 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:08:40-174850 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:08:40-175091 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:08:40-175277 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:08:40-175454 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:08:40-175652 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:08:40-175885 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_SENT
Jul 07 21:08:40-176125 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:08:40-176331 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:08:40-176545 util-scheduler-8627 DEBUG Adding task: 153 / 0x4661f98
Jul 07 21:08:40-176793 util-scheduler-8627 DEBUG Checking readiness of task: 153 / 0x4661f98
Jul 07 21:08:40-176984 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-177174 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-177393 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-177584 util-scheduler-8627 DEBUG Running task: 152 / 0x4d55220
Jul 07 21:08:40-177791 util-scheduler-8627 DEBUG Adding task: 154 / 0x4d55220
Jul 07 21:08:40-178012 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:08:40-178215 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:08:40-178417 util-scheduler-8627 DEBUG Adding task: 155 / 0x4661f98
Jul 07 21:08:40-178686 util-scheduler-8627 DEBUG Checking readiness of task: 155 / 0x4661f98
Jul 07 21:08:40-178879 util-scheduler-8627 DEBUG Checking readiness of task: 153 / 0x4661f98
Jul 07 21:08:40-179069 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-179260 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-179450 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-179642 util-scheduler-8627 DEBUG Running task: 155 / 0x4661f98
Jul 07 21:08:40-179827 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:08:40-180005 util-8627 DEBUG process_notify is running
Jul 07 21:08:40-180178 util-8627 DEBUG client_notify is running
Jul 07 21:08:40-180357 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:08:40-180553 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:08:40-180743 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:08:40-180995 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:08:40-181268 util-scheduler-8627 DEBUG Checking readiness of task: 153 / 0x4661f98
Jul 07 21:08:40-181461 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-181651 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-181840 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-182030 util-scheduler-8627 DEBUG Running task: 153 / 0x4661f98
Jul 07 21:08:40-182431 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:08:40-182660 util-scheduler-8627 DEBUG Adding task: 156 / 0x4662140
Jul 07 21:08:40-182903 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-183094 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-183283 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-183472 util-scheduler-8627 DEBUG Running task: 156 / 0x4662140
Jul 07 21:08:40-183661 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:08:40-183854 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:08:40-184069 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:08:40-184267 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:08:40-184464 util-scheduler-8627 DEBUG Adding task: 157 / 0x4661f98
Jul 07 21:08:40-184646 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:08:40-184843 util-scheduler-8627 DEBUG Adding task: 158 / 0x4661f98
Jul 07 21:08:40-185078 util-scheduler-8627 DEBUG Checking readiness of task: 158 / 0x4661f98
Jul 07 21:08:40-185302 util-scheduler-8627 DEBUG Checking readiness of task: 157 / 0x4661f98
Jul 07 21:08:40-185501 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:08:40-185691 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:08:40-185879 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:08:40-186069 util-scheduler-8627 DEBUG Running task: 157 / 0x4661f98
Jul 07 21:08:40-186253 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:08:40-186426 util-8627 DEBUG process_notify is running
Jul 07 21:08:40-186595 util-8627 DEBUG client_notify is running
Jul 07 21:08:40-186778 util-scheduler-8627 DEBUG Canceling task: 154 / 0x4d55220
Jul 07 21:08:40-187004 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:08:40-187219 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 36)
Jul 07 21:08:40-187449 cadet-p2p-8627 DEBUG Checking 0x4d78410 towards VF7F4W30 (->V8XX)
Jul 07 21:08:40-187681 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:08:40-187858 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:08:40-188027 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:08:40-188208 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:08:40-188378 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:08:40-188643 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 36)
Jul 07 21:08:40-188836 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:08:40-189015 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:08:40-189223 cadet-con-8627 DEBUG  sent BCK {    CONNECTION_ACK}
Jul 07 21:08:40-189405 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:08:40-189770 util-scheduler-8627 DEBUG Adding task: 159 / 0x4d62e70
Jul 07 21:08:40-190013 cadet-con-8627 DEBUG next keepalive in 64 s
Jul 07 21:08:40-190185 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:08:40-190365 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:08:40-190564 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:08:40-190738 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:08:40-190910 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:08:40-191107 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:08:40-191314 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:08:40-191497 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:08:40-191674 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:08:40-191862 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:08:40-192108 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:17-677668 util-scheduler-8627 DEBUG Checking readiness of task: 158 / 0x4661f98
Jul 07 21:09:17-678065 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:17-678262 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:17-678455 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:17-678653 util-scheduler-8627 DEBUG Running task: 158 / 0x4661f98
Jul 07 21:09:17-679077 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:17-679334 util-scheduler-8627 DEBUG Adding task: 160 / 0x4662140
Jul 07 21:09:17-679611 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:17-679803 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:17-679993 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:17-680183 util-scheduler-8627 DEBUG Running task: 160 / 0x4662140
Jul 07 21:09:17-680374 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:09:17-680575 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:09:17-680805 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:09:17-681711 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:09:17-683494 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:09:17-684487 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:17-684856 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:17-685447 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:17-685665 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:17-686652 cadet-con-8627 DEBUG   ACK
Jul 07 21:09:17-687189 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 21:09:17-687996 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:09:17-688359 util-scheduler-8627 DEBUG Canceling task: 91 / 0x4d62e70
Jul 07 21:09:17-689101 util-scheduler-8627 DEBUG Adding task: 161 / 0x4d62e70
Jul 07 21:09:17-690764 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:09:17-691268 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:17-692028 util-scheduler-8627 DEBUG Canceling task: 159 / 0x4d62e70
Jul 07 21:09:17-692251 util-scheduler-8627 DEBUG Adding task: 162 / 0x4d62e70
Jul 07 21:09:17-694236 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:17-695338 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 21:09:17-696477 cadet-tun-8627 DEBUG   cstate triggered rekey
Jul 07 21:09:17-697998 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:17-699553 cadet-tun-8627 INFO   new kx ctx for V8XX
Jul 07 21:09:17-963422 cadet-tun-8627 INFO ME: WZGYSS0H
Jul 07 21:09:17-964650 cadet-tun-8627 INFO PE: 00000000
Jul 07 21:09:17-965785 cadet-tun-8627 INFO KM: SY1Y2DBY
Jul 07 21:09:17-966865 cadet-tun-8627 INFO EK: 65Y43XST
Jul 07 21:09:17-967940 cadet-tun-8627 INFO DK: 9J1RHJ8Z
Jul 07 21:09:17-969537 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:17-971524 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:17-973749 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:17-975374 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:17-977390 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:17-978825 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:17-984300 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:17-986214 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:17-986945 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:17-987164 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:17-987930 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:17-988137 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:17-988365 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:17-988550 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:17-988727 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:17-988937 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:17-989153 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:17-989406 util-scheduler-8627 DEBUG Adding task: 163 / 0x4d55220
Jul 07 21:09:17-989587 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:17-989794 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:17-989970 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:17-990144 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:17-990382 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:17-990577 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:17-990756 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:17-990956 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:17-994868 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:17-995297 util-scheduler-8627 DEBUG Adding task: 164 / 0x4d63d80
Jul 07 21:09:17-996567 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:17-996796 util-scheduler-8627 DEBUG Adding task: 165 / 0x4661f98
Jul 07 21:09:17-997077 util-scheduler-8627 DEBUG Checking readiness of task: 165 / 0x4661f98
Jul 07 21:09:17-997303 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:17-997495 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:17-997686 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:17-997879 util-scheduler-8627 DEBUG Running task: 163 / 0x4d55220
Jul 07 21:09:17-998096 util-scheduler-8627 DEBUG Adding task: 166 / 0x4d55220
Jul 07 21:09:17-998331 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:17-998535 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:17-998738 util-scheduler-8627 DEBUG Adding task: 167 / 0x4661f98
Jul 07 21:09:17-998977 util-scheduler-8627 DEBUG Checking readiness of task: 167 / 0x4661f98
Jul 07 21:09:17-999170 util-scheduler-8627 DEBUG Checking readiness of task: 165 / 0x4661f98
Jul 07 21:09:17-999361 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:17-999578 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:17-999768 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:17-999960 util-scheduler-8627 DEBUG Running task: 167 / 0x4661f98
Jul 07 21:09:18-000147 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:18-000342 util-8627 DEBUG process_notify is running
Jul 07 21:09:18-000517 util-8627 DEBUG client_notify is running
Jul 07 21:09:18-000699 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:18-000897 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:18-001090 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:18-001369 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:18-001619 util-scheduler-8627 DEBUG Checking readiness of task: 165 / 0x4661f98
Jul 07 21:09:18-001813 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:18-002004 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:18-002194 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:18-002387 util-scheduler-8627 DEBUG Running task: 165 / 0x4661f98
Jul 07 21:09:18-002794 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:18-003026 util-scheduler-8627 DEBUG Adding task: 168 / 0x4662140
Jul 07 21:09:18-003272 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:18-003464 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:18-003655 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:18-003845 util-scheduler-8627 DEBUG Running task: 168 / 0x4662140
Jul 07 21:09:18-004038 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:18-004235 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:18-004453 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:18-004652 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:18-004851 util-scheduler-8627 DEBUG Adding task: 169 / 0x4661f98
Jul 07 21:09:18-005035 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:18-005253 util-scheduler-8627 DEBUG Adding task: 170 / 0x4661f98
Jul 07 21:09:18-005494 util-scheduler-8627 DEBUG Checking readiness of task: 170 / 0x4661f98
Jul 07 21:09:18-005686 util-scheduler-8627 DEBUG Checking readiness of task: 169 / 0x4661f98
Jul 07 21:09:18-005878 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:18-006068 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:18-006259 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:18-006450 util-scheduler-8627 DEBUG Running task: 169 / 0x4661f98
Jul 07 21:09:18-006635 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:18-006827 util-8627 DEBUG process_notify is running
Jul 07 21:09:18-006997 util-8627 DEBUG client_notify is running
Jul 07 21:09:18-007183 util-scheduler-8627 DEBUG Canceling task: 166 / 0x4d55220
Jul 07 21:09:18-007417 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:18-007635 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:18-007870 cadet-p2p-8627 DEBUG Checking 0x4df7688 towards VF7F4W30 (->V8XX)
Jul 07 21:09:18-008105 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:18-008284 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:18-009632 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:18-011070 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:18-011275 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:18-011461 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:18-011670 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:18-012285 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:18-012800 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:18-013006 util-scheduler-8627 DEBUG Canceling task: 162 / 0x4d62e70
Jul 07 21:09:18-013242 util-scheduler-8627 DEBUG Adding task: 171 / 0x4d62e70
Jul 07 21:09:18-013493 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:18-013754 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:18-013944 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:18-014147 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:18-014324 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:18-014500 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:18-014700 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:18-014907 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:18-015093 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:18-015273 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:18-015465 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:18-015713 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:20-807434 util-scheduler-8627 DEBUG Checking readiness of task: 170 / 0x4661f98
Jul 07 21:09:20-807768 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:20-807965 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:20-808157 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:20-808353 util-scheduler-8627 DEBUG Running task: 170 / 0x4661f98
Jul 07 21:09:20-808771 util-8627 DEBUG receive_ready read 132/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:20-809020 util-scheduler-8627 DEBUG Adding task: 172 / 0x4662140
Jul 07 21:09:20-809317 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:20-809509 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:20-809700 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:20-809889 util-scheduler-8627 DEBUG Running task: 172 / 0x4662140
Jul 07 21:09:20-810080 util-8627 DEBUG Received message of type 70 and size 132 from core service.
Jul 07 21:09:20-810277 core-api-8627 DEBUG Processing message of type 70 and size 132 from core service
Jul 07 21:09:20-810504 core-api-8627 DEBUG Received message of type 280 and size 96 from peer `V8XX'
Jul 07 21:09:20-811344 cadet-con-8627 INFO <-- {         ENCRYPTED} on connection VF7F4W30 from V8XX
Jul 07 21:09:20-813303 cadet-con-8627 DEBUG   connection VF7F4W30 (->V8XX)
Jul 07 21:09:20-813783 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:20-814027 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:20-816688 cadet-con-8627 DEBUG  PID 0 (expected 0+)
Jul 07 21:09:20-818433 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:09:20-818639 util-scheduler-8627 DEBUG Canceling task: 161 / 0x4d62e70
Jul 07 21:09:20-818870 util-scheduler-8627 DEBUG Adding task: 173 / 0x4d62e70
Jul 07 21:09:20-820048 cadet-con-8627 DEBUG   message for us!
Jul 07 21:09:20-820576 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:09:20-820801 util-scheduler-8627 DEBUG Adding task: 174 / 0x4d50e20
Jul 07 21:09:20-823069 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:09:20-823996 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:09:20-833729 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:09:21-229900 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:09:21-231761 cadet-tun-8627 INFO   HMAC with key 9J1RHJ8Z
Jul 07 21:09:21-243771 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:09:21-244137 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:09:21-247361 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:09:21-254477 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:09:21-255403 cadet-tun-8627 INFO   HMAC with key 00000000
Jul 07 21:09:21-260409 cadet-8627 WARNING Failed checksum validation on tunnel V8XX with KX
Jul 07 21:09:21-262105 cadet-8627 WARNING External protocol violation detected at gnunet-service-cadet_tunnel.c:2036.
Jul 07 21:09:21-266470 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:09:21-267818 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:09:21-269234 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:09:21-270404 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:09:21-272442 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:09:21-273722 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:09:21-274890 cadet-con-8627 DEBUG  last pid 0, last ack 0, qmax 11, q 0
Jul 07 21:09:21-277433 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:09:21-278883 cadet-con-8627 DEBUG  ack 64
Jul 07 21:09:21-279350 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:21-279597 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:21-279818 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:21-280121 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:09:21-280321 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:09:21-280547 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:21-280731 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:21-280906 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:21-281787 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:09:21-282014 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:09:21-282246 util-scheduler-8627 DEBUG Adding task: 175 / 0x4d55220
Jul 07 21:09:21-282428 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:21-282633 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:21-282811 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:21-282987 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:21-283225 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:21-283408 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:09:21-283585 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:09:21-283783 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:21-284508 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:21-284731 util-scheduler-8627 DEBUG Adding task: 176 / 0x4661f98
Jul 07 21:09:21-285008 util-scheduler-8627 DEBUG Checking readiness of task: 176 / 0x4661f98
Jul 07 21:09:21-285225 util-scheduler-8627 DEBUG Checking readiness of task: 174 / 0x4d50e20
Jul 07 21:09:21-285423 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-285614 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-285806 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-286003 util-scheduler-8627 DEBUG Running task: 174 / 0x4d50e20
Jul 07 21:09:21-286191 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:09:21-286383 util-8627 DEBUG process_notify is running
Jul 07 21:09:21-286556 util-8627 DEBUG client_notify is running
Jul 07 21:09:21-286807 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:09:21-287017 util-scheduler-8627 DEBUG Adding task: 177 / 0x4d50e20
Jul 07 21:09:21-287221 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:09:21-287482 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:09:21-288574 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:09:21-289279 util-scheduler-8627 DEBUG Running task: 175 / 0x4d55220
Jul 07 21:09:21-289499 util-scheduler-8627 DEBUG Adding task: 178 / 0x4d55220
Jul 07 21:09:21-289725 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:21-289944 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:21-290145 util-scheduler-8627 DEBUG Adding task: 179 / 0x4661f98
Jul 07 21:09:21-290390 util-scheduler-8627 DEBUG Checking readiness of task: 179 / 0x4661f98
Jul 07 21:09:21-290583 util-scheduler-8627 DEBUG Checking readiness of task: 177 / 0x4d50e20
Jul 07 21:09:21-290775 util-scheduler-8627 DEBUG Checking readiness of task: 176 / 0x4661f98
Jul 07 21:09:21-290964 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-291153 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-291343 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-291597 util-scheduler-8627 DEBUG Running task: 177 / 0x4d50e20
Jul 07 21:09:21-291781 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:09:21-291956 util-8627 DEBUG process_notify is running
Jul 07 21:09:21-292125 util-8627 DEBUG client_notify is running
Jul 07 21:09:21-292338 util-8627 DEBUG Transmitting message of type 168 and size 35 to statistics service.
Jul 07 21:09:21-292583 util-8627 DEBUG Connection transmitted 35/35 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:09:21-292793 util-scheduler-8627 DEBUG Running task: 179 / 0x4661f98
Jul 07 21:09:21-292976 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:21-293150 util-8627 DEBUG process_notify is running
Jul 07 21:09:21-293340 util-8627 DEBUG client_notify is running
Jul 07 21:09:21-293517 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:21-293712 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:21-293899 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:21-294138 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:21-294384 util-scheduler-8627 DEBUG Checking readiness of task: 176 / 0x4661f98
Jul 07 21:09:21-294575 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-294987 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-295177 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-295367 util-scheduler-8627 DEBUG Running task: 176 / 0x4661f98
Jul 07 21:09:21-295774 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:21-296007 util-scheduler-8627 DEBUG Adding task: 180 / 0x4662140
Jul 07 21:09:21-296253 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-296445 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-296637 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-296836 util-scheduler-8627 DEBUG Running task: 180 / 0x4662140
Jul 07 21:09:21-297027 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:21-297243 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:21-297463 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:21-297665 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:21-297866 util-scheduler-8627 DEBUG Adding task: 181 / 0x4661f98
Jul 07 21:09:21-298049 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:21-298249 util-scheduler-8627 DEBUG Adding task: 182 / 0x4661f98
Jul 07 21:09:21-298489 util-scheduler-8627 DEBUG Checking readiness of task: 182 / 0x4661f98
Jul 07 21:09:21-298679 util-scheduler-8627 DEBUG Checking readiness of task: 181 / 0x4661f98
Jul 07 21:09:21-298892 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-299082 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-299271 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-299480 util-scheduler-8627 DEBUG Running task: 181 / 0x4661f98
Jul 07 21:09:21-299665 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:21-299840 util-8627 DEBUG process_notify is running
Jul 07 21:09:21-300009 util-8627 DEBUG client_notify is running
Jul 07 21:09:21-300194 util-scheduler-8627 DEBUG Canceling task: 178 / 0x4d55220
Jul 07 21:09:21-300416 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:09:21-300634 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:21-300868 cadet-p2p-8627 DEBUG Checking 0x4e0f040 towards VF7F4W30 (->V8XX)
Jul 07 21:09:21-301101 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:21-301301 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:09:21-301605 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:09:21-301896 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:09:21-302197 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:21-302384 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:21-302573 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:09:21-303490 cadet-con-8627 DEBUG  calling cont
Jul 07 21:09:21-304334 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:21-304657 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:21-304848 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:09:21-305050 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:21-305246 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:21-305422 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:21-305622 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:21-305827 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:09:21-306011 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:09:21-306189 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:21-306379 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:09:21-306624 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:21-310712 util-scheduler-8627 DEBUG Checking readiness of task: 182 / 0x4661f98
Jul 07 21:09:21-310968 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-311165 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-311359 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-311554 util-scheduler-8627 DEBUG Running task: 182 / 0x4661f98
Jul 07 21:09:21-311966 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:21-312206 util-scheduler-8627 DEBUG Adding task: 183 / 0x4662140
Jul 07 21:09:21-312465 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:21-312657 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:21-313004 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:21-313241 util-scheduler-8627 DEBUG Running task: 183 / 0x4662140
Jul 07 21:09:21-313437 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:09:21-313637 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:09:21-313863 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:09:21-314122 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:09:21-314532 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:09:21-314776 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:21-314985 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:21-315225 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:21-315432 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:21-315709 cadet-con-8627 DEBUG   ACK
Jul 07 21:09:21-315947 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:09:21-316158 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:09:21-316350 util-scheduler-8627 DEBUG Canceling task: 173 / 0x4d62e70
Jul 07 21:09:21-316572 util-scheduler-8627 DEBUG Adding task: 184 / 0x4d62e70
Jul 07 21:09:21-316847 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:09:21-317499 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:21-317735 util-scheduler-8627 DEBUG Adding task: 185 / 0x4661f98
Jul 07 21:09:22-997124 util-scheduler-8627 DEBUG Checking readiness of task: 185 / 0x4661f98
Jul 07 21:09:22-997488 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:22-997684 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:22-997876 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:22-998070 util-scheduler-8627 DEBUG Running task: 164 / 0x4d63d80
Jul 07 21:09:22-998868 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:23-000617 cadet-tun-8627 DEBUG  kx started 5 s ago
Jul 07 21:09:23-001603 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:23-001967 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:23-002331 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:23-002725 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:23-003065 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:23-003447 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:23-003746 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:23-003950 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:23-004194 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:23-004406 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:23-004725 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:23-004929 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:23-005157 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:23-005370 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:23-005549 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:23-005758 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:23-005975 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:23-006214 util-scheduler-8627 DEBUG Adding task: 186 / 0x4d55220
Jul 07 21:09:23-006396 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:23-006602 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:23-006793 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:23-006969 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:23-007209 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:23-007416 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:23-007596 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:23-007798 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:23-008413 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:23-008621 util-scheduler-8627 DEBUG Adding task: 187 / 0x4d63d80
Jul 07 21:09:23-008883 util-scheduler-8627 DEBUG Checking readiness of task: 185 / 0x4661f98
Jul 07 21:09:23-009078 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:23-009294 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:23-009488 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:23-009680 util-scheduler-8627 DEBUG Running task: 186 / 0x4d55220
Jul 07 21:09:23-009891 util-scheduler-8627 DEBUG Adding task: 188 / 0x4d55220
Jul 07 21:09:23-010115 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:23-010320 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:23-010531 util-scheduler-8627 DEBUG Adding task: 189 / 0x4661f98
Jul 07 21:09:23-010800 util-scheduler-8627 DEBUG Checking readiness of task: 189 / 0x4661f98
Jul 07 21:09:23-010995 util-scheduler-8627 DEBUG Checking readiness of task: 185 / 0x4661f98
Jul 07 21:09:23-011187 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:23-011380 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:23-011571 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:23-011765 util-scheduler-8627 DEBUG Running task: 189 / 0x4661f98
Jul 07 21:09:23-011953 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:23-012133 util-8627 DEBUG process_notify is running
Jul 07 21:09:23-012308 util-8627 DEBUG client_notify is running
Jul 07 21:09:23-012490 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:23-012688 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:23-012881 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:23-013137 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:23-013409 util-scheduler-8627 DEBUG Checking readiness of task: 185 / 0x4661f98
Jul 07 21:09:23-013603 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:23-013795 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:23-013986 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:23-014178 util-scheduler-8627 DEBUG Running task: 185 / 0x4661f98
Jul 07 21:09:23-014587 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:23-014820 util-scheduler-8627 DEBUG Adding task: 190 / 0x4662140
Jul 07 21:09:23-015066 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:23-015259 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:23-015450 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:23-015640 util-scheduler-8627 DEBUG Running task: 190 / 0x4662140
Jul 07 21:09:23-015833 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:23-016030 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:23-016249 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:23-016449 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:23-016660 util-scheduler-8627 DEBUG Adding task: 191 / 0x4661f98
Jul 07 21:09:23-016847 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:23-017054 util-scheduler-8627 DEBUG Adding task: 192 / 0x4661f98
Jul 07 21:09:23-017315 util-scheduler-8627 DEBUG Checking readiness of task: 192 / 0x4661f98
Jul 07 21:09:23-017508 util-scheduler-8627 DEBUG Checking readiness of task: 191 / 0x4661f98
Jul 07 21:09:23-017701 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:23-017892 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:23-018082 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:23-018274 util-scheduler-8627 DEBUG Running task: 191 / 0x4661f98
Jul 07 21:09:23-018459 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:23-018636 util-8627 DEBUG process_notify is running
Jul 07 21:09:23-018806 util-8627 DEBUG client_notify is running
Jul 07 21:09:23-018993 util-scheduler-8627 DEBUG Canceling task: 188 / 0x4d55220
Jul 07 21:09:23-019217 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:23-019433 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:23-019667 cadet-p2p-8627 DEBUG Checking 0x4e12cd0 towards VF7F4W30 (->V8XX)
Jul 07 21:09:23-019901 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:23-020080 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:23-020283 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:23-020568 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:23-020764 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:23-020943 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:23-021131 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:23-021350 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:23-021530 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:23-021715 util-scheduler-8627 DEBUG Canceling task: 171 / 0x4d62e70
Jul 07 21:09:23-021926 util-scheduler-8627 DEBUG Adding task: 193 / 0x4d62e70
Jul 07 21:09:23-022172 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:23-022344 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:23-022527 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:23-022727 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:23-022902 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:23-023078 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:23-023277 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:23-023483 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:23-023667 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:23-023847 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:23-024036 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:23-024282 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:24-909558 util-scheduler-8627 DEBUG Checking readiness of task: 192 / 0x4661f98
Jul 07 21:09:24-909915 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-910111 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-910303 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-910500 util-scheduler-8627 DEBUG Running task: 192 / 0x4661f98
Jul 07 21:09:24-910922 util-8627 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:24-911176 util-scheduler-8627 DEBUG Adding task: 194 / 0x4662140
Jul 07 21:09:24-911466 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-911659 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-911849 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-912039 util-scheduler-8627 DEBUG Running task: 194 / 0x4662140
Jul 07 21:09:24-912230 util-8627 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 21:09:24-912429 core-api-8627 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 21:09:24-912658 core-api-8627 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 21:09:24-913549 cadet-con-8627 INFO <-- {              POLL} on connection VF7F4W30 from V8XX
Jul 07 21:09:24-914725 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:24-914958 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:24-915677 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:24-915894 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:24-917080 cadet-con-8627 DEBUG   BCK FC
Jul 07 21:09:24-918352 cadet-con-8627 DEBUG   PID 0, OLD 0
Jul 07 21:09:24-919228 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:09:24-919501 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:09:24-919831 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:09:24-920099 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:09:24-920481 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:09:24-920816 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:09:24-921155 cadet-con-8627 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 21:09:24-921574 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:09:24-921885 cadet-con-8627 DEBUG  ack 64
Jul 07 21:09:24-922072 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:24-922313 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:24-922522 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:24-922828 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:09:24-923028 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:09:24-923255 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:24-923438 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:24-923615 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:24-923821 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:09:24-924036 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:09:24-924261 util-scheduler-8627 DEBUG Adding task: 195 / 0x4d55220
Jul 07 21:09:24-924441 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:24-924645 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:24-924821 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:24-924995 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:24-925258 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:24-925444 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:09:24-925619 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:09:24-925817 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:24-926229 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:24-926451 util-scheduler-8627 DEBUG Adding task: 196 / 0x4661f98
Jul 07 21:09:24-926704 util-scheduler-8627 DEBUG Checking readiness of task: 196 / 0x4661f98
Jul 07 21:09:24-926897 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-927088 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-927282 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-927473 util-scheduler-8627 DEBUG Running task: 195 / 0x4d55220
Jul 07 21:09:24-927681 util-scheduler-8627 DEBUG Adding task: 197 / 0x4d55220
Jul 07 21:09:24-927996 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:24-928206 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:24-928413 util-scheduler-8627 DEBUG Adding task: 198 / 0x4661f98
Jul 07 21:09:24-928658 util-scheduler-8627 DEBUG Checking readiness of task: 198 / 0x4661f98
Jul 07 21:09:24-928852 util-scheduler-8627 DEBUG Checking readiness of task: 196 / 0x4661f98
Jul 07 21:09:24-929042 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-929275 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-929467 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-929658 util-scheduler-8627 DEBUG Running task: 198 / 0x4661f98
Jul 07 21:09:24-929844 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:24-930021 util-8627 DEBUG process_notify is running
Jul 07 21:09:24-930193 util-8627 DEBUG client_notify is running
Jul 07 21:09:24-930372 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:24-930568 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:24-930758 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:24-938444 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:24-938933 util-scheduler-8627 DEBUG Checking readiness of task: 196 / 0x4661f98
Jul 07 21:09:24-939137 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-939331 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-939522 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-939750 util-scheduler-8627 DEBUG Running task: 196 / 0x4661f98
Jul 07 21:09:24-940175 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:24-940429 util-scheduler-8627 DEBUG Adding task: 199 / 0x4662140
Jul 07 21:09:24-940678 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-940870 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-941059 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-941278 util-scheduler-8627 DEBUG Running task: 199 / 0x4662140
Jul 07 21:09:24-941470 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:24-941670 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:24-941924 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:24-942131 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:24-942339 util-scheduler-8627 DEBUG Adding task: 200 / 0x4661f98
Jul 07 21:09:24-942527 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:24-942733 util-scheduler-8627 DEBUG Adding task: 201 / 0x4661f98
Jul 07 21:09:24-942973 util-scheduler-8627 DEBUG Checking readiness of task: 201 / 0x4661f98
Jul 07 21:09:24-943165 util-scheduler-8627 DEBUG Checking readiness of task: 200 / 0x4661f98
Jul 07 21:09:24-943356 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:24-943545 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:24-943735 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:24-943926 util-scheduler-8627 DEBUG Running task: 200 / 0x4661f98
Jul 07 21:09:24-944111 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:24-944289 util-8627 DEBUG process_notify is running
Jul 07 21:09:24-944460 util-8627 DEBUG client_notify is running
Jul 07 21:09:24-944647 util-scheduler-8627 DEBUG Canceling task: 197 / 0x4d55220
Jul 07 21:09:24-944871 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:09:24-945092 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:24-945359 cadet-p2p-8627 DEBUG Checking 0x4e15e40 towards VF7F4W30 (->V8XX)
Jul 07 21:09:24-945597 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:24-945775 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:09:24-945965 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:09:24-946235 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:09:24-946429 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:24-946608 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:24-946795 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:09:24-947227 cadet-con-8627 DEBUG  calling cont
Jul 07 21:09:24-947418 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:24-947594 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:24-947776 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:09:24-947975 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:24-948149 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:24-948323 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:24-948521 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:24-948726 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:09:24-948969 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:09:24-949163 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:24-949383 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:09:24-949639 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:28-011837 util-scheduler-8627 DEBUG Checking readiness of task: 201 / 0x4661f98
Jul 07 21:09:28-012215 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-013032 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-013254 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-013452 util-scheduler-8627 DEBUG Running task: 187 / 0x4d63d80
Jul 07 21:09:28-013693 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:28-014201 cadet-tun-8627 DEBUG  kx started 10 s ago
Jul 07 21:09:28-014415 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:28-014620 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:28-014825 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:28-015061 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:28-015243 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:28-015466 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:28-015759 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:28-015957 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:28-016196 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:28-016405 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:28-016722 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:28-016924 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:28-017151 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:28-017362 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:28-017540 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:28-017769 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:28-017988 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:28-018214 util-scheduler-8627 DEBUG Adding task: 202 / 0x4d55220
Jul 07 21:09:28-018396 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:28-018601 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:28-018779 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:28-018955 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:28-019194 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:28-019391 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:28-019571 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:28-019771 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:28-020016 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:28-020224 util-scheduler-8627 DEBUG Adding task: 203 / 0x4d63d80
Jul 07 21:09:28-020483 util-scheduler-8627 DEBUG Checking readiness of task: 201 / 0x4661f98
Jul 07 21:09:28-020678 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-020869 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-021060 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-021276 util-scheduler-8627 DEBUG Running task: 202 / 0x4d55220
Jul 07 21:09:28-021487 util-scheduler-8627 DEBUG Adding task: 204 / 0x4d55220
Jul 07 21:09:28-021710 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:28-021916 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:28-022127 util-scheduler-8627 DEBUG Adding task: 205 / 0x4661f98
Jul 07 21:09:28-022369 util-scheduler-8627 DEBUG Checking readiness of task: 205 / 0x4661f98
Jul 07 21:09:28-022563 util-scheduler-8627 DEBUG Checking readiness of task: 201 / 0x4661f98
Jul 07 21:09:28-022755 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-022946 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-023137 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-023329 util-scheduler-8627 DEBUG Running task: 205 / 0x4661f98
Jul 07 21:09:28-023516 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:28-023695 util-8627 DEBUG process_notify is running
Jul 07 21:09:28-023887 util-8627 DEBUG client_notify is running
Jul 07 21:09:28-024069 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:28-024268 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:28-024461 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:28-024721 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:28-024970 util-scheduler-8627 DEBUG Checking readiness of task: 201 / 0x4661f98
Jul 07 21:09:28-025164 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-025379 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-025571 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-025764 util-scheduler-8627 DEBUG Running task: 201 / 0x4661f98
Jul 07 21:09:28-026173 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:28-026405 util-scheduler-8627 DEBUG Adding task: 206 / 0x4662140
Jul 07 21:09:28-026652 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-026844 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-027036 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-027228 util-scheduler-8627 DEBUG Running task: 206 / 0x4662140
Jul 07 21:09:28-027420 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:28-027618 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:28-027836 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:28-028039 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:28-028238 util-scheduler-8627 DEBUG Adding task: 207 / 0x4661f98
Jul 07 21:09:28-028424 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:28-028631 util-scheduler-8627 DEBUG Adding task: 208 / 0x4661f98
Jul 07 21:09:28-028870 util-scheduler-8627 DEBUG Checking readiness of task: 208 / 0x4661f98
Jul 07 21:09:28-029063 util-scheduler-8627 DEBUG Checking readiness of task: 207 / 0x4661f98
Jul 07 21:09:28-029279 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:28-029471 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:28-029663 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:28-029855 util-scheduler-8627 DEBUG Running task: 207 / 0x4661f98
Jul 07 21:09:28-030041 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:28-030230 util-8627 DEBUG process_notify is running
Jul 07 21:09:28-030400 util-8627 DEBUG client_notify is running
Jul 07 21:09:28-030587 util-scheduler-8627 DEBUG Canceling task: 204 / 0x4d55220
Jul 07 21:09:28-030811 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:28-031028 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:28-031262 cadet-p2p-8627 DEBUG Checking 0x4e189f0 towards VF7F4W30 (->V8XX)
Jul 07 21:09:28-031497 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:28-031676 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:28-031863 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:28-032147 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:28-032343 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:28-032522 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:28-032711 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:28-032901 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:28-033081 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:28-033289 util-scheduler-8627 DEBUG Canceling task: 193 / 0x4d62e70
Jul 07 21:09:28-033502 util-scheduler-8627 DEBUG Adding task: 209 / 0x4d62e70
Jul 07 21:09:28-033778 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:28-033951 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:28-034134 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:28-034333 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:28-034509 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:28-034684 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:28-034884 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:28-035089 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:28-035275 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:28-035453 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:28-035643 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:28-035890 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:31-199284 util-scheduler-8627 DEBUG Checking readiness of task: 208 / 0x4661f98
Jul 07 21:09:31-199651 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-199848 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-200044 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-200242 util-scheduler-8627 DEBUG Running task: 208 / 0x4661f98
Jul 07 21:09:31-200663 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:31-200917 util-scheduler-8627 DEBUG Adding task: 210 / 0x4662140
Jul 07 21:09:31-201213 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-201409 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-201599 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-201790 util-scheduler-8627 DEBUG Running task: 210 / 0x4662140
Jul 07 21:09:31-201981 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:09:31-202180 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:09:31-202407 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:09:31-202672 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:09:31-202907 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:09:31-203147 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:31-203355 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:31-203594 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:31-203801 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:31-203982 cadet-con-8627 DEBUG   ACK
Jul 07 21:09:31-204211 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:09:31-204395 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:09:31-204580 util-scheduler-8627 DEBUG Canceling task: 184 / 0x4d62e70
Jul 07 21:09:31-204799 util-scheduler-8627 DEBUG Adding task: 211 / 0x4d62e70
Jul 07 21:09:31-204981 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:09:31-205160 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:31-205392 util-scheduler-8627 DEBUG Adding task: 212 / 0x4661f98
Jul 07 21:09:31-874379 util-scheduler-8627 DEBUG Checking readiness of task: 212 / 0x4661f98
Jul 07 21:09:31-874673 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-874871 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-875064 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-875258 util-scheduler-8627 DEBUG Running task: 212 / 0x4661f98
Jul 07 21:09:31-875673 util-8627 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:31-875917 util-scheduler-8627 DEBUG Adding task: 213 / 0x4662140
Jul 07 21:09:31-876232 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-876432 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-876621 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-876809 util-scheduler-8627 DEBUG Running task: 213 / 0x4662140
Jul 07 21:09:31-876999 util-8627 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 21:09:31-877221 core-api-8627 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 21:09:31-877449 core-api-8627 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 21:09:31-877705 cadet-con-8627 INFO <-- {              POLL} on connection VF7F4W30 from V8XX
Jul 07 21:09:31-877954 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:31-878162 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:31-878403 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:31-878609 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:31-878960 cadet-con-8627 DEBUG   BCK FC
Jul 07 21:09:31-879297 cadet-con-8627 DEBUG   PID 0, OLD 0
Jul 07 21:09:31-879534 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:09:31-879710 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:09:31-879893 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:09:31-880066 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:09:31-880308 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:09:31-880488 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:09:31-880670 cadet-con-8627 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 21:09:31-880943 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:09:31-881132 cadet-con-8627 DEBUG  ack 64
Jul 07 21:09:31-881467 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:31-881709 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:31-881991 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:31-882287 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:09:31-882486 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:09:31-882710 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:31-882897 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:31-883076 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:31-883289 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:09:31-883582 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:09:31-883813 util-scheduler-8627 DEBUG Adding task: 214 / 0x4d55220
Jul 07 21:09:31-883997 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:31-884207 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:31-884383 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:31-884559 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:31-884802 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:31-884988 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:09:31-885164 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:09:31-885390 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:31-885573 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:31-885787 util-scheduler-8627 DEBUG Adding task: 215 / 0x4661f98
Jul 07 21:09:31-886046 util-scheduler-8627 DEBUG Checking readiness of task: 215 / 0x4661f98
Jul 07 21:09:31-886240 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-886431 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-886621 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-886815 util-scheduler-8627 DEBUG Running task: 214 / 0x4d55220
Jul 07 21:09:31-887028 util-scheduler-8627 DEBUG Adding task: 216 / 0x4d55220
Jul 07 21:09:31-887270 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:31-887497 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:31-887703 util-scheduler-8627 DEBUG Adding task: 217 / 0x4661f98
Jul 07 21:09:31-887949 util-scheduler-8627 DEBUG Checking readiness of task: 217 / 0x4661f98
Jul 07 21:09:31-888155 util-scheduler-8627 DEBUG Checking readiness of task: 215 / 0x4661f98
Jul 07 21:09:31-888345 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-888534 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-888723 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-888915 util-scheduler-8627 DEBUG Running task: 217 / 0x4661f98
Jul 07 21:09:31-889099 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:31-889300 util-8627 DEBUG process_notify is running
Jul 07 21:09:31-889473 util-8627 DEBUG client_notify is running
Jul 07 21:09:31-889652 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:31-889848 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:31-890038 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:31-890295 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:31-890542 util-scheduler-8627 DEBUG Checking readiness of task: 215 / 0x4661f98
Jul 07 21:09:31-890734 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-890924 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-891113 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-891303 util-scheduler-8627 DEBUG Running task: 215 / 0x4661f98
Jul 07 21:09:31-891705 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:31-891933 util-scheduler-8627 DEBUG Adding task: 218 / 0x4662140
Jul 07 21:09:31-892176 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-892367 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-892556 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-892744 util-scheduler-8627 DEBUG Running task: 218 / 0x4662140
Jul 07 21:09:31-892933 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:31-893129 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:31-893366 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:31-893564 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:31-893761 util-scheduler-8627 DEBUG Adding task: 219 / 0x4661f98
Jul 07 21:09:31-893944 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:31-894143 util-scheduler-8627 DEBUG Adding task: 220 / 0x4661f98
Jul 07 21:09:31-894378 util-scheduler-8627 DEBUG Checking readiness of task: 220 / 0x4661f98
Jul 07 21:09:31-894569 util-scheduler-8627 DEBUG Checking readiness of task: 219 / 0x4661f98
Jul 07 21:09:31-894759 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:31-894948 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:31-895136 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:31-895326 util-scheduler-8627 DEBUG Running task: 219 / 0x4661f98
Jul 07 21:09:31-895509 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:31-895682 util-8627 DEBUG process_notify is running
Jul 07 21:09:31-895851 util-8627 DEBUG client_notify is running
Jul 07 21:09:31-896035 util-scheduler-8627 DEBUG Canceling task: 216 / 0x4d55220
Jul 07 21:09:31-896256 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:09:31-896472 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:31-896703 cadet-p2p-8627 DEBUG Checking 0x4e1c6d8 towards VF7F4W30 (->V8XX)
Jul 07 21:09:31-896961 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:31-897140 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:09:31-897348 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:09:31-897617 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:09:31-897810 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:31-897989 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:31-898174 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:09:31-898348 cadet-con-8627 DEBUG  calling cont
Jul 07 21:09:31-898528 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:31-898702 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:31-898882 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:09:31-899078 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:31-899252 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:31-899425 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:31-899622 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:31-899825 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:09:31-900008 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:09:31-900189 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:31-900377 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:09:31-900618 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:33-021504 util-scheduler-8627 DEBUG Checking readiness of task: 220 / 0x4661f98
Jul 07 21:09:33-021901 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-022816 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-023148 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-023348 util-scheduler-8627 DEBUG Running task: 203 / 0x4d63d80
Jul 07 21:09:33-023585 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:33-023831 cadet-tun-8627 DEBUG  kx started 15 s ago
Jul 07 21:09:33-024038 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:33-024242 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:33-024446 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:33-024680 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:33-024861 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:33-025085 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:33-025404 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:33-025604 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:33-025842 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:33-026052 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:33-026386 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:33-026587 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:33-026814 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:33-026999 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:33-027177 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:33-027385 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:33-027600 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:33-027824 util-scheduler-8627 DEBUG Adding task: 221 / 0x4d55220
Jul 07 21:09:33-028006 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:33-028212 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:33-028392 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:33-028568 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:33-028807 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:33-029004 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:33-029241 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:33-029445 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:33-029688 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:33-029888 util-scheduler-8627 DEBUG Adding task: 222 / 0x4d63d80
Jul 07 21:09:33-030147 util-scheduler-8627 DEBUG Checking readiness of task: 220 / 0x4661f98
Jul 07 21:09:33-030340 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-030532 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-030723 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-030914 util-scheduler-8627 DEBUG Running task: 221 / 0x4d55220
Jul 07 21:09:33-031136 util-scheduler-8627 DEBUG Adding task: 223 / 0x4d55220
Jul 07 21:09:33-031358 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:33-031561 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:33-031771 util-scheduler-8627 DEBUG Adding task: 224 / 0x4661f98
Jul 07 21:09:33-032012 util-scheduler-8627 DEBUG Checking readiness of task: 224 / 0x4661f98
Jul 07 21:09:33-032206 util-scheduler-8627 DEBUG Checking readiness of task: 220 / 0x4661f98
Jul 07 21:09:33-032398 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-032588 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-032779 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-032973 util-scheduler-8627 DEBUG Running task: 224 / 0x4661f98
Jul 07 21:09:33-033160 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:33-033366 util-8627 DEBUG process_notify is running
Jul 07 21:09:33-033541 util-8627 DEBUG client_notify is running
Jul 07 21:09:33-033721 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:33-033919 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:33-034122 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:33-034435 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:33-034686 util-scheduler-8627 DEBUG Checking readiness of task: 220 / 0x4661f98
Jul 07 21:09:33-034880 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-035071 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-035262 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-035454 util-scheduler-8627 DEBUG Running task: 220 / 0x4661f98
Jul 07 21:09:33-035861 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:33-036092 util-scheduler-8627 DEBUG Adding task: 225 / 0x4662140
Jul 07 21:09:33-036338 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-036531 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-036722 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-036912 util-scheduler-8627 DEBUG Running task: 225 / 0x4662140
Jul 07 21:09:33-037104 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:33-037327 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:33-037546 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:33-037745 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:33-037944 util-scheduler-8627 DEBUG Adding task: 226 / 0x4661f98
Jul 07 21:09:33-038130 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:33-038336 util-scheduler-8627 DEBUG Adding task: 227 / 0x4661f98
Jul 07 21:09:33-038575 util-scheduler-8627 DEBUG Checking readiness of task: 227 / 0x4661f98
Jul 07 21:09:33-038766 util-scheduler-8627 DEBUG Checking readiness of task: 226 / 0x4661f98
Jul 07 21:09:33-038974 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:33-039170 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:33-039361 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:33-039552 util-scheduler-8627 DEBUG Running task: 226 / 0x4661f98
Jul 07 21:09:33-039738 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:33-039914 util-8627 DEBUG process_notify is running
Jul 07 21:09:33-040084 util-8627 DEBUG client_notify is running
Jul 07 21:09:33-040269 util-scheduler-8627 DEBUG Canceling task: 223 / 0x4d55220
Jul 07 21:09:33-040493 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:33-040710 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:33-040943 cadet-p2p-8627 DEBUG Checking 0x4e1f288 towards VF7F4W30 (->V8XX)
Jul 07 21:09:33-041177 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:33-041383 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:33-041571 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:33-041854 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:33-042049 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:33-042228 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:33-042416 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:33-042605 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:33-042784 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:33-042968 util-scheduler-8627 DEBUG Canceling task: 209 / 0x4d62e70
Jul 07 21:09:33-043180 util-scheduler-8627 DEBUG Adding task: 228 / 0x4d62e70
Jul 07 21:09:33-043426 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:33-043597 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:33-043778 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:33-043989 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:33-044164 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:33-044339 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:33-044537 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:33-044743 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:33-044928 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:33-045107 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:33-045324 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:33-045575 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:38-035020 util-scheduler-8627 DEBUG Checking readiness of task: 227 / 0x4661f98
Jul 07 21:09:38-035385 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-035893 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-036089 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-036286 util-scheduler-8627 DEBUG Running task: 222 / 0x4d63d80
Jul 07 21:09:38-036520 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:38-036767 cadet-tun-8627 DEBUG  kx started 20 s ago
Jul 07 21:09:38-036972 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:38-037174 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:38-037404 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:38-037640 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:38-037821 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:38-038045 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:38-038335 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:38-038534 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:38-038772 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:38-038982 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:38-039319 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:38-039522 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:38-039748 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:38-039934 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:38-040111 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:38-040337 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:38-040554 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:38-040777 util-scheduler-8627 DEBUG Adding task: 229 / 0x4d55220
Jul 07 21:09:38-040959 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:38-041164 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:38-041366 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:38-041542 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:38-041783 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:38-041980 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:38-042173 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:38-042374 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:38-042616 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:38-042815 util-scheduler-8627 DEBUG Adding task: 230 / 0x4d63d80
Jul 07 21:09:38-043071 util-scheduler-8627 DEBUG Checking readiness of task: 227 / 0x4661f98
Jul 07 21:09:38-043264 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-043455 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-043646 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-043837 util-scheduler-8627 DEBUG Running task: 229 / 0x4d55220
Jul 07 21:09:38-044045 util-scheduler-8627 DEBUG Adding task: 231 / 0x4d55220
Jul 07 21:09:38-044267 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:38-044472 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:38-044683 util-scheduler-8627 DEBUG Adding task: 232 / 0x4661f98
Jul 07 21:09:38-044925 util-scheduler-8627 DEBUG Checking readiness of task: 232 / 0x4661f98
Jul 07 21:09:38-045119 util-scheduler-8627 DEBUG Checking readiness of task: 227 / 0x4661f98
Jul 07 21:09:38-045335 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-045526 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-045719 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-045912 util-scheduler-8627 DEBUG Running task: 232 / 0x4661f98
Jul 07 21:09:38-046098 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:38-046277 util-8627 DEBUG process_notify is running
Jul 07 21:09:38-046452 util-8627 DEBUG client_notify is running
Jul 07 21:09:38-046632 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:38-046830 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:38-047021 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:38-047278 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:38-047527 util-scheduler-8627 DEBUG Checking readiness of task: 227 / 0x4661f98
Jul 07 21:09:38-047721 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-047912 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-048104 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-048296 util-scheduler-8627 DEBUG Running task: 227 / 0x4661f98
Jul 07 21:09:38-048702 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:38-048934 util-scheduler-8627 DEBUG Adding task: 233 / 0x4662140
Jul 07 21:09:38-049218 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-049414 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-049616 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-049808 util-scheduler-8627 DEBUG Running task: 233 / 0x4662140
Jul 07 21:09:38-050000 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:38-050197 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:38-050415 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:38-050614 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:38-050813 util-scheduler-8627 DEBUG Adding task: 234 / 0x4661f98
Jul 07 21:09:38-050998 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:38-051204 util-scheduler-8627 DEBUG Adding task: 235 / 0x4661f98
Jul 07 21:09:38-051444 util-scheduler-8627 DEBUG Checking readiness of task: 235 / 0x4661f98
Jul 07 21:09:38-051636 util-scheduler-8627 DEBUG Checking readiness of task: 234 / 0x4661f98
Jul 07 21:09:38-051832 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:38-052024 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:38-052215 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:38-052407 util-scheduler-8627 DEBUG Running task: 234 / 0x4661f98
Jul 07 21:09:38-052593 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:38-052769 util-8627 DEBUG process_notify is running
Jul 07 21:09:38-052939 util-8627 DEBUG client_notify is running
Jul 07 21:09:38-053124 util-scheduler-8627 DEBUG Canceling task: 231 / 0x4d55220
Jul 07 21:09:38-053372 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:38-053590 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:38-053824 cadet-p2p-8627 DEBUG Checking 0x4e21f60 towards VF7F4W30 (->V8XX)
Jul 07 21:09:38-054058 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:38-054238 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:38-054425 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:38-054708 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:38-054904 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:38-055083 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:38-055271 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:38-055460 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:38-055639 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:38-055824 util-scheduler-8627 DEBUG Canceling task: 228 / 0x4d62e70
Jul 07 21:09:38-056035 util-scheduler-8627 DEBUG Adding task: 236 / 0x4d62e70
Jul 07 21:09:38-056280 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:38-056452 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:38-056634 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:38-056833 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:38-057008 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:38-057183 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:38-057405 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:38-057612 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:38-057797 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:38-057976 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:38-058178 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:38-058424 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:42-751281 util-scheduler-8627 DEBUG Checking readiness of task: 235 / 0x4661f98
Jul 07 21:09:42-751628 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-751851 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-752044 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-752240 util-scheduler-8627 DEBUG Running task: 235 / 0x4661f98
Jul 07 21:09:42-752660 util-8627 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:42-752911 util-scheduler-8627 DEBUG Adding task: 237 / 0x4662140
Jul 07 21:09:42-753183 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-753401 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-753591 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-753780 util-scheduler-8627 DEBUG Running task: 237 / 0x4662140
Jul 07 21:09:42-753971 util-8627 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 21:09:42-754170 core-api-8627 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 21:09:42-754397 core-api-8627 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 21:09:42-754659 cadet-con-8627 INFO <-- {              POLL} on connection VF7F4W30 from V8XX
Jul 07 21:09:42-754913 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:42-755121 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:42-755361 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:42-755568 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:42-755748 cadet-con-8627 DEBUG   BCK FC
Jul 07 21:09:42-755920 cadet-con-8627 DEBUG   PID 0, OLD 0
Jul 07 21:09:42-756147 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:09:42-756321 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:09:42-756503 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:09:42-756674 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:09:42-756893 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:09:42-757070 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:09:42-757270 cadet-con-8627 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 21:09:42-757539 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:09:42-757728 cadet-con-8627 DEBUG  ack 64
Jul 07 21:09:42-757906 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:42-758140 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:42-758345 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:42-758636 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:09:42-758834 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:09:42-759058 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:42-759259 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:42-759434 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:42-759639 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:09:42-759852 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:09:42-760064 util-scheduler-8627 DEBUG Adding task: 238 / 0x4d55220
Jul 07 21:09:42-760243 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:42-760469 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:42-760646 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:42-760819 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:42-761054 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:42-761257 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:09:42-761433 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:09:42-761634 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:42-761813 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:42-762023 util-scheduler-8627 DEBUG Adding task: 239 / 0x4661f98
Jul 07 21:09:42-762264 util-scheduler-8627 DEBUG Checking readiness of task: 239 / 0x4661f98
Jul 07 21:09:42-762454 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-762656 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-762846 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-763035 util-scheduler-8627 DEBUG Running task: 238 / 0x4d55220
Jul 07 21:09:42-763240 util-scheduler-8627 DEBUG Adding task: 240 / 0x4d55220
Jul 07 21:09:42-763460 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:42-763660 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:42-763862 util-scheduler-8627 DEBUG Adding task: 241 / 0x4661f98
Jul 07 21:09:42-764099 util-scheduler-8627 DEBUG Checking readiness of task: 241 / 0x4661f98
Jul 07 21:09:42-764291 util-scheduler-8627 DEBUG Checking readiness of task: 239 / 0x4661f98
Jul 07 21:09:42-764479 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-764669 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-764857 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-765048 util-scheduler-8627 DEBUG Running task: 241 / 0x4661f98
Jul 07 21:09:42-765252 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:42-765429 util-8627 DEBUG process_notify is running
Jul 07 21:09:42-765601 util-8627 DEBUG client_notify is running
Jul 07 21:09:42-765780 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:42-765974 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:42-766164 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:42-766410 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:42-766656 util-scheduler-8627 DEBUG Checking readiness of task: 239 / 0x4661f98
Jul 07 21:09:42-766848 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-767037 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-767225 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-767414 util-scheduler-8627 DEBUG Running task: 239 / 0x4661f98
Jul 07 21:09:42-767824 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:42-768048 util-scheduler-8627 DEBUG Adding task: 242 / 0x4662140
Jul 07 21:09:42-768291 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-768482 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-768671 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-768859 util-scheduler-8627 DEBUG Running task: 242 / 0x4662140
Jul 07 21:09:42-769047 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:42-769259 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:42-769474 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:42-769671 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:42-769867 util-scheduler-8627 DEBUG Adding task: 243 / 0x4661f98
Jul 07 21:09:42-770050 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:42-770248 util-scheduler-8627 DEBUG Adding task: 244 / 0x4661f98
Jul 07 21:09:42-770484 util-scheduler-8627 DEBUG Checking readiness of task: 244 / 0x4661f98
Jul 07 21:09:42-770674 util-scheduler-8627 DEBUG Checking readiness of task: 243 / 0x4661f98
Jul 07 21:09:42-770865 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-771053 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-771242 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-771432 util-scheduler-8627 DEBUG Running task: 243 / 0x4661f98
Jul 07 21:09:42-771619 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:42-771808 util-8627 DEBUG process_notify is running
Jul 07 21:09:42-771978 util-8627 DEBUG client_notify is running
Jul 07 21:09:42-772162 util-scheduler-8627 DEBUG Canceling task: 240 / 0x4d55220
Jul 07 21:09:42-772383 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:09:42-772598 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:42-772830 cadet-p2p-8627 DEBUG Checking 0x4e250d0 towards VF7F4W30 (->V8XX)
Jul 07 21:09:42-773062 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:42-773258 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:09:42-773444 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:09:42-773711 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:09:42-773903 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:42-774081 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:42-774267 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:09:42-774440 cadet-con-8627 DEBUG  calling cont
Jul 07 21:09:42-774620 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:42-774794 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:42-774973 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:09:42-775170 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:42-775343 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:42-775516 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:42-775712 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:42-775916 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:09:42-776098 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:09:42-776285 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:42-776473 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:09:42-776714 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:42-778329 util-scheduler-8627 DEBUG Checking readiness of task: 244 / 0x4661f98
Jul 07 21:09:42-778542 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-778737 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-778928 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-779134 util-scheduler-8627 DEBUG Running task: 244 / 0x4661f98
Jul 07 21:09:42-779535 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:42-779763 util-scheduler-8627 DEBUG Adding task: 245 / 0x4662140
Jul 07 21:09:42-780010 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:42-780201 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:42-780391 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:42-780581 util-scheduler-8627 DEBUG Running task: 245 / 0x4662140
Jul 07 21:09:42-780770 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:09:42-780963 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:09:42-781178 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:09:42-781451 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:09:42-781664 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:09:42-781902 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:42-782110 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:42-782347 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:42-782553 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:42-782734 cadet-con-8627 DEBUG   ACK
Jul 07 21:09:42-782965 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:09:42-783151 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:09:42-783355 util-scheduler-8627 DEBUG Canceling task: 211 / 0x4d62e70
Jul 07 21:09:42-783574 util-scheduler-8627 DEBUG Adding task: 246 / 0x4d62e70
Jul 07 21:09:42-783757 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:09:42-783934 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:42-784135 util-scheduler-8627 DEBUG Adding task: 247 / 0x4661f98
Jul 07 21:09:43-043213 util-scheduler-8627 DEBUG Checking readiness of task: 247 / 0x4661f98
Jul 07 21:09:43-043553 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-044587 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-044785 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-044983 util-scheduler-8627 DEBUG Running task: 230 / 0x4d63d80
Jul 07 21:09:43-045242 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:43-045491 cadet-tun-8627 DEBUG  kx started 25 s ago
Jul 07 21:09:43-045697 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:43-045900 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:43-046120 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:43-046357 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:43-046539 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:43-046762 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:43-047051 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:43-047251 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:43-047489 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:43-047698 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:43-048013 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:43-048216 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:43-048441 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:43-048627 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:43-048804 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:43-049011 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:43-049257 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:43-049596 util-scheduler-8627 DEBUG Adding task: 248 / 0x4d55220
Jul 07 21:09:43-049839 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:43-050052 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:43-050232 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:43-050409 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:43-050650 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:43-050848 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:43-051028 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:43-051229 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:43-051475 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:43-051680 util-scheduler-8627 DEBUG Adding task: 249 / 0x4d63d80
Jul 07 21:09:43-051936 util-scheduler-8627 DEBUG Checking readiness of task: 247 / 0x4661f98
Jul 07 21:09:43-052129 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-052321 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-052513 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-052706 util-scheduler-8627 DEBUG Running task: 248 / 0x4d55220
Jul 07 21:09:43-052925 util-scheduler-8627 DEBUG Adding task: 250 / 0x4d55220
Jul 07 21:09:43-053148 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:43-053377 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:43-053587 util-scheduler-8627 DEBUG Adding task: 251 / 0x4661f98
Jul 07 21:09:43-053829 util-scheduler-8627 DEBUG Checking readiness of task: 251 / 0x4661f98
Jul 07 21:09:43-054024 util-scheduler-8627 DEBUG Checking readiness of task: 247 / 0x4661f98
Jul 07 21:09:43-054238 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-054430 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-054621 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-054814 util-scheduler-8627 DEBUG Running task: 251 / 0x4661f98
Jul 07 21:09:43-055000 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:43-055180 util-8627 DEBUG process_notify is running
Jul 07 21:09:43-055354 util-8627 DEBUG client_notify is running
Jul 07 21:09:43-055534 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:43-055732 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:43-055925 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:43-056179 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:43-056426 util-scheduler-8627 DEBUG Checking readiness of task: 247 / 0x4661f98
Jul 07 21:09:43-056619 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-056810 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-057001 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-057211 util-scheduler-8627 DEBUG Running task: 247 / 0x4661f98
Jul 07 21:09:43-057620 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:43-057850 util-scheduler-8627 DEBUG Adding task: 252 / 0x4662140
Jul 07 21:09:43-058096 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-058289 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-058479 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-058670 util-scheduler-8627 DEBUG Running task: 252 / 0x4662140
Jul 07 21:09:43-058861 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:43-059057 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:43-059275 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:43-059473 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:43-059672 util-scheduler-8627 DEBUG Adding task: 253 / 0x4661f98
Jul 07 21:09:43-059858 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:43-060064 util-scheduler-8627 DEBUG Adding task: 254 / 0x4661f98
Jul 07 21:09:43-060302 util-scheduler-8627 DEBUG Checking readiness of task: 254 / 0x4661f98
Jul 07 21:09:43-060496 util-scheduler-8627 DEBUG Checking readiness of task: 253 / 0x4661f98
Jul 07 21:09:43-060703 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:43-060895 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:43-061085 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:43-061297 util-scheduler-8627 DEBUG Running task: 253 / 0x4661f98
Jul 07 21:09:43-061483 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:43-061663 util-8627 DEBUG process_notify is running
Jul 07 21:09:43-061834 util-8627 DEBUG client_notify is running
Jul 07 21:09:43-062020 util-scheduler-8627 DEBUG Canceling task: 250 / 0x4d55220
Jul 07 21:09:43-062243 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:43-062471 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:43-062703 cadet-p2p-8627 DEBUG Checking 0x4e287f8 towards VF7F4W30 (->V8XX)
Jul 07 21:09:43-062937 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:43-063117 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:43-063305 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:43-063589 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:43-063800 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:43-063979 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:43-064168 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:43-064358 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:43-064538 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:43-064723 util-scheduler-8627 DEBUG Canceling task: 236 / 0x4d62e70
Jul 07 21:09:43-064934 util-scheduler-8627 DEBUG Adding task: 255 / 0x4d62e70
Jul 07 21:09:43-065181 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:43-065373 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:43-065555 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:43-065755 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:43-065930 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:43-066105 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:43-066305 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:43-066511 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:43-066696 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:43-066875 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:43-067066 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:43-067312 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:48-056816 util-scheduler-8627 DEBUG Checking readiness of task: 254 / 0x4661f98
Jul 07 21:09:48-057185 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-057740 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-057967 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-058207 util-scheduler-8627 DEBUG Running task: 249 / 0x4d63d80
Jul 07 21:09:48-058446 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:48-058692 cadet-tun-8627 DEBUG  kx started 30 s ago
Jul 07 21:09:48-058897 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:48-059100 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:48-059303 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:48-059539 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:48-059720 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:48-059979 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:48-060280 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:48-060479 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:48-060717 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:48-060927 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:48-061263 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:48-061466 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:48-061693 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:48-061878 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:48-062055 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:48-062264 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:48-062478 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:48-062703 util-scheduler-8627 DEBUG Adding task: 256 / 0x4d55220
Jul 07 21:09:48-062885 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:48-063089 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:48-063266 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:48-063442 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:48-063680 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:48-063877 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:48-064081 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:48-064283 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:48-064547 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:48-064748 util-scheduler-8627 DEBUG Adding task: 257 / 0x4d63d80
Jul 07 21:09:48-065004 util-scheduler-8627 DEBUG Checking readiness of task: 254 / 0x4661f98
Jul 07 21:09:48-065217 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-065411 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-065602 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-065794 util-scheduler-8627 DEBUG Running task: 256 / 0x4d55220
Jul 07 21:09:48-066004 util-scheduler-8627 DEBUG Adding task: 258 / 0x4d55220
Jul 07 21:09:48-066226 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:48-066431 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:48-066642 util-scheduler-8627 DEBUG Adding task: 259 / 0x4661f98
Jul 07 21:09:48-066885 util-scheduler-8627 DEBUG Checking readiness of task: 259 / 0x4661f98
Jul 07 21:09:48-067080 util-scheduler-8627 DEBUG Checking readiness of task: 254 / 0x4661f98
Jul 07 21:09:48-067281 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-067473 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-067664 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-067893 util-scheduler-8627 DEBUG Running task: 259 / 0x4661f98
Jul 07 21:09:48-068090 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:48-068271 util-8627 DEBUG process_notify is running
Jul 07 21:09:48-068445 util-8627 DEBUG client_notify is running
Jul 07 21:09:48-068626 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:48-068824 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:48-069017 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:48-069292 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:48-069543 util-scheduler-8627 DEBUG Checking readiness of task: 254 / 0x4661f98
Jul 07 21:09:48-069737 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-069928 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-070118 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-070310 util-scheduler-8627 DEBUG Running task: 254 / 0x4661f98
Jul 07 21:09:48-070716 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:48-070949 util-scheduler-8627 DEBUG Adding task: 260 / 0x4662140
Jul 07 21:09:48-071195 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-071388 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-071579 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-071770 util-scheduler-8627 DEBUG Running task: 260 / 0x4662140
Jul 07 21:09:48-071976 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:48-072172 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:48-072390 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:48-072589 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:48-072792 util-scheduler-8627 DEBUG Adding task: 261 / 0x4661f98
Jul 07 21:09:48-072978 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:48-073183 util-scheduler-8627 DEBUG Adding task: 262 / 0x4661f98
Jul 07 21:09:48-073443 util-scheduler-8627 DEBUG Checking readiness of task: 262 / 0x4661f98
Jul 07 21:09:48-073637 util-scheduler-8627 DEBUG Checking readiness of task: 261 / 0x4661f98
Jul 07 21:09:48-073829 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:48-074037 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:48-074228 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:48-074421 util-scheduler-8627 DEBUG Running task: 261 / 0x4661f98
Jul 07 21:09:48-074606 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:48-074782 util-8627 DEBUG process_notify is running
Jul 07 21:09:48-074953 util-8627 DEBUG client_notify is running
Jul 07 21:09:48-075138 util-scheduler-8627 DEBUG Canceling task: 258 / 0x4d55220
Jul 07 21:09:48-075362 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:48-075579 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:48-075812 cadet-p2p-8627 DEBUG Checking 0x4e2b4d0 towards VF7F4W30 (->V8XX)
Jul 07 21:09:48-076047 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:48-076226 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:48-076413 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:48-076697 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:48-076892 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:48-077071 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:48-077289 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:48-077481 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:48-077660 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:48-077845 util-scheduler-8627 DEBUG Canceling task: 255 / 0x4d62e70
Jul 07 21:09:48-078057 util-scheduler-8627 DEBUG Adding task: 263 / 0x4d62e70
Jul 07 21:09:48-078302 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:48-078473 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:48-078655 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:48-078854 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:48-079030 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:48-079205 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:48-079404 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:48-079609 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:48-079794 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:48-079974 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:48-080163 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:48-080408 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:53-069890 util-scheduler-8627 DEBUG Checking readiness of task: 262 / 0x4661f98
Jul 07 21:09:53-070273 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-071029 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-071235 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-071435 util-scheduler-8627 DEBUG Running task: 257 / 0x4d63d80
Jul 07 21:09:53-071673 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:53-071920 cadet-tun-8627 DEBUG  kx started 35 s ago
Jul 07 21:09:53-072126 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:53-072328 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:53-072532 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:53-072769 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:53-072951 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:53-073174 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:53-073493 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:53-073692 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:53-073932 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:53-074141 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:53-074458 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:53-074706 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:53-074937 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:53-075124 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:53-075301 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:53-075512 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:53-075727 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:53-075952 util-scheduler-8627 DEBUG Adding task: 264 / 0x4d55220
Jul 07 21:09:53-076133 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:53-076338 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:53-076515 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:53-076691 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:53-076930 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:53-077128 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:53-077333 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:53-077535 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:53-077779 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:53-077979 util-scheduler-8627 DEBUG Adding task: 265 / 0x4d63d80
Jul 07 21:09:53-078235 util-scheduler-8627 DEBUG Checking readiness of task: 262 / 0x4661f98
Jul 07 21:09:53-078430 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-078622 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-078814 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-079005 util-scheduler-8627 DEBUG Running task: 264 / 0x4d55220
Jul 07 21:09:53-079215 util-scheduler-8627 DEBUG Adding task: 266 / 0x4d55220
Jul 07 21:09:53-079438 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:53-079643 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:53-079855 util-scheduler-8627 DEBUG Adding task: 267 / 0x4661f98
Jul 07 21:09:53-080097 util-scheduler-8627 DEBUG Checking readiness of task: 267 / 0x4661f98
Jul 07 21:09:53-080292 util-scheduler-8627 DEBUG Checking readiness of task: 262 / 0x4661f98
Jul 07 21:09:53-080483 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-080675 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-080866 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-081060 util-scheduler-8627 DEBUG Running task: 267 / 0x4661f98
Jul 07 21:09:53-081270 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:53-081452 util-8627 DEBUG process_notify is running
Jul 07 21:09:53-081627 util-8627 DEBUG client_notify is running
Jul 07 21:09:53-081809 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:53-082007 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:53-082200 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:53-082458 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:53-082707 util-scheduler-8627 DEBUG Checking readiness of task: 262 / 0x4661f98
Jul 07 21:09:53-082902 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-083116 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-083309 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-083502 util-scheduler-8627 DEBUG Running task: 262 / 0x4661f98
Jul 07 21:09:53-083910 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:53-084142 util-scheduler-8627 DEBUG Adding task: 268 / 0x4662140
Jul 07 21:09:53-084389 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-084599 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-084791 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-084983 util-scheduler-8627 DEBUG Running task: 268 / 0x4662140
Jul 07 21:09:53-085176 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:53-085398 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:53-085621 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:53-085821 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:53-086020 util-scheduler-8627 DEBUG Adding task: 269 / 0x4661f98
Jul 07 21:09:53-086206 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:53-086413 util-scheduler-8627 DEBUG Adding task: 270 / 0x4661f98
Jul 07 21:09:53-086652 util-scheduler-8627 DEBUG Checking readiness of task: 270 / 0x4661f98
Jul 07 21:09:53-086846 util-scheduler-8627 DEBUG Checking readiness of task: 269 / 0x4661f98
Jul 07 21:09:53-087039 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:53-087230 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:53-087422 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:53-087614 util-scheduler-8627 DEBUG Running task: 269 / 0x4661f98
Jul 07 21:09:53-087799 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:53-087976 util-8627 DEBUG process_notify is running
Jul 07 21:09:53-088147 util-8627 DEBUG client_notify is running
Jul 07 21:09:53-088334 util-scheduler-8627 DEBUG Canceling task: 266 / 0x4d55220
Jul 07 21:09:53-088557 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:53-088773 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:53-089007 cadet-p2p-8627 DEBUG Checking 0x4e2e1a8 towards VF7F4W30 (->V8XX)
Jul 07 21:09:53-089264 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:53-089446 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:53-089634 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:53-089918 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:53-090114 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:53-090293 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:53-090483 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:53-090673 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:53-090853 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:53-091038 util-scheduler-8627 DEBUG Canceling task: 263 / 0x4d62e70
Jul 07 21:09:53-091250 util-scheduler-8627 DEBUG Adding task: 271 / 0x4d62e70
Jul 07 21:09:53-091496 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:53-091668 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:53-091850 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:53-092049 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:53-092235 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:53-092464 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:53-092665 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:53-092871 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:53-093056 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:53-093258 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:53-093451 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:53-093698 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:57-984892 util-scheduler-8627 DEBUG Checking readiness of task: 270 / 0x4661f98
Jul 07 21:09:57-985272 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:57-985470 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:57-985690 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:57-985887 util-scheduler-8627 DEBUG Running task: 270 / 0x4661f98
Jul 07 21:09:57-986308 util-8627 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:57-986561 util-scheduler-8627 DEBUG Adding task: 272 / 0x4662140
Jul 07 21:09:57-986838 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:57-987030 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:57-987219 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:57-987409 util-scheduler-8627 DEBUG Running task: 272 / 0x4662140
Jul 07 21:09:57-987599 util-8627 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 21:09:57-987798 core-api-8627 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 21:09:57-988027 core-api-8627 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 21:09:57-988291 cadet-con-8627 INFO <-- {              POLL} on connection VF7F4W30 from V8XX
Jul 07 21:09:57-988547 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:57-988757 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:09:57-988999 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:57-989229 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:57-989415 cadet-con-8627 DEBUG   BCK FC
Jul 07 21:09:57-989587 cadet-con-8627 DEBUG   PID 0, OLD 0
Jul 07 21:09:57-989816 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:09:57-989990 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:09:57-990161 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:09:57-990332 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:09:57-990551 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:09:57-990729 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:09:57-990908 cadet-con-8627 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 21:09:57-991175 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:09:57-991364 cadet-con-8627 DEBUG  ack 64
Jul 07 21:09:57-991542 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:57-991776 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:57-992001 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:57-992293 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:09:57-992491 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:09:57-992715 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:57-992898 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:57-993073 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:57-993301 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:09:57-993515 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:09:57-993729 util-scheduler-8627 DEBUG Adding task: 273 / 0x4d55220
Jul 07 21:09:57-993909 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:57-994111 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:57-994286 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:57-994460 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:57-994696 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:57-994879 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:09:57-995053 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:09:57-995250 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:57-995430 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:57-995653 util-scheduler-8627 DEBUG Adding task: 274 / 0x4661f98
Jul 07 21:09:57-995916 util-scheduler-8627 DEBUG Checking readiness of task: 274 / 0x4661f98
Jul 07 21:09:57-996110 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:57-996318 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:57-996508 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:57-996701 util-scheduler-8627 DEBUG Running task: 273 / 0x4d55220
Jul 07 21:09:57-996907 util-scheduler-8627 DEBUG Adding task: 275 / 0x4d55220
Jul 07 21:09:57-997128 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:57-997353 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:57-997555 util-scheduler-8627 DEBUG Adding task: 276 / 0x4661f98
Jul 07 21:09:57-997794 util-scheduler-8627 DEBUG Checking readiness of task: 276 / 0x4661f98
Jul 07 21:09:57-997986 util-scheduler-8627 DEBUG Checking readiness of task: 274 / 0x4661f98
Jul 07 21:09:57-998176 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:57-998365 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:57-998555 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:57-998746 util-scheduler-8627 DEBUG Running task: 276 / 0x4661f98
Jul 07 21:09:57-998931 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:57-999108 util-8627 DEBUG process_notify is running
Jul 07 21:09:57-999281 util-8627 DEBUG client_notify is running
Jul 07 21:09:57-999469 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:57-999665 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:57-999855 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:58-000102 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:58-000352 util-scheduler-8627 DEBUG Checking readiness of task: 274 / 0x4661f98
Jul 07 21:09:58-000545 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-000736 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-000927 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-001118 util-scheduler-8627 DEBUG Running task: 274 / 0x4661f98
Jul 07 21:09:58-001545 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:58-001772 util-scheduler-8627 DEBUG Adding task: 277 / 0x4662140
Jul 07 21:09:58-002017 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-002210 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-002401 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-002591 util-scheduler-8627 DEBUG Running task: 277 / 0x4662140
Jul 07 21:09:58-002782 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:58-002977 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:58-003193 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:58-003392 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:58-003590 util-scheduler-8627 DEBUG Adding task: 278 / 0x4661f98
Jul 07 21:09:58-003774 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:58-003973 util-scheduler-8627 DEBUG Adding task: 279 / 0x4661f98
Jul 07 21:09:58-004211 util-scheduler-8627 DEBUG Checking readiness of task: 279 / 0x4661f98
Jul 07 21:09:58-004403 util-scheduler-8627 DEBUG Checking readiness of task: 278 / 0x4661f98
Jul 07 21:09:58-004596 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-004787 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-004978 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-005170 util-scheduler-8627 DEBUG Running task: 278 / 0x4661f98
Jul 07 21:09:58-005379 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:58-005556 util-8627 DEBUG process_notify is running
Jul 07 21:09:58-005743 util-8627 DEBUG client_notify is running
Jul 07 21:09:58-005930 util-scheduler-8627 DEBUG Canceling task: 275 / 0x4d55220
Jul 07 21:09:58-006153 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:09:58-006371 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:58-006604 cadet-p2p-8627 DEBUG Checking 0x4e31318 towards VF7F4W30 (->V8XX)
Jul 07 21:09:58-006842 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:58-007021 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:09:58-007208 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:09:58-007476 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:09:58-007670 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:58-007849 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:58-008037 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:09:58-008212 cadet-con-8627 DEBUG  calling cont
Jul 07 21:09:58-008394 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:58-008569 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:58-008750 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:09:58-008957 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:58-009133 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:58-009333 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:58-009534 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:58-009740 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:09:58-009925 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:09:58-010104 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:58-010294 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:09:58-010537 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:58-078154 util-scheduler-8627 DEBUG Checking readiness of task: 279 / 0x4661f98
Jul 07 21:09:58-078447 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-079071 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-079306 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-079548 util-scheduler-8627 DEBUG Running task: 265 / 0x4d63d80
Jul 07 21:09:58-079778 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:09:58-080023 cadet-tun-8627 DEBUG  kx started 40 s ago
Jul 07 21:09:58-080230 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:09:58-080432 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:09:58-080636 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:09:58-080868 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:09:58-081050 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:09:58-081296 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:09:58-081582 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:09:58-081780 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:09:58-082019 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:09:58-082228 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:09:58-082559 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:09:58-082761 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:09:58-082987 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:09:58-083172 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:09:58-083350 cadet-con-8627 DEBUG  sendable
Jul 07 21:09:58-083557 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:09:58-083786 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:09:58-084007 util-scheduler-8627 DEBUG Adding task: 280 / 0x4d55220
Jul 07 21:09:58-084211 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:09:58-084416 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:58-084593 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:09:58-084769 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:09:58-085022 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:09:58-085239 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:09:58-085421 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:09:58-085621 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:58-085863 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:09:58-086062 util-scheduler-8627 DEBUG Adding task: 281 / 0x4d63d80
Jul 07 21:09:58-086310 util-scheduler-8627 DEBUG Checking readiness of task: 279 / 0x4661f98
Jul 07 21:09:58-086503 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-086694 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-086885 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-087077 util-scheduler-8627 DEBUG Running task: 280 / 0x4d55220
Jul 07 21:09:58-087285 util-scheduler-8627 DEBUG Adding task: 282 / 0x4d55220
Jul 07 21:09:58-087506 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:09:58-087706 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:58-087914 util-scheduler-8627 DEBUG Adding task: 283 / 0x4661f98
Jul 07 21:09:58-088156 util-scheduler-8627 DEBUG Checking readiness of task: 283 / 0x4661f98
Jul 07 21:09:58-088351 util-scheduler-8627 DEBUG Checking readiness of task: 279 / 0x4661f98
Jul 07 21:09:58-088543 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-088734 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-088925 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-089118 util-scheduler-8627 DEBUG Running task: 283 / 0x4661f98
Jul 07 21:09:58-089325 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:58-089505 util-8627 DEBUG process_notify is running
Jul 07 21:09:58-089678 util-8627 DEBUG client_notify is running
Jul 07 21:09:58-089858 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:09:58-090054 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:58-090246 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:09:58-090498 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:09:58-090746 util-scheduler-8627 DEBUG Checking readiness of task: 279 / 0x4661f98
Jul 07 21:09:58-090939 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-091131 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-091322 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-091514 util-scheduler-8627 DEBUG Running task: 279 / 0x4661f98
Jul 07 21:09:58-091918 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:09:58-092149 util-scheduler-8627 DEBUG Adding task: 284 / 0x4662140
Jul 07 21:09:58-092396 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-092588 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-092779 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-092970 util-scheduler-8627 DEBUG Running task: 284 / 0x4662140
Jul 07 21:09:58-093162 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:09:58-093389 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:09:58-093606 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:09:58-093804 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:09:58-094021 util-scheduler-8627 DEBUG Adding task: 285 / 0x4661f98
Jul 07 21:09:58-094208 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:09:58-094412 util-scheduler-8627 DEBUG Adding task: 286 / 0x4661f98
Jul 07 21:09:58-094652 util-scheduler-8627 DEBUG Checking readiness of task: 286 / 0x4661f98
Jul 07 21:09:58-094848 util-scheduler-8627 DEBUG Checking readiness of task: 285 / 0x4661f98
Jul 07 21:09:58-095041 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:09:58-095233 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:09:58-095424 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:09:58-095617 util-scheduler-8627 DEBUG Running task: 285 / 0x4661f98
Jul 07 21:09:58-095802 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:09:58-096012 util-8627 DEBUG process_notify is running
Jul 07 21:09:58-096197 util-8627 DEBUG client_notify is running
Jul 07 21:09:58-096393 util-scheduler-8627 DEBUG Canceling task: 282 / 0x4d55220
Jul 07 21:09:58-096617 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:09:58-096834 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:09:58-097067 cadet-p2p-8627 DEBUG Checking 0x4e33ec8 towards VF7F4W30 (->V8XX)
Jul 07 21:09:58-097321 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:09:58-097500 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:09:58-097686 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:09:58-097968 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:09:58-098164 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:09:58-098341 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:09:58-098528 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:09:58-098718 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:09:58-098898 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:09:58-099083 util-scheduler-8627 DEBUG Canceling task: 271 / 0x4d62e70
Jul 07 21:09:58-099295 util-scheduler-8627 DEBUG Adding task: 287 / 0x4d62e70
Jul 07 21:09:58-099542 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:09:58-099713 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:09:58-099895 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:09:58-100094 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:09:58-100268 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:09:58-100442 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:09:58-100639 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:09:58-100842 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:09:58-101025 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:09:58-101221 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:09:58-101411 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:09:58-101654 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:03-091194 util-scheduler-8627 DEBUG Checking readiness of task: 286 / 0x4661f98
Jul 07 21:10:03-091576 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-092130 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-092328 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-092582 util-scheduler-8627 DEBUG Running task: 281 / 0x4d63d80
Jul 07 21:10:03-092833 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:03-093080 cadet-tun-8627 DEBUG  kx started 45 s ago
Jul 07 21:10:03-093305 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:03-093508 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:03-093712 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:03-093948 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:03-094129 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:03-094377 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:03-094668 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:03-094867 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:03-095106 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:03-095315 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:03-095630 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:03-095832 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:03-096061 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:03-096259 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:03-096437 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:03-096644 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:03-096860 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:03-097083 util-scheduler-8627 DEBUG Adding task: 288 / 0x4d55220
Jul 07 21:10:03-097286 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:03-097492 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:03-097670 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:03-097845 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:03-098084 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:03-098281 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:03-098471 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:03-098672 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:03-098913 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:03-099113 util-scheduler-8627 DEBUG Adding task: 289 / 0x4d63d80
Jul 07 21:10:03-099366 util-scheduler-8627 DEBUG Checking readiness of task: 286 / 0x4661f98
Jul 07 21:10:03-099560 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-099751 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-099942 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-100134 util-scheduler-8627 DEBUG Running task: 288 / 0x4d55220
Jul 07 21:10:03-100341 util-scheduler-8627 DEBUG Adding task: 290 / 0x4d55220
Jul 07 21:10:03-100560 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:03-100761 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:03-100969 util-scheduler-8627 DEBUG Adding task: 291 / 0x4661f98
Jul 07 21:10:03-101228 util-scheduler-8627 DEBUG Checking readiness of task: 291 / 0x4661f98
Jul 07 21:10:03-101423 util-scheduler-8627 DEBUG Checking readiness of task: 286 / 0x4661f98
Jul 07 21:10:03-101612 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-101802 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-101991 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-102182 util-scheduler-8627 DEBUG Running task: 291 / 0x4661f98
Jul 07 21:10:03-102367 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:03-102544 util-8627 DEBUG process_notify is running
Jul 07 21:10:03-102717 util-8627 DEBUG client_notify is running
Jul 07 21:10:03-102895 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:03-103090 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:03-103280 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:03-103536 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:03-103782 util-scheduler-8627 DEBUG Checking readiness of task: 286 / 0x4661f98
Jul 07 21:10:03-103974 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-104163 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-104369 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-104560 util-scheduler-8627 DEBUG Running task: 286 / 0x4661f98
Jul 07 21:10:03-104964 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:03-105214 util-scheduler-8627 DEBUG Adding task: 292 / 0x4662140
Jul 07 21:10:03-105460 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-105652 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-105841 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-106032 util-scheduler-8627 DEBUG Running task: 292 / 0x4662140
Jul 07 21:10:03-106222 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:03-106416 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:03-106631 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:03-106828 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:03-107059 util-scheduler-8627 DEBUG Adding task: 293 / 0x4661f98
Jul 07 21:10:03-107259 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:03-107464 util-scheduler-8627 DEBUG Adding task: 294 / 0x4661f98
Jul 07 21:10:03-107714 util-scheduler-8627 DEBUG Checking readiness of task: 294 / 0x4661f98
Jul 07 21:10:03-107905 util-scheduler-8627 DEBUG Checking readiness of task: 293 / 0x4661f98
Jul 07 21:10:03-108096 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:03-108285 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:03-108473 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:03-108663 util-scheduler-8627 DEBUG Running task: 293 / 0x4661f98
Jul 07 21:10:03-108846 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:03-109020 util-8627 DEBUG process_notify is running
Jul 07 21:10:03-109206 util-8627 DEBUG client_notify is running
Jul 07 21:10:03-109393 util-scheduler-8627 DEBUG Canceling task: 290 / 0x4d55220
Jul 07 21:10:03-109615 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:03-109829 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:03-110061 cadet-p2p-8627 DEBUG Checking 0x4e36ba0 towards VF7F4W30 (->V8XX)
Jul 07 21:10:03-110292 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:03-110470 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:03-110655 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:03-110937 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:03-111131 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:03-111308 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:03-111493 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:03-111681 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:03-111858 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:03-112041 util-scheduler-8627 DEBUG Canceling task: 287 / 0x4d62e70
Jul 07 21:10:03-112249 util-scheduler-8627 DEBUG Adding task: 295 / 0x4d62e70
Jul 07 21:10:03-112493 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:03-112662 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:03-112843 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:03-113040 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:03-113232 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:03-113406 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:03-113604 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:03-113808 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:03-113990 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:03-114167 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:03-114369 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:03-114613 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:08-101385 util-scheduler-8627 DEBUG Checking readiness of task: 294 / 0x4661f98
Jul 07 21:10:08-101775 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-101972 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-102164 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-102360 util-scheduler-8627 DEBUG Running task: 289 / 0x4d63d80
Jul 07 21:10:08-102599 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:08-102847 cadet-tun-8627 DEBUG  kx started 50 s ago
Jul 07 21:10:08-103053 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:08-103275 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:08-103477 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:08-103713 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:08-103893 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:08-104114 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:08-104422 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:08-104618 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:08-104856 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:08-105064 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:08-105408 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:08-105609 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:08-105835 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:08-106018 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:08-106194 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:08-106400 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:08-106614 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:08-106839 util-scheduler-8627 DEBUG Adding task: 296 / 0x4d55220
Jul 07 21:10:08-107020 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:08-107224 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:08-107400 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:08-107575 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:08-107814 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:08-108010 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:08-108189 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:08-108387 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:08-108630 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:08-108830 util-scheduler-8627 DEBUG Adding task: 297 / 0x4d63d80
Jul 07 21:10:08-109087 util-scheduler-8627 DEBUG Checking readiness of task: 294 / 0x4661f98
Jul 07 21:10:08-110543 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-110774 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-110967 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-111160 util-scheduler-8627 DEBUG Running task: 296 / 0x4d55220
Jul 07 21:10:08-111385 util-scheduler-8627 DEBUG Adding task: 298 / 0x4d55220
Jul 07 21:10:08-111610 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:08-111814 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:08-112025 util-scheduler-8627 DEBUG Adding task: 299 / 0x4661f98
Jul 07 21:10:08-112272 util-scheduler-8627 DEBUG Checking readiness of task: 299 / 0x4661f98
Jul 07 21:10:08-112466 util-scheduler-8627 DEBUG Checking readiness of task: 294 / 0x4661f98
Jul 07 21:10:08-112655 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-112872 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-113062 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-113282 util-scheduler-8627 DEBUG Running task: 299 / 0x4661f98
Jul 07 21:10:08-113469 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:08-113648 util-8627 DEBUG process_notify is running
Jul 07 21:10:08-113821 util-8627 DEBUG client_notify is running
Jul 07 21:10:08-114000 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:08-114197 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:08-114389 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:08-114731 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:08-114983 util-scheduler-8627 DEBUG Checking readiness of task: 294 / 0x4661f98
Jul 07 21:10:08-115175 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-115366 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-115555 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-115745 util-scheduler-8627 DEBUG Running task: 294 / 0x4661f98
Jul 07 21:10:08-116152 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:08-116386 util-scheduler-8627 DEBUG Adding task: 300 / 0x4662140
Jul 07 21:10:08-116634 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-116894 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-117085 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-117300 util-scheduler-8627 DEBUG Running task: 300 / 0x4662140
Jul 07 21:10:08-117491 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:08-117688 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:08-117905 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:08-118104 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:08-118303 util-scheduler-8627 DEBUG Adding task: 301 / 0x4661f98
Jul 07 21:10:08-118488 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:08-118694 util-scheduler-8627 DEBUG Adding task: 302 / 0x4661f98
Jul 07 21:10:08-118933 util-scheduler-8627 DEBUG Checking readiness of task: 302 / 0x4661f98
Jul 07 21:10:08-119124 util-scheduler-8627 DEBUG Checking readiness of task: 301 / 0x4661f98
Jul 07 21:10:08-119318 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:08-119507 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:08-119697 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:08-119887 util-scheduler-8627 DEBUG Running task: 301 / 0x4661f98
Jul 07 21:10:08-120070 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:08-120244 util-8627 DEBUG process_notify is running
Jul 07 21:10:08-120413 util-8627 DEBUG client_notify is running
Jul 07 21:10:08-120599 util-scheduler-8627 DEBUG Canceling task: 298 / 0x4d55220
Jul 07 21:10:08-120822 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:08-121051 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:08-121313 cadet-p2p-8627 DEBUG Checking 0x4e39878 towards VF7F4W30 (->V8XX)
Jul 07 21:10:08-121548 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:08-121727 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:08-121914 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:08-122199 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:08-122394 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:08-122588 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:08-122775 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:08-122965 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:08-123143 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:08-123328 util-scheduler-8627 DEBUG Canceling task: 295 / 0x4d62e70
Jul 07 21:10:08-123537 util-scheduler-8627 DEBUG Adding task: 303 / 0x4d62e70
Jul 07 21:10:08-123784 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:08-123954 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:08-124135 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:08-124333 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:08-124507 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:08-124681 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:08-124879 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:08-125084 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:08-125291 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:08-125469 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:08-125658 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:08-126645 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:13-113977 util-scheduler-8627 DEBUG Checking readiness of task: 302 / 0x4661f98
Jul 07 21:10:13-114370 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-115145 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-115591 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-115793 util-scheduler-8627 DEBUG Running task: 297 / 0x4d63d80
Jul 07 21:10:13-116034 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:13-116294 cadet-tun-8627 DEBUG  kx started 55 s ago
Jul 07 21:10:13-116498 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:13-116698 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:13-116900 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:13-117136 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:13-117339 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:13-117562 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:13-117875 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:13-118073 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:13-118309 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:13-118516 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:13-118831 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:13-119030 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:13-119255 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:13-119438 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:13-119614 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:13-119819 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:13-120032 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:13-120256 util-scheduler-8627 DEBUG Adding task: 304 / 0x4d55220
Jul 07 21:10:13-120435 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:13-120638 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:13-120814 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:13-120987 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:13-121249 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:13-121448 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:13-121626 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:13-121825 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:13-122101 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:13-122300 util-scheduler-8627 DEBUG Adding task: 305 / 0x4d63d80
Jul 07 21:10:13-122563 util-scheduler-8627 DEBUG Checking readiness of task: 302 / 0x4661f98
Jul 07 21:10:13-122754 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-122944 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-123133 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-123322 util-scheduler-8627 DEBUG Running task: 304 / 0x4d55220
Jul 07 21:10:13-123530 util-scheduler-8627 DEBUG Adding task: 306 / 0x4d55220
Jul 07 21:10:13-123751 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:13-123954 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:13-124163 util-scheduler-8627 DEBUG Adding task: 307 / 0x4661f98
Jul 07 21:10:13-124414 util-scheduler-8627 DEBUG Checking readiness of task: 307 / 0x4661f98
Jul 07 21:10:13-124607 util-scheduler-8627 DEBUG Checking readiness of task: 302 / 0x4661f98
Jul 07 21:10:13-124797 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-124986 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-125174 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-125388 util-scheduler-8627 DEBUG Running task: 307 / 0x4661f98
Jul 07 21:10:13-125573 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:13-125750 util-8627 DEBUG process_notify is running
Jul 07 21:10:13-125923 util-8627 DEBUG client_notify is running
Jul 07 21:10:13-126102 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:13-126296 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:13-126487 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:13-126746 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:13-126993 util-scheduler-8627 DEBUG Checking readiness of task: 302 / 0x4661f98
Jul 07 21:10:13-127184 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-127373 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-127562 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-127756 util-scheduler-8627 DEBUG Running task: 302 / 0x4661f98
Jul 07 21:10:13-128163 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:13-128417 util-scheduler-8627 DEBUG Adding task: 308 / 0x4662140
Jul 07 21:10:13-128663 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-128853 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-129043 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-129252 util-scheduler-8627 DEBUG Running task: 308 / 0x4662140
Jul 07 21:10:13-129444 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:13-129638 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:13-129854 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:13-130050 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:13-130246 util-scheduler-8627 DEBUG Adding task: 309 / 0x4661f98
Jul 07 21:10:13-130430 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:13-130635 util-scheduler-8627 DEBUG Adding task: 310 / 0x4661f98
Jul 07 21:10:13-130872 util-scheduler-8627 DEBUG Checking readiness of task: 310 / 0x4661f98
Jul 07 21:10:13-131062 util-scheduler-8627 DEBUG Checking readiness of task: 309 / 0x4661f98
Jul 07 21:10:13-131252 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:13-131440 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:13-131645 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:13-131836 util-scheduler-8627 DEBUG Running task: 309 / 0x4661f98
Jul 07 21:10:13-132019 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:13-132193 util-8627 DEBUG process_notify is running
Jul 07 21:10:13-132362 util-8627 DEBUG client_notify is running
Jul 07 21:10:13-132546 util-scheduler-8627 DEBUG Canceling task: 306 / 0x4d55220
Jul 07 21:10:13-132767 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:13-132981 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:13-133234 cadet-p2p-8627 DEBUG Checking 0x4e3c550 towards VF7F4W30 (->V8XX)
Jul 07 21:10:13-133469 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:13-133646 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:13-133831 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:13-134113 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:13-134316 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:13-134494 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:13-134680 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:13-134869 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:13-135046 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:13-135229 util-scheduler-8627 DEBUG Canceling task: 303 / 0x4d62e70
Jul 07 21:10:13-135438 util-scheduler-8627 DEBUG Adding task: 311 / 0x4d62e70
Jul 07 21:10:13-135682 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:13-135851 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:13-136031 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:13-136228 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:13-136401 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:13-136574 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:13-136771 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:13-136974 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:13-137157 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:13-137353 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:13-137553 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:13-137802 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:18-124875 util-scheduler-8627 DEBUG Checking readiness of task: 310 / 0x4661f98
Jul 07 21:10:18-125277 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-126265 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-126469 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-126722 util-scheduler-8627 DEBUG Running task: 305 / 0x4d63d80
Jul 07 21:10:18-126979 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:18-127240 cadet-tun-8627 DEBUG  kx started 1 m ago
Jul 07 21:10:18-128907 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:18-129116 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:18-129346 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:18-129584 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:18-129765 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:18-129987 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:18-130280 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:18-130478 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:18-130715 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:18-130923 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:18-131250 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:18-131474 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:18-131704 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:18-131887 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:18-132063 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:18-132269 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:18-132484 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:18-132707 util-scheduler-8627 DEBUG Adding task: 312 / 0x4d55220
Jul 07 21:10:18-132888 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:18-133091 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:18-133287 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:18-133462 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:18-133699 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:18-133895 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:18-134072 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:18-134270 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:18-134513 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:18-134711 util-scheduler-8627 DEBUG Adding task: 313 / 0x4d63d80
Jul 07 21:10:18-134970 util-scheduler-8627 DEBUG Checking readiness of task: 310 / 0x4661f98
Jul 07 21:10:18-135162 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-135351 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-135540 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-135730 util-scheduler-8627 DEBUG Running task: 312 / 0x4d55220
Jul 07 21:10:18-135937 util-scheduler-8627 DEBUG Adding task: 314 / 0x4d55220
Jul 07 21:10:18-136159 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:18-136362 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:18-136571 util-scheduler-8627 DEBUG Adding task: 315 / 0x4661f98
Jul 07 21:10:18-136811 util-scheduler-8627 DEBUG Checking readiness of task: 315 / 0x4661f98
Jul 07 21:10:18-137003 util-scheduler-8627 DEBUG Checking readiness of task: 310 / 0x4661f98
Jul 07 21:10:18-137211 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-137403 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-137591 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-137782 util-scheduler-8627 DEBUG Running task: 315 / 0x4661f98
Jul 07 21:10:18-137967 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:18-138144 util-8627 DEBUG process_notify is running
Jul 07 21:10:18-138336 util-8627 DEBUG client_notify is running
Jul 07 21:10:18-138518 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:18-138715 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:18-138908 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:18-139163 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:18-139474 util-scheduler-8627 DEBUG Checking readiness of task: 310 / 0x4661f98
Jul 07 21:10:18-139667 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-139857 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-140046 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-140237 util-scheduler-8627 DEBUG Running task: 310 / 0x4661f98
Jul 07 21:10:18-140645 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:18-140877 util-scheduler-8627 DEBUG Adding task: 316 / 0x4662140
Jul 07 21:10:18-141121 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-141332 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-141538 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-141731 util-scheduler-8627 DEBUG Running task: 316 / 0x4662140
Jul 07 21:10:18-141921 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:18-142118 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:18-142334 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:18-142531 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:18-142728 util-scheduler-8627 DEBUG Adding task: 317 / 0x4661f98
Jul 07 21:10:18-142912 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:18-143117 util-scheduler-8627 DEBUG Adding task: 318 / 0x4661f98
Jul 07 21:10:18-143356 util-scheduler-8627 DEBUG Checking readiness of task: 318 / 0x4661f98
Jul 07 21:10:18-143546 util-scheduler-8627 DEBUG Checking readiness of task: 317 / 0x4661f98
Jul 07 21:10:18-143737 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:18-143925 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:18-144114 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:18-144304 util-scheduler-8627 DEBUG Running task: 317 / 0x4661f98
Jul 07 21:10:18-144487 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:18-144661 util-8627 DEBUG process_notify is running
Jul 07 21:10:18-144829 util-8627 DEBUG client_notify is running
Jul 07 21:10:18-145014 util-scheduler-8627 DEBUG Canceling task: 314 / 0x4d55220
Jul 07 21:10:18-145254 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:18-145472 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:18-145704 cadet-p2p-8627 DEBUG Checking 0x4e3f228 towards VF7F4W30 (->V8XX)
Jul 07 21:10:18-145936 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:18-146113 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:18-146298 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:18-146580 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:18-146774 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:18-146952 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:18-147138 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:18-147326 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:18-147503 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:18-147686 util-scheduler-8627 DEBUG Canceling task: 311 / 0x4d62e70
Jul 07 21:10:18-147895 util-scheduler-8627 DEBUG Adding task: 319 / 0x4d62e70
Jul 07 21:10:18-148138 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:18-148321 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:18-148501 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:18-148709 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:18-148884 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:18-149056 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:18-149274 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:18-149480 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:18-149662 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:18-149839 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:18-150028 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:18-150271 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:23-137357 util-scheduler-8627 DEBUG Checking readiness of task: 318 / 0x4661f98
Jul 07 21:10:23-137716 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-138185 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-138410 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-138669 util-scheduler-8627 DEBUG Running task: 313 / 0x4d63d80
Jul 07 21:10:23-138903 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:23-139147 cadet-tun-8627 DEBUG  kx started 65 s ago
Jul 07 21:10:23-139354 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:23-139554 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:23-139755 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:23-139989 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:23-140168 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:23-140389 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:23-140677 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:23-140874 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:23-141109 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:23-141338 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:23-141652 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:23-141851 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:23-142076 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:23-142258 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:23-142433 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:23-142637 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:23-142872 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:23-143093 util-scheduler-8627 DEBUG Adding task: 320 / 0x4d55220
Jul 07 21:10:23-143272 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:23-143475 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:23-143649 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:23-143822 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:23-144058 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:23-144253 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:23-144431 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:23-144629 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:23-144868 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:23-145066 util-scheduler-8627 DEBUG Adding task: 321 / 0x4d63d80
Jul 07 21:10:23-145339 util-scheduler-8627 DEBUG Checking readiness of task: 318 / 0x4661f98
Jul 07 21:10:23-145531 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-145720 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-145908 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-146098 util-scheduler-8627 DEBUG Running task: 320 / 0x4d55220
Jul 07 21:10:23-146305 util-scheduler-8627 DEBUG Adding task: 322 / 0x4d55220
Jul 07 21:10:23-146525 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:23-146726 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:23-146933 util-scheduler-8627 DEBUG Adding task: 323 / 0x4661f98
Jul 07 21:10:23-147172 util-scheduler-8627 DEBUG Checking readiness of task: 323 / 0x4661f98
Jul 07 21:10:23-147365 util-scheduler-8627 DEBUG Checking readiness of task: 318 / 0x4661f98
Jul 07 21:10:23-147555 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-147744 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-147933 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-148124 util-scheduler-8627 DEBUG Running task: 323 / 0x4661f98
Jul 07 21:10:23-148308 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:23-148505 util-8627 DEBUG process_notify is running
Jul 07 21:10:23-148677 util-8627 DEBUG client_notify is running
Jul 07 21:10:23-148855 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:23-149071 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:23-149283 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:23-149538 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:23-149786 util-scheduler-8627 DEBUG Checking readiness of task: 318 / 0x4661f98
Jul 07 21:10:23-149977 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-150166 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-150355 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-150544 util-scheduler-8627 DEBUG Running task: 318 / 0x4661f98
Jul 07 21:10:23-150949 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:23-151178 util-scheduler-8627 DEBUG Adding task: 324 / 0x4662140
Jul 07 21:10:23-151422 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-151613 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-151802 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-151990 util-scheduler-8627 DEBUG Running task: 324 / 0x4662140
Jul 07 21:10:23-152191 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:23-152385 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:23-152600 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:23-152796 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:23-152996 util-scheduler-8627 DEBUG Adding task: 325 / 0x4661f98
Jul 07 21:10:23-153180 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:23-153405 util-scheduler-8627 DEBUG Adding task: 326 / 0x4661f98
Jul 07 21:10:23-153642 util-scheduler-8627 DEBUG Checking readiness of task: 326 / 0x4661f98
Jul 07 21:10:23-153832 util-scheduler-8627 DEBUG Checking readiness of task: 325 / 0x4661f98
Jul 07 21:10:23-154022 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:23-154211 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:23-154400 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:23-154589 util-scheduler-8627 DEBUG Running task: 325 / 0x4661f98
Jul 07 21:10:23-154772 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:23-154946 util-8627 DEBUG process_notify is running
Jul 07 21:10:23-155114 util-8627 DEBUG client_notify is running
Jul 07 21:10:23-155297 util-scheduler-8627 DEBUG Canceling task: 322 / 0x4d55220
Jul 07 21:10:23-155518 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:23-155732 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:23-155961 cadet-p2p-8627 DEBUG Checking 0x4e41f00 towards VF7F4W30 (->V8XX)
Jul 07 21:10:23-156192 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:23-156369 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:23-156553 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:23-156848 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:23-157042 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:23-157236 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:23-157424 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:23-157611 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:23-157788 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:23-157971 util-scheduler-8627 DEBUG Canceling task: 319 / 0x4d62e70
Jul 07 21:10:23-158179 util-scheduler-8627 DEBUG Adding task: 327 / 0x4d62e70
Jul 07 21:10:23-158423 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:23-158593 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:23-158787 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:23-158985 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:23-159158 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:23-159330 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:23-159527 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:23-159730 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:23-159912 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:23-160089 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:23-160277 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:23-161316 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:26-258176 util-scheduler-8627 DEBUG Checking readiness of task: 326 / 0x4661f98
Jul 07 21:10:26-258521 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-258717 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-258911 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-259107 util-scheduler-8627 DEBUG Running task: 326 / 0x4661f98
Jul 07 21:10:26-259529 util-8627 DEBUG receive_ready read 76/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:26-259780 util-scheduler-8627 DEBUG Adding task: 328 / 0x4662140
Jul 07 21:10:26-260068 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-260267 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-260456 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-260645 util-scheduler-8627 DEBUG Running task: 328 / 0x4662140
Jul 07 21:10:26-260837 util-8627 DEBUG Received message of type 70 and size 76 from core service.
Jul 07 21:10:26-261036 core-api-8627 DEBUG Processing message of type 70 and size 76 from core service
Jul 07 21:10:26-261296 core-api-8627 DEBUG Received message of type 269 and size 40 from peer `V8XX'
Jul 07 21:10:26-261566 cadet-con-8627 INFO <-- {              POLL} on connection VF7F4W30 from V8XX
Jul 07 21:10:26-261822 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-262034 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:26-262281 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-262489 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:26-262671 cadet-con-8627 DEBUG   BCK FC
Jul 07 21:10:26-262842 cadet-con-8627 DEBUG   PID 0, OLD 0
Jul 07 21:10:26-263071 cadet-con-8627 DEBUG GMC send FWD ACK on VF7F4W30 (->V8XX)
Jul 07 21:10:26-263246 cadet-con-8627 DEBUG   getting from all channels
Jul 07 21:10:26-263418 cadet-con-8627 DEBUG   buffer available: 64
Jul 07 21:10:26-263589 cadet-con-8627 DEBUG   sending on connection
Jul 07 21:10:26-263811 cadet-con-8627 DEBUG connection send FWD ack on VF7F4W30 (->V8XX)
Jul 07 21:10:26-263988 cadet-con-8627 DEBUG  ACK 64
Jul 07 21:10:26-264167 cadet-con-8627 DEBUG  last pid 0, last ack 64, qmax 11, q 0
Jul 07 21:10:26-264437 cadet-con-8627 INFO --> {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (40 bytes)
Jul 07 21:10:26-264627 cadet-con-8627 DEBUG  ack 64
Jul 07 21:10:26-264806 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:26-265040 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-265268 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:26-265563 cadet-p2p-8627 INFO que {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 40)
Jul 07 21:10:26-265761 cadet-p2p-8627 DEBUG priority 100
Jul 07 21:10:26-265985 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:26-266167 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:26-266361 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:26-266566 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 40 bytes
Jul 07 21:10:26-266811 core-api-8627 DEBUG Asking core for transmission of 40 bytes to `V8XX'
Jul 07 21:10:26-267029 util-scheduler-8627 DEBUG Adding task: 329 / 0x4d55220
Jul 07 21:10:26-267208 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:26-267414 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:26-267589 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:26-267762 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:26-267998 cadet-p2p-8627 DEBUG QQQ  - {               ACK} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:26-268181 cadet-p2p-8627 DEBUG QQQ    payload , 64
Jul 07 21:10:26-268354 cadet-p2p-8627 DEBUG QQQ    size: 40 bytes
Jul 07 21:10:26-268551 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:26-268731 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:26-268943 util-scheduler-8627 DEBUG Adding task: 330 / 0x4661f98
Jul 07 21:10:26-269213 util-scheduler-8627 DEBUG Checking readiness of task: 330 / 0x4661f98
Jul 07 21:10:26-269410 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-269600 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-269788 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-269979 util-scheduler-8627 DEBUG Running task: 330 / 0x4661f98
Jul 07 21:10:26-270384 util-8627 DEBUG receive_ready read 144/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:26-270618 util-scheduler-8627 DEBUG Adding task: 331 / 0x4662140
Jul 07 21:10:26-270826 util-scheduler-8627 DEBUG Running task: 329 / 0x4d55220
Jul 07 21:10:26-271037 util-scheduler-8627 DEBUG Adding task: 332 / 0x4d55220
Jul 07 21:10:26-271260 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:26-271461 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:26-271664 util-scheduler-8627 DEBUG Adding task: 333 / 0x4661f98
Jul 07 21:10:26-271908 util-scheduler-8627 DEBUG Checking readiness of task: 333 / 0x4661f98
Jul 07 21:10:26-272105 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-272294 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-272482 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-272672 util-scheduler-8627 DEBUG Running task: 333 / 0x4661f98
Jul 07 21:10:26-272859 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:26-273040 util-8627 DEBUG process_notify is running
Jul 07 21:10:26-273240 util-8627 DEBUG client_notify is running
Jul 07 21:10:26-273427 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:26-273627 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:26-273816 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:26-274055 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:26-274266 util-scheduler-8627 DEBUG Running task: 331 / 0x4662140
Jul 07 21:10:26-274460 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:10:26-274661 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:10:26-274901 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:10:26-275155 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:10:26-275369 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:10:26-275606 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-275827 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:26-276066 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-276274 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:26-276456 cadet-con-8627 DEBUG   ACK
Jul 07 21:10:26-276687 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:10:26-276899 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:26-277088 util-scheduler-8627 DEBUG Canceling task: 246 / 0x4d62e70
Jul 07 21:10:26-277337 util-scheduler-8627 DEBUG Adding task: 334 / 0x4d62e70
Jul 07 21:10:26-277522 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:10:26-277729 util-scheduler-8627 DEBUG Adding task: 335 / 0x4662140
Jul 07 21:10:26-277977 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-278170 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-278360 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-278552 util-scheduler-8627 DEBUG Running task: 335 / 0x4662140
Jul 07 21:10:26-278742 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:10:26-278937 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:10:26-279154 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:10:26-279398 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection VF7F4W30 from V8XX
Jul 07 21:10:26-279609 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:10:26-279842 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-280048 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:26-280286 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:26-280491 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:26-280671 cadet-con-8627 DEBUG   ACK
Jul 07 21:10:26-280898 cadet-con-8627 DEBUG Connection VF7F4W30 (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:10:26-281078 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:26-281288 util-scheduler-8627 DEBUG Canceling task: 334 / 0x4d62e70
Jul 07 21:10:26-281502 util-scheduler-8627 DEBUG Adding task: 336 / 0x4d62e70
Jul 07 21:10:26-281683 cadet-con-8627 DEBUG   Connection ACK for us!
Jul 07 21:10:26-281871 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:26-282077 util-scheduler-8627 DEBUG Adding task: 337 / 0x4661f98
Jul 07 21:10:26-282316 util-scheduler-8627 DEBUG Checking readiness of task: 337 / 0x4661f98
Jul 07 21:10:26-282508 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-282698 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-282887 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-283077 util-scheduler-8627 DEBUG Running task: 337 / 0x4661f98
Jul 07 21:10:26-283481 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:26-283707 util-scheduler-8627 DEBUG Adding task: 338 / 0x4662140
Jul 07 21:10:26-283950 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-284141 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-284330 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-284520 util-scheduler-8627 DEBUG Running task: 338 / 0x4662140
Jul 07 21:10:26-284708 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:26-284900 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:26-285112 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:26-285335 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:26-285535 util-scheduler-8627 DEBUG Adding task: 339 / 0x4661f98
Jul 07 21:10:26-285719 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:26-285914 util-scheduler-8627 DEBUG Adding task: 340 / 0x4661f98
Jul 07 21:10:26-286151 util-scheduler-8627 DEBUG Checking readiness of task: 340 / 0x4661f98
Jul 07 21:10:26-286341 util-scheduler-8627 DEBUG Checking readiness of task: 339 / 0x4661f98
Jul 07 21:10:26-286531 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:26-286720 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:26-286926 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:26-287118 util-scheduler-8627 DEBUG Running task: 339 / 0x4661f98
Jul 07 21:10:26-287301 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:26-287477 util-8627 DEBUG process_notify is running
Jul 07 21:10:26-287650 util-8627 DEBUG client_notify is running
Jul 07 21:10:26-287832 util-scheduler-8627 DEBUG Canceling task: 332 / 0x4d55220
Jul 07 21:10:26-288052 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 40 bytes.
Jul 07 21:10:26-288269 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:26-288500 cadet-p2p-8627 DEBUG Checking 0x4e45070 towards VF7F4W30 (->V8XX)
Jul 07 21:10:26-288732 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:26-288908 cadet-p2p-8627 DEBUG   size 40 ok
Jul 07 21:10:26-289094 cadet-p2p-8627 DEBUG   raw {               ACK}
Jul 07 21:10:26-289384 cadet-p2p-8627 INFO snd {               ACK} ( 64) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 40)
Jul 07 21:10:26-289577 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:26-289755 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:26-289941 cadet-con-8627 DEBUG  sent BCK {               ACK}
Jul 07 21:10:26-290115 cadet-con-8627 DEBUG  calling cont
Jul 07 21:10:26-290295 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:26-290468 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:26-290648 cadet-p2p-8627 DEBUG   return 40
Jul 07 21:10:26-290845 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:26-291030 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:26-291203 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:26-291400 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:26-291608 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 40 bytes.
Jul 07 21:10:26-291790 core-api-8627 DEBUG Produced SEND message to core with 40 bytes payload
Jul 07 21:10:26-291968 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:26-292156 util-8627 DEBUG Transmitting message of type 76 and size 96 to core service.
Jul 07 21:10:26-292399 util-8627 DEBUG Connection transmitted 96/96 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:28-145362 util-scheduler-8627 DEBUG Checking readiness of task: 340 / 0x4661f98
Jul 07 21:10:28-145718 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-147083 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-147296 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-147492 util-scheduler-8627 DEBUG Running task: 321 / 0x4d63d80
Jul 07 21:10:28-147737 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:28-147984 cadet-tun-8627 DEBUG  kx started 70 s ago
Jul 07 21:10:28-148190 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:28-148390 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:28-148590 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:28-148827 cadet-tun-8627 DEBUG   connection VF7F4W30 (->V8XX): 3
Jul 07 21:10:28-149011 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:28-149262 cadet-tun-8627 DEBUG  selected: connection VF7F4W30 (->V8XX)
Jul 07 21:10:28-149556 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (196 bytes)
Jul 07 21:10:28-149753 cadet-con-8627 DEBUG   C_P+ 0x4d62e70 0
Jul 07 21:10:28-149990 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:28-150196 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:28-150509 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK towards V8XX (size 196)
Jul 07 21:10:28-150709 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:28-150933 cadet-con-8627 DEBUG  checking sendability of BCK traffic on VF7F4W30 (->V8XX)
Jul 07 21:10:28-151129 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:28-151304 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:28-151534 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:28-151767 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:28-151992 util-scheduler-8627 DEBUG Adding task: 341 / 0x4d55220
Jul 07 21:10:28-152175 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:28-152378 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:28-152554 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:28-152727 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4d5524c
Jul 07 21:10:28-152963 cadet-p2p-8627 DEBUG QQQ  - {                KX} BCK on VF7F4W30 (->V8XX)
Jul 07 21:10:28-153158 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:28-153359 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:28-153558 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:28-153800 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:28-153998 util-scheduler-8627 DEBUG Adding task: 342 / 0x4d63d80
Jul 07 21:10:28-154255 util-scheduler-8627 DEBUG Checking readiness of task: 340 / 0x4661f98
Jul 07 21:10:28-154446 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-154636 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-154824 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-155013 util-scheduler-8627 DEBUG Running task: 341 / 0x4d55220
Jul 07 21:10:28-155220 util-scheduler-8627 DEBUG Adding task: 343 / 0x4d55220
Jul 07 21:10:28-155440 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:28-155641 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:28-155849 util-scheduler-8627 DEBUG Adding task: 344 / 0x4661f98
Jul 07 21:10:28-156088 util-scheduler-8627 DEBUG Checking readiness of task: 344 / 0x4661f98
Jul 07 21:10:28-156280 util-scheduler-8627 DEBUG Checking readiness of task: 340 / 0x4661f98
Jul 07 21:10:28-156470 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-156658 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-156847 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-157037 util-scheduler-8627 DEBUG Running task: 344 / 0x4661f98
Jul 07 21:10:28-157244 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:28-157423 util-8627 DEBUG process_notify is running
Jul 07 21:10:28-157596 util-8627 DEBUG client_notify is running
Jul 07 21:10:28-157775 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:28-157970 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:28-158160 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:28-158413 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:28-158659 util-scheduler-8627 DEBUG Checking readiness of task: 340 / 0x4661f98
Jul 07 21:10:28-158850 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-159039 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-159228 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-159417 util-scheduler-8627 DEBUG Running task: 340 / 0x4661f98
Jul 07 21:10:28-159821 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:28-160051 util-scheduler-8627 DEBUG Adding task: 345 / 0x4662140
Jul 07 21:10:28-160294 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-160484 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-160673 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-160862 util-scheduler-8627 DEBUG Running task: 345 / 0x4662140
Jul 07 21:10:28-161052 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:28-161296 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:28-161515 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:28-161714 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:28-161913 util-scheduler-8627 DEBUG Adding task: 346 / 0x4661f98
Jul 07 21:10:28-162101 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:28-162304 util-scheduler-8627 DEBUG Adding task: 347 / 0x4661f98
Jul 07 21:10:28-162542 util-scheduler-8627 DEBUG Checking readiness of task: 347 / 0x4661f98
Jul 07 21:10:28-162733 util-scheduler-8627 DEBUG Checking readiness of task: 346 / 0x4661f98
Jul 07 21:10:28-162923 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:28-163112 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:28-163301 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:28-163491 util-scheduler-8627 DEBUG Running task: 346 / 0x4661f98
Jul 07 21:10:28-163674 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:28-163848 util-8627 DEBUG process_notify is running
Jul 07 21:10:28-164017 util-8627 DEBUG client_notify is running
Jul 07 21:10:28-164201 util-scheduler-8627 DEBUG Canceling task: 343 / 0x4d55220
Jul 07 21:10:28-164422 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:28-164636 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:28-164866 cadet-p2p-8627 DEBUG Checking 0x4e48ea8 towards VF7F4W30 (->V8XX)
Jul 07 21:10:28-165099 cadet-p2p-8627 DEBUG   on connection VF7F4W30 (->V8XX) BCK
Jul 07 21:10:28-165300 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:28-165486 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:28-165769 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection VF7F4W30 (->V8XX) (0x4d62e70) BCK (size 196)
Jul 07 21:10:28-165962 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:28-166140 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:28-166327 cadet-con-8627 DEBUG  sent BCK {                KX}
Jul 07 21:10:28-166515 cadet-con-8627 DEBUG  C_P- 0x4d62e70 1
Jul 07 21:10:28-166692 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:28-166875 util-scheduler-8627 DEBUG Canceling task: 327 / 0x4d62e70
Jul 07 21:10:28-167083 util-scheduler-8627 DEBUG Adding task: 348 / 0x4d62e70
Jul 07 21:10:28-167327 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:28-167496 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:28-167676 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:28-167873 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:28-168047 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:28-168221 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:28-168420 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:28-168625 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:28-168808 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:28-168985 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:28-169174 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:28-169450 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:32-025803 util-scheduler-8627 DEBUG Checking readiness of task: 347 / 0x4661f98
Jul 07 21:10:32-026198 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-026399 util-scheduler-8627 DEBUG Checking readiness of task: 129 / 0x4663c60
Jul 07 21:10:32-026598 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:32-026798 util-scheduler-8627 DEBUG Running task: 129 / 0x4663c60
Jul 07 21:10:32-027228 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:10:32-027522 util-scheduler-8627 DEBUG Adding task: 349 / 0x4663e08
Jul 07 21:10:32-027807 util-scheduler-8627 DEBUG Checking readiness of task: 347 / 0x4661f98
Jul 07 21:10:32-028005 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-028199 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:32-028394 util-scheduler-8627 DEBUG Running task: 347 / 0x4661f98
Jul 07 21:10:32-028801 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:32-029034 util-scheduler-8627 DEBUG Adding task: 350 / 0x4662140
Jul 07 21:10:32-029303 util-scheduler-8627 DEBUG Running task: 349 / 0x4663e08
Jul 07 21:10:32-029507 util-8627 DEBUG Received message of type 362 and size 40 from transport service.
Jul 07 21:10:32-029712 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:32-029939 util-scheduler-8627 DEBUG Adding task: 351 / 0x4663c60
Jul 07 21:10:32-031607 transport-api-8627 DEBUG Receiving `DISCONNECT' message for `V8XX'.
Jul 07 21:10:32-037305 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-037635 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-037832 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:32-038030 util-scheduler-8627 DEBUG Running task: 350 / 0x4662140
Jul 07 21:10:32-038225 util-8627 DEBUG Received message of type 68 and size 40 from core service.
Jul 07 21:10:32-038429 core-api-8627 DEBUG Processing message of type 68 and size 40 from core service
Jul 07 21:10:32-040190 core-api-8627 DEBUG Received notification about disconnect from `V8XX'.
Jul 07 21:10:32-043927 cadet-p2p-8627 INFO DISCONNECTED GN10 <= V8XX
Jul 07 21:10:32-048037 cadet-p2p-8627 DEBUG   notifying VF7F4W30 (->V8XX) due to V8XX
Jul 07 21:10:32-049785 cadet-con-8627 DEBUG  notify broken on VF7F4W30 (->V8XX) due to V8XX disconnect
Jul 07 21:10:32-050279 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:32-050497 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:32-052346 cadet-con-8627 DEBUG destroying connection VF7F4W30 (->V8XX)
Jul 07 21:10:32-053404 cadet-con-8627 DEBUG  fc's f: 0x4d62e74, b: 0x4d62ea8
Jul 07 21:10:32-054546 cadet-con-8627 DEBUG  fc tasks f: 0, b: 0
Jul 07 21:10:32-056204 cadet-con-8627 DEBUG  *** Cancel FWD queues for connection VF7F4W30 (->V8XX)
Jul 07 21:10:32-057079 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:32-057323 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:32-058796 cadet-con-8627 DEBUG  *** Cancel BCK queues for connection VF7F4W30 (->V8XX)
Jul 07 21:10:32-059194 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:32-059412 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:32-059889 cadet-con-8627 DEBUG  get next hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:32-060106 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:32-061584 cadet-p2p-8627 DEBUG removing connection VF7F4W30 (->V8XX)
Jul 07 21:10:32-062746 cadet-p2p-8627 DEBUG from peer GN10
Jul 07 21:10:32-064205 cadet-p2p-8627 DEBUG peer GN10 ok, has 1 connections.
Jul 07 21:10:32-067365 cadet-con-8627 DEBUG  get prev hop VF7F4W30 (->V8XX) [1/2]
Jul 07 21:10:32-067595 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:32-068301 cadet-p2p-8627 DEBUG removing connection VF7F4W30 (->V8XX)
Jul 07 21:10:32-068661 cadet-p2p-8627 DEBUG from peer V8XX
Jul 07 21:10:32-069026 cadet-p2p-8627 DEBUG peer V8XX ok, has 1 connections.
Jul 07 21:10:32-070290 cadet-con-8627 DEBUG  fc tasks f: 0, b: 0
Jul 07 21:10:32-072528 cadet-tun-8627 DEBUG Removing connection VF7F4W30 (->V8XX) from tunnel V8XX
Jul 07 21:10:32-075286 cadet-tun-8627 DEBUG   no more connections, getting new ones
Jul 07 21:10:32-075958 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_READY => CADET_TUNNEL_SEARCHING
Jul 07 21:10:32-077527 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:32-082166 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-083427 transport-api-8627 DEBUG Control transmit of 382 bytes requested
Jul 07 21:10:32-083826 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-084055 util-scheduler-8627 DEBUG Adding task: 352 / 0x46623e0
Jul 07 21:10:32-086687 cadet-p2p-8627 DEBUG   Starting DHT GET for peer V8XX
Jul 07 21:10:32-088067 cadet-dht-8627 DEBUG   Starting DHT GET for peer V8XX
Jul 07 21:10:32-091619 dht-api-8627 DEBUG Sending query for V8XXK9GA to DHT 0x46641b8
Jul 07 21:10:32-097577 util-8627 DEBUG Scheduling transmission (0x4665ad8).
Jul 07 21:10:32-097808 util-scheduler-8627 DEBUG Adding task: 353 / 0x4665ad8
Jul 07 21:10:32-101645 util-scheduler-8627 DEBUG Canceling task: 336 / 0x4d62e70
Jul 07 21:10:32-102197 util-scheduler-8627 DEBUG Canceling task: 348 / 0x4d62e70
Jul 07 21:10:32-104545 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:10:32-104760 util-scheduler-8627 DEBUG Adding task: 354 / 0x4d50e20
Jul 07 21:10:32-111228 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:32-111451 util-scheduler-8627 DEBUG Adding task: 355 / 0x4661f98
Jul 07 21:10:32-111727 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-111925 util-scheduler-8627 DEBUG Checking readiness of task: 354 / 0x4d50e20
Jul 07 21:10:32-112118 util-scheduler-8627 DEBUG Checking readiness of task: 353 / 0x4665ad8
Jul 07 21:10:32-112309 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-112499 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-112688 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:32-112883 util-scheduler-8627 DEBUG Running task: 353 / 0x4665ad8
Jul 07 21:10:32-113073 util-8627 DEBUG transmit_ready running (0x4665ad8).
Jul 07 21:10:32-113275 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-113450 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-114118 dht-api-8627 DEBUG Forwarded request of 88 bytes to DHT service
Jul 07 21:10:32-114543 util-8627 DEBUG Transmitting message of type 143 and size 88 to dht service.
Jul 07 21:10:32-114817 util-8627 DEBUG Connection transmitted 88/88 bytes to `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665ad8)
Jul 07 21:10:32-115032 util-scheduler-8627 DEBUG Running task: 354 / 0x4d50e20
Jul 07 21:10:32-115219 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:10:32-115395 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-115565 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-115810 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:10:32-116023 util-scheduler-8627 DEBUG Adding task: 356 / 0x4d50e20
Jul 07 21:10:32-116226 util-8627 DEBUG Transmitting message of type 168 and size 36 to statistics service.
Jul 07 21:10:32-116464 util-8627 DEBUG Connection transmitted 36/36 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:10:32-116839 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:10:32-117049 util-scheduler-8627 DEBUG Running task: 352 / 0x46623e0
Jul 07 21:10:32-117367 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-117572 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-117788 util-scheduler-8627 DEBUG Adding task: 357 / 0x4663c60
Jul 07 21:10:32-118042 util-scheduler-8627 DEBUG Checking readiness of task: 357 / 0x4663c60
Jul 07 21:10:32-118237 util-scheduler-8627 DEBUG Checking readiness of task: 356 / 0x4d50e20
Jul 07 21:10:32-118430 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-118621 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-118811 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-119000 util-scheduler-8627 DEBUG Checking readiness of task: 76 / 0x4665ad8
Jul 07 21:10:32-119192 util-scheduler-8627 DEBUG Running task: 76 / 0x4665ad8
Jul 07 21:10:32-119605 util-8627 DEBUG receive_ready read 2828/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665ad8)!
Jul 07 21:10:32-119925 util-scheduler-8627 DEBUG Adding task: 358 / 0x4665c80
Jul 07 21:10:32-120137 util-scheduler-8627 DEBUG Running task: 356 / 0x4d50e20
Jul 07 21:10:32-120321 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:10:32-120496 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-120665 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-120878 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:10:32-121124 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:10:32-121368 util-scheduler-8627 DEBUG Running task: 357 / 0x4663c60
Jul 07 21:10:32-121550 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-121751 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-121920 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-123445 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-126705 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-126936 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-127138 util-scheduler-8627 DEBUG Adding task: 359 / 0x46623e0
Jul 07 21:10:32-129543 transport-api-8627 DEBUG Added 382 bytes of control message at 0
Jul 07 21:10:32-130174 util-scheduler-8627 DEBUG Canceling task: 359 / 0x46623e0
Jul 07 21:10:32-130570 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-130776 util-scheduler-8627 DEBUG Adding task: 360 / 0x46623e0
Jul 07 21:10:32-131127 transport-api-8627 DEBUG Transmitting 382 bytes to transport service
Jul 07 21:10:32-131329 util-8627 DEBUG Transmitting message of type 17 and size 382 to transport service.
Jul 07 21:10:32-131581 util-8627 DEBUG Connection transmitted 382/382 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-131839 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-132031 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-132221 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-132411 util-scheduler-8627 DEBUG Running task: 360 / 0x46623e0
Jul 07 21:10:32-132592 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-132782 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-132982 util-scheduler-8627 DEBUG Adding task: 361 / 0x4663c60
Jul 07 21:10:32-133181 util-scheduler-8627 DEBUG Running task: 358 / 0x4665c80
Jul 07 21:10:32-133394 util-8627 DEBUG Received message of type 145 and size 619 from dht service.
Jul 07 21:10:32-134286 util-scheduler-8627 DEBUG Adding task: 362 / 0x4665c80
Jul 07 21:10:32-135692 dht-api-8627 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46641b8
Jul 07 21:10:32-140242 dht-api-8627 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 21:10:32-146781 cadet-dht-8627 DEBUG    GET has 0 hops.
Jul 07 21:10:32-147955 cadet-dht-8627 DEBUG    PUT has 1 hops.
Jul 07 21:10:32-149723 cadet-dht-8627 DEBUG    Adding from PUT: V8XX.
Jul 07 21:10:32-151719 cadet-dht-8627 DEBUG    (first of PUT: V8XX)
Jul 07 21:10:32-152685 cadet-dht-8627 DEBUG    In total: 2 hops
Jul 07 21:10:32-155328 cadet-dht-8627 DEBUG        1: GN10
Jul 07 21:10:32-155805 cadet-dht-8627 DEBUG        9: V8XX
Jul 07 21:10:32-159040 cadet-dht-8627 INFO Got path from DHT:  GN10 V8XX
Jul 07 21:10:32-160828 cadet-dht-8627 DEBUG Got HELLO for V8XX
Jul 07 21:10:32-163448 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:32-163636 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:32-165867 cadet-p2p-8627 DEBUG  ... connect!
Jul 07 21:10:32-166555 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:32-166919 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-167116 transport-api-8627 DEBUG Control transmit of 382 bytes requested
Jul 07 21:10:32-167650 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-167878 util-scheduler-8627 DEBUG Adding task: 363 / 0x46623e0
Jul 07 21:10:32-168678 cadet-p2p-8627 DEBUG set hello for V8XX
Jul 07 21:10:32-169159 cadet-p2p-8627 DEBUG  merge into 0x4e50f10 (491 bytes)
Jul 07 21:10:32-169838 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-170034 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-170231 util-scheduler-8627 DEBUG Canceling task: 363 / 0x46623e0
Jul 07 21:10:32-170453 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-170652 util-scheduler-8627 DEBUG Adding task: 364 / 0x46623e0
Jul 07 21:10:32-172159 util-scheduler-8627 DEBUG Checking readiness of task: 361 / 0x4663c60
Jul 07 21:10:32-172360 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-172785 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-173061 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-173315 util-scheduler-8627 DEBUG Running task: 361 / 0x4663c60
Jul 07 21:10:32-173507 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-173689 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-173862 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-176078 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-178816 transport-api-8627 DEBUG Added 40 bytes of control message at 0
Jul 07 21:10:32-180174 util-scheduler-8627 DEBUG Canceling task: 364 / 0x46623e0
Jul 07 21:10:32-180412 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-180622 util-scheduler-8627 DEBUG Adding task: 365 / 0x46623e0
Jul 07 21:10:32-180808 transport-api-8627 DEBUG Transmitting 40 bytes to transport service
Jul 07 21:10:32-181008 util-8627 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 21:10:32-181307 util-8627 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-181522 util-scheduler-8627 DEBUG Running task: 362 / 0x4665c80
Jul 07 21:10:32-181715 util-8627 DEBUG Received message of type 145 and size 747 from dht service.
Jul 07 21:10:32-181984 util-scheduler-8627 DEBUG Adding task: 366 / 0x4665c80
Jul 07 21:10:32-182303 dht-api-8627 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46641b8
Jul 07 21:10:32-182620 dht-api-8627 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 21:10:32-184950 cadet-dht-8627 DEBUG    GET has 0 hops.
Jul 07 21:10:32-185336 cadet-dht-8627 DEBUG    PUT has 5 hops.
Jul 07 21:10:32-185710 cadet-dht-8627 DEBUG    Adding from PUT: KNAS.
Jul 07 21:10:32-186075 cadet-dht-8627 DEBUG    Adding from PUT: STRN.
Jul 07 21:10:32-186301 cadet-dht-8627 DEBUG    Adding from PUT: VYGR.
Jul 07 21:10:32-188069 cadet-dht-8627 DEBUG    Adding from PUT: GN10.
Jul 07 21:10:32-188290 cadet-dht-8627 DEBUG    Adding from PUT: V8XX.
Jul 07 21:10:32-188726 cadet-dht-8627 DEBUG    (first of PUT: V8XX)
Jul 07 21:10:32-189057 cadet-dht-8627 DEBUG    In total: 2 hops
Jul 07 21:10:32-189298 cadet-dht-8627 DEBUG        1: GN10
Jul 07 21:10:32-189504 cadet-dht-8627 DEBUG        9: V8XX
Jul 07 21:10:32-189964 cadet-dht-8627 INFO Got path from DHT:  GN10 V8XX
Jul 07 21:10:32-190343 cadet-dht-8627 DEBUG Got HELLO for V8XX
Jul 07 21:10:32-190581 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:32-190761 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:32-191041 cadet-p2p-8627 DEBUG  ... connect!
Jul 07 21:10:32-191245 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:32-191518 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-191712 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-191912 util-scheduler-8627 DEBUG Canceling task: 365 / 0x46623e0
Jul 07 21:10:32-192134 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-192369 util-scheduler-8627 DEBUG Adding task: 367 / 0x46623e0
Jul 07 21:10:32-192591 cadet-p2p-8627 DEBUG set hello for V8XX
Jul 07 21:10:32-193331 cadet-p2p-8627 DEBUG  merge into 0x4e535a8 (491 bytes)
Jul 07 21:10:32-193591 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-193782 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-193975 util-scheduler-8627 DEBUG Canceling task: 367 / 0x46623e0
Jul 07 21:10:32-194191 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-194388 util-scheduler-8627 DEBUG Adding task: 368 / 0x46623e0
Jul 07 21:10:32-194658 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-194851 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-195041 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-195232 util-scheduler-8627 DEBUG Running task: 368 / 0x46623e0
Jul 07 21:10:32-195415 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-195611 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-195817 util-scheduler-8627 DEBUG Adding task: 369 / 0x4663c60
Jul 07 21:10:32-196015 util-scheduler-8627 DEBUG Running task: 366 / 0x4665c80
Jul 07 21:10:32-196205 util-8627 DEBUG Received message of type 145 and size 747 from dht service.
Jul 07 21:10:32-196507 util-scheduler-8627 DEBUG Adding task: 370 / 0x4665c80
Jul 07 21:10:32-196720 dht-api-8627 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46641b8
Jul 07 21:10:32-196929 dht-api-8627 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 21:10:32-198194 cadet-dht-8627 DEBUG    GET has 0 hops.
Jul 07 21:10:32-198379 cadet-dht-8627 DEBUG    PUT has 5 hops.
Jul 07 21:10:32-198588 cadet-dht-8627 DEBUG    Adding from PUT: KNAS.
Jul 07 21:10:32-198799 cadet-dht-8627 DEBUG    Adding from PUT: STRN.
Jul 07 21:10:32-199006 cadet-dht-8627 DEBUG    Adding from PUT: TZQE.
Jul 07 21:10:32-199228 cadet-dht-8627 DEBUG    Adding from PUT: GN10.
Jul 07 21:10:32-199433 cadet-dht-8627 DEBUG    Adding from PUT: V8XX.
Jul 07 21:10:32-199635 cadet-dht-8627 DEBUG    (first of PUT: V8XX)
Jul 07 21:10:32-199808 cadet-dht-8627 DEBUG    In total: 2 hops
Jul 07 21:10:32-200009 cadet-dht-8627 DEBUG        1: GN10
Jul 07 21:10:32-200210 cadet-dht-8627 DEBUG        9: V8XX
Jul 07 21:10:32-200502 cadet-dht-8627 INFO Got path from DHT:  GN10 V8XX
Jul 07 21:10:32-200726 cadet-dht-8627 DEBUG Got HELLO for V8XX
Jul 07 21:10:32-200954 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:32-201132 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:32-201345 cadet-p2p-8627 DEBUG  ... connect!
Jul 07 21:10:32-201541 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:32-201783 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-201972 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-202183 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-202384 util-scheduler-8627 DEBUG Adding task: 371 / 0x46623e0
Jul 07 21:10:32-202602 cadet-p2p-8627 DEBUG set hello for V8XX
Jul 07 21:10:32-203084 cadet-p2p-8627 DEBUG  merge into 0x4e55888 (491 bytes)
Jul 07 21:10:32-203334 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-203527 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-203718 util-scheduler-8627 DEBUG Canceling task: 371 / 0x46623e0
Jul 07 21:10:32-203934 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-204130 util-scheduler-8627 DEBUG Adding task: 372 / 0x46623e0
Jul 07 21:10:32-204376 util-scheduler-8627 DEBUG Checking readiness of task: 369 / 0x4663c60
Jul 07 21:10:32-204569 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-204775 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-204984 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-205177 util-scheduler-8627 DEBUG Running task: 369 / 0x4663c60
Jul 07 21:10:32-205389 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-205567 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-205738 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-206088 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-206301 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-206498 util-scheduler-8627 DEBUG Canceling task: 372 / 0x46623e0
Jul 07 21:10:32-206714 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-206911 util-scheduler-8627 DEBUG Adding task: 373 / 0x46623e0
Jul 07 21:10:32-207739 transport-api-8627 DEBUG Added 382 bytes of control message at 0
Jul 07 21:10:32-208225 util-scheduler-8627 DEBUG Canceling task: 373 / 0x46623e0
Jul 07 21:10:32-208452 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-208652 util-scheduler-8627 DEBUG Adding task: 374 / 0x46623e0
Jul 07 21:10:32-208836 transport-api-8627 DEBUG Transmitting 382 bytes to transport service
Jul 07 21:10:32-209030 util-8627 DEBUG Transmitting message of type 17 and size 382 to transport service.
Jul 07 21:10:32-209320 util-8627 DEBUG Connection transmitted 382/382 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-209531 util-scheduler-8627 DEBUG Running task: 370 / 0x4665c80
Jul 07 21:10:32-209720 util-8627 DEBUG Received message of type 145 and size 715 from dht service.
Jul 07 21:10:32-209915 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:32-210123 util-scheduler-8627 DEBUG Adding task: 375 / 0x4665ad8
Jul 07 21:10:32-210325 dht-api-8627 DEBUG Received reply for `V8XXK9GA' from DHT service 0x46641b8
Jul 07 21:10:32-210527 dht-api-8627 DEBUG Giving 491 byte reply for V8XXK9GA to application
Jul 07 21:10:32-211609 cadet-dht-8627 DEBUG    GET has 0 hops.
Jul 07 21:10:32-211788 cadet-dht-8627 DEBUG    PUT has 4 hops.
Jul 07 21:10:32-211992 cadet-dht-8627 DEBUG    Adding from PUT: D3TJ.
Jul 07 21:10:32-212201 cadet-dht-8627 DEBUG    Adding from PUT: WAKN.
Jul 07 21:10:32-212423 cadet-dht-8627 DEBUG    Adding from PUT: GN10.
Jul 07 21:10:32-212661 cadet-dht-8627 DEBUG    Adding from PUT: V8XX.
Jul 07 21:10:32-212865 cadet-dht-8627 DEBUG    (first of PUT: V8XX)
Jul 07 21:10:32-213037 cadet-dht-8627 DEBUG    In total: 2 hops
Jul 07 21:10:32-213262 cadet-dht-8627 DEBUG        1: GN10
Jul 07 21:10:32-213466 cadet-dht-8627 DEBUG        9: V8XX
Jul 07 21:10:32-213756 cadet-dht-8627 INFO Got path from DHT:  GN10 V8XX
Jul 07 21:10:32-213969 cadet-dht-8627 DEBUG Got HELLO for V8XX
Jul 07 21:10:32-214191 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:32-214368 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:32-214553 cadet-p2p-8627 DEBUG  ... connect!
Jul 07 21:10:32-214747 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:32-214988 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-215176 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-215368 util-scheduler-8627 DEBUG Canceling task: 374 / 0x46623e0
Jul 07 21:10:32-215585 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-215792 util-scheduler-8627 DEBUG Adding task: 376 / 0x46623e0
Jul 07 21:10:32-216010 cadet-p2p-8627 DEBUG set hello for V8XX
Jul 07 21:10:32-216509 cadet-p2p-8627 DEBUG  merge into 0x4e58100 (491 bytes)
Jul 07 21:10:32-216760 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:32-216949 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:32-217139 util-scheduler-8627 DEBUG Canceling task: 376 / 0x46623e0
Jul 07 21:10:32-217381 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-217594 util-scheduler-8627 DEBUG Adding task: 377 / 0x46623e0
Jul 07 21:10:32-217842 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-218034 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-218222 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-218410 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-218600 util-scheduler-8627 DEBUG Running task: 377 / 0x46623e0
Jul 07 21:10:32-218781 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-218973 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-219172 util-scheduler-8627 DEBUG Adding task: 378 / 0x4663c60
Jul 07 21:10:32-219409 util-scheduler-8627 DEBUG Checking readiness of task: 378 / 0x4663c60
Jul 07 21:10:32-219600 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-219790 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-219978 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-220166 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-220357 util-scheduler-8627 DEBUG Running task: 378 / 0x4663c60
Jul 07 21:10:32-220540 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-220725 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-220894 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-221065 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-221289 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-221510 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-221706 util-scheduler-8627 DEBUG Adding task: 379 / 0x46623e0
Jul 07 21:10:32-222211 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-222414 util-scheduler-8627 DEBUG Canceling task: 379 / 0x46623e0
Jul 07 21:10:32-222634 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-222831 util-scheduler-8627 DEBUG Adding task: 380 / 0x46623e0
Jul 07 21:10:32-223013 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-223205 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-223460 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-223708 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-223899 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-224088 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-224276 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-224465 util-scheduler-8627 DEBUG Running task: 380 / 0x46623e0
Jul 07 21:10:32-224645 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-224833 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-225031 util-scheduler-8627 DEBUG Adding task: 381 / 0x4663c60
Jul 07 21:10:32-225293 util-scheduler-8627 DEBUG Checking readiness of task: 381 / 0x4663c60
Jul 07 21:10:32-225484 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-225673 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-225862 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-226050 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-226240 util-scheduler-8627 DEBUG Running task: 381 / 0x4663c60
Jul 07 21:10:32-226422 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-226596 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-226764 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-226934 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-227130 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-227355 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-227551 util-scheduler-8627 DEBUG Adding task: 382 / 0x46623e0
Jul 07 21:10:32-227745 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-227939 util-scheduler-8627 DEBUG Canceling task: 382 / 0x46623e0
Jul 07 21:10:32-228154 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-228348 util-scheduler-8627 DEBUG Adding task: 383 / 0x46623e0
Jul 07 21:10:32-228528 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-228719 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-228967 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-229241 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-229434 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-229623 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-229811 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-229999 util-scheduler-8627 DEBUG Running task: 383 / 0x46623e0
Jul 07 21:10:32-230178 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-230366 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-230562 util-scheduler-8627 DEBUG Adding task: 384 / 0x4663c60
Jul 07 21:10:32-230797 util-scheduler-8627 DEBUG Checking readiness of task: 384 / 0x4663c60
Jul 07 21:10:32-230998 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-231187 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-231375 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-231562 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-231752 util-scheduler-8627 DEBUG Running task: 384 / 0x4663c60
Jul 07 21:10:32-231935 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-232108 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-232280 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-232451 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-232647 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-232857 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-233052 util-scheduler-8627 DEBUG Adding task: 385 / 0x46623e0
Jul 07 21:10:32-233271 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-233466 util-scheduler-8627 DEBUG Canceling task: 385 / 0x46623e0
Jul 07 21:10:32-233681 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-233876 util-scheduler-8627 DEBUG Adding task: 386 / 0x46623e0
Jul 07 21:10:32-234056 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-234247 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-234496 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-234739 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-234929 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-235116 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-235305 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-235492 util-scheduler-8627 DEBUG Running task: 386 / 0x46623e0
Jul 07 21:10:32-235672 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-235859 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-236055 util-scheduler-8627 DEBUG Adding task: 387 / 0x4663c60
Jul 07 21:10:32-236289 util-scheduler-8627 DEBUG Checking readiness of task: 387 / 0x4663c60
Jul 07 21:10:32-236494 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-236684 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-236873 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-237062 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-237278 util-scheduler-8627 DEBUG Running task: 387 / 0x4663c60
Jul 07 21:10:32-237462 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-237635 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-237815 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-237986 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-238182 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-238392 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-238587 util-scheduler-8627 DEBUG Adding task: 388 / 0x46623e0
Jul 07 21:10:32-238781 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-238974 util-scheduler-8627 DEBUG Canceling task: 388 / 0x46623e0
Jul 07 21:10:32-239189 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-239383 util-scheduler-8627 DEBUG Adding task: 389 / 0x46623e0
Jul 07 21:10:32-239563 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-239754 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-240002 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-240246 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-240445 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-240634 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-240822 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-241011 util-scheduler-8627 DEBUG Running task: 389 / 0x46623e0
Jul 07 21:10:32-241212 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-241404 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-241601 util-scheduler-8627 DEBUG Adding task: 390 / 0x4663c60
Jul 07 21:10:32-241836 util-scheduler-8627 DEBUG Checking readiness of task: 390 / 0x4663c60
Jul 07 21:10:32-242027 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-242219 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-242407 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-242595 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-242785 util-scheduler-8627 DEBUG Running task: 390 / 0x4663c60
Jul 07 21:10:32-242967 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-243141 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-243309 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-243480 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-243675 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-243885 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-244080 util-scheduler-8627 DEBUG Adding task: 391 / 0x46623e0
Jul 07 21:10:32-244273 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-244467 util-scheduler-8627 DEBUG Canceling task: 391 / 0x46623e0
Jul 07 21:10:32-244681 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-244875 util-scheduler-8627 DEBUG Adding task: 392 / 0x46623e0
Jul 07 21:10:32-245056 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-245272 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-245520 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-245778 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-245969 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-246158 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-246348 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-246540 util-scheduler-8627 DEBUG Running task: 392 / 0x46623e0
Jul 07 21:10:32-246721 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-246909 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-247107 util-scheduler-8627 DEBUG Adding task: 393 / 0x4663c60
Jul 07 21:10:32-247343 util-scheduler-8627 DEBUG Checking readiness of task: 393 / 0x4663c60
Jul 07 21:10:32-247535 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-247725 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-247914 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-248102 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-248292 util-scheduler-8627 DEBUG Running task: 393 / 0x4663c60
Jul 07 21:10:32-248475 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-248648 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-248816 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-249219 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-250059 transport-api-8627 DEBUG Added 40 bytes of control message at 0
Jul 07 21:10:32-250283 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-250484 util-scheduler-8627 DEBUG Adding task: 394 / 0x46623e0
Jul 07 21:10:32-250667 transport-api-8627 DEBUG Transmitting 40 bytes to transport service
Jul 07 21:10:32-250869 util-8627 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 21:10:32-251118 util-8627 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-251364 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-251554 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-251743 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-251932 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-252121 util-scheduler-8627 DEBUG Running task: 394 / 0x46623e0
Jul 07 21:10:32-252305 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-252615 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-252816 util-scheduler-8627 DEBUG Adding task: 395 / 0x4663c60
Jul 07 21:10:32-253053 util-scheduler-8627 DEBUG Checking readiness of task: 395 / 0x4663c60
Jul 07 21:10:32-253270 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-253462 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-253650 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-253839 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-254030 util-scheduler-8627 DEBUG Running task: 395 / 0x4663c60
Jul 07 21:10:32-254213 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-254387 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-254555 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-254726 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-254924 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-255136 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-255331 util-scheduler-8627 DEBUG Adding task: 396 / 0x46623e0
Jul 07 21:10:32-255525 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-255733 util-scheduler-8627 DEBUG Canceling task: 396 / 0x46623e0
Jul 07 21:10:32-255950 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-256146 util-scheduler-8627 DEBUG Adding task: 397 / 0x46623e0
Jul 07 21:10:32-256326 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-256519 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-256958 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-257235 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-257429 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-257618 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-257807 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-257997 util-scheduler-8627 DEBUG Running task: 397 / 0x46623e0
Jul 07 21:10:32-258177 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-258365 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-258564 util-scheduler-8627 DEBUG Adding task: 398 / 0x4663c60
Jul 07 21:10:32-258799 util-scheduler-8627 DEBUG Checking readiness of task: 398 / 0x4663c60
Jul 07 21:10:32-258990 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-259179 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-259367 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-259555 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-259745 util-scheduler-8627 DEBUG Running task: 398 / 0x4663c60
Jul 07 21:10:32-259938 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-260113 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-260281 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-260452 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:32-260650 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:32-260872 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-261069 util-scheduler-8627 DEBUG Adding task: 399 / 0x46623e0
Jul 07 21:10:32-261291 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:32-261488 util-scheduler-8627 DEBUG Canceling task: 399 / 0x46623e0
Jul 07 21:10:32-261704 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:32-261899 util-scheduler-8627 DEBUG Adding task: 400 / 0x46623e0
Jul 07 21:10:32-262079 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:32-262274 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:32-262521 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:32-262766 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-262956 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-263145 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-263333 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-263522 util-scheduler-8627 DEBUG Running task: 400 / 0x46623e0
Jul 07 21:10:32-263702 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:32-263890 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:32-264086 util-scheduler-8627 DEBUG Adding task: 401 / 0x4663c60
Jul 07 21:10:32-264320 util-scheduler-8627 DEBUG Checking readiness of task: 401 / 0x4663c60
Jul 07 21:10:32-264510 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:32-264699 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:32-264887 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:32-265099 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:32-265316 util-scheduler-8627 DEBUG Running task: 401 / 0x4663c60
Jul 07 21:10:32-265501 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:32-265674 util-8627 DEBUG process_notify is running
Jul 07 21:10:32-265842 util-8627 DEBUG client_notify is running
Jul 07 21:10:32-266044 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-266239 transport-api-8627 DEBUG Added 40 bytes of control message at 0
Jul 07 21:10:32-266457 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-266651 transport-api-8627 DEBUG Added 40 bytes of control message at 40
Jul 07 21:10:32-266863 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-267056 transport-api-8627 DEBUG Added 40 bytes of control message at 80
Jul 07 21:10:32-267268 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-267462 transport-api-8627 DEBUG Added 40 bytes of control message at 120
Jul 07 21:10:32-267675 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-267868 transport-api-8627 DEBUG Added 40 bytes of control message at 160
Jul 07 21:10:32-268080 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-268274 transport-api-8627 DEBUG Added 40 bytes of control message at 200
Jul 07 21:10:32-268487 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:32-268681 transport-api-8627 DEBUG Added 40 bytes of control message at 240
Jul 07 21:10:32-268872 transport-api-8627 DEBUG Transmitting 280 bytes to transport service
Jul 07 21:10:32-269064 util-8627 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 21:10:32-269338 util-8627 DEBUG Connection transmitted 280/280 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:33-155025 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:33-155372 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:33-156262 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:33-156499 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:33-156743 util-scheduler-8627 DEBUG Running task: 342 / 0x4d63d80
Jul 07 21:10:33-156981 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:33-157250 cadet-tun-8627 DEBUG  kx started 75 s ago
Jul 07 21:10:33-157460 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:33-157660 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:33-158029 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:33-158466 cadet-tun-8627 DEBUG  selected: connection NULL
Jul 07 21:10:33-160268 cadet-tun-8627 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 21:10:33-161718 cadet-tun-8627 WARNING TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_SENT
Jul 07 21:10:33-162859 cadet-tun-8627 WARNING TTT  kx_ctx 0x4d7b4d0, rekey_task 0
Jul 07 21:10:33-163947 cadet-tun-8627 WARNING TTT  tq_head (nil), tq_tail (nil)
Jul 07 21:10:33-165035 cadet-tun-8627 WARNING TTT  destroy 0
Jul 07 21:10:33-166023 cadet-tun-8627 WARNING TTT  channels:
Jul 07 21:10:33-167105 cadet-tun-8627 WARNING TTT  connections:
Jul 07 21:10:33-168231 cadet-tun-8627 WARNING TTT DEBUG TUNNEL END
Jul 07 21:10:33-168925 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:33-169139 util-scheduler-8627 DEBUG Adding task: 402 / 0x4d63d80
Jul 07 21:10:33-593952 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:33-594230 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:33-594425 util-scheduler-8627 DEBUG Checking readiness of task: 351 / 0x4663c60
Jul 07 21:10:33-594618 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:33-594840 util-scheduler-8627 DEBUG Running task: 351 / 0x4663c60
Jul 07 21:10:33-595263 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:10:33-595511 util-scheduler-8627 DEBUG Adding task: 403 / 0x4663e08
Jul 07 21:10:33-595770 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:33-595961 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:33-596151 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:33-596340 util-scheduler-8627 DEBUG Running task: 403 / 0x4663e08
Jul 07 21:10:33-596533 util-8627 DEBUG Received message of type 361 and size 44 from transport service.
Jul 07 21:10:33-596758 util-scheduler-8627 DEBUG Adding task: 404 / 0x4663e08
Jul 07 21:10:33-596978 transport-api-8627 DEBUG Receiving `CONNECT' message for `V8XX'.
Jul 07 21:10:33-597211 transport-api-8627 DEBUG Creating entry for neighbour `V8XX'.
Jul 07 21:10:33-597409 util-bandwidth-8627 DEBUG Initializing bandwidth of 1024 Bps
Jul 07 21:10:33-597602 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 initialized with 1024 Bps and max carry 5
Jul 07 21:10:33-597828 util-scheduler-8627 DEBUG Adding task: 405 / 0x4e5ece8
Jul 07 21:10:33-598054 transport-api-8627 DEBUG Receiving `CONNECT' message for `V8XX' with quota 9608
Jul 07 21:10:33-598245 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 bandwidth changed to 9608 Bps
Jul 07 21:10:33-598481 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 updated, have 1024 Bps, last update was 840 µs ago
Jul 07 21:10:33-598693 util-scheduler-8627 DEBUG Canceling task: 405 / 0x4e5ece8
Jul 07 21:10:33-598921 util-scheduler-8627 DEBUG Adding task: 406 / 0x4e5ece8
Jul 07 21:10:33-599155 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:33-599345 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:33-599533 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:33-599739 util-scheduler-8627 DEBUG Running task: 404 / 0x4663e08
Jul 07 21:10:33-599930 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:10:33-600119 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:33-600331 util-scheduler-8627 DEBUG Adding task: 407 / 0x4663c60
Jul 07 21:10:33-600516 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:10:33-600732 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 9608
Jul 07 21:10:33-600922 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 bandwidth changed to 9608 Bps
Jul 07 21:10:33-601150 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 updated, have 9608 Bps, last update was 2675 µs ago
Jul 07 21:10:33-601378 util-scheduler-8627 DEBUG Canceling task: 406 / 0x4e5ece8
Jul 07 21:10:33-601591 util-scheduler-8627 DEBUG Adding task: 408 / 0x4e5ece8
Jul 07 21:10:34-105418 util-scheduler-8627 DEBUG Checking readiness of task: 407 / 0x4663c60
Jul 07 21:10:34-105732 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:34-105927 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:34-106119 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:34-106315 util-scheduler-8627 DEBUG Running task: 407 / 0x4663c60
Jul 07 21:10:34-106733 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:10:34-106979 util-scheduler-8627 DEBUG Adding task: 409 / 0x4663e08
Jul 07 21:10:34-107244 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:34-107435 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:34-107625 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:34-107814 util-scheduler-8627 DEBUG Running task: 409 / 0x4663e08
Jul 07 21:10:34-108005 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:10:34-108223 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:34-108430 util-scheduler-8627 DEBUG Adding task: 410 / 0x4663c60
Jul 07 21:10:34-108614 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:10:34-108834 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `V8XX' with quota 9608
Jul 07 21:10:34-109024 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 bandwidth changed to 9608 Bps
Jul 07 21:10:34-109289 util-bandwidth-8627 DEBUG Tracker 0x4e5ece8 updated, have 9608 Bps, last update was 508 ms ago
Jul 07 21:10:34-109506 util-scheduler-8627 DEBUG Canceling task: 408 / 0x4e5ece8
Jul 07 21:10:34-109718 util-scheduler-8627 DEBUG Adding task: 411 / 0x4e5ece8
Jul 07 21:10:38-173359 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-173746 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-174283 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:38-174480 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-174677 util-scheduler-8627 DEBUG Running task: 402 / 0x4d63d80
Jul 07 21:10:38-174914 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:38-175162 cadet-tun-8627 DEBUG  kx started 80 s ago
Jul 07 21:10:38-175369 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:38-175570 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:38-175772 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:38-175948 cadet-tun-8627 DEBUG  selected: connection NULL
Jul 07 21:10:38-176473 cadet-tun-8627 WARNING TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 21:10:38-176815 cadet-tun-8627 WARNING TTT  cstate CADET_TUNNEL_SEARCHING, estate CADET_TUNNEL_KEY_SENT
Jul 07 21:10:38-177157 cadet-tun-8627 WARNING TTT  kx_ctx 0x4d7b4d0, rekey_task 0
Jul 07 21:10:38-177524 cadet-tun-8627 WARNING TTT  tq_head (nil), tq_tail (nil)
Jul 07 21:10:38-177859 cadet-tun-8627 WARNING TTT  destroy 0
Jul 07 21:10:38-178185 cadet-tun-8627 WARNING TTT  channels:
Jul 07 21:10:38-178519 cadet-tun-8627 WARNING TTT  connections:
Jul 07 21:10:38-178844 cadet-tun-8627 WARNING TTT DEBUG TUNNEL END
Jul 07 21:10:38-179092 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:38-179318 util-scheduler-8627 DEBUG Adding task: 412 / 0x4d63d80
Jul 07 21:10:38-459919 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-460193 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-460387 util-scheduler-8627 DEBUG Checking readiness of task: 355 / 0x4661f98
Jul 07 21:10:38-460582 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-460776 util-scheduler-8627 DEBUG Running task: 355 / 0x4661f98
Jul 07 21:10:38-461223 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:38-461477 util-scheduler-8627 DEBUG Adding task: 413 / 0x4662140
Jul 07 21:10:38-461743 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-461936 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-462127 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-462319 util-scheduler-8627 DEBUG Running task: 413 / 0x4662140
Jul 07 21:10:38-462510 util-8627 DEBUG Received message of type 67 and size 40 from core service.
Jul 07 21:10:38-462711 core-api-8627 DEBUG Processing message of type 67 and size 40 from core service
Jul 07 21:10:38-462933 core-api-8627 DEBUG Received notification about connection from `V8XX'.
Jul 07 21:10:38-463203 cadet-p2p-8627 INFO CONNECTED GN10 <= V8XX
Jul 07 21:10:38-463487 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:10:38-463705 util-scheduler-8627 DEBUG Adding task: 414 / 0x4d50e20
Jul 07 21:10:38-463930 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:38-464109 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:38-464282 cadet-p2p-8627 DEBUG   added last
Jul 07 21:10:38-466182 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:10:38-466533 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:10:38-466733 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:10:38-466952 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:38-467173 util-scheduler-8627 DEBUG Adding task: 415 / 0x46623e0
Jul 07 21:10:38-468112 cadet-p2p-8627 DEBUG   some path exists
Jul 07 21:10:38-472222 cadet-p2p-8627 DEBUG   path to use:  GN10 V8XX
Jul 07 21:10:38-475350 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:38-475817 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:38-476075 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:38-476431 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:10:38-476844 cadet-con-8627 DEBUG register neighbors for connection MCZ5X28Z (->V8XX)
Jul 07 21:10:38-477165 cadet-8627 DEBUG PATH:
Jul 07 21:10:38-477384 cadet-8627 DEBUG   GN10
Jul 07 21:10:38-477570 cadet-8627 DEBUG   V8XX
Jul 07 21:10:38-477878 cadet-8627 DEBUG END
Jul 07 21:10:38-478208 cadet-con-8627 DEBUG own pos 0
Jul 07 21:10:38-478598 cadet-con-8627 DEBUG putting connection MCZ5X28Z (->V8XX) to next peer 0x4d55378
Jul 07 21:10:38-478967 cadet-con-8627 DEBUG next peer 0x4d55378 V8XX
Jul 07 21:10:38-479357 cadet-con-8627 DEBUG putting connection MCZ5X28Z (->V8XX) to prev peer 0x4d4e270
Jul 07 21:10:38-479728 cadet-con-8627 DEBUG prev peer 0x4d4e270 GN10
Jul 07 21:10:38-479966 cadet-p2p-8627 DEBUG adding connection MCZ5X28Z (->V8XX)
Jul 07 21:10:38-480182 cadet-p2p-8627 DEBUG to peer V8XX
Jul 07 21:10:38-480399 cadet-p2p-8627 DEBUG peer V8XX ok, has 0 connections.
Jul 07 21:10:38-480593 cadet-p2p-8627 DEBUG  now has 1 connections.
Jul 07 21:10:38-480768 cadet-p2p-8627 DEBUG result 1
Jul 07 21:10:38-480989 cadet-p2p-8627 DEBUG adding connection MCZ5X28Z (->V8XX)
Jul 07 21:10:38-481210 cadet-p2p-8627 DEBUG to peer GN10
Jul 07 21:10:38-481415 cadet-p2p-8627 DEBUG peer GN10 ok, has 0 connections.
Jul 07 21:10:38-481602 cadet-p2p-8627 DEBUG  now has 1 connections.
Jul 07 21:10:38-481775 cadet-p2p-8627 DEBUG result 1
Jul 07 21:10:38-482441 cadet-tun-8627 DEBUG add connection MCZ5X28Z (->V8XX)
Jul 07 21:10:38-482653 cadet-tun-8627 DEBUG  to tunnel V8XX
Jul 07 21:10:38-482881 util-scheduler-8627 DEBUG Adding task: 416 / 0x4d63d80
Jul 07 21:10:38-485275 cadet-con-8627 INFO ===> { CONNECTION_CREATE} on connection MCZ5X28Z (->V8XX)  (100 bytes)
Jul 07 21:10:38-486336 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0 (create)
Jul 07 21:10:38-486902 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:38-487123 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:38-487779 cadet-p2p-8627 INFO que { CONNECTION_CREATE} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 100)
Jul 07 21:10:38-487986 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:38-488234 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:38-488525 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:38-488709 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:38-488942 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 21:10:38-489167 core-api-8627 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 21:10:38-489415 util-scheduler-8627 DEBUG Adding task: 417 / 0x4e607e8
Jul 07 21:10:38-489598 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:38-489805 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:38-489982 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:38-490159 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:38-490404 cadet-p2p-8627 DEBUG QQQ  - { CONNECTION_CREATE} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:38-490600 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:10:38-490779 cadet-p2p-8627 DEBUG QQQ    size: 100 bytes
Jul 07 21:10:38-490981 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:38-491899 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_SEARCHING => CADET_TUNNEL_WAITING
Jul 07 21:10:38-492619 cadet-con-8627 DEBUG Connection MCZ5X28Z (->V8XX) state CADET_CONNECTION_NEW -> CADET_CONNECTION_SENT
Jul 07 21:10:38-493011 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:38-493258 util-scheduler-8627 DEBUG Adding task: 418 / 0x4661f98
Jul 07 21:10:38-493540 util-scheduler-8627 DEBUG Checking readiness of task: 418 / 0x4661f98
Jul 07 21:10:38-493742 util-scheduler-8627 DEBUG Checking readiness of task: 414 / 0x4d50e20
Jul 07 21:10:38-493937 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-494129 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-494320 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-494516 util-scheduler-8627 DEBUG Running task: 414 / 0x4d50e20
Jul 07 21:10:38-494704 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:10:38-494883 util-8627 DEBUG process_notify is running
Jul 07 21:10:38-495057 util-8627 DEBUG client_notify is running
Jul 07 21:10:38-495290 util-8627 DEBUG Transmitting message of type 168 and size 30 to statistics service.
Jul 07 21:10:38-495643 util-8627 DEBUG Connection transmitted 30/30 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:10:38-495859 util-scheduler-8627 DEBUG Running task: 417 / 0x4e607e8
Jul 07 21:10:38-496071 util-scheduler-8627 DEBUG Adding task: 419 / 0x4e607e8
Jul 07 21:10:38-496295 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:38-496501 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:38-496704 util-scheduler-8627 DEBUG Adding task: 420 / 0x4661f98
Jul 07 21:10:38-496903 util-scheduler-8627 DEBUG Running task: 416 / 0x4d63d80
Jul 07 21:10:38-497103 util-scheduler-8627 DEBUG Running task: 415 / 0x46623e0
Jul 07 21:10:38-497310 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:38-497503 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:38-497700 util-scheduler-8627 DEBUG Adding task: 421 / 0x4663c60
Jul 07 21:10:38-497942 util-scheduler-8627 DEBUG Checking readiness of task: 421 / 0x4663c60
Jul 07 21:10:38-498135 util-scheduler-8627 DEBUG Checking readiness of task: 420 / 0x4661f98
Jul 07 21:10:38-498327 util-scheduler-8627 DEBUG Checking readiness of task: 418 / 0x4661f98
Jul 07 21:10:38-498517 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-498707 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-498897 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-499089 util-scheduler-8627 DEBUG Running task: 420 / 0x4661f98
Jul 07 21:10:38-499273 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:38-499448 util-8627 DEBUG process_notify is running
Jul 07 21:10:38-499618 util-8627 DEBUG client_notify is running
Jul 07 21:10:38-499796 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:38-499993 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:38-500182 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:38-500532 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:38-500744 util-scheduler-8627 DEBUG Running task: 421 / 0x4663c60
Jul 07 21:10:38-500930 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:38-501105 util-8627 DEBUG process_notify is running
Jul 07 21:10:38-501296 util-8627 DEBUG client_notify is running
Jul 07 21:10:38-501485 transport-api-8627 DEBUG Transmitting `HELLO' request.
Jul 07 21:10:38-501694 transport-api-8627 DEBUG Control transmit of 40 bytes requested
Jul 07 21:10:38-501913 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:38-502113 util-scheduler-8627 DEBUG Adding task: 422 / 0x46623e0
Jul 07 21:10:38-502314 transport-api-8627 DEBUG Added 491 bytes of control message at 0
Jul 07 21:10:38-502535 util-scheduler-8627 DEBUG Canceling task: 422 / 0x46623e0
Jul 07 21:10:38-502758 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:10:38-502994 util-scheduler-8627 DEBUG Adding task: 423 / 0x46623e0
Jul 07 21:10:38-503177 transport-api-8627 DEBUG Transmitting 491 bytes to transport service
Jul 07 21:10:38-503371 util-8627 DEBUG Transmitting message of type 17 and size 491 to transport service.
Jul 07 21:10:38-503813 util-8627 DEBUG Connection transmitted 491/491 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:38-504070 util-scheduler-8627 DEBUG Checking readiness of task: 418 / 0x4661f98
Jul 07 21:10:38-504264 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-504455 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-504646 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-504839 util-scheduler-8627 DEBUG Running task: 418 / 0x4661f98
Jul 07 21:10:38-505282 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:38-505517 util-scheduler-8627 DEBUG Adding task: 424 / 0x4662140
Jul 07 21:10:38-505726 util-scheduler-8627 DEBUG Running task: 423 / 0x46623e0
Jul 07 21:10:38-505908 transport-api-8627 DEBUG Calling notify_transmit_ready
Jul 07 21:10:38-506099 util-8627 DEBUG Scheduling transmission (0x4663c60).
Jul 07 21:10:38-506297 util-scheduler-8627 DEBUG Adding task: 425 / 0x4663c60
Jul 07 21:10:38-506532 util-scheduler-8627 DEBUG Checking readiness of task: 425 / 0x4663c60
Jul 07 21:10:38-506723 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-506913 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-507103 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-507294 util-scheduler-8627 DEBUG Running task: 425 / 0x4663c60
Jul 07 21:10:38-507479 util-8627 DEBUG transmit_ready running (0x4663c60).
Jul 07 21:10:38-507655 util-8627 DEBUG process_notify is running
Jul 07 21:10:38-507824 util-8627 DEBUG client_notify is running
Jul 07 21:10:38-508030 transport-api-8627 DEBUG Transmitting `REQUEST_CONNECT' request with respect to `V8XX'.
Jul 07 21:10:38-508230 transport-api-8627 DEBUG Added 40 bytes of control message at 0
Jul 07 21:10:38-508422 transport-api-8627 DEBUG Transmitting 40 bytes to transport service
Jul 07 21:10:38-508615 util-8627 DEBUG Transmitting message of type 374 and size 40 to transport service.
Jul 07 21:10:38-508956 util-8627 DEBUG Connection transmitted 40/40 bytes to `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)
Jul 07 21:10:38-509169 util-scheduler-8627 DEBUG Running task: 424 / 0x4662140
Jul 07 21:10:38-509382 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:38-509582 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:38-509799 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:38-509998 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:38-510196 util-scheduler-8627 DEBUG Adding task: 426 / 0x4661f98
Jul 07 21:10:38-510380 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:38-510580 util-scheduler-8627 DEBUG Adding task: 427 / 0x4661f98
Jul 07 21:10:38-510820 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:38-511012 util-scheduler-8627 DEBUG Checking readiness of task: 426 / 0x4661f98
Jul 07 21:10:38-511214 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:38-511404 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:38-511594 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:38-511785 util-scheduler-8627 DEBUG Running task: 426 / 0x4661f98
Jul 07 21:10:38-511981 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:38-512181 util-8627 DEBUG process_notify is running
Jul 07 21:10:38-512351 util-8627 DEBUG client_notify is running
Jul 07 21:10:38-512534 util-scheduler-8627 DEBUG Canceling task: 419 / 0x4e607e8
Jul 07 21:10:38-512759 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 21:10:38-512976 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:38-513231 cadet-p2p-8627 DEBUG Checking 0x4e62bc0 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:38-513471 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:38-513650 cadet-p2p-8627 DEBUG   size 100 ok
Jul 07 21:10:38-514594 cadet-p2p-8627 DEBUG   path create
Jul 07 21:10:38-516247 cadet-p2p-8627 DEBUG Sending CONNECTION CREATE...
Jul 07 21:10:38-519137 cadet-p2p-8627 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 21:10:38-519575 cadet-p2p-8627 INFO snd { CONNECTION_CREATE} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 100)
Jul 07 21:10:38-519776 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:38-519962 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:38-520289 cadet-con-8627 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 21:10:38-520478 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:38-521064 util-scheduler-8627 DEBUG Adding task: 428 / 0x4e61600
Jul 07 21:10:38-521334 cadet-con-8627 DEBUG next keepalive in 1 s
Jul 07 21:10:38-521510 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:38-521722 cadet-p2p-8627 DEBUG   return 100
Jul 07 21:10:38-521923 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:38-522099 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:38-522274 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:38-522474 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:38-522680 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 21:10:38-522866 core-api-8627 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 21:10:38-523045 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:38-523237 util-8627 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 21:10:38-523476 util-8627 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:39-522220 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:39-522599 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:39-522794 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:39-522985 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:39-523179 util-scheduler-8627 DEBUG Running task: 428 / 0x4e61600
Jul 07 21:10:39-523943 cadet-con-8627 DEBUG FWD keepalive for MCZ5X28Z (->V8XX)
Jul 07 21:10:39-525001 cadet-con-8627 DEBUG sending connection recreate
Jul 07 21:10:39-526070 cadet-con-8627 INFO ===> { CONNECTION_CREATE} on connection MCZ5X28Z (->V8XX)  (100 bytes)
Jul 07 21:10:39-526436 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0 (create)
Jul 07 21:10:39-526678 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:39-526903 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:39-527216 cadet-p2p-8627 INFO que { CONNECTION_CREATE} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 100)
Jul 07 21:10:39-527415 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:39-527651 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:39-527835 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:39-528011 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:39-528219 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 21:10:39-528435 core-api-8627 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 21:10:39-528660 util-scheduler-8627 DEBUG Adding task: 429 / 0x4e607e8
Jul 07 21:10:39-528840 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:39-529045 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:39-529272 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:39-529450 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:39-529690 cadet-p2p-8627 DEBUG QQQ  - { CONNECTION_CREATE} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:39-529873 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:10:39-530048 cadet-p2p-8627 DEBUG QQQ    size: 100 bytes
Jul 07 21:10:39-530248 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:39-530969 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:39-531168 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:39-531360 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:39-531550 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:39-531742 util-scheduler-8627 DEBUG Running task: 429 / 0x4e607e8
Jul 07 21:10:39-531953 util-scheduler-8627 DEBUG Adding task: 430 / 0x4e607e8
Jul 07 21:10:39-532175 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:39-532378 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:39-532586 util-scheduler-8627 DEBUG Adding task: 431 / 0x4661f98
Jul 07 21:10:39-532825 util-scheduler-8627 DEBUG Checking readiness of task: 431 / 0x4661f98
Jul 07 21:10:39-533016 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:39-533227 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:39-533418 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:39-533608 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:39-533799 util-scheduler-8627 DEBUG Running task: 431 / 0x4661f98
Jul 07 21:10:39-533984 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:39-534161 util-8627 DEBUG process_notify is running
Jul 07 21:10:39-534333 util-8627 DEBUG client_notify is running
Jul 07 21:10:39-534512 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:39-534710 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:39-534900 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:39-535227 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:40-420482 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:40-420814 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:40-421008 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:40-421222 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:40-421418 util-scheduler-8627 DEBUG Running task: 411 / 0x4e5ece8
Jul 07 21:10:41-170285 util-scheduler-8627 DEBUG Checking readiness of task: 427 / 0x4661f98
Jul 07 21:10:41-170567 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-170762 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-170959 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-171162 util-scheduler-8627 DEBUG Running task: 427 / 0x4661f98
Jul 07 21:10:41-171584 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:41-171840 util-scheduler-8627 DEBUG Adding task: 432 / 0x4662140
Jul 07 21:10:41-172105 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-172296 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-172488 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-172678 util-scheduler-8627 DEBUG Running task: 432 / 0x4662140
Jul 07 21:10:41-172869 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:41-173068 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:41-173342 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:41-173576 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:41-173783 util-scheduler-8627 DEBUG Adding task: 433 / 0x4661f98
Jul 07 21:10:41-173970 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:41-174176 util-scheduler-8627 DEBUG Adding task: 434 / 0x4661f98
Jul 07 21:10:41-174418 util-scheduler-8627 DEBUG Checking readiness of task: 434 / 0x4661f98
Jul 07 21:10:41-174609 util-scheduler-8627 DEBUG Checking readiness of task: 433 / 0x4661f98
Jul 07 21:10:41-174813 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-175002 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-175191 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-175382 util-scheduler-8627 DEBUG Running task: 433 / 0x4661f98
Jul 07 21:10:41-175567 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:41-175744 util-8627 DEBUG process_notify is running
Jul 07 21:10:41-175915 util-8627 DEBUG client_notify is running
Jul 07 21:10:41-176101 util-scheduler-8627 DEBUG Canceling task: 430 / 0x4e607e8
Jul 07 21:10:41-176325 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 100 bytes.
Jul 07 21:10:41-176545 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:41-176784 cadet-p2p-8627 DEBUG Checking 0x4e66338 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:41-177018 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:41-177218 cadet-p2p-8627 DEBUG   size 100 ok
Jul 07 21:10:41-177563 cadet-p2p-8627 DEBUG   path create
Jul 07 21:10:41-177845 cadet-p2p-8627 DEBUG Sending CONNECTION CREATE...
Jul 07 21:10:41-178121 cadet-p2p-8627 DEBUG CONNECTION CREATE (100 bytes long) sent!
Jul 07 21:10:41-178396 cadet-p2p-8627 INFO snd { CONNECTION_CREATE} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 100)
Jul 07 21:10:41-178592 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:41-178772 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:41-178960 cadet-con-8627 DEBUG  sent FWD { CONNECTION_CREATE}
Jul 07 21:10:41-179140 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:41-179370 util-scheduler-8627 DEBUG Adding task: 435 / 0x4e61600
Jul 07 21:10:41-179609 cadet-con-8627 DEBUG next keepalive in 2 s
Jul 07 21:10:41-179780 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:41-179962 cadet-p2p-8627 DEBUG   return 100
Jul 07 21:10:41-180166 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:41-180339 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:41-180513 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:41-180711 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:41-180916 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 100 bytes.
Jul 07 21:10:41-181101 core-api-8627 DEBUG Produced SEND message to core with 100 bytes payload
Jul 07 21:10:41-181304 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:41-181496 util-8627 DEBUG Transmitting message of type 76 and size 156 to core service.
Jul 07 21:10:41-181737 util-8627 DEBUG Connection transmitted 156/156 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:41-181993 util-scheduler-8627 DEBUG Checking readiness of task: 434 / 0x4661f98
Jul 07 21:10:41-182191 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-182382 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-182572 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-182764 util-scheduler-8627 DEBUG Running task: 434 / 0x4661f98
Jul 07 21:10:41-183169 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:41-183403 util-scheduler-8627 DEBUG Adding task: 436 / 0x4662140
Jul 07 21:10:41-183652 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-183844 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-184057 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-184248 util-scheduler-8627 DEBUG Running task: 436 / 0x4662140
Jul 07 21:10:41-184439 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:10:41-184636 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:10:41-184857 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:10:41-185110 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection MCZ5X28Z from V8XX
Jul 07 21:10:41-185350 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:10:41-185589 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:41-185799 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:41-186757 cadet-con-8627 DEBUG   SYNACK
Jul 07 21:10:41-187386 cadet-con-8627 DEBUG Connection MCZ5X28Z (->V8XX) state CADET_CONNECTION_SENT -> CADET_CONNECTION_ACK
Jul 07 21:10:41-187836 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:41-188696 util-scheduler-8627 DEBUG Adding task: 437 / 0x4e61600
Jul 07 21:10:41-188957 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:41-189140 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:41-190154 cadet-con-8627 DEBUG   Connection (SYN)ACK for us!
Jul 07 21:10:41-190661 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:41-190870 util-scheduler-8627 DEBUG Canceling task: 435 / 0x4e61600
Jul 07 21:10:41-191105 util-scheduler-8627 DEBUG Adding task: 438 / 0x4e61600
Jul 07 21:10:41-191341 cadet-con-8627 DEBUG next keepalive in 4 s
Jul 07 21:10:41-191879 cadet-con-8627 DEBUG Connection MCZ5X28Z (->V8XX) state CADET_CONNECTION_ACK -> CADET_CONNECTION_READY
Jul 07 21:10:41-192452 cadet-con-8627 INFO ===> {           BCK ACK} on connection MCZ5X28Z (->V8XX)
Jul 07 21:10:41-192700 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:41-192912 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:41-193239 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 36)
Jul 07 21:10:41-193441 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:41-193668 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:41-193853 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:41-194030 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:41-194239 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:10:41-194455 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:10:41-194671 util-scheduler-8627 DEBUG Adding task: 439 / 0x4e607e8
Jul 07 21:10:41-194852 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:41-195057 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:41-195238 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:41-195416 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:41-195659 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:41-195845 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:10:41-196021 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:10:41-196222 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:41-196908 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_WAITING => CADET_TUNNEL_READY
Jul 07 21:10:41-197647 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:41-197886 util-scheduler-8627 DEBUG Adding task: 440 / 0x4661f98
Jul 07 21:10:41-198173 util-scheduler-8627 DEBUG Checking readiness of task: 440 / 0x4661f98
Jul 07 21:10:41-198372 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-198565 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-198756 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-198950 util-scheduler-8627 DEBUG Running task: 439 / 0x4e607e8
Jul 07 21:10:41-199167 util-scheduler-8627 DEBUG Adding task: 441 / 0x4e607e8
Jul 07 21:10:41-199426 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:41-199654 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:41-199860 util-scheduler-8627 DEBUG Adding task: 442 / 0x4661f98
Jul 07 21:10:41-200104 util-scheduler-8627 DEBUG Checking readiness of task: 442 / 0x4661f98
Jul 07 21:10:41-200298 util-scheduler-8627 DEBUG Checking readiness of task: 440 / 0x4661f98
Jul 07 21:10:41-200488 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-200678 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-200869 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-201061 util-scheduler-8627 DEBUG Running task: 442 / 0x4661f98
Jul 07 21:10:41-201299 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:41-201479 util-8627 DEBUG process_notify is running
Jul 07 21:10:41-201668 util-8627 DEBUG client_notify is running
Jul 07 21:10:41-201848 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:41-202047 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:41-202239 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:41-202600 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:41-300030 util-scheduler-8627 DEBUG Checking readiness of task: 440 / 0x4661f98
Jul 07 21:10:41-300347 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-300542 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-300735 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-300932 util-scheduler-8627 DEBUG Running task: 440 / 0x4661f98
Jul 07 21:10:41-301378 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:41-301628 util-scheduler-8627 DEBUG Adding task: 443 / 0x4662140
Jul 07 21:10:41-301899 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-302091 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-302281 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-302471 util-scheduler-8627 DEBUG Running task: 443 / 0x4662140
Jul 07 21:10:41-302661 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:41-302859 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:41-303083 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:41-303288 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:41-303494 util-scheduler-8627 DEBUG Adding task: 444 / 0x4661f98
Jul 07 21:10:41-303680 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:41-303885 util-scheduler-8627 DEBUG Adding task: 445 / 0x4661f98
Jul 07 21:10:41-304124 util-scheduler-8627 DEBUG Checking readiness of task: 445 / 0x4661f98
Jul 07 21:10:41-304315 util-scheduler-8627 DEBUG Checking readiness of task: 444 / 0x4661f98
Jul 07 21:10:41-304506 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:41-304695 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:41-304884 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:41-305075 util-scheduler-8627 DEBUG Running task: 444 / 0x4661f98
Jul 07 21:10:41-305285 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:41-305464 util-8627 DEBUG process_notify is running
Jul 07 21:10:41-305636 util-8627 DEBUG client_notify is running
Jul 07 21:10:41-305822 util-scheduler-8627 DEBUG Canceling task: 441 / 0x4e607e8
Jul 07 21:10:41-306046 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:10:41-306267 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:41-306534 cadet-p2p-8627 DEBUG Checking 0x4e695c0 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:41-306768 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:41-306964 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:10:41-307135 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:10:41-307708 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:10:41-307889 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:10:41-308152 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 36)
Jul 07 21:10:41-308346 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:41-308527 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:41-308715 cadet-con-8627 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 21:10:41-308896 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:41-309164 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:41-309379 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:10:41-309581 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:41-309756 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:41-309931 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:41-310130 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:41-310336 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:10:41-310520 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:10:41-310699 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:41-310891 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:10:41-312308 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:43-181358 util-scheduler-8627 DEBUG Checking readiness of task: 445 / 0x4661f98
Jul 07 21:10:43-181742 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:43-182952 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:43-183191 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:43-183417 util-scheduler-8627 DEBUG Running task: 412 / 0x4d63d80
Jul 07 21:10:43-183729 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:43-184012 cadet-tun-8627 DEBUG  kx started 85 s ago
Jul 07 21:10:43-184272 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:43-184476 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:43-184679 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:43-184915 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:10:43-185315 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:43-185545 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:10:43-185842 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:10:43-186274 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:10:43-186528 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:43-186762 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:43-187095 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:10:43-187296 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:43-187519 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:43-187703 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:43-187878 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:43-188083 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:43-188298 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:43-188520 util-scheduler-8627 DEBUG Adding task: 446 / 0x4e607e8
Jul 07 21:10:43-188701 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:43-188904 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:43-189079 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:43-189276 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:43-189542 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:43-189738 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:43-189916 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:43-190114 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:43-190357 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:43-190557 util-scheduler-8627 DEBUG Adding task: 447 / 0x4d63d80
Jul 07 21:10:43-190837 util-scheduler-8627 DEBUG Checking readiness of task: 445 / 0x4661f98
Jul 07 21:10:43-191030 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:43-191220 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:43-191408 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:43-191599 util-scheduler-8627 DEBUG Running task: 446 / 0x4e607e8
Jul 07 21:10:43-191806 util-scheduler-8627 DEBUG Adding task: 448 / 0x4e607e8
Jul 07 21:10:43-192027 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:43-192230 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:43-192439 util-scheduler-8627 DEBUG Adding task: 449 / 0x4661f98
Jul 07 21:10:43-192679 util-scheduler-8627 DEBUG Checking readiness of task: 449 / 0x4661f98
Jul 07 21:10:43-192871 util-scheduler-8627 DEBUG Checking readiness of task: 445 / 0x4661f98
Jul 07 21:10:43-193074 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:43-193293 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:43-193483 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:43-193675 util-scheduler-8627 DEBUG Running task: 449 / 0x4661f98
Jul 07 21:10:43-193860 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:43-194038 util-8627 DEBUG process_notify is running
Jul 07 21:10:43-194210 util-8627 DEBUG client_notify is running
Jul 07 21:10:43-194389 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:43-194584 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:43-194775 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:43-195043 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:44-628190 util-scheduler-8627 DEBUG Checking readiness of task: 445 / 0x4661f98
Jul 07 21:10:44-628575 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:44-628774 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:44-628970 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:44-629210 util-scheduler-8627 DEBUG Running task: 445 / 0x4661f98
Jul 07 21:10:44-629639 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:44-629898 util-scheduler-8627 DEBUG Adding task: 450 / 0x4662140
Jul 07 21:10:44-630183 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:44-630375 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:44-630564 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:44-630754 util-scheduler-8627 DEBUG Running task: 450 / 0x4662140
Jul 07 21:10:44-630944 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:44-631144 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:44-631376 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:44-631583 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:44-631788 util-scheduler-8627 DEBUG Adding task: 451 / 0x4661f98
Jul 07 21:10:44-631974 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:44-632180 util-scheduler-8627 DEBUG Adding task: 452 / 0x4661f98
Jul 07 21:10:44-632421 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:44-632651 util-scheduler-8627 DEBUG Checking readiness of task: 451 / 0x4661f98
Jul 07 21:10:44-632846 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:44-633034 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:44-633246 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:44-633440 util-scheduler-8627 DEBUG Running task: 451 / 0x4661f98
Jul 07 21:10:44-633624 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:44-633804 util-8627 DEBUG process_notify is running
Jul 07 21:10:44-635231 util-8627 DEBUG client_notify is running
Jul 07 21:10:44-635428 util-scheduler-8627 DEBUG Canceling task: 448 / 0x4e607e8
Jul 07 21:10:44-635662 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:44-635882 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:44-636121 cadet-p2p-8627 DEBUG Checking 0x4e6c258 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:44-636356 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:44-636532 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:44-636724 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:44-637014 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:10:44-637230 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:44-637412 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:44-637600 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:10:44-637789 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:44-637967 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:44-638158 util-scheduler-8627 DEBUG Canceling task: 438 / 0x4e61600
Jul 07 21:10:44-638370 util-scheduler-8627 DEBUG Adding task: 453 / 0x4e61600
Jul 07 21:10:44-638620 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:44-638790 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:44-638971 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:44-639190 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:44-639364 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:44-639537 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:44-639735 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:44-639940 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:44-640122 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:44-640301 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:44-640491 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:44-640742 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:45-957689 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:45-958047 util-scheduler-8627 DEBUG Checking readiness of task: 410 / 0x4663c60
Jul 07 21:10:45-958253 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:45-958447 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:45-958644 util-scheduler-8627 DEBUG Running task: 410 / 0x4663c60
Jul 07 21:10:45-959069 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-transport.sock' (0x4663c60)!
Jul 07 21:10:45-959324 util-scheduler-8627 DEBUG Adding task: 454 / 0x4663e08
Jul 07 21:10:45-959597 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:45-959788 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:45-959978 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:45-960168 util-scheduler-8627 DEBUG Running task: 454 / 0x4663e08
Jul 07 21:10:45-960361 util-8627 DEBUG Received message of type 366 and size 40 from transport service.
Jul 07 21:10:45-960557 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:45-960801 util-scheduler-8627 DEBUG Adding task: 455 / 0x4663c60
Jul 07 21:10:45-960988 transport-api-8627 DEBUG Receiving `SET_QUOTA' message.
Jul 07 21:10:45-961240 transport-api-8627 DEBUG Receiving `SET_QUOTA' message for `P00P' with quota 8099
Jul 07 21:10:45-961435 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 bandwidth changed to 8099 Bps
Jul 07 21:10:45-961910 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 updated, have 8117 Bps, last update was 5 m ago
Jul 07 21:10:45-962440 util-bandwidth-8627 DEBUG Tracker 0x4d54cd0 updated, have 8099 Bps, last update was 770 µs ago
Jul 07 21:10:45-962770 util-scheduler-8627 DEBUG Adding task: 456 / 0x4d54cd0
Jul 07 21:10:45-963015 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:45-963208 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:45-963398 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:45-963588 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:45-963778 util-scheduler-8627 DEBUG Running task: 456 / 0x4d54cd0
Jul 07 21:10:48-192945 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:48-193361 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:48-196538 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:48-196735 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:48-196932 util-scheduler-8627 DEBUG Running task: 447 / 0x4d63d80
Jul 07 21:10:48-197172 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:48-197449 cadet-tun-8627 DEBUG  kx started 90 s ago
Jul 07 21:10:48-197657 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:48-197858 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:48-198060 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:48-198294 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:10:48-198498 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:48-198721 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:10:48-199027 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:10:48-199224 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:10:48-199462 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:48-199670 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:48-199988 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:10:48-200188 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:48-200412 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:48-200595 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:48-200770 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:48-200975 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:48-201213 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:48-201440 util-scheduler-8627 DEBUG Adding task: 457 / 0x4e607e8
Jul 07 21:10:48-201620 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:48-201824 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:48-201999 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:48-202173 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:48-202409 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:48-202604 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:48-202781 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:48-202979 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:48-203220 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:48-203418 util-scheduler-8627 DEBUG Adding task: 458 / 0x4d63d80
Jul 07 21:10:48-203675 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:48-203865 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:48-204095 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:48-204285 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:48-204476 util-scheduler-8627 DEBUG Running task: 457 / 0x4e607e8
Jul 07 21:10:48-204684 util-scheduler-8627 DEBUG Adding task: 459 / 0x4e607e8
Jul 07 21:10:48-204964 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:48-205170 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:48-205406 util-scheduler-8627 DEBUG Adding task: 460 / 0x4661f98
Jul 07 21:10:48-205648 util-scheduler-8627 DEBUG Checking readiness of task: 460 / 0x4661f98
Jul 07 21:10:48-205840 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:48-206029 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:48-206218 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:48-206407 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:48-206599 util-scheduler-8627 DEBUG Running task: 460 / 0x4661f98
Jul 07 21:10:48-206784 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:48-206961 util-8627 DEBUG process_notify is running
Jul 07 21:10:48-207134 util-8627 DEBUG client_notify is running
Jul 07 21:10:48-207316 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:48-207511 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:48-207702 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:48-207961 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:49-507953 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:49-508319 util-scheduler-8627 DEBUG Checking readiness of task: 452 / 0x4661f98
Jul 07 21:10:49-508518 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:49-508709 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:49-508906 util-scheduler-8627 DEBUG Running task: 452 / 0x4661f98
Jul 07 21:10:49-509359 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:49-509626 util-scheduler-8627 DEBUG Adding task: 461 / 0x4662140
Jul 07 21:10:49-509902 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:49-510094 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:49-510284 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:49-510475 util-scheduler-8627 DEBUG Running task: 461 / 0x4662140
Jul 07 21:10:49-510667 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:49-510867 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:49-511097 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:49-511304 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:49-511511 util-scheduler-8627 DEBUG Adding task: 462 / 0x4661f98
Jul 07 21:10:49-511697 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:49-511903 util-scheduler-8627 DEBUG Adding task: 463 / 0x4661f98
Jul 07 21:10:49-512144 util-scheduler-8627 DEBUG Checking readiness of task: 463 / 0x4661f98
Jul 07 21:10:49-512335 util-scheduler-8627 DEBUG Checking readiness of task: 462 / 0x4661f98
Jul 07 21:10:49-512525 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:49-512715 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:49-512903 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:49-513095 util-scheduler-8627 DEBUG Running task: 462 / 0x4661f98
Jul 07 21:10:49-513303 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:49-513512 util-8627 DEBUG process_notify is running
Jul 07 21:10:49-513686 util-8627 DEBUG client_notify is running
Jul 07 21:10:49-513873 util-scheduler-8627 DEBUG Canceling task: 459 / 0x4e607e8
Jul 07 21:10:49-514097 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:49-514317 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:49-514558 cadet-p2p-8627 DEBUG Checking 0x4e6f710 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:49-514814 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:49-514992 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:49-515182 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:49-515468 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:10:49-515663 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:49-515843 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:49-516031 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:10:49-516222 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:49-516401 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:49-516587 util-scheduler-8627 DEBUG Canceling task: 453 / 0x4e61600
Jul 07 21:10:49-516797 util-scheduler-8627 DEBUG Adding task: 464 / 0x4e61600
Jul 07 21:10:49-517047 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:49-517236 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:49-517419 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:49-517618 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:49-517793 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:49-517966 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:49-518164 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:49-518369 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:49-518552 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:49-518730 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:49-518921 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:49-519172 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:53-207252 util-scheduler-8627 DEBUG Checking readiness of task: 463 / 0x4661f98
Jul 07 21:10:53-207626 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:53-208204 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:53-208400 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:53-208650 util-scheduler-8627 DEBUG Running task: 458 / 0x4d63d80
Jul 07 21:10:53-208923 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:53-209186 cadet-tun-8627 DEBUG  kx started 95 s ago
Jul 07 21:10:53-209418 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:53-209620 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:53-209822 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:53-210056 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:10:53-210236 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:53-210457 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:10:53-210747 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:10:53-210944 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:10:53-211201 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:53-211410 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:53-211727 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:10:53-211927 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:53-212153 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:53-212338 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:53-212540 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:53-212748 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:53-212963 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:53-213186 util-scheduler-8627 DEBUG Adding task: 465 / 0x4e607e8
Jul 07 21:10:53-213386 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:53-213590 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:53-213765 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:53-213938 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:53-214176 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:53-214371 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:53-214549 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:53-214747 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:53-214989 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:53-215186 util-scheduler-8627 DEBUG Adding task: 466 / 0x4d63d80
Jul 07 21:10:53-215442 util-scheduler-8627 DEBUG Checking readiness of task: 463 / 0x4661f98
Jul 07 21:10:53-215633 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:53-215823 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:53-216011 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:53-216202 util-scheduler-8627 DEBUG Running task: 465 / 0x4e607e8
Jul 07 21:10:53-216409 util-scheduler-8627 DEBUG Adding task: 467 / 0x4e607e8
Jul 07 21:10:53-216630 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:53-216833 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:53-217041 util-scheduler-8627 DEBUG Adding task: 468 / 0x4661f98
Jul 07 21:10:53-217299 util-scheduler-8627 DEBUG Checking readiness of task: 468 / 0x4661f98
Jul 07 21:10:53-217495 util-scheduler-8627 DEBUG Checking readiness of task: 463 / 0x4661f98
Jul 07 21:10:53-217685 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:53-217874 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:53-218064 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:53-218254 util-scheduler-8627 DEBUG Running task: 468 / 0x4661f98
Jul 07 21:10:53-218449 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:53-218627 util-8627 DEBUG process_notify is running
Jul 07 21:10:53-218799 util-8627 DEBUG client_notify is running
Jul 07 21:10:53-218977 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:53-219173 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:53-219363 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:53-219616 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:54-426726 util-scheduler-8627 DEBUG Checking readiness of task: 463 / 0x4661f98
Jul 07 21:10:54-427016 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:54-427211 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:54-427403 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:54-427596 util-scheduler-8627 DEBUG Running task: 463 / 0x4661f98
Jul 07 21:10:54-428015 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:54-428268 util-scheduler-8627 DEBUG Adding task: 469 / 0x4662140
Jul 07 21:10:54-428529 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:54-428721 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:54-428911 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:54-429101 util-scheduler-8627 DEBUG Running task: 469 / 0x4662140
Jul 07 21:10:54-429322 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:54-429547 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:54-429772 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:54-429974 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:54-430175 util-scheduler-8627 DEBUG Adding task: 470 / 0x4661f98
Jul 07 21:10:54-430360 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:54-430565 util-scheduler-8627 DEBUG Adding task: 471 / 0x4661f98
Jul 07 21:10:54-430805 util-scheduler-8627 DEBUG Checking readiness of task: 471 / 0x4661f98
Jul 07 21:10:54-430996 util-scheduler-8627 DEBUG Checking readiness of task: 470 / 0x4661f98
Jul 07 21:10:54-431186 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:54-431374 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:54-431563 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:54-431753 util-scheduler-8627 DEBUG Running task: 470 / 0x4661f98
Jul 07 21:10:54-431937 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:54-432113 util-8627 DEBUG process_notify is running
Jul 07 21:10:54-432284 util-8627 DEBUG client_notify is running
Jul 07 21:10:54-432469 util-scheduler-8627 DEBUG Canceling task: 467 / 0x4e607e8
Jul 07 21:10:54-432691 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:10:54-432909 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:54-433144 cadet-p2p-8627 DEBUG Checking 0x4e723e8 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:54-433402 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:54-433580 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:10:54-433767 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:10:54-434050 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:10:54-434243 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:54-434421 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:54-434608 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:10:54-434796 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:54-434974 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:10:54-435158 util-scheduler-8627 DEBUG Canceling task: 464 / 0x4e61600
Jul 07 21:10:54-435391 util-scheduler-8627 DEBUG Adding task: 472 / 0x4e61600
Jul 07 21:10:54-435638 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:10:54-435808 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:54-435994 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:10:54-436193 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:54-436367 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:54-436540 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:54-436739 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:54-436943 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:10:54-437126 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:10:54-437329 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:54-437531 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:10:54-437777 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:56-513084 util-scheduler-8627 DEBUG Checking readiness of task: 471 / 0x4661f98
Jul 07 21:10:56-513466 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:56-513663 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:56-513855 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:56-514052 util-scheduler-8627 DEBUG Running task: 471 / 0x4661f98
Jul 07 21:10:56-514471 util-8627 DEBUG receive_ready read 72/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:56-514753 util-scheduler-8627 DEBUG Adding task: 473 / 0x4662140
Jul 07 21:10:56-515026 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:56-515217 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:56-515407 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:56-515598 util-scheduler-8627 DEBUG Running task: 473 / 0x4662140
Jul 07 21:10:56-515790 util-8627 DEBUG Received message of type 70 and size 72 from core service.
Jul 07 21:10:56-515990 core-api-8627 DEBUG Processing message of type 70 and size 72 from core service
Jul 07 21:10:56-516217 core-api-8627 DEBUG Received message of type 257 and size 36 from peer `V8XX'
Jul 07 21:10:56-516480 cadet-con-8627 INFO <-- {    CONNECTION_ACK} on connection MCZ5X28Z from V8XX
Jul 07 21:10:56-516696 cadet-con-8627 DEBUG   via peer V8XX
Jul 07 21:10:56-516937 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:56-517145 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:56-517533 cadet-con-8627 DEBUG   SYNACK
Jul 07 21:10:56-517966 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:10:56-518331 util-scheduler-8627 DEBUG Canceling task: 437 / 0x4e61600
Jul 07 21:10:56-519083 util-scheduler-8627 DEBUG Adding task: 474 / 0x4e61600
Jul 07 21:10:56-519343 cadet-p2p-8627 DEBUG adding path [2] to peer V8XX
Jul 07 21:10:56-519525 cadet-p2p-8627 DEBUG  final length: 2
Jul 07 21:10:56-519810 cadet-con-8627 DEBUG   Connection (SYN)ACK for us!
Jul 07 21:10:56-520330 cadet-con-8627 DEBUG Connection MCZ5X28Z (->V8XX) state CADET_CONNECTION_READY -> CADET_CONNECTION_READY
Jul 07 21:10:56-520588 cadet-con-8627 INFO ===> {           BCK ACK} on connection MCZ5X28Z (->V8XX)
Jul 07 21:10:56-520826 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:56-521034 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:56-521350 cadet-p2p-8627 INFO que {    CONNECTION_ACK} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 36)
Jul 07 21:10:56-521549 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:56-521774 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:56-521957 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:56-522133 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:56-522338 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 36 bytes
Jul 07 21:10:56-522552 core-api-8627 DEBUG Asking core for transmission of 36 bytes to `V8XX'
Jul 07 21:10:56-522767 util-scheduler-8627 DEBUG Adding task: 475 / 0x4e607e8
Jul 07 21:10:56-522946 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:56-523168 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:56-523358 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:56-523533 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:56-523771 cadet-p2p-8627 DEBUG QQQ  - {    CONNECTION_ACK} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:56-523954 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:10:56-524130 cadet-p2p-8627 DEBUG QQQ    size: 36 bytes
Jul 07 21:10:56-524327 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:56-524509 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:56-524720 util-scheduler-8627 DEBUG Adding task: 476 / 0x4661f98
Jul 07 21:10:56-524968 util-scheduler-8627 DEBUG Checking readiness of task: 476 / 0x4661f98
Jul 07 21:10:56-525160 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:56-525370 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:56-525560 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:56-525751 util-scheduler-8627 DEBUG Running task: 475 / 0x4e607e8
Jul 07 21:10:56-525957 util-scheduler-8627 DEBUG Adding task: 477 / 0x4e607e8
Jul 07 21:10:56-526179 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:56-526380 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:56-526581 util-scheduler-8627 DEBUG Adding task: 478 / 0x4661f98
Jul 07 21:10:56-526839 util-scheduler-8627 DEBUG Checking readiness of task: 478 / 0x4661f98
Jul 07 21:10:56-527031 util-scheduler-8627 DEBUG Checking readiness of task: 476 / 0x4661f98
Jul 07 21:10:56-527221 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:56-527410 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:56-527609 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:56-527801 util-scheduler-8627 DEBUG Running task: 478 / 0x4661f98
Jul 07 21:10:56-527986 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:56-528163 util-8627 DEBUG process_notify is running
Jul 07 21:10:56-528338 util-8627 DEBUG client_notify is running
Jul 07 21:10:56-528517 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:56-528713 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:56-528902 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:56-529154 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:57-879301 util-scheduler-8627 DEBUG Checking readiness of task: 476 / 0x4661f98
Jul 07 21:10:57-879685 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:57-879882 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:57-880075 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:57-880271 util-scheduler-8627 DEBUG Running task: 476 / 0x4661f98
Jul 07 21:10:57-880699 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:10:57-880958 util-scheduler-8627 DEBUG Adding task: 479 / 0x4662140
Jul 07 21:10:57-881261 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:57-881456 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:57-881648 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:57-881838 util-scheduler-8627 DEBUG Running task: 479 / 0x4662140
Jul 07 21:10:57-882029 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:10:57-882229 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:10:57-882461 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:10:57-882667 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:57-882875 util-scheduler-8627 DEBUG Adding task: 480 / 0x4661f98
Jul 07 21:10:57-883061 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:10:57-883268 util-scheduler-8627 DEBUG Adding task: 481 / 0x4661f98
Jul 07 21:10:57-883509 util-scheduler-8627 DEBUG Checking readiness of task: 481 / 0x4661f98
Jul 07 21:10:57-883700 util-scheduler-8627 DEBUG Checking readiness of task: 480 / 0x4661f98
Jul 07 21:10:57-883892 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:57-884081 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:57-884271 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:57-884463 util-scheduler-8627 DEBUG Running task: 480 / 0x4661f98
Jul 07 21:10:57-884648 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:57-884825 util-8627 DEBUG process_notify is running
Jul 07 21:10:57-884997 util-8627 DEBUG client_notify is running
Jul 07 21:10:57-885186 util-scheduler-8627 DEBUG Canceling task: 477 / 0x4e607e8
Jul 07 21:10:57-885437 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 36 bytes.
Jul 07 21:10:57-885658 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:10:57-885896 cadet-p2p-8627 DEBUG Checking 0x4e75448 towards MCZ5X28Z (->V8XX)
Jul 07 21:10:57-886141 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:10:57-886318 cadet-p2p-8627 DEBUG   size 36 ok
Jul 07 21:10:57-886520 cadet-p2p-8627 DEBUG   path ack
Jul 07 21:10:57-886690 cadet-p2p-8627 DEBUG Sending CONNECTION ACK...
Jul 07 21:10:57-886861 cadet-p2p-8627 DEBUG CONNECTION ACK sent!
Jul 07 21:10:57-887122 cadet-p2p-8627 INFO snd {    CONNECTION_ACK} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 36)
Jul 07 21:10:57-887315 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:10:57-887495 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:10:57-887704 cadet-con-8627 DEBUG  sent FWD {    CONNECTION_ACK}
Jul 07 21:10:57-887884 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:10:57-888059 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:10:57-888238 cadet-p2p-8627 DEBUG   return 36
Jul 07 21:10:57-888437 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:57-888612 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:10:57-888787 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:10:57-888986 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:57-889213 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 36 bytes.
Jul 07 21:10:57-889400 core-api-8627 DEBUG Produced SEND message to core with 36 bytes payload
Jul 07 21:10:57-889578 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:57-889774 util-8627 DEBUG Transmitting message of type 76 and size 92 to core service.
Jul 07 21:10:57-890024 util-8627 DEBUG Connection transmitted 92/92 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:10:58-215652 util-scheduler-8627 DEBUG Checking readiness of task: 481 / 0x4661f98
Jul 07 21:10:58-215976 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:58-220881 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:58-221083 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:58-221309 util-scheduler-8627 DEBUG Running task: 466 / 0x4d63d80
Jul 07 21:10:58-221540 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:10:58-221785 cadet-tun-8627 DEBUG  kx started 100 s ago
Jul 07 21:10:58-221994 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:10:58-222195 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:10:58-222397 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:10:58-222630 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:10:58-222809 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:10:58-223030 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:10:58-223319 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:10:58-223515 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:10:58-223791 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:10:58-224000 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:10:58-224315 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:10:58-224516 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:10:58-224739 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:10:58-224923 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:10:58-225098 cadet-con-8627 DEBUG  sendable
Jul 07 21:10:58-225341 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:10:58-225558 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:10:58-225778 util-scheduler-8627 DEBUG Adding task: 482 / 0x4e607e8
Jul 07 21:10:58-225961 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:10:58-226164 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:10:58-226340 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:10:58-226514 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:10:58-226750 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:10:58-226944 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:10:58-227122 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:10:58-227349 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:10:58-227592 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:10:58-227789 util-scheduler-8627 DEBUG Adding task: 483 / 0x4d63d80
Jul 07 21:10:58-228039 util-scheduler-8627 DEBUG Checking readiness of task: 481 / 0x4661f98
Jul 07 21:10:58-228230 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:58-228418 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:58-228607 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:58-228797 util-scheduler-8627 DEBUG Running task: 482 / 0x4e607e8
Jul 07 21:10:58-229004 util-scheduler-8627 DEBUG Adding task: 484 / 0x4e607e8
Jul 07 21:10:58-229249 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:10:58-229451 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:10:58-229657 util-scheduler-8627 DEBUG Adding task: 485 / 0x4661f98
Jul 07 21:10:58-229897 util-scheduler-8627 DEBUG Checking readiness of task: 485 / 0x4661f98
Jul 07 21:10:58-230089 util-scheduler-8627 DEBUG Checking readiness of task: 481 / 0x4661f98
Jul 07 21:10:58-230279 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:10:58-230468 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:10:58-230656 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:10:58-230847 util-scheduler-8627 DEBUG Running task: 485 / 0x4661f98
Jul 07 21:10:58-231031 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:10:58-231208 util-8627 DEBUG process_notify is running
Jul 07 21:10:58-231380 util-8627 DEBUG client_notify is running
Jul 07 21:10:58-231558 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:10:58-231753 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:10:58-231942 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:10:58-232199 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:01-327918 util-scheduler-8627 DEBUG Checking readiness of task: 481 / 0x4661f98
Jul 07 21:11:01-328289 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:01-328487 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:01-328679 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:01-328876 util-scheduler-8627 DEBUG Running task: 481 / 0x4661f98
Jul 07 21:11:01-329336 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:01-329616 util-scheduler-8627 DEBUG Adding task: 486 / 0x4662140
Jul 07 21:11:01-329895 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:01-330088 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:01-330279 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:01-330470 util-scheduler-8627 DEBUG Running task: 486 / 0x4662140
Jul 07 21:11:01-330661 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:01-330861 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:01-331092 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:01-331299 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:01-331509 util-scheduler-8627 DEBUG Adding task: 487 / 0x4661f98
Jul 07 21:11:01-331696 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:01-331909 util-scheduler-8627 DEBUG Adding task: 488 / 0x4661f98
Jul 07 21:11:01-332150 util-scheduler-8627 DEBUG Checking readiness of task: 488 / 0x4661f98
Jul 07 21:11:01-332341 util-scheduler-8627 DEBUG Checking readiness of task: 487 / 0x4661f98
Jul 07 21:11:01-332532 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:01-332749 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:01-332948 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:01-333140 util-scheduler-8627 DEBUG Running task: 487 / 0x4661f98
Jul 07 21:11:01-333350 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:01-333528 util-8627 DEBUG process_notify is running
Jul 07 21:11:01-333713 util-8627 DEBUG client_notify is running
Jul 07 21:11:01-333899 util-scheduler-8627 DEBUG Canceling task: 484 / 0x4e607e8
Jul 07 21:11:01-334130 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:01-334355 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:01-334597 cadet-p2p-8627 DEBUG Checking 0x4e78038 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:01-334831 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:01-335015 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:01-335206 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:01-335492 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:01-335686 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:01-335867 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:01-336060 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:01-336250 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:01-336427 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:01-336611 util-scheduler-8627 DEBUG Canceling task: 472 / 0x4e61600
Jul 07 21:11:01-336822 util-scheduler-8627 DEBUG Adding task: 489 / 0x4e61600
Jul 07 21:11:01-337073 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:01-337272 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:01-337454 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:01-337658 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:01-337832 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:01-338006 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:01-338209 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:01-338426 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:01-338609 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:01-338788 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:01-338979 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:01-339228 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:03-229824 util-scheduler-8627 DEBUG Checking readiness of task: 488 / 0x4661f98
Jul 07 21:11:03-230176 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:03-230712 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:03-230916 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:03-231205 util-scheduler-8627 DEBUG Running task: 483 / 0x4d63d80
Jul 07 21:11:03-231446 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:03-231690 cadet-tun-8627 DEBUG  kx started 105 s ago
Jul 07 21:11:03-231898 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:03-232110 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:03-232322 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:03-232556 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:03-232735 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:03-232956 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:03-233271 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:03-233470 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:03-233709 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:03-233917 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:03-234234 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:03-234460 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:03-234686 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:03-234869 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:03-235045 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:03-235251 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:03-235466 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:03-235687 util-scheduler-8627 DEBUG Adding task: 490 / 0x4e607e8
Jul 07 21:11:03-235867 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:03-236087 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:03-236264 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:03-236438 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:03-236675 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:03-236871 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:03-237049 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:03-237268 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:03-237510 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:03-237709 util-scheduler-8627 DEBUG Adding task: 491 / 0x4d63d80
Jul 07 21:11:03-237962 util-scheduler-8627 DEBUG Checking readiness of task: 488 / 0x4661f98
Jul 07 21:11:03-238154 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:03-238343 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:03-238532 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:03-238722 util-scheduler-8627 DEBUG Running task: 490 / 0x4e607e8
Jul 07 21:11:03-238929 util-scheduler-8627 DEBUG Adding task: 492 / 0x4e607e8
Jul 07 21:11:03-239180 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:03-239385 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:03-239594 util-scheduler-8627 DEBUG Adding task: 493 / 0x4661f98
Jul 07 21:11:03-239833 util-scheduler-8627 DEBUG Checking readiness of task: 493 / 0x4661f98
Jul 07 21:11:03-240029 util-scheduler-8627 DEBUG Checking readiness of task: 488 / 0x4661f98
Jul 07 21:11:03-240218 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:03-240407 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:03-240596 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:03-240787 util-scheduler-8627 DEBUG Running task: 493 / 0x4661f98
Jul 07 21:11:03-240972 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:03-241149 util-8627 DEBUG process_notify is running
Jul 07 21:11:03-241342 util-8627 DEBUG client_notify is running
Jul 07 21:11:03-241521 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:03-241717 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:03-241907 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:03-242160 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:05-701377 util-scheduler-8627 DEBUG Checking readiness of task: 488 / 0x4661f98
Jul 07 21:11:05-701727 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:05-701927 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:05-702122 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:05-702322 util-scheduler-8627 DEBUG Running task: 488 / 0x4661f98
Jul 07 21:11:05-702771 util-8627 DEBUG receive_ready read 348/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:05-703067 util-scheduler-8627 DEBUG Adding task: 494 / 0x4662140
Jul 07 21:11:05-703340 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:05-703568 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:05-703759 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:05-704042 util-scheduler-8627 DEBUG Running task: 494 / 0x4662140
Jul 07 21:11:05-704238 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:05-704459 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:05-704697 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:05-705361 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:05-707314 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:05-707816 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:05-708042 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:05-708946 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:05-709169 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:05-710008 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:05-710212 util-scheduler-8627 DEBUG Canceling task: 474 / 0x4e61600
Jul 07 21:11:05-710448 util-scheduler-8627 DEBUG Adding task: 495 / 0x4e61600
Jul 07 21:11:05-711468 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:05-711995 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:05-712221 util-scheduler-8627 DEBUG Adding task: 496 / 0x4d50e20
Jul 07 21:11:05-713717 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:05-715229 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:06-591701 cadet-tun-8627 INFO ME: WZGYSS0H
Jul 07 21:11:06-592211 cadet-tun-8627 INFO PE: H9RZ635J
Jul 07 21:11:06-592559 cadet-tun-8627 INFO KM: Z3BNAQ0Q
Jul 07 21:11:06-592902 cadet-tun-8627 INFO EK: 0D5E8DSS
Jul 07 21:11:06-593270 cadet-tun-8627 INFO DK: 45RE1JY5
Jul 07 21:11:06-594470 cadet-tun-8627 DEBUG   our key was sent, sending ping
Jul 07 21:11:06-595897 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:06-597887 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:06-599010 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:06-600258 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:06-601468 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:06-605634 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:06-622787 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:06-623997 cadet-tun-8627 DEBUG   e sending 3602480737
Jul 07 21:11:06-625109 cadet-tun-8627 DEBUG   e towards CY28
Jul 07 21:11:06-625932 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:06-626143 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:06-626379 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:06-626562 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:06-626784 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:06-627316 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:06-627523 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:06-627763 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:06-627973 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:06-628289 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:06-628490 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:06-628715 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-628900 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:06-629076 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:06-630488 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:06-631019 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:06-631203 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:06-631381 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:06-631622 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-631852 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:06-632041 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:06-632279 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-632473 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:06-632651 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:06-632911 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:06-633980 util-scheduler-8627 DEBUG Adding task: 497 / 0x4662140
Jul 07 21:11:06-634275 util-scheduler-8627 DEBUG Checking readiness of task: 496 / 0x4d50e20
Jul 07 21:11:06-634478 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-634671 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-634862 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-635057 util-scheduler-8627 DEBUG Running task: 496 / 0x4d50e20
Jul 07 21:11:06-635245 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:06-635439 util-8627 DEBUG process_notify is running
Jul 07 21:11:06-635612 util-8627 DEBUG client_notify is running
Jul 07 21:11:06-635845 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:06-636111 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:06-636323 util-scheduler-8627 DEBUG Running task: 497 / 0x4662140
Jul 07 21:11:06-636515 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:06-636739 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:06-636958 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:06-637232 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:06-637569 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:06-637805 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:06-638015 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:06-638260 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:06-638467 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:06-638653 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:06-638840 util-scheduler-8627 DEBUG Canceling task: 495 / 0x4e61600
Jul 07 21:11:06-639061 util-scheduler-8627 DEBUG Adding task: 498 / 0x4e61600
Jul 07 21:11:06-639335 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:06-639596 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:06-639827 util-scheduler-8627 DEBUG Adding task: 499 / 0x4d50e20
Jul 07 21:11:06-640169 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:06-641607 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:06-643163 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:06-643747 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:06-643923 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:06-647242 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:06-650843 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:06-652425 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:06-653814 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:06-654554 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:06-654903 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:06-658216 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:06-658977 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:06-659947 cadet-tun-8627 DEBUG   e sending 2706271322
Jul 07 21:11:06-660754 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:06-660964 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:06-661217 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:06-661400 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:06-661621 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:06-662142 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:06-662369 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:06-662607 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:06-662817 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:06-663127 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:06-663326 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:06-663551 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-663734 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:06-663910 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:06-664273 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:06-664482 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:06-664661 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:06-664847 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:06-665085 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-665302 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:06-665497 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:06-665732 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-665926 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:06-666103 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:06-666335 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-666529 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:06-666705 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:06-666903 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:06-667303 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:06-667525 util-scheduler-8627 DEBUG Adding task: 500 / 0x4661f98
Jul 07 21:11:06-667794 util-scheduler-8627 DEBUG Checking readiness of task: 500 / 0x4661f98
Jul 07 21:11:06-667993 util-scheduler-8627 DEBUG Checking readiness of task: 499 / 0x4d50e20
Jul 07 21:11:06-668185 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-668376 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-668566 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-668760 util-scheduler-8627 DEBUG Running task: 499 / 0x4d50e20
Jul 07 21:11:06-668945 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:06-669123 util-8627 DEBUG process_notify is running
Jul 07 21:11:06-669314 util-8627 DEBUG client_notify is running
Jul 07 21:11:06-669537 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:06-669797 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:06-670009 util-scheduler-8627 DEBUG Running task: 500 / 0x4661f98
Jul 07 21:11:06-670420 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:06-670661 util-scheduler-8627 DEBUG Adding task: 501 / 0x4662140
Jul 07 21:11:06-670917 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-671109 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-671299 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-671490 util-scheduler-8627 DEBUG Running task: 501 / 0x4662140
Jul 07 21:11:06-671681 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:06-671877 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:06-672092 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:06-672297 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:06-672509 util-scheduler-8627 DEBUG Adding task: 502 / 0x4661f98
Jul 07 21:11:06-672711 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:06-672910 util-scheduler-8627 DEBUG Adding task: 503 / 0x4661f98
Jul 07 21:11:06-673147 util-scheduler-8627 DEBUG Checking readiness of task: 503 / 0x4661f98
Jul 07 21:11:06-673360 util-scheduler-8627 DEBUG Checking readiness of task: 502 / 0x4661f98
Jul 07 21:11:06-673551 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-673741 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-673930 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-674120 util-scheduler-8627 DEBUG Running task: 502 / 0x4661f98
Jul 07 21:11:06-674304 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:06-674478 util-8627 DEBUG process_notify is running
Jul 07 21:11:06-674646 util-8627 DEBUG client_notify is running
Jul 07 21:11:06-674842 util-scheduler-8627 DEBUG Canceling task: 492 / 0x4e607e8
Jul 07 21:11:06-675063 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:06-675281 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:06-675514 cadet-p2p-8627 DEBUG Checking 0x4e7ad10 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:06-675746 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:06-675923 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:06-676110 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:06-676395 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:06-676839 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:06-677027 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:06-677238 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:06-677432 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:06-677614 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:06-677800 util-scheduler-8627 DEBUG Canceling task: 489 / 0x4e61600
Jul 07 21:11:06-678011 util-scheduler-8627 DEBUG Adding task: 504 / 0x4e61600
Jul 07 21:11:06-678262 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:06-678433 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:06-678657 cadet-p2p-8627 DEBUG Checking 0x5188f80 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:06-678902 cadet-p2p-8627 DEBUG Checking 0x5188f80 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:06-679835 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:06-681020 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:06-681262 util-scheduler-8627 DEBUG Adding task: 505 / 0x4e607e8
Jul 07 21:11:06-681446 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:06-682038 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:06-682247 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:06-682424 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:06-682600 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:06-682839 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-683035 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:06-683213 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:06-683446 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:06-683639 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:06-683817 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:06-684014 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:06-684220 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:06-684404 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:06-684607 util-scheduler-8627 DEBUG Adding task: 506 / 0x4e607e8
Jul 07 21:11:06-684835 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:06-685031 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:06-685251 util-scheduler-8627 DEBUG Adding task: 507 / 0x4661f98
Jul 07 21:11:06-685468 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:06-685719 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:06-685916 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:06-686163 util-scheduler-8627 DEBUG Checking readiness of task: 507 / 0x4661f98
Jul 07 21:11:06-686358 util-scheduler-8627 DEBUG Checking readiness of task: 503 / 0x4661f98
Jul 07 21:11:06-686549 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-686739 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-686930 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-687128 util-scheduler-8627 DEBUG Running task: 507 / 0x4661f98
Jul 07 21:11:06-687325 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:06-687503 util-8627 DEBUG process_notify is running
Jul 07 21:11:06-687673 util-8627 DEBUG client_notify is running
Jul 07 21:11:06-687852 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:06-688059 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:06-688257 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:06-688493 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:06-688699 util-scheduler-8627 DEBUG Running task: 505 / 0x4e607e8
Jul 07 21:11:06-689116 util-scheduler-8627 DEBUG Canceling task: 506 / 0x4e607e8
Jul 07 21:11:06-689545 util-scheduler-8627 DEBUG Adding task: 508 / 0x4e607e8
Jul 07 21:11:06-689773 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:06-689974 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:06-690177 util-scheduler-8627 DEBUG Adding task: 509 / 0x4661f98
Jul 07 21:11:06-690423 util-scheduler-8627 DEBUG Checking readiness of task: 509 / 0x4661f98
Jul 07 21:11:06-690618 util-scheduler-8627 DEBUG Checking readiness of task: 503 / 0x4661f98
Jul 07 21:11:06-690816 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:06-691009 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:06-691200 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:06-691394 util-scheduler-8627 DEBUG Running task: 509 / 0x4661f98
Jul 07 21:11:06-691579 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:06-691756 util-8627 DEBUG process_notify is running
Jul 07 21:11:06-691925 util-8627 DEBUG client_notify is running
Jul 07 21:11:06-692101 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:06-692292 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:06-692481 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:06-692725 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:08-239381 util-scheduler-8627 DEBUG Checking readiness of task: 503 / 0x4661f98
Jul 07 21:11:08-239706 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:08-240393 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:08-240589 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:08-240838 util-scheduler-8627 DEBUG Running task: 491 / 0x4d63d80
Jul 07 21:11:08-241088 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:08-241355 cadet-tun-8627 DEBUG  kx started 110 s ago
Jul 07 21:11:08-241566 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:08-241783 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:08-241985 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:08-242217 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:08-242413 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:08-242658 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:08-242947 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:08-243144 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:08-243382 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:08-243590 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:08-243918 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:08-244119 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:08-244343 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-244526 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:08-244702 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:08-244905 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:08-245107 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:08-245304 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:08-245480 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:08-245718 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-245914 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:08-246093 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:08-246326 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-246519 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:08-246697 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:08-246929 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-247122 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:08-247299 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:08-247497 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:08-248172 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:08-248639 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:08-249009 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:08-249207 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:08-249395 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:08-252869 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:08-254167 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:08-254531 cadet-tun-8627 DEBUG   e sending 222516983
Jul 07 21:11:08-254900 cadet-tun-8627 DEBUG   e towards PD0B
Jul 07 21:11:08-255109 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:08-255311 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:08-255541 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:08-255720 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:08-255940 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:08-256215 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:08-256413 cadet-con-8627 DEBUG   C_P+ 0x4e61600 3
Jul 07 21:11:08-256650 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:08-256915 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:08-257248 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:08-257449 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:08-257681 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-257865 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:08-258041 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:08-258244 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:08-258445 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:08-258620 cadet-p2p-8627 DEBUG QQQ  queue length: 4
Jul 07 21:11:08-258794 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:08-259033 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-259248 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:08-259427 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:08-259660 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-259854 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:08-260031 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:08-260263 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-260456 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:08-260633 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:08-260865 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:08-261058 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:08-261258 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:08-261457 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:08-261941 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:08-262156 util-scheduler-8627 DEBUG Adding task: 510 / 0x4d63d80
Jul 07 21:11:09-863261 util-scheduler-8627 DEBUG Checking readiness of task: 503 / 0x4661f98
Jul 07 21:11:09-863628 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-863825 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-864018 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-864216 util-scheduler-8627 DEBUG Running task: 503 / 0x4661f98
Jul 07 21:11:09-864651 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:09-864910 util-scheduler-8627 DEBUG Adding task: 511 / 0x4662140
Jul 07 21:11:09-865186 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-865407 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-865598 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-865789 util-scheduler-8627 DEBUG Running task: 511 / 0x4662140
Jul 07 21:11:09-865981 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:09-866181 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:09-866412 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:09-866645 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:09-866853 util-scheduler-8627 DEBUG Adding task: 512 / 0x4661f98
Jul 07 21:11:09-867042 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:09-867249 util-scheduler-8627 DEBUG Adding task: 513 / 0x4661f98
Jul 07 21:11:09-867515 util-scheduler-8627 DEBUG Checking readiness of task: 513 / 0x4661f98
Jul 07 21:11:09-867756 util-scheduler-8627 DEBUG Checking readiness of task: 512 / 0x4661f98
Jul 07 21:11:09-867982 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-868189 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-868379 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-868572 util-scheduler-8627 DEBUG Running task: 512 / 0x4661f98
Jul 07 21:11:09-868758 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:09-868937 util-8627 DEBUG process_notify is running
Jul 07 21:11:09-869110 util-8627 DEBUG client_notify is running
Jul 07 21:11:09-869319 util-scheduler-8627 DEBUG Canceling task: 508 / 0x4e607e8
Jul 07 21:11:09-869542 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:09-869763 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:09-870001 cadet-p2p-8627 DEBUG Checking 0x5188f80 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:09-870248 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:09-870424 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:09-870615 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:09-870900 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:09-871122 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:09-871303 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:09-871493 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:09-871683 cadet-con-8627 DEBUG  C_P- 0x4e61600 4
Jul 07 21:11:09-871861 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:09-872046 util-scheduler-8627 DEBUG Canceling task: 504 / 0x4e61600
Jul 07 21:11:09-872257 util-scheduler-8627 DEBUG Adding task: 514 / 0x4e61600
Jul 07 21:11:09-872508 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:09-872679 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:09-872899 cadet-p2p-8627 DEBUG Checking 0x5195e58 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:09-873138 cadet-p2p-8627 DEBUG Checking 0x5195e58 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:09-873503 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:09-873717 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:09-873934 util-scheduler-8627 DEBUG Adding task: 515 / 0x4e607e8
Jul 07 21:11:09-874114 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:09-874290 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:09-874489 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:09-874663 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:09-874838 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:09-875085 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:09-875281 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:09-875459 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:09-875692 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:09-875886 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:09-876063 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:09-876295 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:09-876488 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:09-876665 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:09-876863 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:09-877067 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:09-877271 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:09-877475 util-scheduler-8627 DEBUG Adding task: 516 / 0x4e607e8
Jul 07 21:11:09-877692 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:09-877887 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:09-878087 util-scheduler-8627 DEBUG Adding task: 517 / 0x4661f98
Jul 07 21:11:09-878288 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:09-878541 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:09-878741 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:09-878986 util-scheduler-8627 DEBUG Checking readiness of task: 517 / 0x4661f98
Jul 07 21:11:09-879179 util-scheduler-8627 DEBUG Checking readiness of task: 513 / 0x4661f98
Jul 07 21:11:09-879369 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-879559 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-879748 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-879941 util-scheduler-8627 DEBUG Running task: 517 / 0x4661f98
Jul 07 21:11:09-880125 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:09-880300 util-8627 DEBUG process_notify is running
Jul 07 21:11:09-880468 util-8627 DEBUG client_notify is running
Jul 07 21:11:09-880646 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:09-880840 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:09-881045 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:09-881308 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:09-881517 util-scheduler-8627 DEBUG Running task: 515 / 0x4e607e8
Jul 07 21:11:09-881711 util-scheduler-8627 DEBUG Canceling task: 516 / 0x4e607e8
Jul 07 21:11:09-881923 util-scheduler-8627 DEBUG Adding task: 518 / 0x4e607e8
Jul 07 21:11:09-882139 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:09-882334 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:09-882532 util-scheduler-8627 DEBUG Adding task: 519 / 0x4661f98
Jul 07 21:11:09-882768 util-scheduler-8627 DEBUG Checking readiness of task: 519 / 0x4661f98
Jul 07 21:11:09-882960 util-scheduler-8627 DEBUG Checking readiness of task: 513 / 0x4661f98
Jul 07 21:11:09-883149 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-883348 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-883538 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-883728 util-scheduler-8627 DEBUG Running task: 519 / 0x4661f98
Jul 07 21:11:09-883911 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:09-884085 util-8627 DEBUG process_notify is running
Jul 07 21:11:09-884252 util-8627 DEBUG client_notify is running
Jul 07 21:11:09-884428 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:09-884617 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:09-884803 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:09-885042 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:09-993707 util-scheduler-8627 DEBUG Checking readiness of task: 513 / 0x4661f98
Jul 07 21:11:09-993953 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-994149 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-994342 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-994536 util-scheduler-8627 DEBUG Running task: 513 / 0x4661f98
Jul 07 21:11:09-994943 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:09-995179 util-scheduler-8627 DEBUG Adding task: 520 / 0x4662140
Jul 07 21:11:09-995432 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-995623 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-995814 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-996003 util-scheduler-8627 DEBUG Running task: 520 / 0x4662140
Jul 07 21:11:09-996193 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:09-996389 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:09-996610 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:09-996817 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:09-997019 util-scheduler-8627 DEBUG Adding task: 521 / 0x4661f98
Jul 07 21:11:09-997265 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:09-997472 util-scheduler-8627 DEBUG Adding task: 522 / 0x4661f98
Jul 07 21:11:09-997711 util-scheduler-8627 DEBUG Checking readiness of task: 522 / 0x4661f98
Jul 07 21:11:09-997902 util-scheduler-8627 DEBUG Checking readiness of task: 521 / 0x4661f98
Jul 07 21:11:09-998093 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:09-998282 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:09-998471 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:09-998661 util-scheduler-8627 DEBUG Running task: 521 / 0x4661f98
Jul 07 21:11:09-998865 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:09-999041 util-8627 DEBUG process_notify is running
Jul 07 21:11:09-999211 util-8627 DEBUG client_notify is running
Jul 07 21:11:09-999395 util-scheduler-8627 DEBUG Canceling task: 518 / 0x4e607e8
Jul 07 21:11:09-999615 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:11:09-999830 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:10-000063 cadet-p2p-8627 DEBUG Checking 0x5195e58 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:10-000310 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:10-000488 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:11:10-000675 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:10-000956 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:11:10-001151 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:10-001355 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:10-001543 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:10-001754 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:10-001932 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:10-002118 util-scheduler-8627 DEBUG Canceling task: 514 / 0x4e61600
Jul 07 21:11:10-002328 util-scheduler-8627 DEBUG Adding task: 523 / 0x4e61600
Jul 07 21:11:10-002575 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:10-002745 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:10-002966 cadet-p2p-8627 DEBUG Checking 0x51998b8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:10-003204 cadet-p2p-8627 DEBUG Checking 0x51998b8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:10-003383 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:10-003588 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:10-003802 util-scheduler-8627 DEBUG Adding task: 524 / 0x4e607e8
Jul 07 21:11:10-003982 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:10-004159 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:11:10-004357 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:10-004531 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:10-004707 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:10-004945 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:10-005141 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:10-005343 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:10-005579 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:10-005774 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:10-005952 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:10-006151 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:10-006355 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:11:10-006539 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:11:10-006740 util-scheduler-8627 DEBUG Adding task: 525 / 0x4e607e8
Jul 07 21:11:10-006956 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:10-007150 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:10-007351 util-scheduler-8627 DEBUG Adding task: 526 / 0x4661f98
Jul 07 21:11:10-007550 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:11:10-007797 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:10-007996 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:10-008237 util-scheduler-8627 DEBUG Checking readiness of task: 526 / 0x4661f98
Jul 07 21:11:10-008762 util-scheduler-8627 DEBUG Checking readiness of task: 522 / 0x4661f98
Jul 07 21:11:10-008959 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:10-009152 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:10-009995 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:10-010198 util-scheduler-8627 DEBUG Running task: 526 / 0x4661f98
Jul 07 21:11:10-010389 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:10-010586 util-8627 DEBUG process_notify is running
Jul 07 21:11:10-010762 util-8627 DEBUG client_notify is running
Jul 07 21:11:10-010942 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:10-011139 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:10-011331 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:10-011574 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:10-011795 util-scheduler-8627 DEBUG Running task: 524 / 0x4e607e8
Jul 07 21:11:10-011990 util-scheduler-8627 DEBUG Canceling task: 525 / 0x4e607e8
Jul 07 21:11:10-012209 util-scheduler-8627 DEBUG Adding task: 527 / 0x4e607e8
Jul 07 21:11:10-012429 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:10-012626 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:10-012828 util-scheduler-8627 DEBUG Adding task: 528 / 0x4661f98
Jul 07 21:11:10-013074 util-scheduler-8627 DEBUG Checking readiness of task: 528 / 0x4661f98
Jul 07 21:11:10-013292 util-scheduler-8627 DEBUG Checking readiness of task: 522 / 0x4661f98
Jul 07 21:11:10-013484 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:10-013677 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:10-013868 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:10-014059 util-scheduler-8627 DEBUG Running task: 528 / 0x4661f98
Jul 07 21:11:10-014243 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:10-014419 util-8627 DEBUG process_notify is running
Jul 07 21:11:10-014589 util-8627 DEBUG client_notify is running
Jul 07 21:11:10-014765 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:10-014956 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:10-015144 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:10-015377 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:10-015628 util-scheduler-8627 DEBUG Checking readiness of task: 522 / 0x4661f98
Jul 07 21:11:10-015823 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:10-016014 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:10-016205 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:10-016397 util-scheduler-8627 DEBUG Running task: 522 / 0x4661f98
Jul 07 21:11:10-016801 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:10-017029 util-scheduler-8627 DEBUG Adding task: 529 / 0x4662140
Jul 07 21:11:10-017299 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:10-017492 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:10-017684 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:10-017874 util-scheduler-8627 DEBUG Running task: 529 / 0x4662140
Jul 07 21:11:10-018066 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:10-018262 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:10-018477 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:10-018869 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:10-019082 util-scheduler-8627 DEBUG Adding task: 530 / 0x4661f98
Jul 07 21:11:13-265548 util-scheduler-8627 DEBUG Checking readiness of task: 530 / 0x4661f98
Jul 07 21:11:13-265989 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:13-266271 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:13-266537 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:13-266822 util-scheduler-8627 DEBUG Running task: 510 / 0x4d63d80
Jul 07 21:11:13-267081 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:13-267330 cadet-tun-8627 DEBUG  kx started 115 s ago
Jul 07 21:11:13-267559 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:13-267761 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:13-267964 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:13-268201 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:13-268381 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:13-268603 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:13-268894 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:13-269094 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:13-269375 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:13-269586 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:13-269907 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:13-270110 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:13-270336 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-270521 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:13-270698 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:13-271104 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:13-271311 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:13-271487 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:13-271662 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:13-271900 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-272096 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:13-272277 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:13-272510 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-272703 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:13-272879 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:13-273110 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-273327 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:13-273504 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:13-273719 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:13-273924 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:13-274247 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:13-274447 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:13-274616 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:13-274796 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:13-278341 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:13-279142 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:13-279320 cadet-tun-8627 DEBUG   e sending 1948452687
Jul 07 21:11:13-279528 cadet-tun-8627 DEBUG   e towards H3X7
Jul 07 21:11:13-279726 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:13-279924 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:13-280152 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:13-280330 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:13-280549 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:13-280823 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:13-281020 cadet-con-8627 DEBUG   C_P+ 0x4e61600 3
Jul 07 21:11:13-281286 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:13-281494 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:13-281804 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:13-282027 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:13-282260 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-282455 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:13-282635 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:13-282845 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:13-283053 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:13-283229 cadet-p2p-8627 DEBUG QQQ  queue length: 4
Jul 07 21:11:13-283402 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:13-283640 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-283835 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:13-284012 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:13-284245 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-284436 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:13-284612 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:13-284843 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-285034 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:13-285233 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:13-285466 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:13-285658 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:13-285834 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:13-286030 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:13-286282 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:13-286490 util-scheduler-8627 DEBUG Adding task: 531 / 0x4d63d80
Jul 07 21:11:14-847810 util-scheduler-8627 DEBUG Checking readiness of task: 530 / 0x4661f98
Jul 07 21:11:14-848181 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:14-848377 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:14-848569 util-scheduler-8627 DEBUG Checking readiness of task: 141 / 0x465ed58
Jul 07 21:11:14-848769 util-scheduler-8627 DEBUG Running task: 141 / 0x465ed58
Jul 07 21:11:14-849234 util-8627 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:11:14-849497 util-scheduler-8627 DEBUG Adding task: 532 / 0x465ef00
Jul 07 21:11:14-849776 util-scheduler-8627 DEBUG Checking readiness of task: 530 / 0x4661f98
Jul 07 21:11:14-849969 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:14-850160 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:14-850352 util-scheduler-8627 DEBUG Running task: 532 / 0x465ef00
Jul 07 21:11:14-850546 util-8627 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 21:11:14-850810 nse-api-8627 DEBUG Received information about peer `YTQV' from peerinfo database
Jul 07 21:11:14-851400 cadet-hll-8627 DEBUG  hello with id 0xbee5e888 and msg (nil)
Jul 07 21:11:14-851623 util-scheduler-8627 DEBUG Adding task: 533 / 0x465ef00
Jul 07 21:11:14-851862 util-scheduler-8627 DEBUG Checking readiness of task: 530 / 0x4661f98
Jul 07 21:11:14-852054 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:14-852244 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:14-852434 util-scheduler-8627 DEBUG Running task: 533 / 0x465ef00
Jul 07 21:11:14-852625 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:11:14-852844 nse-api-8627 DEBUG Received information about peer `YTQV' from peerinfo database
Jul 07 21:11:14-853118 cadet-hll-8627 DEBUG  hello for YTQV (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:11:14-853408 cadet-p2p-8627 DEBUG set hello for YTQV
Jul 07 21:11:14-853583 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:11:14-853802 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:14-854018 util-scheduler-8627 DEBUG Adding task: 534 / 0x465ed58
Jul 07 21:11:15-442228 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-442585 util-scheduler-8627 DEBUG Checking readiness of task: 530 / 0x4661f98
Jul 07 21:11:15-442787 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-442979 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-443177 util-scheduler-8627 DEBUG Running task: 530 / 0x4661f98
Jul 07 21:11:15-443618 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:15-443883 util-scheduler-8627 DEBUG Adding task: 535 / 0x4662140
Jul 07 21:11:15-444157 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-444348 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-444538 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-444729 util-scheduler-8627 DEBUG Running task: 535 / 0x4662140
Jul 07 21:11:15-444920 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:15-445121 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:15-445382 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:15-445590 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-445798 util-scheduler-8627 DEBUG Adding task: 536 / 0x4661f98
Jul 07 21:11:15-445984 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:15-446190 util-scheduler-8627 DEBUG Adding task: 537 / 0x4661f98
Jul 07 21:11:15-446431 util-scheduler-8627 DEBUG Checking readiness of task: 537 / 0x4661f98
Jul 07 21:11:15-446622 util-scheduler-8627 DEBUG Checking readiness of task: 536 / 0x4661f98
Jul 07 21:11:15-446814 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-447003 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-447191 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-447383 util-scheduler-8627 DEBUG Running task: 536 / 0x4661f98
Jul 07 21:11:15-447568 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-447745 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-447918 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-448105 util-scheduler-8627 DEBUG Canceling task: 527 / 0x4e607e8
Jul 07 21:11:15-448348 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:15-448567 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:15-448806 cadet-p2p-8627 DEBUG Checking 0x51998b8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-449040 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:15-449238 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:15-449430 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:15-449717 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:15-449912 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:15-450091 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:15-450278 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:15-450467 cadet-con-8627 DEBUG  C_P- 0x4e61600 4
Jul 07 21:11:15-450644 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:15-450829 util-scheduler-8627 DEBUG Canceling task: 523 / 0x4e61600
Jul 07 21:11:15-451040 util-scheduler-8627 DEBUG Adding task: 538 / 0x4e61600
Jul 07 21:11:15-451288 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:15-451458 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:15-451678 cadet-p2p-8627 DEBUG Checking 0x51a0358 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-451915 cadet-p2p-8627 DEBUG Checking 0x51a0358 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-452120 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:15-452328 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:15-452540 util-scheduler-8627 DEBUG Adding task: 539 / 0x4e607e8
Jul 07 21:11:15-452719 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:15-452899 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:15-453097 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:15-453293 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:15-453468 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:15-453707 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-453901 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:15-454078 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:15-454311 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-454502 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:15-454678 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:15-454910 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-455103 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:15-455279 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:15-455476 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:15-455680 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:15-455863 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:15-456125 util-scheduler-8627 DEBUG Adding task: 540 / 0x4e607e8
Jul 07 21:11:15-456345 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-456539 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-456739 util-scheduler-8627 DEBUG Adding task: 541 / 0x4661f98
Jul 07 21:11:15-456940 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:15-457216 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-457417 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:15-457660 util-scheduler-8627 DEBUG Checking readiness of task: 541 / 0x4661f98
Jul 07 21:11:15-457853 util-scheduler-8627 DEBUG Checking readiness of task: 537 / 0x4661f98
Jul 07 21:11:15-458042 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-458230 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-458418 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-458610 util-scheduler-8627 DEBUG Running task: 541 / 0x4661f98
Jul 07 21:11:15-458794 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-458968 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-459136 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-459313 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-459506 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-459693 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-459934 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-460140 util-scheduler-8627 DEBUG Running task: 539 / 0x4e607e8
Jul 07 21:11:15-460331 util-scheduler-8627 DEBUG Canceling task: 540 / 0x4e607e8
Jul 07 21:11:15-460540 util-scheduler-8627 DEBUG Adding task: 542 / 0x4e607e8
Jul 07 21:11:15-460755 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-460947 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-461145 util-scheduler-8627 DEBUG Adding task: 543 / 0x4661f98
Jul 07 21:11:15-461402 util-scheduler-8627 DEBUG Checking readiness of task: 543 / 0x4661f98
Jul 07 21:11:15-461594 util-scheduler-8627 DEBUG Checking readiness of task: 537 / 0x4661f98
Jul 07 21:11:15-461797 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-461987 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-462175 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-462365 util-scheduler-8627 DEBUG Running task: 543 / 0x4661f98
Jul 07 21:11:15-462548 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-462722 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-462893 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-463068 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-463257 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-463443 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-463685 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-699740 util-scheduler-8627 DEBUG Checking readiness of task: 537 / 0x4661f98
Jul 07 21:11:15-700059 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-700255 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-700448 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-700658 util-scheduler-8627 DEBUG Running task: 537 / 0x4661f98
Jul 07 21:11:15-701081 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:15-701377 util-scheduler-8627 DEBUG Adding task: 544 / 0x4662140
Jul 07 21:11:15-701647 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-701840 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-702031 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-702221 util-scheduler-8627 DEBUG Running task: 544 / 0x4662140
Jul 07 21:11:15-702412 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:15-702611 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:15-702837 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:15-703045 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-703250 util-scheduler-8627 DEBUG Adding task: 545 / 0x4661f98
Jul 07 21:11:15-703437 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:15-703639 util-scheduler-8627 DEBUG Adding task: 546 / 0x4661f98
Jul 07 21:11:15-703879 util-scheduler-8627 DEBUG Checking readiness of task: 546 / 0x4661f98
Jul 07 21:11:15-704070 util-scheduler-8627 DEBUG Checking readiness of task: 545 / 0x4661f98
Jul 07 21:11:15-704264 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-704453 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-704643 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-704835 util-scheduler-8627 DEBUG Running task: 545 / 0x4661f98
Jul 07 21:11:15-705020 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-705243 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-705418 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-705605 util-scheduler-8627 DEBUG Canceling task: 542 / 0x4e607e8
Jul 07 21:11:15-705829 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:15-706049 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:15-706289 cadet-p2p-8627 DEBUG Checking 0x51a0358 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-706522 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:15-706699 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:15-706888 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:15-707172 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:15-707398 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:15-707579 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:15-707767 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:15-707956 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:15-708133 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:15-708318 util-scheduler-8627 DEBUG Canceling task: 538 / 0x4e61600
Jul 07 21:11:15-708530 util-scheduler-8627 DEBUG Adding task: 547 / 0x4e61600
Jul 07 21:11:15-708780 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:15-708951 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:15-709171 cadet-p2p-8627 DEBUG Checking 0x51a6948 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-709436 cadet-p2p-8627 DEBUG Checking 0x51a6948 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-709615 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:15-709821 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:15-710044 util-scheduler-8627 DEBUG Adding task: 548 / 0x4e607e8
Jul 07 21:11:15-710222 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:15-710398 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:15-710596 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:15-710771 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:15-710945 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:15-711181 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-711376 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:15-711553 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:15-711786 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-711979 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:15-712155 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:15-712352 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:15-712557 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:15-712740 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:15-712942 util-scheduler-8627 DEBUG Adding task: 549 / 0x4e607e8
Jul 07 21:11:15-713159 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-713381 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-713583 util-scheduler-8627 DEBUG Adding task: 550 / 0x4661f98
Jul 07 21:11:15-713782 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:15-714035 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-714238 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:15-714481 util-scheduler-8627 DEBUG Checking readiness of task: 550 / 0x4661f98
Jul 07 21:11:15-714701 util-scheduler-8627 DEBUG Checking readiness of task: 546 / 0x4661f98
Jul 07 21:11:15-714903 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-715097 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-715290 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-715484 util-scheduler-8627 DEBUG Running task: 550 / 0x4661f98
Jul 07 21:11:15-715669 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-715845 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-716015 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-716193 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-716391 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-716580 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-716824 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-717031 util-scheduler-8627 DEBUG Running task: 548 / 0x4e607e8
Jul 07 21:11:15-717248 util-scheduler-8627 DEBUG Canceling task: 549 / 0x4e607e8
Jul 07 21:11:15-717479 util-scheduler-8627 DEBUG Adding task: 551 / 0x4e607e8
Jul 07 21:11:15-717696 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-717891 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-718102 util-scheduler-8627 DEBUG Adding task: 552 / 0x4661f98
Jul 07 21:11:15-718342 util-scheduler-8627 DEBUG Checking readiness of task: 552 / 0x4661f98
Jul 07 21:11:15-718534 util-scheduler-8627 DEBUG Checking readiness of task: 546 / 0x4661f98
Jul 07 21:11:15-718723 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-718912 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-719110 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-719332 util-scheduler-8627 DEBUG Running task: 552 / 0x4661f98
Jul 07 21:11:15-719517 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-719692 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-719861 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-720037 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-720229 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-720417 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-720667 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-825175 util-scheduler-8627 DEBUG Checking readiness of task: 546 / 0x4661f98
Jul 07 21:11:15-825414 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-825607 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-825799 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-825993 util-scheduler-8627 DEBUG Running task: 546 / 0x4661f98
Jul 07 21:11:15-826399 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:15-826647 util-scheduler-8627 DEBUG Adding task: 553 / 0x4662140
Jul 07 21:11:15-826895 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-827087 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-827277 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-827466 util-scheduler-8627 DEBUG Running task: 553 / 0x4662140
Jul 07 21:11:15-827656 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:15-827852 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:15-828070 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:15-828269 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-828470 util-scheduler-8627 DEBUG Adding task: 554 / 0x4661f98
Jul 07 21:11:15-828654 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:15-828855 util-scheduler-8627 DEBUG Adding task: 555 / 0x4661f98
Jul 07 21:11:15-829092 util-scheduler-8627 DEBUG Checking readiness of task: 555 / 0x4661f98
Jul 07 21:11:15-829311 util-scheduler-8627 DEBUG Checking readiness of task: 554 / 0x4661f98
Jul 07 21:11:15-829502 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-829692 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-829880 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-830071 util-scheduler-8627 DEBUG Running task: 554 / 0x4661f98
Jul 07 21:11:15-830254 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-830428 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-830598 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-830781 util-scheduler-8627 DEBUG Canceling task: 551 / 0x4e607e8
Jul 07 21:11:15-831000 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:15-831236 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:15-831470 cadet-p2p-8627 DEBUG Checking 0x51a6948 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-831701 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:15-831878 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:15-832063 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:15-832356 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:15-832550 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:15-832727 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:15-832912 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:15-833099 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:15-833302 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:15-833487 util-scheduler-8627 DEBUG Canceling task: 547 / 0x4e61600
Jul 07 21:11:15-833696 util-scheduler-8627 DEBUG Adding task: 556 / 0x4e61600
Jul 07 21:11:15-833941 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:15-834111 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:15-834330 cadet-p2p-8627 DEBUG Checking 0x51ad3e8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-834568 cadet-p2p-8627 DEBUG Checking 0x51ad3e8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-834745 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:15-834949 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:15-835159 util-scheduler-8627 DEBUG Adding task: 557 / 0x4e607e8
Jul 07 21:11:15-835337 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:15-835512 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:15-835709 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:15-835883 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:15-836056 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:15-836293 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:15-836491 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:15-836668 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:15-836865 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:15-837069 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:15-837278 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:15-837479 util-scheduler-8627 DEBUG Adding task: 558 / 0x4e607e8
Jul 07 21:11:15-837693 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-837886 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-838085 util-scheduler-8627 DEBUG Adding task: 559 / 0x4661f98
Jul 07 21:11:15-838282 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:15-838532 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-838728 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:15-838968 util-scheduler-8627 DEBUG Checking readiness of task: 559 / 0x4661f98
Jul 07 21:11:15-839160 util-scheduler-8627 DEBUG Checking readiness of task: 555 / 0x4661f98
Jul 07 21:11:15-839349 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-839538 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-839728 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-839919 util-scheduler-8627 DEBUG Running task: 559 / 0x4661f98
Jul 07 21:11:15-840103 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-840288 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-840457 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-840634 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-840826 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-841013 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-841286 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-841494 util-scheduler-8627 DEBUG Running task: 557 / 0x4e607e8
Jul 07 21:11:15-841686 util-scheduler-8627 DEBUG Canceling task: 558 / 0x4e607e8
Jul 07 21:11:15-841897 util-scheduler-8627 DEBUG Adding task: 560 / 0x4e607e8
Jul 07 21:11:15-842112 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:15-842306 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-842504 util-scheduler-8627 DEBUG Adding task: 561 / 0x4661f98
Jul 07 21:11:15-842742 util-scheduler-8627 DEBUG Checking readiness of task: 561 / 0x4661f98
Jul 07 21:11:15-842933 util-scheduler-8627 DEBUG Checking readiness of task: 555 / 0x4661f98
Jul 07 21:11:15-843122 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-843310 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-843499 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-843689 util-scheduler-8627 DEBUG Running task: 555 / 0x4661f98
Jul 07 21:11:15-844089 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:15-844312 util-scheduler-8627 DEBUG Adding task: 562 / 0x4662140
Jul 07 21:11:15-844519 util-scheduler-8627 DEBUG Running task: 561 / 0x4661f98
Jul 07 21:11:15-844702 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-844875 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-845043 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-845242 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:15-845433 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-845620 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:15-845861 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:15-846103 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-846293 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-846485 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-846673 util-scheduler-8627 DEBUG Running task: 562 / 0x4662140
Jul 07 21:11:15-846861 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:15-847052 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:15-847263 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:15-847442 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:15-847652 util-scheduler-8627 DEBUG Adding task: 563 / 0x4661f98
Jul 07 21:11:15-847887 util-scheduler-8627 DEBUG Checking readiness of task: 563 / 0x4661f98
Jul 07 21:11:15-848078 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-848266 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-848454 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-848644 util-scheduler-8627 DEBUG Running task: 563 / 0x4661f98
Jul 07 21:11:15-849042 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:15-849288 util-scheduler-8627 DEBUG Adding task: 564 / 0x4662140
Jul 07 21:11:15-849531 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-849722 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-849911 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-850100 util-scheduler-8627 DEBUG Running task: 564 / 0x4662140
Jul 07 21:11:15-850287 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:15-850501 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:15-850712 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:15-850906 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:15-851103 util-scheduler-8627 DEBUG Adding task: 565 / 0x4661f98
Jul 07 21:11:15-851285 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:15-851481 util-scheduler-8627 DEBUG Adding task: 566 / 0x4661f98
Jul 07 21:11:15-851716 util-scheduler-8627 DEBUG Checking readiness of task: 566 / 0x4661f98
Jul 07 21:11:15-851906 util-scheduler-8627 DEBUG Checking readiness of task: 565 / 0x4661f98
Jul 07 21:11:15-852096 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:15-852284 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:15-852472 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:15-852663 util-scheduler-8627 DEBUG Running task: 565 / 0x4661f98
Jul 07 21:11:15-852845 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:15-853019 util-8627 DEBUG process_notify is running
Jul 07 21:11:15-853241 util-8627 DEBUG client_notify is running
Jul 07 21:11:15-853425 util-scheduler-8627 DEBUG Canceling task: 560 / 0x4e607e8
Jul 07 21:11:15-853642 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:15-853854 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:15-854083 cadet-p2p-8627 DEBUG Checking 0x51ad3e8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:15-854311 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:15-854488 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:15-854757 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:15-855037 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:15-855229 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:15-855404 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:15-855587 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:15-855774 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:15-855949 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:15-856131 util-scheduler-8627 DEBUG Canceling task: 556 / 0x4e61600
Jul 07 21:11:15-856339 util-scheduler-8627 DEBUG Adding task: 567 / 0x4e61600
Jul 07 21:11:15-856583 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:15-856751 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:15-856929 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:15-857125 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:15-857326 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:15-857499 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:15-857696 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:15-857899 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:15-858080 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:15-858256 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:15-858442 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:15-858688 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:18-289063 util-scheduler-8627 DEBUG Checking readiness of task: 566 / 0x4661f98
Jul 07 21:11:18-289479 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:18-290378 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:18-290797 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:18-290999 util-scheduler-8627 DEBUG Running task: 531 / 0x4d63d80
Jul 07 21:11:18-291236 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:18-291495 cadet-tun-8627 DEBUG  kx started 2 m ago
Jul 07 21:11:18-291703 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:18-291934 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:18-292138 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:18-292371 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:18-292551 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:18-292773 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:18-293063 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:18-293286 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:18-293527 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:18-293737 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:18-294052 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:18-294252 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:18-294475 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:18-294659 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:18-294835 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:18-295042 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:18-295257 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:18-295479 util-scheduler-8627 DEBUG Adding task: 568 / 0x4e607e8
Jul 07 21:11:18-295659 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:18-295862 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:18-296037 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:18-296210 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:18-296447 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:18-296642 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:18-296839 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:18-297037 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:18-297259 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:18-297570 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:18-297771 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:18-297941 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:18-298121 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:18-301687 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:18-302999 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:18-303193 cadet-tun-8627 DEBUG   e sending 2859192226
Jul 07 21:11:18-303402 cadet-tun-8627 DEBUG   e towards PX2B
Jul 07 21:11:18-303606 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:18-303805 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:18-304032 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:18-304210 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:18-304429 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:18-304710 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:18-304907 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:18-305140 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:18-305372 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:18-305679 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:18-305876 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:18-306098 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:18-306280 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:18-306454 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:18-306655 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:18-306856 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:18-307030 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:18-307203 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:18-307458 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:18-307654 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:18-307832 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:18-308064 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:18-308257 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:18-308433 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:18-308629 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:18-308876 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:18-309080 util-scheduler-8627 DEBUG Adding task: 569 / 0x4d63d80
Jul 07 21:11:18-309363 util-scheduler-8627 DEBUG Checking readiness of task: 566 / 0x4661f98
Jul 07 21:11:18-309557 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:18-309745 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:18-309933 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:18-310124 util-scheduler-8627 DEBUG Running task: 568 / 0x4e607e8
Jul 07 21:11:18-310330 util-scheduler-8627 DEBUG Adding task: 570 / 0x4e607e8
Jul 07 21:11:18-310550 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:18-310752 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:18-310960 util-scheduler-8627 DEBUG Adding task: 571 / 0x4661f98
Jul 07 21:11:18-311388 util-scheduler-8627 DEBUG Checking readiness of task: 571 / 0x4661f98
Jul 07 21:11:18-311688 util-scheduler-8627 DEBUG Checking readiness of task: 566 / 0x4661f98
Jul 07 21:11:18-311955 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:18-312240 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:18-312502 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:18-312740 util-scheduler-8627 DEBUG Running task: 571 / 0x4661f98
Jul 07 21:11:18-315880 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:18-316063 util-8627 DEBUG process_notify is running
Jul 07 21:11:18-316238 util-8627 DEBUG client_notify is running
Jul 07 21:11:18-316418 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:18-316618 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:18-316810 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:18-317112 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:21-347129 util-scheduler-8627 DEBUG Checking readiness of task: 566 / 0x4661f98
Jul 07 21:11:21-347476 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-347672 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-347868 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-348071 util-scheduler-8627 DEBUG Running task: 566 / 0x4661f98
Jul 07 21:11:21-348494 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:21-348759 util-scheduler-8627 DEBUG Adding task: 572 / 0x4662140
Jul 07 21:11:21-349036 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-349250 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-349442 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-349640 util-scheduler-8627 DEBUG Running task: 572 / 0x4662140
Jul 07 21:11:21-349835 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:21-350034 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:21-350264 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:21-350468 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:21-350701 util-scheduler-8627 DEBUG Adding task: 573 / 0x4661f98
Jul 07 21:11:21-350888 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:21-351094 util-scheduler-8627 DEBUG Adding task: 574 / 0x4661f98
Jul 07 21:11:21-351339 util-scheduler-8627 DEBUG Checking readiness of task: 574 / 0x4661f98
Jul 07 21:11:21-351531 util-scheduler-8627 DEBUG Checking readiness of task: 573 / 0x4661f98
Jul 07 21:11:21-351723 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-351911 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-352100 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-352291 util-scheduler-8627 DEBUG Running task: 573 / 0x4661f98
Jul 07 21:11:21-352476 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:21-352654 util-8627 DEBUG process_notify is running
Jul 07 21:11:21-352824 util-8627 DEBUG client_notify is running
Jul 07 21:11:21-353012 util-scheduler-8627 DEBUG Canceling task: 570 / 0x4e607e8
Jul 07 21:11:21-353257 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:21-353487 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:21-353733 cadet-p2p-8627 DEBUG Checking 0x51b7b90 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:21-353967 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:21-354144 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:21-354340 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:21-355738 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:21-355958 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:21-356165 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:21-357339 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:21-357555 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:21-357738 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:21-357932 util-scheduler-8627 DEBUG Canceling task: 567 / 0x4e61600
Jul 07 21:11:21-358153 util-scheduler-8627 DEBUG Adding task: 575 / 0x4e61600
Jul 07 21:11:21-358591 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:21-358766 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:21-358994 cadet-p2p-8627 DEBUG Checking 0x51be570 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:21-359238 cadet-p2p-8627 DEBUG Checking 0x51be570 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:21-359417 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:21-359624 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:21-359841 util-scheduler-8627 DEBUG Adding task: 576 / 0x4e607e8
Jul 07 21:11:21-360020 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:21-360196 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:21-360396 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:21-360584 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:21-360758 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:21-360996 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:21-361220 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:21-361401 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:21-361599 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:21-361804 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:21-361988 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:21-362191 util-scheduler-8627 DEBUG Adding task: 577 / 0x4e607e8
Jul 07 21:11:21-362409 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:21-362607 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:21-362812 util-scheduler-8627 DEBUG Adding task: 578 / 0x4661f98
Jul 07 21:11:21-363013 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:21-363269 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:21-363493 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:21-363750 util-scheduler-8627 DEBUG Checking readiness of task: 578 / 0x4661f98
Jul 07 21:11:21-363944 util-scheduler-8627 DEBUG Checking readiness of task: 574 / 0x4661f98
Jul 07 21:11:21-364137 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-364326 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-364516 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-364708 util-scheduler-8627 DEBUG Running task: 578 / 0x4661f98
Jul 07 21:11:21-364893 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:21-365069 util-8627 DEBUG process_notify is running
Jul 07 21:11:21-365323 util-8627 DEBUG client_notify is running
Jul 07 21:11:21-365503 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:21-365713 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:21-365901 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:21-366141 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:21-366346 util-scheduler-8627 DEBUG Running task: 576 / 0x4e607e8
Jul 07 21:11:21-366538 util-scheduler-8627 DEBUG Canceling task: 577 / 0x4e607e8
Jul 07 21:11:21-366750 util-scheduler-8627 DEBUG Adding task: 579 / 0x4e607e8
Jul 07 21:11:21-366965 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:21-367159 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:21-367356 util-scheduler-8627 DEBUG Adding task: 580 / 0x4661f98
Jul 07 21:11:21-367592 util-scheduler-8627 DEBUG Checking readiness of task: 580 / 0x4661f98
Jul 07 21:11:21-367784 util-scheduler-8627 DEBUG Checking readiness of task: 574 / 0x4661f98
Jul 07 21:11:21-367973 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-368161 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-368350 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-368539 util-scheduler-8627 DEBUG Running task: 580 / 0x4661f98
Jul 07 21:11:21-368723 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:21-368897 util-8627 DEBUG process_notify is running
Jul 07 21:11:21-369064 util-8627 DEBUG client_notify is running
Jul 07 21:11:21-369259 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:21-369449 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:21-369636 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:21-369875 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:21-603713 util-scheduler-8627 DEBUG Checking readiness of task: 574 / 0x4661f98
Jul 07 21:11:21-603953 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-604148 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-604341 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-604535 util-scheduler-8627 DEBUG Running task: 574 / 0x4661f98
Jul 07 21:11:21-604944 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:21-605180 util-scheduler-8627 DEBUG Adding task: 581 / 0x4662140
Jul 07 21:11:21-605457 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-605649 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-605838 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-606028 util-scheduler-8627 DEBUG Running task: 581 / 0x4662140
Jul 07 21:11:21-606218 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:21-606435 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:21-606655 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:21-606856 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:21-607055 util-scheduler-8627 DEBUG Adding task: 582 / 0x4661f98
Jul 07 21:11:21-607239 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:21-607443 util-scheduler-8627 DEBUG Adding task: 583 / 0x4661f98
Jul 07 21:11:21-607682 util-scheduler-8627 DEBUG Checking readiness of task: 583 / 0x4661f98
Jul 07 21:11:21-607872 util-scheduler-8627 DEBUG Checking readiness of task: 582 / 0x4661f98
Jul 07 21:11:21-608064 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:21-608253 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:21-608442 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:21-608633 util-scheduler-8627 DEBUG Running task: 582 / 0x4661f98
Jul 07 21:11:21-608817 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:21-608993 util-8627 DEBUG process_notify is running
Jul 07 21:11:21-609175 util-8627 DEBUG client_notify is running
Jul 07 21:11:21-609380 util-scheduler-8627 DEBUG Canceling task: 579 / 0x4e607e8
Jul 07 21:11:21-609601 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:21-609817 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:21-610049 cadet-p2p-8627 DEBUG Checking 0x51be570 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:21-610281 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:21-610458 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:21-610645 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:21-610925 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:21-611118 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:21-611296 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:21-611482 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:21-611669 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:21-611845 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:21-612029 util-scheduler-8627 DEBUG Canceling task: 575 / 0x4e61600
Jul 07 21:11:21-612237 util-scheduler-8627 DEBUG Adding task: 584 / 0x4e61600
Jul 07 21:11:21-612481 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:21-612649 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:21-612827 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:21-613025 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:21-613219 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:21-613394 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:21-613591 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:21-613795 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:21-613978 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:21-614156 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:21-614345 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:21-614590 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:23-310907 util-scheduler-8627 DEBUG Checking readiness of task: 583 / 0x4661f98
Jul 07 21:11:23-311240 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:23-312934 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:23-313140 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:23-313380 util-scheduler-8627 DEBUG Running task: 569 / 0x4d63d80
Jul 07 21:11:23-313621 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:23-313865 cadet-tun-8627 DEBUG  kx started 125 s ago
Jul 07 21:11:23-314074 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:23-314298 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:23-314500 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:23-314733 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:23-314912 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:23-315155 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:23-315443 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:23-315640 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:23-315878 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:23-316086 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:23-316401 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:23-316601 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:23-316825 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:23-317009 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:23-317185 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:23-317417 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:23-317633 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:23-317856 util-scheduler-8627 DEBUG Adding task: 585 / 0x4e607e8
Jul 07 21:11:23-318037 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:23-318239 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:23-318414 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:23-318587 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:23-318823 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:23-319019 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:23-319197 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:23-319396 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:23-319598 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:23-319907 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:23-320108 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:23-320283 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:23-320464 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:23-324002 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:23-324808 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:23-324988 cadet-tun-8627 DEBUG   e sending 2025607755
Jul 07 21:11:23-325223 cadet-tun-8627 DEBUG   e towards WHDY
Jul 07 21:11:23-325425 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:23-325624 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:23-325851 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:23-326030 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:23-326249 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:23-326523 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:23-326720 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:23-326954 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:23-327163 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:23-327624 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:23-327824 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:23-328047 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:23-328230 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:23-328415 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:23-328618 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:23-328819 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:23-328994 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:23-329167 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:23-329449 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:23-329646 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:23-329823 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:23-330056 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:23-330249 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:23-330425 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:23-330622 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:23-330870 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:23-331075 util-scheduler-8627 DEBUG Adding task: 586 / 0x4d63d80
Jul 07 21:11:23-331335 util-scheduler-8627 DEBUG Checking readiness of task: 583 / 0x4661f98
Jul 07 21:11:23-331529 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:23-331718 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:23-331907 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:23-332098 util-scheduler-8627 DEBUG Running task: 585 / 0x4e607e8
Jul 07 21:11:23-332305 util-scheduler-8627 DEBUG Adding task: 587 / 0x4e607e8
Jul 07 21:11:23-332525 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:23-332727 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:23-332935 util-scheduler-8627 DEBUG Adding task: 588 / 0x4661f98
Jul 07 21:11:23-333174 util-scheduler-8627 DEBUG Checking readiness of task: 588 / 0x4661f98
Jul 07 21:11:23-333392 util-scheduler-8627 DEBUG Checking readiness of task: 583 / 0x4661f98
Jul 07 21:11:23-333581 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:23-333770 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:23-333959 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:23-334150 util-scheduler-8627 DEBUG Running task: 588 / 0x4661f98
Jul 07 21:11:23-334336 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:23-334512 util-8627 DEBUG process_notify is running
Jul 07 21:11:23-334685 util-8627 DEBUG client_notify is running
Jul 07 21:11:23-334864 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:23-335059 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:23-335249 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:23-335503 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:25-325123 util-scheduler-8627 DEBUG Checking readiness of task: 583 / 0x4661f98
Jul 07 21:11:25-325536 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-325733 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-325925 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-326122 util-scheduler-8627 DEBUG Running task: 583 / 0x4661f98
Jul 07 21:11:25-326550 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:25-326820 util-scheduler-8627 DEBUG Adding task: 589 / 0x4662140
Jul 07 21:11:25-327127 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-327319 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-327510 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-327700 util-scheduler-8627 DEBUG Running task: 589 / 0x4662140
Jul 07 21:11:25-327892 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:25-328093 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:25-328325 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:25-328531 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:25-328738 util-scheduler-8627 DEBUG Adding task: 590 / 0x4661f98
Jul 07 21:11:25-328953 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:25-329161 util-scheduler-8627 DEBUG Adding task: 591 / 0x4661f98
Jul 07 21:11:25-329435 util-scheduler-8627 DEBUG Checking readiness of task: 591 / 0x4661f98
Jul 07 21:11:25-329628 util-scheduler-8627 DEBUG Checking readiness of task: 590 / 0x4661f98
Jul 07 21:11:25-329820 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-330010 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-330199 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-330391 util-scheduler-8627 DEBUG Running task: 590 / 0x4661f98
Jul 07 21:11:25-330577 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:25-330754 util-8627 DEBUG process_notify is running
Jul 07 21:11:25-330926 util-8627 DEBUG client_notify is running
Jul 07 21:11:25-331113 util-scheduler-8627 DEBUG Canceling task: 587 / 0x4e607e8
Jul 07 21:11:25-331336 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:25-331556 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:25-331796 cadet-p2p-8627 DEBUG Checking 0x51c3680 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:25-332030 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:25-332207 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:25-332398 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:25-332685 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:25-332880 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:25-333060 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:25-333273 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:25-333464 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:25-333642 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:25-333825 util-scheduler-8627 DEBUG Canceling task: 584 / 0x4e61600
Jul 07 21:11:25-334036 util-scheduler-8627 DEBUG Adding task: 592 / 0x4e61600
Jul 07 21:11:25-334286 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:25-334457 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:25-334676 cadet-p2p-8627 DEBUG Checking 0x51ca060 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:25-335221 cadet-p2p-8627 DEBUG Checking 0x51ca060 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:25-335435 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:25-335647 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:25-335933 util-scheduler-8627 DEBUG Adding task: 593 / 0x4e607e8
Jul 07 21:11:25-336122 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:25-336303 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:25-336506 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:25-336681 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:25-336910 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:25-337159 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:25-337387 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:25-337565 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:25-337764 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:25-338019 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:25-338206 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:25-338414 util-scheduler-8627 DEBUG Adding task: 594 / 0x4e607e8
Jul 07 21:11:25-338636 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:25-338839 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:25-339090 util-scheduler-8627 DEBUG Adding task: 595 / 0x4661f98
Jul 07 21:11:25-339296 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:25-339562 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:25-339795 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:25-340116 util-scheduler-8627 DEBUG Checking readiness of task: 595 / 0x4661f98
Jul 07 21:11:25-340317 util-scheduler-8627 DEBUG Checking readiness of task: 591 / 0x4661f98
Jul 07 21:11:25-340508 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-340698 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-340888 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-341124 util-scheduler-8627 DEBUG Running task: 595 / 0x4661f98
Jul 07 21:11:25-341338 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:25-341517 util-8627 DEBUG process_notify is running
Jul 07 21:11:25-341690 util-8627 DEBUG client_notify is running
Jul 07 21:11:25-341869 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:25-342067 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:25-342299 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:25-342542 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:25-342749 util-scheduler-8627 DEBUG Running task: 593 / 0x4e607e8
Jul 07 21:11:25-342943 util-scheduler-8627 DEBUG Canceling task: 594 / 0x4e607e8
Jul 07 21:11:25-343158 util-scheduler-8627 DEBUG Adding task: 596 / 0x4e607e8
Jul 07 21:11:25-343421 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:25-343618 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:25-343818 util-scheduler-8627 DEBUG Adding task: 597 / 0x4661f98
Jul 07 21:11:25-344057 util-scheduler-8627 DEBUG Checking readiness of task: 597 / 0x4661f98
Jul 07 21:11:25-344287 util-scheduler-8627 DEBUG Checking readiness of task: 591 / 0x4661f98
Jul 07 21:11:25-344485 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-344686 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-344876 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-345066 util-scheduler-8627 DEBUG Running task: 597 / 0x4661f98
Jul 07 21:11:25-345273 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:25-345494 util-8627 DEBUG process_notify is running
Jul 07 21:11:25-345728 util-8627 DEBUG client_notify is running
Jul 07 21:11:25-345908 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:25-346100 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:25-346288 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:25-346572 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:25-455782 util-scheduler-8627 DEBUG Checking readiness of task: 591 / 0x4661f98
Jul 07 21:11:25-456031 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-456226 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-456417 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-456611 util-scheduler-8627 DEBUG Running task: 591 / 0x4661f98
Jul 07 21:11:25-457030 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:25-457292 util-scheduler-8627 DEBUG Adding task: 598 / 0x4662140
Jul 07 21:11:25-457548 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-457739 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-457929 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-458121 util-scheduler-8627 DEBUG Running task: 598 / 0x4662140
Jul 07 21:11:25-458311 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:25-458753 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:25-458978 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:25-459180 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:25-459383 util-scheduler-8627 DEBUG Adding task: 599 / 0x4661f98
Jul 07 21:11:25-459568 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:25-459773 util-scheduler-8627 DEBUG Adding task: 600 / 0x4661f98
Jul 07 21:11:25-460015 util-scheduler-8627 DEBUG Checking readiness of task: 600 / 0x4661f98
Jul 07 21:11:25-460206 util-scheduler-8627 DEBUG Checking readiness of task: 599 / 0x4661f98
Jul 07 21:11:25-460397 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:25-460586 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:25-460775 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:25-460966 util-scheduler-8627 DEBUG Running task: 599 / 0x4661f98
Jul 07 21:11:25-461151 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:25-461350 util-8627 DEBUG process_notify is running
Jul 07 21:11:25-461520 util-8627 DEBUG client_notify is running
Jul 07 21:11:25-461705 util-scheduler-8627 DEBUG Canceling task: 596 / 0x4e607e8
Jul 07 21:11:25-461926 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:25-462144 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:25-462379 cadet-p2p-8627 DEBUG Checking 0x51ca060 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:25-462612 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:25-462790 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:25-462977 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:25-463260 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:25-463455 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:25-463633 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:25-463821 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:25-464027 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:25-464205 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:25-464390 util-scheduler-8627 DEBUG Canceling task: 592 / 0x4e61600
Jul 07 21:11:25-464601 util-scheduler-8627 DEBUG Adding task: 601 / 0x4e61600
Jul 07 21:11:25-464852 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:25-465021 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:25-465221 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:25-465421 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:25-465595 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:25-465768 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:25-465966 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:25-466169 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:25-466351 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:25-466528 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:25-466716 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:25-466965 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:28-334088 util-scheduler-8627 DEBUG Checking readiness of task: 600 / 0x4661f98
Jul 07 21:11:28-334454 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:28-336312 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:28-336599 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:28-336801 util-scheduler-8627 DEBUG Running task: 586 / 0x4d63d80
Jul 07 21:11:28-337118 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:28-337405 cadet-tun-8627 DEBUG  kx started 130 s ago
Jul 07 21:11:28-337615 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:28-337842 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:28-338045 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:28-338304 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:28-338484 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:28-338706 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:28-339001 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:28-339219 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:28-339459 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:28-339666 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:28-339984 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:28-340184 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:28-340451 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:28-340635 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:28-340810 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:28-341016 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:28-341251 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:28-341498 util-scheduler-8627 DEBUG Adding task: 602 / 0x4e607e8
Jul 07 21:11:28-341679 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:28-341882 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:28-342058 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:28-342232 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:28-342492 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:28-342688 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:28-342868 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:28-343067 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:28-343270 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:28-343601 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:28-343803 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:28-343973 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:28-344154 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:28-347863 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:28-349226 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:28-349411 cadet-tun-8627 DEBUG   e sending 4262981391
Jul 07 21:11:28-349619 cadet-tun-8627 DEBUG   e towards AHMJ
Jul 07 21:11:28-349822 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:28-350042 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:28-350271 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:28-350449 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:28-350668 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:28-350965 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:28-351165 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:28-351400 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:28-351607 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:28-351927 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:28-352148 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:28-352371 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:28-352553 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:28-352728 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:28-352931 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:28-353154 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:28-353351 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:28-353525 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:28-353761 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:28-353981 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:28-354327 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:28-354567 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:28-354761 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:28-354938 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:28-355144 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:28-355416 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:28-355624 util-scheduler-8627 DEBUG Adding task: 603 / 0x4d63d80
Jul 07 21:11:28-355887 util-scheduler-8627 DEBUG Checking readiness of task: 600 / 0x4661f98
Jul 07 21:11:28-356081 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:28-356292 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:28-356483 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:28-356674 util-scheduler-8627 DEBUG Running task: 602 / 0x4e607e8
Jul 07 21:11:28-356882 util-scheduler-8627 DEBUG Adding task: 604 / 0x4e607e8
Jul 07 21:11:28-357103 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:28-357349 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:28-357559 util-scheduler-8627 DEBUG Adding task: 605 / 0x4661f98
Jul 07 21:11:28-357799 util-scheduler-8627 DEBUG Checking readiness of task: 605 / 0x4661f98
Jul 07 21:11:28-357992 util-scheduler-8627 DEBUG Checking readiness of task: 600 / 0x4661f98
Jul 07 21:11:28-358182 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:28-358383 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:28-358583 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:28-358774 util-scheduler-8627 DEBUG Running task: 605 / 0x4661f98
Jul 07 21:11:28-358963 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:28-359140 util-8627 DEBUG process_notify is running
Jul 07 21:11:28-359312 util-8627 DEBUG client_notify is running
Jul 07 21:11:28-359520 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:28-359754 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:28-359947 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:28-360201 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:29-309049 util-scheduler-8627 DEBUG Checking readiness of task: 600 / 0x4661f98
Jul 07 21:11:29-309400 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-309596 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-309789 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-309985 util-scheduler-8627 DEBUG Running task: 600 / 0x4661f98
Jul 07 21:11:29-310417 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:29-310668 util-scheduler-8627 DEBUG Adding task: 606 / 0x4662140
Jul 07 21:11:29-310935 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-311127 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-311317 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-311507 util-scheduler-8627 DEBUG Running task: 606 / 0x4662140
Jul 07 21:11:29-311698 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:29-311897 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:29-312124 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:29-312329 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:29-312534 util-scheduler-8627 DEBUG Adding task: 607 / 0x4661f98
Jul 07 21:11:29-312745 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:29-312952 util-scheduler-8627 DEBUG Adding task: 608 / 0x4661f98
Jul 07 21:11:29-313217 util-scheduler-8627 DEBUG Checking readiness of task: 608 / 0x4661f98
Jul 07 21:11:29-313413 util-scheduler-8627 DEBUG Checking readiness of task: 607 / 0x4661f98
Jul 07 21:11:29-313606 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-313814 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-314004 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-314197 util-scheduler-8627 DEBUG Running task: 607 / 0x4661f98
Jul 07 21:11:29-314382 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:29-314558 util-8627 DEBUG process_notify is running
Jul 07 21:11:29-314730 util-8627 DEBUG client_notify is running
Jul 07 21:11:29-314915 util-scheduler-8627 DEBUG Canceling task: 604 / 0x4e607e8
Jul 07 21:11:29-315138 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:29-315357 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:29-315594 cadet-p2p-8627 DEBUG Checking 0x51cf170 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:29-315829 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:29-316007 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:29-316196 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:29-316482 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:29-316677 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:29-316856 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:29-317044 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:29-317252 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:29-317431 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:29-317614 util-scheduler-8627 DEBUG Canceling task: 601 / 0x4e61600
Jul 07 21:11:29-317825 util-scheduler-8627 DEBUG Adding task: 609 / 0x4e61600
Jul 07 21:11:29-318074 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:29-318244 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:29-318465 cadet-p2p-8627 DEBUG Checking 0x51d5b50 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:29-318702 cadet-p2p-8627 DEBUG Checking 0x51d5b50 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:29-318880 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:29-319088 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:29-319300 util-scheduler-8627 DEBUG Adding task: 610 / 0x4e607e8
Jul 07 21:11:29-319479 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:29-319654 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:29-319852 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:29-320026 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:29-320200 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:29-320436 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:29-320631 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:29-320809 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:29-321007 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:29-321231 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:29-321416 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:29-321633 util-scheduler-8627 DEBUG Adding task: 611 / 0x4e607e8
Jul 07 21:11:29-321851 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:29-322045 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:29-322245 util-scheduler-8627 DEBUG Adding task: 612 / 0x4661f98
Jul 07 21:11:29-322480 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:29-322729 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:29-322944 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:29-323187 util-scheduler-8627 DEBUG Checking readiness of task: 612 / 0x4661f98
Jul 07 21:11:29-323380 util-scheduler-8627 DEBUG Checking readiness of task: 608 / 0x4661f98
Jul 07 21:11:29-323570 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-323759 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-323948 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-324139 util-scheduler-8627 DEBUG Running task: 612 / 0x4661f98
Jul 07 21:11:29-324323 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:29-324497 util-8627 DEBUG process_notify is running
Jul 07 21:11:29-324666 util-8627 DEBUG client_notify is running
Jul 07 21:11:29-324844 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:29-325038 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:29-325247 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:29-325488 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:29-325694 util-scheduler-8627 DEBUG Running task: 610 / 0x4e607e8
Jul 07 21:11:29-325885 util-scheduler-8627 DEBUG Canceling task: 611 / 0x4e607e8
Jul 07 21:11:29-326095 util-scheduler-8627 DEBUG Adding task: 613 / 0x4e607e8
Jul 07 21:11:29-326310 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:29-326503 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:29-326701 util-scheduler-8627 DEBUG Adding task: 614 / 0x4661f98
Jul 07 21:11:29-326936 util-scheduler-8627 DEBUG Checking readiness of task: 614 / 0x4661f98
Jul 07 21:11:29-327127 util-scheduler-8627 DEBUG Checking readiness of task: 608 / 0x4661f98
Jul 07 21:11:29-327315 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-327504 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-327693 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-327882 util-scheduler-8627 DEBUG Running task: 614 / 0x4661f98
Jul 07 21:11:29-328065 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:29-328238 util-8627 DEBUG process_notify is running
Jul 07 21:11:29-328406 util-8627 DEBUG client_notify is running
Jul 07 21:11:29-328581 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:29-328769 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:29-328955 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:29-329217 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:29-439315 util-scheduler-8627 DEBUG Checking readiness of task: 608 / 0x4661f98
Jul 07 21:11:29-439542 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-439736 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-439927 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-440120 util-scheduler-8627 DEBUG Running task: 608 / 0x4661f98
Jul 07 21:11:29-440525 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:29-440754 util-scheduler-8627 DEBUG Adding task: 615 / 0x4662140
Jul 07 21:11:29-441003 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-441220 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-441426 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-441616 util-scheduler-8627 DEBUG Running task: 615 / 0x4662140
Jul 07 21:11:29-441805 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:29-442016 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:29-442232 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:29-442430 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:29-442629 util-scheduler-8627 DEBUG Adding task: 616 / 0x4661f98
Jul 07 21:11:29-442812 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:29-443013 util-scheduler-8627 DEBUG Adding task: 617 / 0x4661f98
Jul 07 21:11:29-443251 util-scheduler-8627 DEBUG Checking readiness of task: 617 / 0x4661f98
Jul 07 21:11:29-443441 util-scheduler-8627 DEBUG Checking readiness of task: 616 / 0x4661f98
Jul 07 21:11:29-443632 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:29-443822 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:29-444011 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:29-444201 util-scheduler-8627 DEBUG Running task: 616 / 0x4661f98
Jul 07 21:11:29-444385 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:29-444560 util-8627 DEBUG process_notify is running
Jul 07 21:11:29-444729 util-8627 DEBUG client_notify is running
Jul 07 21:11:29-444912 util-scheduler-8627 DEBUG Canceling task: 613 / 0x4e607e8
Jul 07 21:11:29-445129 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:29-445369 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:29-445602 cadet-p2p-8627 DEBUG Checking 0x51d5b50 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:29-445831 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:29-446010 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:29-446195 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:29-446474 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:29-446668 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:29-446843 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:29-447029 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:29-447215 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:29-447391 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:29-447574 util-scheduler-8627 DEBUG Canceling task: 609 / 0x4e61600
Jul 07 21:11:29-447783 util-scheduler-8627 DEBUG Adding task: 618 / 0x4e61600
Jul 07 21:11:29-448025 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:29-448194 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:29-448371 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:29-448568 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:29-448742 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:29-448914 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:29-449112 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:29-449337 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:29-449521 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:29-449698 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:29-449896 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:29-450139 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:32-706430 util-scheduler-8627 DEBUG Checking readiness of task: 617 / 0x4661f98
Jul 07 21:11:32-706780 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:32-706976 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:32-707169 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:32-707365 util-scheduler-8627 DEBUG Running task: 617 / 0x4661f98
Jul 07 21:11:32-707787 util-8627 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:32-708038 util-scheduler-8627 DEBUG Adding task: 619 / 0x4662140
Jul 07 21:11:32-708337 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:32-708530 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:32-708721 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:32-708910 util-scheduler-8627 DEBUG Running task: 619 / 0x4662140
Jul 07 21:11:32-709100 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:32-709328 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:32-709558 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:32-709821 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:32-710076 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:32-710308 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:32-710515 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:32-710763 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:32-710971 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:32-711158 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:32-711344 util-scheduler-8627 DEBUG Canceling task: 498 / 0x4e61600
Jul 07 21:11:32-711567 util-scheduler-8627 DEBUG Adding task: 620 / 0x4e61600
Jul 07 21:11:32-711746 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:32-712003 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:32-712216 util-scheduler-8627 DEBUG Adding task: 621 / 0x4d50e20
Jul 07 21:11:32-712397 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:32-712771 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:33-321312 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:33-321713 util-scheduler-8627 DEBUG Adding task: 622 / 0x4661f98
Jul 07 21:11:33-322009 util-scheduler-8627 DEBUG Checking readiness of task: 622 / 0x4661f98
Jul 07 21:11:33-322208 util-scheduler-8627 DEBUG Checking readiness of task: 621 / 0x4d50e20
Jul 07 21:11:33-322401 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-322591 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-322781 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-322976 util-scheduler-8627 DEBUG Running task: 621 / 0x4d50e20
Jul 07 21:11:33-323204 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:33-323385 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-323559 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-323798 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:33-324064 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:33-355741 util-scheduler-8627 DEBUG Checking readiness of task: 622 / 0x4661f98
Jul 07 21:11:33-355966 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-356961 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-357313 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-357512 util-scheduler-8627 DEBUG Running task: 603 / 0x4d63d80
Jul 07 21:11:33-357773 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:33-358018 cadet-tun-8627 DEBUG  kx started 135 s ago
Jul 07 21:11:33-358228 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:33-358430 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:33-358633 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:33-358868 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:33-359049 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:33-359271 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:33-359563 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:33-359760 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:33-359999 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:33-360235 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:33-360551 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:33-360752 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:33-360977 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-361160 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:33-361365 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:33-361575 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:33-361790 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:33-362016 util-scheduler-8627 DEBUG Adding task: 623 / 0x4e607e8
Jul 07 21:11:33-362198 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:33-362403 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:33-362578 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:33-362752 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:33-362989 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-363184 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:33-363362 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:33-363561 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:33-363774 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:33-364081 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:33-364282 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:33-364452 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:33-364634 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:33-368194 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:33-368998 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:33-369177 cadet-tun-8627 DEBUG   e sending 1988458909
Jul 07 21:11:33-369420 cadet-tun-8627 DEBUG   e towards WYZK
Jul 07 21:11:33-369620 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:33-369818 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:33-370047 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:33-370225 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:33-370444 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:33-370718 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:33-370923 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:33-371158 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:33-371365 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:33-371671 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:33-371868 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:33-372090 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-372273 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:33-372448 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:33-372650 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:33-372851 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:33-373026 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:33-373224 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:33-373464 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-373658 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:33-373836 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:33-374068 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-374260 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:33-374438 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:33-374636 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:33-374882 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:33-375104 util-scheduler-8627 DEBUG Adding task: 624 / 0x4d63d80
Jul 07 21:11:33-375370 util-scheduler-8627 DEBUG Checking readiness of task: 622 / 0x4661f98
Jul 07 21:11:33-375562 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-375751 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-375939 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-376129 util-scheduler-8627 DEBUG Running task: 623 / 0x4e607e8
Jul 07 21:11:33-376338 util-scheduler-8627 DEBUG Adding task: 625 / 0x4e607e8
Jul 07 21:11:33-376558 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:33-376760 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:33-376971 util-scheduler-8627 DEBUG Adding task: 626 / 0x4661f98
Jul 07 21:11:33-377237 util-scheduler-8627 DEBUG Checking readiness of task: 626 / 0x4661f98
Jul 07 21:11:33-377432 util-scheduler-8627 DEBUG Checking readiness of task: 622 / 0x4661f98
Jul 07 21:11:33-377622 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-377811 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-378000 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-378201 util-scheduler-8627 DEBUG Running task: 626 / 0x4661f98
Jul 07 21:11:33-378387 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:33-378565 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-378736 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-378914 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:33-379110 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:33-379301 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:33-379562 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:33-427980 util-scheduler-8627 DEBUG Checking readiness of task: 622 / 0x4661f98
Jul 07 21:11:33-428210 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-428405 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-428597 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-428790 util-scheduler-8627 DEBUG Running task: 622 / 0x4661f98
Jul 07 21:11:33-429230 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:33-429472 util-scheduler-8627 DEBUG Adding task: 627 / 0x4662140
Jul 07 21:11:33-429724 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-429915 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-430105 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-430294 util-scheduler-8627 DEBUG Running task: 627 / 0x4662140
Jul 07 21:11:33-430486 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:33-430682 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:33-430900 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:33-431100 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:33-431301 util-scheduler-8627 DEBUG Adding task: 628 / 0x4661f98
Jul 07 21:11:33-431485 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:33-431689 util-scheduler-8627 DEBUG Adding task: 629 / 0x4661f98
Jul 07 21:11:33-431927 util-scheduler-8627 DEBUG Checking readiness of task: 629 / 0x4661f98
Jul 07 21:11:33-432117 util-scheduler-8627 DEBUG Checking readiness of task: 628 / 0x4661f98
Jul 07 21:11:33-432308 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-432497 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-432686 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-432895 util-scheduler-8627 DEBUG Running task: 628 / 0x4661f98
Jul 07 21:11:33-433079 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:33-433281 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-433452 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-433636 util-scheduler-8627 DEBUG Canceling task: 625 / 0x4e607e8
Jul 07 21:11:33-433859 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:33-434076 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:33-434309 cadet-p2p-8627 DEBUG Checking 0x541da88 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:33-434542 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:33-434719 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:33-434907 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:33-435194 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:33-435389 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:33-435568 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:33-435755 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:33-435945 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:33-436123 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:33-436320 util-scheduler-8627 DEBUG Canceling task: 618 / 0x4e61600
Jul 07 21:11:33-436531 util-scheduler-8627 DEBUG Adding task: 630 / 0x4e61600
Jul 07 21:11:33-436777 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:33-436951 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:33-437172 cadet-p2p-8627 DEBUG Checking 0x5424468 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:33-437449 cadet-p2p-8627 DEBUG Checking 0x5424468 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:33-437627 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:33-437832 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:33-438043 util-scheduler-8627 DEBUG Adding task: 631 / 0x4e607e8
Jul 07 21:11:33-438221 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:33-438397 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:33-438595 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:33-438769 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:33-438942 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:33-439179 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:33-439373 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:33-439550 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:33-439747 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:33-439952 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:33-440135 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:33-440336 util-scheduler-8627 DEBUG Adding task: 632 / 0x4e607e8
Jul 07 21:11:33-440549 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:33-440743 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:33-440942 util-scheduler-8627 DEBUG Adding task: 633 / 0x4661f98
Jul 07 21:11:33-441141 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:33-441416 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:33-441613 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:33-441854 util-scheduler-8627 DEBUG Checking readiness of task: 633 / 0x4661f98
Jul 07 21:11:33-442046 util-scheduler-8627 DEBUG Checking readiness of task: 629 / 0x4661f98
Jul 07 21:11:33-442235 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-442425 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-442613 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-442819 util-scheduler-8627 DEBUG Running task: 633 / 0x4661f98
Jul 07 21:11:33-443003 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:33-443176 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-443347 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-443523 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:33-443714 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:33-443900 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:33-444142 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:33-444347 util-scheduler-8627 DEBUG Running task: 631 / 0x4e607e8
Jul 07 21:11:33-444552 util-scheduler-8627 DEBUG Canceling task: 632 / 0x4e607e8
Jul 07 21:11:33-444763 util-scheduler-8627 DEBUG Adding task: 634 / 0x4e607e8
Jul 07 21:11:33-444977 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:33-445170 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:33-445393 util-scheduler-8627 DEBUG Adding task: 635 / 0x4661f98
Jul 07 21:11:33-445630 util-scheduler-8627 DEBUG Checking readiness of task: 635 / 0x4661f98
Jul 07 21:11:33-445821 util-scheduler-8627 DEBUG Checking readiness of task: 629 / 0x4661f98
Jul 07 21:11:33-446010 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-446199 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-446387 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-446578 util-scheduler-8627 DEBUG Running task: 635 / 0x4661f98
Jul 07 21:11:33-446761 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:33-446938 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-447106 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-447280 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:33-447469 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:33-447654 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:33-447897 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:33-558023 util-scheduler-8627 DEBUG Checking readiness of task: 629 / 0x4661f98
Jul 07 21:11:33-558321 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-558518 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-558710 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-558906 util-scheduler-8627 DEBUG Running task: 629 / 0x4661f98
Jul 07 21:11:33-559329 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:33-559580 util-scheduler-8627 DEBUG Adding task: 636 / 0x4662140
Jul 07 21:11:33-559846 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-560038 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-560228 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-560418 util-scheduler-8627 DEBUG Running task: 636 / 0x4662140
Jul 07 21:11:33-560609 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:33-560809 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:33-561041 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:33-561270 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:33-561477 util-scheduler-8627 DEBUG Adding task: 637 / 0x4661f98
Jul 07 21:11:33-561663 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:33-561866 util-scheduler-8627 DEBUG Adding task: 638 / 0x4661f98
Jul 07 21:11:33-562105 util-scheduler-8627 DEBUG Checking readiness of task: 638 / 0x4661f98
Jul 07 21:11:33-562324 util-scheduler-8627 DEBUG Checking readiness of task: 637 / 0x4661f98
Jul 07 21:11:33-562516 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:33-562706 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:33-562895 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:33-563086 util-scheduler-8627 DEBUG Running task: 637 / 0x4661f98
Jul 07 21:11:33-563270 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:33-563445 util-8627 DEBUG process_notify is running
Jul 07 21:11:33-563616 util-8627 DEBUG client_notify is running
Jul 07 21:11:33-563803 util-scheduler-8627 DEBUG Canceling task: 634 / 0x4e607e8
Jul 07 21:11:33-564048 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:33-564268 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:33-564508 cadet-p2p-8627 DEBUG Checking 0x5424468 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:33-564741 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:33-564954 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:33-565147 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:33-565454 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:33-565649 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:33-565829 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:33-566016 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:33-566205 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:33-566382 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:33-566568 util-scheduler-8627 DEBUG Canceling task: 630 / 0x4e61600
Jul 07 21:11:33-566779 util-scheduler-8627 DEBUG Adding task: 639 / 0x4e61600
Jul 07 21:11:33-567031 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:33-567201 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:33-567382 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:33-567580 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:33-567755 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:33-567928 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:33-568127 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:33-568332 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:33-568515 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:33-568693 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:33-569106 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:33-569381 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:36-146410 util-scheduler-8627 DEBUG Checking readiness of task: 638 / 0x4661f98
Jul 07 21:11:36-146780 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-146976 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-147168 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-147365 util-scheduler-8627 DEBUG Running task: 638 / 0x4661f98
Jul 07 21:11:36-147788 util-8627 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:36-148043 util-scheduler-8627 DEBUG Adding task: 640 / 0x4662140
Jul 07 21:11:36-148318 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-148509 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-148699 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-148888 util-scheduler-8627 DEBUG Running task: 640 / 0x4662140
Jul 07 21:11:36-149079 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:36-149310 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:36-149569 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:36-149835 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:36-150077 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:36-150308 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:36-150537 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:36-150784 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:36-150992 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:36-151178 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:36-151364 util-scheduler-8627 DEBUG Canceling task: 620 / 0x4e61600
Jul 07 21:11:36-151587 util-scheduler-8627 DEBUG Adding task: 641 / 0x4e61600
Jul 07 21:11:36-151769 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:36-152025 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:36-152241 util-scheduler-8627 DEBUG Adding task: 642 / 0x4d50e20
Jul 07 21:11:36-152422 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:36-152792 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:36-153147 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:36-153349 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:36-153518 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:36-157084 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:36-158480 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:36-158828 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:36-159222 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:36-159401 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:36-159589 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:36-162778 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:36-163380 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:36-163662 cadet-tun-8627 DEBUG   e sending 552871903
Jul 07 21:11:36-163876 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:36-164079 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:36-164309 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:36-164490 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:36-164711 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:36-164989 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:36-165208 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:36-165447 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:36-165672 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:36-165985 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:36-166185 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:36-166409 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:36-166592 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:36-166768 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:36-166974 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 48 bytes
Jul 07 21:11:36-167218 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:36-167447 util-scheduler-8627 DEBUG Adding task: 643 / 0x4e607e8
Jul 07 21:11:36-167629 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:36-167833 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:36-168008 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:36-168182 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:36-168418 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:36-168614 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:36-168792 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:36-168991 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:36-169173 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:36-169407 util-scheduler-8627 DEBUG Adding task: 644 / 0x4661f98
Jul 07 21:11:36-169730 util-scheduler-8627 DEBUG Checking readiness of task: 644 / 0x4661f98
Jul 07 21:11:36-169927 util-scheduler-8627 DEBUG Checking readiness of task: 642 / 0x4d50e20
Jul 07 21:11:36-170120 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-170311 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-170500 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-170694 util-scheduler-8627 DEBUG Running task: 642 / 0x4d50e20
Jul 07 21:11:36-170881 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:36-171058 util-8627 DEBUG process_notify is running
Jul 07 21:11:36-171231 util-8627 DEBUG client_notify is running
Jul 07 21:11:36-171460 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:36-171730 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:36-171941 util-scheduler-8627 DEBUG Running task: 643 / 0x4e607e8
Jul 07 21:11:36-172150 util-scheduler-8627 DEBUG Adding task: 645 / 0x4e607e8
Jul 07 21:11:36-172371 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:36-172653 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:36-172854 util-scheduler-8627 DEBUG Adding task: 646 / 0x4661f98
Jul 07 21:11:36-173095 util-scheduler-8627 DEBUG Checking readiness of task: 646 / 0x4661f98
Jul 07 21:11:36-173333 util-scheduler-8627 DEBUG Checking readiness of task: 644 / 0x4661f98
Jul 07 21:11:36-173524 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-173713 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-173902 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-174093 util-scheduler-8627 DEBUG Running task: 646 / 0x4661f98
Jul 07 21:11:36-174276 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:36-174451 util-8627 DEBUG process_notify is running
Jul 07 21:11:36-174619 util-8627 DEBUG client_notify is running
Jul 07 21:11:36-174798 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:36-174992 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:36-175179 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:36-175423 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:36-699212 util-scheduler-8627 DEBUG Checking readiness of task: 644 / 0x4661f98
Jul 07 21:11:36-699553 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-699749 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-699941 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-700137 util-scheduler-8627 DEBUG Running task: 644 / 0x4661f98
Jul 07 21:11:36-700560 util-8627 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:36-700811 util-scheduler-8627 DEBUG Adding task: 647 / 0x4662140
Jul 07 21:11:36-701086 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:36-701329 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:36-701522 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:36-701713 util-scheduler-8627 DEBUG Running task: 647 / 0x4662140
Jul 07 21:11:36-701906 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:36-702108 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:36-702337 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:36-702599 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:36-702840 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:36-703100 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:36-703310 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:36-703557 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:36-703767 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:36-703955 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:36-704140 util-scheduler-8627 DEBUG Canceling task: 641 / 0x4e61600
Jul 07 21:11:36-704362 util-scheduler-8627 DEBUG Adding task: 648 / 0x4e61600
Jul 07 21:11:36-704540 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:36-704795 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:36-705008 util-scheduler-8627 DEBUG Adding task: 649 / 0x4d50e20
Jul 07 21:11:36-705269 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:36-705473 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:37-310856 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:37-311232 util-scheduler-8627 DEBUG Adding task: 650 / 0x4661f98
Jul 07 21:11:37-311521 util-scheduler-8627 DEBUG Checking readiness of task: 650 / 0x4661f98
Jul 07 21:11:37-311721 util-scheduler-8627 DEBUG Checking readiness of task: 649 / 0x4d50e20
Jul 07 21:11:37-311914 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:37-312104 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:37-312294 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:37-312489 util-scheduler-8627 DEBUG Running task: 649 / 0x4d50e20
Jul 07 21:11:37-312685 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:37-312865 util-8627 DEBUG process_notify is running
Jul 07 21:11:37-313038 util-8627 DEBUG client_notify is running
Jul 07 21:11:37-313298 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:37-313569 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:37-313782 util-scheduler-8627 DEBUG Running task: 650 / 0x4661f98
Jul 07 21:11:37-314194 util-8627 DEBUG receive_ready read 464/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:37-314467 util-scheduler-8627 DEBUG Adding task: 651 / 0x4662140
Jul 07 21:11:37-314718 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:37-314909 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:37-315099 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:37-315289 util-scheduler-8627 DEBUG Running task: 651 / 0x4662140
Jul 07 21:11:37-315480 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:37-315679 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:37-315905 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:37-316165 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:37-316403 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:37-316632 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-316841 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:37-317098 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-317334 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:37-317520 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:37-317706 util-scheduler-8627 DEBUG Canceling task: 648 / 0x4e61600
Jul 07 21:11:37-317930 util-scheduler-8627 DEBUG Adding task: 652 / 0x4e61600
Jul 07 21:11:37-318109 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:37-318357 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:37-318566 util-scheduler-8627 DEBUG Adding task: 653 / 0x4d50e20
Jul 07 21:11:37-318747 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:37-318943 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:37-319129 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:37-319327 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:37-319494 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:37-322969 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:37-323817 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:37-324033 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:37-324328 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:37-324503 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:37-324688 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:37-327819 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:37-328420 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:37-328598 cadet-tun-8627 DEBUG   e sending 493838224
Jul 07 21:11:37-328805 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:37-329005 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:37-329258 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:37-329441 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:37-329660 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:37-329940 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:37-330140 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:37-330374 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-330580 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:37-330888 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:37-331086 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:37-331310 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-331492 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:37-331667 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:37-331870 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:37-332072 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:37-332247 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:37-332421 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:37-332657 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-332851 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:37-333029 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:37-333287 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-333481 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:37-333667 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:37-333865 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:37-334084 util-scheduler-8627 DEBUG Adding task: 654 / 0x4662140
Jul 07 21:11:37-334351 util-scheduler-8627 DEBUG Checking readiness of task: 653 / 0x4d50e20
Jul 07 21:11:37-334546 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:37-334736 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:37-334924 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:37-335117 util-scheduler-8627 DEBUG Running task: 653 / 0x4d50e20
Jul 07 21:11:37-335301 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:37-335478 util-8627 DEBUG process_notify is running
Jul 07 21:11:37-335649 util-8627 DEBUG client_notify is running
Jul 07 21:11:37-335870 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:37-336130 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:37-336340 util-scheduler-8627 DEBUG Running task: 654 / 0x4662140
Jul 07 21:11:37-336530 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:37-336729 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:37-336944 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:37-337216 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:37-337474 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:37-337703 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-337913 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:37-338154 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-338360 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:37-338545 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:37-338729 util-scheduler-8627 DEBUG Canceling task: 652 / 0x4e61600
Jul 07 21:11:37-338948 util-scheduler-8627 DEBUG Adding task: 655 / 0x4e61600
Jul 07 21:11:37-339126 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:37-339366 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:37-339575 util-scheduler-8627 DEBUG Adding task: 656 / 0x4d50e20
Jul 07 21:11:37-339755 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:37-339952 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:37-945336 util-scheduler-8627 DEBUG Adding task: 657 / 0x4662140
Jul 07 21:11:37-945752 util-scheduler-8627 DEBUG Checking readiness of task: 656 / 0x4d50e20
Jul 07 21:11:37-945952 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:37-946146 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:37-946338 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:37-946534 util-scheduler-8627 DEBUG Running task: 656 / 0x4d50e20
Jul 07 21:11:37-946721 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:37-946901 util-8627 DEBUG process_notify is running
Jul 07 21:11:37-947074 util-8627 DEBUG client_notify is running
Jul 07 21:11:37-947306 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:37-947576 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:37-947786 util-scheduler-8627 DEBUG Running task: 657 / 0x4662140
Jul 07 21:11:37-947979 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:37-948177 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:37-948404 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:37-948671 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:37-948910 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:37-949139 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-949373 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:37-949620 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-949827 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:37-950012 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:37-950198 util-scheduler-8627 DEBUG Canceling task: 655 / 0x4e61600
Jul 07 21:11:37-950418 util-scheduler-8627 DEBUG Adding task: 658 / 0x4e61600
Jul 07 21:11:37-950597 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:37-950844 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:37-951058 util-scheduler-8627 DEBUG Adding task: 659 / 0x4d50e20
Jul 07 21:11:37-951240 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:37-951436 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:37-951623 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:37-951796 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:37-951962 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:37-955423 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:37-956252 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:37-956468 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:37-956758 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:37-956932 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:37-957117 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:37-960241 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:37-961359 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:37-961568 cadet-tun-8627 DEBUG   e sending 3911260934
Jul 07 21:11:37-961776 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:37-961977 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:37-962205 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:37-962383 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:37-962602 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:37-962889 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:37-963088 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:37-963322 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:37-963528 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:37-963836 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:37-964034 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:37-964256 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-964439 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:37-964614 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:37-964815 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:37-965016 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:37-965214 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:37-965391 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:37-965628 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-965822 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:37-966000 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:37-966244 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-966437 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:37-966614 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:37-966845 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:37-967037 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:37-967213 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:37-967410 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:37-967592 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:37-967805 util-scheduler-8627 DEBUG Adding task: 660 / 0x4661f98
Jul 07 21:11:37-968078 util-scheduler-8627 DEBUG Checking readiness of task: 660 / 0x4661f98
Jul 07 21:11:37-968272 util-scheduler-8627 DEBUG Checking readiness of task: 659 / 0x4d50e20
Jul 07 21:11:37-968465 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:37-968653 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:37-968842 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:37-969035 util-scheduler-8627 DEBUG Running task: 659 / 0x4d50e20
Jul 07 21:11:37-969243 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:37-969421 util-8627 DEBUG process_notify is running
Jul 07 21:11:37-969591 util-8627 DEBUG client_notify is running
Jul 07 21:11:37-969813 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:37-970072 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:38-143867 util-scheduler-8627 DEBUG Checking readiness of task: 660 / 0x4661f98
Jul 07 21:11:38-144132 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-144326 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-144531 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-144725 util-scheduler-8627 DEBUG Running task: 660 / 0x4661f98
Jul 07 21:11:38-145137 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:38-145437 util-scheduler-8627 DEBUG Adding task: 661 / 0x4662140
Jul 07 21:11:38-145697 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-145889 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-146078 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-146268 util-scheduler-8627 DEBUG Running task: 661 / 0x4662140
Jul 07 21:11:38-146459 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:38-146654 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:38-146874 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:38-147080 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-147282 util-scheduler-8627 DEBUG Adding task: 662 / 0x4661f98
Jul 07 21:11:38-147467 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:38-147666 util-scheduler-8627 DEBUG Adding task: 663 / 0x4661f98
Jul 07 21:11:38-147904 util-scheduler-8627 DEBUG Checking readiness of task: 663 / 0x4661f98
Jul 07 21:11:38-148097 util-scheduler-8627 DEBUG Checking readiness of task: 662 / 0x4661f98
Jul 07 21:11:38-148287 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-148476 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-148664 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-148853 util-scheduler-8627 DEBUG Running task: 662 / 0x4661f98
Jul 07 21:11:38-149036 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-149234 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-149406 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-149591 util-scheduler-8627 DEBUG Canceling task: 645 / 0x4e607e8
Jul 07 21:11:38-149812 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:11:38-150030 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:38-150265 cadet-p2p-8627 DEBUG Checking 0x5435348 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-150496 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:38-150674 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:11:38-150861 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:38-151146 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:11:38-151340 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:38-151519 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:38-151706 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:38-151895 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:38-152072 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:38-152256 util-scheduler-8627 DEBUG Canceling task: 639 / 0x4e61600
Jul 07 21:11:38-152466 util-scheduler-8627 DEBUG Adding task: 664 / 0x4e61600
Jul 07 21:11:38-152717 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:38-152887 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:38-153106 cadet-p2p-8627 DEBUG Checking 0x5685bd0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-153371 cadet-p2p-8627 DEBUG Checking 0x5685bd0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-153560 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:38-153766 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:38-153978 util-scheduler-8627 DEBUG Adding task: 665 / 0x4e607e8
Jul 07 21:11:38-154157 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:38-154332 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:11:38-154529 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:38-154703 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:38-154876 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:38-155111 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-155304 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:38-155482 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:38-155729 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-155922 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:38-156098 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:38-156294 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:38-156499 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:11:38-156681 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:11:38-156884 util-scheduler-8627 DEBUG Adding task: 666 / 0x4e607e8
Jul 07 21:11:38-157102 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-157323 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-157523 util-scheduler-8627 DEBUG Adding task: 667 / 0x4661f98
Jul 07 21:11:38-157721 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:11:38-157971 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-158172 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:38-158413 util-scheduler-8627 DEBUG Checking readiness of task: 667 / 0x4661f98
Jul 07 21:11:38-158605 util-scheduler-8627 DEBUG Checking readiness of task: 663 / 0x4661f98
Jul 07 21:11:38-158794 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-158983 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-159172 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-159363 util-scheduler-8627 DEBUG Running task: 667 / 0x4661f98
Jul 07 21:11:38-159547 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-159721 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-159890 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-160067 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-160262 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-160451 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-160693 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-160899 util-scheduler-8627 DEBUG Running task: 665 / 0x4e607e8
Jul 07 21:11:38-161102 util-scheduler-8627 DEBUG Canceling task: 666 / 0x4e607e8
Jul 07 21:11:38-161359 util-scheduler-8627 DEBUG Adding task: 668 / 0x4e607e8
Jul 07 21:11:38-161586 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-161781 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-161980 util-scheduler-8627 DEBUG Adding task: 669 / 0x4661f98
Jul 07 21:11:38-162216 util-scheduler-8627 DEBUG Checking readiness of task: 669 / 0x4661f98
Jul 07 21:11:38-162407 util-scheduler-8627 DEBUG Checking readiness of task: 663 / 0x4661f98
Jul 07 21:11:38-162596 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-162785 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-162973 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-163164 util-scheduler-8627 DEBUG Running task: 669 / 0x4661f98
Jul 07 21:11:38-163347 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-163520 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-163688 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-163864 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-164052 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-164238 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-164545 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-274438 util-scheduler-8627 DEBUG Checking readiness of task: 663 / 0x4661f98
Jul 07 21:11:38-274805 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-275002 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-275194 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-275390 util-scheduler-8627 DEBUG Running task: 663 / 0x4661f98
Jul 07 21:11:38-275819 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:38-276073 util-scheduler-8627 DEBUG Adding task: 670 / 0x4662140
Jul 07 21:11:38-276338 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-276529 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-276718 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-276908 util-scheduler-8627 DEBUG Running task: 670 / 0x4662140
Jul 07 21:11:38-277099 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:38-277330 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:38-277562 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:38-277768 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-277975 util-scheduler-8627 DEBUG Adding task: 671 / 0x4661f98
Jul 07 21:11:38-278162 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:38-278368 util-scheduler-8627 DEBUG Adding task: 672 / 0x4661f98
Jul 07 21:11:38-278608 util-scheduler-8627 DEBUG Checking readiness of task: 672 / 0x4661f98
Jul 07 21:11:38-278798 util-scheduler-8627 DEBUG Checking readiness of task: 671 / 0x4661f98
Jul 07 21:11:38-278990 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-279179 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-279368 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-279560 util-scheduler-8627 DEBUG Running task: 671 / 0x4661f98
Jul 07 21:11:38-279744 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-279923 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-280095 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-280282 util-scheduler-8627 DEBUG Canceling task: 668 / 0x4e607e8
Jul 07 21:11:38-280505 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:11:38-280725 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:38-280964 cadet-p2p-8627 DEBUG Checking 0x5685bd0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-281246 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:38-281425 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:11:38-281615 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:38-281900 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:11:38-282094 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:38-282273 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:38-282460 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:38-282649 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:38-282827 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:38-283012 util-scheduler-8627 DEBUG Canceling task: 664 / 0x4e61600
Jul 07 21:11:38-283222 util-scheduler-8627 DEBUG Adding task: 673 / 0x4e61600
Jul 07 21:11:38-283472 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:38-283641 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:38-283861 cadet-p2p-8627 DEBUG Checking 0x58d5568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-284098 cadet-p2p-8627 DEBUG Checking 0x58d5568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-284276 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:38-284481 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:38-284692 util-scheduler-8627 DEBUG Adding task: 674 / 0x4e607e8
Jul 07 21:11:38-284885 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:38-285062 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:11:38-285282 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:38-285457 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:38-285631 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:38-285868 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-286092 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:38-286270 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:38-286468 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:38-286673 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:11:38-286856 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:11:38-287057 util-scheduler-8627 DEBUG Adding task: 675 / 0x4e607e8
Jul 07 21:11:38-287275 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-287468 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-287668 util-scheduler-8627 DEBUG Adding task: 676 / 0x4661f98
Jul 07 21:11:38-287867 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:11:38-288118 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-288317 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:38-288561 util-scheduler-8627 DEBUG Checking readiness of task: 676 / 0x4661f98
Jul 07 21:11:38-288754 util-scheduler-8627 DEBUG Checking readiness of task: 672 / 0x4661f98
Jul 07 21:11:38-288954 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-289143 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-289356 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-289549 util-scheduler-8627 DEBUG Running task: 676 / 0x4661f98
Jul 07 21:11:38-289733 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-289910 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-290080 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-290257 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-290451 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-290638 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-290877 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-291081 util-scheduler-8627 DEBUG Running task: 674 / 0x4e607e8
Jul 07 21:11:38-291291 util-scheduler-8627 DEBUG Canceling task: 675 / 0x4e607e8
Jul 07 21:11:38-291504 util-scheduler-8627 DEBUG Adding task: 677 / 0x4e607e8
Jul 07 21:11:38-291722 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-291917 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-292118 util-scheduler-8627 DEBUG Adding task: 678 / 0x4661f98
Jul 07 21:11:38-292356 util-scheduler-8627 DEBUG Checking readiness of task: 678 / 0x4661f98
Jul 07 21:11:38-292559 util-scheduler-8627 DEBUG Checking readiness of task: 672 / 0x4661f98
Jul 07 21:11:38-292749 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-292937 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-293125 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-293340 util-scheduler-8627 DEBUG Running task: 678 / 0x4661f98
Jul 07 21:11:38-293524 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-293698 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-293866 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-294042 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-294231 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-294433 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-294674 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-375255 util-scheduler-8627 DEBUG Checking readiness of task: 672 / 0x4661f98
Jul 07 21:11:38-375492 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-376429 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-376660 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-376897 util-scheduler-8627 DEBUG Running task: 624 / 0x4d63d80
Jul 07 21:11:38-377120 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:38-377383 cadet-tun-8627 DEBUG  kx started 140 s ago
Jul 07 21:11:38-377593 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:38-377793 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:38-377995 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:38-378225 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:38-378404 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:38-378625 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:38-378920 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:38-379118 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:38-379356 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:38-379563 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:38-379878 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:38-380078 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:38-380303 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-380486 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:38-380661 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:38-380863 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:38-381065 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:38-381259 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:38-381433 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:38-381669 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-381864 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:38-382043 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:38-382278 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-382470 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:38-382647 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:38-382845 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:38-383067 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:38-383375 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:38-383576 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:38-383746 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:38-383928 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:38-387472 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:38-388329 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:38-388510 cadet-tun-8627 DEBUG   e sending 2812660872
Jul 07 21:11:38-388719 cadet-tun-8627 DEBUG   e towards KZKB
Jul 07 21:11:38-388922 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:38-389242 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:38-389475 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:38-389652 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:38-389872 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:38-390147 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:38-390345 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:38-390580 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:38-390812 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:38-391121 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:38-391320 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:38-391542 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-391724 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:38-391899 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:38-392100 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:38-392313 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:38-392488 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:38-392660 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:38-392896 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-393090 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:38-393288 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:38-393521 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-393714 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:38-393891 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:38-394123 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-394316 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:38-394493 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:38-394689 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:38-394937 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:38-395143 util-scheduler-8627 DEBUG Adding task: 679 / 0x4d63d80
Jul 07 21:11:38-400115 util-scheduler-8627 DEBUG Checking readiness of task: 672 / 0x4661f98
Jul 07 21:11:38-400376 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-400572 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-400764 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-400958 util-scheduler-8627 DEBUG Running task: 672 / 0x4661f98
Jul 07 21:11:38-401400 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:38-401636 util-scheduler-8627 DEBUG Adding task: 680 / 0x4662140
Jul 07 21:11:38-401885 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-402077 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-402278 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-402467 util-scheduler-8627 DEBUG Running task: 680 / 0x4662140
Jul 07 21:11:38-402659 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:38-402856 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:38-403072 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:38-403275 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-403479 util-scheduler-8627 DEBUG Adding task: 681 / 0x4661f98
Jul 07 21:11:38-403665 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:38-403867 util-scheduler-8627 DEBUG Adding task: 682 / 0x4661f98
Jul 07 21:11:38-404106 util-scheduler-8627 DEBUG Checking readiness of task: 682 / 0x4661f98
Jul 07 21:11:38-404296 util-scheduler-8627 DEBUG Checking readiness of task: 681 / 0x4661f98
Jul 07 21:11:38-404486 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-404675 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-404863 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-405054 util-scheduler-8627 DEBUG Running task: 681 / 0x4661f98
Jul 07 21:11:38-405261 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-405454 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-405625 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-405811 util-scheduler-8627 DEBUG Canceling task: 677 / 0x4e607e8
Jul 07 21:11:38-406032 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:11:38-406260 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:38-406492 cadet-p2p-8627 DEBUG Checking 0x58d5568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-406724 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:38-406901 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:11:38-407086 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:38-407369 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:11:38-407583 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:38-407848 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:38-408038 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:38-408227 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:38-408404 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:38-408589 util-scheduler-8627 DEBUG Canceling task: 673 / 0x4e61600
Jul 07 21:11:38-408799 util-scheduler-8627 DEBUG Adding task: 683 / 0x4e61600
Jul 07 21:11:38-409043 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:38-409233 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:38-409456 cadet-p2p-8627 DEBUG Checking 0x58db568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-409694 cadet-p2p-8627 DEBUG Checking 0x58db568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:38-409872 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:38-410081 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:38-410294 util-scheduler-8627 DEBUG Adding task: 684 / 0x4e607e8
Jul 07 21:11:38-410472 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:38-410648 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:11:38-410844 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:38-411018 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:38-411191 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:38-411427 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-411620 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:38-411797 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:38-412031 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:38-412224 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:38-412400 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:38-412597 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:38-412802 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:11:38-412985 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:11:38-413185 util-scheduler-8627 DEBUG Adding task: 685 / 0x4e607e8
Jul 07 21:11:38-413424 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-413626 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-413826 util-scheduler-8627 DEBUG Adding task: 686 / 0x4661f98
Jul 07 21:11:38-414025 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:11:38-414273 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-414473 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:38-414712 util-scheduler-8627 DEBUG Checking readiness of task: 686 / 0x4661f98
Jul 07 21:11:38-414906 util-scheduler-8627 DEBUG Checking readiness of task: 682 / 0x4661f98
Jul 07 21:11:38-415096 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-415285 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-415476 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-415687 util-scheduler-8627 DEBUG Running task: 686 / 0x4661f98
Jul 07 21:11:38-415873 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-416049 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-416220 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-416398 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-416594 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-416784 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-417019 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-417247 util-scheduler-8627 DEBUG Running task: 684 / 0x4e607e8
Jul 07 21:11:38-417442 util-scheduler-8627 DEBUG Canceling task: 685 / 0x4e607e8
Jul 07 21:11:38-417664 util-scheduler-8627 DEBUG Adding task: 687 / 0x4e607e8
Jul 07 21:11:38-417887 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:38-418084 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:38-418283 util-scheduler-8627 DEBUG Adding task: 688 / 0x4661f98
Jul 07 21:11:38-418527 util-scheduler-8627 DEBUG Checking readiness of task: 688 / 0x4661f98
Jul 07 21:11:38-418719 util-scheduler-8627 DEBUG Checking readiness of task: 682 / 0x4661f98
Jul 07 21:11:38-418909 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-419098 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-419287 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-419478 util-scheduler-8627 DEBUG Running task: 682 / 0x4661f98
Jul 07 21:11:38-419881 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:38-420111 util-scheduler-8627 DEBUG Adding task: 689 / 0x4662140
Jul 07 21:11:38-420319 util-scheduler-8627 DEBUG Running task: 688 / 0x4661f98
Jul 07 21:11:38-420504 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:38-420681 util-8627 DEBUG process_notify is running
Jul 07 21:11:38-420850 util-8627 DEBUG client_notify is running
Jul 07 21:11:38-421026 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:38-421238 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:38-421428 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:38-421668 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:38-421911 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:38-422101 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:38-422290 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:38-422478 util-scheduler-8627 DEBUG Running task: 689 / 0x4662140
Jul 07 21:11:38-422667 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:38-422860 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:38-423074 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:38-423254 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:38-423465 util-scheduler-8627 DEBUG Adding task: 690 / 0x4661f98
Jul 07 21:11:41-581525 util-scheduler-8627 DEBUG Checking readiness of task: 690 / 0x4661f98
Jul 07 21:11:41-581903 util-scheduler-8627 DEBUG Checking readiness of task: 534 / 0x465ed58
Jul 07 21:11:41-582102 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-582296 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-582494 util-scheduler-8627 DEBUG Running task: 534 / 0x465ed58
Jul 07 21:11:41-582925 util-8627 DEBUG receive_ready read 120/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:11:41-583212 util-scheduler-8627 DEBUG Adding task: 691 / 0x465ef00
Jul 07 21:11:41-583493 util-scheduler-8627 DEBUG Checking readiness of task: 690 / 0x4661f98
Jul 07 21:11:41-583686 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-583876 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-584067 util-scheduler-8627 DEBUG Running task: 691 / 0x465ef00
Jul 07 21:11:41-584259 util-8627 DEBUG Received message of type 332 and size 40 from peerinfo service.
Jul 07 21:11:41-584499 nse-api-8627 DEBUG Received information about peer `Z8AF' from peerinfo database
Jul 07 21:11:41-584687 cadet-hll-8627 DEBUG  hello with id 0xbee5e888 and msg (nil)
Jul 07 21:11:41-584899 util-scheduler-8627 DEBUG Adding task: 692 / 0x465ef00
Jul 07 21:11:41-585133 util-scheduler-8627 DEBUG Checking readiness of task: 690 / 0x4661f98
Jul 07 21:11:41-589057 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-589291 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-589485 util-scheduler-8627 DEBUG Running task: 692 / 0x465ef00
Jul 07 21:11:41-589678 util-8627 DEBUG Received message of type 332 and size 80 from peerinfo service.
Jul 07 21:11:41-589903 nse-api-8627 DEBUG Received information about peer `Z8AF' from peerinfo database
Jul 07 21:11:41-590179 cadet-hll-8627 DEBUG  hello for Z8AF (40 bytes), expires on Wed Dec 31 18:00:00 1969
Jul 07 21:11:41-594414 cadet-p2p-8627 DEBUG set hello for Z8AF
Jul 07 21:11:41-594616 cadet-p2p-8627 DEBUG  new (40 bytes)
Jul 07 21:11:41-594813 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:41-595033 util-scheduler-8627 DEBUG Adding task: 693 / 0x465ed58
Jul 07 21:11:41-887004 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:41-887364 util-scheduler-8627 DEBUG Checking readiness of task: 690 / 0x4661f98
Jul 07 21:11:41-887562 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-887753 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-887950 util-scheduler-8627 DEBUG Running task: 690 / 0x4661f98
Jul 07 21:11:41-888375 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:41-888644 util-scheduler-8627 DEBUG Adding task: 694 / 0x4662140
Jul 07 21:11:41-888917 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:41-889109 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-889327 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-889518 util-scheduler-8627 DEBUG Running task: 694 / 0x4662140
Jul 07 21:11:41-889708 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:41-889908 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:41-890155 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:41-890364 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:41-890570 util-scheduler-8627 DEBUG Adding task: 695 / 0x4661f98
Jul 07 21:11:41-890757 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:41-890962 util-scheduler-8627 DEBUG Adding task: 696 / 0x4661f98
Jul 07 21:11:41-891202 util-scheduler-8627 DEBUG Checking readiness of task: 696 / 0x4661f98
Jul 07 21:11:41-891392 util-scheduler-8627 DEBUG Checking readiness of task: 695 / 0x4661f98
Jul 07 21:11:41-891583 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:41-891821 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-892012 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-892204 util-scheduler-8627 DEBUG Running task: 695 / 0x4661f98
Jul 07 21:11:41-892389 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:41-892567 util-8627 DEBUG process_notify is running
Jul 07 21:11:41-892768 util-8627 DEBUG client_notify is running
Jul 07 21:11:41-892960 util-scheduler-8627 DEBUG Canceling task: 687 / 0x4e607e8
Jul 07 21:11:41-893185 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:41-893429 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:41-893669 cadet-p2p-8627 DEBUG Checking 0x58db568 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:41-893903 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:41-894080 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:41-894270 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:41-894556 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:41-894751 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:41-894930 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:41-895118 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:41-895306 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:41-895484 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:41-895669 util-scheduler-8627 DEBUG Canceling task: 683 / 0x4e61600
Jul 07 21:11:41-895879 util-scheduler-8627 DEBUG Adding task: 697 / 0x4e61600
Jul 07 21:11:41-896130 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:41-896299 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:41-896519 cadet-p2p-8627 DEBUG Checking 0x58e1ee0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:41-896757 cadet-p2p-8627 DEBUG Checking 0x58e1ee0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:41-896935 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:41-897141 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:41-897379 util-scheduler-8627 DEBUG Adding task: 698 / 0x4e607e8
Jul 07 21:11:41-897558 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:41-897734 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:41-897934 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:41-898109 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:41-898283 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:41-898533 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:41-898728 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:41-898906 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:41-899103 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:41-899308 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:41-899491 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:41-899693 util-scheduler-8627 DEBUG Adding task: 699 / 0x4e607e8
Jul 07 21:11:41-899911 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:41-900104 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:41-900305 util-scheduler-8627 DEBUG Adding task: 700 / 0x4661f98
Jul 07 21:11:41-900506 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:41-901295 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:41-901499 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:41-901744 util-scheduler-8627 DEBUG Checking readiness of task: 700 / 0x4661f98
Jul 07 21:11:41-901937 util-scheduler-8627 DEBUG Checking readiness of task: 696 / 0x4661f98
Jul 07 21:11:41-902126 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:41-902316 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-902505 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-902697 util-scheduler-8627 DEBUG Running task: 700 / 0x4661f98
Jul 07 21:11:41-902884 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:41-903059 util-8627 DEBUG process_notify is running
Jul 07 21:11:41-903228 util-8627 DEBUG client_notify is running
Jul 07 21:11:41-903405 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:41-903628 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:41-903816 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:41-904098 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:41-904306 util-scheduler-8627 DEBUG Running task: 698 / 0x4e607e8
Jul 07 21:11:41-904499 util-scheduler-8627 DEBUG Canceling task: 699 / 0x4e607e8
Jul 07 21:11:41-904711 util-scheduler-8627 DEBUG Adding task: 701 / 0x4e607e8
Jul 07 21:11:41-904926 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:41-905121 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:41-905344 util-scheduler-8627 DEBUG Adding task: 702 / 0x4661f98
Jul 07 21:11:41-905581 util-scheduler-8627 DEBUG Checking readiness of task: 702 / 0x4661f98
Jul 07 21:11:41-905773 util-scheduler-8627 DEBUG Checking readiness of task: 696 / 0x4661f98
Jul 07 21:11:41-905961 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:41-906150 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:41-906339 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:41-906546 util-scheduler-8627 DEBUG Running task: 702 / 0x4661f98
Jul 07 21:11:41-906730 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:41-906904 util-8627 DEBUG process_notify is running
Jul 07 21:11:41-907071 util-8627 DEBUG client_notify is running
Jul 07 21:11:41-907246 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:41-907445 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:41-907632 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:41-907914 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:42-017497 util-scheduler-8627 DEBUG Checking readiness of task: 696 / 0x4661f98
Jul 07 21:11:42-017889 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:42-018088 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:42-018283 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:42-018483 util-scheduler-8627 DEBUG Running task: 696 / 0x4661f98
Jul 07 21:11:42-018913 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:42-019172 util-scheduler-8627 DEBUG Adding task: 703 / 0x4662140
Jul 07 21:11:42-019451 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:42-019645 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:42-019837 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:42-020029 util-scheduler-8627 DEBUG Running task: 703 / 0x4662140
Jul 07 21:11:42-020223 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:42-020424 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:42-020658 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:42-020869 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:42-021080 util-scheduler-8627 DEBUG Adding task: 704 / 0x4661f98
Jul 07 21:11:42-021296 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:42-021506 util-scheduler-8627 DEBUG Adding task: 705 / 0x4661f98
Jul 07 21:11:42-021750 util-scheduler-8627 DEBUG Checking readiness of task: 705 / 0x4661f98
Jul 07 21:11:42-021942 util-scheduler-8627 DEBUG Checking readiness of task: 704 / 0x4661f98
Jul 07 21:11:42-022136 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:42-022328 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:42-022549 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:42-022744 util-scheduler-8627 DEBUG Running task: 704 / 0x4661f98
Jul 07 21:11:42-022931 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:42-023111 util-8627 DEBUG process_notify is running
Jul 07 21:11:42-023284 util-8627 DEBUG client_notify is running
Jul 07 21:11:42-023474 util-scheduler-8627 DEBUG Canceling task: 701 / 0x4e607e8
Jul 07 21:11:42-023701 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:42-023923 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:42-024166 cadet-p2p-8627 DEBUG Checking 0x58e1ee0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:42-024402 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:42-024581 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:42-024773 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:42-025060 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:42-025284 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:42-025468 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:42-025657 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:42-025848 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:42-026027 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:42-026215 util-scheduler-8627 DEBUG Canceling task: 697 / 0x4e61600
Jul 07 21:11:42-026428 util-scheduler-8627 DEBUG Adding task: 706 / 0x4e61600
Jul 07 21:11:42-026683 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:42-026855 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:42-027059 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:42-027259 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:42-027435 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:42-027611 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:42-027811 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:42-028017 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:42-028202 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:42-028382 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:42-028575 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:42-028828 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:43-395313 util-scheduler-8627 DEBUG Checking readiness of task: 705 / 0x4661f98
Jul 07 21:11:43-395676 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:43-397363 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:43-397710 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:43-397909 util-scheduler-8627 DEBUG Running task: 679 / 0x4d63d80
Jul 07 21:11:43-398144 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:43-398389 cadet-tun-8627 DEBUG  kx started 145 s ago
Jul 07 21:11:43-398599 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:43-398799 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:43-399002 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:43-399235 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:43-399415 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:43-399637 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:43-399926 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:43-400124 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:43-400363 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:43-400571 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:43-400887 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:43-401089 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:43-401383 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:43-401569 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:43-401746 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:43-401971 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:43-402188 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:43-402410 util-scheduler-8627 DEBUG Adding task: 707 / 0x4e607e8
Jul 07 21:11:43-402591 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:43-402807 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:43-402982 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:43-403156 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:43-403393 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:43-403589 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:43-403768 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:43-403967 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:43-404170 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:43-404481 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:43-404681 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:43-404852 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:43-405032 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:43-408596 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:43-409943 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:43-410182 cadet-tun-8627 DEBUG   e sending 3106981451
Jul 07 21:11:43-410391 cadet-tun-8627 DEBUG   e towards KK03
Jul 07 21:11:43-410591 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:43-410789 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:43-411018 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:43-411201 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:43-411420 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:43-411695 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:43-411893 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:43-412127 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:43-412333 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:43-412662 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:43-412862 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:43-413084 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:43-413293 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:43-413468 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:43-413671 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:43-413872 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:43-414046 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:43-414220 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:43-414455 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:43-414650 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:43-414827 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:43-415059 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:43-415251 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:43-415428 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:43-415624 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:43-415871 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:43-416075 util-scheduler-8627 DEBUG Adding task: 708 / 0x4d63d80
Jul 07 21:11:43-416340 util-scheduler-8627 DEBUG Checking readiness of task: 705 / 0x4661f98
Jul 07 21:11:43-416532 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:43-416731 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:43-416939 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:43-417132 util-scheduler-8627 DEBUG Running task: 707 / 0x4e607e8
Jul 07 21:11:43-417367 util-scheduler-8627 DEBUG Adding task: 709 / 0x4e607e8
Jul 07 21:11:43-417589 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:43-417792 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:43-418000 util-scheduler-8627 DEBUG Adding task: 710 / 0x4661f98
Jul 07 21:11:43-418241 util-scheduler-8627 DEBUG Checking readiness of task: 710 / 0x4661f98
Jul 07 21:11:43-418433 util-scheduler-8627 DEBUG Checking readiness of task: 705 / 0x4661f98
Jul 07 21:11:43-418622 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:43-418811 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:43-419000 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:43-419192 util-scheduler-8627 DEBUG Running task: 710 / 0x4661f98
Jul 07 21:11:43-419377 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:43-419554 util-8627 DEBUG process_notify is running
Jul 07 21:11:43-419726 util-8627 DEBUG client_notify is running
Jul 07 21:11:43-419905 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:43-420099 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:43-420289 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:43-420548 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-291874 util-scheduler-8627 DEBUG Checking readiness of task: 705 / 0x4661f98
Jul 07 21:11:48-292260 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-292460 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-292655 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-292873 util-scheduler-8627 DEBUG Running task: 705 / 0x4661f98
Jul 07 21:11:48-293327 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:48-293591 util-scheduler-8627 DEBUG Adding task: 711 / 0x4662140
Jul 07 21:11:48-293873 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-294068 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-294259 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-294450 util-scheduler-8627 DEBUG Running task: 711 / 0x4662140
Jul 07 21:11:48-294648 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:48-294850 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:48-295085 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:48-295293 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-295502 util-scheduler-8627 DEBUG Adding task: 712 / 0x4661f98
Jul 07 21:11:48-295691 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:48-295900 util-scheduler-8627 DEBUG Adding task: 713 / 0x4661f98
Jul 07 21:11:48-296146 util-scheduler-8627 DEBUG Checking readiness of task: 713 / 0x4661f98
Jul 07 21:11:48-296340 util-scheduler-8627 DEBUG Checking readiness of task: 712 / 0x4661f98
Jul 07 21:11:48-296533 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-296723 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-296913 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-297106 util-scheduler-8627 DEBUG Running task: 712 / 0x4661f98
Jul 07 21:11:48-297602 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-297787 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-297962 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-298188 util-scheduler-8627 DEBUG Canceling task: 709 / 0x4e607e8
Jul 07 21:11:48-298457 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:48-298786 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:48-299033 cadet-p2p-8627 DEBUG Checking 0x58e9fa0 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-299281 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:48-299458 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:48-299649 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:48-299943 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:48-300140 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:48-300322 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:48-300510 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:48-300700 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:48-300879 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:48-301066 util-scheduler-8627 DEBUG Canceling task: 706 / 0x4e61600
Jul 07 21:11:48-301311 util-scheduler-8627 DEBUG Adding task: 714 / 0x4e61600
Jul 07 21:11:48-301565 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:48-301737 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:48-301958 cadet-p2p-8627 DEBUG Checking 0x58f0980 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-302199 cadet-p2p-8627 DEBUG Checking 0x58f0980 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-302378 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:48-302585 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:48-302802 util-scheduler-8627 DEBUG Adding task: 715 / 0x4e607e8
Jul 07 21:11:48-302981 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:48-303159 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:48-303358 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-303533 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:48-303708 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:48-304205 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-304411 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-304595 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-304797 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-305004 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:48-305208 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:48-305432 util-scheduler-8627 DEBUG Adding task: 716 / 0x4e607e8
Jul 07 21:11:48-305653 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-305852 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-306072 util-scheduler-8627 DEBUG Adding task: 717 / 0x4661f98
Jul 07 21:11:48-306276 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:48-307045 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-307254 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:48-307514 util-scheduler-8627 DEBUG Checking readiness of task: 717 / 0x4661f98
Jul 07 21:11:48-307711 util-scheduler-8627 DEBUG Checking readiness of task: 713 / 0x4661f98
Jul 07 21:11:48-307903 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-308093 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-308283 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-308479 util-scheduler-8627 DEBUG Running task: 717 / 0x4661f98
Jul 07 21:11:48-308669 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-308851 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-309025 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-309230 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-309454 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-309642 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-309932 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-310143 util-scheduler-8627 DEBUG Running task: 715 / 0x4e607e8
Jul 07 21:11:48-310338 util-scheduler-8627 DEBUG Canceling task: 716 / 0x4e607e8
Jul 07 21:11:48-310557 util-scheduler-8627 DEBUG Adding task: 718 / 0x4e607e8
Jul 07 21:11:48-310779 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-310977 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-311180 util-scheduler-8627 DEBUG Adding task: 719 / 0x4661f98
Jul 07 21:11:48-311427 util-scheduler-8627 DEBUG Checking readiness of task: 719 / 0x4661f98
Jul 07 21:11:48-311620 util-scheduler-8627 DEBUG Checking readiness of task: 713 / 0x4661f98
Jul 07 21:11:48-311811 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-312001 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-312192 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-312384 util-scheduler-8627 DEBUG Running task: 719 / 0x4661f98
Jul 07 21:11:48-312569 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-312745 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-312915 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-313092 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-313306 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-313495 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-313782 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-416315 util-scheduler-8627 DEBUG Checking readiness of task: 713 / 0x4661f98
Jul 07 21:11:48-416670 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-417531 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-417733 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-417928 util-scheduler-8627 DEBUG Running task: 708 / 0x4d63d80
Jul 07 21:11:48-418163 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:48-418407 cadet-tun-8627 DEBUG  kx started 150 s ago
Jul 07 21:11:48-418616 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:48-418815 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:48-419016 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:48-419268 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:48-419447 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:48-419668 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:48-419955 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:48-420152 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:48-420390 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:48-420597 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:48-420912 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:48-421112 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:48-421357 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-421541 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:48-421715 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:48-421918 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:48-422119 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-422294 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:48-422491 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:48-422729 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-422924 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-423101 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-423333 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-423525 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:48-423701 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:48-423898 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-424100 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:48-424422 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:48-424630 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:48-424811 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:48-424996 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:48-429028 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:48-430064 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:48-430272 cadet-tun-8627 DEBUG   e sending 62500530
Jul 07 21:11:48-430490 cadet-tun-8627 DEBUG   e towards 6M74
Jul 07 21:11:48-430690 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:48-430889 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:48-431121 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:48-431299 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:48-431518 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:48-431795 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:48-431993 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:48-432226 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:48-432432 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:48-432742 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:48-432939 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:48-433247 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-433433 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:48-433609 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:48-433810 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:48-434011 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-434184 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:48-434357 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:48-434596 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-434790 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-434967 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-435198 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-435399 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:48-435575 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:48-435807 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-435998 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-436174 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-436369 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-436620 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:48-436854 util-scheduler-8627 DEBUG Adding task: 720 / 0x4d63d80
Jul 07 21:11:48-553283 util-scheduler-8627 DEBUG Checking readiness of task: 713 / 0x4661f98
Jul 07 21:11:48-553600 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-553796 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-553987 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-554184 util-scheduler-8627 DEBUG Running task: 713 / 0x4661f98
Jul 07 21:11:48-554607 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:48-554887 util-scheduler-8627 DEBUG Adding task: 721 / 0x4662140
Jul 07 21:11:48-555155 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-555347 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-555536 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-555726 util-scheduler-8627 DEBUG Running task: 721 / 0x4662140
Jul 07 21:11:48-555917 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:48-556116 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:48-556342 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:48-556548 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-556754 util-scheduler-8627 DEBUG Adding task: 722 / 0x4661f98
Jul 07 21:11:48-556942 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:48-557147 util-scheduler-8627 DEBUG Adding task: 723 / 0x4661f98
Jul 07 21:11:48-557418 util-scheduler-8627 DEBUG Checking readiness of task: 723 / 0x4661f98
Jul 07 21:11:48-557608 util-scheduler-8627 DEBUG Checking readiness of task: 722 / 0x4661f98
Jul 07 21:11:48-557798 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-557987 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-558175 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-558365 util-scheduler-8627 DEBUG Running task: 722 / 0x4661f98
Jul 07 21:11:48-558569 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-558747 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-558917 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-559102 util-scheduler-8627 DEBUG Canceling task: 718 / 0x4e607e8
Jul 07 21:11:48-559324 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:48-559542 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:48-559777 cadet-p2p-8627 DEBUG Checking 0x58f0980 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-560008 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:48-560185 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:48-560374 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:48-560661 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:48-560857 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:48-561040 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:48-561256 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:48-561453 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:48-561636 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:48-561827 util-scheduler-8627 DEBUG Canceling task: 714 / 0x4e61600
Jul 07 21:11:48-562048 util-scheduler-8627 DEBUG Adding task: 724 / 0x4e61600
Jul 07 21:11:48-562300 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:48-562473 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:48-562701 cadet-p2p-8627 DEBUG Checking 0x58f4768 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-562946 cadet-p2p-8627 DEBUG Checking 0x58f4768 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-563125 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:48-563330 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:48-563545 util-scheduler-8627 DEBUG Adding task: 725 / 0x4e607e8
Jul 07 21:11:48-563723 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:48-563897 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:48-564094 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-564267 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:48-564440 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:48-564676 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-564891 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:48-565069 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:48-565346 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-565539 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-565715 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-565911 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-566115 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:48-566297 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:48-566512 util-scheduler-8627 DEBUG Adding task: 726 / 0x4e607e8
Jul 07 21:11:48-566730 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-566926 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-567129 util-scheduler-8627 DEBUG Adding task: 727 / 0x4661f98
Jul 07 21:11:48-567329 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:48-568088 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-568291 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:48-568542 util-scheduler-8627 DEBUG Checking readiness of task: 727 / 0x4661f98
Jul 07 21:11:48-568735 util-scheduler-8627 DEBUG Checking readiness of task: 723 / 0x4661f98
Jul 07 21:11:48-568924 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-569112 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-569323 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-569516 util-scheduler-8627 DEBUG Running task: 727 / 0x4661f98
Jul 07 21:11:48-569700 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-569876 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-570045 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-570221 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-570416 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-570606 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-570886 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-571093 util-scheduler-8627 DEBUG Running task: 725 / 0x4e607e8
Jul 07 21:11:48-571285 util-scheduler-8627 DEBUG Canceling task: 726 / 0x4e607e8
Jul 07 21:11:48-571497 util-scheduler-8627 DEBUG Adding task: 728 / 0x4e607e8
Jul 07 21:11:48-571711 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-571905 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-572102 util-scheduler-8627 DEBUG Adding task: 729 / 0x4661f98
Jul 07 21:11:48-572337 util-scheduler-8627 DEBUG Checking readiness of task: 729 / 0x4661f98
Jul 07 21:11:48-572528 util-scheduler-8627 DEBUG Checking readiness of task: 723 / 0x4661f98
Jul 07 21:11:48-572717 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-572905 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-573093 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-573304 util-scheduler-8627 DEBUG Running task: 729 / 0x4661f98
Jul 07 21:11:48-573488 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-573662 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-573831 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-574008 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-574200 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-574390 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-574682 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-679123 util-scheduler-8627 DEBUG Checking readiness of task: 723 / 0x4661f98
Jul 07 21:11:48-679410 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-679606 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-679858 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-680064 util-scheduler-8627 DEBUG Running task: 723 / 0x4661f98
Jul 07 21:11:48-680478 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:48-680724 util-scheduler-8627 DEBUG Adding task: 730 / 0x4662140
Jul 07 21:11:48-680999 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-681213 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-681405 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-681594 util-scheduler-8627 DEBUG Running task: 730 / 0x4662140
Jul 07 21:11:48-681784 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:48-681982 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:48-682202 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:48-682404 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-682607 util-scheduler-8627 DEBUG Adding task: 731 / 0x4661f98
Jul 07 21:11:48-682791 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:48-682993 util-scheduler-8627 DEBUG Adding task: 732 / 0x4661f98
Jul 07 21:11:48-683230 util-scheduler-8627 DEBUG Checking readiness of task: 732 / 0x4661f98
Jul 07 21:11:48-683420 util-scheduler-8627 DEBUG Checking readiness of task: 731 / 0x4661f98
Jul 07 21:11:48-683610 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-683799 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-683987 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-684177 util-scheduler-8627 DEBUG Running task: 731 / 0x4661f98
Jul 07 21:11:48-684360 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-684535 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-684704 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-684887 util-scheduler-8627 DEBUG Canceling task: 728 / 0x4e607e8
Jul 07 21:11:48-685107 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:48-685345 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:48-685578 cadet-p2p-8627 DEBUG Checking 0x58f4768 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-685809 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:48-685985 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:48-686171 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:48-686452 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:48-686645 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:48-686822 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:48-687007 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:48-687194 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:48-687370 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:48-687553 util-scheduler-8627 DEBUG Canceling task: 724 / 0x4e61600
Jul 07 21:11:48-687762 util-scheduler-8627 DEBUG Adding task: 733 / 0x4e61600
Jul 07 21:11:48-688006 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:48-688174 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:48-688393 cadet-p2p-8627 DEBUG Checking 0x58fb110 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-688629 cadet-p2p-8627 DEBUG Checking 0x58fb110 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-688806 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:48-689009 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:48-689271 util-scheduler-8627 DEBUG Adding task: 734 / 0x4e607e8
Jul 07 21:11:48-689451 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:48-689627 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:48-689825 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-689998 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:48-690171 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:48-690408 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:48-690604 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:48-690782 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:48-690979 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-691181 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:48-691363 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:48-691575 util-scheduler-8627 DEBUG Adding task: 735 / 0x4e607e8
Jul 07 21:11:48-691790 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-691987 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-692189 util-scheduler-8627 DEBUG Adding task: 736 / 0x4661f98
Jul 07 21:11:48-692391 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:48-693252 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-693472 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:48-693729 util-scheduler-8627 DEBUG Checking readiness of task: 736 / 0x4661f98
Jul 07 21:11:48-694073 util-scheduler-8627 DEBUG Checking readiness of task: 732 / 0x4661f98
Jul 07 21:11:48-694387 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-694579 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-694768 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-694960 util-scheduler-8627 DEBUG Running task: 736 / 0x4661f98
Jul 07 21:11:48-695143 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-695319 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-695489 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-695666 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-695860 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-696047 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-696347 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-696557 util-scheduler-8627 DEBUG Running task: 734 / 0x4e607e8
Jul 07 21:11:48-696751 util-scheduler-8627 DEBUG Canceling task: 735 / 0x4e607e8
Jul 07 21:11:48-696967 util-scheduler-8627 DEBUG Adding task: 737 / 0x4e607e8
Jul 07 21:11:48-697186 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:48-697406 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-697608 util-scheduler-8627 DEBUG Adding task: 738 / 0x4661f98
Jul 07 21:11:48-697848 util-scheduler-8627 DEBUG Checking readiness of task: 738 / 0x4661f98
Jul 07 21:11:48-698040 util-scheduler-8627 DEBUG Checking readiness of task: 732 / 0x4661f98
Jul 07 21:11:48-698229 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-698482 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-698672 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-698862 util-scheduler-8627 DEBUG Running task: 732 / 0x4661f98
Jul 07 21:11:48-699264 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:48-699491 util-scheduler-8627 DEBUG Adding task: 739 / 0x4662140
Jul 07 21:11:48-699720 util-scheduler-8627 DEBUG Running task: 738 / 0x4661f98
Jul 07 21:11:48-699904 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-700078 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-700247 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-700421 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:48-700613 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-700800 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:48-701098 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:48-701367 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-701558 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-701748 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-701936 util-scheduler-8627 DEBUG Running task: 739 / 0x4662140
Jul 07 21:11:48-702126 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:48-702320 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:48-702533 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:48-702713 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:48-702913 util-scheduler-8627 DEBUG Adding task: 740 / 0x4661f98
Jul 07 21:11:48-703149 util-scheduler-8627 DEBUG Checking readiness of task: 740 / 0x4661f98
Jul 07 21:11:48-703340 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-703529 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-703718 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-703907 util-scheduler-8627 DEBUG Running task: 740 / 0x4661f98
Jul 07 21:11:48-704305 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:48-704527 util-scheduler-8627 DEBUG Adding task: 741 / 0x4662140
Jul 07 21:11:48-704769 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-704959 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-705150 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-705375 util-scheduler-8627 DEBUG Running task: 741 / 0x4662140
Jul 07 21:11:48-705563 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:48-705755 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:48-705964 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:48-706159 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:48-706356 util-scheduler-8627 DEBUG Adding task: 742 / 0x4661f98
Jul 07 21:11:48-706537 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:48-706733 util-scheduler-8627 DEBUG Adding task: 743 / 0x4661f98
Jul 07 21:11:48-706969 util-scheduler-8627 DEBUG Checking readiness of task: 743 / 0x4661f98
Jul 07 21:11:48-707159 util-scheduler-8627 DEBUG Checking readiness of task: 742 / 0x4661f98
Jul 07 21:11:48-707348 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:48-707538 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:48-707727 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:48-707918 util-scheduler-8627 DEBUG Running task: 742 / 0x4661f98
Jul 07 21:11:48-708101 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:48-708276 util-8627 DEBUG process_notify is running
Jul 07 21:11:48-708445 util-8627 DEBUG client_notify is running
Jul 07 21:11:48-708626 util-scheduler-8627 DEBUG Canceling task: 737 / 0x4e607e8
Jul 07 21:11:48-708854 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:48-709083 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:48-709341 cadet-p2p-8627 DEBUG Checking 0x58fb110 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:48-709572 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:48-709749 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:48-709936 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:48-710213 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:48-710406 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:48-710582 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:48-710771 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:48-710958 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:48-711135 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:48-711319 util-scheduler-8627 DEBUG Canceling task: 733 / 0x4e61600
Jul 07 21:11:48-711529 util-scheduler-8627 DEBUG Adding task: 744 / 0x4e61600
Jul 07 21:11:48-711772 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:48-711941 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:48-712119 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:48-712316 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:48-712491 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:48-712664 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:48-712876 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:48-713080 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:48-713307 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:48-713484 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:48-713672 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:48-714230 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:51-110369 util-scheduler-8627 DEBUG Checking readiness of task: 743 / 0x4661f98
Jul 07 21:11:51-110749 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-110946 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-111138 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-111338 util-scheduler-8627 DEBUG Running task: 743 / 0x4661f98
Jul 07 21:11:51-111761 util-8627 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:51-112017 util-scheduler-8627 DEBUG Adding task: 745 / 0x4662140
Jul 07 21:11:51-112294 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-112486 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-112677 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-112866 util-scheduler-8627 DEBUG Running task: 745 / 0x4662140
Jul 07 21:11:51-113057 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:51-113286 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:51-113519 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:51-113785 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:51-114027 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:51-114274 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:51-114483 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:51-114731 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:51-114941 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:51-115127 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:51-115314 util-scheduler-8627 DEBUG Canceling task: 658 / 0x4e61600
Jul 07 21:11:51-115537 util-scheduler-8627 DEBUG Adding task: 746 / 0x4e61600
Jul 07 21:11:51-115715 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:51-116002 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:51-116219 util-scheduler-8627 DEBUG Adding task: 747 / 0x4d50e20
Jul 07 21:11:51-116401 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:51-116601 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:51-722097 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:51-722474 util-scheduler-8627 DEBUG Adding task: 748 / 0x4661f98
Jul 07 21:11:51-722771 util-scheduler-8627 DEBUG Checking readiness of task: 748 / 0x4661f98
Jul 07 21:11:51-722970 util-scheduler-8627 DEBUG Checking readiness of task: 747 / 0x4d50e20
Jul 07 21:11:51-723165 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-723355 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-723546 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-723741 util-scheduler-8627 DEBUG Running task: 747 / 0x4d50e20
Jul 07 21:11:51-723928 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:51-724109 util-8627 DEBUG process_notify is running
Jul 07 21:11:51-724282 util-8627 DEBUG client_notify is running
Jul 07 21:11:51-724518 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:51-724781 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:51-792005 util-scheduler-8627 DEBUG Checking readiness of task: 748 / 0x4661f98
Jul 07 21:11:51-792307 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-792501 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-792692 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-792887 util-scheduler-8627 DEBUG Running task: 748 / 0x4661f98
Jul 07 21:11:51-793332 util-8627 DEBUG receive_ready read 116/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:51-793591 util-scheduler-8627 DEBUG Adding task: 749 / 0x4662140
Jul 07 21:11:51-793855 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-794046 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-794235 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-794425 util-scheduler-8627 DEBUG Running task: 749 / 0x4662140
Jul 07 21:11:51-794616 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:51-794821 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:51-795056 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:51-795324 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:51-795568 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:51-795801 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:51-796012 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:51-796261 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:51-796493 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:51-796682 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:51-796872 util-scheduler-8627 DEBUG Canceling task: 746 / 0x4e61600
Jul 07 21:11:51-797097 util-scheduler-8627 DEBUG Adding task: 750 / 0x4e61600
Jul 07 21:11:51-797342 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:51-797603 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:51-797834 util-scheduler-8627 DEBUG Adding task: 751 / 0x4d50e20
Jul 07 21:11:51-798017 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:51-798217 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:51-798404 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:51-798577 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:51-798744 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:51-802937 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:51-803842 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:51-804110 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:51-804410 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:51-804587 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:51-805349 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:51-808583 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:51-809367 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:51-809586 cadet-tun-8627 DEBUG   e sending 2364126573
Jul 07 21:11:51-809809 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:51-810016 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:51-810249 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:51-810429 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:51-810650 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:51-810936 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:51-811137 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:51-811373 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:51-811587 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:51-811904 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:51-812123 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:51-812351 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:51-812537 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:51-812714 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:51-812922 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 48 bytes
Jul 07 21:11:51-813138 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:51-813393 util-scheduler-8627 DEBUG Adding task: 752 / 0x4e607e8
Jul 07 21:11:51-813578 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:51-813784 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:51-813960 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:51-814136 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:51-814376 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:51-814573 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:51-814752 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:51-814952 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:51-815136 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:51-815350 util-scheduler-8627 DEBUG Adding task: 753 / 0x4661f98
Jul 07 21:11:51-815625 util-scheduler-8627 DEBUG Checking readiness of task: 753 / 0x4661f98
Jul 07 21:11:51-815823 util-scheduler-8627 DEBUG Checking readiness of task: 751 / 0x4d50e20
Jul 07 21:11:51-816017 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-816207 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-816398 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-816599 util-scheduler-8627 DEBUG Running task: 751 / 0x4d50e20
Jul 07 21:11:51-816786 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:51-816965 util-8627 DEBUG process_notify is running
Jul 07 21:11:51-817138 util-8627 DEBUG client_notify is running
Jul 07 21:11:51-817394 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:51-817699 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:51-817919 util-scheduler-8627 DEBUG Running task: 752 / 0x4e607e8
Jul 07 21:11:51-818134 util-scheduler-8627 DEBUG Adding task: 754 / 0x4e607e8
Jul 07 21:11:51-818362 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:51-818568 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:51-818773 util-scheduler-8627 DEBUG Adding task: 755 / 0x4661f98
Jul 07 21:11:51-819022 util-scheduler-8627 DEBUG Checking readiness of task: 755 / 0x4661f98
Jul 07 21:11:51-819247 util-scheduler-8627 DEBUG Checking readiness of task: 753 / 0x4661f98
Jul 07 21:11:51-819440 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-819631 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-819821 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-820013 util-scheduler-8627 DEBUG Running task: 755 / 0x4661f98
Jul 07 21:11:51-820198 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:51-820374 util-8627 DEBUG process_notify is running
Jul 07 21:11:51-820559 util-8627 DEBUG client_notify is running
Jul 07 21:11:51-820738 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:51-820936 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:51-821126 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:51-821456 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:51-919189 util-scheduler-8627 DEBUG Checking readiness of task: 753 / 0x4661f98
Jul 07 21:11:51-919540 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-919735 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-919928 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-920124 util-scheduler-8627 DEBUG Running task: 753 / 0x4661f98
Jul 07 21:11:51-920545 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:51-920797 util-scheduler-8627 DEBUG Adding task: 756 / 0x4662140
Jul 07 21:11:51-921067 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-921288 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-921479 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-921669 util-scheduler-8627 DEBUG Running task: 756 / 0x4662140
Jul 07 21:11:51-921860 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:51-922059 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:51-922290 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:51-922499 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:51-922706 util-scheduler-8627 DEBUG Adding task: 757 / 0x4661f98
Jul 07 21:11:51-922893 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:51-923111 util-scheduler-8627 DEBUG Adding task: 758 / 0x4661f98
Jul 07 21:11:51-923353 util-scheduler-8627 DEBUG Checking readiness of task: 758 / 0x4661f98
Jul 07 21:11:51-923544 util-scheduler-8627 DEBUG Checking readiness of task: 757 / 0x4661f98
Jul 07 21:11:51-923735 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:51-923925 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:51-924114 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:51-924305 util-scheduler-8627 DEBUG Running task: 757 / 0x4661f98
Jul 07 21:11:51-924490 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:51-924667 util-8627 DEBUG process_notify is running
Jul 07 21:11:51-924837 util-8627 DEBUG client_notify is running
Jul 07 21:11:51-925024 util-scheduler-8627 DEBUG Canceling task: 754 / 0x4e607e8
Jul 07 21:11:51-925271 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:11:51-925494 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:51-925738 cadet-p2p-8627 DEBUG Checking 0x5b511a8 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:51-925973 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:51-926150 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:11:51-926341 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:51-926657 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:11:51-926852 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:51-927032 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:51-927220 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:51-927409 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:11:51-927588 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:51-927772 util-scheduler-8627 DEBUG Canceling task: 744 / 0x4e61600
Jul 07 21:11:51-928006 util-scheduler-8627 DEBUG Adding task: 759 / 0x4e61600
Jul 07 21:11:51-928258 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:51-928428 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:51-928608 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:11:51-928806 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:51-928980 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:11:51-929154 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:11:51-929376 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:51-929582 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:11:51-929765 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:11:51-929944 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:51-930134 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:11:51-930383 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:53-438498 util-scheduler-8627 DEBUG Checking readiness of task: 758 / 0x4661f98
Jul 07 21:11:53-438845 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:53-439666 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:53-439897 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:53-440134 util-scheduler-8627 DEBUG Running task: 720 / 0x4d63d80
Jul 07 21:11:53-440372 cadet-tun-8627 INFO Re-key Tunnel V8XX
Jul 07 21:11:53-440618 cadet-tun-8627 DEBUG  kx started 155 s ago
Jul 07 21:11:53-440865 cadet-tun-8627 INFO ===> EPHM for V8XX
Jul 07 21:11:53-441066 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:53-441291 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:53-441525 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:53-441705 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:53-441928 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:53-442218 cadet-con-8627 INFO --> {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (196 bytes)
Jul 07 21:11:53-442433 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:11:53-442683 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:53-442893 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:53-443209 cadet-p2p-8627 INFO que {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 196)
Jul 07 21:11:53-443408 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:53-443632 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:53-443816 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:53-443991 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:53-444215 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 196 bytes
Jul 07 21:11:53-444429 core-api-8627 DEBUG Asking core for transmission of 196 bytes to `V8XX'
Jul 07 21:11:53-444652 util-scheduler-8627 DEBUG Adding task: 760 / 0x4e607e8
Jul 07 21:11:53-444833 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:53-445035 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:53-445230 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:53-445406 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:53-445644 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:53-445866 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:53-446046 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:53-446245 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:53-446449 cadet-tun-8627 INFO ===> PING for V8XX
Jul 07 21:11:53-446757 cadet-tun-8627 DEBUG   sending 3700535163
Jul 07 21:11:53-446958 cadet-tun-8627 DEBUG   towards V8XX
Jul 07 21:11:53-447128 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:53-447309 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:53-450846 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:53-452154 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:53-452335 cadet-tun-8627 DEBUG   e sending 3503528825
Jul 07 21:11:53-452545 cadet-tun-8627 DEBUG   e towards H8QD
Jul 07 21:11:53-452744 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:53-452943 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:53-453171 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:53-453374 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:53-453594 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:53-453868 cadet-con-8627 INFO --> {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (80 bytes)
Jul 07 21:11:53-454066 cadet-con-8627 DEBUG   C_P+ 0x4e61600 1
Jul 07 21:11:53-454300 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:53-454507 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:53-454814 cadet-p2p-8627 INFO que {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 80)
Jul 07 21:11:53-455012 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:53-455234 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:53-455417 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:53-455591 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:53-455806 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:53-456008 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:53-456182 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:53-456386 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:53-456623 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:53-456818 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:53-456995 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:53-457249 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:53-457443 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:53-457621 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:53-457818 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:53-458066 cadet-tun-8627 DEBUG   next call in 5 s
Jul 07 21:11:53-458270 util-scheduler-8627 DEBUG Adding task: 761 / 0x4d63d80
Jul 07 21:11:53-458542 util-scheduler-8627 DEBUG Checking readiness of task: 758 / 0x4661f98
Jul 07 21:11:53-458736 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:53-458925 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:53-459114 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:53-459305 util-scheduler-8627 DEBUG Running task: 760 / 0x4e607e8
Jul 07 21:11:53-459513 util-scheduler-8627 DEBUG Adding task: 762 / 0x4e607e8
Jul 07 21:11:53-459733 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:53-459936 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:53-460144 util-scheduler-8627 DEBUG Adding task: 763 / 0x4661f98
Jul 07 21:11:53-460385 util-scheduler-8627 DEBUG Checking readiness of task: 763 / 0x4661f98
Jul 07 21:11:53-460578 util-scheduler-8627 DEBUG Checking readiness of task: 758 / 0x4661f98
Jul 07 21:11:53-460767 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:53-460956 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:53-461235 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:53-461432 util-scheduler-8627 DEBUG Running task: 763 / 0x4661f98
Jul 07 21:11:53-461618 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:53-461798 util-8627 DEBUG process_notify is running
Jul 07 21:11:53-461971 util-8627 DEBUG client_notify is running
Jul 07 21:11:53-462150 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:53-462345 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:53-462534 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:53-462788 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:54-524508 util-scheduler-8627 DEBUG Checking readiness of task: 758 / 0x4661f98
Jul 07 21:11:54-524798 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:54-524994 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:54-525186 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:54-525407 util-scheduler-8627 DEBUG Running task: 758 / 0x4661f98
Jul 07 21:11:54-525824 util-8627 DEBUG receive_ready read 232/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:54-526067 util-scheduler-8627 DEBUG Adding task: 764 / 0x4662140
Jul 07 21:11:54-526328 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:54-526519 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:54-526709 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:54-526899 util-scheduler-8627 DEBUG Running task: 764 / 0x4662140
Jul 07 21:11:54-527091 util-8627 DEBUG Received message of type 70 and size 232 from core service.
Jul 07 21:11:54-527289 core-api-8627 DEBUG Processing message of type 70 and size 232 from core service
Jul 07 21:11:54-527516 core-api-8627 DEBUG Received message of type 262 and size 196 from peer `V8XX'
Jul 07 21:11:54-527774 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:54-528013 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:54-528243 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:54-528450 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:54-528694 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:54-528901 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:54-529087 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:54-529310 util-scheduler-8627 DEBUG Canceling task: 750 / 0x4e61600
Jul 07 21:11:54-529531 util-scheduler-8627 DEBUG Adding task: 765 / 0x4e61600
Jul 07 21:11:54-529710 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:54-529965 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:54-530176 util-scheduler-8627 DEBUG Adding task: 766 / 0x4d50e20
Jul 07 21:11:54-530357 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:54-530556 cadet-tun-8627 INFO <=== EPHM for V8XX
Jul 07 21:11:55-140774 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:55-141178 util-scheduler-8627 DEBUG Adding task: 767 / 0x4661f98
Jul 07 21:11:55-141499 util-scheduler-8627 DEBUG Checking readiness of task: 767 / 0x4661f98
Jul 07 21:11:55-141701 util-scheduler-8627 DEBUG Checking readiness of task: 766 / 0x4d50e20
Jul 07 21:11:55-141894 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:55-142085 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:55-142287 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:55-142482 util-scheduler-8627 DEBUG Running task: 766 / 0x4d50e20
Jul 07 21:11:55-142673 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:55-142853 util-8627 DEBUG process_notify is running
Jul 07 21:11:55-143026 util-8627 DEBUG client_notify is running
Jul 07 21:11:55-143291 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:55-143648 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:55-143863 util-scheduler-8627 DEBUG Running task: 767 / 0x4661f98
Jul 07 21:11:55-144274 util-8627 DEBUG receive_ready read 200/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:55-144518 util-scheduler-8627 DEBUG Adding task: 768 / 0x4662140
Jul 07 21:11:55-144768 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:55-144960 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:55-145149 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:55-145365 util-scheduler-8627 DEBUG Running task: 768 / 0x4662140
Jul 07 21:11:55-145555 util-8627 DEBUG Received message of type 70 and size 116 from core service.
Jul 07 21:11:55-145757 core-api-8627 DEBUG Processing message of type 70 and size 116 from core service
Jul 07 21:11:55-145987 core-api-8627 DEBUG Received message of type 262 and size 80 from peer `V8XX'
Jul 07 21:11:55-146250 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:55-146493 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:55-146723 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:55-146931 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:55-147319 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:55-147573 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:55-147762 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:55-147950 util-scheduler-8627 DEBUG Canceling task: 765 / 0x4e61600
Jul 07 21:11:55-148172 util-scheduler-8627 DEBUG Adding task: 769 / 0x4e61600
Jul 07 21:11:55-148351 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:55-148605 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:55-148828 util-scheduler-8627 DEBUG Adding task: 770 / 0x4d50e20
Jul 07 21:11:55-149009 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:55-149231 cadet-tun-8627 INFO <=== PING for V8XX
Jul 07 21:11:55-149419 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:55-149592 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:55-149757 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:55-153654 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:55-155023 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:55-155243 cadet-tun-8627 INFO ===> PONG for V8XX
Jul 07 21:11:55-155540 cadet-tun-8627 DEBUG   sending 679485456
Jul 07 21:11:55-155715 cadet-tun-8627 DEBUG   t_encrypt start
Jul 07 21:11:55-155901 cadet-tun-8627 INFO   ENC with key 0D5E8DSS
Jul 07 21:11:55-158981 cadet-tun-8627 DEBUG   t_encrypt IV derived
Jul 07 21:11:55-159564 cadet-tun-8627 DEBUG   t_encrypt end
Jul 07 21:11:55-159741 cadet-tun-8627 DEBUG   e sending 3254184085
Jul 07 21:11:55-159948 cadet-tun-8627 DEBUG GMT KX on Tunnel V8XX
Jul 07 21:11:55-160149 cadet-tun-8627 DEBUG tunnel_get_connection V8XX
Jul 07 21:11:55-160378 cadet-tun-8627 DEBUG   connection MCZ5X28Z (->V8XX): 3
Jul 07 21:11:55-160560 cadet-tun-8627 DEBUG     q_n 0, 
Jul 07 21:11:55-160780 cadet-tun-8627 DEBUG  selected: connection MCZ5X28Z (->V8XX)
Jul 07 21:11:55-161060 cadet-con-8627 INFO --> {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (48 bytes)
Jul 07 21:11:55-161287 cadet-con-8627 DEBUG   C_P+ 0x4e61600 2
Jul 07 21:11:55-161523 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:55-161729 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:55-162040 cadet-p2p-8627 INFO que {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 48)
Jul 07 21:11:55-162239 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:11:55-162462 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:11:55-162645 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:11:55-163058 cadet-con-8627 DEBUG  sendable
Jul 07 21:11:55-163385 cadet-p2p-8627 DEBUG core tmt rdy towards V8XX already called
Jul 07 21:11:55-163754 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:55-164022 cadet-p2p-8627 DEBUG QQQ  queue length: 3
Jul 07 21:11:55-164199 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:55-164440 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:55-164637 cadet-p2p-8627 DEBUG QQQ    payload {      KX_EPHEMERAL}, 0
Jul 07 21:11:55-164816 cadet-p2p-8627 DEBUG QQQ    size: 196 bytes
Jul 07 21:11:55-165051 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:55-165271 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:55-165449 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:55-165683 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:55-165877 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:55-166054 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:55-166253 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:55-166479 util-scheduler-8627 DEBUG Adding task: 771 / 0x4662140
Jul 07 21:11:55-166747 util-scheduler-8627 DEBUG Checking readiness of task: 770 / 0x4d50e20
Jul 07 21:11:55-166944 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:55-167135 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:55-167325 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:55-167520 util-scheduler-8627 DEBUG Running task: 770 / 0x4d50e20
Jul 07 21:11:55-167706 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:55-167883 util-8627 DEBUG process_notify is running
Jul 07 21:11:55-168054 util-8627 DEBUG client_notify is running
Jul 07 21:11:55-168278 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:55-168671 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:55-168886 util-scheduler-8627 DEBUG Running task: 771 / 0x4662140
Jul 07 21:11:55-169079 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:11:55-169300 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:11:55-169517 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:11:55-169777 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:11:55-170011 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:11:55-170238 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:55-170447 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:11:55-170689 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:11:55-170896 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:11:55-171082 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:11:55-171267 util-scheduler-8627 DEBUG Canceling task: 769 / 0x4e61600
Jul 07 21:11:55-171486 util-scheduler-8627 DEBUG Adding task: 772 / 0x4e61600
Jul 07 21:11:55-171665 cadet-con-8627 DEBUG   message for us!
Jul 07 21:11:55-171912 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:11:55-172135 util-scheduler-8627 DEBUG Adding task: 773 / 0x4d50e20
Jul 07 21:11:55-172316 cadet-tun-8627 DEBUG kx message received
Jul 07 21:11:55-173699 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:11:55-174528 cadet-tun-8627 DEBUG   t_decrypt with 45RE1JY5
Jul 07 21:11:55-174712 cadet-tun-8627 DEBUG   decrypt start
Jul 07 21:11:55-174882 cadet-tun-8627 DEBUG   decrypt iv
Jul 07 21:11:55-178148 cadet-tun-8627 DEBUG   decrypt iv done
Jul 07 21:11:55-178827 cadet-tun-8627 DEBUG   decrypt end
Jul 07 21:11:55-179440 util-scheduler-8627 DEBUG Canceling task: 761 / 0x4d63d80
Jul 07 21:11:55-181443 util-scheduler-8627 DEBUG Adding task: 774 / 0x4d63d80
Jul 07 21:11:55-183435 cadet-tun-8627 DEBUG Tunnel V8XX estate was CADET_TUNNEL_KEY_PING
Jul 07 21:11:55-184889 cadet-tun-8627 DEBUG Tunnel V8XX estate is now CADET_TUNNEL_KEY_OK
Jul 07 21:11:55-187005 cadet-tun-8627 DEBUG GCT_send_queued_data on tunnel V8XX
Jul 07 21:11:55-187987 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 21:11:55-188178 cadet-tun-8627 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 21:11:55-188366 cadet-tun-8627 DEBUG TTT  kx_ctx 0x4d7b4d0, rekey_task 0
Jul 07 21:11:55-188551 cadet-tun-8627 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 21:11:55-188730 cadet-tun-8627 DEBUG TTT  destroy 0
Jul 07 21:11:55-188911 cadet-tun-8627 DEBUG TTT  channels:
Jul 07 21:11:55-189079 cadet-tun-8627 DEBUG TTT  connections:
Jul 07 21:11:55-192268 cadet-tun-8627 DEBUG TTT  - MCZ5X28Z (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 21:11:55-192693 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL END
Jul 07 21:11:55-193959 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 21:11:55-194145 cadet-tun-8627 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 21:11:55-194331 cadet-tun-8627 DEBUG TTT  kx_ctx 0x4d7b4d0, rekey_task 0
Jul 07 21:11:55-194512 cadet-tun-8627 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 21:11:55-194704 cadet-tun-8627 DEBUG TTT  destroy 0
Jul 07 21:11:55-194875 cadet-tun-8627 DEBUG TTT  channels:
Jul 07 21:11:55-195040 cadet-tun-8627 DEBUG TTT  connections:
Jul 07 21:11:55-195427 cadet-tun-8627 DEBUG TTT  - MCZ5X28Z (->V8XX) [3] buf: 11/11 (qn 0/0)
Jul 07 21:11:55-195618 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL END
Jul 07 21:11:55-197897 cadet-tun-8627 DEBUG   buffer space: 11
Jul 07 21:11:55-198891 cadet-tun-8627 DEBUG   tq head: (nil)
Jul 07 21:11:55-200244 cadet-tun-8627 DEBUG GCT_send_queued_data end
Jul 07 21:11:55-200887 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:55-201114 util-scheduler-8627 DEBUG Adding task: 775 / 0x4661f98
Jul 07 21:11:55-201431 util-scheduler-8627 DEBUG Checking readiness of task: 775 / 0x4661f98
Jul 07 21:11:55-201628 util-scheduler-8627 DEBUG Checking readiness of task: 773 / 0x4d50e20
Jul 07 21:11:55-201837 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:55-202029 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:55-202219 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:55-202444 util-scheduler-8627 DEBUG Running task: 773 / 0x4d50e20
Jul 07 21:11:55-202635 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:11:55-202814 util-8627 DEBUG process_notify is running
Jul 07 21:11:55-202986 util-8627 DEBUG client_notify is running
Jul 07 21:11:55-203208 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:11:55-203544 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:11:57-426824 util-scheduler-8627 DEBUG Checking readiness of task: 775 / 0x4661f98
Jul 07 21:11:57-427205 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-427402 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-427594 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-427792 util-scheduler-8627 DEBUG Running task: 775 / 0x4661f98
Jul 07 21:11:57-428218 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:57-428476 util-scheduler-8627 DEBUG Adding task: 776 / 0x4662140
Jul 07 21:11:57-428754 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-428946 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-429136 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-429364 util-scheduler-8627 DEBUG Running task: 776 / 0x4662140
Jul 07 21:11:57-429557 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:57-429758 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:57-430017 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:57-430226 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-430433 util-scheduler-8627 DEBUG Adding task: 777 / 0x4661f98
Jul 07 21:11:57-430621 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:57-430827 util-scheduler-8627 DEBUG Adding task: 778 / 0x4661f98
Jul 07 21:11:57-431068 util-scheduler-8627 DEBUG Checking readiness of task: 778 / 0x4661f98
Jul 07 21:11:57-431277 util-scheduler-8627 DEBUG Checking readiness of task: 777 / 0x4661f98
Jul 07 21:11:57-431468 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-431657 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-431846 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-432038 util-scheduler-8627 DEBUG Running task: 777 / 0x4661f98
Jul 07 21:11:57-432224 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-432401 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-432573 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-432763 util-scheduler-8627 DEBUG Canceling task: 762 / 0x4e607e8
Jul 07 21:11:57-432987 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 196 bytes.
Jul 07 21:11:57-433235 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:57-433477 cadet-p2p-8627 DEBUG Checking 0x5b54040 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-433711 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:57-433889 cadet-p2p-8627 DEBUG   size 196 ok
Jul 07 21:11:57-434079 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:57-434367 cadet-p2p-8627 INFO snd {                KX} ({      KX_EPHEMERAL} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 196)
Jul 07 21:11:57-434562 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:57-434742 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:57-434929 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:57-435118 cadet-con-8627 DEBUG  C_P- 0x4e61600 3
Jul 07 21:11:57-435297 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:57-435494 util-scheduler-8627 DEBUG Canceling task: 759 / 0x4e61600
Jul 07 21:11:57-435706 util-scheduler-8627 DEBUG Adding task: 779 / 0x4e61600
Jul 07 21:11:57-435958 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:57-436128 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:57-436349 cadet-p2p-8627 DEBUG Checking 0x5b5aa20 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-436586 cadet-p2p-8627 DEBUG Checking 0x5b5aa20 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-436765 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:57-436971 core-api-8627 DEBUG Asking core for transmission of 80 bytes to `V8XX'
Jul 07 21:11:57-437183 util-scheduler-8627 DEBUG Adding task: 780 / 0x4e607e8
Jul 07 21:11:57-437389 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:57-437566 cadet-p2p-8627 DEBUG   return 196
Jul 07 21:11:57-437764 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:57-437939 cadet-p2p-8627 DEBUG QQQ  queue length: 2
Jul 07 21:11:57-438113 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:57-438350 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:57-438545 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PING}, 0
Jul 07 21:11:57-438722 cadet-p2p-8627 DEBUG QQQ    size: 80 bytes
Jul 07 21:11:57-438955 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:57-439148 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:57-439326 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:57-439533 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:57-439739 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 196 bytes.
Jul 07 21:11:57-439923 core-api-8627 DEBUG Produced SEND message to core with 196 bytes payload
Jul 07 21:11:57-440126 util-scheduler-8627 DEBUG Adding task: 781 / 0x4e607e8
Jul 07 21:11:57-440360 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:57-440556 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-440757 util-scheduler-8627 DEBUG Adding task: 782 / 0x4661f98
Jul 07 21:11:57-440956 util-8627 DEBUG Transmitting message of type 76 and size 252 to core service.
Jul 07 21:11:57-441233 util-8627 DEBUG Connection transmitted 252/252 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:57-441433 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:57-441676 util-scheduler-8627 DEBUG Checking readiness of task: 782 / 0x4661f98
Jul 07 21:11:57-441868 util-scheduler-8627 DEBUG Checking readiness of task: 778 / 0x4661f98
Jul 07 21:11:57-442058 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-442246 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-442434 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-442624 util-scheduler-8627 DEBUG Running task: 782 / 0x4661f98
Jul 07 21:11:57-442811 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-442985 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-443155 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-443332 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:57-443525 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:57-443713 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:57-443955 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:57-444161 util-scheduler-8627 DEBUG Running task: 780 / 0x4e607e8
Jul 07 21:11:57-444353 util-scheduler-8627 DEBUG Canceling task: 781 / 0x4e607e8
Jul 07 21:11:57-444563 util-scheduler-8627 DEBUG Adding task: 783 / 0x4e607e8
Jul 07 21:11:57-444778 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:57-444970 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-445167 util-scheduler-8627 DEBUG Adding task: 784 / 0x4661f98
Jul 07 21:11:57-445429 util-scheduler-8627 DEBUG Checking readiness of task: 784 / 0x4661f98
Jul 07 21:11:57-445620 util-scheduler-8627 DEBUG Checking readiness of task: 778 / 0x4661f98
Jul 07 21:11:57-445809 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-445997 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-446186 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-446376 util-scheduler-8627 DEBUG Running task: 784 / 0x4661f98
Jul 07 21:11:57-446560 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-446735 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-446905 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-447080 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:57-447268 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:57-447455 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:57-447697 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:57-683790 util-scheduler-8627 DEBUG Checking readiness of task: 778 / 0x4661f98
Jul 07 21:11:57-684154 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-684350 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-684542 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-684756 util-scheduler-8627 DEBUG Running task: 778 / 0x4661f98
Jul 07 21:11:57-685179 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:11:57-685473 util-scheduler-8627 DEBUG Adding task: 785 / 0x4662140
Jul 07 21:11:57-685774 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-685966 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-686157 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-686347 util-scheduler-8627 DEBUG Running task: 785 / 0x4662140
Jul 07 21:11:57-686539 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:11:57-686737 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:11:57-686968 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:11:57-687174 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-687380 util-scheduler-8627 DEBUG Adding task: 786 / 0x4661f98
Jul 07 21:11:57-687566 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:11:57-687772 util-scheduler-8627 DEBUG Adding task: 787 / 0x4661f98
Jul 07 21:11:57-688012 util-scheduler-8627 DEBUG Checking readiness of task: 787 / 0x4661f98
Jul 07 21:11:57-688204 util-scheduler-8627 DEBUG Checking readiness of task: 786 / 0x4661f98
Jul 07 21:11:57-688395 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-688584 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-688774 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-688966 util-scheduler-8627 DEBUG Running task: 786 / 0x4661f98
Jul 07 21:11:57-689151 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-689357 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-689529 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-689716 util-scheduler-8627 DEBUG Canceling task: 783 / 0x4e607e8
Jul 07 21:11:57-689940 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 80 bytes.
Jul 07 21:11:57-690160 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:11:57-690399 cadet-p2p-8627 DEBUG Checking 0x5b5aa20 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-690633 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:11:57-690811 cadet-p2p-8627 DEBUG   size 80 ok
Jul 07 21:11:57-690999 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:11:57-691282 cadet-p2p-8627 INFO snd {                KX} ({           KX_PING} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 80)
Jul 07 21:11:57-691477 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:11:57-691656 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:11:57-691844 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:11:57-692033 cadet-con-8627 DEBUG  C_P- 0x4e61600 2
Jul 07 21:11:57-692210 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:11:57-692395 util-scheduler-8627 DEBUG Canceling task: 779 / 0x4e61600
Jul 07 21:11:57-692605 util-scheduler-8627 DEBUG Adding task: 788 / 0x4e61600
Jul 07 21:11:57-692872 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:11:57-693042 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:11:57-693288 cadet-p2p-8627 DEBUG Checking 0x5daae70 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-693528 cadet-p2p-8627 DEBUG Checking 0x5daae70 towards MCZ5X28Z (->V8XX)
Jul 07 21:11:57-693707 cadet-p2p-8627 DEBUG   more data!
Jul 07 21:11:57-693924 core-api-8627 DEBUG Asking core for transmission of 48 bytes to `V8XX'
Jul 07 21:11:57-694137 util-scheduler-8627 DEBUG Adding task: 789 / 0x4e607e8
Jul 07 21:11:57-694315 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:11:57-694491 cadet-p2p-8627 DEBUG   return 80
Jul 07 21:11:57-694689 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:11:57-694864 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:11:57-695037 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:11:57-695275 cadet-p2p-8627 DEBUG QQQ  - {                KX} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:11:57-695472 cadet-p2p-8627 DEBUG QQQ    payload {           KX_PONG}, 0
Jul 07 21:11:57-695650 cadet-p2p-8627 DEBUG QQQ    size: 48 bytes
Jul 07 21:11:57-695864 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:11:57-696069 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 80 bytes.
Jul 07 21:11:57-696253 core-api-8627 DEBUG Produced SEND message to core with 80 bytes payload
Jul 07 21:11:57-696453 util-scheduler-8627 DEBUG Adding task: 790 / 0x4e607e8
Jul 07 21:11:57-696672 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:57-696866 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-697066 util-scheduler-8627 DEBUG Adding task: 791 / 0x4661f98
Jul 07 21:11:57-697292 util-8627 DEBUG Transmitting message of type 76 and size 136 to core service.
Jul 07 21:11:57-697547 util-8627 DEBUG Connection transmitted 136/136 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:57-697744 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4661f98).
Jul 07 21:11:57-697986 util-scheduler-8627 DEBUG Checking readiness of task: 791 / 0x4661f98
Jul 07 21:11:57-698178 util-scheduler-8627 DEBUG Checking readiness of task: 787 / 0x4661f98
Jul 07 21:11:57-698368 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-698558 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-698747 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-698939 util-scheduler-8627 DEBUG Running task: 791 / 0x4661f98
Jul 07 21:11:57-699124 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-699300 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-699470 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-699647 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:57-699841 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:57-700028 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:57-700258 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:11:57-700464 util-scheduler-8627 DEBUG Running task: 789 / 0x4e607e8
Jul 07 21:11:57-700654 util-scheduler-8627 DEBUG Canceling task: 790 / 0x4e607e8
Jul 07 21:11:57-700865 util-scheduler-8627 DEBUG Adding task: 792 / 0x4e607e8
Jul 07 21:11:57-701079 core-api-8627 DEBUG Adding SEND REQUEST for peer `V8XX' to message queue
Jul 07 21:11:57-701319 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:11:57-701526 util-scheduler-8627 DEBUG Adding task: 793 / 0x4661f98
Jul 07 21:11:57-701763 util-scheduler-8627 DEBUG Checking readiness of task: 793 / 0x4661f98
Jul 07 21:11:57-701954 util-scheduler-8627 DEBUG Checking readiness of task: 787 / 0x4661f98
Jul 07 21:11:57-702144 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:11:57-702333 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:11:57-702521 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:11:57-702711 util-scheduler-8627 DEBUG Running task: 793 / 0x4661f98
Jul 07 21:11:57-702897 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:11:57-703071 util-8627 DEBUG process_notify is running
Jul 07 21:11:57-703239 util-8627 DEBUG client_notify is running
Jul 07 21:11:57-703414 core-api-8627 DEBUG Transmitting control message with 56 bytes of type 74 to core.
Jul 07 21:11:57-703603 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:11:57-703789 util-8627 DEBUG Transmitting message of type 74 and size 56 to core service.
Jul 07 21:11:57-704031 util-8627 DEBUG Connection transmitted 56/56 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:12:00-955951 util-scheduler-8627 DEBUG Checking readiness of task: 787 / 0x4661f98
Jul 07 21:12:00-956342 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:00-956544 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:00-956738 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:00-956968 util-scheduler-8627 DEBUG Running task: 787 / 0x4661f98
Jul 07 21:12:00-957440 util-8627 DEBUG receive_ready read 40/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:00-957702 util-scheduler-8627 DEBUG Adding task: 794 / 0x4662140
Jul 07 21:12:00-957980 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:00-958178 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:00-958370 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:00-958566 util-scheduler-8627 DEBUG Running task: 794 / 0x4662140
Jul 07 21:12:00-958757 util-8627 DEBUG Received message of type 75 and size 40 from core service.
Jul 07 21:12:00-958957 core-api-8627 DEBUG Processing message of type 75 and size 40 from core service
Jul 07 21:12:00-959189 core-api-8627 DEBUG Received notification about transmission readiness to `V8XX'.
Jul 07 21:12:00-959397 util-8627 DEBUG Scheduling transmission (0x4661f98).
Jul 07 21:12:00-959604 util-scheduler-8627 DEBUG Adding task: 795 / 0x4661f98
Jul 07 21:12:00-959792 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:00-960006 util-scheduler-8627 DEBUG Adding task: 796 / 0x4661f98
Jul 07 21:12:00-961701 util-scheduler-8627 DEBUG Checking readiness of task: 796 / 0x4661f98
Jul 07 21:12:00-961944 util-scheduler-8627 DEBUG Checking readiness of task: 795 / 0x4661f98
Jul 07 21:12:00-962145 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:00-962345 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:00-962539 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:00-962736 util-scheduler-8627 DEBUG Running task: 795 / 0x4661f98
Jul 07 21:12:00-962924 util-8627 DEBUG transmit_ready running (0x4661f98).
Jul 07 21:12:00-963102 util-8627 DEBUG process_notify is running
Jul 07 21:12:00-963274 util-8627 DEBUG client_notify is running
Jul 07 21:12:00-963461 util-scheduler-8627 DEBUG Canceling task: 792 / 0x4e607e8
Jul 07 21:12:00-963694 core-api-8627 DEBUG Transmitting SEND request to `V8XX' with 48 bytes.
Jul 07 21:12:00-963913 cadet-p2p-8627 DEBUG Queue send towards V8XX (max 196)
Jul 07 21:12:00-964153 cadet-p2p-8627 DEBUG Checking 0x5daae70 towards MCZ5X28Z (->V8XX)
Jul 07 21:12:00-964385 cadet-p2p-8627 DEBUG   on connection MCZ5X28Z (->V8XX) FWD
Jul 07 21:12:00-964562 cadet-p2p-8627 DEBUG   size 48 ok
Jul 07 21:12:00-964752 cadet-p2p-8627 DEBUG   raw {                KX}
Jul 07 21:12:00-965062 cadet-p2p-8627 INFO snd {                KX} ({           KX_PONG} 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD (size 48)
Jul 07 21:12:00-965283 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:12:00-965463 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:12:00-965650 cadet-con-8627 DEBUG  sent FWD {                KX}
Jul 07 21:12:00-965838 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:12:00-966015 cadet-con-8627 DEBUG Connection FWD reset timeout
Jul 07 21:12:00-966200 util-scheduler-8627 DEBUG Canceling task: 788 / 0x4e61600
Jul 07 21:12:00-966413 util-scheduler-8627 DEBUG Adding task: 797 / 0x4e61600
Jul 07 21:12:00-966663 cadet-con-8627 DEBUG next keepalive in 5 m
Jul 07 21:12:00-966833 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:12:00-967013 cadet-p2p-8627 DEBUG   return 48
Jul 07 21:12:00-967210 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:12:00-967384 cadet-p2p-8627 DEBUG QQQ  queue length: 0
Jul 07 21:12:00-967558 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: (nil)
Jul 07 21:12:00-967770 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:12:00-967974 core-api-8627 DEBUG Transmitting SEND request to `V8XX' yielded 48 bytes.
Jul 07 21:12:00-968161 core-api-8627 DEBUG Produced SEND message to core with 48 bytes payload
Jul 07 21:12:00-968340 core-api-8627 DEBUG Request queue empty, not processing queue
Jul 07 21:12:00-968530 util-8627 DEBUG Transmitting message of type 76 and size 104 to core service.
Jul 07 21:12:00-969304 util-8627 DEBUG Connection transmitted 104/104 bytes to `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)
Jul 07 21:12:01-599106 util-scheduler-8627 DEBUG Checking readiness of task: 796 / 0x4661f98
Jul 07 21:12:01-599486 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:01-599685 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:01-599880 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:01-600079 util-scheduler-8627 DEBUG Running task: 796 / 0x4661f98
Jul 07 21:12:01-600505 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:01-600763 util-scheduler-8627 DEBUG Adding task: 798 / 0x4662140
Jul 07 21:12:01-601040 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:01-601262 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:01-601454 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:01-601644 util-scheduler-8627 DEBUG Running task: 798 / 0x4662140
Jul 07 21:12:01-601835 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:01-602035 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:01-602264 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:01-602527 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:01-602769 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:01-602999 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:01-603208 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:01-603455 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:01-603664 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:01-603851 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:01-604038 util-scheduler-8627 DEBUG Canceling task: 772 / 0x4e61600
Jul 07 21:12:01-604280 util-scheduler-8627 DEBUG Adding task: 799 / 0x4e61600
Jul 07 21:12:01-604459 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:01-604719 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:01-604936 util-scheduler-8627 DEBUG Adding task: 800 / 0x4d50e20
Jul 07 21:12:01-605119 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:01-605644 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:01-606356 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:01-606573 util-scheduler-8627 DEBUG Adding task: 801 / 0x4661f98
Jul 07 21:12:01-606829 util-scheduler-8627 DEBUG Checking readiness of task: 801 / 0x4661f98
Jul 07 21:12:01-607024 util-scheduler-8627 DEBUG Checking readiness of task: 800 / 0x4d50e20
Jul 07 21:12:01-607217 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:01-607408 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:01-607599 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:01-607793 util-scheduler-8627 DEBUG Running task: 800 / 0x4d50e20
Jul 07 21:12:01-607979 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:01-608156 util-8627 DEBUG process_notify is running
Jul 07 21:12:01-608330 util-8627 DEBUG client_notify is running
Jul 07 21:12:01-608567 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:01-608776 util-scheduler-8627 DEBUG Adding task: 802 / 0x4d50e20
Jul 07 21:12:01-608978 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:01-609301 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:01-609502 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:01-609743 util-scheduler-8627 DEBUG Checking readiness of task: 802 / 0x4d50e20
Jul 07 21:12:01-609936 util-scheduler-8627 DEBUG Checking readiness of task: 801 / 0x4661f98
Jul 07 21:12:01-610154 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:01-610344 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:01-610534 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:01-610724 util-scheduler-8627 DEBUG Running task: 802 / 0x4d50e20
Jul 07 21:12:01-610907 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:01-611097 util-8627 DEBUG process_notify is running
Jul 07 21:12:01-611266 util-8627 DEBUG client_notify is running
Jul 07 21:12:01-611477 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:01-611783 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:05-024524 util-scheduler-8627 DEBUG Checking readiness of task: 801 / 0x4661f98
Jul 07 21:12:05-024916 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:05-025116 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:05-025339 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:05-025569 util-scheduler-8627 DEBUG Running task: 801 / 0x4661f98
Jul 07 21:12:05-025998 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:05-026260 util-scheduler-8627 DEBUG Adding task: 803 / 0x4662140
Jul 07 21:12:05-026542 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:05-026736 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:05-026929 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:05-027122 util-scheduler-8627 DEBUG Running task: 803 / 0x4662140
Jul 07 21:12:05-027326 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:05-027530 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:05-027763 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:05-028030 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:05-028275 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:05-028506 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:05-028716 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:05-028970 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:05-029180 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:05-029398 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:05-029588 util-scheduler-8627 DEBUG Canceling task: 799 / 0x4e61600
Jul 07 21:12:05-029813 util-scheduler-8627 DEBUG Adding task: 804 / 0x4e61600
Jul 07 21:12:05-029996 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:05-030257 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:05-030475 util-scheduler-8627 DEBUG Adding task: 805 / 0x4d50e20
Jul 07 21:12:05-030660 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:05-030862 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:05-031079 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:05-031287 util-scheduler-8627 DEBUG Adding task: 806 / 0x4661f98
Jul 07 21:12:05-031538 util-scheduler-8627 DEBUG Checking readiness of task: 806 / 0x4661f98
Jul 07 21:12:05-031733 util-scheduler-8627 DEBUG Checking readiness of task: 805 / 0x4d50e20
Jul 07 21:12:05-031926 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:05-032118 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:05-032310 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:05-032503 util-scheduler-8627 DEBUG Running task: 805 / 0x4d50e20
Jul 07 21:12:05-032690 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:05-032869 util-8627 DEBUG process_notify is running
Jul 07 21:12:05-033044 util-8627 DEBUG client_notify is running
Jul 07 21:12:05-033336 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:05-033546 util-scheduler-8627 DEBUG Adding task: 807 / 0x4d50e20
Jul 07 21:12:05-033750 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:05-034089 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:05-034292 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:05-034548 util-scheduler-8627 DEBUG Checking readiness of task: 807 / 0x4d50e20
Jul 07 21:12:05-034744 util-scheduler-8627 DEBUG Checking readiness of task: 806 / 0x4661f98
Jul 07 21:12:05-034935 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:05-035126 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:05-035317 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:05-035509 util-scheduler-8627 DEBUG Running task: 807 / 0x4d50e20
Jul 07 21:12:05-035695 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:05-035871 util-8627 DEBUG process_notify is running
Jul 07 21:12:05-036042 util-8627 DEBUG client_notify is running
Jul 07 21:12:05-036253 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:05-036540 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:08-322953 util-scheduler-8627 DEBUG Checking readiness of task: 806 / 0x4661f98
Jul 07 21:12:08-323317 util-scheduler-8627 DEBUG Checking readiness of task: 693 / 0x465ed58
Jul 07 21:12:08-323517 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:08-323711 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:08-323909 util-scheduler-8627 DEBUG Running task: 693 / 0x465ed58
Jul 07 21:12:08-324336 util-8627 DEBUG receive_ready read 130/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:12:08-324596 util-scheduler-8627 DEBUG Adding task: 808 / 0x465ef00
Jul 07 21:12:08-324877 util-scheduler-8627 DEBUG Checking readiness of task: 806 / 0x4661f98
Jul 07 21:12:08-325070 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:08-325286 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:08-325478 util-scheduler-8627 DEBUG Running task: 808 / 0x465ef00
Jul 07 21:12:08-325672 util-8627 DEBUG Received message of type 332 and size 130 from peerinfo service.
Jul 07 21:12:08-325914 nse-api-8627 DEBUG Received information about peer `WAKN' from peerinfo database
Jul 07 21:12:08-326207 cadet-hll-8627 DEBUG  hello for WAKN (90 bytes), expires on Tue Jul 08 09:12:08 2014
Jul 07 21:12:08-326436 cadet-p2p-8627 DEBUG set hello for WAKN
Jul 07 21:12:08-326740 cadet-p2p-8627 DEBUG  merge into 0x5dbb878 (90 bytes)
Jul 07 21:12:08-326939 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:08-327157 util-scheduler-8627 DEBUG Adding task: 809 / 0x465ed58
Jul 07 21:12:10-591953 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:10-592334 util-scheduler-8627 DEBUG Checking readiness of task: 806 / 0x4661f98
Jul 07 21:12:10-592535 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:10-592728 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:10-592926 util-scheduler-8627 DEBUG Running task: 806 / 0x4661f98
Jul 07 21:12:10-593380 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:10-593641 util-scheduler-8627 DEBUG Adding task: 810 / 0x4662140
Jul 07 21:12:10-593919 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:10-594112 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:10-594306 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:10-594533 util-scheduler-8627 DEBUG Running task: 810 / 0x4662140
Jul 07 21:12:10-594726 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:10-594928 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:10-595160 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:10-595425 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:10-595670 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:10-595918 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:10-596127 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:10-596375 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:10-596583 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:10-596771 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:10-596985 util-scheduler-8627 DEBUG Canceling task: 804 / 0x4e61600
Jul 07 21:12:10-597238 util-scheduler-8627 DEBUG Adding task: 811 / 0x4e61600
Jul 07 21:12:10-597421 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:10-597682 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:10-597898 util-scheduler-8627 DEBUG Adding task: 812 / 0x4d50e20
Jul 07 21:12:10-598080 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:10-598280 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:10-598497 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:10-598704 util-scheduler-8627 DEBUG Adding task: 813 / 0x4661f98
Jul 07 21:12:10-598956 util-scheduler-8627 DEBUG Checking readiness of task: 813 / 0x4661f98
Jul 07 21:12:10-599150 util-scheduler-8627 DEBUG Checking readiness of task: 812 / 0x4d50e20
Jul 07 21:12:10-599342 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:10-599533 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:10-599722 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:10-599915 util-scheduler-8627 DEBUG Running task: 812 / 0x4d50e20
Jul 07 21:12:10-600101 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:10-600282 util-8627 DEBUG process_notify is running
Jul 07 21:12:10-600455 util-8627 DEBUG client_notify is running
Jul 07 21:12:10-600692 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:10-600900 util-scheduler-8627 DEBUG Adding task: 814 / 0x4d50e20
Jul 07 21:12:10-601103 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:10-607837 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:10-608044 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:10-608290 util-scheduler-8627 DEBUG Checking readiness of task: 814 / 0x4d50e20
Jul 07 21:12:10-608483 util-scheduler-8627 DEBUG Checking readiness of task: 813 / 0x4661f98
Jul 07 21:12:10-608673 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:10-608863 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:10-609052 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:10-609268 util-scheduler-8627 DEBUG Running task: 814 / 0x4d50e20
Jul 07 21:12:10-609453 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:10-609627 util-8627 DEBUG process_notify is running
Jul 07 21:12:10-609796 util-8627 DEBUG client_notify is running
Jul 07 21:12:10-610007 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:10-610252 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:12-428872 util-scheduler-8627 DEBUG Checking readiness of task: 813 / 0x4661f98
Jul 07 21:12:12-429300 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:12-429499 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:12-429721 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:12-429920 util-scheduler-8627 DEBUG Running task: 813 / 0x4661f98
Jul 07 21:12:12-430347 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:12-430606 util-scheduler-8627 DEBUG Adding task: 815 / 0x4662140
Jul 07 21:12:12-430885 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:12-431076 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:12-431267 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:12-431456 util-scheduler-8627 DEBUG Running task: 815 / 0x4662140
Jul 07 21:12:12-431647 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:12-431847 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:12-432076 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:12-432339 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:12-432593 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:12-432821 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:12-433029 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:12-433299 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:12-433508 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:12-433697 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:12-433883 util-scheduler-8627 DEBUG Canceling task: 811 / 0x4e61600
Jul 07 21:12:12-434104 util-scheduler-8627 DEBUG Adding task: 816 / 0x4e61600
Jul 07 21:12:12-434281 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:12-434538 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:12-434753 util-scheduler-8627 DEBUG Adding task: 817 / 0x4d50e20
Jul 07 21:12:12-434934 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:12-435133 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:12-435350 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:12-435556 util-scheduler-8627 DEBUG Adding task: 818 / 0x4661f98
Jul 07 21:12:12-435804 util-scheduler-8627 DEBUG Checking readiness of task: 818 / 0x4661f98
Jul 07 21:12:12-435996 util-scheduler-8627 DEBUG Checking readiness of task: 817 / 0x4d50e20
Jul 07 21:12:12-436191 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:12-436381 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:12-436571 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:12-436762 util-scheduler-8627 DEBUG Running task: 817 / 0x4d50e20
Jul 07 21:12:12-436959 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:12-437137 util-8627 DEBUG process_notify is running
Jul 07 21:12:12-437406 util-8627 DEBUG client_notify is running
Jul 07 21:12:12-437645 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:12-437853 util-scheduler-8627 DEBUG Adding task: 819 / 0x4d50e20
Jul 07 21:12:12-438054 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:12-438348 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:12-438548 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:12-438788 util-scheduler-8627 DEBUG Checking readiness of task: 819 / 0x4d50e20
Jul 07 21:12:12-438981 util-scheduler-8627 DEBUG Checking readiness of task: 818 / 0x4661f98
Jul 07 21:12:12-439171 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:12-439360 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:12-439550 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:12-439740 util-scheduler-8627 DEBUG Running task: 819 / 0x4d50e20
Jul 07 21:12:12-439940 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:12-440117 util-8627 DEBUG process_notify is running
Jul 07 21:12:12-440285 util-8627 DEBUG client_notify is running
Jul 07 21:12:12-440494 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:12-440778 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:15-132807 util-scheduler-8627 DEBUG Checking readiness of task: 818 / 0x4661f98
Jul 07 21:12:15-133218 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:15-133418 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:15-133611 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:15-133810 util-scheduler-8627 DEBUG Running task: 818 / 0x4661f98
Jul 07 21:12:15-134234 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:15-134493 util-scheduler-8627 DEBUG Adding task: 820 / 0x4662140
Jul 07 21:12:15-134771 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:15-134964 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:15-135155 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:15-135345 util-scheduler-8627 DEBUG Running task: 820 / 0x4662140
Jul 07 21:12:15-135537 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:15-135737 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:15-135970 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:15-136235 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:15-136477 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:15-136705 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:15-136913 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:15-137160 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:15-140422 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:15-140619 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:15-140809 util-scheduler-8627 DEBUG Canceling task: 816 / 0x4e61600
Jul 07 21:12:15-141035 util-scheduler-8627 DEBUG Adding task: 821 / 0x4e61600
Jul 07 21:12:15-141241 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:15-141526 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:15-141745 util-scheduler-8627 DEBUG Adding task: 822 / 0x4d50e20
Jul 07 21:12:15-141927 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:15-142126 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:15-142344 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:15-142551 util-scheduler-8627 DEBUG Adding task: 823 / 0x4661f98
Jul 07 21:12:15-142808 util-scheduler-8627 DEBUG Checking readiness of task: 823 / 0x4661f98
Jul 07 21:12:15-143001 util-scheduler-8627 DEBUG Checking readiness of task: 822 / 0x4d50e20
Jul 07 21:12:15-143193 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:15-143383 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:15-143572 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:15-143764 util-scheduler-8627 DEBUG Running task: 822 / 0x4d50e20
Jul 07 21:12:15-143950 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:15-144128 util-8627 DEBUG process_notify is running
Jul 07 21:12:15-144300 util-8627 DEBUG client_notify is running
Jul 07 21:12:15-144537 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:15-144745 util-scheduler-8627 DEBUG Adding task: 824 / 0x4d50e20
Jul 07 21:12:15-144947 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:15-145213 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:15-145969 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:15-146216 util-scheduler-8627 DEBUG Checking readiness of task: 824 / 0x4d50e20
Jul 07 21:12:15-146410 util-scheduler-8627 DEBUG Checking readiness of task: 823 / 0x4661f98
Jul 07 21:12:15-146601 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:15-146792 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:15-146983 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:15-147175 util-scheduler-8627 DEBUG Running task: 824 / 0x4d50e20
Jul 07 21:12:15-147360 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:15-147535 util-8627 DEBUG process_notify is running
Jul 07 21:12:15-147705 util-8627 DEBUG client_notify is running
Jul 07 21:12:15-147915 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:15-148228 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:20-483752 util-scheduler-8627 DEBUG Checking readiness of task: 823 / 0x4661f98
Jul 07 21:12:20-484137 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:20-484335 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:20-484527 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:20-484725 util-scheduler-8627 DEBUG Running task: 823 / 0x4661f98
Jul 07 21:12:20-485149 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:20-485440 util-scheduler-8627 DEBUG Adding task: 825 / 0x4662140
Jul 07 21:12:20-487383 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:20-487742 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:20-487938 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:20-488136 util-scheduler-8627 DEBUG Running task: 825 / 0x4662140
Jul 07 21:12:20-488331 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:20-488535 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:20-488774 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:20-489062 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:20-489394 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:20-489624 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:20-489833 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:20-490082 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:20-490291 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:20-490481 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:20-490668 util-scheduler-8627 DEBUG Canceling task: 821 / 0x4e61600
Jul 07 21:12:20-490898 util-scheduler-8627 DEBUG Adding task: 826 / 0x4e61600
Jul 07 21:12:20-491076 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:20-491338 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:20-492864 util-scheduler-8627 DEBUG Adding task: 827 / 0x4d50e20
Jul 07 21:12:20-493052 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:20-493280 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:20-493503 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:20-493712 util-scheduler-8627 DEBUG Adding task: 828 / 0x4661f98
Jul 07 21:12:20-493967 util-scheduler-8627 DEBUG Checking readiness of task: 828 / 0x4661f98
Jul 07 21:12:20-494162 util-scheduler-8627 DEBUG Checking readiness of task: 827 / 0x4d50e20
Jul 07 21:12:20-494355 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:20-494546 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:20-494736 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:20-494957 util-scheduler-8627 DEBUG Running task: 827 / 0x4d50e20
Jul 07 21:12:20-495145 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:20-495325 util-8627 DEBUG process_notify is running
Jul 07 21:12:20-496044 util-8627 DEBUG client_notify is running
Jul 07 21:12:20-496286 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:20-496496 util-scheduler-8627 DEBUG Adding task: 829 / 0x4d50e20
Jul 07 21:12:20-496700 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:20-497020 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:20-497245 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:20-497545 util-scheduler-8627 DEBUG Checking readiness of task: 829 / 0x4d50e20
Jul 07 21:12:20-497740 util-scheduler-8627 DEBUG Checking readiness of task: 828 / 0x4661f98
Jul 07 21:12:20-497932 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:20-498429 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:20-499071 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:20-499654 util-scheduler-8627 DEBUG Running task: 829 / 0x4d50e20
Jul 07 21:12:20-500037 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:20-500228 util-8627 DEBUG process_notify is running
Jul 07 21:12:20-500398 util-8627 DEBUG client_notify is running
Jul 07 21:12:20-500609 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:20-500941 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:25-901024 util-scheduler-8627 DEBUG Checking readiness of task: 828 / 0x4661f98
Jul 07 21:12:25-901442 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:25-901640 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:25-901834 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:25-902032 util-scheduler-8627 DEBUG Running task: 828 / 0x4661f98
Jul 07 21:12:25-902458 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:25-902719 util-scheduler-8627 DEBUG Adding task: 830 / 0x4662140
Jul 07 21:12:25-903000 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:25-903192 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:25-903383 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:25-903573 util-scheduler-8627 DEBUG Running task: 830 / 0x4662140
Jul 07 21:12:25-903765 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:25-903966 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:25-904200 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:25-904464 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:25-904707 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:25-904936 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:25-905145 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:25-905420 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:25-905629 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:25-905820 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:25-906007 util-scheduler-8627 DEBUG Canceling task: 826 / 0x4e61600
Jul 07 21:12:25-906232 util-scheduler-8627 DEBUG Adding task: 831 / 0x4e61600
Jul 07 21:12:25-906411 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:25-906669 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:25-906887 util-scheduler-8627 DEBUG Adding task: 832 / 0x4d50e20
Jul 07 21:12:25-907070 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:25-907311 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:25-907529 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:25-907737 util-scheduler-8627 DEBUG Adding task: 833 / 0x4661f98
Jul 07 21:12:25-907988 util-scheduler-8627 DEBUG Checking readiness of task: 833 / 0x4661f98
Jul 07 21:12:25-908201 util-scheduler-8627 DEBUG Checking readiness of task: 832 / 0x4d50e20
Jul 07 21:12:25-908394 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:25-908585 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:25-908774 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:25-908967 util-scheduler-8627 DEBUG Running task: 832 / 0x4d50e20
Jul 07 21:12:25-909153 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:25-911996 util-8627 DEBUG process_notify is running
Jul 07 21:12:25-912178 util-8627 DEBUG client_notify is running
Jul 07 21:12:25-912422 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:25-912634 util-scheduler-8627 DEBUG Adding task: 834 / 0x4d50e20
Jul 07 21:12:25-912839 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:25-913177 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:25-913405 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:25-913653 util-scheduler-8627 DEBUG Checking readiness of task: 834 / 0x4d50e20
Jul 07 21:12:25-913848 util-scheduler-8627 DEBUG Checking readiness of task: 833 / 0x4661f98
Jul 07 21:12:25-914039 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:25-914232 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:25-914422 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:25-914614 util-scheduler-8627 DEBUG Running task: 834 / 0x4d50e20
Jul 07 21:12:25-914798 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:25-914973 util-8627 DEBUG process_notify is running
Jul 07 21:12:25-915142 util-8627 DEBUG client_notify is running
Jul 07 21:12:25-915351 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:25-915664 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:30-137880 util-scheduler-8627 DEBUG Checking readiness of task: 833 / 0x4661f98
Jul 07 21:12:30-138276 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:30-138472 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:30-138663 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:30-138860 util-scheduler-8627 DEBUG Running task: 833 / 0x4661f98
Jul 07 21:12:30-139282 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:30-139538 util-scheduler-8627 DEBUG Adding task: 835 / 0x4662140
Jul 07 21:12:30-139812 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:30-140003 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:30-140192 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:30-140381 util-scheduler-8627 DEBUG Running task: 835 / 0x4662140
Jul 07 21:12:30-140571 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:30-140769 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:30-140997 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:30-141281 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:30-141523 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:30-141750 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:30-141985 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:30-142232 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:30-142439 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:30-142627 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:30-142812 util-scheduler-8627 DEBUG Canceling task: 831 / 0x4e61600
Jul 07 21:12:30-143052 util-scheduler-8627 DEBUG Adding task: 836 / 0x4e61600
Jul 07 21:12:30-143230 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:30-143484 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:30-143700 util-scheduler-8627 DEBUG Adding task: 837 / 0x4d50e20
Jul 07 21:12:30-143880 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:30-144078 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:30-144292 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:30-144497 util-scheduler-8627 DEBUG Adding task: 838 / 0x4661f98
Jul 07 21:12:30-144745 util-scheduler-8627 DEBUG Checking readiness of task: 838 / 0x4661f98
Jul 07 21:12:30-144936 util-scheduler-8627 DEBUG Checking readiness of task: 837 / 0x4d50e20
Jul 07 21:12:30-145127 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:30-147126 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:30-147327 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:30-147523 util-scheduler-8627 DEBUG Running task: 837 / 0x4d50e20
Jul 07 21:12:30-147711 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:30-147891 util-8627 DEBUG process_notify is running
Jul 07 21:12:30-148064 util-8627 DEBUG client_notify is running
Jul 07 21:12:30-148305 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:30-148515 util-scheduler-8627 DEBUG Adding task: 839 / 0x4d50e20
Jul 07 21:12:30-148718 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:30-149016 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:30-149247 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:30-149513 util-scheduler-8627 DEBUG Checking readiness of task: 839 / 0x4d50e20
Jul 07 21:12:30-149710 util-scheduler-8627 DEBUG Checking readiness of task: 838 / 0x4661f98
Jul 07 21:12:30-149962 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:30-150154 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:30-150343 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:30-150534 util-scheduler-8627 DEBUG Running task: 839 / 0x4d50e20
Jul 07 21:12:30-150718 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:30-150893 util-8627 DEBUG process_notify is running
Jul 07 21:12:30-151062 util-8627 DEBUG client_notify is running
Jul 07 21:12:30-151278 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:30-151564 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:32-059239 util-scheduler-8627 DEBUG Checking readiness of task: 838 / 0x4661f98
Jul 07 21:12:32-059625 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:32-059828 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:32-060026 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:32-060227 util-scheduler-8627 DEBUG Running task: 838 / 0x4661f98
Jul 07 21:12:32-060655 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:32-060917 util-scheduler-8627 DEBUG Adding task: 840 / 0x4662140
Jul 07 21:12:32-061226 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:32-061424 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:32-061618 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:32-061842 util-scheduler-8627 DEBUG Running task: 840 / 0x4662140
Jul 07 21:12:32-062038 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:32-062261 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:32-062501 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:32-062781 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:32-063040 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:32-063273 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:32-063487 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:32-063736 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:32-063945 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:32-064140 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:32-064332 util-scheduler-8627 DEBUG Canceling task: 836 / 0x4e61600
Jul 07 21:12:32-064562 util-scheduler-8627 DEBUG Adding task: 841 / 0x4e61600
Jul 07 21:12:32-064745 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:32-065008 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:32-065250 util-scheduler-8627 DEBUG Adding task: 842 / 0x4d50e20
Jul 07 21:12:32-065437 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:32-065639 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:32-065858 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:32-066066 util-scheduler-8627 DEBUG Adding task: 843 / 0x4661f98
Jul 07 21:12:32-066326 util-scheduler-8627 DEBUG Checking readiness of task: 843 / 0x4661f98
Jul 07 21:12:32-066521 util-scheduler-8627 DEBUG Checking readiness of task: 842 / 0x4d50e20
Jul 07 21:12:32-066716 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:32-066907 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:32-067098 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:32-067292 util-scheduler-8627 DEBUG Running task: 842 / 0x4d50e20
Jul 07 21:12:32-067480 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:32-067659 util-8627 DEBUG process_notify is running
Jul 07 21:12:32-067832 util-8627 DEBUG client_notify is running
Jul 07 21:12:32-068068 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:32-068277 util-scheduler-8627 DEBUG Adding task: 844 / 0x4d50e20
Jul 07 21:12:32-068481 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:32-068737 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:32-068939 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:32-069180 util-scheduler-8627 DEBUG Checking readiness of task: 844 / 0x4d50e20
Jul 07 21:12:32-069398 util-scheduler-8627 DEBUG Checking readiness of task: 843 / 0x4661f98
Jul 07 21:12:32-069604 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:32-069796 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:32-069999 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:32-070192 util-scheduler-8627 DEBUG Running task: 844 / 0x4d50e20
Jul 07 21:12:32-070377 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:32-070552 util-8627 DEBUG process_notify is running
Jul 07 21:12:32-070723 util-8627 DEBUG client_notify is running
Jul 07 21:12:32-070933 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:32-071178 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:35-744130 util-scheduler-8627 DEBUG Checking readiness of task: 843 / 0x4661f98
Jul 07 21:12:35-744503 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:35-744700 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:35-744924 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:35-745121 util-scheduler-8627 DEBUG Running task: 843 / 0x4661f98
Jul 07 21:12:35-745574 util-8627 DEBUG receive_ready read 84/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:12:35-745835 util-scheduler-8627 DEBUG Adding task: 845 / 0x4662140
Jul 07 21:12:35-746117 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:35-746311 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:35-746509 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:35-746701 util-scheduler-8627 DEBUG Running task: 845 / 0x4662140
Jul 07 21:12:35-746894 util-8627 DEBUG Received message of type 70 and size 84 from core service.
Jul 07 21:12:35-747097 core-api-8627 DEBUG Processing message of type 70 and size 84 from core service
Jul 07 21:12:35-747330 core-api-8627 DEBUG Received message of type 262 and size 48 from peer `V8XX'
Jul 07 21:12:35-747595 cadet-con-8627 INFO <-- {                KX} on connection MCZ5X28Z from V8XX
Jul 07 21:12:35-747839 cadet-con-8627 DEBUG  on connection MCZ5X28Z (->V8XX)
Jul 07 21:12:35-748070 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:35-748279 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:12:35-748529 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:12:35-748738 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:12:35-748928 cadet-con-8627 DEBUG Connection BCK reset timeout
Jul 07 21:12:35-749115 util-scheduler-8627 DEBUG Canceling task: 841 / 0x4e61600
Jul 07 21:12:35-749369 util-scheduler-8627 DEBUG Adding task: 846 / 0x4e61600
Jul 07 21:12:35-749551 cadet-con-8627 DEBUG   message for us!
Jul 07 21:12:35-749809 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:35-750027 util-scheduler-8627 DEBUG Adding task: 847 / 0x4d50e20
Jul 07 21:12:35-750211 cadet-tun-8627 DEBUG kx message received
Jul 07 21:12:35-750409 cadet-tun-8627 INFO <=== PONG for V8XX
Jul 07 21:12:35-750647 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:35-750855 util-scheduler-8627 DEBUG Adding task: 848 / 0x4661f98
Jul 07 21:12:35-751111 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:12:35-751307 util-scheduler-8627 DEBUG Checking readiness of task: 847 / 0x4d50e20
Jul 07 21:12:35-751500 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:35-751690 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:35-751879 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:35-752072 util-scheduler-8627 DEBUG Running task: 847 / 0x4d50e20
Jul 07 21:12:35-752259 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:35-752437 util-8627 DEBUG process_notify is running
Jul 07 21:12:35-752609 util-8627 DEBUG client_notify is running
Jul 07 21:12:35-752847 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:12:35-753058 util-scheduler-8627 DEBUG Adding task: 849 / 0x4d50e20
Jul 07 21:12:35-753283 util-8627 DEBUG Transmitting message of type 168 and size 42 to statistics service.
Jul 07 21:12:35-753584 util-8627 DEBUG Connection transmitted 42/42 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:35-753842 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:12:35-754092 util-scheduler-8627 DEBUG Checking readiness of task: 849 / 0x4d50e20
Jul 07 21:12:35-754287 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:12:35-754478 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:35-754669 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:35-754859 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:35-755052 util-scheduler-8627 DEBUG Running task: 849 / 0x4d50e20
Jul 07 21:12:35-755259 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:12:35-755436 util-8627 DEBUG process_notify is running
Jul 07 21:12:35-755607 util-8627 DEBUG client_notify is running
Jul 07 21:12:35-755823 util-8627 DEBUG Transmitting message of type 168 and size 48 to statistics service.
Jul 07 21:12:35-756061 util-8627 DEBUG Connection transmitted 48/48 bytes to `/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' (0x4d50e20)
Jul 07 21:12:46-078123 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:12:46-078517 util-scheduler-8627 DEBUG Checking readiness of task: 809 / 0x465ed58
Jul 07 21:12:46-078719 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:46-078915 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:46-079115 util-scheduler-8627 DEBUG Running task: 809 / 0x465ed58
Jul 07 21:12:46-079546 util-8627 DEBUG receive_ready read 104/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:12:46-079807 util-scheduler-8627 DEBUG Adding task: 850 / 0x465ef00
Jul 07 21:12:46-080090 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:12:46-080285 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:46-080479 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:46-080673 util-scheduler-8627 DEBUG Running task: 850 / 0x465ef00
Jul 07 21:12:46-080869 util-8627 DEBUG Received message of type 332 and size 104 from peerinfo service.
Jul 07 21:12:46-081112 nse-api-8627 DEBUG Received information about peer `P00P' from peerinfo database
Jul 07 21:12:46-081431 cadet-hll-8627 DEBUG  hello for P00P (64 bytes), expires on Tue Jul 08 09:12:46 2014
Jul 07 21:12:46-081659 cadet-p2p-8627 DEBUG set hello for P00P
Jul 07 21:12:46-081943 cadet-p2p-8627 DEBUG  merge into 0x5dc6dd0 (64 bytes)
Jul 07 21:12:46-082140 util-8627 DEBUG calling GNUNET_CONNECTION_receive
Jul 07 21:12:46-082356 util-scheduler-8627 DEBUG Adding task: 851 / 0x465ed58
Jul 07 21:12:55-189380 util-scheduler-8627 DEBUG Checking readiness of task: 851 / 0x465ed58
Jul 07 21:12:55-189770 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:12:55-189966 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:12:55-190171 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:12:55-190365 util-scheduler-8627 DEBUG Running task: 774 / 0x4d63d80
Jul 07 21:12:55-191966 cadet-tun-8627 INFO finish KX for V8XX
Jul 07 21:13:28-319329 util-scheduler-8627 DEBUG Checking readiness of task: 851 / 0x465ed58
Jul 07 21:13:28-319709 util-scheduler-8627 DEBUG Checking readiness of task: 848 / 0x4661f98
Jul 07 21:13:28-319904 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:13:28-320098 util-scheduler-8627 DEBUG Checking readiness of task: 375 / 0x4665ad8
Jul 07 21:13:28-320295 util-scheduler-8627 DEBUG Running task: 375 / 0x4665ad8
Jul 07 21:13:28-320720 util-8627 DEBUG receive_ready read 0/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-dht.sock' (0x4665ad8)!
Jul 07 21:13:28-323307 util-8627 DEBUG Timeout in receive_helper, available 0, client->connection non-NULL, errCode `Success'
Jul 07 21:13:28-324759 dht-api-8627 DEBUG Error receiving data from DHT service, reconnecting
Jul 07 21:13:28-327215 cadet-8627 DEBUG Disconnecting from DHT service, will try to reconnect in 0 ms
Jul 07 21:13:28-329980 util-8627 DEBUG Shutting down connection (0x4665ad8)
Jul 07 21:13:28-336038 util-scheduler-8627 DEBUG Adding task: 852 / 0x46641b8
Jul 07 21:13:28-336751 util-scheduler-8627 DEBUG Running task: 848 / 0x4661f98
Jul 07 21:13:28-337168 util-8627 DEBUG receive_ready read 0/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-core.sock' (0x4661f98)!
Jul 07 21:13:28-337699 util-8627 DEBUG Timeout in receive_helper, available 0, client->connection non-NULL, errCode `Success'
Jul 07 21:13:28-339169 core-api-8627 INFO Client was disconnected from core service, trying to reconnect.
Jul 07 21:13:28-340553 util-8627 DEBUG Shutting down connection (0x4661f98)
Jul 07 21:13:28-341370 util-scheduler-8627 DEBUG Adding task: 853 / 0x4660500
Jul 07 21:13:28-344186 cadet-p2p-8627 INFO DISCONNECTED GN10 (self)
Jul 07 21:13:28-345044 cadet-p2p-8627 DEBUG   notifying MCZ5X28Z (->V8XX) due to V8XX
Jul 07 21:13:28-345489 cadet-con-8627 DEBUG  notify broken on MCZ5X28Z (->V8XX) due to V8XX disconnect
Jul 07 21:13:28-345734 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-345945 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:13:28-348779 cadet-con-8627 INFO --> { CONNECTION_BROKEN} ( 0) on connection MCZ5X28Z (->V8XX) (100 bytes)
Jul 07 21:13:28-348994 cadet-con-8627 DEBUG   C_P+ 0x4e61600 0
Jul 07 21:13:28-349280 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-349503 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:13:28-349805 cadet-p2p-8627 INFO que { CONNECTION_BROKEN} ( 0) on connection MCZ5X28Z (->V8XX) (0x4e61600) FWD towards V8XX (size 100)
Jul 07 21:13:28-350006 cadet-p2p-8627 DEBUG priority 0
Jul 07 21:13:28-350235 cadet-con-8627 DEBUG  checking sendability of FWD traffic on MCZ5X28Z (->V8XX)
Jul 07 21:13:28-350420 cadet-con-8627 DEBUG  last ack recv: 0, last pid sent: 4294967295
Jul 07 21:13:28-350598 cadet-con-8627 DEBUG  sendable
Jul 07 21:13:28-350816 cadet-p2p-8627 DEBUG calling core tmt rdy towards V8XX for 100 bytes
Jul 07 21:13:28-351034 core-api-8627 DEBUG Asking core for transmission of 100 bytes to `V8XX'
Jul 07 21:13:28-351256 util-scheduler-8627 DEBUG Adding task: 854 / 0x4e607e8
Jul 07 21:13:28-351438 core-api-8627 DEBUG Transmission request added to queue
Jul 07 21:13:28-351644 cadet-p2p-8627 DEBUG QQQ Message queue towards V8XX
Jul 07 21:13:28-351821 cadet-p2p-8627 DEBUG QQQ  queue length: 1
Jul 07 21:13:28-351997 cadet-p2p-8627 DEBUG QQQ  core tmt rdy: 0x4e60814
Jul 07 21:13:28-352236 cadet-p2p-8627 DEBUG QQQ  - { CONNECTION_BROKEN} FWD on MCZ5X28Z (->V8XX)
Jul 07 21:13:28-352420 cadet-p2p-8627 DEBUG QQQ    payload , 0
Jul 07 21:13:28-352596 cadet-p2p-8627 DEBUG QQQ    size: 100 bytes
Jul 07 21:13:28-352795 cadet-p2p-8627 DEBUG QQQ End queue towards V8XX
Jul 07 21:13:28-353469 cadet-con-8627 DEBUG  *** Cancel BCK queues for connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-353710 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-353920 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:13:28-354956 util-8627 DEBUG Scheduling transmission (0x4d50e20).
Jul 07 21:13:28-355185 util-scheduler-8627 DEBUG Adding task: 855 / 0x4d50e20
Jul 07 21:13:28-355926 cadet-p2p-8627 INFO DISCONNECTED GN10 <= KNAS
Jul 07 21:13:28-356245 cadet-p2p-8627 INFO DISCONNECTED GN10 <= STRN
Jul 07 21:13:28-358760 cadet-p2p-8627 INFO DISCONNECTED GN10 <= TZQE
Jul 07 21:13:28-359198 util-scheduler-8627 DEBUG Canceling task: 854 / 0x4e607e8
Jul 07 21:13:28-359613 cadet-p2p-8627 INFO DISCONNECTED GN10 <= V8XX
Jul 07 21:13:28-359867 cadet-p2p-8627 DEBUG   notifying MCZ5X28Z (->V8XX) due to V8XX
Jul 07 21:13:28-360125 cadet-con-8627 DEBUG  notify broken on MCZ5X28Z (->V8XX) due to V8XX disconnect
Jul 07 21:13:28-360357 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-360564 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:13:28-361052 cadet-con-8627 DEBUG destroying connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-361460 cadet-con-8627 DEBUG  fc's f: 0x4e61604, b: 0x4e61638
Jul 07 21:13:28-361806 cadet-con-8627 DEBUG  fc tasks f: 0, b: 0
Jul 07 21:13:28-362045 cadet-con-8627 DEBUG  *** Cancel FWD queues for connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-362279 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-362487 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:13:28-363927 cadet-p2p-8627 DEBUG GMP queue cancel { CONNECTION_BROKEN}
Jul 07 21:13:28-365871 cadet-p2p-8627 DEBUG queue destroy type { CONNECTION_BROKEN}
Jul 07 21:13:28-366734 cadet-p2p-8627 DEBUG  calling callback
Jul 07 21:13:28-366924 cadet-con-8627 DEBUG connection message_sent
Jul 07 21:13:28-367417 cadet-con-8627 DEBUG  not sent FWD { CONNECTION_BROKEN}
Jul 07 21:13:28-367637 cadet-con-8627 DEBUG  C_P- 0x4e61600 1
Jul 07 21:13:28-367817 cadet-con-8627 DEBUG !  message sent!
Jul 07 21:13:28-369801 core-api-8627 DEBUG Aborting transmission request to core for 100 bytes to `V8XX'
Jul 07 21:13:28-371502 cadet-con-8627 DEBUG  *** Cancel BCK queues for connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-371743 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-371955 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:13:28-372196 cadet-con-8627 DEBUG  get next hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-372406 cadet-con-8627 DEBUG   ID: V8XX (9)
Jul 07 21:13:28-372646 cadet-p2p-8627 DEBUG removing connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-372847 cadet-p2p-8627 DEBUG from peer V8XX
Jul 07 21:13:28-373051 cadet-p2p-8627 DEBUG peer V8XX ok, has 1 connections.
Jul 07 21:13:28-373337 cadet-con-8627 DEBUG  get prev hop MCZ5X28Z (->V8XX) [0/2]
Jul 07 21:13:28-373546 cadet-con-8627 DEBUG   ID: GN10 (1)
Jul 07 21:13:28-373777 cadet-p2p-8627 DEBUG removing connection MCZ5X28Z (->V8XX)
Jul 07 21:13:28-373975 cadet-p2p-8627 DEBUG from peer GN10
Jul 07 21:13:28-375125 cadet-p2p-8627 DEBUG Peer GN10 is not a neighbor!
Jul 07 21:13:28-376357 cadet-con-8627 DEBUG   cstate: 4
Jul 07 21:13:28-377048 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL TOWARDS V8XX
Jul 07 21:13:28-377264 cadet-tun-8627 DEBUG TTT  cstate CADET_TUNNEL_READY, estate CADET_TUNNEL_KEY_OK
Jul 07 21:13:28-377456 cadet-tun-8627 DEBUG TTT  kx_ctx (nil), rekey_task 0
Jul 07 21:13:28-377639 cadet-tun-8627 DEBUG TTT  tq_head (nil), tq_tail (nil)
Jul 07 21:13:28-377828 cadet-tun-8627 DEBUG TTT  destroy 0
Jul 07 21:13:28-378000 cadet-tun-8627 DEBUG TTT  channels:
Jul 07 21:13:28-378168 cadet-tun-8627 DEBUG TTT  connections:
Jul 07 21:13:28-378405 cadet-tun-8627 DEBUG TTT  - MCZ5X28Z (->V8XX) [4] buf: 11/11 (qn 0/0)
Jul 07 21:13:28-378592 cadet-tun-8627 DEBUG TTT DEBUG TUNNEL END
Jul 07 21:13:28-379024 cadet-con-8627 DEBUG  fc tasks f: 0, b: 0
Jul 07 21:13:28-379435 cadet-tun-8627 DEBUG Removing connection MCZ5X28Z (->V8XX) from tunnel V8XX
Jul 07 21:13:28-379721 cadet-tun-8627 DEBUG   no more connections, getting new ones
Jul 07 21:13:28-379936 cadet-tun-8627 DEBUG Tunnel V8XX cstate CADET_TUNNEL_READY => CADET_TUNNEL_SEARCHING
Jul 07 21:13:28-380153 cadet-p2p-8627 DEBUG peer_connect towards V8XX
Jul 07 21:13:28-380419 transport-api-8627 DEBUG Offering `HELLO' message of `V8XX' to transport for validation.
Jul 07 21:13:28-380615 transport-api-8627 DEBUG Control transmit of 491 bytes requested
Jul 07 21:13:28-380833 transport-api-8627 DEBUG Scheduling next transmission to service in 0 ms
Jul 07 21:13:28-381040 util-scheduler-8627 DEBUG Adding task: 856 / 0x46623e0
Jul 07 21:13:28-381418 util-scheduler-8627 DEBUG Canceling task: 797 / 0x4e61600
Jul 07 21:13:28-381626 util-scheduler-8627 DEBUG Canceling task: 846 / 0x4e61600
Jul 07 21:13:28-382690 cadet-p2p-8627 INFO DISCONNECTED GN10 <= D3TJ
Jul 07 21:13:28-386160 util-scheduler-8627 DEBUG Running task: 851 / 0x465ed58
Jul 07 21:13:28-386586 util-8627 DEBUG receive_ready read 0/65535 bytes from `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock' (0x465ed58)!
Jul 07 21:13:28-386816 util-8627 DEBUG Timeout in receive_helper, available 0, client->connection non-NULL, errCode `Success'
Jul 07 21:13:28-387355 util-8627 DEBUG Shutting down connection (0x465ed58)
Jul 07 21:13:28-388269 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:13:28-388467 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:13:28-388745 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:13:28-388959 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:13:28-389154 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:13:28-389371 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:13:28-389607 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:13:28-389832 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:13:28-390018 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:13:28-390221 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:13:28-390403 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:13:28-390577 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:13:28-390766 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:13:28-390947 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:13:28-391149 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:13:28-391328 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:13:28-391501 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:13:28-391672 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:13:28-391857 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:13:28-392061 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:13:28-392245 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:13:28-392441 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:13:28-392641 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:13:28-392860 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:13:28-393071 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:13:28-393309 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:13:28-393555 util-8627 DEBUG Asked to retrieve filename `UNIXPATH' in section `peerinfo'
Jul 07 21:13:28-393739 util-8627 DEBUG Asked to retrieve string `UNIXPATH' in section `peerinfo'
Jul 07 21:13:28-393987 util-8627 DEBUG Retrieved filename `$GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock', $-expanding
Jul 07 21:13:28-394182 util-8627 DEBUG Asked to $-expand $GNUNET_RUNTIME_DIR/gnunet-service-peerinfo.sock
Jul 07 21:13:28-394371 util-8627 DEBUG Split into `GNUNET_RUNTIME_DIR' and `gnunet-service-peerinfo.sock' with default (null)
Jul 07 21:13:28-394558 util-8627 DEBUG Asked to retrieve string `GNUNET_RUNTIME_DIR' in section `PATHS'
Jul 07 21:13:28-394788 util-8627 DEBUG Asked to $-expand ${TMPDIR:-${TMP:-/tmp}}/gnunet-system-runtime/
Jul 07 21:13:28-394989 util-8627 DEBUG Split into `TMPDIR' and `/gnunet-system-runtime/' with default ${TMP:-/tmp}
Jul 07 21:13:28-395173 util-8627 DEBUG Asked to retrieve string `TMPDIR' in section `PATHS'
Jul 07 21:13:28-395374 util-8627 DEBUG Filename for `TMPDIR' is not in PATHS config section
Jul 07 21:13:28-395552 util-8627 DEBUG `TMPDIR' is not an environment variable
Jul 07 21:13:28-395725 util-8627 DEBUG Asked to $-expand ${TMP:-/tmp}
Jul 07 21:13:28-395913 util-8627 DEBUG Split into `TMP' and `' with default /tmp
Jul 07 21:13:28-396093 util-8627 DEBUG Asked to retrieve string `TMP' in section `PATHS'
Jul 07 21:13:28-396294 util-8627 DEBUG Filename for `TMP' is not in PATHS config section
Jul 07 21:13:28-396487 util-8627 DEBUG `TMP' is not an environment variable
Jul 07 21:13:28-396660 util-8627 DEBUG Asked to $-expand /tmp
Jul 07 21:13:28-396829 util-8627 DEBUG Doesn't start with $ - not expanding
Jul 07 21:13:28-397011 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:13:28-397240 util-8627 DEBUG Expanded to `/tmp'
Jul 07 21:13:28-397426 util-8627 DEBUG Prefix is `/tmp'
Jul 07 21:13:28-397675 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime/'
Jul 07 21:13:28-397869 util-8627 DEBUG Prefix is `/tmp/gnunet-system-runtime/'
Jul 07 21:13:28-398077 util-8627 DEBUG Expanded to `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:13:28-398284 util-8627 DEBUG Expanded to filename `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock', *nix-expanding
Jul 07 21:13:28-398491 util-8627 DEBUG Filename result is `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'
Jul 07 21:13:28-399876 util-8627 DEBUG Connected to unixpath `/tmp/gnunet-system-runtime//gnunet-service-peerinfo.sock'!
Jul 07 21:13:28-401054 util-scheduler-8627 DEBUG Adding task: 857 / 0x5dcc670
Jul 07 21:13:28-405453 util-scheduler-8627 DEBUG Checking readiness of task: 855 / 0x4d50e20
Jul 07 21:13:28-405664 util-scheduler-8627 DEBUG Checking readiness of task: 455 / 0x4663c60
Jul 07 21:13:28-405865 util-scheduler-8627 DEBUG Running task: 455 / 0x4663c60
Jul 07 21:13:28-406680 util-scheduler-8627 DEBUG Adding task: 858 / 0x4663c60
Jul 07 21:13:28-407191 util-scheduler-8627 DEBUG Running task: 855 / 0x4d50e20
Jul 07 21:13:28-407385 util-8627 DEBUG transmit_ready running (0x4d50e20).
Jul 07 21:13:28-407674 util-8627 DEBUG Re-scheduling transmit_ready (more to do) (0x4d50e20).
Jul 07 21:13:28-408633 util-scheduler-8627 DEBUG Adding task: 859 / 0x4d50e20
Jul 07 21:13:28-409142 util-scheduler-8627 DEBUG Running task: 4 / (nil)
Jul 07 21:13:28-410079 cadet-8627 DEBUG shutting down
Jul 07 21:13:28-417180 util-scheduler-8627 DEBUG Canceling task: 857 / 0x5dcc670
Jul 07 21:13:28-418422 util-8627 DEBUG Shutting down connection (0x5dcc670)
Jul 07 21:13:28-420751 util-8627 DEBUG Shutting down connection (0x465d370)
Jul 07 21:13:28-423021 util-scheduler-8627 DEBUG Canceling task: 12 / (nil)
Jul 07 21:13:28-424672 cadet-tun-8627 DEBUG GCT_shutdown destroying tunnel at 0x4d63d80
Jul 07 21:13:28-426126 cadet-tun-8627 DEBUG destroying tunnel V8XX
Jul 07 21:13:28-431825 dht-api-8627 DEBUG Sending STOP for V8XXK9GA to DHT via 0x46641b8
Jul 07 21:13:28-436460 cadet-8627 DEBUG process_pending_messages called, but client is NULL, reconnecting
Jul 07 21:13:28-446701 util-scheduler-8627 DEBUG Canceling task: 852 / 0x46641b8
Jul 07 21:13:28-448020 util-scheduler-8627 DEBUG Canceling task: 73 / (nil)
Jul 07 21:13:28-450439 core-api-8627 DEBUG Disconnecting from CORE service
Jul 07 21:13:28-451609 util-scheduler-8627 DEBUG Canceling task: 853 / 0x4660500
Jul 07 21:13:28-454360 transport-api-8627 DEBUG Transport disconnect called!
Jul 07 21:13:28-456584 util-scheduler-8627 DEBUG Canceling task: 858 / 0x4663c60
Jul 07 21:13:28-457287 util-8627 DEBUG Shutting down connection (0x4663c60)
Jul 07 21:13:28-458629 util-scheduler-8627 DEBUG Canceling task: 856 / 0x46623e0
Jul 07 21:13:28-460577 transport-api-8627 DEBUG Timeout while trying to transmit `HELLO' request.
Jul 07 21:13:28-464064 transport-api-8627 DEBUG Scheduling task to reconnect to transport service in 0 ms.
Jul 07 21:13:28-464629 util-scheduler-8627 DEBUG Adding task: 860 / 0x46623e0
Jul 07 21:13:28-467903 util-scheduler-8627 DEBUG Canceling task: 860 / 0x46623e0
Jul 07 21:13:28-474444 util-scheduler-8627 DEBUG Canceling task: 859 / 0x4d50e20
Jul 07 21:13:28-475625 util-8627 DEBUG Shutting down connection (0x4d50e20)
Jul 07 21:13:28-478096 cadet-8627 DEBUG shut down
Jul 07 21:13:28-478302 util-scheduler-8627 DEBUG Running task: 3 / 0xbee5ea60
Jul 07 21:13:28-480350 util-8627 DEBUG Server shutting down.
Jul 07 21:13:28-482872 cadet-loc-8627 DEBUG client disconnected: (nil)
Jul 07 21:13:28-483874 cadet-loc-8627 DEBUG    (SERVER DOWN)
Jul 07 21:13:28-486260 cadet-loc-8627 DEBUG client connected: (nil)